User's Manual
630
Document #: LTRT-10375
Mediant 500 MSBR
For facilitating debugging procedures, some administrators require that the value in
the Call-ID header remains unchanged between the inbound and outbound SBC legs.
As B2BUA changes the Call-ID header, such debugging requirements would fail.
The operating mode can be configured per the following configuration entities:
SRDs in the SRDs table (see Configuring SRDs on page 315)
IP Groups in the IP Groups table (see Configuring IP Groups on page 333)
If the operation mode is configured in both tables, the operation mode of the IP Group is
applied. Once configured, the device uses default settings in the IP Profiles table for
handling the SIP headers, as mentioned previously. However, you can change the default
settings to enable partial transparency.
Note:
•
The To-header tag remains the same for inbound and outbound legs of the dialog,
regardless of operation mode.
•
If the Operation Mode of the SRD\IP Group of one leg of the dialog is set to 'Call
Stateful Proxy', the device also operates in this mode on the other leg with regards
to the dialog identifiers (Call-ID header, tags, CSeq header).
•
It is recommended to implement the B2BUA mode, unless one of the reasons
mentioned previously is required. B2BUA supports all the device's feature-rich
offerings, while Stateful Proxy may offer only limited support. The following
features are not supported when in Stateful Proxy mode:
√
Alternative routing
√
Call forking
√
Terminating REFER/3xx
•
If Stateful Proxy mode is enabled and any one of the unsupported features is
enabled, the device disables the Stateful Proxy mode and operates in B2BUA
mode.
•
You can configure the device to operate in both B2BUA and Stateful Proxy modes
for the same users. This is typically implemented when users need to
communicate with different SIP entities (IP Groups). For example, B2BUA mode
for calls destined to a SIP Trunk and Stateful Proxy mode for calls destined to an
IP PBX. The configuration is done using IP Groups and SRDs.
•
If Stateful Proxy mode is used only due to the debugging benefits, it is
recommended to configure the device to only forward the Call-ID header
unchanged
Summary of Contents for Mediant 500 MSBR
Page 2: ......
Page 33: ...Part I Getting Started with Initial Connectivity ...
Page 34: ......
Page 36: ...User s Manual 36 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 40: ...User s Manual 40 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 45: ...Part II Management Tools ...
Page 46: ......
Page 48: ...User s Manual 48 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 115: ...Part III General System Settings ...
Page 116: ......
Page 132: ...User s Manual 132 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 137: ...Part IV General VoIP Configuration ...
Page 138: ......
Page 290: ...User s Manual 290 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 306: ...User s Manual 306 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 380: ...User s Manual 380 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 454: ...User s Manual 454 Document LTRT 10375 Mediant 500 MSBR This page is intentionallty left blank ...
Page 455: ...Part V Gateway Application ...
Page 456: ......
Page 460: ...User s Manual 460 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 484: ...User s Manual 484 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 494: ...User s Manual 494 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 625: ...Part VI Session Border Controller Application ...
Page 626: ......
Page 654: ...User s Manual 654 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 656: ...User s Manual 656 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 741: ...Part VII Cloud Resilience Package ...
Page 742: ......
Page 751: ...Part VIII Data Router Configuration ...
Page 752: ......
Page 753: ......
Page 754: ......
Page 756: ...User s Manual 756 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 757: ...Part IX Maintenance ...
Page 758: ......
Page 834: ...User s Manual 834 Document LTRT 10375 Mediant 500 MSBR This page is intetnionaly left blank ...
Page 837: ...Part X Status Performance Monitoring and Reporting ...
Page 838: ......
Page 848: ...User s Manual 848 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 852: ...User s Manual 852 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 854: ...User s Manual 854 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 878: ...User s Manual 878 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 880: ...User s Manual 880 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 926: ...User s Manual 926 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 927: ...Part XI Diagnostics ...
Page 928: ......
Page 950: ...User s Manual 950 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 954: ...User s Manual 954 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 956: ...User s Manual 956 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 958: ...User s Manual 958 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 974: ...User s Manual 974 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 976: ...User s Manual 976 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...
Page 977: ...Part XII Appendix ...
Page 978: ......
Page 982: ...User s Manual 982 Document LTRT 10375 Mediant 500 MSBR This page is intentionally left blank ...