Error Messages System: xx has the following error when booked in Cisco TMS: Cannot add participant When adding a new system to TMS XE and saving the configuration the error below is received. Errors occurred when testing booking with one or more of the provided systems. System:101 has the following error when booked in Cisco TMS: Cannot add participant This error occurs because in TMS the endpoint is not set to be bookable.

Start a call xcommand Dial Number: 12345 Retrieve calls status and ID xstatus call *s Call 20 Status: Connected *s Call 20 AnswerState: Answered *s Call 20 CallPriority: None *s Call 20 CallType: Video *s Call 20 CallbackNumber: “sip:12345@10.10.10.13” *s Call 20 DeviceType: Endpoint *s Call 20 Direction: Outgoing *s Call 20 DisplayName: “12345” *s Call 20 Duration: 12 *s Call 20 Encryption Type: “None” *s Call 20 FacilityServiceId: 0

Upgrading a Cisco Meeting Server (CMS) database cluster is a straightforward process thanks to the simplicity of the solution. Thanks, Acano team! The text below describes the steps for upgrading a three node cluster with two slaves and a single master. Two of the servers are Acano X3’s in a Call Bridge cluster and the other is a virtual appliance providing only database functions. Before doing anything backups of each CMS should be taken.

From the CLI use the utils network capture command. To capture everything, use parameters similar to that shown below. utils network capture eth0 file packets count 10000 size all To stop the capture before the 10000 count press ctrl+c To retrieve the files use the command file get activelog platform/cli/packets.cap and providing valid SFTP server details Alternatively, log in using RTMT > Trace & Log Central > Collect Files > select Packet Capture Logs > Set the time interval as per normal and download Updated - 28/05/2018 To locate capture files you can use the command file list activelog platform/cli

Mute all future participants using DTMF In this scenario, the muteAllNewAudio DTMF sequence is used to set the call parameter joinAudioMuteOverride “If true, new participants will be muted when joining the call.” (Cisco Meeting Server API Reference Guide 2.0. p. 55) Set the callLegProfile used by the space with the parameter changeJoinAudioMuteOverrideAllowed=true On the DTMFProfile configure: muteAllNewAudio=*8 unmuteAllNewAudio=*9 toggleMuteSelfAudio=*6 Now a participant can join a space and using DTMF enter *8.

Using the Cisco TelePresence Conductor conference template you can create a video loopback by setting the advanced parameters: customParams = {“callAttributes”:{“displaySelfView”:true}} displayDefaultLayoutSingleScreen = layoutSingle iXEnabled = True

In this article, I document the steps I used to capture a live H.264 video conferencing call and then replay it for viewing. To do this I built an Ubuntu Virtual Machine, and utilised: Wireshark - to perform the packet capture Videosnarf - to decode the RTP streams from the packet capture Mplayer - to replay the captured video Videosnarf can be found here, http://ucsniff.sourceforge.net/videosnarf.html. To build the Ubuntu Virtual Machine do the following:

Convert a DER to PEM openssl x509 -inform der -in myder_certificate.cer -out mypem_certificate.cer Convert a PFX to PEM openssl pkcs12 -in mypfx.pfx -out mypem.pem -nodes Convert a PFX to PEM without keys openssl pkcs12 -in mypfx.pfx -out mypem.pem -nodes -nokeys Convert a PFX to PEM keys only openssl pkcs12 -in mypfx.pfx -out mypem.pem -nodes -nocerts Confirm a private key againt a certificate. Both should output the same value. openssl rsa -noout -modulus -in mycertificate.

This post details how to configure a SIP-TLS trunk between Cisco Video Communications Server (VCS) or Cisco Expressway-Core and Cisco Unified Communications Server (CUCM). This post references a single CUCM node (version 10.5) with a single VCS Control (version X8.2.1) lab build throughout, and only the minimum steps to achieve the desired outcome are described. It is assumed that both CUCM and VCS have a basic config and endpoints can register with SIP-TLS and can dial other endpoints registered to the same system (VCS>VCS, CUCM>CUCM, etc.

This post details how to register a Cisco Videoconferencing endpoint, specifically TC based endpoints such as the C or EX series, to Cisco Unified Communications Manager (CUCM) 10.5 utilising SIP-TLS. This post references a single node lab build throughout, and only the minimum steps to achieve the desired outcome (registering the TC based Videoconferencing endpoint to CUCM using SIP-TLS). Firstly why would you use SIP-TLS in the first place? Using the Transport Layer Security (TLS) protocol will protect the SIP messaging traffic on the legs where it is enabled, preventing a third party (the forever mentioned and nefarious BOB) from intercepting the SIP messages for malicious purposes, such as deciphering the caller and callee details which could be sensitive in certain environments.