I am baffled by my Callmanager behavior. It is ignoring the Calling Search Spaces when routing calls, and is dialing the closest match.
For example, a remote site has Partition A with DN 101, and the main site has Partition B with a route pattern 1XX which is connected to an old PBX (there is a 101 DN on the PBX).
The main site does NOT have rights to dial the remote site over the WAN, and the remote site isn't supposed to be able to dial the main site. All site to site calls are supposed to go over the PSTN.
The problem is, an IP phone at the main site dials 101 expecting to be transfered to the PBX, but gets the remote site IP phone. In otherwords, CallManager is choosing the exact match of 101 instead of the 1XX pattern, even though that IP phone doesn't have the Partition A in it's CSS.
I've gone over the Calling Search Spaces (phone and line) and Partitions with a fine tooth comb, but I can't figure out what's happening. I also checked the translation patterns, reset the calling search spaces, and made sure there were no route patterns in the <none> partition.
The gateway is MGCP, and the CallManager version is 3.3(3)sr76.
I don't have Dialed Number analyzer on the publisher. Any ideas?
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 ...