Setup for TelePresence Video Communication Server
Available Languages
Contents
- Setup for TelePresence Video Communication Server
- Prerequisites
- TMS setup for provisioning
- Defining device address pattern
- Setting up provisioning template and assigning it to users
- Understanding provisioning options
- VCS setup
- Firewall requirements
- Preparing user instructions
- Main types of communication
- SIP communication
- Media communication
- Changing port range in TMS
- Changing port range in VCS
- About Binary Floor Control Protocol (BFCP)
- Media routing
- Media routing with no ICE
- Media routing with ICE
- Turning on ICE
- TURN port for Jabber for iPad
- How communication works at sign-in?
- Specifying maximum time for registration refresh
- How communication works after sign-in?
- Connectivity checks
- Bandwidth probing
- Directory search
- Call setup
- Encryption
- Sent and received bandwidth
- Video resolution
- Outgoing video resolution
- Incoming video resolution
- Presentation resolution
- Video and audio standards
- ICE negotiation
- Actions during a call
- Multiway
- Mute media streams
- Automatic bandwidth adaptation
Setup for TelePresence Video Communication Server
This chapter provides comprehensive information about setting up Jabber for iPad using TelePresence Video Communication Server (VCS).
- Prerequisites
- TMS setup for provisioning
- Understanding provisioning options
- VCS setup
- Firewall requirements
- Preparing user instructions
- Main types of communication
- How communication works at sign-in?
- Specifying maximum time for registration refresh
- How communication works after sign-in?
- Directory search
- Call setup
- Actions during a call
Prerequisites
Perform these tasks:
- Ensure that your versions of the Cisco VCS and Cisco TMS (TelePresence Management Suite) meet the following requirements.
- Set up NTLM authentication with VCS and Jabber for iPad. For instructions, see the Cisco TelePresence Video Communication Server Authenticating Devices Deployment Guide for your release at http://www.cisco.com/en/US/products/ps11337/products_installation_and_configuration_guides_list.html.
TMS setup for provisioning
To deploy VCS on Jabber for iPad, provision the user devices with appropriate settings. You add and manage desired settings in TMS. The data is then transferred to the VCS, from which it is distributed to the devices through the Provisioning Server running on the VCS.
Perform these two required procedures to set up TMS for provisioning.
Defining device address pattern
Device address patterns are templates that TMS Provisioning Extension (TMSPE) uses to create addresses for provisioned devices. Assign device address patterns so that TMSPE can connect users to their devices.
To specify a device address pattern for Jabber for iPad, set the attribute {device.model} to jabbertablet. Optionally, add an alias conversion from jabbertablet to jabber to simplify naming.
For detailed instructions about creating address patterns, see the Cisco TelePresence Management Suite Provisioning Extension Deployment Guide at http://www.cisco.com/en/US/products/ps11472/prod_installation_guides_list.html.
Setting up provisioning template and assigning it to users
Jabber for iPad requires a specific template—an XML file containing all the possible settings supported by the application. After you download the template and upload it in TMS, you can then set up the template and assign it to groups of users.
For detailed instructions about each of the steps in the procedure, consult the appropriate documentation:
- If you are using the TMS Agent Legacy, included in TMS versions 13.2 and earlier, see the Cisco TelePresence Management Suite Agent Legacy Deployment Guide at http://www.cisco.com/en/US/products/ps11338/products_installation_and_configuration_guides_list.html.
- If you are using the TMS Provisioning Extension (TMSPE), included in TMS versions 13.2 and later, see the Cisco TelePresence Management Suite Provisioning Extension Deployment Guide at http://www.cisco.com/en/US/products/ps11472/prod_installation_guides_list.html.
Step 1 Download the template to your local server from http://www.cisco.com/cisco/software/navigator.html?mdfid=280443139&flowid=29241. Step 2 Upload the template or template schema in TMS. The term "template schema" is used in TMSPE while the term "template" is used in TMS Agent Legacy.
Step 3 Add these server addresses, in addition to any other necessary settings, in the template: Step 4 Assign the template to the appropriate groups of users. Any template you assign to a group is inherited by all users in the group, all subgroups, and all users in subgroups. You cannot assign a template directly to an individual user.
Understanding provisioning options
Provisioning allows you to specify settings that control how VCS works with Jabber for iPad. Upon subscribing to the VCS, Jabber for iPad receives provisioning information from the Cisco TMS Agent and acts on it.
This table explains the provisioning options that are applicable for Jabber for iPad and includes tips on how you can use them.
Field Default Description Bandwidth Prober Time 0 After a user signs in to Jabber for iPad, the application probes the TURN relay server for bandwidth quality between the app and TURN server. This option determines the duration of the probing in seconds:
The provisioned time is split into 256 KB/s intervals up to the maximum provisioned bandwidth.
Bandwidth Prober Auto Scheduling Off This option allows bandwidth probing. Bandwidth probing also requires these settings to be provisioned: ClearPath On ClearPath is a Cisco TelePresence solution that minimizes the negative effects of packet loss in a non-optimal network. Among the mechanisms used are H.264-specific error recovery techniques, feedback from decoders, and forward error correction (FEC).
Both call participants must be using devices that support ClearPath for it to take effect.
Default Mediatype Candidate Host This is the address to use
The available options are
- Host—the local network address
- Rflx—the corporate public IP address seen from outside of the organization's network (public IP)
- Relay—the address of the TURN relay server
You can use Relay if you are deploying Jabber for iPad in environments where most other devices do not understand ICE. See Turning on ICE for more information.
Detect Media Mangling On Detects whether a server in the network is trying to relay media Encryption Policy Auto Determines the encryption policy for the account. This option affects both the SIP communication (Transport TLS or TCP) and the media communication (SRTP or no SRTP).
ICE Off Interactive Connectivity Establishment (ICE) dynamically discovers the best possible path for media to travel among call participants.
See Turning on ICE for more information on what is required to turn on this setting.
IP version 4 Available options are
Note Do not force Jabber for iPad to use IPv6 unless all users are permanently on an IPv6 network. If you select 6, users who sign in over IPv4, for example from a home network, will be denied access.
Additionally, ICE is not supported with IPv6 for Jabber for iPad. If users sign in over an IPv6 connection, ICE will be disabled.
Maximum In Bandwidth 512 KB/s The value you specify determines the maximum bandwidth allowed in the user accounts for receiving and sending data. High bandwidth is directly related to good video quality. However, bandwidth control can prevent an application from trying to receive or send data beyond its capacity, which may result in packet loss, jitter, and low video quality.
Maximum Out Bandwidth 384 KB/s Media Port Range End 21900 The upper/lower bound of the port numbers that are used in the video and audio communication.
You can set these up to control security and firewall issues. You must specify a range of minimum of 10 ports; otherwise, Jabber for iPad will revert to default.
Media Port Range Start 21000 MNS Mode Off Enabling this option forces relayed media to be relayed via private HD links with guaranteed capacity to ensure quality of video.
This setting relies on ICE being enabled. Private dedicated links are provided by companies such as Media Network Services.
Multiple Server Connections Off Select this option to allow Jabber for iPad to keep open connections with several servers in a cluster and to failover by automatically transferring to the next server in the cluster if one server goes down. If one connection is lost, Jabber for iPad will then be reachable from multiple servers.
You can also turn on the option if SIP Outbound (RFC 5626) is supported.
Note VCS X6.0 or later is required for this option
Multiway Participant URI When Multiway is initiated, participants are directed to this Uniform Resource Identifier (URI). See Multiway for more information. Phone Book Server URI Allows the account to search for other accounts in the Cisco TMS Agent database.
Set up the URI in this format: phonebook@<sip_domain>.com
Important:If you do not specify any value, Jabber for iPad cannot search for contacts.
Presence Server URI Allows the account to send availability status to the VCS server.
Set up the URI in this format: presence@<sip_domain>.com
Note Jabber for iPad uses the availability status from Cisco WebEx Connect if a Connect server has been identified.
If you do not specify any value, Jabber for iPad cannot publish availability status and will appear offline.
Public Bandwidth Prober Auto Scheduling Uses the value set for Bandwidth Prober Auto Scheduling To turn on bandwidth probing, you must select On. Bandwidth probing also requires these settings to be provisioned:
Public Default Mediatype Candidate Uses the value set for Default Mediatype Candidate Changes dynamically
This is the address to use
The available options are
- Host—the local network address
- Rflx—the corporate public IP address seen from outside of the organization's network (public IP)
- Relay—the address of the TURN relay server
Cisco recommends that you use Relay if your users will connect from outside your organization's network. ICE negotiation can take a few seconds to complete, and using the TURN relay helps media flow through the firewalls from the beginning of the call.
Upon completion of ICE negotiation, media is redirected if a superior media path has been located. See Turning on ICE for more information.
Public IP version Uses the value set for IP Version
Changes dynamically
Available options are
Note Do not force Jabber for iPad to use IPv6 unless all users are permanently on an IPv6 network. If you select 6, users who sign in to the app over IPv4, for example from a home network, will be denied access.
Additionally, ICE is not supported with IPv6 for Jabber for iPad. If users sign in over an IPv6 connection, ICE will be disabled.
Public Maximum In Bandwidth Uses the value set for Maximum In Bandwidth
Changes dynamically
The value you specify determines the maximum bandwidth allowed for receiving and sending data after users sign in to the application using their VCS accounts.
The settings may be useful for controlling the bandwidth for users who connect from outside their organizations' networks. These users may have slow network connections or the company may want to limit their bandwidth usage.
Public Maximum Out Bandwidth Uses the value set for Maximum Out Bandwidth
Changes dynamically
Public Multiple Server Connections Uses the value set for Multiple Server Connections
Changes dynamically
Use this setting to allow Jabber for iPad to keep open connections with several servers in a cluster and to failover by automatically transferring to the next server in the cluster if one server goes down. If one connection is lost, Jabber for iPad will then be reachable from multiple servers.
You can also turn on the option if SIP Outbound (RFC 5626) is supported.
Note VCS X6.0 or later is required for this option
Public Phone Book Server URI Uses the value set for Phone Book Server URI
Changes dynamically
It is sufficient to set the Phone Book Server URI setting.
Public Presence Server URI Uses the value set for Presence Server URI
Changes dynamically
It is sufficient to set the Presence Server URI setting.
Public SIP Server Address Uses the value set for SIP Server Address
Changes dynamically
the server address to which a registration request is sent after users sign in with an external VCS server address
Generally, this information is the same as the external server address the users specify in Jabber for iPad.
Resolution Preferences High Restricts incoming and outgoing video resolution. Jabber for iPad overrides this value.
See Video resolution for more information.
The restrictions depend on many factors, but as a general rule
SIP Server Address the VCS server that Jabber for iPad is subscribed to the server address to which a registration request is sent
It is the same as the internal server address users specify in Jabber for iPad.
Tcp Media Relay Off Select one of these options: TurnAuthPassword TURN server settings that are required for enabling ICE. See Turning on ICE for more information. TurnAuthUsername TurnServer VCS setup
Review this topic if you use the registration Allow List or search rules.
In order for the user devices to work with the VCS, the devices must first register with the VCS. The suffix in the registration URIs for Jabber for iPad users is .jabbertablet or .jabber. For example, a user's URI may be in this format with the new suffixes: userName.jabbertablet@DomainName or userName.jabber@DomainName. Because of the URI suffix additions, you may need to make these changes:
- Update the registration Allow List () to allow the new URI suffixes. Example: If you have deployed both VCS and VCSE (VCS Expressway) and used the Allow List to control registration from external locations, add the new suffixes to the Allow List.
- Update or create search rules to include the new URI suffixes. In creating search rules, specify a pattern string that resembles the format .+\.(jabbertablet|jabber).*@%localdomains%.*. Example: If you have multiple VCS clusters (zones) within your organization, you may have to update the rules that control call routing between the VCS and VCSE zones.
Firewall requirements
For Jabber for iPad to work properly, set up hardware firewalls to allow the ports to carry traffic for the application. Hardware firewalls are network devices that provide protection from unwanted traffic at an organizational level. This table lists the ports required for the deployment of VCS. These ports must be open on all firewalls for the application to function properly.
Preparing user instructions
To provide users with the information they need to use VCS in Jabber for iPad, send a customized email message from the TMS to the users. The default email template contains a simple message and the username and password.
Also include the following information in your email message:
- The internal and external server addresses. If your users are dispersed on different VCS clusters, ensure to communicate the correct server addresses to the different groups of users.
- The SIP domain address
- Directions to download and install the app, named "Cisco Jabber for iPad," from the App Store
- Directions to access the FAQs, which users can view by selecting
- Anything else you may want to communicate with your users
To learn more about sending account information from the TMS, consult the appropriate documentation:
- If you use the TMS Agent Legacy, see the Cisco TelePresence Management Suite Agent Legacy Deployment Guide at http://www.cisco.com/en/US/products/ps11338/products_installation_and_configuration_guides_list.html.
- If you use the TMS Provisioning Extension (TMSPE), see the Cisco TelePresence Management Suite Provisioning Extension Deployment Guide at http://www.cisco.com/en/US/products/ps11472/prod_installation_guides_list.html.
Main types of communication
Review these topics to understand the main types of communication for VCS on Jabber for iPad.
SIP communication
Jabber for iPad communicates with the VCS using Session Initiation Protocol (SIP). With the exception of video and audio, SIP is responsible for all communications, including subscribing, registering, availability querying, and call invitations. SIP messages are sent by TCP, with or without TLS encryption, depending on the provisioned settings.
The default SIP listening ports used in the VCS are
To change those listening ports, go to .
Note
Jabber itself uses ephemeral TCP ports for these communications. These ports are handed over to Jabber for iPad by the TCP stack and are not configurable.
To enable communication with devices that rely on H.323 and do not support SIP, interworking on the Cisco VCS can be used.
Media communication
Media data is transferred through up to nine UDP links (ports). These are the media streams used in Jabber for iPad:
- audio
- primary video
- secondary video (presentation sharing)
- BFCP (management of presentation sharing). See also About Binary Floor Control Protocol (BFCP).
With the exception of BFCP, each of these streams requires two links—one link for RTP packets and one link for RTCP packets. The SRTP protocol is used if encryption is enabled.
Changing port range in TMS
The default port range for Jabber for iPad to receive media is 21,000-21,900. You can change the range in the TMS.
Note
The port numbers used are consecutive, but they are chosen randomly within the specified range.
Step 1 Go to Step 2 Specify your range using Media Port Range Start and Media Port Range End. Specify a minimum range of 10 ports; otherwise, the default range is used.
Changing port range in VCS
The default port range used on the VCS is 50,000-52,399. You can change it.
Note
The port numbers used are consecutive, but they are chosen randomly within the specified range.
Step 1 Go to . Step 2 Specify your range using Traversal media port start and Traversal media port end. Specify a minimum range of 10 ports; otherwise, the default range is used.
About Binary Floor Control Protocol (BFCP)
Jabber for iPad supports single BFCP streams from multipoint control units (MCUs) for handling the control of presentation sharing. BFCP communication can be sent over a UDP or a TCP link. Jabber for iPad uses the same ports as for audio and video for this communication.
On the VCS, a port is chosen randomly from the same range that has been assigned to the media links.
Media routing
Jabber for iPad supports Interactive Connectivity Establishment (ICE) for better media routing. During a call, ICE is used if enabled for all participants' applications. Review these topics to learn more.
Media routing with no ICE
Media links can be established directly between two devices in non-traversal calls or between Jabber for iPad and the VCS in traversal calls. As a general rule, non-traversal calls are defined as calls between two participants that are on the same network and do not require interworking.
SIP-to-H.323 calls require interworking. Such calls are traversal calls, whether or not the devices are on the same network. For details, see the Cisco TelePresence Video Communication Server Administrator Guide for your VCS release at http://www.cisco.com/en/US/products/ps11337/prod_maintenance_guides_list.html.
Media routing with ICE
ICE dynamically discovers the best possible path for media to travel among call participants. You can improve the routing of media and force it through dedicated links by using the Enable MNS Mode provisioning setting.
Turning on ICE
Set up Cisco VCS Expressway in order to turn on ICE.
Media routing using ICE requires a TURN server. VCS Expressway running version X5.2 or later can function as a TURN server if it has TURN Relay licenses. The TURN server option key is required.
Note
ICE provisioning is not available by default.
TURN port for Jabber for iPad
TURN port setup should be controlled through DNS. Jabber for iPad does an SRV lookup for the TURN IP, priority, weight, and port. As TURN runs over UDP, the lookup is for _turn._udp.<domain>. If no SRV record for TURN is found, Jabber performs an A record lookup (IPv4) or an AAAA lookup (IPv6) but defaults to port 3478.
If the port needs to be provisioned, you can append it to the IP address in the TurnServer field, for example 192.0.2.0:3478.
How communication works at sign-in?
Upon signing in to Jabber for iPad, users specify the internal and external VCS server addresses. The application first attempts to subscribe to the internal address. In such situations as the iPad device being connected to non-corporate Wi-Fi, the application then tries to subscribe to the external address.
If the internal VCS server address is a DNS address that translates to more than one IP address, the application attempts to connect to all these IP numbers before trying the external VCS server address. If the DNS server contains SRV records, the application adheres to the priority and weight of the IP addresses; otherwise they are tried in a random order.
Typically, the VCS or the TMS Agent challenges the first subscription message. The application answers this challenge by sending another SUBSCRIBE message with the authentication information.
After the subscription has been authenticated, the TMS Agent sends provisioning information to the application.
The application registers to the VCS according to the provisioning information for SIP Server URI or Public SIP Server URI in the TMS. If this provisioning information is identical to the internal and external VCS server addresses users specify upon signing in (Cisco recommends that they are identical.), the application registers to the same VCS it subscribes to. As long as the application is registered, the VCS knows to forward messages to the application.
After initial registration, the application continues to send registration messages to the VCS according to the Standard registration refresh maximum (seconds) setting in the VCS server. The application sends the messages after 75% of the specified time interval has elapsed.
Specifying maximum time for registration refresh
When a user temporarily leaves Jabber for iPad to do something else on the device, the application goes into the background and is set to wake up every 10 minutes. You must set the maximum value for a standard SIP registration refresh period to 900 so the application can continue registering to the VCS server.
Step 1 In the VCS server, go to . Step 2 In the "Registration controls" section, enter 900 for Standard registration refresh maximum (seconds). Step 3 Select Save.
How communication works after sign-in?
After users sign in to Jabber for iPad, the application continuously performs these tasks.
Connectivity checks
Jabber for iPad uses DNS to find TURN servers and ports after users sign in to the application. If specified in the SRV records and supported by the TURN server, the application can use any port, including 80 (HTTP) and 443 (HTTPS).
The application looks for ports in the following order:
If no ports are detected, the application defaults to ports 3478 and 5349.
Note
Firewall traversal using TCP relay is not supported if you use the VCS as a TURN server at this time.
Bandwidth probing
If bandwidth probing is provisioned, Jabber for iPad routes dummy media to the TURN server and back from the server after users sign in to the application. This functionality relies on a TURN server being successfully provisioned.
The results of bandwidth probing are used for the application's dynamic resource adaptation. The results also depend on the provisioned time for probing and in many cases represent a "worst case" bandwidth scenario in which more bandwidth may be available during an actual call.
Directory search
Every time a user types a character in the search field of Jabber for iPad, the application queries the TMS Agent on the VCS, and the TMS Agent answers with matching results. When a search result is selected, the application also queries the VCS for the availability of the contact.
Call setup
Call setup is communicated by SIP messages passed through the VCS. Review these topics to learn how attributes of a call are determined during call setup.
Encryption
For a call to be encrypted, both the SIP and the media communication must be encrypted, and all parties must support encryption. Encrypted media communication is sent by the Secure Real-time Transport Protocol (SRTP) with 128-bit Advanced Encryption Standard (AES).
You can specify these encryption policy settings by going to in the TMS:
- Force TLS/TCP—Determines whether the SIP communication is encrypted (TLS) or not (TCP). The TLS version used by Jabber for iPad is currently 1.0.
- Force/No Srtp—Determines whether the media communication is encrypted or not.
- Auto—Jabber for iPad tries to have an encrypted call. If not possible, the application allows the call to be unencrypted.
Sent and received bandwidth
During call setup, Jabber for iPad signals the maximum bandwidth it wants to receive according to the settings in the server. It is up to the system on the other end of the call to respect this signaling.
Both the maximum bandwidth to be sent during a call and the bandwidth sent at the start of a call are determined during call setup.
During a call, the application can send more or less bandwidth, but the sent bandwidth never goes beyond the maximum bandwidth decided during call setup.
Video resolution
The Resolution Preferences setting in provisioning controls the resolution for both incoming and outgoing video. See Understanding provisioning options. It is up to the systems used by the other participants in a call to obey restrictions on incoming video.
Many factors contribute to good video quality. Frame rate, high image resolution, scene lighting, and optical quality of the cameras used in a call are all important factors.
Outgoing video resolution
Jabber for iPad uses these criteria when determining the resolution when it sends video:
- the resolution in native format from the camera
- The resolution must be permitted by the receiving end.
- Sending high resolution at low bandwidth results in poor quality. The bandwidth sent must be sufficient for the resolution. See these guidelines:
Increasing bandwidth improves image quality. You can specify bandwidth permissions using Maximum Out Bandwidth. For more information, see Understanding provisioning options.
If a high resolution is not achieved despite sufficient bandwidth as described above, this can usually be attributed to one or both of the following:
Incoming video resolution
You can specify bandwidth permissions for incoming video by using Maximum In Bandwidth in provisioning. For more information, see Understanding provisioning options. The bandwidth required for incoming high-resolution video varies with the capabilities and limitations of the device of each call participant.
Note
If a participant device is capable of sending high-resolution video and you specify no restrictions on bandwidth for incoming video, network connection issues, such as packet loss, may still cause incoming video to achieve less-than-desired resolution.
Presentation resolution
The maximum resolution for a shared presentation is dependent on the available bandwidth and the capabilities of the devices of the call participants. For a Jabber-to-Jabber call using unlimited bandwidth, the presentation resolution is 448 p.
You cannot change the resolution for presentations.
Actions during a call
After a call has been set up, a number of actions can be prompted in Jabber for iPad, either as a result of a user action or as an automated response to changing conditions. Review these topics to learn more.
Multiway
Multiway is the ability for a user to join a call and seamlessly create a multi-participant conference. Jabber for iPad cannot initiate multiway. If multiway is initiated from devices that other participants are using, the call is redirected to a multi-conference system according to the Multiway Participant URI provisioning option.
Mute media streams
If a camera or microphone is muted during a call, Jabber for iPad allocates the bandwidth for the other media links to use. If a user does not have enough bandwidth for two streams, it is possible to mute one stream and improve the quality of the other stream.
To prevent the unused link from being closed, for example by a firewall, the application sends STUN (keep alive) messages every 7 seconds.
Automatic bandwidth adaptation
In situations where Jabber for iPad is sending or receiving bandwidth that exceeds the network capabilities, high packet loss may occur and the user may experience poor call quality. The application uses automatic bandwidth adaptation mechanisms to tackle such bandwidth issues.
Note
Automatic adaptations take time. Cisco recommends that you set up the application to fit the network and system capabilities.
Feedback