AudioCodes Mediant 800B User Manual page 418

Parameter
Remote Hold Format
remote-hold-Format
[IPProfile_SBCRemoteHoldFor
mat]
Remote Representation Mode
sbc-rmt-rprsntation
[IpProfile_SBCRemoteReprese
ntationMode]
Keep Incoming Via Headers
sbc-keep-via-headers
[IpProfile_SBCKeepVIAHeader
s]
User's Manual
Note: If the parameter is set to Yes, the device plays the tone only
if the 'SBC Remote Hold Format' parameter is set to transparent,
send-only, send only 0.0.0.0, or not supported.
Defines the format of the SDP in the re-INVITE for call hold that the
device sends to the held party.

[0] Transparent = (Default) Device forwards SDP as is.

[1] Send Only = Device sends SDP with 'a=sendonly'.

[2] Send Only Zero ip = Device sends SDP with 'a=sendonly'
and 'c=0.0.0.0'.

[3] Inactive = Device sends SDP with 'a=inactive'.

[4] Inactive Zero ip = Device sends SDP with 'a=inactive' and
'c=0.0.0.0'.

[5] Not Supported = Used when remote side cannot identify a
call-hold message. The device terminates the received call-hold
message (re-INVITE / UPDATE) and sends a 200 OK to the
initiator of the call hold. The device plays a held tone to the held
party if the 'SBC Play Held Tone' parameter is set to Yes.
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 Group or
SRD 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 = Device replaces the address in the
Contact header, received in incoming messages from the other
side, with its own address 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).
Enables interworking SIP Via headers between SIP entities. The
parameter defines the device's handling of Via headers for
messages sent to the SIP entity associated with the IP Profile.

[-1] According to Operation Mode = Depends on the setting of
the 'Operation Mode' parameter in the IP Group table or SRD
table:

B2BUA: Device operates as if the parameter is set to
Disable [0].

Call State-full Proxy: Device operates as if the parameter is
set to Enable [1].

[0] Disable = Device removes all Via headers received in the
418
Mediant 800B Gateway and E- SBC
Description
Document #: LTRT-10296