Loop Sip Trunk always fails authentication even though its set as not required

[Lloyd M]

Hi. To fix a call routing issue I've been trying the suggestion I see a number of times in the forums to create a SIP Loop Trunk ...a generic trunk with address 127.0.0.1:5060 with no auth needed.....I've tried it several ways but it always fails....when any call routes out the loop trunk it fails saying:
; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
and:
[email protected]:5060> has failed; Cause: 403 Invalid credentials/INVITE from 127.0.0.1:5060

Any Ideas?

The reason I need this is that calls to our own 10 digit DID's on our main SIP trunk from internal phones will route back in and will connect but will end up with no audio so I'm trying a loop trunk. (I have made sure PBX Delivers Audio option is enabled on the phones).

Lloyd
School District 53, BC, Canada

 

[Lloyd M]

I tried this on another test 3CX server I have and a loopback worked just fine setup the same way. Maybe it has something to do with other SIP trunks on this main server. I have a main SIP trunk working fine and then several other SIP trunks that talk to Informacast messaging servers, as well as a bridge to another 3CX server...

 

[leejor]

I'm wondering if it is an extension issue rather than a trunk issue since it is the extension that is mentioned in the log. I haven't had the issue so I'm not sure how a failed log would look for that type of call.

While a loop trunk should work, have you considered putting the (as dialed) 10 digit numbers in each extensions SIP ID forcing the calls to route directly to each? It would save you a call licence per call.

 

[Lloyd M]

The SIP ID option does work and is what I'll probably do for now as a workaround.
However, I'm hoping to still figure out an answer because most of the DID's go to a digital receptionist rather than direct to a phone.
The outbound rule seems to be where it fails before even reaching the inbound rule. The outbound rule just strips the 7 off the 11 digits and sends it out the loop trunk. (it's setup here so they dial 7 first for outside calls).

 

[leejor]

The outbound rule seems to be where it fails before even reaching the inbound rule. The outbound rule just strips the 7 off the 11 digits and sends it out the loop trunk. (it's setup here so they dial 7 first for outside calls).

And have you placed the DID outbound rules above the "general" outbound rule? Rules are read from top to bottom, first match is taken.

 

[Lloyd M]

And have you placed the DID outbound rules above the "general" outbound rule? Rules are read from top to bottom, first match is taken.

Yes, it's at the top and the logs show it getting that rule...but failing when trying to use the loop trunk...