04-22-2009 04:29 AM - edited 03-18-2019 10:54 PM
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
04-22-2009 05:10 AM
Check out this doc for the click the call. The application dial rules are perfect for CUPS also. Uses the same premise.
Also search the forum for Application Dial Rules. You will find many comments on the + symbol. In CUCM 6, it ignores the + all together and just looks at the digits. In CUCM, it uses the plus as a digit, etc. So adjust your strings accordingly.
09-09-2011 08:37 AM
How to proceed with the application dial rules if I want CUPC to dial a number from the IE beginning with 0+variable length number and should be converted to +49+variable length number to match the e164 dialplanin the CUCM.
As I know the Appl Dial rules supports only fixed length numbers..., this excludes international installations of CUPC with a click to dial usage.
Any idea ??
Thanks,
Jacky
09-09-2011 08:38 AM
You will have to come up with every variable since its only fixed. If you notice the table for application dialing rules, the international numbers are all there for different lengths.
09-13-2011 08:51 AM
Hi,
There is a concept of Phone number masks in CUPC.
This is for CUCILync but its valid for CUPC too
Brian
09-13-2011 09:03 AM
Hi Brian,
very interesting as the wildcards are covering also variable/overlapping dialplans.
But, are you sure this is helpfull for Office and Browser Strings Click to Call ??
Jacky
09-13-2011 09:06 AM
Hi Jacky,
This covers the contact resolution when calling from CUPC only. Non alpha-numeric characters in C2C are ignored.
Brian
09-13-2011 09:14 AM
Well, do you have suggestions to filter out the best IE/Office strings in a variable length/overlapping dialplan
like in Germay?
In the IE we could have some wild formats...
I did not find any cool way to do that as the application dial rules covers only fixed length strings, even on CUCM 8.5
The only solution I've found is to use dedicated CUPC CSS/PART, separated from what the deskphone is using.
This way we could interfere with the existing country dialplan, that's why it is not an ideal way.
Jacky
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide