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

[Kevin Thorngren]

The CUCM SRND discusses + dialing support.  May or may not answer your  
questions but it does explain it in depth.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/dialplan.html

Kevin
On Feb 18, 2010, at 4:52 PM, Jason Aarons (US) wrote:

> The + still breaks things like UCCX, and the dialer on my cell phone  
> (syncs to Outlook where some numbers have +).  There might be cases  
> where some DNs would need to be non e164 for awhile.
>
> I recommend longer digits on the phones, with translation patterns  
> to expand your 4-5 digits to the longer match.
>
> This thread was covered last week as well;
>
> http://www.gossamer-threads.com/lists/cisco/voip/125479
>
>
> 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 3: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.
>
>
>
>
> Disclaimer: This e-mail communication and any attachments may  
> contain confidential and privileged information and is for use by  
> the designated addressee(s) named above only. If you are not the  
> intended addressee, you are hereby notified that you have received  
> this communication in error and that any use or reproduction of this  
> email or its contents is strictly prohibited and may be unlawful. If  
> you have received this communication in error, please notify us  
> immediately by replying to this message and deleting it from your  
> computer. Thank you.
>
> _______________________________________________
> cisco-voip mailing list
> 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/df507247/attachment.html>