topic Christopher, in Collaboration Applications

Jabber for Windows 9.1 get message could not be delivered.

Atllp_rtutt — Sun, 17 Mar 2019 21:51:23 GMT

Everytime I message a co-worker for the first time every day I get this error

Then when he responds it doesn't have his name listed. i.e. (his responce is "just once")

To which I said hrm!!

Very odd. It seems that he is the only person that this happens to.

We have rebuilt his cisco framework softphone. (Razor blade icon)

I deleted my win 7 profile cache in both local and roaming.

Re: Jabber for Windows 9.1 get message could not be delivered.

Muhammad Maqsood Mushtaq — Thu, 06 Dec 2012 13:05:37 GMT

Hi,

If this is cloud deployment (WebEx) and you see following statements in log file for the failed message, then it is a known issue:

DEBUG [0x000024c8] [\imp\handlers\IMP2PResultHandler.cpp(41)] [csf-unified.imp.presenceadapter.imp2presulthandler] [IMP2PResultHandler::execute] - Jid: johndoe@example.com Result: SUCCESS

.......

DEBUG [0x000024c8] [\imp\handlers\IMP2PResultHandler.cpp(41)] [csf-unified.imp.presenceadapter.imp2presulthandler] [IMP2PResultHandler::execute] - Jid:johndoe@example.com Result: FAILURE

If it is On-Prem (CUP) deployment, this will need further investigation via a TAC case.

Thanks,

Maqsood

Jabber for Windows 9.1 get message could not be delivered.

Atllp_rtutt — Thu, 06 Dec 2012 21:51:06 GMT

This is on prem cup deployment. Only seems to happen with this user.

Jabber for Windows 9.1 get message could not be delivered.

David Grunenberger — Tue, 18 Dec 2012 19:03:04 GMT

We were able to test an upcoming version in our shop for Cisco and it seems to correct this problem. Hopefully will release right after Xmas. I believe the 9.1.2 release.

Jabber for Windows 9.1 get message could not be delivered.

Christopher Koelling — Thu, 10 Jan 2013 17:58:06 GMT

I am running 9.1.2 Jabber and still get this issue with an On-prem deployment....8.6.4 CUPS...

Any Ideas? IT isn't consistent.....

Jabber for Windows 9.1 get message could not be delivered.

ashbrook2004 — Thu, 17 Jan 2013 15:04:51 GMT

I am seeing the same issue as Christopher. Upgraded to Jabber 9.1.2 with on-prem deployment 8.6.4 CUPS. Any other ideas?

Jabber for Windows 9.1 get message could not be delivered.

Christopher Koelling — Thu, 17 Jan 2013 15:20:42 GMT

This is actually a bug in CUPS. It has to do with the IM forking that happens if you have multiple devices using chat.(Iphone, ipad and windows clients for instance) once you reply to the mesage then the chat is unicast to the one specific device and the issue dissapears. The current workaround is stopping the SIP Proxy service on your CUPS server. The only thing this affects is web based stuff in the administration pages. This is supposed to be fixed in v8.6.5 CUPS.

Jabber for Windows 9.1 get message could not be delivered.

ashley.pearce — Thu, 14 Feb 2013 16:16:27 GMT

Hi All,

We're seeing this bug on 9.1.1, is there a bug id for this issue?

Ash

Jabber for Windows 9.1 get message could not be delivered.

Chris Deren — Fri, 15 Feb 2013 00:43:30 GMT

I just noticed this on new IMP 9.1 deployment with J4W 9.1.3, always occurs on new conversation and goes away after initial reply, very frustrating.

Chris

Jabber for Windows 9.1 get message could not be delivered.

haotran_26 — Wed, 06 Mar 2013 16:48:37 GMT

We ran into the same issue with one individual user, we were able to resolved it by going to Call Manager and remove the user license capability and re-enable it.

Jabber for Windows 9.1 get message could not be delivered.

Joshua Sandi — Tue, 12 Mar 2013 12:19:55 GMT

Hi there,

I would recommend you through a CLI run the command "utils service list" and see if the following services are running:

Cisco SIP Proxy
Cisco Sync Agent
Cisco XCP Authentication Service
Cisco XCP Connection Manager
Cisco Presence Engine

