we're running UCM 7.1.3 and currently using the UCM internal database for directory lookups. I want to change this so that UCM pulls data from AD via LDAP. The problem I have is that the UCM database listed users extensions in 4 digit format and in AD it's the full E.164 number.
I need to create a solution to the following - can anyone help.
When the users get imported from AD into UCM their contact number will be (for example)
site a 01925 85XXXX
site b 01235 51XXXX
We route 4 digit extension numbers between sites over our WAN. So currently when a user querys the phone directory site a calls site b they use the 4 digit extension that routes via the WAN.
When we import the users via AD this will be different as the numbers displayed will be the full 11 digit E.164 number. This means that when site a calls site b all calls will be routed via the PSTN and will cost us money.
I need to come up with a solution that takes the 11 digit PSTN numbers that will be displayed within the ucm directory and discards digits from the dialled string so that the following happens.
user a looks in the corporate directory for user b - the number displayed in 11 digits and looks something like this 01235 511234 user a then calls this number and through some route pattern configuration only the last 4 digits are called (1234) this will allow us to route calls over the WAN while allowing for the import from AD to happen.
I've been looking at pre dot discard digits and think this might be the correct way to procced - can someone help?
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: firstname.lastname@example.org 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 ...