Unity 8.6 Sign-In Conversation plays failsafe prompt after an invaild ID is entered
My customer has requested that all users who attempt to sign in to their voicemail box via the TUI enter their ID first and not be prompted for a PIN based on the calling extension. The two conversations that can be used is "Attempt Sign In" or "Sign In". "Sign In" gives me the expected behavior for my client unless a user enters and invalid ID at which point I would expect to hear "that is an invalid ID" and ask me to try again, however the behavior I get is a prompt (indicated as the Failsafe prompt in the Port Monitor) that says "This system is unable to complete your call. Call again later. Goodbye." and hangs up. Is there a way to change the conversation? Seems to be an unhandled exception from the conversation.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...