[Standards-JIG] Jingle: DTMF

Matthew O'Gorman ogorman at gmail.com
Tue Feb 14 20:40:11 UTC 2006


you could also have a <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 duration=100'/>
>   </jingle>
> </iq>



for a duration of 100 ms

On 2/14/06, Peter Saint-Andre <stpeter at jabber.org> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> 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. :-)
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFD8j82NF1RSzyt3NURAgL2AJ91Xw6SZFKSzX/h34/LPNU29wo/ZgCaAok1
> kB4QMSsnH624WSVydOGCPA0=
> =zT9M
> -----END PGP SIGNATURE-----
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060214/4355af82/attachment.html>


More information about the Standards mailing list