Digest authentication on outgoing SIP trunk

I am doing some testing and my provider say to setup my trunk as digest and not register. They can’t provide me answers because they never setup FreePBX. I have the Provider domain, Customer DomainTrunk, Group ID, Username, Trunk Password and SBC SIP Interface. But how do I enter this info into the trunk page on FreePBX?

Can anyone Help? I need to setup the this trunk. This is what I got so far.

This is the outgoing Peer details

username=username

secret=**********

disallow=all

type=peer

port=5060

nat=auto

insecure=invite

host=siptrunking.bell.ca

dtmfmode=rfc2833

context=from-trunk

canreinvite=no

allow=ulaw&alaw&g729l

This is the Trace

OPTIONS sip:customer2.lab.internetvoice.ca:5060;maddr=173.238.1.246 SIP/2.0

Via: SIP/2.0/UDP 207.236.237.197:5060;branch=z9hG4bK7avhhf30107a3h7b8dt0

Call-ID: [email protected]

To: sip:[email protected]

From: sip:[email protected];tag=c9131ca320ce85761a43077a35c091b9000m192

Max-Forwards: 0

CSeq: 7058 OPTIONS

SIP/2.0 200 OK

Via: SIP/2.0/UDP 207.236.237.197:5060;branch=z9hG4bK7avhhf30107a3h7b8dt0;received=207.236.237.197;rport=5060

From: sip:[email protected];tag=c9131ca320ce85761a43077a35c091b9000m192

To: sip:[email protected];tag=as6c4d0826

Call-ID: [email protected]

CSeq: 7058 OPTIONS

Server: FPBX-13.0.195.4(11.25.3)

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

Supported: replaces, timer

Contact: sip:173.238.1.246:5060

Accept: application/sdp

Content-Length: 0

OPTIONS sip:customer2.lab.internetvoice.ca:5060;maddr=173.238.1.246 SIP/2.0

Via: SIP/2.0/UDP 207.236.237.197:5060;branch=z9hG4bK1jhaoe3010970qrtos20

Call-ID: [email protected]

To: sip:[email protected]

From: sip:[email protected];tag=c9131ca320ce85761a43077a35c091b9000mh92

Max-Forwards: 0

CSeq: 7059 OPTIONS

SIP/2.0 200 OK

Via: SIP/2.0/UDP 207.236.237.197:5060;branch=z9hG4bK1jhaoe3010970qrtos20;received=207.236.237.197;rport=5060

From: sip:[email protected];tag=c9131ca320ce85761a43077a35c091b9000mh92

To: sip:[email protected];tag=as67902044

Call-ID: d268b46436a317ac20597c77da0ed2[email protected]

CSeq: 7059 OPTIONS

Server: FPBX-13.0.195.4(11.25.3)

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

Supported: replaces, timer

Contact: sip:173.238.1.246:5060

Accept: application/sdp

Content-Length: 0

OPTIONS sip:customer2.lab.internetvoice.ca:5060;maddr=173.238.1.246 SIP/2.0

Via: SIP/2.0/UDP 207.236.237.197:5060;branch=z9hG4bKmrspin10201mcuc49s00

Call-ID: [email protected]

To: sip:[email protected]

From: sip:[email protected];tag=c9131ca320ce85761a43077a35c091b9000m1a2

Max-Forwards: 0

CSeq: 7060 OPTIONS

SIP/2.0 200 OK

Via: SIP/2.0/UDP 207.236.237.197:5060;branch=z9hG4bKmrspin10201mcuc49s00;received=207.236.237.197;rport=5060

From: sip:[email protected];tag=c9131ca320ce85761a43077a35c091b9000m1a2

To: sip:[email protected];tag=as067068d8

Call-ID: [email protected]

CSeq: 7060 OPTIONS

Server: FPBX-13.0.195.4(11.25.3)

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

Supported: replaces, timer

Contact: sip:173.238.1.246:5060

Accept: application/sdp

Content-Length: 0

OPTIONS sip:customer2.lab.internetvoice.ca:5060;maddr=173.238.1.246 SIP/2.0

Via: SIP/2.0/UDP 207.236.237.197:5060;branch=z9hG4bKcc12rn302gu24vl2qmr0

Call-ID: [email protected]

To: sip:[email protected]

From: sip:[email protected];tag=c9131ca320ce85761a43077a35c091b9000mha2

Max-Forwards: 0

CSeq: 7061 OPTIONS

SIP/2.0 200 OK

Via: SIP/2.0/UDP 207.236.237.197:5060;branch=z9hG4bKcc12rn302gu24vl2qmr0;received=207.236.237.197;rport=5060

From: sip:[email protected];tag=c9131ca320ce85761a43077a35c091b9000mha2

To: sip:[email protected];tag=as2a7c172b

Call-ID: [email protected]

CSeq: 7061 OPTIONS

Server: FPBX-13.0.195.4(11.25.3)

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

Supported: replaces, timer

Contact: sip:173.238.1.246:5060

Accept: application/sdp

Content-Length: 0

OPTIONS sip:customer2.lab.internetvoice.ca:5060;maddr=173.238.1.246 SIP/2.0

Via: SIP/2.0/UDP 207.236.237.197:5060;branch=z9hG4bK25jin92020q1mnda8hi0

Call-ID: [email protected]

To: sip:[email protected]

From: sip:[email protected];tag=c9131ca320ce85761a43077a35c091b9000m1b2

Max-Forwards: 0

CSeq: 7062 OPTIONS

SIP/2.0 200 OK

Via: SIP/2.0/UDP 207.236.237.197:5060;branch=z9hG4bK25jin92020q1mnda8hi0;received=207.236.237.197;rport=5060

From: sip:[email protected];tag=c9131ca320ce85761a43077a35c091b9000m1b2

To: sip:[email protected];tag=as1d467363

Call-ID: [email protected]

CSeq: 7062 OPTIONS

Server: FPBX-13.0.195.4(11.25.3)

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

Supported: replaces, timer

Contact: sip:173.238.1.246:5060

Accept: application/sdp

Content-Length: 0

Can you guys tell me if you notice anything wrong? They told me they were using Digest authentication if that helps.

Your SIP OPTIONS messages are irrelevant.

insecure=invite means your incoming calls are UN-authenticated.
If you need to authenticate - change it to insecure=no or remove the entire row (as insecure=no is the default)

Make a test outgoing call - that SIP trace is more relevant to this post…

Jonathan

I remove the insecure. Getting all circuits are busy and the call was not answered. The number I called did not ring.
Thank you

can you post a SIP trace of your call?

No.
insecure=invite means that your PBX won’t challenge incoming Invites for authentication. Many voice service providers require this.
Best practice is to not use insecure=invite at all, but use remotesecret= instead of secret if your voice service provider doesn’t want you to challenge incoming invites coming from them with a 401 unauthorized.

Remotesecret is a newer option that replaces insecure=invite.

(Technically the difference is that insecure=invite is an older option that disables authentication in the inbount direction, only for INVITEs, not REGISTERs.)

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.