[cisco-voip] Active Directory Integration using E.164

[Go0se]

Mark,

 

Just a note, in my example the numbers were not entered into AD with the
lead "+".  As others have suggested the "+" can cause some issues. Also, you
may or may not need the outside access code or enter it both ways.

 

Thanks,

 

Go0se

 

My blog: 

http://atc.go0se.com <http://atc.go0se.com/> 

 

-------------------------------------

Help Hopegivers International 

feed the orphans of India.

http://www.hopegivers.org <http://www.hopegivers.org/> 

-------------------------------------

 

From: Mark Marquez [mailto:MMarquez at goldsys.com] 
Sent: Thursday, February 18, 2010 9:24 PM
To: Go0se; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Active Directory Integration using E.164

 

Thanks goose.  Your screenshot verifies what I was thinking.  I also really
like the IP phone option that Scott Voll suggested. I hadn't noticed that
under the LDAP Directory configuration screen there are two options for
Phone Number -telephoneNumber and ipPhone.  This is great.  I've got
options. Thanks everyone.

 

 

Mark Marquez

Unified Communications Specialist

Gold Systems, Inc.

4840 Pearl East Circle, Suite #106

Boulder, Colorado 80301

303.447.2774 say "Mark Marquez"

mmarquez at goldsys.com <mailto:loui at goldsys.com> 

 

From: Go0se [mailto:me at go0se.com] 
Sent: Thursday, February 18, 2010 2:48 PM
To: Mark Marquez; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Active Directory Integration using E.164

 

I have done exactly what you describe for the same reason and  it works
without any issues - at least none that I have seen. Added benefit: if you
have users in remote offices that don't realize they can 4 digit dial it
keeps them from ringing up toll charges or at worst if you have toll bypass
configured it keeps them from tying up trunk lines.

 



 

Thanks,

 

Go0se

 

My blog: 

http://atc.go0se.com <http://atc.go0se.com/> 

 

-------------------------------------

Help Hopegivers International 

feed the orphans of India.

http://www.hopegivers.org <http://www.hopegivers.org/> 

-------------------------------------

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mark Marquez
Sent: Thursday, February 18, 2010 2:43 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Active Directory Integration using E.164

 

I'd like to hear from the list regarding the possible implications of using
E.164 formatted numbers (i.e. +1333445555) in Active Directory and
performing CUCM LDAP integration using CUCM7.  The internal extension ranges
vary depending on location and can be either 4 or 5 digits extensions.  I
realize that by populating Active Directory with E.164 numbers that the CUCM
Directory would probably not have numbers in a "dialable" format.  In other
words, I wouldn't be able to select a telephone number via the Corporate
Directory and dial it unless some kind of Translation pattern were applied
behind the scenes. Again, I'm assuming I could use a Translation pattern to
modify the E.164 number displayed in the Directory to either a 4 or 5 digits
number.  If this is possible, and what other things should I take into
consideration.

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100218/6a4c0034/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 42420 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100218/6a4c0034/attachment.png>