Version 7.2 995 Mediant 1000B Gateway & E-SBC
User's Manual 62. Configuration Parameters Reference
Parameter Description
[SIPDestinationPort]
Use user=phone in SIP URL
configure voip > sip-
definition settings >
user=phone-in-url
[IsUserPhone]
Determines whether the 'user=phone' string is added to the SIP URI
and SIP To header.
ï‚§ [0] No = 'user=phone' string is not added.
ï‚§ [1] Yes = (Default) 'user=phone' string is part of the SIP URI and
SIP To header.
Use user=phone in From
Header
configure voip > sip-
definition settings > phone-
in-from-hdr
[IsUserPhoneInFrom]
Determines whether the 'user=phone' string is added to the From and
Contact SIP headers.
ï‚§ [0] No = (Default) Doesn't add 'user=phone' string.
ï‚§ [1] Yes = 'user=phone' string is part of the From and Contact
headers.
Use Tel URI for Asserted
Identity
configure voip > sip-
definition settings > uri-for-
assert-id
[UseTelURIForAssertedID]
Determines the format of the URI in the P-Asserted-Identity and P-
Preferred-Identity headers.
ï‚§ [0] Disable = (Default) 'sip:'
ï‚§ [1] Enable = 'tel:'
Tel to IP No Answer
Timeout
configure voip > gateway
advanced > tel2ip-no-ans-
timeout
[IPAlertTimeout]
Defines the time (in seconds) that the device waits for a 200 OK
response from the called party (IP side) after sending an INVITE
message, for Tel-to-IP calls. If the timer expires, the call is released.
The valid range is 0 to 3600. The default is 180.
Enable Remote Party ID
configure voip > sip-
definition settings > remote-
party-id
[EnableRPIheader]
Enables Remote-Party-Identity headers for calling and called numbers
for Tel-to-IP calls.
ï‚§ [0] Disable (default).
ï‚§ [1] Enable = Remote-Party-Identity headers are generated in SIP
INVITE messages for both called and calling numbers.
Enable History-Info Header
configure voip > sip-
definition settings > hist-info-
hdr
[EnableHistoryInfo]
Enables usage of the SIP History-Info header.
ï‚§ [0] Disable (default)
ï‚§ [1] Enable
User Agent Client (UAC) Behavior:
ï‚§ Initial request: The History-Info header is equal to the Request-URI.
If a PSTN Redirect number is received, it is added as an additional
History-Info header with an appropriate reason.
ï‚§ Upon receiving the final failure response, the device copies the
History-Info as is, adds the reason of the failure response
entry, and concatenates a new destination to it (if an additional
request is sent). The order of the reasons is as follows:
a. Q.850 Reason
b. SIP Reason
c. SIP Response code
ï‚§ Upon receiving the final response (success or failure), the device
searches for a Redirect reason in the History-Info (i.e., 3xx/4xx SIP
reason). If found, it is passed to ISDN according to the following