That's the most primitive LCR function I have ever seen. It simply doesn't do a thing other than following the defined list. It requires people making the calculation first and manually updates it as required.
The kind of LCR function I am referring to, is CCM selecting the best route based on automatic calcution on specific values (usually cost). It can further determine the best route to go cost wise depends on the time, the existing volume, etc. CCM doesn't do that now!
Well, without further information I had nothing else to go on.
We don't currently have anything natively in CallManager that can route calls based on the results of a mathematical expression that gives the best actual cost. Values in the expression could be things like which trunk, what time of day, how many active calls on existing trunks, etc.
I don't know if this type of feature is on the product roadmap for CallManager or not.
In the meantime, the only way I can think of to implement this is through a CTI application using TAPI or JTAPI. And you would need some sort of front-end to the application so that the administrator can say what type of trunks they have, how many going to each provider, how much their minutes cost during what days and times, etc.
It would not be a small undertaking at all, but I know of no native way to accomplish this cost based automation within CallManager currently.
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...
[toc:faq]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 discusse...