Unity Connection 8.6 integration with CUCM 8.6 and LDAP

[fuhrersk8]

                   Hello guys!

     I am tryng to better understand how does the Unity Connection (version 8.6) manages Users when integrated with CUCM and LDAP. In my scenario the CUCM and CUCxN are both integrated with LDAP and both are populating their databases with LDAP Users. Also, the CUCM and CUCxN are integrated through SCCP integration. I know that Userid and password (password for Jabber , password for Voicemail Server Account on Jabber and Web App on Unity) are pulled from the LDAP database. Also, the PIN for Voicemail should be pulled from CUCM PIN on End User config or CUCxN PIN on User Voicemail password config.

My questions are the follwoing:

1. How does the Unity knows wich users should have mailbox if its getting Users from LDAP?

2. Does Unity is supposed to Synch with CUCM for User information like primary extension, etc.?

3. Wich PIN has precedence, PIN configured at CUCM or PIN configured at CUCxN for Voicemail? Also, if PIN is changed on End User at CUCM, it should synch and change the PIN for the User at CUCxN?

Thanks in advanced for your help and support!

[Chris Deren · Accepted solution]

PIN is not pulled from CUCM, PIN is local to UCXN database.  Only passwords are synched with LDAP.

You can integrate UCXN with CUCM via AXL, but that does not integrate PINs either (i dont think) and this is not recommended as then your passwords would have to be local to UCXN database.

Users/Mailboxes are not automatically created in UCXN by integrating with either solution, you still need to import the user either from LDAP, CUCM or build a local one.

HTH,

Chris

[fuhrersk8]

Thanks Chris for the information. But if Users are imported from LDAP into CUCxN, does is still necessary to configure the primary extension on the End User config page in the CUCM?

Thanks again!

[Steve Snodgrass]

If you have phone numbers in the LDAP directory, you can create a phone number conversion rule (under the LDAP section) that will automatically populate the extension field for each user.

[Chris Deren]

Correct, the issue with phone number conversion rule is that you can only have one of those.

When you import the user depending on your LDAP integration field mapping it will bring in either the telephoneNumber of ipPhone filed and if it needs to be entered differently or it is not filled out you enter the desired extension during the import.

HTH,

Chirs

[fuhrersk8]

Excellent, thanks both for the good information!