Trunk down since update

[Badevil]

Hi together,

I got this moring the mail that my 3CX was successfully updated at 3:00am. Since this time my 3CX is not able to connect the SIP trunk. As I was not there I also did not changed anything.
In the log I can just see the following:
SIP Server/Call Manager ID: 12293

Registration at Deutsche Telekom has failed. Destination (sip:217.0.128.133:5060;transport=TCP;lr) is not reachable, DNS error resolving FQDN, or service is not available.

 

[leejor]

While not exactly the same , similar...
https://www.3cx.com/community/threads/sip-trunk-re-registration.69594/

You are now using 3CX SP?

 

[Badevil]

Not that I would know

 

[Badevil]

I noticed that since the Update something in the behavior of 3CX changed. My IPS is complaining about PROTOCOL-VOIP outbound 401 Unauthorized message
and when I check my firewall I can see the following:
Could not associate packet to any connection.
and if I check the capture on the FW or 3CX I noticed that it sends a PSH and as there is no known session it will be dropped... was there a switch from UDP to TCP?

 

[cobaltit]

And this is why auto-update is a bad idea. If you have auto discovery turned on I'd try forcing it to UDP.

 

[YiannisH_3CX]

Hello @Badevil

The 3CX Deutsche Telekom template always pointed to TCP so there should not be any change there. Are you using the default 3CX template? Can you check if Auto Discovery is on and that the transport option is set to TCP?