We are testing JFW 10.5 and I think its the best version so far. But we are seeing a issue with the presence status.
Sometimes it shows a user available but in the fact, the user is offline (client closed).
We are running CUP version: 184.108.40.20600-2 and CUCM: 220.127.116.1100-9.
If a user is logged off it should show the user with a grey presence colour. However, the user is displayed with a green colour, and therefore it looks like the user is online, but the fact is that the user is offline.
No :( I think we have to start a TAC :( please do the same, The more the merrier.
Which user are you unchecking? the user that are seeing another user as available, or the users that are showed available, but in fact are offline.
I have now looked in the presence viewer on the CUPS. The user is grey and offline but in the Jabber client, it shows that the user is green and available. After an restart of the Jabber client the user is grey.
What can it be?
Then you would need to drill down to traces and PRTs to find out if it's CUPS that is not sending the update, or if Jabber is not processing the update properly.
I would try with a few other users, if you have more than one server, try with users on the same server and see if the behavior is the same.
You might want to open a TAC for this
Scroll down to traces and PRTs? you mean that I should generate a PRT in the Client?
Atm. we only have one CUPS. Several users have been reported this issue.
I will contact Cisco TAC.
I know this is a little old but wanted to give my resolution when i see this. If I un-assign and then disable the user for presence. Next re-enable the user and re-assign his presence node the status returns.
I have seen this in almost every version since CUPs and Jabber 8.6. Not sure why it happens but this usually resolves the problem.
But this is happen for random users.
But which user should I re-enable? The user that are seeing the presence issue, or the other end?
Hi I actually just finished resolving another user that had this problem. For me it is also random users not everyone. In this order:
Un-assign the user in CUCM "assign presence users".
Remove Jabber capabilities in CUCM user. Save.
Re-enable user for jabber. Save.
Re-Assign CUCM "assign presence users".
We have the same issue, but also with other J4W clients.
Disabling en re-enabling a user for CUP is a crappy workaround.
One cannot disable and re-enable ALL jabber users in the hopes they won't be facing this issue.
We have a running case at TAC, however we always get the comment "update the jabber client and give us a ring whenever this happens so we can do some real-time troubleshooting".
Has anyone resolved this issue with TAC yet? I constantly have a user here or there that don't show correct status, I have two CUPS servers and have found that if I move the user from one to the other after a couple minutes their viewer status goes from unavailable to correct status, but this work around is not a resolution. Before I open a TAC case I am trying to find out if there was a resolution, currently on Jabber 10.6.2
Did you find a solution for this presence issue?? I´m having the same trouble in CUP 11.5 and Jabber 11.9