This patch seemed to do the trick for me when we had issues sending DTMF to our carrier (which is NOT L3). http://h6315.com/dtmf.patch
> Date: Fri, 20 Jul 2007 13:13:22 -0700 > From: "Douglas Garstang" <[EMAIL PROTECTED]> > Subject: Re: [asterisk-biz] Sprint via L3 problems: no DTMF > To: "Commercial and Business-Oriented Asterisk Discussion" > <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > We received this from Level 3 last week. If they've done it already, > then they are early! > > " Dear Level 3 Customer, > Level 3 will be upgrading gateway media servers and initial feasibility > tests have shown that Asterisk software versions prior to 1.4 are not > compatible with RFC specifications. The issue relates specifically to > Asterisk's support for Dual-Tone Multi-Frequency (DTMF) named events > (RFC 2833). > > Asterisk software prior to version 1.4 does not send "duration" in the > actual DTMF Event packet. This violation of RFC 2833, as described in > sections 3.5 (Payload Format) and 3.6 (Sending Event Packets), causes > call failures on Level 3's network. > > However, this is a known issue which has been resolved by Asterisk > beginning > with their code release 1.4. > > For customers using earlier version of Asterisk, you will need to > upgrade your Asterisk software to version 1.4 or higher by August 1, > 2007 in order to prevent disruptions to your service. Failure to upgrade > your network will result in DTMF detection failures beginning August 1, > 2007, may negatively impact your calling traffic over the Level 3 > network. > > In-band DTMF detection will continue to function properly on Level 3's > network and can be used as an alternative to the software upgrade. > > Level 3 provides this notification more than 45 days in advance of the > network GCR so that customers have adequate time to upgrade their > software. > > If you have questions or concerns about this letter please contact the > Level 3 Service Management Center at 1-877-453-8353 option 4 followed by > option 3. > We appreciate your business and apologize for any inconvenience this may > > cause you." > > Douglas. > > >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:asterisk-biz- >> [EMAIL PROTECTED] On Behalf Of Peter Beckman >> Sent: Friday, July 20, 2007 12:30 PM >> To: [email protected] >> Subject: [asterisk-biz] Sprint via L3 problems: no DTMF >> >> Folks -- >> >> I'm troubleshooting a strange issue. >> >> Asterisk 1.2.13 -> Vitelity -> L3 -> Sprint Mobile Phone 703-867 >> >> DTMF fails from the Sprint Mobile Phone back to my Asterisk box. >> >> When Vitelity routes that call out a different carrier, DTMF works > fine. >> >> Can those of you with access to L3 termination and a Sprint Mobile > test >> DTMF back to asterisk? >> >> Beckman >> > ------------------------------------------------------------------------ > -- >> - >> Peter Beckman > Internet >> Guy >> [EMAIL PROTECTED] >> http://www.angryox.com/ >> > ------------------------------------------------------------------------ > -- >> - >> ** PLEASE NOTE PurpleCow.com IS NOW AngryOx.com DO NOT USE > PurpleCow.com >> ** >> ** PurpleCow.com is now owned by City Auto Credit LLC as of May 23, > 2007 >> ** >> > ------------------------------------------------------------------------ > -- >> - >> >> _______________________________________________ >> --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 > > > > ------------------------------ > > Message: 7 > Date: Fri, 20 Jul 2007 16:27:06 -0400 > From: "Anthony Cennami" <[EMAIL PROTECTED]> > Subject: Re: [asterisk-biz] Sprint via L3 problems: no DTMF > To: "Commercial and Business-Oriented Asterisk Discussion" > <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > My organization uses L3 among others directly for SIP orig/term. It is > worth noting that some time ago we received communication from L3 that > their > new infrastructure (switch software update) would no longer support > Asterisk > 1.2 DTMF, and that users term/orig calls on the L3 network would be > required > to upgrade to 1.4.x by 8/1/07 > > I'm not sure L3 is aware of the implications of this, nor their > sub-carriers > who provide wholesale/resold access into the L3 network, but it is > unfortunately true. > > 1.4 came with a substantial rewrite of the DTMF code, and in fact requires > SIP options to be enabled if you are going to be passing calls between > 1.4and > 1.2 boxes. > > Personally I think L3 is going to be unhappy when they find out just how > many * 1.2 boxes are terminating RTP directly to them, and that many of > those people will be forced to reroute traffic/switch carriers/upgrade > systems. > > For those of you who are not connected directly with L3, but do terminate > RTP with them, I suggest you speak to your reseller to determine what you > or > they may need to do...... > > anthony > > > On 7/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> >> Many times this is a cell phone config problem. >> Look at the settings on the cell phone for DTMF. >> If it is on "SHORT" then change it to "LONG" or "continuous". >> >> James Taylor >> MetroTel >> http://www.metrotel.net >> 1-972-505-3503 >> >> >> Quoting Peter Beckman <[EMAIL PROTECTED]>: >> >> > Folks -- >> > >> > I'm troubleshooting a strange issue. >> > >> > Asterisk 1.2.13 -> Vitelity -> L3 -> Sprint Mobile Phone 703-867 >> > >> > DTMF fails from the Sprint Mobile Phone back to my Asterisk box. >> > >> > When Vitelity routes that call out a different carrier, DTMF works >> > fine. >> > >> > Can those of you with access to L3 termination and a Sprint Mobile test >> > DTMF back to asterisk? >> > >> > Beckman >> > >> --------------------------------------------------------------------------- >> > Peter Beckman Internet >> Guy >> > [EMAIL PROTECTED] >> http://www.angryox.com/ >> > >> --------------------------------------------------------------------------- >> > ** PLEASE NOTE PurpleCow.com IS NOW AngryOx.com DO NOT USE >> > PurpleCow.com** >> > ** PurpleCow.com is now owned by City Auto Credit LLC as of May 23, >> > 2007 >> ** >> > >> --------------------------------------------------------------------------- >> > >> > _______________________________________________ >> > --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 >> > >> > >> >> >> >> >> _______________________________________________ >> --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 >> > > > > -- > Anthony Cennami > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.digium.com/pipermail/asterisk-biz/attachments/20070720/9053ca52/attachment.htm > > ------------------------------ > > _______________________________________________ > --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 > > End of asterisk-biz Digest, Vol 36, Issue 75 > ******************************************** > _______________________________________________ --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
