[cisco-voip] Why would Jabber for Windows and CUPC clients not be able to use IM?

[Jeffrey Girard]

I have also discovered that I am unable to manually enter an IM address into the contact details - both on CUPC and on Jabber.  The boxes are greyed out and not available for me to manually enter an IM address.

Are LDAP and DNS "required" to provide the necessary infrastructure to support Jabber IM?

------------------------------------------------------------------------------------
Dr. Jeffrey T. Girard (Jeff), PhD
Colonel, United States Army (Retired)
Senior Network Engineer / VoIP Engineer - WireMeHappy.com
reply to: jeffrey.girard at wiremehappy.com<mailto:jeffrey.girard at wiremehappy.com>
(607)835-0406 (home office)
(845)764-1661 (mobile)
(607)835-0458 (fax)

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jeffrey Girard
Sent: Wednesday, July 02, 2014 8:19 AM
To: Matthew Loraditch; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Why would Jabber for Windows and CUPC clients not be able to use IM?

Matthew -
          Thanks for the response.

          Yes, checked and confirmed that each user has the UC Service Profile and that Profile has both the IM&P service as well as the CTI service configured.

          I also checked and confirmed that within IM&P under Messaging that Instant Messaging is enabled via the checkbox.

------------------------------------------------------------------------------------
Dr. Jeffrey T. Girard (Jeff), PhD
Colonel, United States Army (Retired)
Senior Network Engineer / VoIP Engineer - WireMeHappy.com
reply to: jeffrey.girard at wiremehappy.com<mailto:jeffrey.girard at wiremehappy.com>
(607)835-0406 (home office)
(845)764-1661 (mobile)
(607)835-0458 (fax)

From: Matthew Loraditch [mailto:MLoraditch at heliontechnologies.com]
Sent: Tuesday, July 01, 2014 11:15 PM
To: Jeffrey Girard; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] Why would Jabber for Windows and CUPC clients not be able to use IM?


UC Service Profile have the IM&P server defined?


Matthew G. Loraditch - CCNP-V, CCNA-R&S, CCDA

1965 Greenspring Drive
Timonium, MD 21093

direct voice. 443.541.1518
fax.  410.252.9284

Twitter<http://twitter.com/heliontech>  |  Facebook<http://www.facebook.com/#!/pages/Helion/252157915296>  | Website<http://www.heliontechnologies.com/>  |  Email Support<mailto:support at heliontechnologies.com?subject=Technical%20Support%20Request>
________________________________
From: cisco-voip [cisco-voip-bounces at puck.nether.net] on behalf of Jeffrey Girard [jeffrey.girard at girardinc.com]
Sent: Tuesday, July 01, 2014 8:16 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] Why would Jabber for Windows and CUPC clients not be able to use IM?
This is a lab environment and my third round at doing a fresh install / configuration of IM & P.  CUCM 9 and IM & P 9.

Integration is complete and all diagnostics show green across the board.

There is no LDAP integration this time (I had done it before so I was comfortable in how to do the integration).

No DNS either (again, in my two previous lab iterations, I had stood us a Microsoft domain and used A/D, LDAP integration, and DNS.  This time I decided not to do that).  I simply added an entry in the laptop host file for the CUPS server

So, Presence works on the IP phones (BLF/SD) show the appropriate information

Both CUPC and Jabber for Windows (version 9.7? I think) log in and register to the IM & P and to the CUCM servers.

Calls can be placed between all devices.

However, Instant Messaging is not available.  The only symbol/icon for the users are the phone.  Double clicking on the user only initiates a phone call and not a chat session.

Im sure its something pretty simple that Im missing.....

A thought.......do I need to add an entry in the host file for the CUCM server?

Any ideas?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140702/d51e0105/attachment.html>