(Solved) DTMF Tones sudden problem

Just got notice of this problem that started out of nowhere with our DTMF tones to dial access codes for our gotomeeting conferences. The problem is that it doesn’t recognize the tones at all. This worked perfectly for the past yr. Also with other confrence lines it reconizes the tones but sometimes it thinks you pressed the number twice.

Wondering if an update caused the issue or what we can possibly do to fix our problem.

We haven’t done any changes to the server but run the freepbx updates from time to time thats what makes me believe that it may have been caused by an update.

Thanks in advance,
Joe

I have solved this by changing DTMF mode from inband in trunk to auto… And in the extensions changing dtmfmode to inband. Don’t know why but this is the only way this seemed to work for me.

I honestly dont’ know what to say. If you put DTMF in your logger.conf file like I shnowed you. Are you running tail -f /var/log/asterisk/full ?

When you hit a key it should show up on the tail. Don’t know about that "rotate.

This may be a case for a higher authority. Keep posting, though. You’ll get it. What kind of phones are you using? On Polycoms there is a setting for DTMF in sip.cfg. I monkied around with those. The only think that worked for me was dtmfmode=inband in the Trunk.

Also for extensions I have set:

dtmfmode rfc2833

Is this correct?

Also got some output now, it seems that it is being passed through but Gotomeeting wont acknowledge them:

[Apr 4 11:14:48] VERBOSE[2015] logger.c: == Using SIP RTP TOS bits 184
[Apr 4 11:14:48] VERBOSE[2015] logger.c: == Using SIP RTP CoS mark 5
[Apr 4 11:14:48] VERBOSE[2015] logger.c: – Called vonage-18566522249/16265210011
[Apr 4 11:14:48] VERBOSE[2015] logger.c: – SIP/vonage-18566522249-00000003 is making progress passing it to SIP/6010-00000002
[Apr 4 11:14:48] VERBOSE[2015] logger.c: – SIP/vonage-18566522249-00000003 answered SIP/6010-00000002
[Apr 4 11:14:59] DTMF[2015] channel.c: DTMF begin ‘6’ received on SIP/6010-00000002
[Apr 4 11:14:59] DTMF[2015] channel.c: DTMF begin passthrough ‘6’ on SIP/6010-00000002
[Apr 4 11:14:59] DTMF[2015] channel.c: DTMF end ‘6’ received on SIP/6010-00000002, duration 220 ms
[Apr 4 11:14:59] DTMF[2015] channel.c: DTMF end accepted with begin ‘6’ on SIP/6010-00000002
[Apr 4 11:14:59] DTMF[2015] channel.c: DTMF end passthrough ‘6’ on SIP/6010-00000002
[Apr 4 11:15:00] DTMF[2015] channel.c: DTMF begin ‘8’ received on SIP/6010-00000002
[Apr 4 11:15:00] DTMF[2015] channel.c: DTMF begin passthrough ‘8’ on SIP/6010-00000002
[Apr 4 11:15:00] DTMF[2015] channel.c: DTMF end ‘8’ received on SIP/6010-00000002, duration 240 ms
[Apr 4 11:15:00] DTMF[2015] channel.c: DTMF end accepted with begin ‘8’ on SIP/6010-00000002
[Apr 4 11:15:00] DTMF[2015] channel.c: DTMF end passthrough ‘8’ on SIP/6010-00000002
[Apr 4 11:15:01] DTMF[2015] channel.c: DTMF begin ‘7’ received on SIP/6010-00000002
[Apr 4 11:15:01] DTMF[2015] channel.c: DTMF begin passthrough ‘7’ on SIP/6010-00000002
[Apr 4 11:15:01] DTMF[2015] channel.c: DTMF end ‘7’ received on SIP/6010-00000002, duration 190 ms
[Apr 4 11:15:01] DTMF[2015] channel.c: DTMF end accepted with begin ‘7’ on SIP/6010-00000002
[Apr 4 11:15:01] DTMF[2015] channel.c: DTMF end passthrough ‘7’ on SIP/6010-00000002
[Apr 4 11:15:04] DTMF[2015] channel.c: DTMF begin ‘4’ received on SIP/6010-00000002
[Apr 4 11:15:04] DTMF[2015] channel.c: DTMF begin passthrough ‘4’ on SIP/6010-00000002
[Apr 4 11:15:04] DTMF[2015] channel.c: DTMF end passthrough ‘4’ on SIP/6010-00000002
[Apr 4 11:15:11] DTMF[2015] channel.c: DTMF begin ‘6’ received on SIP/6010-00000002
[Apr 4 11:15:11] DTMF[2015] channel.c: DTMF begin passthrough ‘6’ on SIP/6010-00000002
[Apr 4 11:15:11] DTMF[2015] channel.c: DTMF end ‘6’ received on SIP/6010-00000002, duration 190 ms
[Apr 4 11:15:11] DTMF[2015] channel.c: DTMF end accepted with begin ‘6’ on SIP/6010-00000002
[Apr 4 11:15:11] DTMF[2015] channel.c: DTMF end passthrough ‘6’ on SIP/6010-00000002
[Apr 4 11:15:11] DTMF[2015] channel.c: DTMF begin ‘8’ received on SIP/6010-00000002
[Apr 4 11:15:11] DTMF[2015] channel.c: DTMF begin passthrough ‘8’ on SIP/6010-00000002
[Apr 4 11:15:12] DTMF[2015] channel.c: DTMF end ‘8’ received on SIP/6010-00000002, duration 220 ms
[Apr 4 11:15:12] DTMF[2015] channel.c: DTMF end accepted with begin ‘8’ on SIP/6010-00000002
[Apr 4 11:15:12] DTMF[2015] channel.c: DTMF end passthrough ‘8’ on SIP/6010-00000002
[Apr 4 11:15:12] DTMF[2015] channel.c: DTMF begin ‘7’ received on SIP/6010-00000002
[Apr 4 11:15:12] DTMF[2015] channel.c: DTMF begin passthrough ‘7’ on SIP/6010-00000002
[Apr 4 11:15:12] DTMF[2015] channel.c: DTMF end ‘7’ received on SIP/6010-00000002, duration 230 ms
[Apr 4 11:15:12] DTMF[2015] channel.c: DTMF end accepted with begin ‘7’ on SIP/6010-00000002
[Apr 4 11:15:12] DTMF[2015] channel.c: DTMF end passthrough ‘7’ on SIP/6010-00000002

