[Standards-JIG] Jingle: DTMF

Joe Beda jbeda at google.com
Tue Feb 14 20:41:49 UTC 2006

I'm not a fan of this proposal but I'm okay with this as long as it isn't
required.  The result would be two ways to get DTMF to a client: XMPP and
embedded in RTP.  I'd prefer that we only have one way.

I would be strongly against *requiring* DTMF to be handled in the XMPP
* When gatewaying to other protocols, this would require the media to be
proxied/relayed in order to put the DTMF onto the signalling channel. This
could raise the bandwidth cost of doing gatewaying dramatically.
* Keep in mind that the latencies on the XMPP connection could be much
higher than the latency on the RTP/P2P channel.  In situations where the
timing of the DTMF is critical this could cause problems.


On 2/14/06, Peter Saint-Andre <stpeter at jabber.org> wrote:
> Hash: SHA1
> I just read through the older thread on Jingle with PBX etc. My sense
> right now is that including DTMF [1] as part of the Jingle audio media
> description format (JEP-0167) would be best. So to send DTMF codes to
> the other party (which might be an Asterisk server, a voicemail box, an
> IVR system, or what have you), we'd send Jingle "info" messages with a
> special Jingle audio payload. Here's an example:
> <iq from='juliet at capulet.com' to='voicemail.shakespeare.lit' type='set'>
>   <jingle xmlns='http://jabber.org/protocol/jingle'
>           action='info'
>           initiator='romeo at montague.net/orchard'
>           sid='a73sjjvkla37jfea'>
>     <dtmf xmlns='http://jabber.org/protocol/jingle/info/audio'
>           code='1234'/>
>   </jingle>
> </iq>
> If a gateway needs to convert that into audio tones or whatever (e.g.,
> RFC 2833 format for RTP), it could do so, but we'd never send those as
> audio tones over XMPP.
> Thoughts?
> Peter
> [1] http://margo.student.utwente.nl/el/phone/dtmf.htm is a nice page
> about DTMF if you're wondering what it is. :-)
> Version: GnuPG v1.4.1 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> iD8DBQFD8j82NF1RSzyt3NURAgL2AJ91Xw6SZFKSzX/h34/LPNU29wo/ZgCaAok1
> kB4QMSsnH624WSVydOGCPA0=
> =zT9M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060214/985dc15a/attachment.html>

More information about the Standards mailing list