Wednesday, April 2, 2008

Re: [asterisk-biz] Solving DTMF issue

On Wed, 2008-04-02 at 16:45 -0500, Kevin P. Fleming wrote:
> Trixter aka Bret McDanel wrote:
> > dtmf in asterisk (rfc2833) violates the rfc. There are many switches
> > that usually are only "big carrier types" that do not properly deal with
> > what asterisk sends. I gave oej specifics as he was doing something
> > relating to a filed bug on this issue. I even wrote a patch, but until
> > asterisk is no longer released gpl I cant contribute it (personal thing
> > just as some wont contribute unless its gpl I wont contribute if it is).
>
> This was only true with Asterisk up to and including 1.2; 1.4 and beyond
> send proper RFC2833 (now RFC4833) DTMF telephone-events and
> interoperability has been dramatically improved.
>
I just noticed that you said rfc4833, I assume you meant 4733, however
that is not backwards compatible with 2833. The marker bit changed
meanings, as did a couple of other things. Its 90% the same or so, and
they even cut and pasted some of the poorly written paragraphs from
2833, but there are differences that will break 2833 in other ways. The
differences from the spec I mentioned are all afaik broken for both.

So my question is is asterisk only 4733 now? Or is it dual mode?


--
Trixter http://www.0xdecafbad.com

Bret McDanel
Belfast +44 28 9099 6461 US +1 516 687 5200
http://www.trxtel.com the phone company that pays you!


_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-biz mailing list
To UNSUBSCRIBE or update options visit:

http://lists.digium.com/mailman/listinfo/asterisk-biz

No comments: