I have an action set up in my conference call controls like so: <action application="bind_digit_action" data="confi,#*,exec:javascript,/usr/share/freeswitch/scripts/record-my-name.js" /> Which oddly works with some calls but not with others (all the calls are coming via the same operator network - the SIP/RTP comes from a media gateway somewhere in their network). In the case of a good one, we see this in the console: 2015-07-07 14:41:08.597322 [DEBUG] switch_rtp.c:6039 RTP RECV DTMF #:480 2015-07-07 14:41:08.597322 [DEBUG] switch_channel.c:488 RECV DTMF #:480 2015-07-07 14:41:08.937325 [DEBUG] switch_rtp.c:6039 RTP RECV DTMF *:480 2015-07-07 14:41:08.937325 [DEBUG] switch_channel.c:488 RECV DTMF *:480 2015-07-07 14:41:08.937325 [DEBUG] mod_conference.c:4131 Execute app: javascript, /usr/share/freeswitch/scripts/record-my-name.js and in the case of a bad one: 2015-07-07 14:43:13.897322 [DEBUG] switch_rtp.c:6039 RTP RECV DTMF #:480 2015-07-07 14:43:13.897322 [DEBUG] switch_channel.c:488 RECV DTMF #:480 2015-07-07 14:43:14.757320 [DEBUG] switch_rtp.c:6039 RTP RECV DTMF *:480 2015-07-07 14:43:14.757320 [DEBUG] switch_channel.c:488 RECV DTMF *:480 In other words the DTMF are seen, but the bind action doesn't fire. I grabbed a trace of the RTP, and the two cases look indistinguishable, there are start/stop events, with sensible volume and duration (in fact these parameters are the same in the two cases). Can anyone tell me what further diagnostics are available in Freeswitch to tell why the DTMF don't fire the bind action? Regards, Martyn