Table Of Contents
Configuring Cisco Unified Videoconferencing Solution Components
How to Configure a Cisco Unified Videoconferencing Desktop Server
Desktop Meeting Control Server
Desktop Recording Server
Desktop Streaming Server
Configuring Basic Cisco Unified Videoconferencing Desktop Server Settings
Configuring Meeting Access Instructions
How to Configure a Cisco Unified Videoconferencing 3500 MCU
Performing Basic MCU Configuration
Configuring the Auto-Attendant Feature in Multiple-MCU Deployments
Configuring a Cisco Unified Videoconferencing 3500 Series Gateway
How to Configure a Cisco Unified Videoconferencing Manager
Performing Basic Cisco Unified Videoconferencing Manager Configuration
Configuring an Auto-Attendant Session
How to Configure Solution Components for Recording
Configuring Cisco Unified Videoconferencing Desktop Server for Recording
Desktop Recording Server Connection
Configuring this Cisco Unified Videoconferencing Desktop Server to Manage Recording
Configuring an Alternate Cisco Unified Videoconferencing Desktop Server to Manage Recording
Configuring Recording Parameters
Disabling the Automatic Recording Feature
Configuring Cisco Unified Videoconferencing Manager for Recording
Allowing Recording by Specified Roles
Allowing Recording by Specified Users
Enabling Recording for Specified Virtual Rooms
Configuring a Gatekeeper
How to Configure a Cisco Unified Videoconferencing Desktop Server to Allow Streaming
Desktop Server Limitations
Enabling Streaming Over Port 7070
Configuring Streaming for Playback Using the UDP Connection
How to Enable Streaming or Recording Playback Over Port 80
Binding a Cisco Unified Videoconferencing Streaming Server
Enabling Streaming or Recording Playback Over Port 80
Binding an Apache Tomcat to a Specific IP Address
How to Configure Third-Party Equipment
Configuring a Firewall
Firewall Guidelines to Support the Cisco Unified Videoconferencing Solution
Ports to Open in the Firewall to Allow Streaming
Load Balancing Deployments
Persistence
Dispatch Methods
Health Check
Configuring Cisco Unified Videoconferencing Solution Components
•
How to Configure a Cisco Unified Videoconferencing Desktop Server
•How to Configure a Cisco Unified Videoconferencing 3500 MCU
•Configuring a Cisco Unified Videoconferencing 3500 Series Gateway
•How to Configure a Cisco Unified Videoconferencing Manager
•How to Configure Solution Components for Recording
•Configuring a Gatekeeper
•How to Configure a Cisco Unified Videoconferencing Desktop Server to Allow Streaming
•How to Configure Third-Party Equipment
How to Configure a Cisco Unified Videoconferencing Desktop Server
This section describes how to perform a basic Cisco Unified Videoconferencing Desktop Server configuration after the Cisco Unified Videoconferencing Desktop Server is installed. After this configuration is performed, Cisco Unified Videoconferencing Desktop Server is operational and ready to be used for video calls.
•Desktop Meeting Control Server
•Desktop Recording Server
•Desktop Streaming Server
•Configuring Basic Cisco Unified Videoconferencing Desktop Server Settings
•Configuring Meeting Access Instructions
Desktop Meeting Control Server
Configure the type of server used for moderation of Desktop meetings according to the following recommendations:
•For a simple deployment including a single MCU, configure the MCU.
•For deployments containing Desktop with multiple MCUs but without Cisco Unified Videoconferencing Manager, you can connect to multiple MCUs but you do not have moderation control. Without Cisco Unified Videoconferencing Manager, the MCUs do not cascade MCUs into virtual meetings.
•For more complex deployments, select the Cisco Unified Videoconferencing Manager.
Alternatively, you can configure Desktop to work without a meeting control server in a multiple MCU deployment.
Note When you configure Desktop to work with Cisco Unified Videoconferencing Manager, participants can access their own virtual room settings via the Virtual Room button in the Preferences screen on the Desktop entry page.
Desktop Recording Server
Recording can be managed either by a single Cisco Unified Videoconferencing Desktop Server or by multiple Cisco Unified Videoconferencing Desktop Servers.
If a single Cisco Unified Videoconferencing Desktop Server is set to manage recording, only participants connected through that Cisco Unified Videoconferencing Desktop Server can start or stop recording. In this case other Cisco Unified Videoconferencing Desktop Servers in the deployment can be configured to display the list of recordings from the Cisco Unified Videoconferencing Desktop Server configured to manage recording.
If multiple Cisco Unified Videoconferencing Desktop Servers are configured to manage recording, they manage recording independently causing each Desktop portal to display its own list of recordings.
To designate a single Cisco Unified Videoconferencing Desktop Server to manage recording, enable recording on this Cisco Unified Videoconferencing Desktop Server. In this case you must disable recording on other Cisco Unified Videoconferencing Desktop Server in the same deployment, and enable them to allow playback of recordings from an alternate Cisco Unified Videoconferencing Desktop Server in order to display a list of recordings in the portal.
To enable multiple Cisco Unified Videoconferencing Desktop Server for managing recording, enable recording on each Cisco Unified Videoconferencing Desktop Server in this deployment.
Desktop Streaming Server
Streaming can be managed either by a single Cisco Unified Videoconferencing Desktop Server or by multiple Cisco Unified Videoconferencing Desktop Servers. If a single Cisco Unified Videoconferencing Desktop Server is set to manage streaming, all other participants are directed to this server. If multiple Cisco Unified Videoconferencing Desktop Servers are configured to manage streaming, they manage streaming independently.
To designate a single Cisco Unified Videoconferencing Desktop Server to manage streaming, enable streaming on this Cisco Unified Videoconferencing Desktop Server. In this case you must disable streaming on other Cisco Unified Videoconferencing Desktop Servers in the same deployment. However, you can configure those server to allow watching of webcasts from the Cisco Unified Videoconferencing Desktop Server on which streaming is enabled.
To enable multiple Cisco Unified Videoconferencing Desktop Servers for managing streaming, enable streaming on each Cisco Unified Videoconferencing Desktop Server in this deployment.
Note When multiple Cisco Unified Videoconferencing Desktop Servers manage streaming, streaming must be enabled or disabled on each individual Cisco Unified Videoconferencing Desktop Server. For example, if streaming is enabled for a meeting or virtual room, a moderator cannot disable it, because each Cisco Unified Videoconferencing Desktop Server manages streaming independently. If a moderator connected to one Cisco Unified Videoconferencing Desktop Server disables streaming, the other Cisco Unified Videoconferencing Desktop Server still continues to stream, unless it is disabled by its moderator as well.
Configuring Basic Cisco Unified Videoconferencing Desktop Server Settings
Procedure
Step 1 Access the Cisco Unified Videoconferencing Desktop Server Administration interface using the following URL: http://<ip_address:port>cuvcmrm/admin.
Step 2 Enter your user name and password.
Note The default user name and password are both "admin".
Step 3 Click Next to begin the configuration wizard.
Step 4 Configure these settings on the Server Settings page:
a. Enter the IP address of the gatekeeper in the Gatekeeper IP Address field.
b. If necessary, modify the IP address of the Desktop Network Interface.
c. Click Next.
Note In a deployment with a single Cisco Unified Videoconferencing 3500 MCU, use the same gatekeeper as the Cisco Unified Videoconferencing 3500 MCU is configured to use. If you install Cisco Unified Videoconferencing Manager as a part of your deployment, specify the Cisco Unified Videoconferencing Manager Internal Gatekeeper.
Step 5 Specify the server used for moderation of Desktop meetings on the Meeting Control page.
a. To use Cisco Unified Videoconferencing Manager as your meeting control server, perform the following:
–Select Cisco Unified Videoconferencing Manager from the list.
–Enter the Cisco Unified Videoconferencing Manager IP address in the Address field.
–To configure the HTTP port, enter the port number in the HTTP port field. It must be the same port number as used during the Cisco Unified Videoconferencing Manager installation.
Note For deployments in which Cisco Unified Videoconferencing Desktop Server and Cisco Unified Videoconferencing Manager are installed on the same server, we recommend that you use the default port (8080).
–Enter the H.323 ID for Desktop which matches the H.323 ID configured in the Cisco Unified Videoconferencing Manager.
b. To use Cisco Unified Videoconferencing 3500 MCU as your meeting control server, perform the following:
–Select Cisco Unified Videoconferencing 3500 MCU from the list.
–Enter the Cisco Unified Videoconferencing 3500 MCU IP address.
–Enter the user name and password used to access the Cisco Unified Videoconferencing 3500 MCU Administration web user interface.
c. Click Next to continue.
Note You must use the specific IP addresses, not loopback addresses.
Step 6 Configure recording on the Recording Server page.
a. To enable recording and select a server to manage recording:
–Select Enable recording from the list.
–Enter the IP address of the Recording Server.
–Enter an FQDN in the Public Address field.
Note We recommend that you use an FQDN that clients can resolve.
–Select the IP address from the CUVC Desktop Network Interface list.
The Desktop Server uses this IP address for communications with Cisco Unified Videoconferencing Streaming Server and TCP Proxy.
–Enter the TCP port.
–This port is used by clients to access the recording in case a UDP connection fails.
Note You must configure the TCP port on the Cisco Unified Videoconferencing Streaming Server and open this port on the firewall.
b. To disable recording, select Disable recording from the list.
c. Click Next.
Step 7 Configure streaming on the Streaming Server page.
a. To enable streaming and select a server to manage streaming:
–Select Enable streaming and define the Cisco Unified Videoconferencing Desktop Server that you are currently configuring as the Cisco Unified Videoconferencing Desktop Server that is enabled for streaming.
–If you install the Cisco Unified Videoconferencing Streaming sever on a separate server, enter the IP address of that server in the Cisco Unified Videoconferencing Streaming Sever Address field.
b. To disable streaming, perform the following:
–Select Disable streaming to disable streaming for the Cisco Unified Videoconferencing Desktop Server that you are currently configuring.
–Enter the Fully Qualified Domain Name (FQDN) of the Cisco Unified Videoconferencing Desktop Server that is enabled for streaming in the Public Address field.
c. Click Next.
Step 8 Change the user name and password on the Security page used to access the Desktop administration interface, and then click Next.
Step 9 Click Finish. The Desktop Status page opens.
Step 10 Verify that all four types of servers are connected.
Note The light next to each link indicates whether or not the connection to the target server or registration with the Gatekeeper is successful. When the light is red, a tooltip containing error details is available. Click the red light to view further error information.
Step 11 If you installed and configured the Desktop Recording Server, click the Recording Status tab, and verify that the Desktop Recording Server is connected.
Note The light next to each link indicates whether or not the connection to the server is successful. When the light is red, a tooltip containing error details is available. Click the red light to view further error information.
Related Topics
•Configuring Streaming for Playback Using the UDP Connection
Configuring Meeting Access Instructions
This section describes how to view the default instructions for joining a meeting that the Cisco Unified Videoconferencing Desktop Server Outlook add-on sends to invitees, and how to modify the contents of these email invitations.
Procedure
Step 1 Click Settings in the sidebar of the in the Cisco Unified Videoconferencing Desktop Server Administration interface.
Step 2 Click the Invitations tab.
The default instructions for accessing the meeting from a desktop, phone or video conferencing device appear on the screen.
Step 3 In the Desktop Access section:
•Click Meeting URL to insert a link to the meeting.
•Click Client Installation to insert a link used to ensure that the Desktop Client is installed and up-to-date.
If you have multiple Cisco Unified Videoconferencing Desktop Servers and want participants to know about them, insert link information for each of them into each Desktop e-mail configuration. For example, if you have one Desktop in Europe, one in Asia, and another in the US, you could place the following information in your e-mail:
"From Europe, connect to http://europe.server.com/cuvcmrm?ID=1234
From Asia, connect to http:/asia.server.com/cuvcmrm?ID=1234
From the US, connect to http://us.server.com/cuvcmrm?ID=1234."
Note The automatically inserted server address is the Desktop FQDN specified during installation.
Step 4 Click E.164 to insert the required E.164 alias in the Phone Access and Video-Conference Device Access sections.
Step 5 Click OK or Apply.
How to Configure a Cisco Unified Videoconferencing 3500 MCU
•Performing Basic MCU Configuration
•Configuring the Auto-Attendant Feature in Multiple-MCU Deployments
Performing Basic MCU Configuration
Procedure
Step 1 Access the MCU Administration web interface.
Step 2 Click MCU on the sidebar.
Step 3 Verify that the EMP modules appear in the Media Processing tab.
Step 4 Click H.323 in the Protocols tab.
Step 5 Enter the IP address in the Gatekeeper Address field.
If you use Cisco Unified Videoconferencing Manager as your meeting control server, enter the Cisco Unified Videoconferencing Manager IP address in the Gatekeeper address field so that the MCU uses the Cisco Unified Videoconferencing Manager Internal Gatekeeper.
Step 6 Click Upload.
Step 7 To enable High Definition Continuous Presence conferences, perform the following steps:
Note Enabling High Definition Continuous Presence conferences reduces MCU capacity.
a. Click Basics in the Settings tab.
b. Select Enable High Definition Continuous Presence.
c. Click Upload.
d. Double-click a service in the Services tab to use for High Definition Continuous Presence conferences.
Note We recommend that you use the preconfigured service 81 HD/SD Continuous Presence.
e. Select 720p from the Support image size up to list in the Automatic Service Definition window.
f. Click Upload.
Note Configuring the MCU for H.235 (secure video) is not supported by Cisco Unified Videoconferencing Desktop Server.
Configuring the Auto-Attendant Feature in Multiple-MCU Deployments
The Auto-attendant feature allows users to dial into Cisco conferencing system using a global auto-attendance session number which is a system-wide prefix allowing users to connect to an auto-attendant session. This prefix is configured via Cisco Unified Videoconferencing Manager which is used to moderate conferencing in multiple-MCU deployments. Once the auto-attendance session number is configured, the MCU auto-attendance (IVR) mechanism is managed by Cisco Unified Videoconferencing Manager.
Note The auto-attendant session is referred to as "IVR session" in the Cisco Unified Videoconferencing 3500 MCU User Guide.
Configuring auto-attendant session is performed in two steps:
•Via the Cisco Unified Videoconferencing 3500 MCU Administrator interface, a new service is created and configured to function as an Cisco Unified Videoconferencing Manager meeting type.
•Via the Cisco Unified Videoconferencing Manager Administrator interface, the auto-attendance session number is assigned to the service created in the MCU.
After this configuration is performed, an auto-attendant session is created in accordance with the configured service every time a user dials the auto-attendance session number configured in Cisco Unified Videoconferencing Manager.
To dial into the auto-attendance (video IVR) using direct IP dialing, users dial the IP address of the Cisco IOS H.323 Gatekeeper.
Procedure
Step 1 Access the MCU Administration web interface.
Step 2 Click MCU in the sidebar.
Step 3 Click the Services tab.
Step 4 Click Add.
Step 5 Define these new service parameters in the Automatic Service Definition dialog box.
•Service prefix
•Service description
•Service type—HD/SD Continuous Presence
•Max call rate—Default value of 2048Kbps
•Support image size up to—4CIF
•Clear the Support presentation view check box.
Step 6 Click Advanced Video Settings.
Step 7 Move the H.263 video codec to the top of the list in the Advanced Video Settings dialog box to assign the highest priority to it.
Step 8 Click OK.
Step 9 Click Upload.
Configuring a Cisco Unified Videoconferencing 3500 Series Gateway
Configure gateways in your network to enable PSTN/ISDN/mobile terminals to join a meeting. Resource Manager uses the gateway information to provide proper dialing information for meeting participants, and to dial out to terminals to invite them to meetings. Resource Manager also manages gateway resources to allow successful call scheduling using network gateways.
When you add a gateway, settings in Resource Manager must be consistent with the actual gateway configuration. We recommend the following:
•If you make changes to the gateway, maintain the IVR and DID numbers in Resource Manager.
•To ensure that there are no gateway ports available for scheduled and ad hoc calls, maintain capacity information.
Procedure
Step 1 Click Resource Management in the sidebar menu.
Step 2 Click Gateway.
Step 3 Click the link in the Name column for the gateway you require, or click Add to create a new gateway profile.
Step 4 Enter the name of the gateway in the Name field.
Step 5 Select a gateway model and enter an IP address in the relevant fields.
Note If multiple gateways are pooled together in a local network with the same access phone number, you can enter multiple IP addresses in the IP Address field to indicate the gateways in the gateway pool. IP addresses are separated by a colon (:).
Step 6 From the Registered To list, select the gatekeeper to which the gateway is registered.
Step 7 From the Location list, select the device island to which the MCU belongs.
The Location field is visible only when the IP Topology tab is activated in the Resource Manager Configuration Tool under System Configuration > UI Settings.
Step 8 Enter the bandwidth for the gateway or gateway pool. For example, for an E1 line, the bandwidth should be 30 B-channels (3940 Kbps).
Step 9 Indicate in the Working Mode field whether the gateway operates in IVR or DID mode.
Resource Manager works with the gateway in DID mode so that meeting participants can easily dial into a meeting. You can assign a range of DID numbers to the gateway. These numbers can be assigned to individual dial-in terminals (endpoints). If you dial one of the assigned DID numbers, you are automatically added to the meeting that the DID number is associated with. Only one terminal can dial a DID number at any given time.
If you configure the gateway in DID mode and set a DID number in the Telephone Number field, when a terminal dials this DID number Resource Manager routes the call to the appropriate meeting based on the terminal number. If no associated meeting is found, then the dial-in call is routed back to the gateway for an IVR session. After entering the meeting ID using the IVR, the terminal is permitted to join the meeting.
Step 10 Enter a gateway phone number.
a. Enter a description of the phone number for the gateway in the Description field.
b. Enter the numeric prefix required to make an international long distance call in the International Access Code field.
c. Enter the numeric prefix required to make a long distance call within the same country in the Domestic Long Distance Prefix field.
d. Enter the country code for the gateway phone number in the Country Code field.
Resource Manager adds this prefix when dial-out is performed from this gateway to a terminal located in a different country than the country in which the gateway is located.
If Allow Out of Area Calls is not selected, only endpoints with the same area code as the gateway are allowed to reach Resource Manager via the gateway.
If you select Allow Out of Area Calls, the gateway accepts incoming calls to Resource Manager from terminals with a different area code than that of the gateway.
e. Enter the domestic area code of the gateway number in the Area Code field.
f. Specify a local telephone number in the Telephone Number field that you want to assign to the specific port.
g. Enter a number in the To access an outside line for local calls, dial field for a gateway with no direct access to an outside line for local calls.
h. Enter a number in the To access an outside line for long distance calls, dial field, for a gateway with no direct access to an outside line for long distance calls.
i. Assign the ISDN device island that the gateway or gateway pool belongs to. If ISDN Topology is hidden, then this field is also hidden.
Step 11 Define the DID range.
If DID is selected in the Working Mode field, define the DID range for the gateway or gateway pool.
Step 12 Click Add Service to add or modify the gateway service.
Note If you select Restricted Mode in the Bandwidth section, 56 appears in the Kbps list. Multiples of 56 Kbps are used instead of multiples of 64. Resource Manager does not support gateway services whose bandwidth is set to "auto" since Resource Manager needs the specific bandwidth to perform resource reservation. If there is a gateway service with "auto" bandwidth, when you configure this service in Resource Manager, select a bandwidth value to best approximate the average bandwidth endpoints use when dialing that service.
Step 13 Set the Advanced Settings.
a. Set the gateway port used for signaling in the Signaling Port field. By default, it is left blank and signaling port will be negotiated dynamically on the fly.
b. Set the SNMP community name required by Resource Manager to communicate with the gateway in the SNMP Get/Set Community fields.
c. Select Dial-in Only to mark the gateway for use only with terminals that users dial into. Resource Manager does not schedule dial-out calls on this gateway.
Step 14 Click OK to save your changes.
How to Configure a Cisco Unified Videoconferencing Manager
•Performing Basic Cisco Unified Videoconferencing Manager Configuration
•Configuring an Auto-Attendant Session
Performing Basic Cisco Unified Videoconferencing Manager Configuration
Procedure
Step 1 Access the Resource Manager Administration web interface.
When you access Resource Manager for the first time, the User Provisioning page opens.
Note For a standard installation, the URL format is http://<server address>:8080.
Step 2 Use this procedure to define the LDAP you want to work with:
a. Click Via.
b. From the Directory Server Type list, select the type of LDAP server to which Cisco Unified Videoconferencing Manager connects to import the LDAP directory information.
c. Enter the URL, login ID, and password of the LDAP server in the URL, Login ID, and Password fields respectively.
Note The user account needs to have read access to the LDAP server directory tree to synchronize Cisco Unified Videoconferencing Manager. This user account does not have to be part of the Search Base.
d. Enter the organization domain in LDAP Server Domain.
e. Enter search strings in LDAP Search Base. Search conditions include "ou" and "cn", for example.
f. Click Advanced.
g. Assign an LDAP group to a specific Resource Manager user role in the Mapping Groups to User Type section. There are four user roles to which an LDAP user can be mapped:
•Organization Administrator
•Meeting Operator
•Meeting Organizer
•Regular User
Note By default, all users are assigned the Organization Administrator user role.
h. Select Do not update users without an e-mail address from the LDAP server to Cisco Unified Videoconferencing Manager in the Update Settings section.
i. To create a virtual room for each LDAP user, click the Virtual Room Number and select the unique user attribute from the list.
By default, the telephoneNumber option is used since everyone within an organization should have a unique telephone number. The resulting virtual room is the concatenation of the Cisco Unified Videoconferencing Manager Meeting ID prefix and the LDAP field that is used for generating the virtual room number.
Note The default Cisco Unified Videoconferencing Manager Meeting ID prefix is 6. If it does not suit the organization dial plan, it can be changed. For operational information, see the related topics.
j. To download a user profile from an LDAP server, define this properties for that user on the LDAP server:
•User ID and password
•First name or last name
•E-mail address
•Belongs to OU
•Belongs to a group (if you want to assign a user role based on group)
k. From the Update Frequency list select an option to define if and how often Cisco Unified Videoconferencing Manager updates the LDAP server settings.
l. Click OK.
Step 3 Display the list of users:
a. Click User Management in the sidebar.
b. Click the Users tab.
c. Click Update.
Note The user database is updated according to advanced settings configured on the LDAP Configurations tab.
Step 4 Verify that connection to the gatekeeper is successful:
a. Click Resource Management in the sidebar.
b. Click the Gatekeeper/SIP server tab.
c. Verify that all connections are successful.
Step 5 Add Cisco Unified Videoconferencing 3500 MCUs:
a. Click the MCU tab, and click Add.
b. Enter data in the New MCU window and click OK.
c. Verify that all connections are successful and the status is Online. For more information, see the configuration guide for Cisco Unified Videoconferencing Manager.
Step 6 Add Cisco Unified Videoconferencing 3500 Series Gateways:
a. Click the Gateway tab, and click Add.
b. Enter data in the New Gateway window and click OK. For operational information about adding a Cisco Unified Videoconferencing 3500 Series Gateway, see the configuration guide for Cisco Unified Videoconferencing Manager.
Step 7 Configure the predefined Cisco Unified Videoconferencing Desktop Server:
a. Click the Desktop tab.
b. Change the Cisco Unified Videoconferencing Desktop Server name if necessary.
c. Change the URL to the public address (FQDN) of your Cisco Unified Videoconferencing Desktop Server in the Web Access URL field in the Servers tab of the Cisco Unified Videoconferencing Desktop Server Administrator interface.
d. Enter the value configured in the H.323 ID field at "Configuring Basic Cisco Unified Videoconferencing Desktop Server Settings" section.
e. Click OK.
Step 8 Add terminals if necessary. For operational information about adding terminals, see the configuration guide for Cisco Unified Videoconferencing Manager.
Step 9 If the LDAP server configuration needs to be changed, perform this configuration as described in Step 2.
Step 10 Download services:
a. Click Meeting Types on the sidebar.
b. Click the Active Meeting Types tab.
c. Click Download.
d. Verify that services are displayed on the Active Meeting Types tab.
e. Click OK.
Step 11 To configure the auto attendance session number:
a. Click the meeting type in the Active Meeting Type tab to be used for auto attendance sessions.
Note This meeting type should be preconfigured via the MCU Administrator interface.
b. Select the Used for Auto Attendance session option in the Meeting Type Detail page.
c. Enter a number in the Auto Attendance session number field.
d. Click OK.
Step 12 Assign a meeting type to a user virtual room using the Cisco Unified Videoconferencing Manager Administration interface:
a. Click User Management in the sidebar.
b. Click the Users tab.
c. Click a user.
d. Click Virtual Room Settings on the User Profile page.
e. Click Add.
f. Enter information and click OK.
-or-
Assign a meeting type to a user virtual room using Desktop Client:
a. Enter the Cisco Unified Videoconferencing Desktop Server URL in an Internet browser.
b. Without entering your user name and password, click Virtual Room Settings.
The Virtual room settings page is displayed.
c. Enter information in the fields.
Note From the Meeting Type list, select the meeting type associated with the virtual room.
d. Click OK.
Step 13 Update the Cisco Unified Videoconferencing Manager license:
a. Click Start > Programs > Cisco Unified Videoconferencing Manager > Update License.
b. Enter the license key and the supplied serial number. For more information about obtaining a license key, see the installation guide for Cisco Unified Videoconferencing Manager.
c. Click Update.
Configuring an Auto-Attendant Session
This section describes configuration you need to perform for deployments using Cisco Unified Videoconferencing Manager for conference moderation.
During this procedure an MCU service, referred to as a meeting type in the Cisco Unified Videoconferencing Manager Administrator interface, is assigned for connecting to the auto-attendant (IVR) session.
Procedure
Step 1 Click Meeting Types in the sidebar menu.
Step 2 Click Active Meeting Types.
Step 3 Click the name of the service you want to use for entry to the IVR.
Step 4 Select Used for auto attendance session.
Step 5 Enter a number in the Auto attendance session number field.
Verify that this number does not begin with any MCU or Gateway service or Cisco IOS H.323 Gatekeeper zone prefix, or is the same as the number of an IP terminal.
Step 6 Click OK to save your changes.
The designated service is marked with an icon in the Name column of the Active Meeting Types screen.
Related Topics
•Configuring the Auto-Attendant Feature in Multiple-MCU Deployments
•Performing Basic Cisco Unified Videoconferencing Manager Configuration
How to Configure Solution Components for Recording
Cisco Unified Videoconferencing Desktop Server allows users to record meetings and to view recorded meetings. A recording includes all media types: the audio, video and presentation. Servers used for recording meetings must have a recording license installed on them.
This section describes how to configure Cisco Unified Videoconferencing Solution components to enable and support the Desktop recording feature.
•Configuring Cisco Unified Videoconferencing Desktop Server for Recording
•Configuring Cisco Unified Videoconferencing Manager for Recording
Configuring Cisco Unified Videoconferencing Desktop Server for Recording
•Desktop Recording Server Connection
•Configuring this Cisco Unified Videoconferencing Desktop Server to Manage Recording
•Configuring an Alternate Cisco Unified Videoconferencing Desktop Server to Manage Recording
•Configuring Recording Parameters
•Disabling the Automatic Recording Feature
Desktop Recording Server Connection
This section describes how to configure Desktop Recording Server settings. Recording can be managed either by a single Cisco Unified Videoconferencing Desktop Server or by multiple Cisco Unified Videoconferencing Desktop Servers.
If a single Cisco Unified Videoconferencing Desktop Server is set to manage recording, only participants connected through that Cisco Unified Videoconferencing Desktop Server can start or stop recording. In this case other Cisco Unified Videoconferencing Desktop Servers in the deployment can be configured to display the list of recordings from the Cisco Unified Videoconferencing Desktop Server configured to manage recording.
If multiple Cisco Unified Videoconferencing Desktop Servers are configured to manage recording, they manage recording independently causing each Desktop portal to display its own list of recordings.
To designate a single Cisco Unified Videoconferencing Desktop Server to manage recording, enable recording on this Cisco Unified Videoconferencing Desktop Server. In this case you must disable recording on other Cisco Unified Videoconferencing Desktop Server in the same deployment, and enable them to allow playback of recordings from an alternate Cisco Unified Videoconferencing Desktop Server in order to display a list of recordings in the portal.
To enable multiple Cisco Unified Videoconferencing Desktop Server for managing recording, enable recording on each Cisco Unified Videoconferencing Desktop Server in this deployment.
Configuring this Cisco Unified Videoconferencing Desktop Server to Manage Recording
The public address you define during this procedure performs a similar role to the public address defined for the Desktop Server. If the Desktop Recording Server resides behind a NAT, the clients may not resolve the Desktop Recording Server IP address. In this case the clients use the public address to connect to the Desktop Recording Server.
You can configure recording settings as well as manage recordings if you select this server to manage recording.
Before You Begin
•Navigate to the Cisco Unified Videoconferencing Desktop Server Administration web user interface.
Procedure
Step 1 Click Recordings in the sidebar.
Step 2 Click the Connection tab.
Step 3 From the list, select Enable recording.
Step 4 Enter the IP address of the Recording Server.
Step 5 Enter an FQDN in the Public Address field.
Note We recommend that you use an FQDN that clients can resolve.
Step 6 Select the IP address from the CUVC Desktop Network Interface list.
The Desktop Server uses this IP address for communications with Cisco Unified Videoconferencing Streaming Server and TCP Proxy.
Step 7 Click OK or Apply.
Note The indicator next to the Address field shows whether not registration to the Cisco Unified Videoconferencing Streaming Server is successful. When the indicator is red, a tooltip containing error details is displayed.
Configuring an Alternate Cisco Unified Videoconferencing Desktop Server to Manage Recording
If you select an alternate server to manage recording, you can configure neither recording settings nor manage recordings.
Before You Begin
•Navigate to the Desktop Server Administration web user interface.
Procedure
Step 1 Click Recordings in the sidebar.
Step 2 Click the Connection tab.
Step 3 From the list, select Enable recording.
Step 4 Enter the URL of the alternate Desktop Server in the Server URL field.
Step 5 Click OK or Apply.
Configuring Recording Parameters
During the configuration described in this section you define the recording policy by enabling the recording option for Desktop users and by specifying the type of meetings the users can record.
If you disable recording for users, you do not need to select a meeting type.
If Cisco Unified Videoconferencing Manager is configured to moderate Desktop Server meetings, both Cisco Unified Videoconferencing Manager and Desktop control recording. If the recording policy is differently configured on Cisco Unified Videoconferencing Manager and Desktop, the more restrictive settings overrule the less restrictive settings, creating a unified recording policy. For example, if the recording policy of Desktop is configured to allow recording of any meeting, while the policy of Cisco Unified Videoconferencing Manager is set to enable recording only for certain virtual rooms, recording of meetings in the specified virtual rooms will be allowed.
You also define the following parameters during this configuration:
•Video size and Recording bit rate—These parameters are used to control the quality of recordings.
Note Setting the recording bit rate to a value lower than 256 Kbps can affect the quality and frame rate of the H.239 Data in the live connection and streaming modes. We recommend that you set the recording bit rate to 384 Kbps.
•Maximum Recording Duration—The value set for this parameter controls maximum allowed duration for any recording.
•Send tone periodically during recording—This parameter defines the frequency of the tone played during a recording which serves to remind users that their meeting is being recorded.
Before You Begin
•Navigate to the Desktop Server Administration web user interface.
Procedure
Step 1 Click Recordings in the sidebar.
Step 2 Click the Settings tab.
Step 3 From the Video Size list, select an option.
Step 4 From the Recording bit rate list, select a value.
Step 5 Select the check box to enable recording for Desktop users.
Step 6 If you enabled recording for users, select a meeting type:
•Any meeting
•Only moderated meetings—Users are allowed to record only meetings for which a moderator PIN is configured.
Step 7 Enter a value in the Maximum Storage Capacity field.
Step 8 Enter a value in the Maximum Recording Duration field.
Step 9 Select an option from the Send tone periodically during recording list.
Step 10 Click OK.
Disabling the Automatic Recording Feature
The procedure in this section describes how to disable the automatic recording feature on Cisco Unified Videoconferencing Desktop Server in deployments using multiple Cisco Unified Videoconferencing Desktop Servers.
Procedure
Step 1 Stop the "Desktop Server - Apache Tomcat" service.
Step 2 Modify the ctmx.ini file:
a. Using either the Microsoft Notepad or the Microsoft Wordpad application, open the following file:
<installDir>\tomcat\webapps\cuvcmrm\WEB-INF\data\ctmx.ini
where <installDir> represents the actual installation directory.
b. Locate the [meetingmgr] section.
c. Find the entry for autorecord and set the value to "false".
d. Save the file.
e. Close the application you used for editing the file.
Step 3 Start the "Desktop Server - Apache Tomcat" service.
Configuring Cisco Unified Videoconferencing Manager for Recording
You can use Cisco Unified Videoconferencing Manager to automatically record either a virtual room or a scheduled meeting when the meeting begins. In this case Desktop records the meeting unless one of the following problems interferes with recording:
•There are not enough available recording ports on the Desktop at the time when the meeting is scheduled
•There is not enough disk space the disk on which recordings are stored
•The maximum number of simultaneous recordings is reached
If the deployment in use comprises multiple Cisco Unified Videoconferencing Desktop Servers, automatic recording is performed on all Cisco Unified Videoconferencing Desktop Servers and several identical recordings are created. In this case it is advisable to allow one of the Cisco Unified Videoconferencing Desktop Servers to perform automatic recording, while disabling the automatic recording feature on the rest of the Cisco Unified Videoconferencing Desktop Servers in the deployment.
•Allowing Recording by Specified Roles
•Allowing Recording by Specified Users
•Enabling Recording for Specified Virtual Rooms
Related Topics
•Disabling the Automatic Recording Feature
Allowing Recording by Specified Roles
Procedure
Step 1 Click Advanced Settings in the sidebar menu.
Step 2 Click Default User Settings.
Step 3 Select an option from the Recording Policy field.
Step 4 Select Allow everyone to record to enable recording permission for endpoint-initiated ad hoc conferences that do not belong to a specific user.
Step 5 Click OK to save your changes.
Allowing Recording by Specified Users
Procedure
Step 1 Click User Management in the sidebar menu.
Step 2 Click Users.
Step 3 Click the link in the Name column for the user you require.
Step 4 Click Advanced.
Step 5 (Optional) Select Inherit recording policy from Default User Settings to define custom recording policy for this user.
Step 6 (Optional) Select Allow user to record meeting to enable this user to record meeting regardless of the global policy.
Step 7 Click OK to save your changes.
Enabling Recording for Specified Virtual Rooms
Procedure
Step 1 Click User Management in the sidebar menu.
Step 2 Click Users.
Step 3 Click the link in the Name column for the user you require.
Step 4 Click Virtual Room Setting.
Step 5 Select Try to record meeting when meeting starts to automatically record a meeting when the meeting starts. This option is available if
•Recording is allowed for the current user according to the recording policy.
•The Record Meeting field is set to Enabled under Admin > Advanced Settings > Look and Feel.
The meeting will not be recorded if there are not enough available recording ports on the Desktop when the meeting is scheduled.
Step 6 Click OK to save your changes.
Configuring a Gatekeeper
This section describes how to set a gatekeeper to work in Call Setup (Q.931) and Call Control (H.245) Routed Mode to enable Cisco Unified Videoconferencing Solution deployments to operate correctly without Cisco Unified Videoconferencing Manager.
Note Do not configure an external gatekeeper if using a deployment with Cisco Unified Videoconferencing Manager. For more information about gatekeeper design options, see the Cisco Unified Videoconferencing Solution Reference Network Design (SRND) at http://www.cisco.com/en/US/docs/video/cuvc/design/guides/srnd/vc5xsrnd.htm.
Procedure
Step 1 Click Gatekeeper in the sidebar of the Administrator interface.
Step 2 Click Settings.
Step 3 Click Calls.
Step 4 Select Call Setup (Q.931) and Call Control (H.245) in the Routing mode field.
Step 5 Click Upload to save the change.
How to Configure a Cisco Unified Videoconferencing Desktop Server to Allow Streaming
•Desktop Server Limitations
•Enabling Streaming Over Port 7070
•Configuring Streaming for Playback Using the UDP Connection
•How to Enable Streaming or Recording Playback Over Port 80
Desktop Server Limitations
These are limitations of Cisco Unified Videoconferencing Desktop Server streaming:
•To establish synchronized moderated streaming, select a single streaming server to be used by all Cisco Unified Videoconferencing Desktop Servers.
•On each Cisco Unified Videoconferencing Desktop Server, define an alternate streaming server and URL to enable a moderator on any Cisco Unified Videoconferencing Desktop Server to allow streaming across all the Cisco Unified Videoconferencing Desktop Servers.
•An independent Cisco Unified Videoconferencing Desktop Server with its own streaming server can be enabled only by a moderator on that server.
•Streaming works better with TCP buffering on the Internet. Control ports on your firewall to force meeting participants to use TCP on the Streaming Server to ensure buffering and prevent packet loss.
•UDP transport provides lower latency on a local network with no packet loss.
Enabling Streaming Over Port 7070
By default, the Cisco Unified Videoconferencing Desktop Server is configured to allow streaming over the TCP port 7070. If necessary, you can configure a different port for streaming.
During this procedure you configure the following:
•IP address of the Cisco Unified Videoconferencing Streaming Server—The address is used for communications with the Cisco Unified Videoconferencing Desktop Server, as well as for external access if the public address is not defined.
•Public address—The address that clients use to access the Cisco Unified Videoconferencing Streaming Server. You can use either a unique IP address or a DNS address if there is an internal and an external IP address.
•TCP port number—By default, this is port 7070. This port must be open on the firewall.
If streaming is disabled for this Cisco Unified Videoconferencing Desktop Server, you can enable users to watch webcasts from the Desktop portal using an alternate Cisco Unified Videoconferencing Desktop Server. In this case you need to provide the alternate Cisco Unified Videoconferencing Desktop Server URL.
Procedure
Step 1 Click Streaming in the sidebar of the Cisco Unified Videoconferencing Desktop Server Administration user interface.
Step 2 Click the Connection tab.
Step 3 To configure this Cisco Unified Videoconferencing Desktop Server to manage streaming, perform the steps below. To configure an alternate Cisco Unified Videoconferencing Desktop Server to manage streaming, proceed with 4.
a. Select Enable streaming from the list.
b. Enter the IP address of the Cisco Unified Videoconferencing Streaming Server.
Note The indicator next to the Streaming Server Address field indicates whether or not the connection to the target server is successful.
c. (Optional) Enter the public address.
d. Enter the TCP port number.
Note You must correctly configure the DNS to allow the Streaming Server public address to resolve to the correct IP address.
e. Click the Settings tab.
f. Select Small (QCIF) or Medium (CIF) in the Video Size field to define the size of the video used for streaming.
g. Select a value in the Rate (KB/s) field to define the bit rate for all meetings.
Step 4 To disable streaming, select Disable Streaming from the list.
Step 5 To enable users to watch webcasts from the Desktop portal using an alternate Cisco Unified Videoconferencing Desktop Server, perform the following:
a. Select Allow watching of webcasts from an alternate Cisco Unified Videoconferencing Desktop Server.
b. Enter the Server URL to redirect users to the specified Cisco Unified Videoconferencing Desktop Server.
Step 6 Click OK or Apply.
Related Topics
•Configuring Streaming for Playback Using the UDP Connection
Configuring Streaming for Playback Using the UDP Connection
This procedure describes how to allow UDP connections to streaming, in case you want to allow UDP streaming first be attempted before the default TCP on default port 7070.
Procedure
Step 1 Perform these steps in the Cisco Unified Videoconferencing Desktop Server:
a. Navigate to the following directory: C:\Program Files\Darwin Streaming Server.
b. Open the streamingserver.xml file.
c. Change the force_tcp parameter value to "false".
d. Save the file.
e. Restart the Darwin Streaming Server.
f. Restart the "Darwin Streaming Server" service.
Step 2 Perform these steps on the Desktop Client computer.
a. Navigate to the following directory: %AppData%\Apple Computer\QuickTime.
b. Delete the file QuickTime.qtp
How to Enable Streaming or Recording Playback Over Port 80
•Binding a Cisco Unified Videoconferencing Streaming Server
•Enabling Streaming or Recording Playback Over Port 80
•Binding an Apache Tomcat to a Specific IP Address
Binding a Cisco Unified Videoconferencing Streaming Server
If the Cisco Unified Videoconferencing Streaming Server runs on the same server as Cisco Unified Videoconferencing Desktop Server, you need to bind it to a separate NIC or IP address on the PC so that it does not conflict with port 80 access to the Cisco Unified Videoconferencing Desktop Server portal. Alternatively, you can deploy the Cisco Unified Videoconferencing Streaming Server on a separate server.
This procedure describes how to configure the Cisco Unified Videoconferencing Streaming Server to bind to a specific IP.
Procedure
Step 1 Open the streamingserver.xml file at
C:\Program Files\Darwin Streaming Server.
Step 2 Find the property bind_ip_addr:
<PREF NAME="bind_ip_addr">0</PREF>
By default, this property is set to a value of zero which indicates that all IP addresses are enabled for the server.
Step 3 Replace the zero with the IP address to which you wish to bind (for example, 1.2.3.4):
<PREF NAME="bind_ip_addr">1.2.3.4</PREF>
Step 4 Save the streamingserver.xml file as a plain text file (not as .rtf or any other format).
Enabling Streaming or Recording Playback Over Port 80
Procedure
Step 1 Find the section for the rtsp_port property in the same streamingserver.xml file.
Step 2 By default, these values are present:
<LIST-PREF NAME="rtsp_port" TYPE="UInt16">
Step 3 Add this entry:
To force streaming only over port 80, you can remove some of the other values but you must leave the value for port 554, as this is the port over which the Darwin Server monitors administrative functions as well as RTSP.
The code should look as follows:
<LIST-PREF NAME="rtsp_port" TYPE="UInt16">
Step 4 Save the streamingserver.xml file as a plain text file (not as .rtf or any other format).
Step 5 Restart the Darwin service (Darwin Streaming Server).
Binding an Apache Tomcat to a Specific IP Address
Procedure
Step 1 Open the server.xml file at
C:\Program Files\Cisco\Cisco Unified Videoconferencing Desktop\tomcat\conf.
Step 2 Add the address="1.2.3.4" field in the port 80 connector definition as follows, and restart Tomcat:
<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
<Connector port="80" maxHttpHeaderSize="8192"
connectionTimeout="20000"
disableUploadTimeout="true"
where 1.2.3.4 is the IP address you want to bind to.
Step 3 Click Streaming in the Cisco Unified Videoconferencing Desktop Server Administration user interface.
Step 4 Enter the Tomcat IP address in the Streaming Server Address field.
Step 5 Enter the IP address or DNS name in the Streaming Server Virtual Address field but do not specify a specific port.
Note Users connecting from behind an HTTP Proxy might need to modify their client-side Quicktime Player transport settings to default to HTTP tunneling.
Step 6 Save the server.xml file as a plain text file (not as .rtf or any other format).
How to Configure Third-Party Equipment
This section describes how to configure third-party communication and security equipment used in Cisco Unified Videoconferencing Solution deployments.
•Configuring a Firewall
•Load Balancing Deployments
Configuring a Firewall
Verify that the firewall is properly configured according to a topology described in Chapter 1, "Selecting a Cisco Unified Videoconferencing Solution Deployment Topology".
•Firewall Guidelines to Support the Cisco Unified Videoconferencing Solution
•Ports to Open in the Firewall to Allow Streaming
Firewall Guidelines to Support the Cisco Unified Videoconferencing Solution
•Firewall Configuration Guidelines
•NAT Configuration Guidelines
Firewall Configuration Guidelines
This section describes the simplest and most typical firewall configuration. A typical configuration allows any computer located on an private network to reach a DMZ and external networks. A computer on an external network can access some specific services in the DMZ but not the private network. In contrast to this, a host located on the DMZ can access the external networks as well as some specific services on specific servers but not the entire private network.
The firewall system uses these interfaces to control different network types:
•WAN—Controls access to and from unprotected external networks, for example a public internet or a partner organization network.
•DMZ—Controls a DMZ network protected by the firewall.
•LAN—Controls a private network protected by the firewall.
Related Topics
•Firewall and NAT Rules for the Cisco Unified Videoconferencing Solution, page D-1
NAT Configuration Guidelines
Network address translation (NAT) is supported for these traffic directions:
•From DMZ to external networks
•From internal networks to external networks
Traffic is not allowed between internal networks and the DMZ because NAT configuration between internal networks and the DMZ is not supported by Cisco Unified Videoconferencing Solution version 5.5.
A firewall rule must be added for each NAT table entry described in this section to permit traffic through the NAT rule. For deployments that do not implement NAT, add a firewall rule corresponding to the following NAT table entries to permit the associated traffic.
Related Topics
•Firewall and NAT Rules for the Cisco Unified Videoconferencing Solution, page D-1
Ports to Open in the Firewall to Allow Streaming
To configure the firewall to allow streaming, you must open a number of ports including:
•Ports from the user to the Cisco Unified Videoconferencing Streaming Server
•TCP port 7070 (or other port of choice) for tunneled RTSP
•Ports for Cisco Unified Videoconferencing Desktop Server to the Cisco Unified Videoconferencing Streaming Server
•UDP ports 6972-65535
•TCP port 554
Sometimes firewalls are configured to block packets used for streaming media. Two general options exist for crossing the firewall boundary: either configure the firewall to allow streaming packets, or reconfigure the streaming server and client to use different network protocols that cross the firewall boundary.
The Streaming Server uses the IETF RTSP/RTP protocols. RTSP runs on top of TCP, while RTP runs over UDP. Many firewalls are configured to restrict TCP packets by port number and are very restrictive on the UDP. The streaming server can tunnel RTSP/RTP traffic through HTTP (the protocol used by web servers and web browsers).
Some firewalls might inspect traffic on port 80 and not allow the tunneled RTSP/RTP on that port. For this reason, we recommend that you use an alternate TCP port for HTTP tunneling such as the QuickTime de facto standard port 7070. This is configured in the streaming server by default as long as you specify the port as part of the streaming server virtual address in the Streaming section of the Cisco Unified Videoconferencing Desktop Server Administration user interface.
Load Balancing Deployments
This section provides general guidelines for configuring a load balancer. For operational information, contact Cisco customer support. A load balancer is used to increase the capacity of multiple Cisco Unified Videoconferencing Desktop Servers beyond that of a single Cisco Unified Videoconferencing Desktop Server. Using a load balancer also allows the Cisco Unified Videoconferencing Desktop Server service to continue even in the event of a Cisco Unified Videoconferencing Desktop Server down time caused by server failure or server maintenance.
A Desktop Client can reach a physical Cisco Unified Videoconferencing Desktop Server by sending a request to the load balancer, also referred to as the virtual server (vserver) or as the director. A group of physical Cisco Unified Videoconferencing Desktop Servers are configured as a Cisco Unified Videoconferencing Desktop Server farm. Each server supplies Desktop services and can be accessed by the load balancer for each Desktop Client request. To deploy the Cisco Unified Videoconferencing Solution correctly, all traffic that reaches the load balancer must be redirected to the physical server using all TCP and UDP ports; thus, connections between Desktop Clients and Cisco Unified Videoconferencing Desktop Servers are managed by the load balancer, as shown in Figure 3-1. A dual-NIC configuration must be used for all servers on the farm. For more information about Dual-NIC configuration, see Appendix B, "Configuring Dual-NIC Cisco Unified Videoconferencing Solution Deployments".
Figure 3-1 Load Balancer Deployment
Related Topics
•Persistence
•Dispatch Methods
•Health Check
Persistence
The Desktop Client state is maintained on the Cisco Unified Videoconferencing Desktop Server, therefore the Layer 4 connection persistence feature must be supported by the load balancer you select for the deployment.
When the connection persistence feature is enabled on the load balancer, subsequent requests from the same client are directed to the same server, once a physical server is selected.
Dispatch Methods
A load balancer supports several methods for determining to which physical server a client request is dispatched. These dispatch methods are supported for a typical load balancer deployment:
•Least Amount of Traffic—A request is sent to the server that currently has the fewest active connections.
•Round-robin—Requests are sent to servers in a sequential and circular pattern. For example, server1, server2, server3, ..., serverN, server1, and so on.
•Fastest—Server responsiveness is dynamically measured and requests are sent to the server with the fastest current response time.
When the persistence feature is used, the load balancing methods are only used for the first request from a new client. For all later requests from the same client, the persistence feature is automatically used for directing requests to the proper server and overrides the load balancing methods.
Note We recommend that the Least Amount of Traffic dispatch method is used.
Health Check
Load balancers also perform server monitoring of services in a Cisco Unified Videoconferencing Desktop Server farm. In the case of a service failure, the load balancer continues to perform load balancing across the remaining servers that are in a working state.
Note Load balancing Desktop server streaming services across multiple Cisco Unified Videoconferencing Streaming Servers are not supported by the Cisco Unified Videoconferencing Solution. Only the interactive connections from the Desktop clients to the Cisco Unified Videoconferencing Desktop Server is supported. For information about scaling the live streaming solution beyond the streaming capacity of a single server and supporting other large scale streaming video distribution technologies for enterprise networks, see the Cisco Application and Content Networking System (ACNS) solution: http://www.cisco.com/en/US/prod/contnetw/ps5680/ps491/networking_solutions_products_genericcontent0900aecd804671a7.htm.
It is recommended that both ICMP echo request and HTTP Web (TCP port 80) health checks are used to monitor Cisco Unified Videoconferencing Desktop Servers on the farm in your deployment.
