Ticket #5862 (closed Bugs: invalid)

Opened 1 year ago

Last modified 7 months ago

Outband routes doesn't failover trunks on busy

Reported by: fiftyz Assigned to: tonyclewis
Priority: major Milestone: 2.11
Component: Core - Trunks/Routing Version: 2.10-branch
Keywords: macro-dialout-trunk, failover, outbound route Cc:
Confirmation: Unreviewed Distro:
Backend Engine: All Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description

When you set up multiple trunks on an outbound route I think the only logic that you setup multiple trunks is to failover them if one is unavailable (including busy). So i think the code in [macro-dialout-trunk]: 

[macro-dialout-trunk]
...
exten => s-BUSY,1,Noop(Dial failed due to trunk reporting BUSY - giving up)
exten => s-BUSY,n,Playtones(busy)
exten => s-BUSY,n,Busy(20)
...

should by: 

[macro-dialout-trunk]
...
exten => s-BUSY,1,MacroExit()
...

in order to let the route code to set congestion for the route not just one trunk.

Change History

06/01/12 09:54:28 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to invalid.
  • component changed from FreePBX Distro to Core - Trunks/Routing.

The failover only occurs if the TRUNK is congested. If the phone number you are trying to reach is BUSY then there is no point trying it with other trunks. If the carrier is returning a BUSY because they are "congested" then they are signaling incorrectly and should be returning a congested state which tells FreePBX to try the next trunk.

12/04/12 16:17:11 changed by torontob

You are taking into account only local calls. This is not the case with international calls. In fact it's very needed to jump to next trunk when there is no ANSWER - no matter what the response code is.

12/04/12 16:17:27 changed by torontob

*you are NOT*