Cisco Video Conferencing

Space CE controls a Cisco RoomOS codec so that room users join and run meetings from the room touch panel instead of the codec’s own interface. The codec keeps its registration, calendar and media handling; Space CE connects to it over SSH and keeps the panel in step with it. This page covers what a room gets, what the codec needs, how to configure it and what users see.

Capabilities

These are the elements Space CE makes available to the touch panel when the feature is enabled. Each client’s interface presents the subset it was built for, laid out and labelled in its own way. Available from Space CE v2.16.0 unless a later version is specified.

Prerequisites

• Codec. A Cisco RoomOS codec.
• Firmware. xAPI JSON output mode support. Verified on RoomOS 11.40 and RoomOS 26.8.
• SSH. SSH enabled and a local user with the Admin role for Space CE. The Space CE host needs TCP port 22 to the codec; the panel never talks to the codec directly.
• Registration and calendar. Scheduled meetings need a calendar connected to the codec’s workspace.

Configuration

Add the codec as a device, then fill in the Conferencing section.

Codec device

Under Devices, add the codec with the Cisco Codec (SSH) driver, its IP address and device credentials. The codec’s camera is a separate device using the Cisco Camera (SSH) driver with the same IP address and credentials, referenced from Camera Sources.

Conferencing section

Codec as an audio channel

A Microphones channel whose Mute targets the codec makes the room’s microphone mute drive and follow the codec’s. A Program Audio channel on the codec controls speaker volume and mute. The codec has no block IDs, so only the device ID is given. See Audio Sources.

"Audio Sources": {
  "Program Audio": [
    {
      "ID": "program.audio.1",
      "Name": "Codec Speakers",
      "Level": { "Device ID": "dev.codec.1", "Minimum": 0, "Maximum": 100 },
      "Mute": { "Device ID": "dev.codec.1", "Startup Action": "Unmute", "Shutdown Action": "Mute" }
    }
  ],
  "Microphones": [
    {
      "ID": "mic.codec.1",
      "Name": "Codec Microphone",
      "Mute": { "Device ID": "dev.codec.1", "Startup Action": "Unmute", "Shutdown Action": "Mute" }
    }
  ]
}

On the touch panel

Each client’s touch panel interface presents conferencing in its own way: screens, labels and navigation differ between deployments, and an interface may leave out elements its rooms do not use. What follows describes each element as Space CE provides it.

Scheduled meetings. Upcoming meetings from the codec’s calendar are listed with title, organiser and time, and can be joined from the list. Bookings without a dial-in address, such as in-person meetings, cannot be joined.

Joining by meeting ID. The user picks the platform and enters the meeting ID, called the meeting number on Webex and the meeting code on Google Meet, plus a passcode where the platform uses one. For Teams a video ID can be entered instead, with the room’s tenant filled in from the codec.

Dialling and contacts. Where direct dialling is enabled, the user can search the directory by name or type an address, then dial.

Incoming calls. A prompt shows the caller’s name with accept and reject. The codec rings whether or not the room is on; the prompt appears while the room is on.

In a call. The panel shows the meeting title, organiser and end time, with controls for microphone mute, camera mute, sharing, layout, keypad and ending the call. Sharing and keypad are offered only when the meeting supports them; Teams meetings offer neither. Layout names come from the codec and vary by platform. A footer indicator shows call and mute state from every tab.

Meeting PINs. If the meeting asks for a PIN, the panel prompts for it. A rejected code shows an error and the user can enter it again. Closing the prompt leaves the meeting.

Wireless sharing. When the user selects the room’s wireless source, the panel explains how to connect and shows the codec’s current pairing code for the Webex app or the Webex web sharing page. Space CE updates the code as the codec rotates it, so the code on the panel matches the one the codec accepts.

Appendix: technical reference

Join failure reasons

From v2.24.0 a join that does not connect is reported to the panel with one of these reasons. A call that connected and then ended is never reported as a failure, and neither is a missed incoming call or a call the user ends while it is still dialling.

Automation surface

The conferencing manager publishes CallStatus with the values Idle, Dialling, Ringing and InCall. Macro triggers read it under the guid conferencing.manager; visibility conditions and macro scripts read it as conferencing.CallStatus. A dial that never connects stays Dialling until it tears down, so InCall only ever means a call that connected. Macro scripts can call conferencing.PerformConferencingAction("..."), conferencing.JoinConferencingMeeting("...") and conferencing.SetConferencingLayout("..."); the accepted actions are listed on Available Actions, and the Macros page has a worked example.

Diagnostics

Related Articles

• Creating a Space CE Template
• Devices
• Audio Sources
• Macros
• Visibility Condition
• Space CE v2.16.0 Release Notes