X-Lite, Asterisk, and RFC2833 DTMF Support

[DirtyPete]

Hello,

Through discussion on the Asterisk developers mailing list, it appears that we may have stumbled upon a bug in the implementation of RFC2833 in X-Lite. Please use the following as reference:

The post on the mailing list: http://lists.digium.com/pipermail/asterisk-dev/2003-July/001176.html

It has something to do with the "duration" field in the RTP packet when sending an RFC2833 compliant DTMF sequence.

Thanks!

[DirtyPete]

Hello,

Through discussion on the Asterisk developers mailing list, it appears that we may have stumbled upon a bug in the implementation of RFC2833 in X-Lite. Please use the following as reference:

The post on the mailing list: http://lists.digium.com/pipermail/asterisk-dev/2003-July/001176.html

It has something to do with the "duration" field in the RTP packet when sending an RFC2833 compliant DTMF sequence.

Thanks!

A bit of added data from the mailing list:

<Direct quote from Chris Heiser of asterisk-dev>
Here's the payloads as X-Lite sends them:

010A00A0
010A00A0
010A00A0
010A00A0
010A00A0
010A00A0

As you can see... the duration field is staying at 0A0 which is incorrect.
The proper sequence should look something like this:

010A00A0
010A0140
010A01E0
010A0280
010A0320
010A03C0
etc...
</quote>

[lgoodman]

I think I am running into this 2833 bug as well. Is there anyway in Xlite
to disable 2833 support and just run the dtmf inband?

Thanks

Lee Goodman

[DirtyPete]

I think I am running into this 2833 bug as well. Is there anyway in Xlite
to disable 2833 support and just run the dtmf inband?

Thanks

Lee Goodman

Erik said he was going to fix it soon.. Hopefully soon will be within the next couple days

Pete

[rob]

Should be fixed in private build 1059 or greater. There was an asterisk bug as well, not sure which build you need for it.

-Rob