asterisk users - Jul 2008 - ?? Vitelity dtmfmode=rfc2833 started working!

I appreciate your report (below), but it's a strange and disturbing
coincidence for me.  DTMF out through Vitelity was not working for me until 1-2
days ago when I changed it from rfc2833 to inband!

Maybe I just missed the change date and I should change it back?

----

Date: Tue, 22 Jul 2008 12:23:39 -0400
From: "Mark G. Thomas" <Mark at Misty.com>
Subject: [asterisk-users] Vitelity dtmfmode=rfc2833 started working!
To: asterisk-users at lists.digium.com
Message-ID: <20080722162339.GA12794 at lucky.misty.com>
Content-Type: text/plain; charset=us-ascii

Hi,

Last week my outbound (dtmfmode=inband) DTMF via Vitelity started acting
more weird than usual, and for outbound calls, incoming DTMF tones would
consistenly get stuck, breaking a call screen macro I had set up.

I checked "sip show peer" and saw that Vitelity for inbound was
now reporting "DTMFmode : rfc2833" (it didn't used to), so
switched
my ountbound dtmfmode to rfc2833 and my problems went away! Yay!

It looks like Vitelity now supports rfc2833 on SIP channels.

I thought others might be interested in knowing this, as at least in my
case it broke things until I changed my settings, and I see this has been
a prior source of frustration for many others.

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20080722/a57bd3f3/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3221 bytes
Desc: S/MIME Cryptographic Signature
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20080722/a57bd3f3/attachment.bin