WebEx Site Enabling Recording Ready Notification

I do not usually post about WebEx site admin settings but going to make an exception for this one so I do not forget.

After a recording has been completed in WebEx you should see a automatic notification email in your inbox when your recording is ready. If you have set your site to record every session this setting is not recommended but for some reason if its not working here is how you turn it on. Under site options:

Just select the "Send notification email to host when the meeting recording is ready".

Site options documentation:


Troubleshooting Intelligent Proximity on Cisco Collaboration Endpoints

One of the issues that you may come upon with Intelligent Proximity is knowing if your endpoint is emitting the ultrasound required to pair with your device. There may be a number a number or reasons for this, including if your using a third party screen with a integrator system (SX10, Sx20, SX80), and the good news is there is an easy way to tell using a free third party application on an iOS device. I am not sure if the same company makes this app on other OS’s but on an iPhone it works extremely well.

SpectrumView will present the ultrasound output from your device in a easy to read format. You will have to change the default range to get the range required to see the Proximity output but this is easy enough to do in the settings of the app.

Below is a screenshot of Proximity turned off. In my case I just turned the power to my third party screen off that was connected to an SX80. As you can see the required range highlighted in red is pretty quite. If you haven't worked it out yet this is the equivalent of a none functioning Proximity pairing signal.


Below I have turned my screen back on and the Proximity pairing signal is coming through just fine again highlighted in red.


If ultrasound is detected but the audio levels are low, try increasing the ultrasound volume using the command below:

xConfiguration Proximity Pairing Audio Volume MaxLevel: <0-90> default: 70

Hope this helps with your Proximity troubleshooting.


More on Troubleshooting SpeakerTrack 60

This is not a failure prone device, its far from it but when you do have an issue because it does not happen very often it can be difficult to find troubleshooting information. Below are some tips and tricks I have seen and used to help diagnose and fix issues.

Issue: Audio tracking and face detection not aligning

This is a much harder condition to diagnose because it looks like its working but seems really slow to change camera angles and zoom in on the face detected.

The best way to discover this issues is with these two commands:

xCommand Experimental SpeakerTrack Diagnostics Start

xCommand Experimental SpeakerTrack Diagnostics Stop

Once your in diagnostic mode what you will notice is a lot of red squares which means a face has been detected as shown below but not a lot of green which means a voice has not been matched to a face. I also noticed that F value was pegging at around 100%.


Solution: Firstly you should always open a TAC Case but in saying that you can also factory reset the SpeakerTrack unit (not the codec). This can help to recover the SpeakerTrack and restore functionality.

Refer to page 17 of the SpeakerTrack Admin guide how to do this:


For the MX700 Dual the picture below points to where the reset button is for the camera modules. Handy to know if you have a single camera that goes offline. The ST unit also has a similar factory reset button. This can also be done via a null modem cable connected to the serial port but most people do not often have a modem cable handy and a paper clip is much easier to find.

SpeakerTrack FR

More Handy Commands for SpeakerTrack:

Checking status:
xstatus // speakerTrack
*s Cameras SpeakerTrack Availability: Available
*s Cameras SpeakerTrack LeftCamera VideoInputConnector: 1
*s Cameras SpeakerTrack RightCamera VideoInputConnector: 2
*s Cameras SpeakerTrack Status: Active
xstatus // Peripherals
*s Peripherals ConnectedDevice 1045 Name: "SpeakerTrack 60"
*s Peripherals ConnectedDevice 1045 SoftwareInfo: "MT7.3.0.8cb420c"
*s Peripherals ConnectedDevice 1045 Status: Connected
*s Peripherals ConnectedDevice 1045 Type: SpeakerTracker
Things to look for are whether ST is connected and also the software version number aligns with your codec versioning.
Turning on/off SpeakerTrack:
xCommand Cameras SpeakerTrack Activate
xCommand Cameras SpeakerTrack Deactivate
SpeakerTrack Setup document:


Previous Troubleshooting post:


If you have run into other commands that are handy or tips and trick's please feel free to post in the comments.


Troubleshooting Cisco TelePresence SpeakerTrack 60

More and more companies I am working with are deploying Cisco TelePresence SpeakerTrack 60 with either a MX integrated device or as a standalone with an SX80. So I thought it would be good to let everyone in on a very helpful command to watch the SpeakerTrack in action. There are a couple of steps involved to turn on the diagnostic mode and it can only be done via the command line today.

If you have never used SSH to log in to a Cisco TelePresence device your going to have to download and install a SSH client like Putty or from a MAC use the command line. Here is the link to Putty: http://www.putty.org/

SSH into the codec via its IP address.


Log in.

Run the following commands to turn SpeakerTrack diagnostic mode on and off.

xCommand Experimental SpeakerTrack Diagnostics Start

xCommand Experimental SpeakerTrack Diagnostics Stop

Below is a screenshot of diagnostic mode turned on and a face is detected but no audio match.


Now the engineer is speaking below, and the green square indicates a positive match for facial detection and voice. Therefore the system will zoom in to this person.

The indicators down the bottom of the screen match up with the following:

F = 10.1% detected voice
T = 91.6% non-noise
E = 0% voice from far end
C = 28.1% camera movement
U = 0% ultrasound detected
N = 89.9% silence
S = 178 samples from sound algorithm


If you run this it will help you understand if SpeakerTrack is working but you will need someone in the room to see it displayed on the screen and hae a face to actually track. You wont see jack if you do not have someone in the room with the SpeakerTrack!

Here is the API reference guide just in case your curious on other commands: