Cisco Cisco TelePresence Video Communication Server Expressway
n
Deskphone control (QBE/CTI)
n
Additional mobility features including DVO-R, GSM handoff and session persistency
n
Self-care portal
n
Support for Jabber SDK
n
Shared lines are supported in a limited way. Multiple endpoints can share a line but in-call features (like
hold/resume) only work on the first endpoint that answers. Endpoints sharing the line may not correctly
recognise the state of the call.
hold/resume) only work on the first endpoint that answers. Endpoints sharing the line may not correctly
recognise the state of the call.
Unsupported features and limitations when using mobile and remote
access
access
n
Secure XMPP traffic between VCS Control and IM&P servers (XMPP traffic is secure between VCS
Control and VCS Expressway, and between VCS Expressway and remote endpoint)
Control and VCS Expressway, and between VCS Expressway and remote endpoint)
n
Calls involving secure endpoints remotely registered to Unified CM via VCS may end up with a portion of
the call using non-secure media; these portions will only ever be on sections of the call that are on premises
(between the VCS Control and endpoints registered locally to Unified CM), never on the public Internet
the call using non-secure media; these portions will only ever be on sections of the call that are on premises
(between the VCS Control and endpoints registered locally to Unified CM), never on the public Internet
n
Endpoint management capability (SNMP, SSH/HTTP access)
n
Multi-domain and multi-customer support; each VCS deployment supports only one IM&P domain (even
though IM & Presence 10.0 or later supports multiple IM&P domains)
though IM & Presence 10.0 or later supports multiple IM&P domains)
n
Mobile and remote access functionality is not within the FIPS boundary
n
The VCS Control used for Mobile and Remote Access cannot also be used as a Lync 2013 gateway (if
required, this must be configured on a stand-alone VCS Control
required, this must be configured on a stand-alone VCS Control
n
NTLM authentication via the HTTP proxy
n
XMPP federation managed directly by VCS Expressway (note that remote client access via VCS for
XMPP inter domain federation managed by CUP is supported)
XMPP inter domain federation managed by CUP is supported)
n
Maintenance mode; if a VCS-C or VCS Expressway is placed into maintenance mode, any existing calls
passing through that VCS will be dropped
passing through that VCS will be dropped
n
The VCS Expressway must not have TURN services enabled
n
The VCS Expressway DNS hostname must not contain underscore characters (it can only contain letters,
digits and hyphens)
digits and hyphens)
n
Deployments on Large VM servers are limited to 2500 proxied registrations to Unified CM (the same limit
as VCS appliances or equivalent VM)
as VCS appliances or equivalent VM)
Protocol summary
The table below lists the protocols and associated services used in the Unified Communications solution.
Protocol
Security
Service
SIP
TLS
Session establishment – Register, Invite etc.
HTTPS
TLS
Logon, provisioning/configuration, directory, visual voicemail
RTP
SRTP
Media - audio, video, content sharing
XMPP
TLS
Instant Messaging, Presence
Unified Communications: Mobile and Remote Access via Cisco VCS Deployment Guide (X8.1.1)
Page 28 of 36
Additional information