Flowroute invites

[easttek]

I have a long-existing V18 3cx system self-hosted on a Debian machine onsite. Very intermittently maybe 1 out of 20 invites are not being responded to by the server and (after 6 attempts from 2 different flowroute IPs) they are getting sent to a failover external pots line I have set up for the event of an internet outage. I have not had much luck replicating the issue due to being so intermittent but I can confirm the system and internet connection are online when this is happening. After going back and forth with flowroute I suspect this has to do with an invite formatting issue, after some research possibly a + being added to the number format in the invite but this has not been confirmed. Any thoughts?

 

[YiannisH_3CX]

Hello @easttek

When the issue occurs do you see the call hitting the PBX? You can check the activity log for this but you will need to enable Verbose logging. This will tell you if the call is indeed being rejected by 3CX or not.
Also why is 1 out of 20 Invites different? The called number format sent by Flowroute should always be the same.

Verify that you are using the default Flowroute template with the default values set. You can set a "dummy" Flowroute and compare settings.

 

[AWS2P]

Hi ,
I don't know if what I encountered last few days is the same kind of problem, I was in call with 3CX commercial representative and got call dropped at 19 minutes each time.
I asked details to my trunk provider (Dstny) and they said it was re invite not answered from my side pbx. This problem is coming randomly , not all the calls are dropped when they are longer than 19 minutes.

 

[YiannisH_3CX]

I don't know if what I encountered last few days is the same kind of problem, I was in call with 3CX commercial representative and got call dropped at 19 minutes each time.
I asked details to my trunk provider (Dstny) and they said it was re invite not answered from my side pbx. This problem is coming randomly , not all the calls are dropped when they are longer than 19 minutes.

I don't think the 2 issues are related but if you run a tshark on the server so we can catch a call dropping in the act that would help us troubleshoot the issue and see if the re-invites are actually hitting the PBX or not.

 

[easttek]

Hello @easttek

When the issue occurs do you see the call hitting the PBX? You can check the activity log for this but you will need to enable Verbose logging. This will tell you if the call is indeed being rejected by 3CX or not.
Also why is 1 out of 20 Invites different? The called number format sent by Flowroute should always be the same.

Verify that you are using the default Flowroute template with the default values set. You can set a "dummy" Flowroute and compare settings.

Yes flowroute default template, calls not hitting PBX at all. PBX just ignores them completely.
You are correct, it was not the + being added as every invite is the same.

It seems to be something going on with the route, currently back and forth with flowroute about this but it seems when using the route provided by the PBX's sip registration to their server the calls come in fine, whenever the route is using the Hostname they are not (flowroute recommends adding a host route to all DIDs). When or how flowroute decides which route to take is beyond me so I am waiting to hear back. I admittedly did not specify the sip signaling port 5060 in their host configuration page although it should default to 5060, I have since added :5060 after my FQDN in flowroute's host config in an attempt to mitigate the problem.

UPDATE: Invites are not being forwarded to the PBX by 2 separate servers at their provider at Bandwidth inc.

 

[easttek]

UPDATE: So after much back and forth with flowroute I am back at square one. Some invites are just not hitting the pbx, I have with absolute certainty the server is not going offline. Any Ideas?