DTMF detection issues for VOIP calls (e.g. using key presses to acknowledge alarms over voice calls)
TopView can use these key presses to allow calls to proceed, or to acknowledge alarms via voice notifications.
Here are some common issues and solutions if you suspect TopView is not able to detect DTMF during a voice call.
Verify that TopView is not seeing DTMF/key presses
TopView will log all received DTMF/key presses during a phone call.
The easiest method to test DTMF/key press detection is to make a test call from the TopView Configurator. During the test call a log is displayed and updated with information during the call. Any key press events are logged to the screen during the test call.
- The firewall is blocking audio communication
- Poor audio quality prevents DTMF detection
- Set DTMF detection in VOIP system to RFC2833
DTMF tones are sent to TopView from the SIP/VOIP Server as part of the VOIP call. This means that the VOIP server/system is responsible for recognizing the DTMF tone from the recipient's phone and sending that back to TopView.
DTMF issues are usually due to one of the following:
- Firewalling/traffic blocking issues (this is the usual one)
- Check your firewalls and network to ensure ports aren't blocked. SIP transport typically happens on port 5060 and RTP (phone call media) happens on another. DTMF is usually based on call audio so the RTP ports must be open. Test to make sure audio from both sides of the call can be heard. If possible, you can use Wireshark to monitor the call, or The 3CX Firewall Checker Client Application on the TopView computer to try to expose issues.
- Phone/VOIP server
settings and issues (e.g. the DMTF settings for the phone communicate key
presses in a different way that the server expects or understands)
- We recommend setting DTMF detection, if possible, to RFC2833.
- Poor audio quality that affects the VOIP server's DTMF detection
- You may be able to adjust the audio codecs TopView uses to improve the audio quality.
- The receiving mobile device may be able to switch to, or away from, VoLTE ("Voice over LTE") to see if audio quality improves.
Cisco system (e.g. CUCM)
We recommend trying to set up for detection using RFC2833 because we've seen other VOIP systems leverage that and work, and it delivers the DTMF key presses through SIP which TopView is set to monitor.
Here are some other resources that may be helpful:
VOIP and SIP issues
If test voice notifications via VOIP are experiencing difficulties, we recommend the following tests and procedures: Verify that the authorization name and password are correct for the SIP server Can a softphone installed on the same computer as ...
VOIP Phone call register/unregister issues
Overview TopView Voice Notification makes VOIP phone calls for alarm notification. The VOIP protocol is SIP. TopView is a "SIP client" that connects to the SIP Server to make phone calls. Each phone call in TopView is made by a separate call process ...
What codec should I use for voice calls?
TopView voice calls over VOIP allow the specification of a codec used for encoding the audio to be used during the call. This article explains what codecs are and why you might want to use a codec that is different from the defaults used by TopView. ...
Voice Notification: What hardware do I need?
TopView 6.25 dropped support for voice notifications using TAPI modems and it will not be supported for future versions Due to the dwindling hardware and OS-level support for these devices we no longer support TAPI as a notification method. We ...
What do I need for VOIP call-out notification?
For many years TopView has supported voice call-out notification over traditional phone lines but, due to both hardware and software developments, voice notification via TAPI modems is much less reliable than it used to be (see the reliability ...