I have two issues that I would like your assistance in resolved.
1) The 7961G phones connected to my CME 4.1 system with the updated DST firmware are displaying a time 5 hours ahead of local time. I have set the clock timezone command, performed the DST IOS work-around, and the router syncs to a stratum 2 NTP source. I am at wits end trying to figure out why they all display the incorrect time - while the other models in product (7912s, 7936) are displaying time correctly.
2) The 7936 locks up in off-hook status if during a call to another internal extension the call is placed on hold, or held temporarily for a transfer. When the far end comes off hold - the audio path is not reconnected and the call is lost. We have to unplug the 7936 from the wall to reset this condition. Any ideas?
Are the 7961s running 7.03 firmware ?Many 7941/61s come with this particular load from manufacturing. I have had a tough time trying to upgrade them to latest firmware to get the time to show up properly.
It appears from the debug ephone detail that my 7961 phones are attempting to register with the CME as 7960 phones. This of course has the affect of negating the load 7961 and load 7941 commands for new firmware.
Since I do not have any 7960s on the system, I modified the load 7960-7940 command to reflect the new firmware. Upon cycling the phones - they still failed to update to the new code.
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...
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 discusses the bas...