LDAP synchronization physicalDeliveryOfficeName attribute

Version 1
    This document was generated from CDN thread

    Created by: Shivinder Singh on 13-11-2012 02:24:23 PM
    We have Callmanager 8.0. Cisco DirSync service is enabled and our LDAP source is Microsoft Active Directory. Is it possible to add a new LDAP field to the list of fields that are synchronized? For instance there is a column called building in the enduser table in the informix backend database, but its empty for all end users. We would like to use the physicalDeliveryOfficeName LDAP attribute to populate that.

    Subject: RE: LDAP synchronization physicalDeliveryOfficeName attribute
    Replied by: Shivinder Singh on 30-11-2012 01:19:06 PM
    Is this the wrong forum, or this is not possible? Annnyyy ideas?

    Subject: RE: LDAP synchronization physicalDeliveryOfficeName attribute
    Replied by: David Staudt on 04-12-2012 09:48:48 AM
    UCM 9.0 introduced this capability via the 'addLdapSyncCustomField' request (corresponding UI in the UCM admin LDAP config pages.)  Prior to that, it is not possible to customize the fields for syncing.

    Subject: RE: LDAP synchronization physicalDeliveryOfficeName attribute
    Replied by: Enda McManemy on 04-12-2012 11:41:51 AM
    David Staudt:
    UCM 9.0 introduced this capability via the 'addLdapSyncCustomField' request (corresponding UI in the UCM admin LDAP config pages.)  Prior to that, it is not possible to customize the fields for syncing.

     
    Hi David,
     
    What triggers the sync event from LDAP to CUCM. Is their an optimum way to do this.
    Is it feasible to trigger this once every hour or would this have performace impacts on CUCM?
     
    Thanks
    Enda

    Subject: RE: LDAP synchronization physicalDeliveryOfficeName attribute
    Replied by: David Staudt on 04-12-2012 05:06:26 PM
    Normally LDAP sync occurs on a schedule (every 1 to 7 days...at midnight..?)  It is possible to trigger an immediate LDAP sync from the UCM admin pages, or via AXL 'doLdapSync' request (UCM 8.0+)
    Typically LDAP sync is configured because the number of users is large and unwieldy enough to require a dedicated directory system.  Therefore it is quite possible that a sync could have a performance impact, and doing so hourly (or indeed, during business hours) might need to be avoided.  Probably only careful testing (best done in vivo) can give you a complete understanding of the impact.
     
     

    Subject: RE: LDAP synchronization physicalDeliveryOfficeName attribute
    Replied by: Enda McManemy on 05-12-2012 03:31:55 AM
    David Staudt:
    Normally LDAP sync occurs on a schedule (every 1 to 7 days...at midnight..?)  It is possible to trigger an immediate LDAP sync from the UCM admin pages, or via AXL 'doLdapSync' request (UCM 8.0+)
    Typically LDAP sync is configured because the number of users is large and unwieldy enough to require a dedicated directory system.  Therefore it is quite possible that a sync could have a performance impact, and doing so hourly (or indeed, during business hours) might need to be avoided.  Probably only careful testing (best done in vivo) can give you a complete understanding of the impact.
     
     

     
    Thanks for the feedback David. Have Cisco any plans to provide a mechanism that will allow newly added users in AD to be synched to CUCM on an adhoc basis as opposed to needing to sync all users. This mechanism could be utilized throughout the working day and a nightly job could sync the full AD repo with CUCM.

    Subject: RE: LDAP synchronization physicalDeliveryOfficeName attribute
    Replied by: David Staudt on 05-12-2012 09:50:00 AM
    Not aware of anything immediately forthcoming, but my visibility is incomplete in that area.