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.
I've upgraded two 4500 chassis with 9400 so far. Replaced with 9407 with L3 PC uplink config on other end 6880 untouched, but when I do 'channel-group x mode active' on the 9400 both sides claim lacp isn't configured on the other side. Switch origina...
I'm using UCM 10.5(2)SU2a (10.5.2.12901-1) & Jabber 11.1.1 on Windows and Mac, but I'm sure same thing happened with earlier versions of UCM and Jabber. Neither platform's Jabber client respects the CSF phone parameter in UCM 'Automatically Start in ...
I recently upgraded from a 10.5.2 release to 10.5(2)SU2a, and it all works fine. But the GUI is sluggish compared to earlier versions. Adding and updating phones takes perhaps twice as long to add or save. If an add or change took 2-3 seconds I'm goi...
I'm using UCM and IMP 9.1.2. All versions of Jabber v9.6 won't login in 'auto' mode, even though it can see my IMP server dns address has been identified to jabber via the SRV record. I must click 'manual setup' and then select Presence as the meth...
I have a 4260 with the latest software and I know it is rated at 1 - 2 Gbps (transactional / media rich) throughput. I have it monitoring a 400 Mbps pipe that is pretty well maxed out at 400 down and 100 up during peak times for a total of 500 Mbps ...
Thank you for your work. I'm sure it should be obvious, but one clarification in the above instructions about meaning of "one by one" if I may. Do you mean one by one according to host or by service? By host like this #1 On pub restart:Cisco CallMana...
I realized that the fixed version is the latest (16.6.3 was the latest when I had this issue) so I just upgraded a 9400 and turned lacp back on. I can now verify it works great. Thanks again.
Ah, I missed that one. By making the state active manually, I'm not sure it wouldn't go into suspend again in case of a power outage or reboot. I'll just try the next upgrade using the fixed 16.6.4 to be safe.
I found it. There was an InitialPhoneSelection keyword set to 'deskphone' in the policies section of the jabber-config.xml. I changed it to 'softphone', but perhaps I could have removed it.
