E.164 dial pattern question

[Lance Cutler]

I am in the middle of a jabber phone only rollout.  I am working on e.164 click to dial for them.  I have a mix of DID and non DID in format +17143669860 for did and +17143661000 ext 1234 for non did.  The jabbers see the non-did as +171436610003981234.  My users on 7962 see it as +17143661000 ext 1234.  They cannot dial it like Jabber can.  Am I SOL on the 7962 or am I missing something?

[Chris Deren]

What is the actual extension assigned to the CSF device? I dont follow when you say the 7962 sees it as +17143661000 ext 1234, what do you mean by that?

Each DN should be unique across the system, and if a decision was not to give DIDs to some folks then you should be using internal only DNs for those, ie. +1000000XXXX, or whatever you decide on.

[Lance Cutler]

The extensions are 5 digit for now.  Some are full E.164.

I am referring to the corporate directory on the devices pulling from AD.

I am sorry I lefte that out...

[Chris Deren]

I see, phones will not be able to dial this long extension, i.e +17143661000 ext 1234 as thee is a limit to how many characters they pull from the directory, Jabber might work as the limit does not exist assuming you have proper translation/application dial rule for it.  There is nothing you can do short of fixing the appearance in AD.

[Dennis Mink]

Lance,

I strongly advise you to clean up AD and only use E164 to populated its phone numbers.

in fact, use E164 as the extension on all phone and use the enterprise alternate numbers and E164 alternate numbers to cater for your 5 digit number plan. and have the best of both worlds.

Jabber directory lookup is a direct reflection of what you have in AD, so clean that up first