Are you using SIP or H323 for Multiway? I remember having some issues interworking CTS/SIP to H323, specifically relating to content sharing but it was some time ago so I don't remember the details. I do know however that Cisco recommends against it...
Likewise, check for interworking in the calls between the C60 and CTS-1300. Maybe it's interworked in one direction but not the other? This could explain the differences...
Is this SIP only or is there interworking? CTS endpoints will only use TIP for presentations by default. If they can't negotiate BFCP properly, you will fall back to PiP.
You might need to configure BFCP properly on both the VCS and CUCM in the device and trunks/zone profiles. Otherwise, the CTS 1300 will only be able to show PiP. In the deployment guide for CUCM with VCS for any versions, it has a step by step config guide. Also, in the CTS device profiles, you will need to enable BFCP in the SIP profile.
There could be a lot more going on, but this is a good place to start.
BFCP has been enabled on all devices and functions fine.
I've followed all the installation guides and double-checked them again for good measure.
The issue only appears on multiway conferences and as I mentioned before only when the CTS-1300 calls the C60 (which is already in the multiway conf) and is then added into the multiway. If the C60 invites the CTS1300 into the multiway conference, the CTS1300 successfully negotiates the content channel with the MCU.
All other presentation sharing on other conferences and point-to-point calls are working as expected.
The other thing I would check is encrypted vs. non-encrypted.
The recently(ish) released version of MCU (4.5) supports encrypted SIP content, while previous versions didn't.
You might be getting encryption in one call direction (CTS1300 to C60) and not the other (C60 to CTS1300), which would affect whether or not a content channel was supported. In any case, I would also check the software versions on all endpoints and the MCU are at the latest.
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...