LifeSize ClearSea Administrator Guide

(1)

Administrator Guide

(2)

LifeSize ClearSea Server

LifeSize ClearSea is a client/server solution for desktop and mobile video collaboration. Users can connect from their desktops or mobile devices to H.323 or SIP devices, including video systems, MCUs, and gateways. This guide describes LifeSize ClearSea Server:

Related documentation is available from lifesize.com/support.

Terminology for Users and Groups

The following terms are used in this document to describe LifeSize ClearSea users and groups. These terms may differ from terms used with other LifeSize systems. Familiarize yourself with these terms to best understand the capabilities of your LifeSize ClearSea Server.

server administrator - administrator role with full capabilities.

user administrator - administrator role with a subset of management capabilities.

user or end user - a user who connects to the VoIP network managed by LifeSize ClearSea.

user account - a unique user account on the server side related to a LifeSize ClearSea Client user and/or

SIP or H.323 video systems. Each user account includes a user ID and an extension.

user ID - unique string representation of any user account. You can dial the string from a LifeSize

ClearSea Client or select the string from the contact list to place a call.

extension - unique numeric representation of any user account. You can dial the extension from any client

by accessing the IVR flow.

group or provisioning group - every user account belongs to one group. For each group, administrators

can define how LifeSize ClearSea Client is configured. For example: enabling or disabling LifeSize ClearSea Client features, setting video and audio codecs, and limiting maximum bandwidth.

contact and contact list - each LifeSize ClearSea Client user account can maintain a server side contact

list.

Deployment Scenarios Provides an overview of common deployment scenarios, including the external firewall configuration.

Initial Configuration Guides you through the initial configuration after you have installed LifeSize ClearSea Server.

User Call Flows Provides an overview of calling.

(3)

Section 1: Deployment Scenarios

Networking and Call Requirements

LifeSize ClearSea Server is designed to work as a hub for enterprise visual communication.

Users allowed to connect to LifeSize ClearSea Server can place and receive calls regardless of the physical network to which they are connected. For example, users connected to LifeSize ClearSea from the Internet can place video calls to users on the internal company LAN or external to the company LAN. LifeSize ClearSea Server manages call routing and allows users to communicate without knowing the physical location of the call recipient or which networking and VoIP protocols it supports.

The LifeSize ClearSea Server must be able to connect to the master server for activation. Read more at

Activation and Licensing.

(4)

Standalone Deployments

The following sections highlight common standalone deployments. Read about configuring standalone servers at Cluster Management.

Scenario 1: Corporate LAN and Public IP

(5)

Internet Access without NAT

In the following diagram, the LifeSize ClearSea Server is assigned a public IP address typically protected by a firewall. All LifeSize ClearSea Client users and video systems over the Internet are able to place and receive calls to and from the LifeSize ClearSea Server.

Internet Access with 1-to-1 NAT

This scenario is identical to the previous setup, but the WAN interface is assigned a private corporate address with a 1-1 NAT address from the Internet router. As in the previous example, a firewall system might enforce access control.

(6)

Scenario 2: WAN Interface Only, Public IP

In the following diagram, only the WAN interface is connected and all users are on the Internet.

Scenario 3: LAN Interface Only

(7)

Clustered Deployments

You can deploy LifeSize ClearSea in a wide range of clustered configurations. The following sections highlight the most common clustered deployments. Read about configuring clustered servers at Cluster Management.

Scenario 1: Cluster for Redundancy (Dual Homed)

The following deployment allows calls to and from the Internet and to and from the corporate LAN, configuring both interfaces on the LifeSize ClearSea appliance. In this case, it is possible to set up a cluster for redundancy and failover.

Requirements:

• sub network with public IP addresses, possibly behind a firewall (public LAN)

• LAN

Configure this scenario as follows from the LifeSize ClearSea Control Panel in SYSTEM : Network

Interfaces.

Field Value

Internal (LAN) IP address IP address in the LAN

Subnet mask LAN netmask

External (WAN) IP address public IP address in the public network

Subnet mask public network netmask

(8)

You must open the following ports on the firewall between the Internet and the public LAN:

* For the cluster setup, copy all rules for each CSS IP address.

** In this scenario it is highly recommended that you create the cluster on the corporate LAN. Global Configuration DNS (primary/secondary) DNS IP address

Default Gateway default gateway (if applicable) of the public network

NOTE: Instead of configuring a default gateway, you can also set a proper routing rule in Control Panel : SYSTEM : Static Routes.

(9)

Scenario 2: Cluster for Security (DMZ with Public IP)

This deployment allows calls to and from the Internet and to and from the corporate LAN, configuring a single interface on the LifeSize ClearSea appliance. You must set up a cluster to grant security on the corporate LAN.

Requirements:

• controlled network with public IP addresses (DMZ)

• LAN

On each LifeSize ClearSea appliance, plug in the first interface only (LAN) on the related network. Configure the following preferences from the LifeSize ClearSea Control Panel in SYSTEM : Network

Interfaces:

Field Value

Internal (LAN) IP address IP address in the DMZ/LAN

Subnet mask DMZ/LAN netmask

Global Configuration DNS (primary/secondary) DNS IP address

(10)

After creating a cluster, add the following node rule on each node from the LifeSize ClearSea Control Panel in SYSTEM : Cluster Management:

1. Click the LOCAL Node Type entry and Edit Node Routes.

2. Configure the Default Destination Node with the system ID of the node in the DMZ.

3. Add a Node Route, setting the IP/Mask (CIDR notation) for the LAN and the system ID of the node in the LAN as the Destination Node.

On the Internet interface, you must open the following ports on the firewall between the Internet and the DMZ:

(11)

Scenario 3: Cluster for Security (DMZ with Public IP) and Redundancy

This deployment allows calls to and from the Internet and to and from the corporate LAN, configuring a single interface on the LifeSize ClearSea appliance. You must set up a cluster to grant security on the corporate LAN and provide redundancy against server failures.

The setup rules are the same as in Scenario 2: Cluster for Security (DMZ with Public IP), including the following:

• Firewall rules on the firewall between the Internet and the DMZ must be replicated for each node in the DMZ.

(12)

Scenario 4: Cluster for Security (LAN and DMZ with 1:1 NAT)

This deployment allows calls to and from the Internet and to and from the corporate LAN, configuring a single interface on the LifeSize ClearSea appliance. You must set up a cluster to grant security on the corporate LAN.

Requirements:

• controlled network (DMZ)

• public IP

• LAN

