Visual Dialplan For Asterisk
The lack of interest to Visual Dialplan option really puzzles me. I understand that an experienced administrator does not need a visual dialplan, except perhaps as a view of what's already configured. I also understand that this forum is not frequented by the end users or office administrators:). That said, I am surprised that practically nobody (of our service provider customers) wants to have a tool that may let their customers manage themselves. Do you think this is 1) not realistic (as in - customers will call you anyway after they do something wrong or get stuck), 2) will drive your fees down faster than costs as it will look like 'self service', or you think that 3) most of your customers won't use it anyway?
I am assuming you mean something like the picture I attached. In my experience customers very rarely change their IVR once it is programmed. Set it & forget it. If it took one person 2 days to code it would be a nice selling feature but it would take longer to train the user on how to use it than to do it ourselves.
If you move forward please budget to have professional documentation produced we can give to the end user. I would rather see every penny spent toward: 1. Fixing bugs 2. Fixing bugs 3. Improving mobile applications - it is rapidly going to a mobile first world 4. Current documentation for administrators/resellers 5. Yealink phone apps (I could see paying per seat for this) 6.
Enhanced routing options a. Burnintest linux keygen. Choose things like 1st & 3rd Saturday b. Route on Labor day, Thanksgiving & day after, etc instead of having to update every year - c.
Combine/link operator and time based routes - now we have to loop calls 7. Create global phone templates (If you can today let please let me know) Attached file.
Visual Dialplan for Asterisk® is modern rapid application development platform for Asterisk dial plan development. It comes with drag-and-drop visual modeling environment and large component library, handy dial plan samples, powerful validation engine, and single button deployment functionality.
Couldn't agree with Matt more. Discussed this numerous times with you historically and even provided a very detailed writeup on call flow either on the forums or in an email to you on the need for improved call flow (Matt's '6c') with custom flow destinations and variables. We too have to loop calls in all kinds of hackish ways to meet our customer's needs with the existing very basic routing options. I would say the order is fix bugs, fix bugs, improve call routing, enhance mobile applications. I do not really agree with Matt on the need for a dedicated holiday schedule because that just opens up a new can of worms because I am sure every company operates with a different holiday schedule. Some companies are open 'black Friday', others close. Some may work Christmas Eve/New Years Eve, others close and consider those days holidays.
Visual Dialplan For Asterisk
As such, I do not think you can ever eliminate the manually oversight for call routing on holidays, but it can be made easier with more advanced call routing options (custom call destinations/variables). Matt youre going to love me with regards to this.