FASTDEVICE Posted February 4, 2018 Report Posted February 4, 2018 My use case is for the user to press 9 (or any callflow ext.) and hear a dial tone while trying to collect dtmf. In my case, I want the user to dial a telephone number and it seems the most intuitive way to let them know what's expected.
Administrators Darren Schreiber Posted February 4, 2018 Administrators Report Posted February 4, 2018 Is this like "dial 9 for an outside line" style?
FASTDEVICE Posted February 4, 2018 Author Report Posted February 4, 2018 yes, sir. And thanks for the quick reply.
Administrators Darren Schreiber Posted February 4, 2018 Administrators Report Posted February 4, 2018 Yup np. Sooo actually most physical phones support this capability via their dialplan configurations. http://forum.yealink.com/forum/showthread.php?tid=1492 as an example.
FASTDEVICE Posted February 4, 2018 Author Report Posted February 4, 2018 Wouldn't that end with an actual number being dialed from the phone? I'm wanting to enter a pivot, grab a number, compare that number to what's in a database and route accordingly.
Administrators Darren Schreiber Posted February 4, 2018 Administrators Report Posted February 4, 2018 If the goal is to have them dial 9 plus a number, the Dialplan would strip the 9 and send the full number to Kazoo (when dialed). You would then make a no_match rule to capture all outbound calls and process them via Pivot instead. Not sure that actually works the way you want.
FASTDEVICE Posted February 4, 2018 Author Report Posted February 4, 2018 (edited) genius.... replace no_match global carrier with pivot. I love that idea and don't even care if they dial 9. I was only considering that to enter a callflow. Let me take a few swings at a strategy, it might work. Edited February 4, 2018 by FASTDEVICE (see edit history)
FASTDEVICE Posted February 4, 2018 Author Report Posted February 4, 2018 Oh and thanks! So excited , I'm jumping head in.
.thumb.png.53ba4a40488cd13986c71377d45b8fdf.png)
Recommended Posts