On the LifeSize ClearSea appliance in the DMZ, plug in the second interface only (WAN). Configure the following preferences from the LifeSize ClearSea Control Panel in SYSTEM : Network Interfaces:

Field Value

External (WAN) IP address IP address in the DMZ

Subnet mask DMZ netmask

NAT IP address public IP address for 1:1 NAT Global Configuration DNS (primary/secondary) DNS IP address

(13)

On the LifeSize ClearSea appliance in the corporate LAN plug in the first interface only (LAN). From the LifeSize ClearSea Control Panel, configure the following preferences in SYSTEM : Network Interfaces:

After creating a cluster, add the following node rule on each node from the LifeSize ClearSea Control Panel in SYSTEM : Cluster Management.

1. Click the LOCAL Node Type entry and Edit Node Routes.

2. Configure the Default Destination Node with the system ID of the node in the DMZ.

3. Add a Node Route, setting the IP/Mask (CIDR notation) for the LAN and the system ID of the node in the LAN as the Destination Node.

On the Internet interface, you must open the following ports on the firewall between the Internet and the DMZ:

On the DMZ interface, you must open the following ports on the firewall between the LAN and the DMZ:

Field Value

Internal (LAN) IP address IP address in the LAN

Subnet mask LAN netmask

Global Configuration DNS (primary/secondary) DNS IP address

(14)

Scenario 5: Cluster for Geographical Load Balancing and Redundancy

This deployment allows calls to and from the Internet and to and from the corporate LAN of each of the company office headquarters, balancing by geographical location and providing redundancy against server failures.

The setup rules are the same as in Scenario 1: Cluster for Redundancy (Dual Homed), including the following:

• The two nodes are installed on the public network on the two geographical sites.

• The cluster is created, binding on the public IP addresses.

• The DNS must resolve the LifeSize ClearSea domain with the public IP addresses from both nodes.

Sizing Limits

Standalone Maximum number of accounts on a single LifeSize ClearSea unit: 10,000 Maximum number of concurrent registrations: 2,500

Cluster Maximum number of nodes in a LifeSize ClearSea cluster: 4

Maximum number of accounts in a LifeSize ClearSea cluster: 40,000

(15)

External Firewall Configuration

(16)

Section 2: Initial Configuration

Networking

After you install your LifeSize ClearSea Server (hardware appliance or virtual machine), you must configure the network interfaces according to your production network environment.

From the LifeSize ClearSea Control Panel or local console, navigate to SYSTEM : Network Interfaces. For a detailed explanation of the configuration parameters in this section, refer to Network Interfaces. The LifeSize ClearSea Server has two Ethernet interfaces: Internal (LAN) and External (WAN).

If your environment includes an external firewall to control access to the LifeSize ClearSea Server interfaces, you must configure it as described in External Firewall Configuration.

Once networking has been set up, proceed with activation as described in the following section.

Activation and Licensing

Master Server

Contact the master server through the Internet to activate the main license and any other licensing option.

The connection is always initiated by the LifeSize ClearSea Server toward the master server; the LifeSize ClearSea Server connects to master.mirial.com on TCP port 443 using a TLS encrypted socket.

You must configure your network to allow connections from your LifeSize ClearSea Server to

master.mirial.com on TCP port 443. You can configure an HTTP proxy server for connecting to the master, as described in Administrative.

The master server handles all licensing options, including support, firmware upgrade notifications, periodic system health checks, and other functions that keep your LifeSize ClearSea Server running.

(17)

Activation

You must activate your LifeSize ClearSea Server to manage calls. Activate LifeSize ClearSea Server in

Control Panel : MAINTENANCE : License and Options.

NOTE The local console does not include a licensing section. You must access the Control Panel to perform the activation.

If you have a physical appliance, LifeSize activates the system. If you must activate your system, enter your activation code in the License and Options dialog box. Your activation request is sent to the master server and if it is successful, the following occurs:

• A message appears: Your ClearSea Server is activated. All active licensing options appear in this Control Panel section.

• A system ID is assigned to your LifeSize ClearSea Server. The system ID is displayed in the upper right corner of the Control Panel.

• All Control Panel sections are enabled.

• The ClearSea VoIP service starts.

Checkpoint

The LifeSize ClearSea Server and master server exchange information periodically. This type of interaction between the two servers is called checkpoint.

Upgrade Notifications

When a new LifeSize ClearSea Server release is available, an alert appears in the Control Panel. For more information about product upgrade and downgrade refer to Software Upgrade.

License Options

The checkpoint also performs license option checks and automatically updates your licensing options based on your contract status.

To manually force a checkpoint to update your license, select Control Panel : MAINTENANCE : License

(18)

Configuring the LifeSize ClearSea Service

After the system has been activated, the administrator must configure basic service parameters to test service functionality.

Configure the LifeSize ClearSea Domain

Domain Name in Control Panel : SERVICE : General is one of the following values:

• Either the LAN or WAN interface IP address. This does not require setting up the DNS and is recommended for simple network scenarios.

• A fully qualified domain name such as sea.mycompany.com. The DNS of the client video systems must resolve the domain name to the IP address of the target LifeSize ClearSea network interface (LAN or WAN).

Configure One or More Users

To complete basic setup and be able to place a call, you must add at least one user in Control Panel :

SERVICE : Accounts. Click Add Account to enter the user’s information.

LifeSize ClearSea Client

LifeSize ClearSea Client is a software-only video phone used with LifeSize ClearSea Server. LifeSize ClearSea Client is available for both Windows and Mac OS X operating systems and for iOS or Android devices.

Downloading the LifeSize ClearSea Desktop Client

Users can download the LifeSize ClearSea desktop client with a web browser from http://<address>, where <address> is one of the IP addresses or DNS names assigned to the unit. For example:

clearsea.mycompany.com.

Users select either the Windows or Mac OS X installation package.

NOTE Download mobile clients for iOS and Android devices from the Apple AppStore and the Android Market.

Installing the LifeSize ClearSea Client

1. Launch the installation package you downloaded.

(19)

The ClearSea Server field is set to the same address (hostname or IP address) you used to download the client. The LifeSize ClearSea Client displays the address of the last server to which it was connected; however, you can change this server address.

All user data, such as contacts and history, is stored independently on each LifeSize ClearSea Server.

Multiple LifeSize ClearSea Clients using the same user account may be simultaneously connected to the same LifeSize ClearSea Server (example: one at the office and one at home). The first to answer an incoming call establishes the connection. With a connection established, LifeSize ClearSea Server ignores the call on another client.

For a detailed description of how to install, run, and configure the LifeSize ClearSea Client, refer to the

