Simon, I will second that with Matthew. Not a single issue we have with DTMF on RFC2833 - Packet to Packet bridging. With one client we process close to 100K calls per month with 10 Digit DTMF per call with Caller ID authentication on their calling card platform. At one point we did aggressive tests from both land lines and cell phones, were close to 100% perfect. With all our CLEC's I am peered with RFC2833 as an FYI.

Cheers!

--
*FOUNDER & SR. TELECOM ANALYST
VOIPERNETICS COMMUNICATIONS
NATION WIDE DIDS, SIP TRUNKS & VOIP 911.
PARTIAL / FULL VIRTUAL PRI - NO CONTRACTS!
HOSTED PBX & TERMINATION SERVICES.
TEL:  647-476-2067

*

[email protected] wrote the following on 4/28/2011 10:28 PM:
And what DTMF mode are you trying to use on both the SIP Trunk and the device?  
With RFC2833 on both side and Packet to Packet bridging you shouldn't have any 
issues.


------Original Message------
From: [email protected]
To: Simon P. Ditner
To: [email protected]
To: 'Asterisk Users Group'
ReplyTo: [email protected]
Subject: Re: [on-asterisk] DTMF, will it ever work?
Sent: Apr 28, 2011 22:27

Which version of asterisk are you using?
------Original Message------
From: Simon P. Ditner
Sender: [email protected]
To: 'Asterisk Users Group'
Subject: [on-asterisk] DTMF, will it ever work?
Sent: 28 Apr 2011 22:22

Is there some trick to getting asterisk working reliably when calling
into conference bridges and voicemail? No end of trouble with DTMF on
my home system regardless of which provider I'm using. Drives my wife
nuts when she's working from home.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


Sent from my BlackBerry device on the Rogers Wireless Network

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to