[Asterisk-Users] Beta2 problems with DTMF with "T" option in Dial
Command
Hadar Pedhazur
hadar at unorthodox.com
Fri Nov 4 09:12:52 MST 2005
I was running CVS HEAD from 2005/07/31 until the day that beta2 came
out. I installed beta2 on a number of servers without touching anything
in /etc/asterisk.
Most everything has been working well.
One thing that is not is "remote" DTMF, more specifically, the "#" key.
When I dial voicemail from DIAX, connected directly to the asterisk
machine, I can retrieve voicemail. If I have DIAX connected to another
asterisk, and dial the extension that connects me back to voicemail on
that first box, then after I type the box number, it complains about an
incorrect password on the first number that I type, no matter what that is.
This is _not_ just a voicemail problem. If I have a DISA statement, with
a hard-coded PIN, if DIAX is connected to the box directly, DISA works
correctly. If I go through a remote asterisk, DISA fails every time. It
_never_ recognizes the "#", so it thinks the password has "timed out"
every time.
A little digging seems to show that the problem is in the "T" option to
the Dial command which connects the two asterisk boxes. My features.conf
file has "blindxfer = #7" and "atxfer = ##". A single "#" has been
passed through correctly for months. Now, if I remove the "T" from the
Dial command, then the remote voicemail (or DISA) works correctly.
A few details:
1) all boxes in this experiment are running 1.2 beta2.
2) all boxes force ULAW codec only
3) if dtmfmode is ever referenced, it is always set to "inband".
4) all of this worked in CVS HEAD as of July 31st, 2005.
More information about the asterisk-users
mailing list