DTMF in call script

DidierDE

Bronze Partner
Advanced Certified
Joined
Nov 12, 2025
Messages
43
Reaction score
5
We are facing issues with DTMF.

We have made a script that can call a user when an alert is triggered in our monitoring tools.

The agent has to press 1 to confirm receiving the alert.

When the agent accepts the call using the 3CX app, this works fine.
When the agent has set 'Also ring my mobile', the agent can hear the message, but confirming by pressing 1 does not work.

We also have an IVR and there we can use DTMF to select menu options.

What can I do to make this work?
 
Hi @DidierDE is the issue only with the external calls? what voip provider is this? is it a supported sip trunk?

Do they support DTMF RFC2833?

Could you please check if the issue with the DMTF is only with inbound or outbound calls.
 
When making an inbound call to our IVR, DTMF works.

When making an outbound call, and an engineer tries to confirm with DTMF, it does not work.

In the wireshark trace on the 3CX server, we can see that the DTMF signal is coming in.
1794930660976.png


It is a generic sip trunk to our voice gateway.
 
Ok @DidierDE I tested your scenario and identified the issue. When a mobile number is set in a user extension with "Also ring my mobile" enabled, DTMF forwarding is not supported once the call is answered on the mobile device. This is why keypad inputs (DTMF tones) pressed on the mobile phone are not being passed through.

To resolve this, disable "Also ring my mobile" and configure the status forwarding rules to route calls to the mobile number instead. DTMF will work as expected with that setup.
 
Ok @DidierDE I tested your scenario and identified the issue. When a mobile number is set in a user extension with "Also ring my mobile" enabled, DTMF forwarding is not supported once the call is answered on the mobile device. This is why keypad inputs (DTMF tones) pressed on the mobile phone are not being passed through.

To resolve this, disable "Also ring my mobile" and configure the status forwarding rules to route calls to the mobile number instead. DTMF will work as expected with that setup.
The issue here is that the call is sent to a queue. In this way different agents can easily switch their duty status on or off.
And when a call is sent to a queue, the forwarding rules are not applied...
 
Since the DTMF can be seen in the wireshark trace, it means that our provider and voice gateway support it and it is 3CX that does not support it. Is this something that can be changed?
 
Hi @DidierDE as mentioned before, when using the parameter Also Ring my Mobile and the call is answered in the mobile, there is not DTMF forwarding.

You need to use either the forwarding rule to route to the mobile number or install the 3CX App on the smartphone.
 
I understand that it is not supported at the moment. My question is if it is a possibility to add this in the (near) future? Technically, it should be possible, since I can see that the DTMF signal is coming in.

Using forwarding rules is no option in this case for us because forwarding rules are not applied when calling to a queue.
 
I created a workaround by changing my script. The script now first checks when the agent has 'Also ring my mobile' enabled. If so, the call goes directly to the mobile number and then DTMF works.
 
  • Like
Reactions: Alejandro_3CX

Forum statistics

Threads
112,547
Messages
593,145
Members
165,757
Latest member
Aline