other option is to use the ip phone number and map to your extensions and leave telephone number the full format.<div><br></div><div>Scott<br><br><div class="gmail_quote">On Thu, Feb 18, 2010 at 12:42 PM, Mark Marquez <span dir="ltr"><<a href="mailto:MMarquez@goldsys.com">MMarquez@goldsys.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal">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.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
</div>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>