User's Manual 624 Document #: LTRT-42060
Mediant 2600 E-SBC
Parameter Description
Web: SBC Preferences Mode
[SBCPreferencesMode]
Determines the order of the Extension coders (coders added if
there are no common coders between SDP offered coders and
Allowed coders) and Allowed coders (configured in the Allowed
Coders Group table) in the outgoing SIP message (in the SDP).
[0] Doesn’t Include Extensions = (Default) Extension coders are
added at the end of the coder list.
[1] Include Extensions = Extension coders and Allowed coders
are arranged according to their order of appearance in the
Allowed Coders Group table.
Note: This parameter is applicable only if an Extension Coders
Group is assigned to the IP Profile (IP Profile table's parameter,
SBCExtensionCodersGroupID).
SBC RTCP Mode
CLI: sbc-rtcp-mode
[SBCRTCPMode]
Global parameter that defines the handling of RTCP packets. You
can also configure this functionality per specific calls, using IP
Profiles (IPProfile_SBCRTCPMode). For a detailed description of
this parameter and for configuring this functionality in the IP Profile
table, see ''Configuring IP Profiles'' on page 297.
Note: If this functionality is configured for a specific IP Profile, the
settings of this global parameter is ignored for calls associated with
the IP Profile.
Web: SBC Send Invite To All
Contacts
CLI: sbc-send-invite-to-all-
contacts
[SBCSendInviteToAllContacts
]
Enables call forking of INVITE message received with a Request-
URI of a specific contact registered in the device's database, to all
users under the same AOR as the contact.
[0] Disable (default) = Sends the INVITE only to the contact of
the received Request-URI.
[1] Enable
To configure call forking initiated by the device, see ''Initiating SIP
Call Forking'' on page 350.
Web: SBC Shared Line
Registration Mode
CLI: sbc-shared-line-reg-mode
[SBCSharedLineRegMode]
Enables the termination on the device of SIP REGISTER
messages from secondary lines pertaining to the Shared Line
feature.
[0] Disable = (Default) Device forwards the REGISTER
messages as is (i.e., not terminated on the device).
[1] Enable = REGISTER messages of secondary lines are
terminated on the device.
Note: The device always forwards REGISTER messages of the
primary line.
Web: SBC Forking Handling
Mode
CLI: sbc-forking-handling-mode
[SBCForkingHandlingMode]
Defines the handling of SIP 18x responses received due to call
forking of an INVITE.
[0] Latch On First = (Default) Only the first 18x is forwarded to
the INVITE-initiating UA. If SIP 18x with SDP is received, the
device opens a voice stream according to the received SDP and
disregards any subsequent 18x forking responses (with or
without SDP). If the first response is 180 without SDP, the
device sends it to the other side.
[1] Sequential = All 18x responses are forwarded, one at a time
(sequentially) to the INVITE-
initiating UA. If a 18x arrives with an
offer only, then only the first offer is forwarded to the INVITE-
initiating UA and subsequent 18x responses are discarded.
[SBCRemoveSIPSFromNonSec
uredTransport]
Defines the SIP headers for which the device replaces “sips:” with
“sip:” in the outgoing SIP-initiating dialog request (e.g., INVITE)
To Next Page
Loading...
