Actually, to make a comment about my previous message. You don't even need to worry about the advisory when upgrading E20s, as they don't need a release key, you can simply upgrade them without it as they're not required. So no need to go through the advisory in regards to the E20.
While attempting to add a Cisco E20 to a multi-point Secure Conference in TMS, we receive the following message.
Cannot add Sip Participant in a Secure Conference Due to Wrong Encryption Settings
Any idea what is causing this? Is this not possible? The E20 is on software TE126.96.36.1999545.
If the conference is set to 'encryption = yes' in booking, this means TMS will REQUIRE a participant be known to support ecryption before it is allowed to be booked as part of the meeting. If set to Best Effort, TMS will allow a non-encrypted participant, but not set encryption required on the devices.
This message is saying TMS does not believe your E20 as configured supports encryption. For SIP encryption in the E20 and TC endpoints, TMS looks at the SIP Transport Type to determine if the endpoint can support encryption (it's not an easy determination for SIP...).
If your E20 is not set to SIP Transport = Auto or TLS... TMS infers the device can not support encryption on SIP and will not allow it in a call where encryption is required instead of optional.
check your SIP profile properties in the E20 and set it to Auto or TLS (assuming your registrar supports TLS)
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...