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.
To All, We recently updated our Jabber to address a critical vulnerability and have been discouraged to have been blessed with a new "feature" from Cisco. We operate ~50 Cisco 8851 phones with 3 lines per phone (2 shared lines for two separate busine...
Hello All, I'm hoping someone can help me out with an incredibly frustrating issue I'm facing with our Cisco VOIP system. We have approximately 25 Cisco 8851 VOIP phones at 3 separate locations. The majority of the phones work correctly, without issu...
This is actually a new "feature" from Cisco post Jabber 12.1 version through current 14.x. There is a feature change request in place that you should sign up for, so we can get this addressed. It's a big issue for our organization: https://bst.clouda...
Thank you for the clarification Jaime. It seems like this should be a fairly sizable issue and will need correcting ASAP. I will reach out to our SE to get added to the PER.
I would consider bouncing the phones from the switch via PoE if you still haven't found a solution to this. Seems like you could write something to do a power inline never power inline auto on the switch ports.
To All, I'm circling back to provide the solution to this issue, just in case anyone else runs into this problem. After extensive discussions w/ Cisco TAC engineers from the VOIP, CUCM, and Firewall teams, we determined that the issue was ultimately ...
Paul, This is very helpful information. I will give this a shot and post the results here. I've always used the GUI on the ASAs, but am learning the CLI as I go here. Thx,Ap.
