Solved Inbound routing problem with Multiple Trunks from Flowroute

[Shane Jensen]

We utilize two separate Flowroute accounts to provide 2 DIDs (19528959700 and 19524795780). Each trunk is set to go to a separate Digital Reception extension (801 and 810), however all calls are being routed to the extension 810 defined as the inbound destination for 19524795780.

05/18/2018 7:23:10 AM - [CM503001]: Call(C:23): Incoming call from Line:10000<<+1XXXXXX4592 to <sip:[email protected]:5060>
05/18/2018 7:23:10 AM - Leg L:23.1[Line:10000<<+1XXXXXX4592] has external party ID {+1XXXXXX4592}
05/18/2018 7:23:10 AM - IncomingCall: C:23 from <sip:[email protected]:5060> to <sip:[email protected]:5060>

Both accounts are set for IP authentication, however we have also tried account registration with no change in behavior. We have also tried to place a random number in the Authentication ID for each trunk as stated here: https://www.3cx.com/community/threa...re-than-one-ip-authenticated-sip-trunk.47452/ with no success.

We have an inbound route set for both accounts and have tried the following formats for DID matching:
19528959700
*19528959700
*9528959700
+19528959700
Currently the routes are using *9528959700 and *9524795780

We have also tried removing the Inbound Routing and let the Trunk handle the routing, again no change.

We contacted Flowroute with captures and logs and the confirm the signaling is correct as calls are being completed successfully.

We need two Trunks as billing is separate for each.

What are we missing?

 

[aberry]

Seems like things should be working - we use flowroute as our backup and a local generic as our primary and route DIDs from both with no issues. Seems like something must be messed up with the inbound rule though. You sure you have the correct instance of the trunk selected for each DID for inbound rules?

SIP Trunk settings should either work or not, so it seems that the only thing that could be causing problems are the inbound rules for the DIDs.

I do the wildcards for DIDs same as you also and haven't had any trouble, although I only use one instance of flowroute.

 

[Shane Jensen]

Quick update. Each Flowroute Trunk has 2 DID's 1 fax and 1 phone. For Trunk 9524795780 we can add the fax DID and set inbound rules for both the main line and the fax. The fax DID follows the Inbound rule however the Main DID follows the SIP Trunk route and ignores any inbound rules. The DID matching appears to work correctly as we use the same format for both numbers and the fax matches the inbound rule correctly.

This got me thinking that maybe it was just the first number listed in each trunk that was not being routed correctly so I created an inbound rule for a 2nd DID on Trunk 9528959700 hoping it would process through the Inbound rule, but it did not. The call went to the default route for Trunk 9524795780.

 

[Shane Jensen]

Follow up - Calls always arrive on "Line:10000"

05/18/2018 11:54:56 AM - [CM503001]: Call(C:42): Incoming call from Line:10000<<+1XXXXXX4592 to <sip:[email protected]:5060>

Does "line" relate to the Trunk?

 

[leejor]

10000 refers to the trunk group. This can be any number of concurrent calls depending on what you are paying for, and the trunk settings.

 

[Shane Jensen]

@leejor Would that trunk group number be provided by Flowroute or 3CX?

 

[cobaltit]

Any chance you have the routing on the flowroute side wrong?

 

[YiannisH_3CX]

Hello @Shane Jensen

Please note that Flowroute is supported for a single account on each PBX because the static Source identification settings that are required are the same for all accounts. The PBX matches the incoming calls using the source id settings. Since the settings match the first trunk all calls are routed to that trunk.
If the DID's are unique to each trunk you can try enabling the "Use both "Source Identification" rules and "Caller Number/Name" field mappings (Note: Disables catch all routing capability)" option under the Inbound parameters of both trunks and see if that works for you.
This way the PBX will try to match the call using the source ID settings and the DID number.




Note that the supported trunk type for Flowroute is Authentication based and not IP based so we have not really tested the IP based trunks.
https://www.3cx.com/partners/sip-trunks/usa/

 

[Shane Jensen]

@YiannisH_3CX Thank you, that appears to work!

I had tried account registration as well as IP authentication and results were the same.

Currently using IP authentication and checking "Source Identification" rules and "Caller Number/Name" field mappings (Note: Disables catch all routing capability)" works.

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the post with your solution. As i have mentioned this will only work if the trunks have unique DID numbers.