(20)

Section 3: User Call Flows

Test Calls

Placing a test call provides feedback about VoIP functionality and call quality at the far end. LifeSize ClearSea records the caller’s audio and video and plays the recording for the user to preview.

To place a test call, from the LifeSize ClearSea Client, click ClearSea Test Call in the list of contacts. You can also enter testcall in the search box.

Any SIP or H.323 video system that can signal to the LifeSize ClearSea Server an alphanumeric alias as the dialed party name can call testcall.

The test call procedure is timed and requires approximately one minute.

IVR

The interactive voice response (IVR) allows callers to dial the numeric extension of a specific user. This is particularly useful when the caller is not capable of dialing alphanumeric aliases such as name@domain.

Every LifeSize ClearSea user account is assigned an extension that is a unique number used to reach the user account via a guided IVR flow.

To activate the IVR, a user dials the LifeSize ClearSea Server IP address or hostname (for example:

sea.mydomain.com) without specifying any user account alias or number.

The IVR allows the caller to dial the desired extension by using DTMF tones (keypad buttons). Once the extension is dialed and confirmed with the # key, the LifeSize ClearSea Server attempts to contact the called user account.

When trying to connect to the dialed extension, one of the following cases can occur:

• The called user account answers the call.

• The called user account rejects the call (busy signal).

• The called user account does not answer the call (timeout).

• The dialed extension is not available (wrong extension number or the user account is not currently available).

Direct Two-Way Calls

The LifeSize ClearSea Server processes calls to and from the following devices:

• LifeSize ClearSea Client: The software client for Windows, Mac OS X and iOS or Android devices.

(21)

• SIP video system registered to the LifeSize ClearSea Server using credentials from a user account.

• H.323 video system using LifeSize ClearSea Server as a gateway, authenticated using credentials from a user account.

• Video system not associated with a LifeSize ClearSea user account: SIP or H.323 equipment whose IP address is not configured in the Endpoint List of a user account.

NOTE Either the caller or call recipient must have a LifeSize ClearSea user account for the call to be successful.

LifeSize ClearSea connects users on different networks:

• Both the caller and call recipient are in the company LAN.

• The caller is in the LAN, and the call recipient is in the WAN (or vice-versa).

• Both the caller and call recipient are in the WAN.

Additionally, if callers are not using the same communications protocol (SIP or H.323), LifeSize ClearSea performs protocol conversion to connect the callers.

Read more at Standalone Deployments and Clustered Deployments.

User Account with Multiple LifeSize ClearSea Clients or Registered Video

Systems

Any LifeSize ClearSea user account can have multiple instances of the LifeSize ClearSea Client running on separate Windows, Mac OS X, iOS, or Android devices; or registered SIP or authenticated H.323 video systems, all simultaneously connected to the same LifeSize ClearSea Server. With multiple LifeSize ClearSea Clients, when a call is received, it rings on all LifeSize ClearSea Clients and registered SIP and authenticated H.323 video systems. You can answer the call on any system. Once the call is answered (or ignored), all other clients and video systems stop ringing.

MCU

The LifeSize ClearSea Server offers the following MCU capabilities:

• Conferences hosted by the MCU embedded in LifeSize ClearSea Server or an external MCU. Read more at MCU Management.

(22)

Section 4: Administrator Control Panel

The LifeSize ClearSea administrator manages LifeSize ClearSea Server from the Control Panel.

User Roles

Two administrator users can access the following areas of the Control Panel:

• The server administrator has full access to all Control Panel sections.

• The user administrator has access only to Control Panel sections related to user management.

- Alerts

- STATUS : Active Calls

- STATUS : Registered ClearSea Clients

- SERVICE : Groups

- SERVICE : Accounts

Logging In

The integrated web server manages the Control Panel. Access the Control Panel as follows:

1. Open a web browser and enter the following URL for plain text access:

http://<address>:8800

Enter the following URL for encrypted access:

https://<address>:8801

Where <address> refers to one of the IP addresses assigned to the unit.

2. Enter your username and password. Default credentials:

NOTE Login credentials are case-sensitive. Modify these passwords in the

SYSTEM : Administrative section of the Control Panel or the local console.

User Username Password

(23)

Alerts

Alerts that are created either locally by LifeSize ClearSea or remotely by the master server appear in the

Alerts section of the Control Panel. Each alert contains the following information:

Remove an alert from the list by clicking Dismiss selected. To remove all alert messages, click Dismiss

All.

NOTE If you do not dismiss an alert, it appears each time you log in.

ID Incremental alert unique identifier.

Level Possible values: FATAL, ERROR, WARN, INFO. Time Date and time the event occurred.

(24)

STATUS

View the status of your LifeSize ClearSea Server from the Control Panel in STATUS.

System Status

View system status and shut down or reboot the server in Control Panel : STATUS : System Status. The following fields are available:

Active Calls

View active calls on the LifeSize ClearSea Server in Control Panel : STATUS : Active Calls. For each call, the following fields appear:

System Read more at System Status.

Active calls Read more at Active Calls.

Active conference rooms Shows the number of participants and duration of active conference rooms. Learn how to add a conference room in Conference Rooms.

Active MCUs Shows details of active MCUs, including IP address, resolution, maximum and active ports, initialization date, and duration. Learn how to configure MCUs in MCU Management.

Registered users Read more at Registered Users.

Field Description

Service Status Core service status. Normal status is RUNNING. You must activate the LifeSize ClearSea Server for this button to be functional.

Version LifeSize ClearSea product version in the form major.minor.patch Build Number LifeSize ClearSea build number.

Ports (current/max) Current used ports and maximum licensed ports. If the maximum number of used ports is reached, new calls fail.

Ports are related to the call legs: a call between user A and user B includes two call legs and uses two ports. Ports used for test calls are not accounted for in this field. Provisioned Users

(current/max)

Number of provisioned (created) user accounts and maximum supported user accounts.

Registered Users Number of users with LifeSize ClearSea Client logged in to the LifeSize ClearSea Server.

Server Shutdown Shuts down the hardware appliance. Server Reboot Reboots the hardware appliance.

Caller ID Caller ID from signaling.

(25)

The table is updated automatically in real time. To disable or enable auto updates, click the three circles in the lower left corner of the grid. The search text field in the top right corner filters the table to show only rows containing the searched text in any field.

Registered Users

View the list of LifeSize ClearSea Clients currently logged in and registered to the LifeSize ClearSea Server in Control Panel : STATUS : Registered Users. For each client, the following fields appear:

