Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi There-
Well i didn't find much about how to make it happen but there is an option where i can use the board with the hybrid calls service, i already implemented the hybrid calls (everything is working, etc.) now i don't really know how to make t...
I will try to explain this behavior as simple as i could.
1.I have one active call in the physical phone (Cisco 7821)
2.I also have Cisco Jabber active and registered in my smartphone.
3.On my physical phone I receive a new incoming call, but my Ci...
After i upgraded Jabber to 11.9 i am not able to use custom tabs, etc. using the jabber-config-user.xml on my windows 10 computer. I tried resetting the jabber, erasing it completly from my computer, i used another computer -also win 10- with a diffe...
I have a CME with a 100 phones Permanent licence i am only using 38
I registered one SCP phone and then one of the other phones got the message "Max Phones Exceeded" on the screen.
The Max ephone and Ephone Dn is set to the top -allowed by the CME-...
Hi Stuart-
Hope you are doing well.
1. Are you using the correct syntax on your XML file?
2. in the Cisco Support Field are you putting the correct file name? as shown above Example: "configurationfile=bv-jabber-test.xml"
3. What version are you ...
I have not found the solution for that....i just know that the file that replaced the local XML config is now encrypted so configuring locally is not gonna work.
I think there is something we have to do/upload in the CUCM in order to Jabber to dow...
Good afternoon.
Hi @Mohammed al Baqari everything is configured as you said. but i found the root of this issue, this is happening just in Jabber for iPhones, it works perfectly on Android and MAC/Windows.
I was reading the restrictions and limit...
I was facing the same issue and instead of pointing the TSP config to a publisher node i pointed it to a subscriber node and it worked perfectly, the Cisco TAC told me it could be a CTI Manager issue on the publisher node.
Regards,
