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

[Mark Marquez]

Calling/Called transformation apply to a number going to a GW or trunk.  I've used these transformations before.  I don't believe they can be applied to telephone number selected via the Corporate Directory. I was thinking translation patterns.

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: Mathew Miller [mailto:miller.mathew at gmail.com]
Sent: Thursday, February 18, 2010 2:22 PM
To: Mark Marquez
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Active Directory Integration using E.164

This is covered pretty extensively in the CUCM 7 SRND http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/dialplan.html#wp1103930

You would basically used Called and Calling Party number transformations.


On Feb 18, 2010, at 2:42 PM, Mark Marquez wrote:


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.


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100218/da93f2a4/attachment.html>