voicemail access, 1-way audio, and device unregistrations with Win OS SP4
My client is running CM 3.3(2) spC in a 2 CM group for a single campus. There are approx. 1000 devices in total between 7960's, 7940's, 7905's, 7935's, VG-248 and 6608 gateways, CTI ports, and Unity voicemail ports.
We recently installed the Cisco distributed update for Win OS SP4 on the call managers, and apparently have had several call processing issues as a result. Almost immediately we began to see issues with the voicemail button the the phones getting dead air or reorder, then we started to get delayed or one-way audio between skinny devices on the LAN. Most recently we have been seeing devices unregister from call manager individually or in groups of up to 10 or more. For the latest problem, we suspected an inline power issue, but each Cat6513 shows approximately 1100 Watts available (sh env inlinepower).
Rebooting the call manager cluster did not help. Putting the latest phone load on the 7940/60's of P00305000300 seems to help with the voicemail button and we think the one-way audio, but it is still not conclusive.
Does anyone have any thoughts or has seen this too?
Re: voicemail access, 1-way audio, and device unregistrations wi
Here's a couple of items that I have seen in our environment, which is now CCM 3.3.3 SR2, Unity 3.15, and IPCC/Express 3.1(2). When we first installed Win OS SP4 it caused a bunch of problems with IPCC calls. We were getting one-way audio, reorder tone, or disconnects. We backed off the maintenance ASAP and then later found out that P00305000101 phone load was causing the problem. We installed the latest P00305000300 load and then followed with the OS SP4 maintenance (OS2000.2.5sr4). The problem has not reoccurred.
We also had groups of phones un-registering. This turned out to be an unrelated LAN problem. Phones and gateways at one location would un-register and immediately re-register at 4 hour intervals, but not every four hours. Sometimes at 04:00am, then at 08:00am. Or at noon and then at 4:00pm. We were also getting Ciscoworks alerts about new spanning-tree root were discovered on the subnets on the same 4 hour intervals. Our physical configuration has not changed for three years, but within the last few months we started seeing more phones unregister. We also just turned up Ciscoworks, so we do not know when the spanning-tree root changes started to occur, but we didnt have the problem in the past.
We were running CatOS 7.1(2) on our core Cat6509's and our phones were on Cat3524's running IOS 12.0(5)WC8. The Cat3524s were dual-homed to a pair of Cat6509s in the core. We ended up upgrading our Cat6509's to CatOS 7.6(3a) and all the spanning-tree root changes have disappeared. So for us the group of devices un-registering at the same time was caused by the LAN problems.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...