We have two callmanager clusters. We have servicedesk at three locations. One location, suppose A, is regestered to one CCM cluster and remaining locations B & C are registered to other CCM cluster. Our customer has placed interesting requirement as below:
There will be one pilot number common for servicedesk at all locations and that is only servicedesk number known to all users at all three locations. Every location will be having its own internal pilot number which is known to servicedesk people only and not to any other user.
Common pilot 9999
Location A 6666
Location B 7777
Location C 8888
When a user dials that number, servicedesk extensions at all locations must start ringing. Suppose user at location A dials common pilot 9999 and servicedesk member at location C picks up the call. When that member from location C comes to know that user is from location A and wants to transfer the call to location A, that member will dial pilot number 6666 and servicedesk extensions at location A will start ringing.
I am really very thankful for your prompt reply. We have to implement this on CCM clusters only and we are not suppose to touch Unity for any configuration changes. I tried to use hunt pilot and hunt list, line group for implementation. I created one hunt pilot and added three extensions in it. I forwarded the call of each extension to another pilot number of respective location. When i dialed the main hunt pilot 9999, call got landed to these extensions and not got forwarded to hunt pilots. It means that call forwarding was overriden. Can we overcome the prblm of overriding? is there any work arround?
the only possible option i can think of would be to use mobile connect with members from the line group to ring another phone, i'm not really sure if this will do the trick since it's not really the reason why mobile connect was created.
no WA to make CF settings to be followed, that is WAD.
you could certainly make this ring in cascade but i don't believe you can get this to ring all at once.
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...