IM&P > Presence > Settings > Advanced Settings change IM to email warning?
This screenshot below/attached worries me. New Deployment of IM&P 10.0.1 with Jabber for Windows 9.7.1 Under Presence > Advanced Settings if I change the IM address I get a pop-up warning about “All clients must be capable of supporting Directory URI as IM Address Scheme. Do not change this setting if you have any clients that do not support the new address scheme”
Basically our sAMAccountName is short name, and our Chat IM Address we want to be email based, and our CUCM LDAP Directory > Directory URI = email
Are any new Jabber clients not capable of supporting Directory URI as the IM Address? Eg Jabber for iPhone/iPad/Mac/Android/Blackberry ? I assume this message is for older software versions?
I have an problem with outlook the proxyaddress have multidomain, therefore the presence outlook is false, my solution is upgrade cucm and IM&Presence to version 10.5, this support mutidomain with IM address URI, but the cisco tac,currently no Jabber clients support directory URI address scheme, this is true?
Here is an extract from the installation guide for IM&P:
If you configure the node to use Directory URI as the IM address scheme, Cisco recommends that you deploy only clients that support Directory URI. Any client that does not support Directory URI will not work if the Directory URI IM address scheme is enabled. Cisco recommends that you use the UserID@Default_Domain IM address scheme and not the Directory URI IM address scheme if you have any deployed clients that do not support Directory URI.
If I am not wrong the latest versions of Jabber do support Directory URI as the IM Address.
Below you'll find the documentation that I mentioned before:
Flexible Jabber ID—Cisco Jabber 10.6 supports multiple presence domain architecture models for on premises deployments when the domains are on the same presence architecture, for example users in example-us.com and example-uk.com.
To support multi domain models, all components of the deployment require the following versions:
Cisco Unified Communications IM and Presence server nodes and call control nodes version 10.x or later.
All Cisco Jabber clients on Windows, Mac, IOS and Android version 10.6 or later.
Only deploy Cisco Jabber with multiple domain architecture in the following scenarios:
Cisco Jabber 10.6 or later is deployed as a new installation to all users in your organization on all platforms (Windows, Mac, IOS and Android, including Android based IP Phones such as the DX series).
Before making any domain or IM address changes on the presence server, Cisco Jabber is upgraded to version 10.6 or later for all users on all platforms (Windows, Mac, IOS and Android, including Android based IP Phones such as the DX series).
When setting up Cisco Jabber the Jabber ID that identifies the users can be mapped to the Directory URI field on Cisco Unified Communications Manager. This allows Cisco Jabber to identify the users by their AD mail attribute or the AD msRTCSIP-primaryuseraddress attribute. A user can log into Cisco Jabber with their sAMAccountName attribute, while the Jabber ID is mapped to the Directory URI field. For more information see the IM Address Scheme section in the Cisco Jabber 10.6 Deployment and Installation Guide.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...