Calls get cancelled with 404 with German Telekom Sip

[mcom]

Since 2 days calls with the Telekom Magenta Sip Trunk gets cancelled after a few seconds.

Create a Pcap. It tells

Reason: SIP;cause=404;text="Not Found (1:27)"

It seems to be a problem with the Prio of SRV Records and Loadbalancing negotiation. After attempt to re register the call gets cancelled.

Auto Discovery for SRV is on.

Please help

 

[YiannisH_3CX]

HI @mcom

Since you run a capture you should see where the error is coming from. Is it coming from your providers IP? If so then contact them and ask them what is wrong. Usually these errors are caused by a number being dialed or sent in the wrong format. Your provider should be able to tell you exactly what the issue is.

 

[mcom]

It comes from the Provider Site. But the Problem is the new Update Build 18.0.3.444

After Updating there is the Problem with the SRV Priority. Before everything is good. Please check the Update with Telekom Sip Magenta.

I tried it with the stable Update 2 and Update 3 Beta. After Upgrading the error exists permanently. But only on the Telekom Sip

18.0 (Build 444)

 

[YiannisH_3CX]

What is the problem with the SRV priority? Can you provide a little more information?
For example what happens if you restart the SIP Server service? The PBX will perform a DNS query and try to connect. Does it connect successfully? Does it try to connect to the wrong protocol? Does it failover to another IP when a call fails?

 

[mcom]

Its about the reconnection with the Registrar Server. If the priority of the Registrar Server changes during a active call it send the timeout and cancel the call.

The Register of the SIP account is ok and work well.

This happened when updating to SP 3 Beta. On the stable Update 2 everything is fine.

 

[NickD_3CX]

Its about the reconnection with the Registrar Server. If the priority of the Registrar Server changes during a active call it send the timeout and cancel the call.

The Register of the SIP account is ok and work well.

This happened when updating to SP 3 Beta. On the stable Update 2 everything is fine.

Hi! I'd like to have a look myself, could you send my a PM with TeamViewer credentials for me to connect to your 3CX server?

 

[domk]

Hey, did you manage to figure out the problem?

For what its worth, I am experiencing the same issue since updating to Update 3. Calls from the Telekom Sip Trunk keep disconnecting after 10-30s. Calls over other Trunks work just fine.

Is there any way I can help with diagnosing the issue?

 

[NickD_3CX]

Hey, did you manage to figure out the problem?

For what its worth, I am experiencing the same issue since updating to Update 3. Calls from the Telekom Sip Trunk keep disconnecting after 10-30s. Calls over other Trunks work just fine.

Is there any way I can help with diagnosing the issue?

Can we do a quick TeamViewer session to check it?
If yes, send me a PM with the ID and password.

 

[domk]

If anyone is having the same issue: it seems to be related to 3cx being set to dynamic public IP. Changing it to static public ip alleviates the issue until a patch is available.

 

[mcom]

Can we do a quick TeamViewer session to check it?
If yes, send me a PM with the ID and password.

I use this 3CX in an Productive Environment. But i can install an 3cx via VMWARE and grant you access to the machine. I had an pcap dump but after seeing that it worked properly on the Update 2 i deleted it.

It seems to be a problem on the Update 3 itself.

 

[NickD_3CX]

I use this 3CX in an Productive Environment. But i can install an 3cx via VMWARE and grant you access to the machine. I had an pcap dump but after seeing that it worked properly on the Update 2 i deleted it.

It seems to be a problem on the Update 3 itself.

As this is a production environment, there are 2 choices:
a) You do what @domk did in the reply #9 , so set the 3CX to "Static" if you currently have it set to "Dynamic". In this case you need to change the setting in Settings --> Network. After this you need to restart the System Service and SIP Server once.
b) If it is the same case as domk, I have a patch that I can install for you, but this may take a couple of minutes to install.

Tell me what you would like to do.

 

[Thomas Woelfle]

I have the same problem with 2 customers with dynamic puplic IP. Do you already know when the update will be available? Or can we get the patch?

Thomas

 

[NickD_3CX]

I have the same problem with 2 customers with dynamic puplic IP. Do you already know when the update will be available? Or can we get the patch?

Thomas

I'll send you a PM in a minute.

 

[SKDamon]

I'm having the same issues: 3CX 18.0 Update 3 Branch 450, Dynamic public IP, Telekom CompanyFlex SIP-Trunk.

We've had 5-6 calls per day that failed with Reason: SIP;cause=404;text="Not Found (1:27)".

Please PM me if you need to debug or have a patch we can install @NickD_3CX !

 

[ChrisC_3CX]

@SKDamon I'll PM you about this shortly.

 

[ChrisC_3CX]

@SKDamon has also set to static IP and everything seems to be fine now.

 

[mcom]

I heard another Problem with other Sip Trunks being disconnected and register in a loop. Same after upgrading to Update 3. I think this must generally be patched soon. Workaround for us is no upgrade to Update 3. If so, then static IP Change. But this is not applicable to all customers.

 

[ChrisC_3CX]

I heard another Problem with other Sip Trunks being disconnected and register in a loop.

Could you please provide links to where this was mentioned? Just want to make sure that nothing is being misinterpreted and generally clarify on the situation where possible.

Also, do note that a few functionality wrinkles that popped up here and there will be ironed out soon enough.

 

[mcom]

I had it from other 3CX Customers and see it for example on e.g. Callcentric or VSENET Sip Trunk. But on this Calls works perfectly. Its only about temporarily disconnecting since the update.

On Static everything works fine

 

[ChrisC_3CX]

I see, well as mentioned, a patch will be out soon so this shouldn't be an issue for long.