Telnyx TLS - registration intermittently fails 401 unauthorized

[rattler555]

Hello All,

I've recently setup a POC for a client with a sip trunk to Telnyx. Everything was working fine,, however a couple times I've found the trunk in a unregistered state. Refreshing registration would fix it sometimes. Othertimes, making a non-impacting change on the telnyx side would re-establish connectivity.

Does anyone have a similar setup and with TLS to Telnyx with long-term success? Any tuning I need to do? I'm also going to work with Tenlyx - will post if I find a resolution.

Thanks

 

[[email protected]]

I had some difficulty in getting SRTP to work as well. From a deployment standpoint, my Telnyx trunk(s) are still in Beta-- meaning primary voice traffic (outgoing and incoming) is not dependent on them being registered and online. When I was having trouble with it, Telnyx was able to resolve it on their end by opening a ticket.

That said, I have a second system deployed for a colleague that is also on a Telnyx trunk, and I have never been able to get his trunk to register successfully when SRTP is enabled. His is Hosted by 3CX, mine is on prem.

I know it doesn't give you a fix, but figured I would just share my experience that it seems like it's a little temperamental. In my experience, Telnyx ticket is probably your best way to the speediest resolution.

 

[NickD_3CX]

During our testing and on our testing SIP Trunks we have with Telnyx (on-prem and hosted) we have not observed any such behavior ourselves.

Have you followed the instructions for TLS as explained here?
Check the whole guide as well, just in case you have created a Telnyx account in a different way, in which case it may have something to do with that.

 

[rattler555]

Yes, I followed those instructions. Would changing the re-register parameter to 0 benefit this situation? Telnyx asked to disable this.

 

[YiannisH_3CX]

Yes, I followed those instructions. Would changing the re-register parameter to 0 benefit this situation? Telnyx asked to disable this.

You should leave the re-registration value to default as it will not benefit your situation. That is a suggestion timeout to the provider. It is the providers response in the 200 OK message that determines the actual re-registration timeout.
Check that your firewall does not have a low TCP connection timeout that would interfere with the TCP connection and see if increasing that resolves your issue.