I have a centralized cluster with multiple SRST sites. Can I have multiple 911 CTI Route Points registered to the CER user and CER server?
I need to be able to have multiple route points because I need to customize the forward on failure to the locale 911 gateway, providing the actual building address. From what I'm seeing, I can only have 1 911 route point associated and registered at a time. I also have my 913XXXXXXXXXX route point associated.
I'm having trouble getting an answer from TAC. Anyone have any ideas? Also, if I can only have 1 route point, are there any suggestions on how to route the call out the proper gateway if the CER server were to go down?
There is no possible solution to how we want to design it. When CER is working, then yes, it supports multiple sites. However, if CER fails and Call Manager stays active, there is only one possible route point and one foward on failure option.
One thing to think of is SRST. If, by chance, you have the situation where the CER server and ALL Call Manager servers fail, then your remote sites will be in SRST, thus the 911 call will go out the local PRI or analog port (if you have those at each site)
This will finally be solver in CM 7.0 due out this fall. CM 7.0 introduces a feaure called "local route groups", where one configures Device Pools and points them to local route groups, this way you will have a single default fail 911 route pattern and instead of poiting directly to route list/route group it will point to a route list that has system default local route group listed.
I've actually verified that it will indeed resolve the CER default routing caveat by labbing it out.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...