<div dir="ltr">The big thing here is that most companies use the telephoneNumber for their internal corporate directory (web page...) which means it screws with the phone corporate directory and attendant console, unless you use translation patterns and application dial rules, which can be a pain to implement without experience.<br>
<br><br>Jonathan<br><br><div class="gmail_quote">On Mon, Sep 15, 2008 at 10:26 AM, Ryan West <span dir="ltr"><<a href="mailto:rwest@zyedge.com">rwest@zyedge.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Just to build on this, if you already have the full e. 164
number in AD, it's pretty easy to create a script to populate the ipPhone
field. I agree with Jonathan, I think that's the best way to go about doing
it. Users with mobile devices can still do a directory lookup against AD if
you separate the two.</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">-ryan</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;">
<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On
Behalf Of </b>Jonathan Charles<br>
<b>Sent:</b> Monday, September 15, 2008 11:02 AM<br>
<b>To:</b> STEVEN CASPER<br>
<b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] Cisco Unified Communications and Active
Directory</span></p>
</div><div><div></div><div class="Wj3C7c">
<p> </p>
<div>
<p style="margin-bottom: 12pt;">Your big thing for AD
integration is two fields in AD, telephoneNumber and ipPhone.<br>
<br>
I would make sure you populate ipPhone with their 4 (or 5) digit IP Phone
extension and populate telephoneNumber with their full e.164.<br>
<br>
Then integrate CCM to AD using the ipPhone field.<br>
<br>
CCM, Presence, MPX, can integrate (thru CCM) to AD.<br>
<br>
Unity UM will integrate to AD and Exchange/Notes (Notes sux).<br>
<br>
<br>
Jonathan</p>
<div>
<p>On Mon, Sep 15, 2008 at 9:31 AM, STEVEN CASPER <<a href="mailto:SCASPER@mtb.com" target="_blank">SCASPER@mtb.com</a>> wrote:</p>
<div style="margin: 3pt 3pt 0.75pt; font-size-adjust: none; font-stretch: normal;">
<div>
<p><span style="font-size: 10pt;"> I
have been asked an interesting question and thought I would pose it to the
group:</span></p>
</div>
<div>
<p><span style="font-size: 10pt;"> </span></p>
</div>
<div>
<p><span style="font-size: 10pt;"> "What
opportunities exist for the Cisco Unified Communications environment
when presented with a green field Active Directory
2008 implementation".</span></p>
</div>
<div>
<p><span style="font-size: 10pt;"> </span></p>
</div>
<div>
<p><span style="font-size: 10pt;"> Assuming
CUCM 6/7, CUPs 6.x, CUPC, and either Unity 7.x or Connections 7.x -
I would hope to see us using a common user directory across all of
our Unified Communications products - Call Manager, Unity/Connections,
Unified Office Communicator and Presence. I would also hope that we could use
the AD domain for user authentication across these products with single sign on
capability. </span></p>
</div>
<div>
<p><span style="font-size: 10pt;"> </span></p>
</div>
<div>
<p><span style="font-size: 10pt;">So
what am I missing?</span></p>
</div>
<div>
<p><span style="font-size: 10pt;"> </span></p>
</div>
<div>
<p><span style="font-size: 10pt;">Thanks
for any feedback,</span></p>
</div>
<div>
<p><span style="font-size: 10pt;"> </span></p>
</div>
<div>
<p><span style="font-size: 10pt;">Steve</span></p>
</div>
<pre>************************************</pre><pre>This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.</pre>
<pre>There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.</pre>
<pre>************************************</pre></div>
<p style="margin-bottom: 12pt;"><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">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></p>
</div>
<p> </p>
</div>
</div></div></div>
</div>
</blockquote></div><br></div>