[Standards-JIG] Jingle: DTMF

Matthew O'Gorman ogorman at gmail.com
Wed Feb 15 19:40:44 UTC 2006

i can tell you thomas that the majority of sip devices only support inband
in ulaw or rfc2833 , info digits is the lame duck.  and I agree doing inband
would be very stupid is well.  I think the only two reasonable candidates
are rfc2833 or some xmpp solution.  Like I have said before both are fine,
doing it in rfc2833 is more in tune with sip and makes it easier for
connecting to sip gateways esp. if your routing traffic like google is,
however, it is not the jabber way, or at least thats what i think.  I don't
think it really matters which is chosen as they both will work well.  I
think it will put more work on the client developers as they will have to
implement that part using an rtp stack where as before it is simple xmpp.
But seriously please just pick one. ^_^


On 2/15/06, Thomas Charron <twaffle at gmail.com> wrote:
> On 2/15/06, Matthew O'Gorman <ogorman at gmail.com> wrote:
> >
> > yes thomas rfc2833 acts much like a voice packet just it contains a
> > digit.  It is very important what is decided, because it will decide what
> > clients implement, if you have mulitple methods all clients must implement
> > multiple methods or they will not interoperate correctly with each other,
> > and in the end every client will just need to support all formats, when only
> > one was really needed, putting more work on everyone.
>   See my last message..  ;-)
>   Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060215/9e3ce1da/attachment.html>

More information about the Standards mailing list