unable to add the directory group in Jabber

[Rajkumar Yadav]

Hi,

I'm trying to add the distribution group in Cisco Jabber 11.6.2 and CUCM & IMP 11.5

Getting error as " the directory group does not exist", Although it is available and can be searched in Jabber itself.

Attached is the snapshot error.

Regards,

Raaj

[Jonathan Schulenberg]

Is Jabber using UDS or EDI? It's possible that the group shows up in search results if using EDI as the ADSI API on Windows doesn't have the same restrictions as Jabber/IM&P itself.

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_6/cjab_b_feature-configuration-for-cisco-jabber/cjab_b_feature-configuration-for-cisco-jabber_chapter_00.html#CJAB_RF_E8C70BC6_00

One other basic thing to check: the LDAP Sync agreement is set to include groups and that group is within the Search Base, correct?

Also, there are mentions of special character restrictions. Are you able to add a group that doesn't include the underscore characters shown in your screenshots?

[Rajkumar Yadav]

Hi Jonathan,

We are using the EDI method and this laptop is part of domain.

LDAP sync is set to users and group with search base as root OU of the AD

we have filter applied  as (&(objectclass=user)(!(objectclass=Computer))(ipPhone=*))

Still we are not able to add the distribution group.

I'm checking the option of adding a group without _character and this need to be created in AD as client have syntax to add it.

Regards,

Raaj

[Jaime Valencia]

Do you see them under user groups in CUCM and do they show up properly populated?

[Rajkumar Yadav]

Hi Jaime,

I don't see the exact group, it shows the username followed by OU details.

I can share the snapshot tomorrow.

Regards,

Raaj

[Rajkumar Yadav]

Hi,

I was able to resolve this, however it won't be scalable solution.

I was having only one sync agreement with user and group, where the search base was directly pointing to  rout OU.

Now my all distribution group were under the OU=Group and this group OU was under Root OU

So the User group in CUCM was coming as "_BPM,OU=Group" and actually the group name in AD was just _BPM, so there was mismatch.

To avoid this mismatch i modified the first sync agreement to sync only user and added another sync agreement for group with search base  OU=Groups,DC=Root,DC=Global

Once I added this and synced then group name in CUCM came as _BPM and i was able to add it to jabber.

Now if in case there multiple OU under Root OU were distribution group are created then it requires separate sync agreement for each Group OU which is weird.

If anyone has better option, do please let me know.

Regards,

Raaj 

[Trad Tobaishat]

What you are hitting is new Defect on CUCM 11.5 I guess. CUCM 11.0 works fine.