CHAPTER 60 Configuration Parameters Reference
Mediant 4000 SBC | User's Manual
Parameter
Description
[EnableReasonHeade
r]
'Gateway Name'
configure voip >
sip-definition
settings > gw-
name
[SIPGatewayName]
Defines a name for the device (e.g., device123.com). This name is
used as the host part of the SIP URI in the From header. If not
specified, the device's IP address is used instead (default).
Note:
■
Ensure that the parameter value is the one with which the Proxy
has been configured with to identify the device.
■
The parameter can also be configured for an IP Group (in the IP
Groups table).
configure voip >
sip-definition
settings > zero-
sdp-behavior
[ZeroSDPHandling]
Determines the device's response to an incoming SDP that includes
an IP address of 0.0.0.0 in the SDP's Connection Information field
(i.e., "c=IN IP4 0.0.0.0").
■
[0] = (Default) Sets the IP address of the outgoing SDP's c= field
to 0.0.0.0.
■
[1] = Sets the IP address of the outgoing SDP c= field to the IP
address of the device. If the incoming SDP doesn’t contain the
"a=inactive" line, the returned SDP contains the "a=recvonly"
line.
'Delayed Offer'
configure voip >
sip-definition
settings >
delayed-offer
[EnableDelayedOffer]
Determines whether the device sends the initial INVITE message
with or without an SDP. Sending the first INVITE without SDP is
typically done by clients for obtaining the far-end's full list of
capabilities before sending their own offer. (An alternative method for
obtaining the list of supported capabilities is by using SIP
OPTIONS, which is not supported by every SIP agent.)
■
[0]
Disable
= (Default) The device sends the initial INVITE
message with an SDP.
■
[1]
Enable
= The device sends the initial INVITE message
without an SDP.
[SIPDigestAuthorizati
onURIMode]
Defines whether the device includes or excludes URI parameters for
the Digest URI in the SIP Proxy-Authorization or Authorization
headers of the request that the device sends in reply to a received
SIP 401 (Unauthorized) or 407 (Proxy Authentication Required)
response. Below shows an example of a request with an
Authorization header containing a Digest URI (shown in bold):
Authorization: Digest username="alice at
AudioCodes.com",realm="AudioCodes.com",nonce="",
response="",
uri="sip:AudioCodes.com"
■
[0] = (Default) The device sends the request without a Digest
URI.
■
[1] = The device sends the request with a Digest URI, which is
set to the same value as the URI in the original Request-URI.
- 939 -
Summary of Contents for Mediant 4000 SBC
Page 1: ...User s Manual AudioCodes Series of Session Border Controllers SBC Mediant 4000 SBC Version 7 2...
Page 40: ...Part I Getting Started with Initial Connectivity...
Page 48: ...Part II Management Tools...
Page 113: ...Part III General System Settings...
Page 118: ...Part IV General VoIP Configuration...
Page 525: ...Part V Session Border Controller Application...
Page 654: ...Part VI Cloud Resilience Package...
Page 663: ...Part VII High Availability System...
Page 685: ...Part VIII Maintenance...
Page 759: ...Part IX Status Performance Monitoring and Reporting...
Page 844: ...Part X Diagnostics...
Page 888: ...Part XI Appendix...