Anyone have any ideas why the phone icon on the bottom right side of the jabber client screen would be greyed out. This happens intermittently. Repeated "sign out" and "sign in" will eventually bring it back.
I also came across this issue in a lab i had a while ago; but i had to delete the Cisco Jabber app data in order for me to get the phone icon back. As soon as i logged out and back in, it stopped working.
Would be interesting to see if you managed to resolve this?
We have about 40 clients running J4W 9.0.3. Unfortunately one user have this issue (and he is a CEO ). It's also happens very intermittently, but a sign out-sign in fix the issue. But it shortly returns. I think it happens when he remove a forward to his cell.
I have also tried 9.0.4 on his PC, but same thing. Does anyone have a fix for this? And other users don't seems to have the problem.
This is not a known issue. Please open a case with Cisco TAC so that team could investigate this further.
We had our telephony vendor open a case with TAC and they were aware of similar issues. We are told the next release of Jabber (October 2012) is supposed to fix the issue.
Upgraded Jabber for Windows clients in my lab to 9.0.5 and it appears to have resolved the issue.
Phone icon is present on all clients now, do we know what the issue was? It looked like it something to do with the local machine which Jabber was installed on, some of my users worked and some didnt, yet they had identical config in CUCM?
I have some news.
I have found out how to trigger this on all of our Jabber for Windows installations.
How to trigger the greyed out button:
Now the button is greyed out. At least on our setup. If I also have a deskphone I can take the hook off and put it down again, and the button is active again. So it seems there have to be some line activity to reactivate the button.
Can anyone confirm the same issue? We are running J4W 9.0.5.
This is really annoying
I tried above steps to reproduce but no luck. Since you can reproduce it consistently, please provide a problem report for investigation as below:
1. Exit Jabber and clear Logs folder under "C:\Users\xx\AppData\Local\Cisco\Unified Communications\Jabber\CSF"
2. Start Jabber and reproduce the problem.
3. Create PRT and upload it to my webex site using steps below.
- Open link
- You will see Meetings and Files tab.
- Click on Files tab. It contains a folder called "Jabber Logs" and Upload link on the far right.
- Upload you PRT in this folder
I have the PRT file for you. But I can't see the folder called "Jabber Logs" in the WebEx meeting.
Kristian Steen Kirk
Can you try it once more?
- Click on Files tab.
Any news about this one? It's really really anoying in our installation. I have opened a TAC on this one, and the TAC supporter could reproduce the problem. I hope that you have a fix soon.
In the logs we could see that the Jabber client tries to connect to the client itself and not the CUCM. Really strange.
This is unacceptable.
Is it 622978655? This TAC case has been escalated and is being triaged at the moment.
I have tested J4W 9.1 beta, and here I can't reproduce the issue. I'm looking forward to the final release of 9.1. And also 9.2 which should add support for EHS .
Come on J4W team, you are almost there.