04-27-2016 12:37 AM - edited 03-17-2019 06:04 PM
Hello,
Recently I installed presence 10.5.2 for the first time. Before that I had my Jabber for Iphone and Windows registered without presence to CUCM as softphone. So when I added presence to the cluster, only thing I had to do is "Asign Presence Users" and on each end user "Enable User for Unified CM IM and Presence". And only with that I had my users set on presence, able to watch each other's presence status and sending IM.
No trunks were required and none of the configuration steps that were necessary before with previous CUCM/presence when the CUCP/Jabber was connected to CUCM through Presence. I am aware that this is minimal configuration and that for any additional integration with unity conn, chatrooms and what not additional steps would be necessary. But for the minimal config to make it work this was enough.
SO my question is, what is the approach for this? Register jabber to CUCM or to presence? what is really the difference? Is Cisco leaning towards registering jabbers directly to CUCM? What motivation would I have to register them old-fashionly through Presence (except enjoying huge number of configuration steps)?
thanks for any clarification or thoughts on this
Goran
04-27-2016 02:25 AM
Hi Goran,
I think the answer lies in the IM&P product info page:
http://www.cisco.com/c/en/us/products/unified-communications/unified-presence/index.html
Cisco Unified Presence technology has been integrated with Cisco Unified Communications Manager for Release 9.0 and later. All the features and capabilities of Cisco Unified Presence 8.6 are now part of the Cisco Unified Communications Manager.
With this integral component of the Cisco Unified Communications system, you can:
Manish
04-27-2016 03:40 AM
Hi Manish,
Tnx so much for your answer. Are you saying that from version 9.0->, registration of jabber through Presence is not the way of doing it anymore? That jabber should be connected directly to CUCM?
In that sense, on jabber, when signing in through advanced settings (where I can choose automatic, webex messenger, IM&Presence, CUCM8 or CUCM9), I shouldn't - mustn't - couldn't choose IM&Presence?
also , does this make DNS SRV record _cuplogin._tcp.example.com obsolete?
My question is: is with >9.X versions the only way of registering jabber directly through CUCM, or can it still be done through Presence and what is the practical difference?
Tnx again
04-27-2016 03:04 PM
I am going to give it a shoot here (Jabber Login). It varies depending on deployment model
Condition:
CUCM (9.x or above) is LDAP Authenticated with IM&P cluster (No Phone-Only), No SSO, with DNS SRV "_cisco-uds._tcp.<domain> pointing to CUCM, No MRA (Mobile Remote Access) and Jabber set to "Automatic":
Now, _cuplogin is still available as a backup mechanism for some flavors of Jabber, but not advised for CUCM 9.x above. Because with _cuplogin Jabber will directly contact IM&P for auth without talking to CUCM First for service profile information (IM&P Database does have a copy of cucm service profile).
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide