Al, I spoke with a tech support person at Digium today. He suggested adding a 'w' to the dial string. I did this and thus far it appears to have solved the problem.
; we must add a pause (w) in the dial string for some reason otherwise the dtmf digits sent won't be complete. ; appears only to be a problem with tdm400 cards, x100p cards seem to dial ok without the w exten => _9X.,1,Dial(ZAP/10/w${EXTEN:1}) exten => _9X.,2,Congestion As a side item, while doing all the testing to figure this out, I noticed that there is a delay in the dialing of the last digit. So if you dial 5551212 the card actually dials 555121 <pause> 2. Does anyone know why it does this? The Digium support guy seemed to think it was a bug and suggested I report it on bugs.digium.com, which I'll do unless someone here can enlighten me as to the a meanful purpose to the delay. It already takes longer than is really comfortable to dial a number so I'd like to speed it up as much as possible. Mark > I have the *exact* same problem. Please let me know if you have found > any solution. Thanks! > > In my setup I have 2 of the TDM400P cards, with four FXO modules each. > > Al > > [EMAIL PROTECTED] wrote: > >>I have a tdm400p 4 port fxo card which is not reliably creating the dtmf >>dialed digits when making a call. I have placed a linemans handset in >>monitor mode on the line and can hear that what the system reports it is >>dialing is not what the card is actually dialing. This happens about >>25-50% of the time. The remaining time the digits dialed are correct and >>the call goes through properly. >> >>For example, I dial 5551212 >> >> == Spawn extension (default, 95551212, 1) exited non-zero on >> 'SIP/102-8da7' >> -- Executing Dial("SIP/102-07cb", "Zap/2/5551212") in new stack >> -- Called 2/5551212 >> -- Zap/2-1 answered SIP/102-07cb >> >>The system logs that it's dialing 5551212 to channel zap/2.. great. >> >>Now when I actually listen to what the card is dialing, it doesn't dial >>5551212 but something like 555212. I don't know what exactly it's >> dialing >>since I can't decode dtmf in my head, but it's clearly missing a digit or >>two. As a result, the telco comes back with a "your call can't be >>completed" because the full phone number wasn't dialed. >> >>I have a X100P which is also in the system which works just fine.. it >>never has this problem. >> >>This is a brand new card, and I only have this one, so I can't test with >>any others. Maybe it's defective? I've spent all day trying to >>troubleshoot this - I've tried different phone lines, even put the card >>into another box I built to try and troubleshoot. Always get the same >>intermittant problem. >> >>Also I've noticed in this testing that there is a slight pause before the >>last digit is dialed. This always occurs and I'm curious why it does >>this. >> >>Thanks for anyones help! >> >>Mark >> >>_______________________________________________ >>Asterisk-Users mailing list >>[EMAIL PROTECTED] >>http://lists.digium.com/mailman/listinfo/asterisk-users >>To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-users >> >> > > -- > Alok K. Dhir <[EMAIL PROTECTED]> > Symplicity Corporation > http://solutions.symplicity.com > 703 351 6987 (w) | 703 351-6357 (f) > > _______________________________________________ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users