02-28-2008 02:14 PM - edited 03-13-2019 05:01 PM
Outlook displays phone numbers without the 91. When I click on an Outlook contact CUPC shows failed conversation. If I add a 91 plus the 10 digit phone number to the contact then click on it the call goes through. I tried adding an Application Dial rule in CM 6 but it doesn't seem to work. Adding 91 to all of our company contacts is out of the question. Any other suggestions on how to fix this problem?
Thanks:)
Solved! Go to Solution.
03-07-2008 10:42 AM
actually we got it working with app dial rules. please confirm you have configured the following app dial rule (no 414*, since regexp in app dial are somehow different than in translation pattern)
Name: CUPC-Add91
Number Begins With: 414
Number of Digits: 10
Total Digits to be Removed: 0
Prefix With Pattern: 91
however, app dial rules are based on fix number of digits. so you have to be sure the rule matches your dial length. for 4145551212 this would be 10
no, you don't have to restart any CUCM service, only the both CUPS services mentioned in my last post - and probably CUPC client.
03-05-2008 02:42 PM
Try this BUG - CSCsb19302
03-05-2008 02:54 PM
Thanks for the information but we are using Outlook not OWA. The problem occurs when we click to dial any external phone number from the Outlook contacts page. Out Outlook contact phone numbers appear as 414-XXX-XXXX. The 91 needs to be inserted automatically so the Communications Manager sees 91414XXXXXXX. I am not sure how to make that happen automatically from Outlook.
03-06-2008 01:12 AM
we have faced the same problem. actually you can use CUCM application dial rules to dial from your outlook contacts.
add the following application dial rule to CUCM:
Name Number Begins With Number of Digits Total Digits to be Removed Prefix With Pattern
CUPC-Add91 414 10 0 91
to activate the application dial rules for CUPC you have to restart CUPS services "Cisco UP SIP Proxy" as well as "Cisco UP Presence Engine".
hope this helps. if so, please rate
03-07-2008 08:57 AM
Unfortunately that didn't work. First I tried using 414 and then I tried a * as the dialed digits and neither one worked. The only thing that works so far is manually adding 91 in my Outlook contacts but we have too many contacts company wide to add 91 to all of them. When I built the app dial rule with a * in the "Number Begins With" field I could still dial out from my outlook contact which showed up in Outlook as 914145551212. I thought the app dial rule would add 91 making the number dialed out number 91914145551212 if the app dial rule was applied. I am wondering if a service needs to be reset on the CM to enable the app dial rule. Any thoughts?
03-07-2008 10:42 AM
actually we got it working with app dial rules. please confirm you have configured the following app dial rule (no 414*, since regexp in app dial are somehow different than in translation pattern)
Name: CUPC-Add91
Number Begins With: 414
Number of Digits: 10
Total Digits to be Removed: 0
Prefix With Pattern: 91
however, app dial rules are based on fix number of digits. so you have to be sure the rule matches your dial length. for 4145551212 this would be 10
no, you don't have to restart any CUCM service, only the both CUPS services mentioned in my last post - and probably CUPC client.
03-07-2008 11:42 AM
Awesome - it's working. I restarted CUPC and Outlook. So I guess you have to restart the SIP and Presence service then restart CUPC and maybe Outlook too to get this working.
03-07-2008 12:13 PM
glad it helped!
07-27-2008 11:34 AM
First, thank you for posting and helping.
Questions:
That solutions will have to be implemented for each long distance area code that your user community use, right (414, 212, 954, etc)?
What about local calls, jus prefix with â9â instead of â91â, I am guessing. The dilemma for us, what about when you have 2 or more sites? If you have the following, anyway to do this?
New York
212
Florida
954
If you append 91 for 212 (10 digits), it will work for the Florida office what about the New York office calling local from outlook, they only need the â9â.
Have any one had the situation above?
08-20-2008 07:20 AM
We now have a better method for the Application Dial Rules which will save a lot of programming time.
For local calls = Number begins with - leave blank, Number of digits - 7, Total digits to be removed - 0, Prefix with pattern - 9.
For toll calls = Number begins with - leave blank, Number of digits - 10, Total digits to be removed - 0, Prefix with pattern - 91.
08-25-2008 12:46 PM
How do you handle it when some exchanges in the local area code are long distance? Do you have to build a list of all the local exchanges to remove the area code?
If so, is there a limit to the number of dial rules, since each exchange will have to be listed seperately.
Thanks
08-25-2008 12:51 PM
Please refer to the previous message "we now have a better method" and you will see that only a couple of entries need to be entered for all exchanges.
08-25-2008 01:28 PM
So your contact do not have the area code if they are a local call, correct?
The problem with that is that if they sync with a cell phone it will cause problems when the area code needs to be dialed from the contacts.
Does that make sense?
08-26-2008 04:57 AM
The user clicks to dial from Outlook then the call goes out through the user's desk phone. This works on our system for all calls to cell phones and land line phones. I haven't tried using it to call out my desk phone via my cell phone. Mobile Voice Access is disabled on our system.
08-26-2008 08:10 AM
After talking to our own user community and customers communities everyone agreed that users are responsible for having the right number, 7 digits local, 10 digits local and long distance code â1â for USA. This way they can replicate their Outlook and their phone (Blackberry & PDA's) without breaking either system (Outlook & Presence).
We are responsible for adding the outside code, in our case and most customers was â9â, so we add the following 3 Dial Rules:
7 digits local
Number of Digits: 7
Total Digits to be Removed: 0
Prefix with Pattern: 9
10 digits local
Number of Digits: 10
Total Digits to be Removed: 0
Prefix with Pattern: 9
11 digits LD
Number Begins With: 1
Number of Digits: 11
Total Digits to be Removed: 0
Prefix with Pattern: 9
The âNumber Begins With: 1â & âNumber of Digits: 11â is very important not to confuse with 11 digits calls â92124441234â. This is safe since no USA area code can start with â1â.
Finally, after creating the rules above you need to restart some services on the Presence Server, I took the Microsoft approach and reboot the Presence Server instead to be safe.
Regards,
Hiram
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