Call Forking-Based Ip-To-Ip Routing Rules - AudioCodes Mediant 1000B User Manual

User's Manual
The SBC also supports media synchronization for call forking. If the active UA is the first
one to send the final response (e.g., 200 OK) the call is established and all other final
responses are acknowledged and a BYE is sent if needed. If another UA sends the first
final response, then it is possible that the SDP answer that was forwarded to the INVITE-
initiating UA is not relevant, and media synchronization is needed between the two UAs.
Media synchronization is done by sending a re-INVITE request immediately after the call is
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.

28.10.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
530.
Version 6.8 513 Mediant 1000B Gateway & SBC
28. SBC Overview