Nortel Networks Mediant TP-1610 SIP - Manual (Page 107)

Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000
Version 4.4 107 July 2005
Table 6-3: SIP Configuration Parameters (continues on pages 100 to 110)
ini File Field Name
Web Parameter Name
*
Valid Range and Description
XferPrefix
[Transfer Prefix] Defined string that is added, as a prefix, to the transferred called number, when
Refer/3xx message is received.
Note 1:
The number manipulation rules apply to the user part of the Refer-TO/Contact
URL before it is sent in the Invite message.
Note 2:
The xferprefix parameter can be used to apply different manipulation rules to
differentiate the transferred number from the original dialed number.
EnableHold
[Enable Hold] 0 = Hold service disabled (default)
1 = Hold service is enabled, held tone is played to holding party.
EnableForward
[Enable Call Forward] 0 = Disable call forward (default)
1 = Enable call forward service.
The Mediant 2000 doesn't initiate call forward, it can only respond to call forward
requests.
UseSIPURIForDiversionHe
ader Sets the URI format in the Diversion header.
0 = “tel:” (default).
1 = “sip:”.
EnableCallWaiting
[Enable Call Waiting]
0 = Disabled (default)
1 = Enabled
If enabled, when the gateway initiates a Tel to IP call to a destination that is busy, it
plays a Call Waiting Ringback tone to the originator of the call.
Note 1:
The gateway’s Call Progress Tones file must include a Call Waiting Ringback
tone.
Note 2:
The EnableHold parameter must be enabled on the called side.
RxDTMFOption
[Declare RFC 2833 in SDP]
Defines the supported Receive DTMF negotiation method.
0 = Don’t declare RFC 2833 Telephony-event parameter in SDP
1 = n/a
2 = n/a
3 = Declare RFC 2833 “Telephony-event” parameter in SDP (default)
The gateway is designed to always be receptive to RFC 2833 DTMF relay packets.
Therefore, it is always correct to include the “Telephony-event” parameter as a default
in the SDP. However some gateways use the absence of the “telephony-event” from
the SDP to decide to send DTMF digits inband using G.711 coder, if this is the case
you can set “RxDTMFOption=0”.
TxDTMFOption
[DTMF RFC2833
Negotiation]
0 = No negotiation, DTMF digit is sent according to the “DTMFTransportType”
parameter.
4 = Enable RFC 2833 payload type (PT) negotiation (default).
Note 1:
This parameter is applicable only if “IsDTMFUsed=0” (out-of-band DTMF is not
used)
Note 2:
If enabled, the gateway:
• Negotiates RFC 2833 payload type using local and remote SDPs.
• Sends DTMF packets using RFC 2833 PT according to the received SDP.
• Expects to receive RFC 2833 packets with the same PT as configured by the
“RFC2833PayloadType” parameter.
Note 3: If the remote party doesn’t include the RFC 2833 DTMF relay payload type in
the SDP, the gateway uses the same PT for send and for receive.
Note 4:
If TxDTMFOption is set to 0, the RFC 2833 payload type is set according to the
parameter ‘RFC2833PayloadType’ for both transmit and receive.
IsDTMFUsed
[Use Out-of-Band DTMF] Use out-of-band signaling to relay DTMF digits.
0 = Disable, DTMF digits are sent according to DTMFTransportType parameter.
(default)
1 = Enable sending DTMF digits within INFO or NOTIFY messages.
When out-of-band DTMF transfer is used DTMFTransportType is automatically set to 0.