Call Forking-Based Ip-To-Ip Routing Rules; Alternative Routing On Detection Of Failed Sip Response - AudioCodes Mediant 500 E-SBC User Manual

established. The re-INVITE is sent without an offer to the INVITE-initiating UA. This causes
the UA to send an offer which is forwarded to the UA that confirmed the call. The media
synchronization process is enabled by the EnableSBCMediaSync parameter.

27.9.3 Call Forking-based IP-to-IP Routing Rules

You can configure call forking routing rules in the IP-to-IP Routing table. This is done by
configuring multiple routing rules under a forking group. These rules send an incoming IP
call to multiple destinations of any type (e.g., IP Group or IP address). The device forks the
call by sending simultaneous INVITE messages to all the specified destinations. It handles
the multiple SIP dialogs until one of the calls is answered and then terminates the other
SIP dialogs. For more information, see ''Configuring SBC IP-to-IP Routing Rules'' on page
487.
27.10 Alternative Routing on Detection of Failed SIP
Response
The device can detect failure of a sent SIP response (e.g., TCP timeout, and UDP ICMP).
In such a scenario, the device re-sends the response to an alternative destination. This
support is in addition to alternative routing if the device detects failed SIP requests.
For example, assume the device sends a SIP 200 OK in response to a received INVITE
request. If the device does not receive a SIP ACK in response to this, it sends a new 200
OK to the next alternative destination. This new destination can be the next given IP
address resolved from a DNS from the Contact or Record-Route header in the request
related to the response.
User's Manual 470
Mediant 500 E-SBC
Document #: LTRT-10437