Outbound rules calls switch to backup trunk

[kenzoo]

Hi,
we have two SIP trunks set up where one is primary and the other is backup. Our provider is 3CX supported provider and has set up the incoming calls so that if the primary link fails, the calls are routed to the secondary trunk. Incoming calls are working fine upon primary link failure - they are routed through the secondary trunk.

The problem is with the outgoing calls. When the primary link fails it takes 32s to switch to the backup trunk for outgoing calls.

The sip registration is IP based and in our test we switch off (Power off) the sip primary modem provider.
The 3CX is sending invite until it switch to the second trunk for all the calls it's take 32s to get a dial.

Do you please have any solution for this issue?

 

[YiannisH_3CX]

Hello @kenzoo

Please note that in SIP 32 seconds is the time that it takes for an entity to be dimmed inactive. If the server did send a error response then the PBX would switch to the second route immediately.
This is all defined in RFC3261.

 

[kenzoo]

Hi Yiannis
Thank you for your reply, but in the RFC I didn't see the case of no message,
You can understand if the primary provider goes down without sending message error the second route should goes fast then 32s. Otherwise how all others sip softswitch (providers) manage today therir routing. I think you should take this issue in consideration. If route 1 failed the second route should just work instantly. Maybe decrease this time or do other better mechanism.

 

[leejor]

If the first route were no longer registered, then it would be considered "not available" and calls would then flow to the second route immediately. The re-registration time could be shortened, to a minimum time, allowed by the provider.

 

[kenzoo]

Thank you Leejor for your input

 

[YiannisH_3CX]

Thank you for your reply, but in the RFC I didn't see the case of no message,
You can understand if the primary provider goes down without sending message error the second route should goes fast then 32s. Otherwise how all others sip softswitch (providers) manage today therir routing. I think you should take this issue in consideration. If route 1 failed the second route should just work instantly. Maybe decrease this time or do other better mechanism.

In the case of no answer Timer F will be used which equals to Timer 1 * 64. Since Timer 1 is half a second then this amounts to 32 seconds.
I would recommend posting this as a feature request on https://www.3cx.com/community/forums/3cx-ideas/ . All posts are reviewed by their corresponding Departments and, if feasible and voted for by other users as well, may be implemented in an upcoming service pack or update.

 

[kenzoo]

I did hope they fixe the issue