Update (1/27/2014): We've migrated our community/forum experience to our DevNet Developer community at communities.cisco.com/community/developer.  We've locked the forums here on 1/24 from future entries, but are leaving them open for review for 30 days. To ask a new question or post a new comment please proceed to communities.cisco.com/community/developer and find the corresponding space supporting the technology you're interested in or working with.

To head back to DevNet, click here

Make plans now to attend XMPP integration with CVP 2012/06/14 @ 10:00 AM at Cisco Live! in San Diego.

 



Cisco Developer Network will be presenting a CDN Developer Track at Cisco Live! London the week of January 31, 2011.

We are presenting technical sessions which highlight Application Programming interfaces (APIs) and Software Developer Kits (SDKs) for Cisco technologies such as Unified Communications, IOS, and Access Routing Technologies ¿ including the new Cisco Cius Application Development SDK ! You¿ll get technical insight into the available interfaces, hear from subject matter experts and learn about the benefits of becoming a Cisco developer.

Learn more about the new Cisco Live track for the Developer Network Program!

http://www.ciscolive.com/europe/attendees/education/dnp

 

Recently noticed that there have been repeated questions from our developer community complaining that they can't seem to get the beep to work with <record>. They have set the beep attribute to "true" alright, and the reference guide even says this is supported but why doesn't it work?

It fails to work coz IOS still has a vxml version defaulted to pre2.0, you can check this using the "show run" on the gateway. And hence it still behaves as a pre2.0 compliant browser wrt some . Run this command at the CLI to make it 2.0 compliant
# vxml version 2.0
and voila!! the beep works emoticon

Another tedious way would be to add a beep.wav audio before the record element. Any takers?

 

August 01, 2006
Earlier today, as I was typing a comment in our internal issuing-tracking system, I hit backspace to correct a typo. WHAM! I go back to the previous page, and my long-winded comment is gone. Apparently I somehow left the context of the text area (did I tab, or spuriously click, or??), which causes backspace to act as a hotkey for "Back". The web browser was not very forgiving of my mistake.

Are your IVR applications forgiving? They should be.

I can think of one great example. When I call my cell phone provider's voicemail system, and I delete a message, I am immediately given the option "To undelete this message, press 1." If I am checking my voicemails on the go and accidentally hit the 7 key (delete) instead of what I meant to do, this is a lifesaver!

I can also think of many calls (I won't name companies) where I've ended up in some part of the app where I was destined to hear a message and be disconnected. What if I got there by mistake? What if I would prefer to leave a message? Forgive me for not using the app in the way you had forecasted. If I feel that it's impossible to make mistakes while in your app, I probably won't mind using it again.

Posted by Vance

 

Mark Gibbs over at Network World has put together a spiffy little scoring system for customer service systems (including many criteria for IVR systems). How would callers score your IVR using Mark's guidelines? Place a call and find out, you may be surprised.

Even if you are still in the development stages, it's worth a read; many of his observations are a quick-n-dirty VUI design lesson. However, I don't necessarily agree with all of his criteria, such as "Subtract one point if there is music on hold" and "Add one point if a human answers". Different callers will value these things in different ways, and an IVR that your customers enjoy using may be more welcome than a live agent.

Here are some highlights:

Subtract three points if the person or IVR tells you that you have to call another number for the service you want. Subtract 1,000 points if the other number is wrong, busy or discontinued.
...subtract three points if you have to listen to a long menu of choices and the IVR won't let you enter your selection until it finishes. Subtract 10 points if the choice you're looking for and what you are offered are completely different.
Subtract 10 points if the first person you speak to does not have [your call] details, and if you get transferred, subtract 10 points for each subsequent person without your details.
Posted by Vance

 

Showing 1 - 5 of 6 results.
Items per Page 5
of 2

CVP Forum

Threads
There are no threads in this category.
Showing 0 results.
Thread Flag Started By Posts Views Last Post
There are no threads in this category.
Showing 0 results.