one your gateway could just convert the xmpp to dtmf, much like
asterisk does or any other sip to pstn gateway, and two there is no
reason to support multiple dtmf formats for one protocol, you might as
well just pick one that works the best.<br><br><div><span class="gmail_quote">On 2/15/06, <b class="gmail_sendername">Pedro Melo</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>On Feb 15, 2006, at 5:34 PM, Thomas Charron wrote:<br>> Let's not forget that DTMF *WAS CREATED* to get around a total<br>> LACK of any sort of supplimental signaling over phone lines. We<br>> now have this. Why not use it?
<br><br>Because old style PSTN will not support it ever? And for those who is<br>vital to interop with them, this is not an option?<br><br>For PSTN integration I really don't see any other option except RTP-<br>based one. At least in our environment, a telco.
<br><br>About other protocols: I think that it's great to have standards for<br>signaling other protocols. I just don't see the need to be inside the<br>jingle spec.<br><br>If my Jingle buddy, via a gateway, has a JID X, I can disco JID X,
<br>find out support for "Electric Chair Protocol", and use the<br>appropriate JEP to signal my pain to him. Why do I need to put this<br>inside Jingle?<br><br>Same goes for DTMF even: I disco my jingle buddy, the gateway
<br>responds with "DTMF-over-XMPP" protocol, and you follow that JEP,<br>probably with a <message> of some sort.<br><br>Really, XMPP already does this. I'm probably missing something, but<br>why do we want to put this inside Jingle?
<br><br>Best regards,<br>--<br>HIId: Pedro Melo<br>SMTP: <a href="mailto:firstname.lastname@example.org">email@example.com</a><br>XMPP: <a href="mailto:firstname.lastname@example.org">email@example.com</a><br><br></blockquote></div><br>