Cisco VCS Expressway Starter Pack Cisco TelePresence Deployment Guide Cisco VCS X5.1 D14618.
Contents Contents Introduction ............................................................................................................................4 Purpose of this guide............................................................................................................................... 4 Related documents .......................................................................................................................... 5 Configuring the Cisco VCS .................................
Contents Modifying a user’s display name ........................................................................................................... 25 Appendix 5 – Characters allowed in SIP URIs...................................................................26 Appendix 6 – Determining the FindMe ID for a caller .......................................................27 Cisco VCS Deployment Guide: Cisco VCS Expressway Starter Pack (X5.
Introduction Introduction A Cisco TelePresence Video Communications Server (Cisco VCS) with the Starter Pack option key creates a Cisco VCS Expressway Starter Pack which acts as a standalone provisioning server, registrar and proxy server for Movi endpoints. The Cisco VCS Expressway Starter Pack may have endpoints register to it locally or register to it from behind a home, small business or hotel firewall.
Introduction Related documents Document number Title D14049 Cisco VCS Administrator Guide D14088 FindMe™ User Guide D14427 Provisioning troubleshooting guide D14525 Cisco VCS Deployment Guide – FindMe™ Cisco VCS Deployment Guide: Cisco VCS Expressway Starter Pack (X5.
Configuring the Cisco VCS Configuring the Cisco VCS This deployment guide assumes that the Cisco VCS is accessible on an IP network and has had a basic configuration implemented. This means that the Cisco VCS has been configured with: IP details DNS details NTP server details Note: Brief instructions on how to carry out this configuration is available in ‘Appendix 1 – Basic Cisco VCS configuration’ on page 18.
Configuring the Cisco VCS Configure the routable address of the Cisco VCS The routable address of the Cisco VCS (its FQDN) is the address supplied by the provisioning system to the provisioned device (Movi) for it to use as its SIP registrar (the address to which it sends registration requests). 1. Go to the Clustering page (VCS configuration > Clustering). 2. Configure the fields as follows: Cluster name (FQDN for Provisioning) 3.
Configuring the Cisco VCS Enable FindMe™ 1. Go to the FindMe configuration page (Applications > FindMe > Configuration). 2. Configure the fields as follows: FindMe mode 3. On Configure the fields as follows: Caller ID FindMe ID: the caller ID of a call being made through this Cisco VCS is replaced with the relevant FindMe ID. Note: For more details on the use of Caller ID and FindMe ID, see “Appendix 6 – Determining the FindMe ID for a caller” on page 27. 4. Click Save.
Configuring the Cisco VCS Enable presence server (optional) The presence server allows Movi clients to see the presence status (Online, Away, Busy in a call and Offline) of other Movi clients. 1. Go to the Presence page (Applications > Presence). 2. Configure the fields as follows: SIP SIMPLE Presence Server 3. On Click Save. Create user accounts You must configure an account for each user: 1. Go to the User accounts page (Maintenance > Login accounts > User accounts) and click New.
Configuring the Cisco VCS 2. Configure the fields as follows: Username The username for logging into this user account, for example name.surname. Note that the username is case sensitive. This same username must be used as the name in the local authentication database if device authentication is enabled. This username is also used to create the FindMe default device URI and the provisioned device URI.
Configuring the Cisco VCS See “Create authentication credentials for the user (optional)” below for more details. ** The password entries are only displayed if User authentication source is set to Local (see “Enable FindMe™“ on page 8.) 3. Click Save. 4. Repeat these steps to create accounts for all users. Additional users can be added later, as and when required, by returning to the User accounts page and selecting New. Note: Cisco VCS Expressway Starter Pack supports a maximum of 50 registered users.
Configuring the Cisco VCS Configure bandwidths provisioned to Movi clients (optional) The Cisco VCS can provision bandwidth limits to Movi clients. These are used to configure Movi with default values for it to use for incoming and outgoing bandwidth control. 1. Go to the Provisioning page (Applications > Provisioning). 2. Set Provision bandwidth limits to On. 3. 4. 5. Check and set the Maximum incoming bandwidth for Movi (e.g. 512kbps). Check and set the Maximum outgoing bandwidth for Movi (e.g.
Installing and configuring Movi Installing and configuring Movi As part of the Cisco TelePresence Movi Starter Pack – Express Edition solution, a Movi software client installation pack will be supplied. Movi can be installed by IT administrators, or more typically will be supplied to end users for them to install. After Movi has been installed, it must be configured with user credentials and connection details for the Cisco VCS Expressway Starter Pack: 1. Start Movi. 2. Click Advanced. 3.
Installing and configuring Movi 4. Click OK to return to the Movi sign in page. 5. Configure the fields as follows: 6. Username The same username as entered on the Cisco VCS in the Create user account page (Maintenance > Login accounts > User accounts). Password If device authentication is enabled this must be the same password as the authentication credential password entered for this user (VCS configuration > Authentication > Devices > Local database).
Installing and configuring Movi Making calls When you are signed in to Movi, calls can be made by entering the FindMe ID of another user in the Type name, number or address field and then pressing Enter. Cisco VCS Deployment Guide: Cisco VCS Expressway Starter Pack (X5.
Testing the Cisco VCS Expressway Starter Pack installation Testing the Cisco VCS Expressway Starter Pack installation Local system testing Start by testing Movi devices locally registered to the Cisco VCS Expressway Starter Pack. 1. Configure three users. 2. Install three Movi clients. 3. Connect the three Movi PCs to the same network as the Cisco VCS Expressway Starter Pack. 4.
Testing the Cisco VCS Expressway Starter Pack installation Behind home, small business or hotel firewall testing When public network testing is successful, test Movi behind a firewall. 1. 2. Sign out of the two Movi clients in the public network and connect them behind a home, small business or hotel firewall. With the Movi clients sign connected behind the firewall, sign in as User2 and User3: Ensure that sign in is successful.
Appendix 1 – Basic Cisco VCS configuration Appendix 1 – Basic Cisco VCS configuration Follow the process specified in the “Cisco VCS Getting Started Guide” to connect, power up, configure the IP address, change passwords and gain access to the Cisco VCS via the web browser. System name 1. Go to System configuration > System and set System name to a name that represents this Cisco VCS, for example “VCS Movi server”. 2. Enable or disable Telnet, SSH, HTTP and HTTPS as required.
Appendix 2 – Troubleshooting Appendix 2 – Troubleshooting Movi sign in messaging If there are problems signing in to Movi, a status message will be displayed, for example: Possible messages include: Login failed – Wrong username, domain, and / or password Check and correct these items either at the Movi login, or on the Cisco VCS. - Mis-typed domain names are a common cause of this problem (see VCS Configuration > Protocols > SIP > Domains).
Appendix 2 – Troubleshooting Login failed – The server did not respond in time This means the provisioning request was acknowledged by the server, but no provisioning message was received by Movi. Make sure that no firewalls are blocking communication from the Cisco VCS to Movi. Make sure that the Cisco VCS can contact the IP address of the Movi (or if behind a home, small business or hotel firewall, the outside IP address of that firewall).
Appendix 2 – Troubleshooting Call failed – The user could not be reached. Please try again later. The user did not respond. Call failed – An error was received from the server The call was rejected by the Cisco VCS. The error message received from the server is in the user’s Audit.log. See the Movi troubleshooting section in the Cisco TMS Provisioning troubleshooting guide. Call failed – Not enough call licenses All available licenses may already be in use.
Appendix 2 – Troubleshooting OK (to register) To: .ep@ To: .ep@ Subscribe To:provisioning@ From: @ Event: ua-profile OK (to subscribe) To:provisioning@ From: @ Event: ua-profile … may be any time … maybe any time following subscribe for presence Subscribe To:@ From: .ep@ Event: presence OK (to subscribe) To:@ From: .
Appendix 2 – Troubleshooting When Movi looks for phone book information the message flow is: Movi Cisco VCS INFO To: sip:phonebook@ From: @ Content-Type: application/tandbergphonebook+xml Unauthorised To: phonebook@ From: @ www-authenticate: Digest nonce INFO To: sip:phonebook@ From: @ Authorization: Digest nonce Content-Type: application/tandbergphonebook+xml
Appendix 3 – Comparison of Cisco VCS Expressway Starter Pack provisioning and Cisco TMS provisioning Appendix 3 – Comparison of Cisco VCS Expressway Starter Pack provisioning and Cisco TMS provisioning Cisco VCS Expressway Starter Pack Provisioning Cisco VCS with Cisco TMS Provisioning and Management Centralized 50 Centralized/Distributed 2500 per Cisco VCS Failover No of concurrent calls 5 Registration capacity 50 Presence server Interworking gateway 50 registrations Up to 5
Appendix 4 – Known limitations Appendix 4 – Known limitations Modifying a user’s display name Any change to a user account Display name is immediately reflected in phone books and the display name returned in FindMe searches. However, the caller ID display name in SIP messaging is only updated after the relevant Movi is reprovisioned (for example, after signing out and signing back in again). Cisco VCS Deployment Guide: Cisco VCS Expressway Starter Pack (X5.
Appendix 5 – Characters allowed in SIP URIs Appendix 5 – Characters allowed in SIP URIs The following character set is allowed in SIP URIs (further details may be found in RFC 3261): a-z / A-Z / 0-9 / "-" / "_" / "." / "!" / "~" / "*" / "'"/ "(" / ")" "&" / "=" / "+" / "$" / "," / ";" / "?" / "/" If other characters are needed they must be “escaped” using "%" HexDigit HexDigit where HexDigit HexDigit is the ASCII value for the required character. e.g. steve%20hight@company.
Appendix 6 – Determining the FindMe ID for a caller Appendix 6 – Determining the FindMe ID for a caller Cisco VCS can only overwrite the Caller ID with a FindMe ID if: the call signaling passes through the Cisco VCS / Cisco VCS cluster where the FindMe data is held the Cisco VCS can identify a FindMe as the owner of the endpoint caller ID If either of these conditions are not met, the incoming caller ID will be passed through unchanged.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