Caller Endpoint Caller vendor ID and product ID. Caller Status Caller's call status.

Dial String Dialed alias, number, or address.

Called ID Called ID from signaling.

Called IP Called signaling IP.

Called Endpoint Called vendor ID and product ID. Duration Call duration (time since call connection). Details Shows additional details about the call. Drop Allows you to end the call.

User ID LifeSize ClearSea Client user ID.

User IP IP address from which the LifeSize ClearSea user account is logged in. LAN or WAN appears, depending on the server interface to which the user is connected.

Status The SIP registration status.

User Endpoint Vendor ID and product ID.

OS Info Information about the operating system of the LifeSize ClearSea Client, if available. System ID The system ID of the cluster node to which the user is connected.

Duration Elapsed time since the user logged in.

Unregister Allows you to manually unregister the user. If the user is in a call, the call is ended as soon as the registration check is performed on the LifeSize ClearSea Client.

NOTE: In a clustered deployment, this action is available only on the cluster node to which the user is connected.

(26)

SYSTEM

This section allows you to configure the local LifeSize ClearSea system.

Network Interfaces

CAUTION Ensure that you check the embedded firewall settings before changing network parameters. If the embedded firewall is enabled, incorrect network settings might prevent the administrator from accessing the system from the service adapter. Refer also to Firewall.

Access network information in Control Panel : SYSTEM : Network Interfaces. This page shows details for each Ethernet interface.

NOTE Modifying field values marked with a red * (asterisk) might require you to restart the LifeSize ClearSea service. Restarting the LifeSize ClearSea service ends all active calls and causes all client registrations to be lost.

Parameter Description

Status Ethernet cable connection/disconnection status. MAC address Hardware MAC address of the Ethernet interface.

Enable DHCP This master switch enables or disables DHCP. If DHCP is enabled, you cannot manually configure the IP address or the Subnet Mask parameter.

IP Address The IP address assigned to the network interface. Subnet Mask The IP subnet mask assigned to the network interface. NAT IP Address (WAN

only)

When the LifeSize ClearSea Server is located behind a router or a firewall in a 1-to-1 NAT configuration, this field must contain the public IP address.

Enable external H.323 conferencing

This master switch enables or disables calls to and from external H.323 video systems (if licensed). This does not affect LifeSize ClearSea Clients.

H.323 Endpoint bandwidth (kbps)

Maximum bit rate allowed for the H.323 video systems (if licensed). This does not affect LifeSize ClearSea Clients. The default depends on licensing options. Enable external SIP

conferencing

This master switch enables or disables calls to and from external SIP video systems. This does not affect LifeSize ClearSea Clients.

SIP Endpoint bandwidth (kbps)

(27)

The Global Configurations section lists network settings that are applied globally:

• primary DNS

• secondary DNS

• default gateway

Firewall

Access firewall information in Control Panel : SYSTEM : Firewall. LifeSize ClearSea embeds a simple firewall to restrict administrative access to specified hosts or subnets. The firewall filters access to the administrative Control Panel and to other management services. Include IP addresses or subnets in CIDR format.

CAUTION Ensure that you include the IP address or subnet from which you access the Control Panel before enabling the firewall and saving the settings. If you cannot access the Control Panel, you can disable the firewall from the local console.

Date and Time

Configure the system date and time in Control Panel : SYSTEM : Date and Time.

Enable Control Panel access

This master switch enables or disables access to the Control Panel.

NOTE: You must enable Control Panel access to at least one interface. If you disable access on both interfaces, the system automatically re-enables it on the LAN interface.

Enable Media Encryption This master switch enables or disables the media encryption on the specified network interface. By disabling this feature, all the calls through the specified network interface do not use media encryption, overriding the LifeSize ClearSea Client and user group media encryption settings. Read more at Group Properties.

NOTE: If media encryption is not licensed, this feature is not enabled and this master switch is locked.

Current Date and Time This read-only field displays the current date and time in YYYY-MM-DD HH:mm:ss format.

Enable automatic synchronization with NTP

Master NTP server switch. LifeSize strongly recommends that all production systems are synchronized with the same NTP server.

NTP Server The NTP server IP or hostname.

Time Zone System time zone.

(28)

Hosts

Edit host file entries to override the DNS resolution in Control Panel : SYSTEM : Hosts. For each hostname or domain name, include the IP address to which the hostname or domain name resolves.

Static Routes

Manage IP static routes in Control Panel : SYSTEM : Static Routes. For each configured static route, the following fields are available.

Administrative

Modify access criteria to the administrative Control Panel in Control Panel : SYSTEM : Administrative.

Automatically adjust clock for daylight saving changes

Depending on the time zone, this setting automatically adjusts the clock for daylight saving changes depending on your time zone.

Change settings manually Select this option if you want to change the system date and time manually.

NOTE: If the NTP server is enabled, this option is disabled.

New date When changing the system clock manually, enter the date in YYYY-MM-DD format. New time When changing the system clock manually, enter the time in HH:mm:ss format.

IP/Mask The destination IP address or subnet in CIDR format. For example: 10.0.0.0/16 Gateway The gateway to the specified destination.

Passwords Modify passwords for the server and user administrators in Server Administrator Password and User Administrator Password. Passwords must meet these criteria:

• The password cannot be empty.

• The maximum length is 15 characters.

• Allowed characters are alphanumeric (a-z, A-Z, 0-9), underscore (_), dot (.), and dash (-). Encryption Read more at Encrypted Access.

SNMP Use the SNMP Configuration section to enable or disable SNMP functionality. The exposed MIBs are those implemented by Microsoft Windows XP machines. Refer to http://

support.microsoft.com/kb/237295/en-us?fr=1.

HTTP proxy In Master Server Access, configure an HTTP proxy for contacting the master server. When enabled, all communication with the master server is performed using the specified HTTP proxy server. Specify the hostname or IP address and port of the proxy. If you use proxy server authentication, include the username and password for authentication.

LifeSize ClearSea Server must be able to contact the master server to perform activation and checkpoints.

(29)

Encrypted Access

Configure encrypted access in HTTPS Control Panel Access (Port 8801):

By default, an internally generated self-signed certificate is used. Setting SSL Certificate to CUSTOM allows you to set a custom certificate/private key pair. The following fields are available:

To restore the default certificate, choose INTERNAL and click Save.

Always Redirect HTTP to HTTPS

When enabled, every attempt to access the Control Panel at port 8800 is redirected to the encrypted Control Panel at port 8801.

SSL Certificate Allows you to change the certificate used for encryption.

