Flowroute Call Formatting issue

[healthy]

A few weeks ago, I had an issue where all of our calls are routed to the main number if the SIP trunk DIDs are in +1... format. If I re-populate as 3CX Requires, my calls no longer route to the proper DIDs.

I reached out to Flowroute support and they tell me they cannot format the calls any differently, and that I must reformat the inbound numbers to prepend the + in front of the number. I don't see anywhere to do this in my system.

 

[OlegR_3CX]

Hi there.
Can you show us an example of the working scenarios and the one that does not work?
Also, if you run the capture, do you see the numbers entered in the exact same way as the provider sends them to you?

 

[healthy]

Sure, I just ran the call test. Outside phone number to a DID which fowards to my extension:



Made with our number without the leading + - Call routes properly to the extension (111 in this case)



4/23/2024 5:34:28 PM - NAT/ALG check:L:133.1[Line:10000<<OUTSIDENUMBER] RESPONSE 200 on 'INVITE' - some of SIP/SDP headers contain inconsistent information or modified by intermediate hop

SIP proxy detected:

Record-Route:<sip:35.173.62.45:5060;lr>

Record-Route:<sip:34.226.36.35:5060;lr;did=9e21.2762>

Media session IP ('c=' attribute) is not equal to the SIP packet source(IPort):

Media session IP: 207.223.67.137

Received from: OUR_PBX_IP



04/23/2024 5:34:27 PM - NAT/ALG check:L:133.1[Line:10000<<OUTSIDENUMBER] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop

SIP proxy detected:

Via:SIP/2.0/UDP 34.226.36.35:5060;branch=z9hG4bKa3bb.ee898a83c6b20b270dfa44e7402e17cd.0

Via:SIP/2.0/UDP 54.71.6.127:5060;branch=z9hG4bKa3bb.e4e692497cfa346c0a5b910215218d3c.0

Via:SIP/2.0/UDP 35.173.62.45:5060;branch=z9hG4bKa3bb.eada3407208189c098e6f9338e68488f.0

Via:SIP/2.0/UDP 207.223.78.224:5060;branch=z9hG4bK00B0b2f430501936877

Media session IP ('c=' attribute) is not equal to the SIP packet source(IPort):

Media session IP: 207.223.67.137

Received from: 34.226.36.35



04/23/2024 5:34:17 PM - [CM503003]: Call(C:132): Call to <sip:111@OUR_PBX_INTERNAL_IP:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.60.125:5060

04/23/2024 5:34:14 PM - [CM503003]: Call(C:132): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483





Re-tested with + in front of the number inside of the SIP Trunk



04/23/2024 5:39:13 PM - [CM100002]: *!* Exception detected: unknown *!*

04/23/2024 5:35:26 PM - [CM503003]: Call(C:134): Call to <sip:111@OUR_PBX_INTERNAL_IP:0> has failed; Cause: 487 Request Terminated/INVITE from MY_DESKPHONE_IP:5060

04/23/2024 5:35:25 PM - [CM503003]: Call(C:134): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

04/23/2024 5:35:22 PM - NAT/ALG check:L:134.1[Line:10000<<OUTSIDENUMBER] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop

SIP proxy detected:

Via:SIP/2.0/UDP 34.226.36.35:5060;branch=z9hG4bKd571.375ecb8000d93f9c9b575884ef4c9f9c.0

Via:SIP/2.0/UDP 54.71.6.127:5060;branch=z9hG4bKd571.81cbf8d079e58025aeb94b8b2f4c47da.1

Via:SIP/2.0/UDP 34.211.68.10:5060;branch=z9hG4bKd571.dc30765385564b5a558df34b0cb7123b.0

Via:SIP/2.0/UDP 207.223.78.224:5060;branch=z9hG4bK0cBc54de552cb871f84

Media session IP ('c=' attribute) is not equal to the SIP packet source(IPort):

Media session IP: 207.223.67.137

Received from: 34.226.36.35



04/23/2024 5:34:28 PM - NAT/ALG check:L:133.1[Line:10000<<OUTSIDENUMBER] RESPONSE 200 on 'INVITE' - some of SIP/SDP headers contain inconsistent information or modified by intermediate hop

SIP proxy detected:

Record-Route:<sip:35.173.62.45:5060;lr>

Record-Route:<sip:34.226.36.35:5060;lr;did=9e21.2762>

Media session IP ('c=' attribute) is not equal to the SIP packet source(IPort):

Media session IP: 207.223.67.137

Received from: OUR_PBX_IP



04/23/2024 5:34:27 PM - NAT/ALG check:L:133.1[Line:10000<<OUTSIDENUMBER] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop

SIP proxy detected:

Via:SIP/2.0/UDP 34.226.36.35:5060;branch=z9hG4bKa3bb.ee898a83c6b20b270dfa44e7402e17cd.0

Via:SIP/2.0/UDP 54.71.6.127:5060;branch=z9hG4bKa3bb.e4e692497cfa346c0a5b910215218d3c.0

Via:SIP/2.0/UDP 35.173.62.45:5060;branch=z9hG4bKa3bb.eada3407208189c098e6f9338e68488f.0

Via:SIP/2.0/UDP 207.223.78.224:5060;branch=z9hG4bK00B0b2f430501936877

Media session IP ('c=' attribute) is not equal to the SIP packet source(IPort):

Media session IP: 207.223.67.137

Received from: 34.226.36.35

 

[OlegR_3CX]

If possible open the ticket with us so we can check the logs and take it from there