<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<title>RE: [cisco-voip] UserID when syncing via ldap.. Removing certain
characters?</title>
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;}
span.EmailStyle20
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Mark,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>There is no way, that I can see, to change the LDAP directory
integration fields without deleting the old ones and recreating them.
Even then, there are only three fields that can be manipulated. Those are
the TN and Middle name fields. As for the deletion of users, I believe
that is a batched job that occurs after a set period of time, something like a
day. So it won't just delete all your users immediately. I have
tested the device association part a couple of times internally and have not
lost any device associtations, so I think you're okay there.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I verified in the admin guide for 6.0 (1) that those options
exist. I'm sure the timeout value for the deletion cycle is listed there
as well. Since you went through the trouble of doing LDAP
synchronization, why not just authenticate your users against it too?
Assuming your managing the AD and phone system, it's one less password to
manage at the end of the day.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>-ryan<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>MILLS, Mark<br>
<b>Sent:</b> Friday, April 04, 2008 5:56 PM<br>
<b>To:</b> Ryan Ratliff<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] UserID when syncing via ldap.. Removing
certain characters?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p style='margin-bottom:12.0pt'><span style='font-size:10.0pt'>Hi,<br>
<br>
I actually thought of that, but it seems I would need to delete the current
ldap directory intergration, and configure a new intergration, as you cant just
change the field. I am also not sure if its possible with CM6.0.1, as I
couldnt see ipPhone as an ldap attribute option in my CM 6.0.1 system?<br>
<br>
If I do this all the current end users will be deleted. When it syncs again and
the users are imported using the different ldap attribute, will CM be smart
enough to recognise the users and keep the same settings, or will they need
their device profiles and passwords etc reconfigured?<br>
<br>
Thanks,<br>
Mark<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Ryan Ratliff [<a href="mailto:rratliff@cisco.com">mailto:rratliff@cisco.com</a>]<br>
Sent: Sat 4/5/2008 12:07 AM<br>
To: MILLS, Mark<br>
Cc: cisco-voip@puck.nether.net<br>
Subject: Re: [cisco-voip] UserID when syncing via ldap.. Removing certain
characters?<br>
<br>
Not that I'm aware of. Would it be possible to populate the IPPhone <br>
attribute for your users with the number you wish CM to use and then <br>
map that attribute instead of telephoneNumber?<br>
<br>
-Ryan<br>
<br>
On Apr 4, 2008, at 1:07 AM, MILLS, Mark wrote:<br>
<br>
Hi,<br>
<br>
We are doing Active Directory syncing for CallManager 6 users.<br>
<br>
We use the telephoneNumber ldap attribute to map to the User ID field in<br>
CCM, but in AD want to use the full international format such as<br>
"+61(0)884807702" for numbers.<br>
<br>
This is obviously a bit horrible for users to enter via their phone, is<br>
there any way possible that we can have it selectively strip out the<br>
+61(0) part of the number when creating the synced User ID's??? Ie,
so<br>
the login for the above number would actually be 884807702 ?<br>
<br>
I have had a hunt around, and cant seem to find anything about doing<br>
this, so I am assuming its not possible? :(<br>
<br>
Thanks,<br>
Mark<br>
"Warning:<br>
The information contained in this email and any attached files is<br>
confidential to BAE Systems Australia. If you are not the intended<br>
recipient, any use, disclosure or copying of this email or any<br>
attachments is expressly prohibited. If you have received this email<br>
in error, please notify us immediately. VIRUS: Every care has been<br>
taken to ensure this email and its attachments are virus free,<br>
however, any loss or damage incurred in using this email is not the<br>
sender's responsibility. It is your responsibility to ensure virus<br>
checks are completed before installing any data sent in this email to<br>
your computer."<br>
<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
</span><o:p></o:p></p>
<pre>"Warning:<o:p></o:p></pre><pre>The information contained in this email and any attached files is<o:p></o:p></pre><pre>confidential to BAE Systems Australia. If you are not the intended<o:p></o:p></pre><pre>recipient, any use, disclosure or copying of this email or any<o:p></o:p></pre><pre>attachments is expressly prohibited. If you have received this email<o:p></o:p></pre><pre>in error, please notify us immediately. VIRUS: Every care has been<o:p></o:p></pre><pre>taken to ensure this email and its attachments are virus free,<o:p></o:p></pre><pre>however, any loss or damage incurred in using this email is not the<o:p></o:p></pre><pre>sender's responsibility. It is your responsibility to ensure virus<o:p></o:p></pre><pre>checks are completed before installing any data sent in this email to<o:p></o:p></pre><pre>your computer."<o:p></o:p></pre><pre><o:p> </o:p></pre></div>
</body>
</html>