06-18-2015 06:22 PM - edited 03-17-2019 03:24 AM
Hi mates,
On our newly deployed Cisco 8841 phones, the phone won't dial out when the dialed number contains space(s). For example, the number in directory is +12 3 4567 8900. This is not a problem for Cisco 79XX phones when there is invalid digit in the number.
Any suggestion? Thanks in advance.
Regards,
Gary
Solved! Go to Solution.
06-18-2015 08:22 PM
Hi Gary,
There is a bug, try to get the phone to the fixed version
https://tools.cisco.com/bugsearch/bug/CSCuq14595/?reffering_site=dumpcr
Symptom:
When CUCM is integrated with AD and while using Corporate Directory to dial out a user phone number.
If the number is configured on AD with "-" hypen/dash ex: 91-80-XXXX-XXXX calls fails. But Same work fine in other model 79XX,78XX,99XX only fails in 88X1 (Big Easy Phones) if "-" hypen/dash is removed call works.
Conditions:
HW:88X1
SW:sip88xx.10-2-1
Workaround:
Remove "-" hypen/dash on the AD Telephone number attribute and then perform a resync
HTH
Manish
06-18-2015 08:22 PM
Hi Gary,
There is a bug, try to get the phone to the fixed version
https://tools.cisco.com/bugsearch/bug/CSCuq14595/?reffering_site=dumpcr
Symptom:
When CUCM is integrated with AD and while using Corporate Directory to dial out a user phone number.
If the number is configured on AD with "-" hypen/dash ex: 91-80-XXXX-XXXX calls fails. But Same work fine in other model 79XX,78XX,99XX only fails in 88X1 (Big Easy Phones) if "-" hypen/dash is removed call works.
Conditions:
HW:88X1
SW:sip88xx.10-2-1
Workaround:
Remove "-" hypen/dash on the AD Telephone number attribute and then perform a resync
HTH
Manish
06-18-2015 09:14 PM
Hi Manish,
Thank you for the response.
We're at version 10.2(2) and we have the problem. And the versions mentioned in the Bug page are not available in Cisco.com.
We're clearing the problem by changing the phone numbers in AD.
Regards,
Gary
06-18-2015 09:17 PM
These are special versions of firmware. You can contact TAC and they can publish one of the fixed version for you. It will save you a lot of effort. You can also check the release notes for latest firmware on cisco.com and check resolved caveats section to see if this bug is fixed in it.
HTH
Manish
06-18-2015 09:30 PM
Fantastic. Thanks a lot.
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