We have a department with an 800 toll-free line who wishes for a call attendant. To acomplish this, I simply forward all calls from this number to a call handler within Unity. The departments complaint stems from callers ability to dial extensions other than their own from within the auto attendant, thereby paying for other department's calls (through the 800 number). Is there a way that we can limit what is input into a call handler so that callers can only be transfered to certain extensions, not all the extensions on campus?<br><br><br>Sean Poure<br>NEC-Voice Engineering<br>Sr. Aplication Engineer<br>714 4846275<br>
Sounds like tenant services which we don't really have right now. The only way I could see preventing people from hopping all over the place is to direct callers within Call Handlers via locked key Caller Input keys, but depending upon how many places they need to go (the more, the worse) it could be a pain.
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...