Certificate Visible only when you choose CUSTOM from SSL Certificate. Paste the contents of a signed certificate in X.509 PEM format in the box.

(30)

Cluster Management

Clustered configuration provides service scalability and fault tolerance. All systems in a cluster share the same SERVICE settings.

SYSTEM : Cluster Management shows the current clustering status of the server. The most important

status parameter is Clustering Mode, which can be Standalone (not part of a cluster), Candidate (waiting for the cluster join request to be accepted), or Replicated (part of a cluster).

Depending on the current clustering mode, you can do the following:

Create a new cluster This option is available only if the current clustering mode is Standalone. In Create Cluster, select the local Bind Address for cluster interconnection and click Create new Cluster. After the new cluster is created, the system is ready to accept join requests from other systems. The clustering mode of this server is now Replicated.

Request to join this system to an existing cluster

This option is available only if the current clustering mode is Standalone.

In Join Cluster, select the local Bind Address for cluster interconnection and enter the IP address of another LifeSize ClearSea system that is already part of the cluster in IP address of a node in the cluster. Click Join Cluster to send the join request to the other LifeSize ClearSea system.

If the clock of the local system is not synchronized with the cluster, the join request is rejected. To avoid this issue, use the same NTP server for all systems in the cluster.

The clustering mode is set to Candidate until the request is accepted by the administrator on the remote node to which the request has been sent.

CAUTION: This procedure replaces all SERVICE settings on the candidate node with the settings from the cluster.

Accept or reject another system’s request to joint the cluster

This option is available only if the current clustering mode is Replicated and one or more remote systems requested to join the cluster and are waiting as cluster candidates.

Cluster Nodes contains a row for every remote server that requested to join the cluster. Click Add all candidates to accept all join requests or Reject all candidates to reject all join requests.

Remove the local system from the cluster

This option is available only if the current clustering mode is Candidate or Replicated.

Click Revert to standalone to revert the system to Standalone mode. Remove a remote system

from the cluster

This option is available only if the current clustering mode is Replicated.

In SYSTEM : Cluster Management, select the remote system and click Remove Node: this removes the selected remote systems from the cluster and reverts to Standalone.

(31)

Editing Node Routes

NOTE This option is available only if the current clustering mode is Replicated.

In SYSTEM : Cluster Management, select the system and click Edit Node Routes to open Routes for

node<SystemID>. Use this window to define specific call routes for given subnets. You can also add, edit,

or delete node routes. When you add a node route, define the following parameters.

Node routes are evaluated after local call routing. Refer to Call Routing for details on configuring local call routing rules.

Node routes are evaluated as a classic routing table, choosing the first more specific subnet. If no node route matches (or no node route is defined), the Default Destination Node is used to place the call (it acts as a default gateway).

NOTE If a node route matches and the call fails on the matched node, no fallback is performed and the call fails. Node routes are applied only to external

unregistered video systems; registered video systems are always called through the node to which they are registered.

(32)

SERVICE

Configure LifeSize ClearSea service settings in Control Panel : SERVICE.

Domain Configuration and Authentication

Configure LifeSize ClearSea Client authentication and optional HTTP redirects in Control Panel :

SERVICE : General. The following fields are available:

Domain Name The LifeSize ClearSea domain. This field is required for proper LifeSize ClearSea SIP functionality.

Set to the fully qualified domain name or one of the IP addresses of the LifeSize ClearSea Server.

Examples: mcs.company.com or 192.168.0.20

Call Setup Timeout The timeout in seconds that applies to all outbound calls. The LifeSize ClearSea Server ends the call as Unanswered if the far end does not answer within the configured timeout. The default value is 30 seconds.

NOTE: Editing the value of Call Setup Timeout might affect call routing rules. Clients Authentication

Mode

Specifies whether LifeSize ClearSea Client authentication is handled internally or by an external LDAP server:

• INTERNAL authentication requires a user ID and password associated with the user account. Accounts without local credentials are not allowed to log in or register with SIP and H.323 video systems. Read more at Local credentials.

• LDAP bind authentication uses LDAP credentials. LifeSize ClearSea Server sends an LDAP bind request to an external LDAP server. If this bind succeeds, the user is authenticated.

• LDAP search authentication performs an LDAP search on an external LDAP server. A user is authenticated only if the LDAP search returns at least one account and an LDAP bind using the retrieved account succeeds. Use this authentication method to authorize a subset of the LDAP users.

If you use LDAP authentication, note the following distinction between client types:

• LifeSize ClearSea Client users can log in with either their LDAP or local credentials.

• Users registering with other SIP or H.323 video systems must log in with their local credentials.

LDAP Version Specifies the protocol version of the external LDAP server.

LDAP Host The external LDAP server host or IP address. Example: ldap.mycompany.com LDAP Port The external LDAP server port. The LDAP default port is 389, or 636 if SSL is

enabled. LDAP over SSL enabled

(LDAPS)

Specifies if communication with the LDAP server is protected with SSL on the configured port (LDAPS).

(33)

LDAP bind DN DN when authenticating (using LDAP bind) on the external LDAP server. This string may contain one or more of the following wildcards:

• <U> is replaced with the username of the LifeSize ClearSea Client user who is authenticating.

• <P> is replaced with the plain text password of the authenticating user.

• <P-MD5> is replaced with the MD5 hash of the user's password, in LDAP userPassword format: {MD5} followed by base64 encoding of the hash.

• <P-SHA> is replaced with the SHA-1 hash of the user's password, in LDAP userPassword format: {SHA} followed by base64 encoding of the hash. This option is available only when Clients Authentication Mode is set to LDAP bind or LDAP search.

LDAP bind password Password for authenticating (using LDAP bind) on the external LDAP server when performing an LDAP search request.

This option is available only when Clients Authentication Mode is set to LDAP search.

LDAP search DN DN for performing an LDAP search on the external LDAP server. This string can contain the same wildcards as LDAP bind DN.

LDAP search filter Search filter for performing an LDAP search on the external LDAP server. This string can contain the same wildcards as LDAP bind DN.

LDAP search scope The starting point of an LDAP search and the depth of the search from the base DN.

Automatic Import of LDAP Accounts

If enabled, new user accounts are automatically created for users that do not have a user account but who provide correct credentials for the LDAP domain. All parameters configured in the Imported LDAP Accounts are applied to user accounts after each successful login.

This option is available only when LDAP integration is enabled. Imported Accounts

Default Group

Specifies the user group to configure for user accounts that log in successfully on the LDAP server and do not specify an attribute for Group.

