This means what ever device is sending the dtmf is FAILING at life. AKA Not sending the proper end bits so we give up and accept the digit anyway. But you should complain to your device manufacture and have them read and understand RFC2833 properly. Seems to be a great source of pain in SIP. -- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH_Wire T: +1.918.420.9266 | F: +1.918.420.9267 | M: +1.918.424.WEST iNUM: +883 5100 1420 9266 UK: +44 20 3298 4900 ISN: 410*543 On Nov 21, 2012, at 2:58 AM, Debasish Chandra <debasish.chandra@telemune.net> wrote:
Hi,
I am getting "Failed DTMF sanity check" randomly (not on every call, 2 - 3 calls out of 10). Application is running using Plivo REST API, while FS receiving call from Sangoma NSG TDM gateway. I have read on FS wiki that "Failed DTMF sanity check" means FS never received RFC2833 DTMF 'end' packet. However call tcpdump shows that DTMF digits has been sent to FS from Sangoma NSG, FS showing error "Failed DTMF sanity check" and ignores the digit.
Please let me know if I need to do any extra settings like editing dtmf duration or type.
Best Regards, Debasish Chandra