Trunk authentication error on Telnyx only on new deployed instances V18

[acontreras]

I'm having some issues, deploying 3CX with telnyx sip trunking

Error: SIP/2.0 407 Proxy Authentication Required

technical details:
3CX cloud hosted on Amazon V 18.0 (Build 314)
Register to:sip.telnyx.com
Authentication type Don't required IP base
Call options: Allow inbound calls and Allow outbound calls
Extension use 3CX iphone APP V18.0.2.186


I can place outbound calls but any inbound call gets busy signal, I contacted Telnyx support regarding this issue and this is what they said to me:

Telnyx Support reply:
Mandatory IE Missing error. This happens whenever it is setup to register and expects Telnyx to send an authorization string on inbound calls. We don't allow registrations when using IP auth so we wouldn't be sending that authorization string. And I see you are using IP authentication on the assigned connection for this number.

You would need to configure your system to not register with us and not to expect that authorization string for IP auth to work. Otherwise, you can always use credential authentication.​

If I change the Authentication type to: Account based I can make it work but I have other 3CX instances running the same way with IP Base authentication without any issues.
This only happens on new deployed systems, any system upgraded from V16 to 18 works fine.

Any Ideas?

 

[ChrisC_3CX]

As per our 3CX Supported SIP Providers page Telnyx is supported as a Register based provider and that is why the 3CX template has "Register/Account Based" selected by default:



That said, these parameters are the ones the particular provider was tested with and the ones with which we can guarantee normal functionality so I'd recommend you stick with them.

 

[acontreras]

As per our 3CX Supported SIP Providers page Telnyx is supported as a Register based provider and that is why the 3CX template has "Register/Account Based" selected by default:
View attachment 27783


That said, these parameters are the ones the particular provider was tested with and the ones with which we can guarantee normal functionality so I'd recommend you stick with them.

Hi Chris,

I have some deployments from V16 where support was IP base, upgrade to V18 and they are still working, according to documentation I'll need to change all to account base.

This is something that when under the radar for me.

Works on upgrade it versions but not on newly stalled versions.

I get it but I don't get it.

Thanks

 

[ChrisC_3CX]

I see your point and can understand your predicament but since we have a specific recommended configuration for each supported provider, all I can really say is that we can't guarantee normal behavior if you deviate from it. That said, the fact that you have SIP Trunks configured in this manner that work is fortunate but it's not enough for us to confirm that you can have this config reliably.

You could also maybe take a look at your DIDs and make sure you're using the correct format (Telnyx requires E164 format) and also check Telnyx's portal to make sure you have the correct format settings there also. I highly recommend going over this guide and confirming everything mentioned applies for your setup as well. If you still can't get it to work, you will have to switch to Register Based.