AudioCodes Mediant 4000 SBC User Manual page 450

Session border controllers
Hide thumbs Also See for Mediant 4000 SBC:
Table of Contents

Advertisement

CHAPTER 19    Coders and Profiles
Parameter
'Remote re-INVITE'
sbc-rmt-re-invite-supp
[IpProfile_
SBCRemoteReinviteSupport]
'Remote Delayed Offer Support'
sbc-rmt-delayed-offer
[IpProfile_
SBCRemoteDelayedOfferSupp
ort]
'Remote Representation Mode'
sbc-rmt-rprsntation
[IpProfile_
SBCRemoteRepresentationMo
de]
Description
[1] Supported Only After Connect = UPDATE
message is supported only after the call is connected.
[2] Supported = (Default) UPDATE message is
supported during call setup and after call
establishment.
[3] According Remote Allow = For refreshing the
timer of currently active SIP sessions, the device
sends session refreshes using SIP UPDATE
messages only if the SIP Allow header in the last SIP
message received from the user contains the value
"UPDATE". If the Allow header does not contain the
"UPDATE" value (or if the parameter is not configured
to this option), the device uses INVITE messages for
session refreshes.
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.
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 the parameter to function, you need to assign
extension coders to the IP Profile of the SIP entity that
does not support delayed offer (using the IpProfile_
SBCExtensionCodersGroupName parameter).
Enables interworking SIP in-dialog, Contact and Record-
Route headers between SIP entities. The parameter
defines the device's handling of in-dialog, Contact and
Record-Route headers for messages sent to the SIP entity
associated with the IP Profile.
[-1] According to Operation Mode = (Default)
Depends on the setting of the 'Operation Mode'
parameter in the IP Groups or SRDs table:
- 417 -
Mediant 4000 SBC | User's Manual

Advertisement

Table of Contents
loading

Table of Contents