I'm migrating from an old Lucent Definity system 75 and currently using CallManager 3.0(8).
Our old system could assign extensions to groups which could control routing patterns... I'm sure CM does the same thing, but I need help -- I have three classes of phones I need to implement:
1) Classroom phone - This phone can receive calls, and if anyone tries to make an outside call (9.@) it then prompts for their personal ID# / long distance/billing code
2) Office phone - This phone receives calls and can make local calls without a billing code; long distance calls require a billing code.
3) Executive phone - No long distance code restrictions.
Is there any way to implement this? I'd like each individual person to have their own billing code, and don't want to have them "log in" to the phone... it should be a simple dial 4 digits for an outside line setup.
We don't have anything built into CallManager to support codes at the moment. You could use an external solution such as IP-IVR to implement this, or if you are using AS5300 for the gateway you can implement an IP-side TCL script and RADIUS server to implement the functionality.
For example, using route partitions and calling search spaces, you could setup route patterns that actually included unique codes based on a variety of different methods, such as by department, by person, by building, etc.
An example might be that 1 phone may be able to dial the following patterns:
9.@ for local numbers (using a route filter to restrict anything but local numbers and services like 911)
91234.@ for long distance (route filter set for long distance dialing)
95678.@ for international (route filter set for international dialing)
And then only people knowing the special codes would be able to dial the numbers you wish.
Obviously using just these generic codes for all phones in the system is not particularly secure. However using partitions and CSS as I mentioned before you can get very granular, even down to the point where each phone's code for long distance and international numbers are different from other phones... of course the more granular you make it the more time-consuming it will be to configure -- and to maintain. If you are not familiar with partitions and calling search spaces, a good intro can be found at:
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...