I tried this on an SX20 with a touchscreen paired remotely and get the same results as what you have on your C20. If you have root access to your C20, can you check the file named /var/log/eventlog/touchdevice.log ? There I see the touchpanel does get the command from the codec to store a snapshot like this :
Sep 4 08:50:11 localhost touchmenu: INFO : Created screen shot: "/uifs/snapshots/snapshot.png"
Sep 4 08:50:47 localhost touchmenu: INFO : Created screen shot: "/uifs/snapshots/snapshot.png"
Sep 4 08:51:00 localhost touchmenu: INFO : Created screen shot: "/uifs/snapshots/snapshot.png"
I think the problem might be related to codec not being able to retrieve that file ?
I have ssh open to my touch panel [I am using some test software], so I did an scp of the snapshot copied below.
I wonder whether this is intentional, i.e. snapshots do now work over remotely paired touch.
the /uifs/snapshots folder would be on the touch filesystem, not the codec. For security purposes, the touch cannot be accessed via ssh, so maybe we cannot retrieve those files. In directly paired mode, the touch talks to the codec using TCP/telnet as opposed to SSH. That difference could well be the underlying reason why snapshots fo not work for non-directly paired touch.
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...