User with Jabber iPad + Jabber Windows

[bastienbertout]

Hi,

Is it possible to have a functional directory config for a user having 2 jabber devices : 1 JFW + 1 Jabber iPad in 9.6 release ?

- UDS does not seem to work well

- JFW uses EDI does not seem to work with BDI

- Jabber for iPad uses BDI and does not seem to worki with EDI

Thanx,

Regards,

Bastien.

[Kevin kamau]

Facing this same problem too...How to go about it??

[Amit Kumar]

Jabber for windows 9.7 now supports UDS directory resolution like Jabber for iPad/iPhone 9.6. Please refer to the following link which confirms the same;

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/JABW_BK_CF8F083D_00_cisco-jabber-for-windows-97/JABW_BK_CF8F083D_00_cisco-jabber-for-windows-97_chapter_00.html#JABW_RF_N17BA9CE_00

Please refer to the following snippet;

UDS On-Premises Directory Integration

Cisco Jabber for Windows now supports Cisco Unified Communications Manager User Data Service. This means that you can deploy approximately 50 percent of the maximum number of Cisco Jabber clients that your Cisco Unified Communications Manager node supports. For information about configuring UDS for directory integration, see the Directory Integration chapter of the Installation and Configuration Guide.

-> Also you will need to refer to the following information for Jabber for windows 9.7 UDS requirements; please check the following link;

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/JABW_BK_C4C679C9_00_cisco-jabber-for-windows-97/JABW_BK_C4C679C9_00_cisco-jabber-for-windows-97_chapter_01.html#JABW_RF_DC70A650_00

Cisco Unified Communications Manager User Data Service
Cisco Jabber supports UDS using the following Cisco Unified Communications Manager versions:
Cisco Unified Communications Manager version 9.1(2) or later with the following COP file: cmterm-cucm-uds-912-5.cop.sgn.
Cisco Unified Communications Manager version 10.0(1). No COP file is required.

- please rate if this helps.

[Kevin kamau]

Iam using CUCM 9.1(2) , that means I need to download the cmterm-cucm-uds-912-5.cop.sgn?

Can I use one jabber-config file to support all cllients;jabber for windows 9.7,jabber for ipad 9.6 and jabber for iphone 9.6 for Mobile  Remote Access?

Currently Iam using EDI and its only working well for Jabber for Windows but directory doesnt work on ipad and iphone. But when using BDI it works on the ipad&iphone only. Still on-premise.

[Amit Kumar]

-> EDI and BDI config can co exist on the same jabber-config.xml with two directory enclosures.

<Directory>

  < DirectoryServerType>EDI< /DirectoryServerType>

      ........

</Directory>

<Directory>

< DirectoryServerType>BDI< /DirectoryServerType>

</Directory>

-> To make it just with UDS one config of Directory will cover all clients, ofcourse there would chances to do a bit of troubleshooting though it should work.

i hope this clarifies the query.

[Kevin kamau]

I have out my jabber-config.xml file below. Only Jabber for Windows clients seem to be searching contacts but jabber for iphone and jabber for ipad

cannot lookup contacts.

Dont know if you can point me out to where am going wrong.

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
<Directory>
   <PresenceDomain>xxx.xxx</PresenceDomain>
   <DirectoryServerType>EDI</DirectoryServerType>
   <PrimaryServerName>192.168.37.219</PrimaryServerName>
   <ServerPort1>3268</ServerPort1>
   <UseSSL>0</UseSSL>
   <UseSecureConnection>0</UseSecureConnection>
   <UseWindowsCredentials>0</UseWindowsCredentials>
   <ConnectionUsername>Administrator@xxx.xxx</ConnectionUsername>
   <ConnectionPassword>C0mput@r5</ConnectionPassword>
   <SipUri>mail</SipUri>
   <BaseFilter>(&amp;(objectCategory=person))</BaseFilter>
   <SearchBase1>ou=xxx,dc=xxx,dc=xxx,dc=xxx</SearchBase1>
   <SearchBase2>ou=xxx,dc=xxx,dc=xxx,dc=xxx</SearchBase2>
   <SearchBase3>ou=xxx,dc=xxx,dc=xxx,dc=xxx</SearchBase3>
   <SearchBase4>ou=xxx,dc=xxx,dc=xxx,dc=xxx</SearchBase4>
   <SearchBase5>ou=xxx,dc=xxx,dc=xxx,dc=xxx</SearchBase5>
</Directory>
<Directory>
   <DirectoryServerType>BDI</DirectoryServerType>
   <BDILDAPServerType>AD</BDILDAPServerType>
   <BDIPrimaryServerName>192.168.37.219</BDIPrimaryServerName>
   <BDIPresenceDomain>xxx.xxx</BDIPresenceDomain>
   <BDIServerPort1>3268</BDIServerPort1>
   <BDIConnectionUsername>Administrator@xxx.xxx</BDIConnectionUsername>
   <BDIConnectionPassword>C0mput@r5</BDIConnectionPassword>
   <BDIBaseFilter>(&amp;(objectClass=inetOrgPerson)</BDIBaseFilter>
   <BDISearchBase1>xxx,dc=xxx,dc=xxx,dc=xxx</BDISearchBase1>
</Directory>
<Policies>
    <EnableSIPURIDialling>true</EnableSIPURIDialling>
</Policies>
</config>