3CX Outbound Calls With Voiceflex Trunks Disconnect

[Matt_AIT]

We have noticed this morning that all of our clients who use Voiceflex as a trunk provider are having issues calling out. The call disconnects after 10-15 seconds. I have spoken to Voiceflex who are aware of an issue but have said it is only happening with 3CX. Apparently, they are not receiving ACK after their 200ok.

Thought I would raise it here in case anyone else is experiencing this issue.

 

[NickD_3CX]

As it's happening to all calls, it should be easy enough to get a Packet Capture of a dropped call.
If you arelady have one, in the "Contact" header of the 200 OK, what IP is present there?
Is that where the ACK is being sent to?

If you have a packet capture of such a call, you could upload it to a file sharing service of your choice and send me a download link in a PM for me to have a look too.

 

[OITMGR_Andy]

I'm trying to setup a Voiceflex SIP on hosted 3CX instance. We can receive calls fine but cannot make outgoing calls at all (just get busy tone - set everything up per 3CX guide but no joy). Agent at Voiceflex has stated that 3CX is taking longer than usual to respond to the 401 Authorisation requests from their system as of yesterday and they are apparently in talks with them about it.

 

[Matt_AIT]

I'm trying to setup a Voiceflex SIP on hosted 3CX instance. We can receive calls fine but cannot make outgoing calls at all (just get busy tone - set everything up per 3CX guide but no joy). Agent at Voiceflex has stated that 3CX is taking longer than usual to respond to the 401 Authorisation requests from their system as of yesterday and they are apparently in talks with them about it.

I have been told the same thing. Voiceflex have been able to resolve our issues by manually increasing the time out, they should be able to do the same for you.

 

[NickD_3CX]

I'm trying to setup a Voiceflex SIP on hosted 3CX instance. We can receive calls fine but cannot make outgoing calls at all (just get busy tone - set everything up per 3CX guide but no joy). Agent at Voiceflex has stated that 3CX is taking longer than usual to respond to the 401 Authorisation requests from their system as of yesterday and they are apparently in talks with them about it.

We are currently working with Voiceflex to see what exactly is happening.
As @Matt_Alcom_IT said, this seems to have occurred after a small change on the side of Voiceflex. Asking them to revert it should solve the problem for you.

I'll try and update the thread once we have more information, although I have the impression that they have reverted on all their platform for now.

 

[NickD_3CX]

Just a question, your 3CX systems that were affected, do they happen to be Self-Hosted somewhere? And if yes, is that somewhere Azure?

We have been going through things with Voiceflex, and although there is an improvement that can be made on the Voiceflex side to mitigate this, we have a feeling that the 'very very slight delay' that caused this is being introduced by the network, possibly of a specific Hosting Provider.

 

[Matt_AIT]

Just a question, your 3CX systems that were affected, do they happen to be Self-Hosted somewhere? And if yes, is that somewhere Azure?

We have been going through things with Voiceflex, and although there is an improvement that can be made on the Voiceflex side to mitigate this, we have a feeling that the 'very very slight delay' that caused this is being introduced by the network, possibly of a specific Hosting Provider.

All are hosted on Azure.

 

[NickD_3CX]

Thanks!
I suspected as much but wanted to double-check.
@OITMGR_Andy is your 3CX also on Azure?

I have given this feedback to Voiceflex so they can act accordingly now that we know most likely where the changes is that has caused the issue.