Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

X is replaced as digit 9

We have a customer with 8.6 CUCM and CUPS 8.6, CUCM is integrated with their AD where they have all their employees extension as X1234. All works fine when you use a phone and regular CUPC client for Windows but they have some MAC users using Jabber client , when they search directory on Jabber and dial, X is replaced as 9 so it it dials "91234" for internal call and fails. Is there any way we can fix this without changing that X in AD.?

Thanks for your help.

Everyone's tags (3)
5 REPLIES

X is replaced as digit 9

You could use a translation pattern to strip the 9.

New Member

X is replaced as digit 9

I know we can do that but they dial 9 for outbound calls if I use a pattern with 9xxxx stripping 9 all the outbound calls will try to dial only 4 digit and might stop or there may be delays with interdigit timeouts.

X is replaced as digit 9

If you put the Jabber Clients in a separate device calling search space, there should not be any issues as these are SIP clients so they will not get secondary dialtone unless it is configured on the client.  SIP messaging is sent with the entire dialed number rather than digit-by-digit like in SCCP.

New Member

Re: X is replaced as digit 9

Thanks for your quick response. Yes I was planning to do the same as workaround but I wanted to know why this was adding 9 so we can fix it permanently if there is a solution. Thanks for your help again.

Re: X is replaced as digit 9

do you have any application dial rules configured in CUCM that might adding the 9 ?

372
Views
0
Helpful
5
Replies
CreatePlease login to create content