(on and on)

[Apr 4 11:15:40] VERBOSE[2015] logger.c: – Executing [h@macro-dialout-trunk:1] ^[[1;36;40mMacro^[[0;37;40m("^[[1;35;40mSIP/6010-00000002^[[0;37;40m", “^[[1;35;40mhangupcall,^[[0;37;40m”) in new stack
[Apr 4 11:15:40] VERBOSE[2015] logger.c: – Executing [s@macro-hangupcall:1] ^[[1;36;40mGotoIf^[[0;37;40m("^[[1;35;40mSIP/6010-00000002^[[0;37;40m", “^[[1;35;40m1?skiprg^[[0;37;40m”) in new stack
[Apr 4 11:15:40] VERBOSE[2015] logger.c: – Goto (macro-hangupcall,s,4)
[Apr 4 11:15:40] VERBOSE[2015] logger.c: – Executing [s@macro-hangupcall:4] ^[[1;36;40mGotoIf^[[0;37;40m("^[[1;35;40mSIP/6010-00000002^[[0;37;40m", “^[[1;35;40m1?skipblkvm^[[0;37;40m”) in new stack
[Apr 4 11:15:40] VERBOSE[2015] logger.c: – Goto (macro-hangupcall,s,7)
[Apr 4 11:15:40] VERBOSE[2015] logger.c: – Executing [s@macro-hangupcall:7] ^[[1;36;40mGotoIf^[[0;37;40m("^[[1;35;40mSIP/6010-00000002^[[0;37;40m", “^[[1;35;40m1?theend^[[0;37;40m”) in new stack
[Apr 4 11:15:40] VERBOSE[2015] logger.c: – Goto (macro-hangupcall,s,9)
[Apr 4 11:15:40] VERBOSE[2015] logger.c: – Executing [s@macro-hangupcall:9] ^[[1;36;40mHangup^[[0;37;40m("^[[1;35;40mSIP/6010-00000002^[[0;37;40m", “^[[1;35;40m^[[0;37;40m”) in new stack
[Apr 4 11:15:40] VERBOSE[2015] logger.c: == Spawn extension (macro-hangupcall, s, 9) exited non-zero on ‘SIP/6010-00000002’ in macro ‘hangupcall’
[Apr 4 11:15:40] VERBOSE[2015] logger.c: == Spawn extension (macro-dialout-trunk, s, 19) exited non-zero on ‘SIP/6010-00000002’ in macro ‘dialout-trunk’
[Apr 4 11:15:40] VERBOSE[2015] logger.c: == Spawn extension (from-internal, 916265210011, 5) exited non-zero on ‘SIP/6010-00000002’
[Apr 4 11:15:40] VERBOSE[2016] logger.c: == MixMonitor close filestream
[Apr 4 11:15:40] VERBOSE[2016] logger.c: == End MixMonitor Recording SIP/6010-00000002
[Apr 4 11:15:42] VERBOSE[1990] logger.c: > Saved useragent “Mitel-5220-SIP-Phone 06.00.00.19 08000F165759” for peer 2013

ok for some reason my log was empty so I had to run asterisk -rx “logger rotate”

had to add DTMF to full in /etc/asterisk/logger.conf

already had dtmfmode=inband in trunk

nothing shows up in my asterisk/full log or my debug at verbosity of 15 of me entering any DTMF tones.

Same as trying to enter my access code (there recording keeps playing not acknowledging my pressing any keys)

Would give you my log and debug info but there is nothing to show.

Can give it to you anyways if you think it will help.

run tail -f /var/log/asterisk/full
Make sure you have DTMF in your /etc/asterisk/logger.conf file so that you have something that looks like this:

;debug => debug
;console => notice,warning,error
console => notice,warning,error,debug,verbose
;messages => notice,warning,error
full => notice,warning,error,debug,DTMF,verbose

If you are using SIP, try putting dtmfmode=inband in your Trunk

1 Like