![]() ![]() Anyone know what DTMF signaling mode works best for the Cisco SPA504G ? Some user feedback suggests speakerphone echo perhaps is causing this issue. The Cisco 504G is setup with the following settings: Not sure if I need to restart the phone, rebuilt template or anything else of the change to happen? If I switch the extension DTMF setting to auto I see the same thing. DTMF: channel.c:4191 _ast_read: DTMF end ‘8’ has duration 68 but want minimum 80, emulating on SIP/2281-00016531 DTMF: channel.c:4184 _ast_read: DTMF end ‘8’ detected to have actual duration 68 on the wire, emulation will be triggered on SIP/2281-00016531 ![]() To test I called a conference # 50 times but couldn’t recreate the issue It happens infrequently so unfortunately I don’t have logged examples of when the issue occurs. SIP trunk: set to dtmf=auto on the PEER side Phones: Cisco SPA504G running firmware 7.5.6aĮxtension: DTMF on the extension is set to RFC 2833 Trying to troubleshoot a DTMF issues where a small percentage of the time when people are calling to conferencing services like GoToMeeting (but not just GoToMeeting) it doesn’t properly recognize the digits they type in.
0 Comments
Leave a Reply. |