>Now, the question is, are these CCM-specific fields stored in AD, or<br>>in some stripped-down Linux version of DCD?<br><br>Stored in CCM Informix DB. The CM 5.x ldap synch is one way...into callmanager. CallManager specific attributes are stored in informix and therefore, there is no dependency on AD for things such as Extension Mobility since the pin is stored on callmanager. If AD is down, the pin can still be authenticated and users can login. However, the password is from AD. I think ccmuser won't work if AD is down because callmanager proxys this request to AD.
<br><br><div><span class="gmail_quote">On 6/12/07, <b class="gmail_sendername">Jonathan Charles</b> <<a href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
OK, I tried it with a test box. I integrated with AD and made a lot of<br>CallManager-specific things to a few users. I associated a device, I<br>associated an Extension Mob device profile, I set their primary<br>extension and I added them to user groups.
<br><br>I then added a second integration to the same AD DC with ipPhone<br>instead of telephoneNumber. I performed a full synch and the data came<br>over. I then deleted the original LDAP integration.<br><br>All of the CallManager-specific things were still there... the user
<br>group, device associations, etc.<br><br>Looks like it worked like a champ.<br><br>Now, the question is, are these CCM-specific fields stored in AD, or<br>in some stripped-down Linux version of DCD?<br><br><br><br>Jonathan
<br><br>On 6/12/07, Jonathan Charles <<a href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>> wrote:<br>> I don't see how we can change any without first deleting the LDAP reference.<br>><br>> There is no way to edit the field after it has been configured (or
<br>> none that I am aware of).<br>><br>> I have now found about six ways to do this and none of them are<br>> acceptable to the customer (including changing the<br>> CorporateDirectory.txt file on the PCs)...
<br>><br>> At the end of the day, the only thing the customer will accept is the<br>> ipPhone field, but I need to do it in a way that will NOT blow out the<br>> existing user configurations (PINs, device associations and primary
<br>> extensions).<br>><br>><br>><br>> Jonathan<br>><br>> On 6/12/07, Ryan Ratliff <<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>> wrote:<br>> > You won't nuke anything by adding this value. Try setting one, kick
<br>> > off an ldap synch, and see how nothing changes.<br>> > The ipPhone attribute won't be used by default because in the LDAP<br>> > Directory configuration you can choose whether you want the CM Phone
<br>> > Number attribute to be the AD telephoneNumber or ipPhone attribute.<br>> > It looks like you can't modify the existing config, so you'll have to<br>> > copy it, change the attribute, then delete the old one.
<br>> ><br>> > So you have three options. You can create a custom directory file<br>> > (see AC documentation) and use it, get the ipPhone attribute set on<br>> > all your users with their internal extension, change the LDAP synch
<br>> > to use it, and re-synch...<br>> ><br>> > Or the final option is to mess with the directory lookup rules.<br>> > In the 4.x documentation it talks about creating directory lookup<br>> > rules via modifying the
DialRules.xml file on the server. This has<br>> > definitely changed with 5.x<br>> ><br>> > 4.x docs for directory lookup rules:<br>> > <a href="http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/">
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/</a><br>> > sys_ad/4_1_3/ccmfeat/fsccmac.htm#wp1146596<br>> ><br>> > 5.x directory lookup rules:<br>> > <a href="http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/5_0/">
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/5_0/</a><br>> > sys_ad/5_0_4/ccmcfg/b03dirlk.htm#wp79051<br>> ><br>> > -Ryan<br>> ><br>> > On Jun 11, 2007, at 5:40 PM, Jonathan Charles wrote:
<br>> ><br>> > Yeah, found it.<br>> ><br>> > But how do we change over without nuking the users out? I don't want<br>> > to have to go back and re-associate every device and create new PIN
<br>> > numbers.<br>> ><br>> ><br>> ><br>> > Jonathan<br>> ><br>> > On 6/11/07, Brian Henry <<a href="mailto:Brian.Henry@apptis.com">Brian.Henry@apptis.com</a>> wrote:<br>> > > ?
<br>> > ><br>> > ><br>> > > There is an attribute for the ipPhone field under every User Object<br>> > > in AD.<br>> > ><br>> > > Brian<br>> > ><br>> > > ________________________________
<br>> > > From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> on behalf of<br>> > > Jonathan Charles<br>> > > Sent: Mon 6/11/2007 5:18 PM<br>> > >
<br>> > > To: Patrick Diener<br>> > > Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > > Subject: Re: [cisco-voip] Repost - Attendant Console presence...<br>
> > ><br>> > ><br>> > ><br>> > ><br>> > > OK, here is an update... I know why it is broken, but don't know how<br>> > > to fix it easily.<br>> > ><br>> > > Customer is AD integrated. AD has 10-digit extensions for the
<br>> > > numbers.<br>> > > Only 4-digit on the phones.<br>> > ><br>> > > LDAP brought in numbers that don't match phone extensions.<br>> > ><br>> > > How can we fix this without modifying the AD telephone number?
<br>> > ><br>> > > Under LDAP integrations, there is a listing for an ipPHone field...<br>> > > where is this in AD?<br>> > ><br>> > ><br>> > ><br>> > > Jonathan
<br>> > ><br>> > > On 6/4/07, Patrick Diener <<a href="mailto:patrick.diener@gmail.com">patrick.diener@gmail.com</a>> wrote:<br>> > >> the SUBSCRIBE CSS is used for the new "SIP based" presence feature of
<br>> > >> 5.0 and higher (BLFs, Presence enabled Call Lists, etc...)<br>> > >> If a "normal" CSS restricts the Route Patterns where a call setup (in<br>> > >> SIP a INVITE message RFC 3261) can be routed to, the SUBSCRIBE CSS
<br>> > >> regulates from which extensions presence information can be retrieved<br>> > >> (done using the SIP SUBSCRIBE message RFC 3265). Hence if you are<br>> > >> restricted by the SUBSCRIBE CSS to send a SUBSCRIBE message to an
<br>> > >> extension no presence info can be retrieved...<br>> > >><br>> > >> if that applies at all to AC, I don't know...<br>> > >><br>> > >> Regards<br>> > >> Patrick
<br>> > >><br>> > >> On 6/4/07, Jonathan Charles <<a href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>> wrote:<br>> > >>> Ah, something new...<br>> > >>><br>
> > >>> What is a subscribe CSS???<br>> > >>><br>> > >>><br>> > >>><br>> > >>> Jonathan<br>> > >>><br>> > >>> On 6/4/07, Justin Steinberg <
<a href="mailto:jsteinberg@gmail.com">jsteinberg@gmail.com</a>> wrote:<br>> > >>>> give this a shot. for your 'ac' user, ensure that you have a<br>> > >>>> properly configured 'subscribe css' that has visibility to the
<br>> > >>>> partitions for the dn's you want to monitor.<br>> > >>>><br>> > >>>> i know the subscribe css definately plays a role with presence but<br>> > >>>> cant remember if ac needs this or not.
<br>> > >>>><br>> > >>>> justin<br>> > >>>><br>> > >>>> On 6/4/07, Jonathan Charles <<a href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>> wrote:
<br>> > >>>>> Which users, the AC users or the AC-special user?<br>> > >>>>><br>> > >>>>> Or the end-users?<br>> > >>>>><br>> > >>>>>
<br>> > >>>>><br>> > >>>>> Jonathan<br>> > >>>>><br>> > >>>>> On 6/4/07, Matt Slaga (US) <<a href="mailto:Matt.Slaga@us.didata.com">Matt.Slaga@us.didata.com
</a>> wrote:<br>> > >>>>>> AC gets it's pseudo "presence information" from the user<br>> > > accounts.<br>> > >>>>>> These accounts need to be application users, and they need the
<br>> > > CTI super<br>> > >>>>>> provider set as well. 4.x worked the same way. Call routing is<br>> > > based<br>> > >>>>>> on pilot points, user information comes from ac account being
<br>> > > associated<br>> > >>>>>> with devices.<br>> > >>>>>><br>> > >>>>>> -----Original Message-----<br>> > >>>>>> From: Jonathan Charles [mailto:
<a href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>]<br>> > >>>>>> Sent: Monday, June 04, 2007 1:24 PM<br>> > >>>>>> To: Matt Slaga (US)<br>> > >>>>>> Cc: Patrick Diener;
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > >>>>>> Subject: Re: [cisco-voip] Repost - Attendant Console presence...<br>> > >>>>>><br>> > >>>>>> Yes.
<br>> > >>>>>><br>> > >>>>>> AC works fine, except for presence.<br>> > >>>>>><br>> > >>>>>><br>> > >>>>>>
<br>> > >>>>>> Jonathan<br>> > >>>>>><br>> > >>>>>> On 6/4/07, Matt Slaga (US) <<a href="mailto:Matt.Slaga@us.didata.com">Matt.Slaga@us.didata.com
</a>> wrote:<br>> > >>>>>>> Well, did you create the pertinent users for 5.x?<br>> > >>>>>>><br>> > >>>>>>><br>> > >>>>>>
<br>> > > <a href="http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/">http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/</a><br>> > > products_ad<br>> > >>>>>>>
<br>> > > ministration_guide_chapter09186a00806b7f16.html#wp1145819<br>> > >>>>>>><br>> > >>>>>>><br>> > >>>>>>><br>> > >>>>>>> -----Original Message-----
<br>> > >>>>>>> From: Jonathan Charles [mailto:<a href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>]<br>> > >>>>>>> Sent: Monday, June 04, 2007 12:18 PM<br>> > >>>>>>> To: Matt Slaga (US)
<br>> > >>>>>>> Cc: Patrick Diener; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > >>>>>>> Subject: Re: [cisco-voip] Repost - Attendant Console
<br>> > > presence...<br>> > >>>>>>><br>> > >>>>>>> There is no DCD... it is ccm5.1.1b<br>> > >>>>>>><br>> > >>>>>>>
<br>> > >>>>>>> Jonathan<br>> > >>>>>>><br>> > >>>>>>> On 6/4/07, Matt Slaga (US) <<a href="mailto:Matt.Slaga@us.didata.com">Matt.Slaga@us.didata.com
</a>> wrote:<br>> > >>>>>>>> Check to make sure you created the "ac" user in DCD with<br>> > > password<br>> > >>>>>>> 12345.<br>> > >>>>>>>>
<br>> > >>>>>>>> -----Original Message-----<br>> > >>>>>>>> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>> > >>>>>>>> [mailto:
<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]<br>> > > On Behalf Of Jonathan<br>> > >>>>>>>> Charles<br>> > >>>>>>>> Sent: Monday, June 04, 2007 11:19 AM
<br>> > >>>>>>>> To: Patrick Diener<br>> > >>>>>>>> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > >>>>>>>> Subject: Re: [cisco-voip] Repost - Attendant Console
<br>> > > presence...<br>> > >>>>>>>><br>> > >>>>>>>> Yeah...<br>> > >>>>>>>><br>> > >>>>>>>> AC works fine... except for this... someone suggested the
<br>> > > Windows<br>> > >>>>>> FW,<br>> > >>>>>>>> but it is disabled... someone else suggested disabling their<br>> > > AV...<br>> > >>>>>> but
<br>> > >>>>>>>> I haven't tried it yet.<br>> > >>>>>>>><br>> > >>>>>>>><br>> > >>>>>>>> Jonathan
<br>> > >>>>>>>><br>> > >>>>>>>> On 6/4/07, Patrick Diener <<a href="mailto:patrick.diener@gmail.com">patrick.diener@gmail.com</a>> wrote:<br>> > >>>>>>>>> I suppose CTI Manager Service and the CTI User and Password
<br>> > > that<br>> > >>>>>> is<br>> > >>>>>>>>> used by the TCD service has been checked...<br>> > >>>>>>>>><br>> > >>>>>>>>> and the AC Application has been downloaded from the
<br>> > > currently<br>> > >>>>>>> running<br>> > >>>>>>>>> CCM Version...<br>> > >>>>>>>>><br>> > >>>>>>>>> Regards
<br>> > >>>>>>>>> Patrick<br>> > >>>>>>>>><br>> > >>>>>>>>> On 6/4/07, Jonathan Charles <<a href="mailto:jonvoip@gmail.com">
jonvoip@gmail.com</a>> wrote:<br>> > >>>>>>>>>> OK, so, we have installed attendant console on four<br>> > > different<br>> > >>>>>> PCs,<br>> > >>>>>>>> no
<br>> > >>>>>>>>>> hunt groups, just a user with AC and the main number on<br>> > > her<br>> > >>>>>>> phone...<br>> > >>>>>>>>>> she routes the calls where they need to go...
<br>> > >>>>>>>>>><br>> > >>>>>>>>>> For speed dials and the directory we just have the<br>> > > question-mark<br>> > >>>>>>> of
<br>> > >>>>>>>> doom...<br>> > >>>>>>>>>><br>> > >>>>>>>>>> How do we get presence to work?<br>> > >>>>>>>>>>
<br>> > >>>>>>>>>> I have tried all of the previous suggestions... setting<br>> > > the<br>> > >>>>>>>> interface,<br>> > >>>>>>>>>> etc. No luck...
<br>> > >>>>>>>>>><br>> > >>>>>>>>>> Call Control is up, the user is online... I have no idea<br>> > > why<br>> > >>>>>> this
<br>> > >>>>>>>> doesn't work.<br>> > >>>>>>>>>><br>> > >>>>>>>>>><br>> > >>>>>>>>>>
<br>> > >>>>>>>>>> Jonathan<br>> > >>>>>>>>>><br>> > > _______________________________________________<br>> > >>>>>>>>>> cisco-voip mailing list
<br>> > >>>>>>>>>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > >>>>>>>>>><br>> > > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">
https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>> > >>>>>>>>>><br>> > >>>>>>>>><br>> > > _______________________________________________
<br>> > >>>>>>>>> cisco-voip mailing list<br>> > >>>>>>>>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > >>>>>>>>>
<br>> > > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>> > >>>>>>>>><br>> > >>>>>>>>
<br>> > > _______________________________________________<br>> > >>>>>>>> cisco-voip mailing list<br>> > >>>>>>>> <a href="mailto:cisco-voip@puck.nether.net">
cisco-voip@puck.nether.net</a><br>> > >>>>>>>><br>> > > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>> > >>>>>>>>
<br>> > >>>>>>>> -----------------------------------------<br>> > >>>>>>>> Disclaimer:<br>> > >>>>>>>><br>> > >>>>>>>> This e-mail communication and any attachments may contain
<br>> > >>>>>>>> confidential and privileged information and is for use by the<br>> > >>>>>>>> designated addressee(s) named above only. If you are not the<br>> > >>>>>>>> intended addressee, you are hereby notified that you have
<br>> > > received<br>> > >>>>>>>> this communication in error and that any use or reproduction<br>> > > of<br>> > >>>>>>>> this email or its contents is strictly prohibited and may be
<br>> > >>>>>>>> unlawful. If you have received this communication in error,<br>> > > please<br>> > >>>>>>>> notify us immediately by replying to this message and
<br>> > > deleting it<br>> > >>>>>>>> from your computer. Thank you.<br>> > >>>>>>>><br>> > >>>>>>><br>> > >>>>>>> -----------------------------------------
<br>> > >>>>>>> Disclaimer:<br>> > >>>>>>><br>> > >>>>>>> This e-mail communication and any attachments may contain<br>> > >>>>>>> confidential and privileged information and is for use by the
<br>> > >>>>>>> designated addressee(s) named above only. If you are not the<br>> > >>>>>>> intended addressee, you are hereby notified that you have<br>> > > received
<br>> > >>>>>>> this communication in error and that any use or reproduction of<br>> > >>>>>>> this email or its contents is strictly prohibited and may be<br>> > >>>>>>> unlawful. If you have received this communication in error,
<br>> > > please<br>> > >>>>>>> notify us immediately by replying to this message and deleting<br>> > > it<br>> > >>>>>>> from your computer. Thank you.
<br>> > >>>>>>><br>> > >>>>>><br>> > >>>>>> -----------------------------------------<br>> > >>>>>> Disclaimer:<br>> > >>>>>>
<br>> > >>>>>> This e-mail communication and any attachments may contain<br>> > >>>>>> confidential and privileged information and is for use by the<br>> > >>>>>> designated addressee(s) named above only. If you are not the
<br>> > >>>>>> intended addressee, you are hereby notified that you have<br>> > > received<br>> > >>>>>> this communication in error and that any use or reproduction of
<br>> > >>>>>> this email or its contents is strictly prohibited and may be<br>> > >>>>>> unlawful. If you have received this communication in error,<br>> > > please
<br>> > >>>>>> notify us immediately by replying to this message and deleting it<br>> > >>>>>> from your computer. Thank you.<br>> > >>>>>><br>> > >>>>> _______________________________________________
<br>> > >>>>> cisco-voip mailing list<br>> > >>>>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > >>>>><br>> > > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">
https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>> > >>>>><br>> > >>>><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">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><br>> > >>><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">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>> > >><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">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><br>> > ><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">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>> ><br>><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">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></blockquote></div><br>