I upgraded an MX300 G1 from TC 6.3.0 to 7.1.2. After upgrade, it lost connection to the touch panel.
After rebooting a couple of times, I went back to 6.3 and the touch panel was fine. I then reupgraded to 7.1.2 and its lost its pairing again. I also tried 7.1.1 - still no pairing. Again, downgrading back to 6.3 fixes the issue.
The strange thing is that I've got another MX300 G1 that I upgraded from 6.3 > 7.1.2 with no issues. They are both configured pretty much identically, with different system names and SIP URIs.
We had someone attend site and said that the touch panel was just sitting there on the "spinning circle" icon, without giving any options to point to the codec etc. Unfortunately I wasn't available at the time to look further, but they downgraded back to 6.3 in any case to get the unit back online.
Is this expected behavior, or should the panel be providing some kind of "prompt" to allow manual pairing? I've only used the Touch 8"s remotely or with EX90s in which case they've always paired automatically, I've never had to manually pair one so please excuse my ignorance.
The solution is to factory reset the touch, and reboot the endpoint before the Touch comes up again. To do this:
Press and hold down the exclamation mark Touch button (which is found below the volume bar) for 10 seconds or until it turns white.
Press the mute button twice. The Touch panel will now initiate a factory reset.
When the Touch is booting up you will see the screen goes black before showing the Cisco logo, now restart the endpoint immediately. On EX series, press the front power button until shut down. On MX series, flip the power switch on the back of the unit.
Power on the unit after a few seconds. The Touch panel should now successfully pair with the endpoint.
(Note: Steps 1-4 copied verbatim from documentation, I haven't tried them myself )
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...