Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Jabber Config File - Directory methods

hi

with Jabber 9.5 for iphone using the BDI method but windows still supporting EDI or UDS can I have one config file that serves both?

I did try this with BDI info at the top and UDS at the bottom in seperate dir tags but half the features are not picked up (like photo) on the windows 9.2-6 client

  • Jabber Clients
3 ACCEPTED SOLUTIONS

Accepted Solutions
New Member

Jabber Config File - Directory methods

My problem as well.  It is crazy to think that you have everything working with Global jabber-config then you introduce Jabber for iPhone and you then have to decide do you want your enterprise users with Windows to work or do you want you iPhone users to work.  Pick one, but not both.

The function of different Jabber clients and where they get (TFTP, LDAP, VoiceMail, Search Base, LDAP login credentials, how to login username or UPN) is bordering on insanity.  What is Cisco thinking?  To add to this confusion there is no one document that explains exactly where each client gets all these parameters.  It is hard to work through this in a lab much less a customer.

Stop IT!!!

Cisco Employee

Jabber Config File - Directory methods

Hi Ian,

The jabber-config.xml can only have one instance of the key.  This means can't have both UDS and EDI/BDI in the same file.    If you have multiple instances of a key in the file is will only read the first instance and ignore and further entries.   

Windows 9.2 now only provides limited support for UDS and will only support up to 200 users.    We recommend that on premise deployments are configured to use LDAP where possible.  Jabber for Windows 9.6 does remove support for UDS but based on customer feedback we are looking to see if we can bring UDS support back into the product.

Bryan

Cisco Employee

Jabber Config File - Directory methods

Hi,

The global jabber-config.xml does work across clients.   You can't have a mix of UDS and LDAP in the same file but we would recommend not mixing contact sources.     With the Jabber 9.6 releases you will see much more alignment across the clients on how they pick up this information.

Bryan

4 REPLIES
New Member

Jabber Config File - Directory methods

My problem as well.  It is crazy to think that you have everything working with Global jabber-config then you introduce Jabber for iPhone and you then have to decide do you want your enterprise users with Windows to work or do you want you iPhone users to work.  Pick one, but not both.

The function of different Jabber clients and where they get (TFTP, LDAP, VoiceMail, Search Base, LDAP login credentials, how to login username or UPN) is bordering on insanity.  What is Cisco thinking?  To add to this confusion there is no one document that explains exactly where each client gets all these parameters.  It is hard to work through this in a lab much less a customer.

Stop IT!!!

Cisco Employee

Jabber Config File - Directory methods

Hi,

The global jabber-config.xml does work across clients.   You can't have a mix of UDS and LDAP in the same file but we would recommend not mixing contact sources.     With the Jabber 9.6 releases you will see much more alignment across the clients on how they pick up this information.

Bryan

New Member

Jabber Config File - Directory methods

the issue right now is how do I support jabber for windows 9.3 and jabber for iphone 9.5 in the same file - one needs EDI and the other needs BDI

jabber for ipad still uses the LDAP profile configured in CUPS

Cisco Employee

Jabber Config File - Directory methods

Hi Ian,

The jabber-config.xml can only have one instance of the key.  This means can't have both UDS and EDI/BDI in the same file.    If you have multiple instances of a key in the file is will only read the first instance and ignore and further entries.   

Windows 9.2 now only provides limited support for UDS and will only support up to 200 users.    We recommend that on premise deployments are configured to use LDAP where possible.  Jabber for Windows 9.6 does remove support for UDS but based on customer feedback we are looking to see if we can bring UDS support back into the product.

Bryan

1621
Views
20
Helpful
4
Replies