Route Advance

For Termination Vendor and Origination Customer trunk groups, The route advance regular expression determines how to process failed call attempts (i.e. when the remote device responds to a SIP Invite with a 4XX-6XX response code).

If the response code is in the route advance regular expression then Peeredge Orchestrator will:

• For termination vendor trunks groups

        When the Orchestrator receives a failure response code, the call will be routed to the next available vendor configured in the termination route plan.  If no additional trunk groups are available, the Orchestrator will reply to the SIP Invite transaction received on the termination customer trunk group with an appropriate failure response code.

The Peeredge Orchestrator will never route advance to additional trunks in the same vendor trunk group.

The Peeredge Orchestrator will not route advance when receiving the following SIP Response Codes from the vendor (even if they are in the regular expression rule):  404, 428, 436, 437, 438, 484, 486, 504, 607, 608.

• For origination customer trunk groups, the Orchestrator will route advance to the next available trunk in the trunk group when receiving 4.. failure response codes. When 5..|6.. response codes are received or no additional trunks are available in the trunk group, the On Failure forwarding action for the specific DNIS will taken (if configured). When no additional trunks or number specific failover actions are available, the Orchestrator will reply to the SIP Invite transaction received on the origination vendor trunk group with the failure response code provided by the customer's remote device (SBC/IP PBX). 

If there is no response (timeout) to the SIP Invite then the following will occur:

If trunk monitoring is not enabled and the B Timer is not configured on the currently selected trunk group, then the Peeredge Orchestrator will continue to resend the SIP Invite at regular intervals as defined in RFC 3261 until Timer B (not the same timer as B Timer) expires (32 seconds).  

If trunk monitoring is enabled, then most likely the remote device as not responded to SIP Option messages and the trunk has been logically downed and no SIP Invites would be sent to this trunk.

If the B Timer is configured and it expires due to the lack of a provisional response, then the Orchestrator will act as if a failure response that matches the route advance regular expression had been provided.

Note: For enterprise customer the Route advance logic for inbound connections is used.  If all available trunks have been tried, then any configured failover action configured for the specific DNIS will be taken.