The important piece is in above log message is number 21156 which is thread id to look for.

Once you identify the interesting line what you need to look for is something like this: VERBOSE res_rtp_asterisk.c: Sent RTP DTMF packet to x.x.x.x:14584 (type 101, seq 052452, ts 411623440, len 000004)

Once above is enabled full file will be filled with data about RTP packets, try to grep by string DTMF. Disable full in nf and perform logger reload Since there will be lots of data, I recommend that you enable above quickly and then reset to default settings:ģ. rtp set debug on needs to be enabled in Asterisk CLI core set debug 3 or core set debug 4 needs to be set in Asterisk CLIģ. nf has to be modified and full debugging with dtmf option has to be enabledįull => notice,warning,error,debug,verbose,dtmf,faxĢ. To do that certain logging options have to be set:ġ. In order to debug problems of incorrectly detected DTMF digits, one needs to figure out whether digits are detected at all and why they are ignored.įirst one should detect via tcpdump that DTMF are indeed sent! And if that is the case, one goes further… Here we will try to quickly explain how to troubleshoot RTP DTMF problems in Asterisk.

Asterisk dtmf