Version 6.6
433
Mediant 3000
User's Manual
28. SBC Overview
28.10.2 SIP Forking Initiated by SIP Proxy Server
The device can handle SIP forking responses received from a proxy server in response to
an INVITE forwarded by the device from a UA. In other words, received responses with a
different SIP To header 'tag' parameter for the request forwarded by the device. This
occurs in scenarios, for example, where a proxy server forks the INVITE request to several
UAs, and therefore, the SBC device may receive several replies for a single request.
Forked SIP responses may result in a single SDP offer with two or more SDP answers
during call setup. The SBC handles this scenario by "hiding" the forked responses from the
INVITE-initiating UA. This is achieved by marking the UA that responded first to the INVITE
as the active UA, and only requests/responses from that UA are subsequently forwarded.
All other requests/responses from other UAs are handled by the SBC (SDP offers from
these users are answered with an 'inactive' media).
The SBC supports two forking modes, configured by the SBCForkingHandlingMode
parameter:
Latch On First - only the first received 18x response is forwarded to the INVITE
initiating UA, and disregards any subsequently received 18x forking responses (with or
without SDP).
Sequential - all 18x responses are forwarded to the INVITE initiating UA, one at a time
in a sequential manner. If 18x arrives with an offer only, only the first offer is forwarded
to the INVITE initiating UA.
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.
Содержание Mediant 3000
Страница 1: ...User s Manual Version 6 6 Enterprise Session Border Controller VoIP Digital Media Gateway Mediant 3000...
Страница 2: ......
Страница 21: ...Version 6 6 21 Mediant 3000 User s Manual 1 Overview Figure 1 2 Mediant 3000 TP 6310 Functional Block Diagram...
Страница 22: ...User s Manual 22 Document LTRT 89729 Mediant 3000 Figure 1 3 Mediant 3000 TP 8410 Functional Block Diagram...
Страница 26: ...User s Manual 26 Document LTRT 89729 Mediant 3000 Reader s Note...
Страница 27: ...Part I Getting Started with Initial Connectivity...
Страница 28: ......
Страница 40: ...User s Manual 40 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 41: ...Part II Management Tools...
Страница 42: ......
Страница 44: ...User s Manual 44 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 80: ...User s Manual 80 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 98: ...User s Manual 98 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 103: ...Part III General System Settings...
Страница 104: ......
Страница 113: ...Part IV General VoIP Configuration...
Страница 114: ......
Страница 144: ...User s Manual 144 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 164: ...User s Manual 164 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 222: ...User s Manual 222 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 224: ...User s Manual 224 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 275: ...Part V Gateway and IP to IP Application...
Страница 276: ......
Страница 278: ...User s Manual 278 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 399: ...Part VI Session Border Controller Application...
Страница 400: ......
Страница 402: ...User s Manual 402 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 464: ...User s Manual 464 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 465: ...Part VII Stand Alone Survivability Application...
Страница 466: ......
Страница 474: ...User s Manual 474 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 494: ...User s Manual 494 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 497: ...Part VIII IP Media Capabilities...
Страница 498: ......
Страница 501: ...Part IX High Availability System...
Страница 502: ......
Страница 515: ...Part X Maintenance...
Страница 516: ......
Страница 522: ...User s Manual 522 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 524: ...User s Manual 524 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 552: ...User s Manual 552 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 562: ...User s Manual 562 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 565: ...Part XI Status Performance Monitoring and Reporting...
Страница 566: ......
Страница 578: ...User s Manual 578 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 609: ...Part XII Diagnostics...
Страница 610: ......
Страница 624: ...User s Manual 624 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 626: ...User s Manual 626 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 638: ...User s Manual 638 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 639: ...Part XIII Appendix...
Страница 640: ......
Страница 864: ...User s Manual 864 Document LTRT 89729 Mediant 3000 Reader s Notes...
Страница 871: ...Version 6 6 871 Mediant 3000 User s Manual 55 Selected Technical Specifications Reader s Notes...
Страница 872: ...User s Manual Ver 6 6 www audiocodes com...