This option is available only when Automatic Import of LDAP Accounts is enabled.

LDAP Attribute for "Group"

Specifies an LDAP Attribute to retrieve through the LDAP search. This attribute configures a user account's Group after each successful login.

This option is available only when Automatic Import of LDAP Accounts is enabled and Clients Authentication Mode is set to LDAP search.

This option can be left empty. LDAP Attribute for

"Extension"

Specifies an LDAP Attribute to retrieve through the LDAP search. This attribute configures a user account's Extension after each successful login.

This option can be left empty.

(34)

If the authentication mode is set to LDAP bind or LDAP search, the LDAP connection is checked as soon as the settings are applied; if the LDAP connection is not functional, an alert appears.

Example 1: Configuration of LDAP Authentication

The following example shows authentication managed by Microsoft Active Directory, allowing all users to log in to LifeSize ClearSea with their Active Directory credentials.

LDAP Attribute for "Display Name"

Specifies an LDAP Attribute to retrieve through the LDAP search. This attribute configures a user account's Display Name after each successful login.

This option can be left empty. LDAP Attribute for "Email

address"

Specifies an LDAP Attribute to be retrieved through the LDAP search. This attribute is used to configure a user account's Email address after each successful login.

This option can be left empty. LDAP Attribute for

"Description"

Specifies an LDAP Attribute to be retrieved through the LDAP search. This attribute configures a user account's Description after each successful login. This option is available only when Automatic Import of LDAP Accounts is enabled and Clients Authentication Mode is set to LDAP search.

This option can be left empty.

Enable Redirect If enabled, all HTTP requests to the root of the public web server (port 80) are redirected to the external web server specified in Redirect URL.

NOTE: If LifeSize ClearSea Server is behind a firewall with a NAT configuration, you must redirect HTTP requests to Redirect URL.

Redirect URL URL of an external web server to which HTTP requests are redirected.

Clients Authentication Mode LDAP bind

LDAP Version LDAPv2

LDAP Host mydomain

LDAP Port 389

LDAP over SSL enabled (LDAPS) Disabled

LDAP bind DN <U>@mydomain

Enabled

LDAP Accounts Group Default

(35)

Example 2: Configuration of LDAP Authentication

The following example shows authentication managed by Microsoft Active Directory through LDAP search. In this example, the server has SSL enabled (LDAPS) and access is granted only to members of a group named CN=ClearSea Users,CN=Users,DC=MyDomain.

When a user logs in, LifeSize ClearSea binds on the LDAP server using a configured administrator’s account credentials. An LDAP search request is performed, and if the search request returns at least one account, LifeSize ClearSea Server binds again using the retrieved account and the password entered by the user.

The user login succeeds only if all steps are completed successfully and the final bind succeeds.

Clients Authentication Mode LDAP search

LDAP Version LDAPv3

LDAP Host 10.0.0.100

LDAP Port 636

LDAP over SSL enabled (LDAPS) Enabled

LDAP bind DN admin@mydomain

LDAP bind password ******

LDAP search DN CN=Users,DC=MyDomain

LDAP search filter (&(sAMAccountName=<U>)(&(objectClass=organizationalPerson) (memberOf= CN=ClearSea Users,CN=Users,DC=MyDomain)))

LDAP search scope Subtree

Enabled

Imported Accounts Default Group Default LDAP Attribute for "Group" group LDAP Attribute for "Extension" extension LDAP Attribute for "Display Name" displayName LDAP Attribute for "Email address" mail

(36)

Groups

Each user account belongs to only one group. Create and manage groups and group contacts from the Control Panel in SERVICE : Groups.The following options are available:

• Add a group and edit group settings. Read more at Group Properties.

• Edit the group’s contact list. Each group has its own contacts. User accounts belonging to this group inherit these contacts in their LifeSize ClearSea Client address book. Read more at Group Contact List.

• Delete a group (after confirmation). The Default group cannot be deleted.

Group Properties

Click Edit Group to customize the settings for a selected group. Depending on the licensing options, some codecs, resolutions, or settings might not be available.

Edit the following fields in General:

Manage the provisioned banner images in Banners for both desktops (Banner (8.x desktop client)) and mobile devices (Banner (8.x mobile client)):

Name Group name used in the Control Panel. The group name does not appear to LifeSize ClearSea Client users.

Enable Enables or disables the group.

NOTE: The Default group is always present and cannot be disabled. Allow client to save user

password locally

Enabled by default. Clear the checkbox to require users to enter a password each time they log in to LifeSize ClearSea Client

Chat Enables or disables chat functionality between provisioned LifeSize ClearSea Clients for this group.

Call recording Enables or disables call recording (and the recorder window) for LifeSize ClearSea Clients in the group. By default, enabled.

Image file Uploads the image that is displayed on the LifeSize ClearSea Client for this group. Valid formats are .gif, .jpg, .jpeg, .png, .bmp.

Size constraints: maximum height 90 pixels for the desktop LifeSize ClearSea Client banner, maximum height 140 pixels for the mobile LifeSize ClearSea Client banner. Larger images are not allowed.

After you upload the image, an image preview appears with Alignment, Background color and Remove banner image controls.

PNG images can optionally include the alpha channel; GIF images can include optional transparency and can be animated on the desktop LifeSize ClearSea Client only. LifeSize recommends that you use PNG images, but avoid using animated GIF images.

(37)

In Contacts, configure which user accounts are added to the contact list of LifeSize ClearSea Clients in this group:

NOTE To enhance client performance and reduce network traffic, LifeSize ClearSea Server sends no more than 1000 contacts to a LifeSize ClearSea Client at login. The number of call history entries for a LifeSize ClearSea Client is limited to 20. Both values cannot be changed.

Notifications of the status of a contact’s presence might be unreliable if more than 200 contacts are online at the same time for a specific group. Avoid this condition by reducing the number of total contacts configured in Contacts and leveraging the server search feature configurable in Search, enabling the user to find anyone on demand on the server or in specific groups.

Alignment Aligns the banner image in the LifeSize ClearSea Client banner space. This setting is available only when a valid banner image is loaded.

Background color Sets the background color for the banner image in the LifeSize ClearSea Client banner space. Valid values are HTML color codes in hexadecimal notation. For example: #FF0000.

This setting is available only when a valid banner image is loaded. Remove banner image This option is available only when a valid banner image is loaded.

Remove “ClearSea Test Call” entry

Allows you to provision user accounts in this group without the ClearSea Test Call Contact. By default, this option is not selected.

