Delay in pressing numbers with dtmf tool
# support
s
There are some calls where IVRs has to be handled but we see delays in the numbers pressed on the calls. Do we know why is that the case?
v
@Shivam Sharma It sounds like you're experiencing latency issues with the Interactive Voice Response (IVR) system where there's a delay in recognizing the numbers pressed during calls. This can be caused by several factors, including network latency, IVR system performance, or the configuration of the IVR system itself. To better assist you, could you provide more details about the IVR system you're using and the specific scenarios where you notice these delays? This information will help in diagnosing the issue more accurately.
You can continue this conversation by mentioning me in the message.
s
@User We have three methods for sending DTMF tones: 1. In-band: This method sends the button or keypress frequencies over the audio wire. 2. RFC 2833/4733: This method sends digits as non-audio RTP packets. 3. SIP INFO: This method sends digits or buttons as SIP INFO packets.
Now, Twilio doesn't support sending DTMF digits as non-audio RTP packets due to the limitations of bidirectional media streams. Because of this, they recommend using Elastic SIP Trunking to send calls, which allows DTMF to function correctly.
that's why the keypress frequencies didn’t work as expected when using the bot, but with Elastic SIP Trunking (which supports SIP INFO), the DTMF tones will work.
s
I'll try this, thanks
e
I've set up Twilio Elastic SIP Trunking and tested the number. It works. However, DTMF is still not coming through from the assistant when the assistant presses numbers on the keypad. Only clicks come through in the audio. Here is a call log with an example: 7d1c2e13-1b18-49ed-924a-7cbb2ff91f8a
s
I tried this, how do i know that twilio elastic SIP trunking is active and being used because I don't see any change.
s
@Shivam Sharma You have to use SIP Calling to enable elastic SIP trunking and then it works pretty much the same. Do let me know if you get blocked somewhere.
e
@Shubham Bajaj here you go: 7d1c2e13-1b18-49ed-924a-7cbb2ff91f8a
s
@Edpreble Thank you for pointing this out! Currently, we don't have IVR navigation fully set up, but we're actively working on mapping it out. Your example is very helpful, it's exactly the kind of input we need to shape our plans. Regarding the timeline, this feature should be available during early Q2 of this year. In the meantime, you can implement IVR navigation programmatically using keywords or phrases, and then programmatically transfer the call to the Vapi number.
@Edpreble You can use Twilio with GPT for IVR navigation and then transfer the call to VAPI. https://github.com/twilio-labs/call-gpt
2 Views