AudioCodes Mediant 800 User Manual page 478

CHAPTER 19 Coders and Profiles
Parameter
'Remote Delayed Offer Support'
sbc-rmt-delayed-offer
[IpProfile_
SBCRemoteDelayedOfferSupp
ort]
'Remote Representation Mode'
sbc-rmt-rprsntation
[IpProfile_
SBCRemoteRepresentationMo
de]
Mediant 800 Gateway & E-SBC | User's Manual
Description
■ [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:
✔
B2BUA: Device operates as if the parameter is set
to Replace Contact [0].
✔
Call State-full Proxy: Device operates as if the
parameter is set to Add Routing Headers [1].
■ [0] Replace Contact = The URI host part in the
Contact header of the received message (from the
other side) is replaced with the device's address or with
the value of the 'SIP Group Name' parameter
(configured in the IP Groups table) in the outgoing
message sent to the SIP entity.
■ [1] Add Routing Headers = Device adds a Record-
Route header for itself to outgoing messages
(requests\responses) sent to the SIP entity in dialog-
setup transactions. The Contact header remains
unchanged.
■ [2] Transparent = Device doesn't change the Contact
header and doesn't add a Record-Route header for
itself. Instead, it relies on its' own inherent mechanism
to remain in the route of future requests in the dialog (for
example, relying on the way the endpoints are set up or
on TLS as the transport type).
- 438 -