AudioCodes Mediant 4000 SBC, User Manual

Page: 969 / 1037

CHAPTER 60 Configuration Parameters Reference
Mediant 4000 SBC | User's Manual
Parameter Description
Even though some SIP devices don’t follow this behavior and don’t
increment the origin value even in scenarios where they want to re-
negotiate, the device can assume that the remote party operates
according to RFC 3264, and in cases where the origin field is not
incremented, the device does not re-negotiate SDP capabilities.
■ [0] Disable = (Default) The device negotiates any new SDP re-
offer, regardless of the origin field.
■ [1] Enable = The device negotiates only an SDP re-offer with an
incremented origin field.
'Subject'
configure voip >
sip-definition
settings > usr-
def-subject
[SIPSubject]
Defines the Subject header value in outgoing INVITE messages. If
not specified, the Subject header isn't included (default).
The maximum length is up to 50 characters.
'Multiple Packetization
Time Format'
configure voip >
sip-definition
settings > mult-
ptime-format
[MultiPtimeFormat]
Determines whether the 'mptime' attribute is included in the outgoing
SDP.
■ [0] None = (Default) Disabled.
■ [1] PacketCable = Includes the 'mptime' attribute in the outgoing
SDP - PacketCable-defined format.
The mptime' attribute enables the device to define a separate
packetization period for each negotiated coder in the SDP. The
'mptime' attribute is only included if the parameter is enabled even if
the remote side includes it in the SDP offer. Upon receipt, each
coder receives its 'ptime' value in the following precedence: from
'mptime' attribute, from 'ptime' attribute, and then from default value.
configure voip >
sip-definition
settings >
enable-ptime
[EnablePtime]
Determines whether the 'ptime' attribute is included in the SDP.
■ [0] = Remove the 'ptime' attribute from SDP.
■ [1] = (Default) Include the 'ptime' attribute in SDP.
'3xx Behavior'
3xx-behavior
[3xxBehavior]
Determines the device's behavior regarding call identifiers when a
3xx response is received for an outgoing INVITE request. The
device can use the same call identifiers (Call-ID, To, and From tags)
or change them in the new initiated INVITE.
■ [0] Forward = (Default) Use different call identifiers for a
redirected INVITE message.
■ [1] Redirect = Use the same call identifiers in the new INVITE
as the original call.
[RetryAfterMode] Defines the device’s behavior when it receives a SIP 503 (Service
Unavailable) containing a Retry-After header, in response to a SIP
message (e.g., REGISTER) sent to the proxy server.
- 936 -