Howto:DTMF and SIP
Supported
- DTMF signaling through RTP channel (aka. telephone-event) acc. to RFC-2833
- DTMF signaling through signaling channel using INFO request
- DTMF as tones
DTMF signaling through RTP channel
For end-to-end signaling. Requires negotiation of a payload type for "telephone-event". Both endpoints needs to offer a payload type for "telephone-event". If either side does not provide a payload type for "telephone-event", this way of DTMF transmission is not possible.
DTMF signaling through signaling channel
Transport using INFO request with Content-Type "dtmf-relay". This way of DTMF transmission is used when (1) is not possible.
DTMF as tones
If a VoIP endpoint is configured to generate DTMF as audio tones, non of the above signaling methods are used. DTMF tones are part of the audio stream. Processing requires DTMF tone detection at the receiving side which usually requires hardware support (DSPs). DTMF tone detection hardly works together with audio compression like G.723 or G.729.
Why is INFO used on my installation?
INFO (1.2) is used if "telephone-event" (1.1) is not possible.
And "telephone-event" is not possible if payload type is not negotiated.
Object busing DTMF
DTMF-handling objects such as Voicemail or WaitingQueue will only work with signaled DTMFs through RTP or signaling channel. Inband-DTMF recognition requires a DSP.