[Standards-JIG] Jingle: DTMF

Jean-Louis Seguineau jean-louis.seguineau at laposte.net
Tue Feb 14 23:00:54 UTC 2006

There is certainly no guarantee that separate stanzas will reach their
target in the proper order. But we may just group entire DTMF tone sequence
in one single stanza. Then we have a better chance to get them in the proper

	<iq from=' juliet at capulet.com' to='voicemail.shakespeare.lit'
	  <jingle xmlns='http://jabber.org/protocol/jingle'
	          initiator='romeo at montague.net/orchard'
	    <dtmf xmlns='http://jabber.org/protocol/jingle/info/audio'>
             <tone code='1234'/>
             <tone code='5678' duration=100'/>

-----Original Message-----
Message: 2
Date: Tue, 14 Feb 2006 17:19:03 -0500
From: "Simon Guindon" <simon.guindon at tomahawk.ca>
Subject: RE: [Standards-JIG] Jingle: DTMF
To: "Jabber protocol discussion list" <standards-jig at jabber.org>
Message-ID: <3E6F9E04F4CF864DBCC3EECB90FDFB502DA269 at BART>
Content-Type: text/plain; charset="us-ascii"

I'm an advocate of doing it over XMPP because I think this makes the
Jingle gateway more flexible, especially in the sense of other protocols
that may not support DTMF, which allows the jabber client to still
navigate IVR's.
One example comes to mind, lets pretend protocol X gets a jingle
gateway, and there is a voicemail service running on the server. Even a
non-DTMF capable protocol can now navigate IVR's.
On the flip side, I get a bit skeptical as well after thinking a bit
about Joe's thoughts. Can the INFO packets ever come out of order?
Also on the flip side.What in the case of a sip phone calling this
jingle gateway to check voicemail. The jingle gateway will need to
handle SIP's DTMF and pass the INFO messages to the voicemail "server
component" which speaks Jingle.
What are everyones thoughts? I hope I was clear what I was meaning to
get across.
Thanks and take care,

More information about the Standards mailing list