[Standards-JIG] Jingle: DTMF

Matthew O'Gorman ogorman at gmail.com
Tue Feb 14 23:41:52 UTC 2006


well you can get around this error the same way rfc2833 gets around it using
sequence numbers

On 2/14/06, Steve Kann <stevek at stevek.com> wrote:
>
> Matthew O'Gorman wrote:
>
> but this isnt always something you can do early, it is a realtime event,
> end user presses one so that the other end can send you on in the ivr.
> however i dont see how you could have them come out of order as the other
> end is most likely waiting for said dtmf
>
>
> This seems to assume that all DTMF exchanges are just one digit..
>
> You get to an IVR prompt:  "How many widgets would you like to buy?".  You
> dial "109".  If each digit is a separate stanza, and the stanzas are not
> guaranteed to arrive in order, the other end may receive "901", and you're
> going to wonder why you get 792 more widgets than you asked for!
>
> -SteveK
>
>
>
> On 2/14/06, Jean-Louis Seguineau <jean-louis.seguineau at laposte.net >
> wrote:
> >
> > 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
> > order.
> >
> >         <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'<http://jabber.org/protocol/jingle/info/audio%27>
> > >
> >              <tone code='1234'/>
> >              <tone code='5678' duration=100'/>
> >             </dtmf>
> >           </jingle>
> >         </iq>
> >
> >
> >
> > -----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,
> > Simon
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060214/7642cb17/attachment.html>


More information about the Standards mailing list