User's Manual 308 Document #: LTRT-42060
Mediant 2600 E-SBC
Parameter Description
Web: Remote re-INVITE
CLI: sbc-rmt-re-invite-supp
[IpProfile_SBCRemoteReinvite
Support]
Defines whether the destination UA of the re-INVITE request
supports re-INVITE messages and if so, whether it supports re-
INVITE with or without SDP.
[0] Not Supported = re-INVITE is not supported and the device
does not forward re-INVITE requests. The device sends a SIP
response to the re-INVITE request, which can either be a
success or a failure, depending on whether the device can
bridge the media between the endpoints.
[1] Supported only with SDP = re-INVITE is supported, but only
with SDP. If the incoming re-INVITE arrives without SDP, the
device creates an SDP and adds it to the outgoing re-INVITE.
[2] Supported = (Default) re-INVITE is supported with or without
SDP.
Web: Remote Delayed Offer
Support
CLI: sbc-rmt-delayed-offer
[IpProfile_SBCRemoteDelayed
OfferSupport]
Defines whether the remote endpoint supports delayed offer (i.e.,
initial INVITEs without an SDP offer).
[0] Not Supported = Initial INVITE requests without SDP are not
supported.
[1] Supported = (Default) Initial INVITE requests without SDP
are supported.
Note: For this parameter to function, you need to configure a valid
Extension Coders Group ID for IP Profiles that do not support
delayed offer.
Web: Remote REFER Behavior
CLI: sbc-rmt-refer-behavior
[IpProfile_SBCRemoteReferBeh
avior]
Defines the device's handling of REFER requests for this SIP
entity.
[0] Regular = (Default) Refer-To header is unchanged and the
device forwards the REFER as is.
[1] Database URL = Changes the Refer-To header so that the
re-routed INVITE is sent through the SBC:
a. Before forwarding the REFER request, the device changes
the host part to the device's IP address and adds a special
prefix ("T~&R_") to the Contact user part.
b. The incoming INVITE is identified as a REFER-resultant
INVITE according to this special prefix.
c. The device replaces the host part in the Request-URI with
the host from the REFER contact. The special prefix
remains in the user part for regular classification,
manipulation, and routing. The special prefix can also be
used for specific routing rules for REFER-resultant INVITEs.
d. The special prefix is removed before the resultant INVITE is
sent to the destination.
[2] IP Group Name = Sets the host part in the REFER message
to the name defined for the IP Group (in the IP Group table).
[3] Handle Locally = Handles the incoming REFER request itself
without forwarding the REFER. The device generates a new
INVITE to the alternative destination according to the rules in
the IP-to-IP Routing table (the 'Call Trigger' field must be set to
REFER).
Note: The corresponding global parameter is SBCReferBehavior.