With the LDAP sync between AD and CUCM and CUPS, dialing straight from CUPC by right clicking your contacts, will result in dialing the extension as entered in AD under telephone number (or business phone).
Now, many people in our organisation have entered E.164 numbers, have added brackets, spaces etc. in other words, patterns that are not recognised by CUCM. As CUPC is essentially a CTI device, all digit manipulation will have to take place on CUCM. which does not have the flexibility of SIP patterns.
As we have about 4000 users on presence, having these people to change their contact number via our AD front end is a daunting task
Have other people in this forum dealt with this issue?
i know CUCM 7 at least handles the + sign in patterns but that will only partially fix the issue