In a normal troubleshooting scenario, when you have proved it works in all situations except one, then it would be the "one" that is at fault.
That would be the "normal" case. However, we are talking about Asterisk ;) DTMF has been very problematic in Asterisk for a long time and there are various interpretations and implementations of RFC2833. What I suspect you have encountered is your carrier has a particular SIP switch which is not compatible with the RFC2833 implementation as implemented in Asterisk 1.2.x. Actually, I'm surprised that it works with Unlimitel. Their switches used to require a manual patch to Asterisk 1.2.X in order to work properly but perhaps they have recently implemented a work around so that Asterisk 1.2.X works? And I suspect the other carriers have done the same which is why it works with most of them. So the short answer is, Asterisk 1.2.9.1 is probably at fault but since so many people use Asterisk most carriers have implemented a work-around. BTW, if I remember correctly; the problem with Asterisk is that it doesn't set the tone length (or it leaves it at zero or something). Some systems consider this to be invalid so they ignore it but most systems default to the bare minimum DTMF length. Either way this causes problems since even the minimum length is very hard to detect reliably. More recent versions of 1.4 have dramatically improved DTMF. John On Tue, 2008-03-25 at 12:36 -0400, Reza M. Reza wrote: > I have an issue with a carrier and hoping for some feedback. My carrier > has been amazing and responsive, but as in any business, there are minor > things that arise from time to time The issue I am facing is that > RFC2833 does not work on certain numbers, specially government IVRs. > This is on Asterisk 1.2.9.1 > > I then tested the exact same thing RFC2833 on the government numbers in > question from my Asterisk 1.4.18 It works perfectly. > > > HOWEVER!!!!!!! > 1. When I use other CDN trunks from 1.2.9.1 Asterisk with RFC2833 it > works FINE. > 2. When I use Unlimitel it is fine. > 3. When I use a dozen other carriers (American), its ALL fine. > 4. Regardless of 1.2.9.1 or 1.4.18 RFC2833 works from ALL other carriers. > > SO..... > IF ALL other carriers are passing DTMF perfectly from my 1.2.9.1 except > for the one in question, then would it be fair to say the problem is the > specific carrier which is consistent in failure to transmit DTMF to those > government numbers? Or are there other possible scenarios that I may be > missing out? > > The quick fix here is to divert outgoing calls from 1.2.9.1 to the trunks > that are 100% on DTMF via RFC2833. > > Any suggestions is welcome! > > Best, > Reza. > > > --------------------------------------------------------------------- > 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]
