Navigating IVR
# support
r
Is there a way to navigate IVR without using Twilio Flex? Upon doing it in Twilio flex there no way that you could include parameters such as name, email etc.. upon call forwarding. Basically you wont able to use those dynamic variables you have set in your prompt such as name, email and etc... I need this to fix urgent. @User
z
Hey Rommel, I was thinking about this too -- can you keep your call on hold and conference in Twilio Flex to press the IVR buttons so that the original call maintains context? What does your integration with Twilio Flex look like?
s
@Rommel and @zyf, Please allow me a few days to investigate this matter further. I will be in touch with @Gelo , who is also working on a similar solution. We will provide you with an update as soon as we have a solution.
z
Sounds great thanks Shubham
Hey @Shubham Bajaj just following up to see if you have an update here!
Hey @User just bumping this again -- thanks!
s
@Rommel @zyf I checked with my team the feature has been picked and we are evaluating the possible solutions . there are generally three methods for sending DTMF tones: In-band (this is what we do, sending the button frequency over the audio wire) 2 different out-of-band methods: RFC 2833/4733 - send digits as non-audio RTP packet SIP INFO - send digits as SIP INFO requests RFC 2833 is the default that most people use. an ideal implementation would have all three and/or configure which one for each call. twilio doesn't support RFC 2833 over bidirectional streams. they'll want to use elastic sip trunking in twilio to send calls to our SBC and then DTMF will work SO, if you as a human can call the number and your dtmf tones are working BUT when bot calls and sends dtmf it's not working, THEN most likely they use our SBC
I will let you know guys once this is resolved.
z
Thanks for the context! This continues to be important to us so I really appreciate it and look forward to the updates