User`s manual

SIP User's Manual 5. Web Management
Version 5.0 75 December 2006
Table 5-7: DTMF & Dialing Parameters (continues on pages 74 to 76)
Parameter Description
Declare RFC 2833 in SDP
[RxDTMFOption]
Defines the supported Receive DTMF negotiation method.
No [0] = Don’t declare RFC 2833 telephony-event parameter in SDP
Yes
[3] = Declare RFC 2833 telephony-event parameter in SDP (default)
The MediaPack 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 in-band using
G.711 coder, if this is the case you can set ‘RxDTMFOption=0’.
1
st
to 5
th
Tx DTMF Option
[TxDTMFOption]
Determines a single or several preferred transmit DTMF negotiation methods.
0 (Not Supported) = No negotiation, DTMF digits are sent according to the
parameters ‘DTMFTransportType’ and ‘RFC2833PayloadType’ (default).
1 (INFO Nortel) = Sends DTMF digits according to IETF <draft-choudhuri-sip-info-
digit-00>.
2 (NOTIFY) = Sends DTMF digits according to <draft-mahy-sipping-signaled-
digits-01>.
3 (INFO Cisco) = Sends DTMF digits according to Cisco format.
4 (RFC 2833).
Note 1: DTMF negotiation methods are prioritized according to the order of their
appearance.
Note 2: When out-of-band DTMF transfer is used (1, 2 or 3), the parameter
‘DTMFTransportType’ is automatically set to 0 (DTMF digits are erased from the
RTP stream).
Note 3: When RFC 2833 (4) is selected, the gateway:
 Negotiates RFC 2833 Payload Type (PT) using local and remote SDPs.
 Sends DTMF packets using RFC 2833 PT according to the PT in the received
SDP.
 Expects to receive RFC 2833 packets with the same PT as configured by the
parameter ‘RFC2833PayloadType’.
 Uses the same PT for send and receive if the remote party doesn’t include the
RFC 2833 DTMF PT in its SDP.
Note 4: When TxDTMFOption is set to 0, the RFC 2833 PT is set according to the
parameter ‘RFC2833PayloadType’ for both transmit and receive.
ini
file note: The DTMF transmit methods are defined using a repetition of the
same (TxDTMFOption) parameter (up to five options can be provided).
RFC 2833 Payload Type
[RFC2833PayloadType]
The RFC 2833 DTMF relay dynamic payload type.
Range: 96 to 99, 106 to 127; Default = 96
The 100, 102 to 105 range is allocated for proprietary usage.
Note 1: Cisco is using payload type 101 for RFC 2833.
Note 2: When RFC 2833 payload type (PT) negotiation is used
(TxDTMFOption=4), this payload type is used for the received DTMF packets. If
negotiation isn’t used, this payload type is used for receive and for transmit.
Hook-flash Option
[HookFlashOption]
Supported hook-flash Transport Type (method by which hook-flash is sent and
received).
Valid options include:
Not Supported
[0] = Hook-Flash indication isn’t sent (default).
INFO
[1] = Send proprietary INFO message with Hook-Flash indication.
RFC 2833
[4] = RFC 2833.
Note: FXO gateways support the receiving of RFC 2833 Hook-Flash signals.
[IsHookFlashUsed]
This parameter is obsolete; use instead the parameter HookFlashOption