Also some times this can be related to the "Persistent Chat" being enabled, you might be able to check that in CUPS under Messaging > Group Chat and Persistent Chat Settings, if you're not using it you might want to disable it.

Regards,

Jabber for Windows 9.1 get message could not be delivered.

Muhammad Younas — Mon, 08 Jul 2013 07:39:59 GMT

Hi Hao Tran,

I got the same issue and your solution worked for. Thanking you

Jabber for Windows 9.1 get message could not be delivered.

Paul McGurn — Mon, 21 Oct 2013 14:21:08 GMT

Is anyone getting this on CUPS 9.1 specifically in HA with user assignment set to Balanced mode vs. using the secondary node as a hot standby? I seem to only see this issue between users that are not on the same node, and TAC gave me some dodgy reasoning around assigning all users to a single node that I didn't really buy into.

Jabber for Windows 9.1 get message could not be delivered.

David Grunenberger — Mon, 21 Oct 2013 14:34:08 GMT

All I had to do was go to Call Manager and remove the user license capability and re-enable it per Hao above. That fixed the issue.

Jabber for Windows 9.1 get message could not be delivered.

haotran_26 — Mon, 21 Oct 2013 14:36:38 GMT

Hi Paul,

What Jabber 4 Windows version are you running? Are your userID and mailID in the same format? There is a bug starting with Jabber 9.2.4 with visual voicemail. Basically if User A call User B and left User B a message, User B will not be able to send User A anymore instant message until they delete the visual voicemail message and remove the caching info in the user's local CSF and voicemail folder. This is due to IM address being changed due to visual voicemail integration. Version 9.6 and 9.2.6 appeared to resolve the issue.

CSCuj48084 Bug Details

Jabber changes IM of contacts from whom user has voicemail messages

Symptom:

User is unable to IM certain contacts. Sees error "Message to XXX, XXX could not be delivered." in chat window.

When right-click on contact to view profile, IM address incorrectly set to email address.

Conditions:

When running Jabber for Windows 9.2.4, with visual Voicemail connected to Unity Connection, receive a voicemail from a user on your contact list.

Workaround:

Permanently delete voicemail message from that user, then sign out of Jabber and sign back in.

Further Problem Description:

Jabber for Windows 9.1 get message could not be delivered.

Paul McGurn — Mon, 21 Oct 2013 14:36:52 GMT

That didn't work for me, and it isn't a "fix" it's a workaround. Other workarounds have been to bounce Jabber for both users involved, migrate the user to a different node, and blow away the local configuration folders. None of these are a fix, though. It's a bug, for sure, but I'm trying to narrow it down to either rCUPS or Jabber so I'm not spending 5 hours on the phone with TAC running through a script.

Jabber for Windows 9.1 get message could not be delivered.

Paul McGurn — Mon, 21 Oct 2013 14:51:00 GMT

When it's saying that the IM address is being overridden to email, is that on the machine viewing the profile, or the machine of the user the profile describes? Our Unity mail ID is identical to the CUPS IM address, in any case.

I'm on 9.2.6 and the user I'm able to reproduce the erro with is on 9.2.4. I've never left him a voicemail, and he's never left me one. I deleted the %appdata% and %localappdata% folders on his machine, as well.\

I found CSCuc81728 in teh bug toolkit as well, but it's about as generic as it gets as far as descriptions go. I opened a TAC case, in the interim.

Jabber for Windows 9.1 get message could not be delivered.

Andrija Divac — Mon, 04 Nov 2013 22:38:49 GMT

I am having this issue with 9.2.4 and 9.2.6 with multiple users.

We have this issue occuring

Jessica Cochran — Tue, 15 Apr 2014 14:23:30 GMT

We have this issue occuring as well with a few users, but not everyone

Anything new we could try?

We are running V 9.1.1 Presence and then Jabber v9.7.0

HiUpgrade your CUP server to

Leonid.Arkhipov_2 — Tue, 15 Apr 2014 15:16:17 GMT

Upgrade your CUP server to the latest version of 9.1.3 minor relese.

This recommendation was provided by Cisco TAC and helped me in the case I encountered.

Cheers

Leo