NOTE: When registered to a LifeSize ClearSea Server, all users can dial testcall to ensure that LifeSize ClearSea Client is configured correctly.

All accounts from server Adds all active user accounts on the server to the contact list of LifeSize ClearSea Clients in this group.

NOTE: Because large contact lists increase loading times on LifeSize ClearSea Client, especially for mobile devices, use this option with caution.

All accounts from selected groups

When selected, shows a list of all server user groups. Selecting a group adds all active user accounts in that group to the contact list of LifeSize ClearSea Clients in this group.

NOTE: Because large contact lists increase loading times on LifeSize ClearSea Client, especially for mobile devices, use this option with caution.

This is the default setting for newly created user groups.

None Adds no user accounts to the contact list of LifeSize ClearSea Clients in this group.

(38)

In Search, configure which user accounts are searchable by LifeSize ClearSea Clients in this group:

In Codecs, configure the following media codecs for the selected group. For each codec on the client, click

Allow to enable (or disable) it. For each enabled codec, click Default to specify whether the codec is

selected (or deselected) on the client by default.

• G.711 A-law • G.711 u-law • G.722.1 • G.722.1C • H.263 • H.264 • H.224 • H.239

In Video formats, configure the following video formats for the selected group. For each video resolution on the client, click Allow to enable (or disable) it. For each resolution, click Default to specify whether the video resolution is selected (or deselected) on the client by default.

• SQCIF (128x96) • QCIF (176x144) • CIF (352x288) • 4CIF (704x576) • 720p (1280x720) • 1080p (1920x1080) Field Description

All accounts from server Specifies that all active user accounts on the server are searchable by LifeSize ClearSea Clients in this group. This is the default setting for newly created user groups.

All accounts from selected groups

When selected, shows a list of all server user groups. Selecting a group makes all active user accounts in that group searchable by LifeSize ClearSea Clients in this group.

(39)

In Endpoint, you can configure video system specific settings:

NOTE RTP Port Range must contain at least 10 ports. A higher number is strongly

recommended to avoid possible conflicts with other applications running on the LifeSize ClearSea Client system.

Group Contact List

Each group has an associated list of contacts. All users who belong to the group inherit all of the group’s contacts. Select a group and click Edit Contact List to manage the group. For each contact in the group, define the display name, address (IP address, alias, number, or URI string), and optional description.

Max BitRate DL (Kbps) Maximum download (receive) bit rate for the LifeSize ClearSea Client. The default value is 512 kb/s.

Max BitRate UL (Kbps) Maximum upload (transmit) bit rate for the LifeSize ClearSea Client. The default value is 512 kb/s.

RTP Port Range (LOW) Lowest port available for RTP. The default value is 4000. RTP Port Range (HIGH) Highest port available for RTP. The default value is 65535.

Media Encryption default Defines the default setting for media encryption in incoming and outgoing calls in LifeSize ClearSea Client. Available values are:

• DISABLED - media encryption is never used.

• ENABLED - media encryption is used when possible.

• REQUIRED - media encryption is always used.

NOTE: Disabling Enable Media Encryption in SYSTEM : Network Interfaces overrides the group media encryption settings.

Allow users to change media encryption

If checked, allows users to change the media encryption setting in the LifeSize ClearSea Client configurations panel, Network & Protocols tab.

(40)

Accounts

The term user account identifies system users. You can optionally associate each user account with a list of video systems. Each entry in this list can be a standard H.323 or SIP video system, videophone, MCU, and gateway.

The LifeSize ClearSea administrator creates user accounts. Each user account includes call history and a contact list; the user can access this information through the LifeSize ClearSea Client.

In Accounts, you can perform the following operations.

Grid Button Description

Add Account Creates a new account.

Edit Account Edits the account.

Edit Associated Endpoints Edits the video systems associated with the account. Edit Contact List Edits the personal contacts of the account.

Call History Opens the call history window of the account. Delete Account Deletes the account.

Import from CSV Imports all accounts from an existing CSV file. Importing a CSV file allows you to configure a large number of user accounts.

UTF-8 character encoding is autodetected from BOM; otherwise ISO 8859-1 is used as a default. Before uploading the CSV file, you can select the field separator. Existing accounts are updated, and import results appear when the process is complete.

Fields included are:

• User ID

• Extension

• Enable (true or false)

• Expiry date (in yyyy-mm-dd +zzzz format. For example: 2011-01-20 +0000)

• Group

• Display name

• Email address

• Description

• Has local credentials (true or false)

(41)

When you export a CSV file from the Control Panel, * SECRET * replaces the actual password for any account with local credentials. If you re-import the file, LifeSize ClearSea Server processes account records with the * SECRET * password as follows:

• If the user account already exists, no updates are made to the account’s password.

• If the user account does not exist, the import creates a new user account with local credentials disabled and no password set. This means that the user will be unable to log in until you reactivate the account and create a valid password. After you import a CSV file, a dialog box shows the number of users created with disabled local credentials. Review also the transactions log in Control Panel :

LOGs and CDRs for failures and warnings.

The authentication method configured for your LifeSize ClearSea Server determines whether user accounts have local credentials. Read more at Domain Configuration and Authentication and Local credentials.

NOTE To copy accounts from one server to another, use the backup and restore functionality instead. Read more at Backup and Restore.

When you add or edit an account, a new window opens with the following fields:

Export All to CSV Exports all accounts as a UTF-8 CSV file. Fields included are:

• User ID

• Extension

• Enable (true or false)

• Expiry date (in yyyy-mm-dd +zzzz format. For example: 2011-01-20 +0000)

• Group

• Display name

• Email address

• Description

• Has local credentials (true or false)

• Password (for security, in the export file * SECRET * replaces the password of any account with local credentials)

Account field Description

User ID Unique LifeSize ClearSea account identifier. VoIP video systems can use this string to contact the user as follows:

• LifeSize ClearSea Clients can dial only the user ID with or without the LifeSize ClearSea hostname or IP. For example: alice, alice@mycompany.com, alice@192.168.0.20

• H.323 video systems can specify the user ID as an H.323 alias.

• SIP video systems can specify the user ID as a SIP URI user part. For example: alice@mycompany.com

(42)

Click Edit Contact List to edit the contact list of the selected user account. This process is functionally identical to editing the group contact list, except that the user account’s contact list is unique to that user account and does not appear to other users.

User accounts can edit personal contacts within their LifeSize ClearSea Client.

Click Edit Associated Endpoints to edit the list of external SIP and H.323 video systems. Video systems added to this list are associated with the selected account.

Extension Unique extension number associated with the user. Typically, you use the extension to contact the user through the IVR, but you can also use the extension to contact the user directly:

• LifeSize ClearSea Clients can dial only the extension with or without the LifeSize ClearSea hostname or IP. For example: 1000,

1000@mycompany.com, 1000@192.168.0.20, mycompany.com##1000, mycompany.com**1000

• H.323 video systems can specify the extension as an H.323 alias or E.164 number.

• SIP video systems can specify the extension as a SIP URI user part. For example: 1000@mycompany.com, mycompany.com##1000,

mycompany.com**1000

Enable Enables or disables the user account. A disabled user account cannot log in to the LifeSize ClearSea Server and is not considered a potential destination for a call. Expiry date The expiration date of the account. If empty, the account is always valid. Group Each user account must belong to a group.

Display Name Display name that appears in the contact list. Email address The email address associated with the account. Description Verbose description of the user.

Local credentials If enabled, associates a password with the account and stores the password on the LifeSize ClearSea Server.

Depending on the Clients Authentication Mode, a user without local credentials might not be allowed to log in through LifeSize ClearSea Client or register SIP or H.323 video systems. Read more at Domain Configuration and Authentication. Password / Change

Password

Confirm Password

When Local credentials is enabled, you must configure a password for a user account to authenticate with the LifeSize ClearSea Client. An empty password is valid.

Endpoint List field Description

Dial String The dial string used to contact the associated video system; if the call protocol is specified as a prefix (sip: h323:), calls to this video system use the specified protocol. Otherwise, an internal heuristic attempts to call the video system using the first working protocol.

(43)

For each call initiated or received by a user account, an entry is added to Call History. Access the call history by clicking Call History. Each entry includes the following information:

• date and time the call started

• date and time the call ended

• call duration in seconds

• remote party

• type of call: Incoming, Outgoing, or Missed

You cannot edit or delete an entry in the call history from the Control Panel.

Conference Rooms

Manage conference rooms in Control Panel : SERVICE : Conference Rooms. When you add or edit a conference room, you must provide the following information:

LifeSize ClearSea can detect who is speaking during a conference. The system displays only the far end video of the participant who is currently speaking; audio of all participants is available to everyone.

Both LifeSize ClearSea Client and other video systems can access a conference either by calling the ID of a conference room or by accessing the IVR and entering the associated extension. If required, a caller is prompted to enter a PIN and # when joining a conference.

Edit Conference Room field Description

Room ID Unique conference room identifier.

Extension Unique extension number associated with the room.

The extension is typically used to contact the user via the IVR (refer to IVR), but can also be used to contact the user directly:

• LifeSize ClearSea Clients can dial only the extension with or without the LifeSize ClearSea hostname or IP. For example: 1000, 1000@mycompany.com, 1000@192.168.0.20, mycompany.com##1000, mycompany.com**1000

• H.323 video systems can specify the extension as an H.323 alias, or E.164 number.

• SIP video systems can specify the extension as a SIP URI user part. For example: 1000@mycompany.com, mycompany.com##1000,

mycompany.com**1000

Enable Enables or disables the conference room. A disabled conference room cannot be joined by any caller.

Requires PIN If selected, a new participant is required to enter a PIN. PIN If a PIN is required, the PIN for conference room access.

(44)

Call Routing

Configure call routing in Control Panel : SERVICE : Call Routing. The Call Routing page allows you to route calls to specific destinations based on rules you configure. You can configure multiple routing rules, each one with a different match order.

For incoming calls, the call routing engine checks each rule in match order until it finds a rule that matches the required call parameters. The call routing engine finally executes the action configured in the matching rule. If no matching rule is detected, the call is forwarded to its intended destination by default.

All routing rules are listed in Control Panel : SERVICE : Call Routing.

For each rule, the following fields appear:

Adding, duplicating, or editing a rule opens the Edit Rule window. The following fields appear:

Match order The order in which the rules will be evaluated by the call routing engine.

Name The rule name.

Action A brief description of a rule's associated action.

Name The rule name.

Conditions One or more match conditions to be matched against the incoming VoIP call parameters. All conditions must be valid for the rule to be matched.

You must specify the Field to check, the Operator, and the Value to use for the check. Refer also to Match Condition Field Types for a detailed description of the condition’s Field types.

You can add, edit, or delete conditions from the condition list.

Action Defines the action to trigger for the incoming call if the rule is matched.

(45)

Type > Destinations Enabled only if Action is Forward or Redirect.

• Forward: this field is a list of destination URIs, each destination on a new line. Destination URIs may be a User ID, an extension, a SIP or H.323 URI, or a request to a ENUM server. Refer to Allowed Destinations and Transformations Syntax for additional information about the accepted syntax. Refer to Resolving a Forward Destination Against an ENUM Server for details on how to add a destination resolved by a server with ENUM support.

• Redirect: this field accepts a single destination. The server redirects the request to the provided address. Refer to Allowed Destinations and Transformations Syntax for the accepted destination syntax.

Type > Concurrent Calls Enabled only if Action is Forward.

If selected, instructs the call routing engine to call configured forward destinations concurrently: all destinations are called, and the first destination to answer forces all the other calls to be disconnected. If not selected, the configured destination is called in the configured order until one destination answers.

By default, this option is not selected. Type > Limit Call Bitrate

(Kbps)

Enabled only if Action is Forward.

Set to empty to leave the call bit rate unlimited. The value must be greater than or equal to 64 kb/s.

By default, this field is empty: no explicit limit applies. Type > Request Timeout

(sec)

Defines the maximum time in seconds to wait for a final response from the video system to which the call has been successfully forwarded by the rule.

The Request Timeout (sec) timer is started immediately when the call request has been sent to the forwarding destination.

If the Request Timeout (sec) time elapses, the server acts as if a 408 RULE REQUEST TIMEOUT response had been received from the forwarding destination, and will proceed evaluating the remaining rules of type Call Answer Timeout. By default, this field is empty.

Type > Enable Caller Transformation

If selected, enables the caller details transformation, activating the Caller Transformation configuration tab.

NOTE: These transformations are applied at a signaling level. By default, this option is not selected.

Type > Enable Called Transformation

If selected, enables the called details transformation, activating the Called Transformation configuration tab.

NOTE: These transformations are applied at a signaling level. By default, this option is not selected.

Caller Transformation > Display String

Defines how the caller display string is transformed. Refer to Allowed Destinations and Transformations Syntax for the accepted transformation syntax.

By default, this field is empty: if the caller transformation is enabled, the result of the transformation is an empty string.