1. About Avistar C3 Conference™ ........................................................................ 1. 1.1. Introduction

Avistar C3 Conference™ Administrators Guide

Date 10/13/1963


Release 3.1

ii

Important Notices Copyrights and Trademarks Copyrighted material of Avistar Communications Corporation, © 1994-2012 The Software may also contain copyrighted materials licensed to Avistar by (i) Microsoft © 2011-2012; (ii) Paradial AS © 2008 – 2011; (iii) Vanguard Software Solutions Inc. © 1995-2011; (iv) Nalpeiron Inc., © 2008 – 2011; and (v) Intel Corporation © 2007 – 2009. Use of the Software is subject to the terms of the applicable End User License Agreement ("EULA") included with the Software. All rights reserved. Avistar, the Avistar logos, Avistar Systems, Avistar C3, Avistar C3 Communicator, Avistar C3 Unified, Avistar C3 Desktop, Avistar C3 Integrator, Avistar C3 Conference, Avistar C3 Tunnel Server, Avistar C3 Connect, Avistar C3 Command, Avistar C3 Media Engine, vBrief, Shareboard, AvistarVOS, and World on the Desktop are trademarks or registered trademarks of Avistar Communications Corporation. All other names used are the trademarks of their respective owners. Avistar's products are manufactured under certain US and Avistar's products are manufactured under the certain US and International patents a complete list of which can be view at: http://www.avistar.com/company/default.aspx?id=74. Other pending published patent applications maybe relevant. Portions of the Avistar products are manufactured under the AVC Patent Portfolio license and are licensed for the for the personal use of a consumer or other uses in which it does not receive remuneration to (i) encode video in compliance with the AVC Standard (“AVC Video”) and/or (ii) decode AVC Video that was encoded by a consumer engaged in a personal activity and/or was obtained from a video provider licensed to provide AVC Video. No license is granted or shall be implied for any other use. Additional information may be obtained Additional information may be obtained from MPEG LA, L.L.C. See http://www.mpegla.com. In addition, portions of the Software may contain royalty-free copyrighted material ("Freeware") of the following licensors, copyright holders and their contributors ("Owners"): Copyright (c) 2001-2003 Ant-Contrib project. Ant-Contrib (subject to Apache v1.1 Software License). Apache Tomcat; Apache XML RPC; Commons beanutils; Commons codec; Commons collection; Commons fileupload; Commons HTTP client; Commons io; Commons lang; Commons logging; Commons net; Derby; EZMorph; jain-sip; Json-lib; log4j; Opencsv; OpenJPA; Quartz; Apache Velocity Engine; all Copyright © 1999-2010, The Apache Software Foundation (subject to Apache Software v2.0 January 2004). antlr Copyright (c) 2003-2008 Terence Parr. ASM Attribute classes Copyright (c) 2000-2005 INRIA, France Telecom. Boost.copyright of Boost Software License - Version 1.0 - August 17th, 2003. Bouncy Castle. Copyright © 2000-2009 The Legion of Bouncy Castle (http://www.bouncycastle.org). dnsjavaCopyright (c) 1999-2005, Brian Wellington. expat Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd. jaxenCopyright 2003-2006 The Werken Company. jQueryCopyright(c) 2010 John Resig, http://jquery.com/. libsrtp Copyright (c) 2001-2005 Cisco Systems, Inc. SLF4J (API); SLF4J (Log4J);SLF4J (Full) all Copyright (c) 2004-2008 QOS.ch. Speex © 2002-2003, Jean-Marc Valin/Xiph.Org Foundation. YUI © 2010 Yahoo!, Inc. WiX © 2005-2010 Microsoft Corporation. (Subject Common Public License v1.0). hibernate AG45 Copyright (C) 1991, 1999 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. (subject LGPL v2.1 February 1999). hibernate AG45; hibernate-annotations; hibernate-commons-annotations; hibernate-entitymanager; all Copyright (C) 1991, 1999 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. (subject LGPL v2.1 February 1999). c-ares Copyright 1998 by the Massachusetts Institute of Technology. zLib Copyright (C) 1995-2010 Jean-loup Gailly and Mark Adler. OpenLDAP Copyright 1999-2003 The OpenLDAP Foundation, Redwood City,California, USA+AG53. OpenSSL Copyright Copyright (c) 1998-2008 The OpenSSL Project. (C) 1995-1998 Eric Young ([email protected]) © Tim Hudson ([email protected]). IPP Software. Intel Corporation © 2007 – 2009. Polycom® Siren 14 (a.k.a. G.722.1c) audio codec. Copyright © Polycom, Inc. ASG.WEB.CUM.EDU © 2001 Carnegie Mellon University Computing Services at Carnegie Mellon University

(<http://www.cmu.edu/computing/>) and John Meyers, Netscape Corporation (subject LGPL v2.1 February 1999). Mobicents Sip Servlets (jain); (sip); (stun4) (mail) all © 2003-2010 Mobicents and individual contributors (subject to LGPL License v2.1 - 1999). OPAL and PTLIB © 2008 - 2010 Craig Southern and Robert Jongbloed (Subject to Mozilla v1.0 License). Windows SDK Copyright (c) 2006 Microsoft Corporation. All Rights Reserved. MS SQL JDBC © 2005-2010 Microsoft Corporation. The PHP License, version 3.01 Copyright (c) 1999 - 2006 The PHP Group. All rights reserved. Independent JPEG Group (c) 1991-1998, Thomas G. Lane. Unless otherwise noted above (i.e., where the Freeware is subject to specific named license agreements), permission is hereby granted by the Owners, free of charge, to any person obtaining a copy of Software to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to strict adherence to the following conditions: (i) The above copyright notice, listing each Copyright Holder, and this permission notice along with the disclaimer notice in (iii) below shall be included in all copies or substantial portions of the Freeware. (ii) The Freeware is provided by the Owners "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED, INCLUDING ANY WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR PERFORMANCE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. (iii) The name of the Owners may not be used to endorse or promote products derived from this software without specific prior written permission of the Owners. (iv) Disclaimer Notice - Redistribution and use of this software in source and binary forms, with or without modification, is permitted provided that the following conditions are met: Redistributions must retain the above copyright notice, the above list of conditions and disclaimers in all copies. Additional details available at: http://www.avistar.com/wp-content/uploads/packages/copyright-confv31.pdf.

Version Information Avistar Part Number 20-55-2000-0310 March 2012

Avistar Communications Corporation 1855 South Grant Street 4th Floor San Mateo, CA 94402 Voice +650.525.3300 Fax +650.525.1360 http://www.avistar.com Avistar Technical Support In the U.S.A. and Canada 1.800.803.0153 All other countries +650.525.3333 [email protected]

http://www.avistar.com/company/default.aspx?id=74�

http://www.bouncycastle.org/�

http://jquery.com/�

mailto:[email protected]�


iii

Table of Contents 1. About Avistar C3 Conference™ ........................................................................ 1

1.1. Introduction ........................................................................................................................ 1

1.2. Features ............................................................................................................................... 1

1.3. About This Manual ............................................................................................................ 2

2. Installation ............................................................................................................. 3

2.1. Server Capacity Planning ................................................................................................. 3

2.2. Hardware and Software Requirements .......................................................................... 5

2.3. Installing Avistar C3 Conference ..................................................................................... 6

2.4. Installing Avistar C3 Conference™ – Media Processor Only ...................................... 8

2.5. Licensing ............................................................................................................................. 9

2.6. Checking Avistar C3 Conference™ Services.................................................................. 9

2.7. Uninstalling ........................................................................................................................ 9

2.8. Logging in ........................................................................................................................... 9

3. Displaying MCU Status .................................................................................... 10

4. Monitoring Conferences ................................................................................... 11

4.1. View Conference Details ................................................................................................. 12

4.2. View Call Statistics .......................................................................................................... 12

4.3. Set Video Layout .............................................................................................................. 12

4.4. View Conference Participant History ........................................................................... 13

4.5. Add Participants to a Conference .................................................................................. 14

4.6. End a Conference ............................................................................................................. 14

4.7. Lock a Conference ............................................................................................................ 14

4.8. Mute a Participant ........................................................................................................... 14

5. Configuring the MCU........................................................................................ 15

5.1. System Details .................................................................................................................. 15

iv

5.2. Managing Media Processors .......................................................................................... 16

5.3. Configuring Settings ........................................................................................................ 16

5.4. Certificates ........................................................................................................................ 18

5.5. Configuring SIP Settings ................................................................................................. 21

5.6. Configuring Network Settings ....................................................................................... 21

5.7. Configuring Conference Services .................................................................................. 22

6. Logging ................................................................................................................. 26

6.1. General information ........................................................................................................ 26

6.2. Calling a Meeting Room ................................................................................................. 27

Appendix A: Resource Units Required by Resolution ........................................ 28

6.3. Configuring Logging ....................................................................................................... 29

7. Administering User Accounts .......................................................................... 30

7.1. About User Roles ............................................................................................................. 30

7.2. View and Edit Users ........................................................................................................ 30

7.3. View Users by Roles ........................................................................................................ 30

7.4. Add a User ........................................................................................................................ 31

7.5. Edit a User ......................................................................................................................... 31

7.6. Remove a User ................................................................................................................. 32

8. Reports .................................................................................................................. 33

8.1. Conference Detail ............................................................................................................. 33

9. H.323 Endpoint Support .................................................................................... 34

9.1. Installation ........................................................................................................................ 34

9.2. Configuration ................................................................................................................... 34

9.3. Calling a Meeting Room ................................................................................................. 35

Appendix A: Resource Units Required by Resolution ........................................ 36

Appendix B: Logging Database Schema ................................................................ 37


v

Appendix C: Firewall Ports ....................................................................................... 43


1

1. About Avistar C3 Conference™

1.1. Introduction Avistar C3 Conference™ is a standards-based, software multiport control unit (MCU) that provides multipoint voice and video conferencing for any SIP or H.323 endpoint, including desktops, room systems, and mobile users. Users can easily access conferences via integrated one-click, ad-hoc conferencing or by calling into an on-demand, personal meeting room. Once connected, Avistar C3 Conference™ delivers a high-quality audio and video experience with continuous presence and voice-switched layouts for a truly interactive experience.

Avistar C3 Conference™ provides a flexible solution to meet the conferencing needs of any enterprise or service provider. As a software solution, administrators can deploy Avistar C3 Conference™ on one or more standard Microsoft Windows Server and provide conferencing capacity required for their organization. Using the intuitive management interface, administrators can define meeting rooms to support the conferencing needs for any application of use.

1.2. Features The table below provides a summary of features available using the Avistar C3 Conference™ software MCU:

Feature Description

Multipoint conferencing for SIP and H.323 endpoints

Compatible with all major vendors’ endpoints

On-demand, personal meeting rooms An administrator can configure a personal meeting room for any user to provide a simple and accessible conferencing solution. An administrator can configure the call rate, quality level, security settings, and number of allowed users for each meeting room to ensure a consistent user experience.

Large conference support A conference can include any number of voice and video endpoints up to the capacity of the host server.

Unlimited conferencing scalability Use multiple host servers to create a single, virtual MCU capable of supporting thousands of endpoint connections.

Personal layout selection Users can choose between a continuous presence or current speaker layout. The continuous presence layout automatically chooses the appropriate layout based on the number of video participants in the conference.

Right-sized buying Avistar C3 Conference™ allows administrators to purchase only the number of ports they need at one time, and then grow into additional ports as the need arises. One port is equivalent to 98 resource units of conference capacity.

High quality audio and video conferencing

Avistar C3 Conference™ delivers a high-quality audio and video experience with support for HD conferencing. Each user receives the best media experience possible with full transcoding and transrating for each user. Avistar C3

About Avistar C3 Conference™

2

Feature Description Conference™ supports: Up to 720p30 transmit and receive Call rate support up to 4Mbps with dynamic rate adaption Selectable 4:3 and 16:9 aspect ratio for transmitted video H.264, H.263, H.263+, and H.263++ video codecs G.711, G.722, G.722.1, G.722.1c audio codecs

Web-based management and monitoring

Avistar C3 Conference™ is managed via a web-based administrative interface. Administrators can monitor the status of the MCU and all active conferences.

SIP registration and proxy support Integrate with existing SIP infrastructure via SIP registration and proxy support. All meeting rooms and the ad-hoc conferencing service are registered.

Secure communications Avistar C3 Conference supports encrypted signaling and media using TLS and SRTP.

H.323 gatekeeper support Integrate with existing H.323 environment by registering Avistar C3 Conference™ with a gatekeeper.

Usage and system logging Log all usage and system data to a Microsoft SQL Server database.

Administrative access control Avistar C3 Conference™ provides secure access control using Windows Domain authentication, local system, or LDAP authentication. There are three levels of administrative access. Viewer: Users can view all settings and active conferences on the MCU. Administrator: Users can modify any setting on the MCU with the exception of adding or editing user accounts. Superuser: Users can perform all functions on the MCU.

API support for advanced conference management

Avistar C3 Conference™ provides a SIP CSTA API that enables 3rd party applications or endpoints to utilize advanced conference management features. These features include: 1-click, ad-hoc conference initiation Add additional users via the endpoint’s address book Remote hold/resume and hang up

Web API for easy integration with 3rd party applications

Avistar C3 Conference™ provides a XML over HTTP interface to enable configuration, management, and monitoring of the MCU.

1.3. About This Manual This document lists the prerequisites for installing Avistar C3 Conference™ and tells how to install the program. It then describes the features and functions of the Avistar C3 Conference™ program.

This manual is intended for Avistar software installers and Avistar network administrators. It assumes reasonable familiarity with networking terms and concepts and with your own enterprise network.


3

2. Installation Avistar C3 Conference™ can be installed on one or more servers. When Avistar C3 Conference™ is deployed a single server, both the Conference Manager and Media Processor are installed on a single host server. When Avistar C3 Conference™ is deployed on multiple servers, the Conference Manager is installed on one server and one or more remote Media Processors are installed on the other servers. The same Avistar C3 Conference™ installer is used for both deployment scenarios. Each time the Avistar C3 Conference™ installer is executed on a new host machine, the administrator is asked to specify which components (Conference Manager and Media Processor) should be installed.

2.1. Server Capacity Planning As a software-only MCU, Avistar C3 Conference™ provides significant deployment flexibility. One or more servers can be used to build a conferencing solution that meets the needs of an organization. Avistar C3 Conference™ is comprised of two components: Avistar Conference Manager and Avistar Media Processor. A single Avistar Conference Manager is capable of managing multiple Avistar Media Processors. From an endpoint and administrative perspective, this deployment of multiple servers looks like a single MCU. The diagram below shows a deployment of Avistar C3 Conference™ using multiple servers.

Installation

4

To ensure maximum usage flexibility and return on investment, Avistar C3 Conference’s capacity is managed using Resource Units (RU). A RU is a unit of computation required for encoding and decoding voice and video streams. 1 RU is arbitrarily defined to mean the computation required to encode and decode an audio-only stream. The number of RU required for each video session depends on the image resolution transmitted by the MCU to the endpoint. The higher the resolution, the more resource units required for each session.

The table below provides a few examples of the resource units for each resolution.

Resolution* Minimum Call rate Resource Units / Endpoint

400 x 224 128 Kbps 11

640 x 368 384 Kbps 26

848 x 480 512 Kbps 44

1024 x 576 768 Kbps 63

1280 x 720 (720p30)

1024 Kbps 98

The complete table of RUs required per resolution can be found in Appendix AMeeting room endpoint call rate. It is important to note that RU are allocated and released as participants enter and leave meeting rooms. Endpoints can connect at any call rate and resolution less than the configured maximum and utilize resource units accordingly.

Avistar C3 Conference™ automatically profiles the host server to determine how many resource units it can provide. The total number of resource units is a function of processor speed and number of cores/processors. The number of available resource units for a Media Processor/server can be found on the Configuration->Media Processors page. The total resource units available in Avistar C3 Conference™ is determined based on the lesser of the license key and the sum of resource units available with each Media Processor. This value is displayed on the Dashboard page and the Configuration->System page.

The table below summarizes the expected resource units available for a host server of Avistar C3 Conference™ with the specified processor configuration:

Processor Resource Units Provided

Max Resource Units Per Endpoint

Wide Screen VGA – 368p30 Endpoints

Quad Intel Xeon CPU E7-8837 @ 2.67 GHz

4300 136 78

Dual Intel Xeon CPU X5680 @ 3.33 GHz

2028 140 78

Dual Intel Xeon CPU X5570 @ 2.93 GHz

1388 103 53

Dual Intel Xeon CPU E5520 964 104 37


5

Processor Resource Units Provided

Max Resource Units Per Endpoint

Wide Screen VGA – 368p30 Endpoints

@2.27 GHz Dual Intel Xeon CPU L5420 @ 2.50 GHz

771 102 29

All numbers are approximate and may vary based on actual hardware and software configuration of the host server.

It is important to note that deployments can use multiple servers with the processors specified above. For example, a deployment of Avistar C3 Conference™ using 16 Media Processors running on Dell PowerEdge R910 Servers using 4 Intel Xeon E7-8837 processors provides a combined total of 68,800 resource units (~4,300 resource units per Media Processor). This configuration is capable of supporting any of the following endpoint connections:

• 512 high definition (HD) endpoint connections (720p30)

o 1 high definition per available core

• 1563 standard definition (SD) endpoint connections (480p30)

o 44 resource units per SD connection

• 2646 wide-screen VGA (WS-VGA) endpoint connections (368p30)

o 26 resource units per WS-VGA connection

Avistar C3 Conference™ uses advanced load balancing to select which Media Processor hosts each new conference request. The Media Processor with the most available resource units is selected to host the new conference. All conference participants are connected to the same Media Processor to ensure a high quality, low latency experience. Avistar C3 Conference™ supports up to 16 Media Processors of any capacity and up to 5,000 concurrent calls. It is important to note that if the Conference Manager and a Media Processor are hosted on the same machine, the available resource units on the local Media Processor decrease each time a new remote Media Processor is added. This is to ensure that server resources are reserved for the Conference Manager functions.

2.2. Hardware and Software Requirements The host computer where you install Avistar C3 Conference™ must meet these requirements:

Resource Requirement

Operating system Microsoft Windows Server 2003 and R2 Microsoft Windows Server 2008

CPU Dual core processor or higher required for operation. 2.5 GHz Intel Xeon processor or higher required for HD video support. Capacity of the MCU varies based on the available processor speed and

Installation

6

Resource Requirement number of available cores; resource usage varies by selected resolution. Example: Quad Intel Xeon E7-8837 @ 2.67 Ghz processors support up to any of the following: 32 video participants at HD (720p30) plus 14 video participants at 656p30 resolution 97 video participants at SD resolution (480p30) 165 video participants at Widescreen VGA resolution (368p30) 390 video participants at Widescreen FCIF (224p30) 4,300 audio-only participants using any supported audio codec.

Memory Minimum 2 GB Memory Configuration “Optimized for Performance”

Disk space At least 2 GB available

Network interface Single, 100 Mbps full-duplex Ethernet TCP/IP local network connection with static IP address

Privileges Administrator privileges are required for installation

Database (optional) Microsoft SQL Server 2008 to support logging

Virtual Servers Supported; requires dedicated resources

Web-browser Internet Explorer v8.0 and v9.0 Firefox v3.5

2.3. Installing Avistar C3 Conference This procedure specifies how to install your first instance of Avistar C3 Conference™ that includes a Conference Manager and Media Processor.

1. Log in to the host machine as Administrator.

2. Double-click the installer file, C3ConferenceSetup.exe, to start the installation wizard.

3. After accepting the license agreement, choose a deployment model. In this case, select the radio button for Avistar C3 Conference™ and click Next.

4. Choose a destination folder for Avistar C3 Conference, or click Next to accept the default location.

5. Specify the ports used for HTTP, HTTPS, and SIP, or click Next to accept the default values. The installer should verify that the ports are available before proceeding

6. Specify the logging Database Server, Server Port, Database Name, Database Account and Password for Installation, and the Database Account and Password for Operation. The installer should verify connectivity to the database and ensure the accounts have the necessary privileges. The database account for installation must have the following permissions: db_datareader, db_datawriter, and db_owner. The database account for


7

operations must have the following permissions: db_datareader and db_datawriter. You can also disable external logging by unchecking the Enable external logging check box.

Installation

8

7. Configure the initial default administration account. The initial account specified during installation has Superuser rights. Specify the first name, last name, username, password, and domain of the default administration account, and click Next.

8. Verify the configuration information provided and click Install to start the

installation.

9. Click Finish to complete the Avistar C3 Conference™ installation.

10. Restart the server.

The installer creates a shortcut to the web interface on the desktop and in the Start menu program list.

2.4. Installing Avistar C3 Conference™ – Media Processor Only This procedure specifies how to install a remote Media Processor that is managed by a Conference Manager located on a different machine.

1. Log in to the host machine as Administrator.

2. Double-click the installer file, C3ConferenceSetup.exe, to start the installation wizard.


9

3. After accepting the license agreement, choose a deployment model. In this case, select the radio button for Avistar C3 Conference™ – Media Processor Only and click Next.

4. Choose a destination folder for Avistar C3 Conference, or click Next to accept the default location.

5. Verify the configuration information provided and click Install to start the installation.

6. Click Finish to complete the Avistar C3 Conference™ installation.

7. Restart the server.

2.5. Licensing A valid license is required for Avistar C3 Conference™ to operate. The Avistar C3 Conference™ license is provided to you by Avistar in the form of an XML file. Contact Avistar Support at [email protected] to obtain your license file. The license specifies the number of resource units available and the MAC address of the host server. In deployments using multiple Media Processors, the MAC address of the server used for the Conference Manager must be used in the License Key for Avistar C3 Conference. This enables additional Media Processors to be added without changing the license key assuming that sufficient resource units are licensed.

2.6. Checking Avistar C3 Conference™ Services After successful installation, the following services should be running on your server host machine: • Avistar C3 Conference™ Web Service • Avistar Multipoint Processor

On a server host machine where only a Media Processor is deployed, only the Avistar Multipoint Processor service is active.

2.7. Uninstalling To uninstall Avistar C3 Conference, go to Control Panel > Add or Remove Programs, select Avistar C3 Conference™ from the program list, and click Remove.

2.8. Logging in To log in to the Avistar C3 Conference™ web interface, open a web browser and enter the IP address or host name of the Avistar C3 Conference™ server in the browser’s Address field.

After you log in, Avistar C3 Conference™ displays the Dashboard screen.


Displaying MCU Status

10

3. Displaying MCU Status The Dashboard screen is your home page when you log in to C3 Conference. Use the Dashboard to monitor the overall system status of the MCU. You can view the number of video and audio endpoints currently connected to the MCU, the percentage utilization of available resource units, and total incoming and outgoing bandwidth.

The Dashboard screen displays the following information:

Field Description

Username Your Avistar C3 Conference™ user name

Domain Your network domain

Roles Your current role: viewer, administrator, or superuser. See Administering User Accounts.

Login Time Date and time you logged in to Avistar C3 Conference™ for the current session

Last Login Time When you logged in to Avistar C3 Conference™ for your previous session

Media Processors Up Number of Media Processors in an up state that are managed by the current Conference Manager.

Media Processors Down Number of Media Processors in a down state that are managed by the current Conference Manager.

Utilization of Resource Units Percentage of total available resource units currently in use. Utilization is calculated by dividing the resource units in use by the total number of resource units.

Resource Units Available Total resource units available. The lesser of the number of resource units available on all Media Processors and the license capacity allowed in the license file. See Licensing.

Resource Units In Use Number of resource units in use. This number divided by total available units determines resource utilization.

Active Conferences The number of conferences currently active on the MCU.

Video Endpoints Connected The total number of video endpoints connected to the MCU, for all active conferences.

Audio-only Endpoints Connected

The total number of audio endpoints connected to the MCU, for all active conferences.

Total Incoming Bandwidth The total data rate being received by the MCU.

Total Outgoing Bandwidth The total data rate being sent by the MCU.


11

4. Monitoring Conferences The Monitoring screen shows active conferences on the MCU. The upper section of the screen lists the conferences. For the selected conference, the lower section of the screen shows both the Active or current participants in the conference, and a Participant History of anyone who attended but may have left the conference.

The conference list shows Conference Address, Conference Name, Start Time, and Duration of a conference, as well as the current number of participants. An Action link is also available. The Address and Name are assigned when someone creates a meeting room for the conference. Add a Meeting Room

Ad-hoc conferences or “instant conferences” also display on the Monitoring screen. Ad-hoc conferences are created when two connected endpoints invite one or more additional participants into a call. On the Monitoring screen, the Conference Address displays Ad-hoc Conference and the Conference Name displays Instant Conference and the date.

In the upper section, click the End Conference link in the Action column to end any conference.

The lower section shows information about a selected conference. By clicking links in the Action column, you can view conference statistics, add a participant to the conference, lock the conference, hang up a selected user, change the video layout, and mute a particular user.

Monitoring Conferences

12

4.1. View Conference Details 1. Choose Monitoring > Conferences. 2. Select an active conference in the upper part of the screen. 3. Click the Active participants tab in the lower part of the screen. The participant

list shows the following information for each participant: • Participant address • Start time • Duration • Type – video conference, audio conference, or both • Encryption status • Status – Calling, Ringing, Connecting, Active, Disconnecting, or Hold • Resource units (used by endpoint) • Action

4. Use links in the Action column toView Call Statistics, hang up, change a participant’s video layout, or mute the participant.

4.2. View Call Statistics You can display call statistics for any conference participant, including audio and video transmission information in both directions between the participant and C3 Conference. 1. Choose Monitoring > Conferences. 2. Click the Active Participants tab. 3. For a particular participant, click Statistics in the Action column. Statistics displayed include the participant’s call start time and duration, audio and video data rate, and information on total and lost audio and video packets.

4.3. Set Video Layout The Avistar C3 Conference™ administrator can control the video layout for all participants in a conference or individual attendees. All available video layouts are shown for a particular meeting room. These are the video layout options:

Current speaker – Displays only the current speaker in the conference (as determined by the MCU). This view is sent to all participants except the current speaker, who sees video of the previous speaker.

Auto (Hide Self enabled) – Displays all participants in the conference, but does not show the user himself. The continuous presence layout changes as the number of participants in the conference changes.

Auto (Hide Self disabled) – Displays all conference participants. The continuous presence layout changes as the number of participants in the conference changes.

5+1 – Displays a fixed screen layout showing the current speaker and up to six participants. If additional participants join the conference, the latest six participants are displayed on the screen.


13

For the two continuous presence options, the video layout changes according to the number of participants in the conference, as shown in the table below:

# Video Participants

in Conference CP Video Layout, Hide Self Disabled

CP Video Layout, Hide Self Enabled

1

2

3

4

5

6+ Additional participants display using voice switched.

Additional participants display using voice switched.

To set video layout for conference participants: 1. Choose Monitoring > Conferences. 2. Select a conference in the top part of the Conferences screen. 3. In the Active Participants tab, click the Video Layout link for a conference

participant. 4. In the Video Layout dialog box, select a video layout: Current Speaker,

Continuous Presence, or Continuous Presence with Hide Self. 5. Select whether to apply the video layout to the individual participant or to all

participants in the conference. 6. Click Set.

4.4. View Conference Participant History For active conferences on the MCU, you can view current participants and a history of anyone who has attended the conference, but may have left or been hung up.

1. Choose Monitoring > Conferences.

2. Select a conference in the upper part of the screen.

Monitoring Conferences

14

3. Click the Participant History tab in the lower part of the screen.

4. The history lists any participants who left the conference, the participant address, the start time and duration of their attendance, connection type, resource units used, and the End Event that terminated their participation.

4.5. Add Participants to a Conference You can use the Avistar C3 Conference™ management interface to add one or more participants to an ongoing conference. 1. Choose Monitoring > Conferences. 2. Select the active conference to which you want to add a participant. 3. Click the Active Participants tab. 4. Click the Add Participant link at the right. 5. In the Add Participant dialog box, enter the IP address (or SIP URI, if a SIP

registrar is configured) of the invitee in the Participant Address field. 6. Choose a Call Rate for the invitee. 7. Click Add. Avistar C3 Conference™ calls the address given. Once the invitee answers the call, he is connected to the conference and added to the Active Participants list for the meeting room.

4.6. End a Conference When necessary, the Avistar C3 Conference™ administrator can choose to end an active conference. This may be necessary for an ongoing conference without attendees, or to clear bandwidth. 1. Choose Monitoring > Conferences. 2. Select the conference you want to end. 3. In the Action column, click the End Conference link. You are prompted with a

warning before the conference is ended. 4. The conference is removed from the active conferences list.

4.7. Lock a Conference When necessary, the Avistar C3 Conference™ administrator can lock a conference to prevent new people from joining.

4.8. Mute a Participant When necessary, the Avistar C3 Conference™ administrator can mute specific participants.


15

5. Configuring the MCU

5.1. System Details To view MCU system status, current license settings, host server, and network information:

1. Choose Configuration > System.

2. The following information is displayed:

Status – Avistar C3 Conference™ software version, Media processors operating, Resource Unit utilization.

License – Current license status, and license capacity in Resource Units. License expiration date and licensed MAC address of the Conference Manager host server. For information on upgrading your Avistar C3 Conference™ license, see section 5.1.2, Updating The Software License, below.Downloading Conference Controller Logs

To facilitate troubleshooting issues, administrators can download an archive of the Conference Controller logs from the administrative interface. All of the Conference Controller logs are zipped into a single file.

Updating the Software License

Controller Host Server – Avistar C3 Conference™ host server name, operating system, processor, memory.

Controller Network – Host controller IP address, router IP, subnet mask, MAC address, and UDP/TCP Port.

5.1.1. Downloading Conference Controller Logs

To facilitate troubleshooting issues, administrators can download an archive of the Conference Controller logs from the administrative interface. All of the Conference Controller logs are zipped into a single file.

5.1.2. Updating the Software License

Your Avistar C3 Conference™ software license controls how many Resource Units are available for the Conference Manager. The license file also specifies an expiration date and the MAC address of the Conference Manager host machine.

To update your license, you can import a new license file. Follow these steps: 1. Choose Configuration > System. 2. Click Import at the bottom of the screen. 3. In the Upload License dialog box, enter the filename and location of the new

license. Click Browse if necessary to locate the file on your machine. 4. Click Import.

Configuring the MCU

16

The new license file is verified before it replaces your existing license file. Note: The license file is for all Media Processors managed by the Conference Manager.

5.2. Managing Media Processors Choose Configuration > Media Processors to manage the Media Processors managed by the Conference Manager.

For the selected processor in the top part of the screen, the lower section of the screen displays Media Processor status, Media Processor host server details and Media Processor network details. Avistar C3 Conference™ runs a series of automated server benchmarking tests to determine the server capacity in resource units and the maximum number of resource units per call. This information is displayed in the Host Server area and can be modified when instructed by an administrator.

The Action column all includes the options to Restart, Download Logs, Remove, and Enable/Disable a Media Processor. When a Media Processor is disabled, no new conferences are hosted on the Media Processor. Existing conferences continue to operate.

To add a Media Processor, click the Add Media Processor button and specify the IP address or host name of the remote Media Processor. The Media Processor must be up and available to be initially added to the Conference Manager configuration.

5.3. Configuring Settings

5.3.1. General Conferencing Settings

Use the Settings screen to use LDAP for administrative user authentication, manage user account time limits, set conference entry and exit sounds, and configure Security Pin Queue options, including sounds and displayed images.

To configure general Avistar C3 Conference™ settings: 1. Choose Configuration > Settings. 2. Click Edit. 3. Configure the LDAP, Administration, Conference Sounds, and Security Pin

Queue settings as needed.

5.3.2. Administrative User Authentication Via LDAP Enable administrative user authentication via LDAP if you would like to use an LDAP directory instead of Windows Domain authentication. Administrators must specify a domain name label, repository URL, search base, login ID field name, and Bind DN.


17

5.3.3. Administration Settings

1. Choose the Inactive account suspension limit in days after which a user account becomes inactive if the user does not log in to C3 Conference. The range is from 1 to 365 days.

NOTE: This setting does affect users who are set to Not Expire in their user settings. See Add a User.

2. Choose the Inactive session expiration limit after which administrative sessions expire. Range is from 1 to 60 minutes.

5.3.4. Sounds Settings

Use these settings to select the Entry Tone and Exit Tone sounds that conference attendees hear when a participant enters or leaves the conference. A menu of choices is available for each tone, based on sounds that are installed in the Data folder, inside the default installation folder. Click Play to listen to the selected tone.

5.3.5. Security PIN Queue Settings 1. Choose Welcome, Correct Pin Message, Incorrect Pin Message, Endpoint

Disconnected Message, and No More Participants audio and image files. Click Play to listen to the selected tone.

2. Click Save to save changes or Cancel to exit without saving changes.

Configuring the MCU

18

5.4. Certificates Certificates are used to support both encryption and authentication. For encryption, certificates provide a secure method to exchange password “keys” shared only between the two host machines establishing the connection. For authentication, a certificate can identify what generated the certificate. For additional security, certificates can be rejected if the authority that generated the certificate is not trusted.

Avistar C3 Conference supports the following types of certificates:

Name Alias Usual Extension

Could Contain Suitable for

PKCS #12 Personal Information Exchange

PFX pfx Certificates, private keys

HTTPS, TLS, trusted roots

PKCS #7 Cryptographic Message Syntax Standard

P7B p7b Certificates Trusted roots

PEM Base64-encoded X.509

– cer Certificates, private keys


DER DER-encoded binary X.509

– cer Certificates, private keys


JKS Java keystore

– – Certificates, private keys



19

5.4.1. Importing an HTTPS Certificate

Browser sessions to administer Avistar C3 Conference require a secure session using HTTPS. Avistar C3 Conference installs a default HTTPS certificate to enable access initially, but Avistar recommends replacing the default HTTPS certificate with one generated by a Trusted Root Authority. This recommendation applies even for deployments where Avistar C3 Conference is only accessed internally.

5.4.2. Importing a TLS Certificate

For media encryption and encrypted communication with remote servers and endpoints, Avistar C3 Conference requires installing a valid TLS certificate before additional ports and configuration options for TLS can be enabled. When a certificate is generated for HTTPS, the same certificate can also be imported for TLS.

5.4.3. Certificate Verification

For additional security, Avistar C3 Conference can be configured to only maintain connections with servers presenting certificates generated by hosts configured as a Trusted Root Authorities in Avistar C3 Conference. Before Verify Certificates can be enabled, at least one certificate from a machine serving as a Root Authority must be imported into the Trusted Root Authorities portion of the Certificate configuration page.

If Verify Certificates is not enabled, a valid TLS certificate is still required for secure communication but, even if a Trusted Root Authority certificate has been

Configuring the MCU

20

imported, certificates are not checked to verify they were generated by one of the Trusted Root Authorities.

It is possible to deploy self-generated certificates throughout an organization and disable Verify Certificates if there are no security concerns about server connections within the deployment.

5.4.4. Importing a Trusted ROOT Authorities Certificate

Avistar C3 Conference supports importing as many Trusted Root Authority certificates as needed for your organization. In practice, most deployments configure a single machine as Trusted Certificate Authority (Trusted CA). The Trusted Certificate Authority is used to generate the required certificates. Depending on your deployment, you may require certificates for multiple Avistar Call Control servers, Avistar C3 Conference, and Avistar C3 Command. By importing a certificate from the Trusted CA that created those certificates into the Trusted Root Authorities section in each server, communication among multiple servers can be verified and secure without risk of an unauthorized server maintaining a connection.

When TLS and Verify Certificates are enabled, Avistar C3 Conference verifies the certificate provided by the remote server.


21

5.5. Configuring SIP Settings Use the SIP configuration screen to register the MCU with a SIP registrar. This allows conference participants with SIP endpoints to connect to the MCU by dialing a meeting room number rather than an IP address.

If your network has a SIP server and you enable the Outbound SIP Proxy, outbound calls are directed through a SIP proxy server. The Proxy server may or may not be the same name entered in the Registrar field, above.

To enable the SIP registrar and/or SIP proxy server: 1. Choose Configuration > SIP 2. Click Edit. 3. Enter values for the following fields as needed:

Field Description

SIP Register

Status Select Enabled to turn SIP registration on

SIP Domain Domain name associated with the MCU

Registrar Address Network address of the SIP registrar (host name or IP address)

Secure Signaling (TLS) Select Enabled to use TLS when registering with the SIP Server.

Username The login name for the MCU on the SIP registrar

Password Password for the MCU on the SIP registrar

Outbound Proxy

Proxy Status Select Enabled to use a SIP Proxy

Proxy Address Network address of the SIP Proxy

Proxy User The login name for the MCU on the SIP Proxy

Proxy Password Password for the MCU on the SIP Proxy

4. Click Save.

5.6. Configuring Network Settings Click Configuration > Network to view current network settings for the MCU. Click Edit to change network settings. You can configure the following settings:

Field Description

UDP/TCP Port Allows administrators to enable/disable UDP/TCP and to specify which port is used. The default state is Enabled using port 5060.

TLS Port Allows administrators to enable/disabled TLS and to specify which port is used. The default state is Disabled using port 50611.

DiffServe Audio Priority 0-63. ToS/QoS value – prioritizes audio/video traffic over other network traffic to the server.

DiffServe Video Priority (see above)

Maximum Packet Size (MTU) Network admin has set up network with an optimized MTU - this

Configuring the MCU

22

tailors C3 Conf. packets to your network settings.

RTP Lowest Port Number The starting UDP port number. The lowest port number to which the packets are sent. Data for audio and video packets use several different RTP ports. This specifies a range to prevent conflicts with other traffic on the system.

RTP Highest Port Number The ending UDP port number. The highest port number to which the packets are sent.

Dynamic Rate Adaption Select Disabled to turn off dynamic rate adaption. Dynamic rate adaption enables Avistar C3 Conference adjust call rates and resolution based on network conditions.

5.7. Configuring Conference Services Avistar C3 Conference™ provides two types of conferencing services: Ad-hoc conferences and personal meeting rooms. Ad-hoc conferences are ‘instant conferences’ that are created on the fly when two connected video endpoints conference in additional endpoints. Avistar C3 Conference™ supports ad-hoc conferences and allows you to monitor them like other scheduled conferences. Meeting rooms allow multiple users to connect in a planned videoconference. Using Avistar C3 Conference, you can set up personal meeting rooms for employees who frequently host meetings with multiple participants. Users can then include their personal meeting room information as part of calendar invites when they are scheduling meetings. Avistar C3 Conference™ supports any number of ad-hoc conferences and personal meeting rooms.

Here’s a brief overview of the conference service creation process for a meeting room: 1. A user with Administrator privileges logs into Avistar C3 Conference™ and

creates a conference service of type meeting room. The user specifies a meeting room number (“1234”) and name (“Brian’s Meeting Room”). Note: The meeting room number must be unique.

2. When the meeting room is created, a SIP URI is also created that can be dialed by any SIP endpoint. The meeting room SIP URI for our sample meeting room is [email protected].

3. Endpoint 1 dials [email protected] and is connected to the MCU in meeting room 1234.

4. Endpoint 2 dials [email protected] and is connected to the MCU in meeting room 1234.

5. Subsequent endpoints (3, 4, and so on) dial the same SIP URI and are connected to the meeting room.

6. Alternately, using the Avistar C3 Conference™ web interface, the administrator can add a participant to an ongoing conference. The administrator selects meeting room 1234 on the Monitoring > Conferences screen and then enters the IP address (or SIP URI, if a SIP registrar is configured) of the endpoint to be called and conferenced in.Add Participants to a Conference.

If no Resource Units are left on the MCU, additional endpoints calling into a conference get a busy signal.





23

5.7.1. Manage Conference Services 1. Choose Configuration > Conference Services to display the Conference

Services screen. On this screen, you can view and manage currently configured conference services, or create a new conference service.

2. To create a conference service, click Add a conference service. The name, address, maximum call rate, Service Type and status are listed for existing meeting rooms. The address is the string that callers enter in their video conferencing endpoint application to call into the meeting room. The name is assigned when the meeting room is created, or can be edited at any time. You can sort meetings by the contents of the Address, Name, or Max Call Rate column. Click a column heading to make that the sort column. Click the heading again to reverse the sort order: for example, if the Address column is the current sort column, you can display meetings in forward or reverse alphabetical order. To search for a meeting, enter the first and/or any subsequent letters or numbers of the meeting name or address in the Search field. As you enter letters or numbers, the meeting list is filtered to show only meetings whose name or address starts with those characters.

3. Click links in the Action column to do any of the following: • Edit settings for a meeting room, including the maximum call rate and the

resolution. Note: If you edit a meeting room hosting an ongoing conference, new settings only affect attendees that join after the changes are made.

• Remove a meeting room. Any conference participants in the room are disconnected.

• Disable a meeting room, to make it temporarily unusable. The status changes from Registered to Not Registered in the Status column and new users cannot call into the meeting room. Click Enable to enable the room again.

5.7.2. Add a Meeting Room

Meeting rooms allow multiple callers to join a videoconference. As the meeting room administrator, you can set up a meeting room, and then invite attendees. 1. Choose Configuration > Meeting Rooms. 2. Click Add Meeting Room. 3. Name the room and assign it a unique number (up to 15 digits). The name

appears in the Name column on the Meeting Rooms screen. The number is combined with the Avistar C3 Conference™ host machine number to create the Meeting Room Address.

4. Choose a Meeting Room Pin if you would like to create a meeting room that can only be joined by people you specify. If you do not create a pin, anyone with the Meeting Room name can join the conference. Pins can be up to 10 digits (0 to 9). Potential attendees are disconnected after three failed attempts to enter the pin.

Configuring the MCU

24

5. Choose the Maximum Allowed Participants for the meeting to limit the maximum number of people you would like to participate in the conference. You can choose between 1 and 1000 for the number of participants. If you choose no limit, one conference could use all the resource units available for the MCU.

6. Choose a maximum call rate for the meeting. See Meeting room endpoint call rate for more information.

7. Choose an aspect ratio for the video window: 16:9 or 4:3. 8. After selecting an aspect ratio, select the dimensions (width x height, in pixels)

for the video window. You can also adjust how the video layouts are enabled. The following layouts are available: • Auto (Hide-self Enabled) • Auto (Hide-self Disabled) • Current Speaker (VS) • 5+1 Note that at least one video layout must be specified. The default selections are Auto (Hide-self Enabled) and Current Speaker (VS). When endpoints are connected to a meeting room, the video layout change options rotate through the list of available video layouts selected. This applies to using the #5 on the keypad and using the video layout button in Avistar C3 Unified or Avistar C3 Communicator.

9. Choose the Initial Video Layout. 10. Choose whether media encryption is required for this meeting room. Note that

TLS must be enabled before media encryption can be required. 11. Click Save. The new meeting room appears in the meeting room list. The address of the room is the room number@the hostname of the machine running C3 Conference.

5.7.3. Meeting room endpoint call rate

The Max Call Rate sets the maximum video resolution transmitted from the MCU to endpoint for each meeting room. The call rate you select filters the resolution options available in the Maximum Video Resolution menu. Only resolutions that provide a good video experience are displayed for the selected call rate.

Higher call rates support larger video resolutions and an improved video experience. Larger video resolutions also require the allocation of more Resource Units from the MCU for a videoconference. See Appendix A for the required resource units for each resolution.

To enable Ad-hoc conferencing: 1. Choose Configuration > Ad-hoc 2. Click Edit. 3. Set Status to Enabled. 4. Enter the Ad-hoc Conferencing Alias. This is a string of your choice that must

match the string used when the ad-hoc conferencing service is configured on client endpoints. When configuring the endpoint, the ad-hoc conferencing alias is entered as follows: <Ad-hoc Conferencing Alias>@<SIP Domain>


25

5. Choose the Maximum Allowed Participants for the meeting to limit the maximum number of people you would like to participate in the conference. You can choose between 1 and 1000 for the number of participants. If you choose no limit, one conference could use all the resource units available for the MCU.

6. Choose a maximum call rate for the meeting. See Meeting room endpoint call rate for more information.

7. Choose an aspect ratio for the video window: 16:9 or 4:3. 8. After selecting an aspect ratio, select the dimensions (width x height, in pixels)

for the video window. Refer to the Set Video Layout section for more information.

9. Choose the Initial Video Layout. 10. Choose whether media encryption is required for this ad-hoc conference. 11. Click Save.

Logging

26

6. Logging Avistar C3 Conference™ logs basic usage information to a SQL Server database to support troubleshooting and debugging. Both conference-level information and individual usage information is captured, including the following data:

6.1. General information

6.1.1. Conference Information • Meeting Room Name and Address • Media Processor Host Name • Start/Stop Time • End Reason • Configured Maximum call rate • All failed attempts to start a conference. Failed attempts include situations due

to error or resources not being available

6.1.2. Conference Participant Information • Participant Display Name • Participant SIP URI • Participant IP Address • Participant Call Rate • Start/Stop time • End reason For details on database structure, see Appendix BConfiguration

Administrators configure Avistar C3 Connect by modifying the sgw.ini file. Complete the following steps to use Avistar C3 Connect with Avistar C3 Conference:

6.1.3. General

1. Stop the Avistar C3 Connect service.

2. Change the autoStartMgr configuration parameter to True.

6.1.4. SIP Configuration

1. Change the SIP_InboundDialPattern configuration parameter to 1.

2. Change the SIP_AllowedServers configuration parameter to the IP address of your Avistar C3 Conference™ host server.


27

3. Change the SIP_B2bUAURL configuration parameter to the IP address of your Avistar C3 Conference™ host server.

6.1.5. H.323 Configuration

If the H.323 environment includes a gatekeeper with which Avistar C3 Connect registers, modify the following configuration parameters:

a. Set h323_Gk_Enable to True b. Set h323_GK_Addr to the IP address of your gatekeeper.

Additional details on configuring Avistar C3 Connect can be found in the Avistar C3 Connect XML API Reference Guide.

6.2. Calling a Meeting Room Once Avistar C3 Connect has been configured for use with Avistar C3 Conference, H.323 endpoints can join conferences hosted on the MCU. For H.323 endpoints in an unmanaged environment (no gatekeeper configured), the meeting room number is specified using the dialed digits. For example, an environment where Avistar C3 Conference™ and Avistar C3 Connect are hosted on a server with the IP address of 192.168.12.12, a Polycom endpoint would dial 192.168.12.12##1000 join the meeting room with a number of 1000. In an environment where Avistar C3 Connect is registered with a gatekeeper using the prefix 88, a Polycom endpoint would dial 881000 to be connected to the meeting room with a number of 1000. NOTE: Avistar C3 Conference™ does not currently support DTMF tone

detection so endpoints must send security PINs and layout change commands in the signaling channel. Endpoints from Cisco/Tandberg and LifeSize typically send DTMFs in the signaling channel when the remote party advertises this capability. Unfortunately, Polycom endpoints do not send DTMFs in the signaling channel and therefore can not joint meeting rooms with security PINs.

Logging

28

Appendix A: Resource Units Required by Resolution

The table below shows the Resource Units required for various call rates and resolutions, at 16:9 and 4:3 aspect ratios.

16:9 Aspect Ratio

Resolution Minimum Call Rate Resource Units per Endpoint

320 x 176 128 Kbps 7 400 x 224 128 Kbps 11 512 x 288 256 Kbps 17 592 x 336 256 Kbps 22 640 x 368 384 Kbps 26 704 x 400 384 Kbps 31 768 x 432 512 Kbps 36 848 x 480 512 Kbps 44 960 x 544 768 Kbps 56 1024 x 576 768 Kbps 63 1088 x 608 768 Kbps 70 1168 x 656 1024 Kbps 82 1280 x 720 (720p30) 1024 Kbps 98

4:3 Aspect Ratio Resolution Minimum Call Rate Resource Units per Endpoint

320 x 240 128 Kbps 10 384 x 288 256 Kbps 13 448 x 336 256 Kbps 17 512 x 384 256 Kbps 22 576 x 432 384 Kbps 27 640 x 480 384 Kbps 34 704 x 528 512 Kbps 40 768 x 576 512 Kbps 48 832 x 624 768 Kbps 56 896 x 672 768 Kbps 64 1024 x 768 1024 Kbps 83 1088 x 816 1024 Kbps 94

Appendix B: Logging Database Schema.


29

6.3. Configuring Logging 1. Create a new database in Microsoft SQL Server 2008. Keep track of the

database name and the user and password information needed to access the database.

2. Choose Configuration > Logging. 3. Click Edit to open the Edit Logging Settings dialog box. 4. Change Status to Enabled. 5. Leave Database Type at the default, Microsoft SQL Server 2008. 6. Enter the Hostname and Port of the computer hosting the database. 7. Enter the name of the database. 8. Enter Username and Password required to access the SQL database.

Administering User Accounts

30

7. Administering User Accounts

7.1. About User Roles Avistar C3 Conference™ supports three levels of administrative roles: Viewer, Administrator, and Superuser.

Role Description

Viewer Can view current settings and status of the MCU. Status includes active conferences and the statistics of each participant in the conference.

Administrator Can manage all aspects of the MCU except for adding and editing user accounts.

Superuser Can manage all aspects of the MCU, including adding and editing user accounts.

7.2. View and Edit Users User Name, Login ID and Email address are listed for each user, as well as whether the user account is currently active. For the selected user in the list, the Details section shows additional information, including the users Role: viewer, administrator, or superuser. 1. Choose Users > Users to display current Avistar C3 Conference™ user

accounts. 2. Choose Edit in the Action column to change aspects of the selected user. You

can update the first and last name, email address, Client Ref Id, Division, Job Function, and Title. You can also assign roles, indicate active status, and set whether or not the user status expires.

3. Choose Remove in the Action column to remove a particular user. 4. You can sort users in ascending or descending order by clicking on Name,

Login Id, Email, or Active.

7.3. View Users by Roles

7.3.1. Displaying Role Privileges

To display the specific list of privileges available to each user level: 1. Choose Users > Roles. 2. Select a user role in the top part of the screen: administrator, superuser, or

viewer. 3. Click the Details tab in the lower part of the screen.


31

7.3.2. Displaying User Roles

To display a user by role: 1. Choose Users > Roles to view user roles, and the permissions that are assigned

to each role. 2. Click on a role in the top part of the screen: administrator, superuser, or

viewer. On the Details tab in the lower part of the screen, the associated permissions for that user role are listed.

3. Click the Users tab to show all current users assigned to the selected role. 1. Click the user name link in the Action column to edit the user’s information. 2. Click Remove to remove the currently selected role from a user. Any

remaining roles for that user are left unchanged. Enter a letter in the Filter by Last Name field to display only users whose names start with that letter. Enter additional letters to make the filter more specific.

7.4. Add a User 1. On the Users tab, click Add New User. 2. In the Add User dialog, enter information for the new user. Starred (*) fields

are required. All fields can be edited later, except Login ID and Domain. 3. In the Login ID field, type the user’s Windows login username. 4. Select the user’s Domain from the domains listed in the pull-down menu. 5. Enter the user’s first and last names. 6. Enter the email address if desired. 7. In the Client Ref ID field, insert any ID used by your organization as a unique

employee identifier. 8. The Division, Job Function, and Title fields contain optional information that

may be helpful. 9. Select one or more roles for the new user: Viewer, Administrator, or Superuser.

See About User Roles. 10. An Active user can log into and administer Avistar C3 Conference™ according

to his assigned role. If a user is not active, his account information remains in the Avistar C3 Conference™ database, but he does not have access to the program and to administrative functions.

11. Click Yes in Not Expire to prevent the account from expiring if the user doesn’t log in for a specified number of days. (Go to the Configuration > Settings tab to view or edit this time period). The account of at least one Superuser must be set to Not Expire, to prevent the possibility (however remote) of all users being locked out of the system.

7.5. Edit a User 1. Choose Users > Users. Users are listed in the top part of the screen. 2. Click on a line to select a user. 3. Do one of the following:

• Click the Edit link in the Action column. • Click the Edit button in the Details area.

Administering User Accounts

32

The Edit User dialog box displays. Required fields are marked with a red asterisk.

4. Click Save.

7.6. Remove a User 1. Choose Users > Users. Users are listed in the top part of the screen. 2. Click on a line to select a user. 3. Do one of the following:

• Click the Remove link in the Action column. • Click the Remove button in the Details area.

4. When prompted to delete the user, click Yes.


33

8. Reports

8.1. Conference Detail The Conference Detail report enables administrators to troubleshoot conference calls that occurred in the past. To utilize the Conference Detail report, logging must be enabled for Avistar C3 Conference. The Conference Detail report provides a list of all completed conferences in the top section of the page. Administrators can filter the conference list by time and Conference Name. Once the desired conference is found and selected in the top section, the bottom section shows additional details about the conference including: Participant lists, start times, duration, encryption status, call rate, resource units used, and network statistics by participant.

H.323 Endpoint Support

34

9. H.323 Endpoint Support Using Avistar C3 Connect™, administrators can enable H.323 endpoints to join conferences hosted by Avistar C3 Conference. Avistar C3 Connect is a signaling gateway between H.323 and SIP protocols. While Avistar C3 Connect participates in the call setup, it does not deal directly with the media streams exchanged during a call so media can flow directly between the endpoint and MCU. The diagram below shows the signaling and media flows of deployment with H.323 capabilities enabled.

9.1. Installation Avistar C3 Connect can be installed on the same host servers as the Conference Manager of Avistar C3 Conference. The installation procedure below assumes this deployment scenario. 1. Log in to the host machine as Administrator.

2. Double-click the installer file, C3ConnectSetup.exe, to start the installation wizard.

3. After accepting the license agreement, choose a destination folder for Avistar C3 Connect, or click Next to accept the default location.

4. Specify the ports used for the SIP TCP and the SIP UDP ports, or click Next to accept the default values. The installer should verify that the ports are available before proceeding

5. Click Install to start the installation.

6. Click Finish to complete the Avistar C3 Connect installation.

9.2. Configuration Administrators configure Avistar C3 Connect by modifying the sgw.ini file. Complete the following steps to use Avistar C3 Connect with Avistar C3 Conference:


35

9.2.1. General

1. Stop the Avistar C3 Connect service.

2. Change the autoStartMgr configuration parameter to True.

9.2.2. SIP Configuration

1. Change the SIP_InboundDialPattern configuration parameter to 1.

2. Change the SIP_AllowedServers configuration parameter to the IP address of your Avistar C3 Conference™ host server.

3. Change the SIP_B2bUAURL configuration parameter to the IP address of your Avistar C3 Conference™ host server.

9.2.3. H.323 Configuration

If the H.323 environment includes a gatekeeper with which Avistar C3 Connect registers, modify the following configuration parameters:

c. Set h323_Gk_Enable to True d. Set h323_GK_Addr to the IP address of your gatekeeper.

Additional details on configuring Avistar C3 Connect can be found in the Avistar C3 Connect XML API Reference Guide.

9.3. Calling a Meeting Room Once Avistar C3 Connect has been configured for use with Avistar C3 Conference, H.323 endpoints can join conferences hosted on the MCU. For H.323 endpoints in an unmanaged environment (no gatekeeper configured), the meeting room number is specified using the dialed digits. For example, an environment where Avistar C3 Conference™ and Avistar C3 Connect are hosted on a server with the IP address of 192.168.12.12, a Polycom endpoint would dial 192.168.12.12##1000 join the meeting room with a number of 1000. In an environment where Avistar C3 Connect is registered with a gatekeeper using the prefix 88, a Polycom endpoint would dial 881000 to be connected to the meeting room with a number of 1000. NOTE: Avistar C3 Conference™ does not currently support DTMF tone

detection so endpoints must send security PINs and layout change commands in the signaling channel. Endpoints from Cisco/Tandberg and LifeSize typically send DTMFs in the signaling channel when the remote party advertises this capability. Unfortunately, Polycom endpoints do not send DTMFs in the signaling channel and therefore can not joint meeting rooms with security PINs.


36

Appendix A: Resource Units Required by Resolution

The table below shows the Resource Units required for various call rates and resolutions, at 16:9 and 4:3 aspect ratios.

16:9 Aspect Ratio

Resolution Minimum Call Rate Resource Units per Endpoint

320 x 176 128 Kbps 7 400 x 224 128 Kbps 11 512 x 288 256 Kbps 17 592 x 336 256 Kbps 22 640 x 368 384 Kbps 26 704 x 400 384 Kbps 31 768 x 432 512 Kbps 36 848 x 480 512 Kbps 44 960 x 544 768 Kbps 56 1024 x 576 768 Kbps 63 1088 x 608 768 Kbps 70 1168 x 656 1024 Kbps 82 1280 x 720 (720p30) 1024 Kbps 98

4:3 Aspect Ratio Resolution Minimum Call Rate Resource Units per Endpoint

320 x 240 128 Kbps 10 384 x 288 256 Kbps 13 448 x 336 256 Kbps 17 512 x 384 256 Kbps 22 576 x 432 384 Kbps 27 640 x 480 384 Kbps 34 704 x 528 512 Kbps 40 768 x 576 512 Kbps 48 832 x 624 768 Kbps 56 896 x 672 768 Kbps 64 1024 x 768 1024 Kbps 83 1088 x 816 1024 Kbps 94


37

Appendix B: Logging Database Schema Avistar C3 Conference™ logs MCU usage data in the following SQL database tables:

Table name Stores information about

CONFERENCE_HISTORY Conference creation and termination for a particular meeting room

PARTICIPANT_HISTORY Details about each participant in a conference

SIGNALING_INFO Additional information about call signaling (SIP) for a call

STREAM_INFO RTP statistics for a single media stream

AVERAGE_STATISTICS RTP statistics for a single media stream

TOTAL_STATISTICS RTP statistics for a single media stream (overall information)

LOST_STATISTICS Lost statistics records

CONFERENCE_HISTORY A new record is added to this table every time a conference is created and it should be updated when the conference is destroyed. Notifications can be obtained through the ConferenceListener interface.

Column Name Column Type Value

ConferenceId CHAR(32), NOT NULL, Primary Key

Conference identifier, primary key. The value is automatically generated by conference engine for new conference.

Type VARCHAR(64), NOT NULL

Identifies conference type as MeetingRoom or AdHocConference.

RoomNumber VARCHAR(64), NULL

Meeting room number. NULL for ad-hoc conferences.

Address VARCHAR(256), NOT NULL

Address of the conference. It can be different for the same meeting room within this table because it depends on SIP registrar settings.

Name VARCHAR(256), NOT NULL

Name of the conference. Usually it is the meeting room name.

Hostname VARCHAR(256), NOT NULL

Avistar C3 Conference™ hostname, to separate logs from different controllers

MediaProcessorHostname VARCHAR(256), NULL

Media processor host name. Can be NULL if there are no free media processors.

StartTime TIMESTAMP, NOT NULL

Start time of the conference. Must be indexed because data usually are sorted by StartTime.

EndTime TIMESTAMP, NULL

End Time, in UTC. Set to NULL if the conference is still active.

EndReason VARCHAR(256), NULL

End Reason. Set to NULL if the conference is still active.

CallRate INT, NOT NULL

Configured maximum call rate.


38


MaxVideoResolutionWidth INT, NULL

Configured maximum video resolution, width in pixels. NULL for audio-only conferences.

MaxVideoResolutionHeight

INT, NULL

Configured maximum video resolution, height in pixels. NULL for audio-only conferences.

PARTICIPANT_HISTORY

A new record is added to this table every time a participant is added to a conference and it should be updated when the participant is removed. Notifications can be obtained through the ConferenceListener interface. For outbound calls, SIP-related information is unavailable but can be updated on an EndpointListener.statusChanged(...) event when the endpoint status becomes CONNECTED.


CallId CHAR(32), Primary Key

Call identifier, primary key. The value is automatically generated for a new call.

ConferenceId CHAR(32), NOT NULL

Conference identifier, foreign key to CONFERENCE_HISTORY.

CallType VARCHAR(64), NOT NULL

Identifies the call as Inbound or Outbound.

DisplayName VARCHAR(256), NULL

The display name of the remote user. This property may be NULL if the display name is not available. For outgoing calls, remote display name is optionally provided in ConferenceControl.addParticipant(…). For incoming calls, the field is retrieved from the From header of the incoming INVITE.

SipUri VARCHAR(256), NOT NULL

Participant SIP URI. Typically, this is its Address Of Record.

Contact VARCHAR(256), NOT NULL

Contact URI of the remote endpoint.

FromAddress VARCHAR(40), NULL

Participant IP Address.

SipCallId VARCHAR(64), NULL

The SIP call ID of the call. It can be NULL if the participant is added when the outgoing call is in the initialization state.

CallRate INT, NOT NULL

Participant Call Rate.


Start time of the call, in UTC. Must be indexed.

ReferredBy VARCHAR(64), NULL

User name of the user who brought this endpoint into the conference.

AcceptTime TIMESTAMP, NULL

The accept time of the call, in GMT. The accept time is defined as the time when 200 was sent for inbound calls, or when Conference receives the 200 response to the INVITE for outbound calls. It is NULL if the call never gets answered.

EndTime

TIMESTAMP, NULL

End time of the call, in UTC. Set to NULL if the call is still in progress.


39


EndReason VARCHAR(256), NULL

Records the reason for ending the call.

SessionType VARCHAR(64), NOT NULL

Identifies the call by media type as Audio or Video.

MaxUnits INT, NOT NULL

Maximum number of resource units allocated within the conference.

ActiveSpeaker TIME, NOT NULL

Total time during participant was the current speaker.

Secure CHAR(1), NOT NULL

Indicates if participant used secure connection (‘Y’) or unsecure (‘N’). Default value is ‘N’.

SIGNALING_INFO

A new record is added to this table every time endpoint changes status to DISCONNECTED. Notifications can be obtained through the EndpointListener interface.


CallId CHAR(32), Primary Key, Foreign Key

Call identifier, primary key and foreign key to PARTICIPANT_HISTORY table.

SipRoute TEXT, NULL

The route set for the call. In the current implementation, this string includes the SIP proxy URL, if configured. The route set may be updated by Record-Route headers in incoming messages. This property includes zero or more SIP URLs separated by pairs of CR LF characters (\u000D\u000A).

SipVias TEXT, NULL

The set of Via header fields for the call. This property returns a non-empty value only if one or more SIP requests are received for this call. This property includes zero or more SIP Via header field values separated by pairs of CR LF characters (\u000D\u000A).

SipUserAgent VARCHAR(64), NULL

Contains the value of the User-Agent header.

SipInviteResponseCode INT, NULL Contains the response code for the SIP INVITE. Only valid for outgoing calls.

SipInviteResponseMessage VARCHAR(256), NULL

Contains the response message for the SIP INVITE. Only valid for outgoing calls.

SipInviteWarningCode INT, NULL Contains the warning code for the SIP INVITE. Only valid for outgoing calls that fail and return a response with a Warning header field; otherwise NULL.

SipInviteWarningHost VARCHAR(64), NULL

Contains the warning host for the SIP INVITE. Only valid for outgoing calls that fail and return a response with a Warning header field; otherwise NULL.

SipInviteWarningMessage VARCHAR(256), Contains the warning message for the SIP


40

NULL INVITE. Only valid for outgoing calls that fail and return a response with a Warning header field; otherwise NULL.

STREAM_INFO A new record is added to this table or updated on CallStatisticsListener.callStatistics (…) event.


StreamId INT, AutoIncrement, Primary Key

Stream identifier, primary key. The value is automatically generated for new records.

CallId CHAR(32), Foreign Key

Call identifier, foreign key to PARTICIPANT_HISTORY table.

Type VARCHAR(64), NOT NULL

Describes direction of this stream. It can be Sending or Receiving.

MediaType VARCHAR(64), NOT NULL

The media type for the stream. This corresponds to the media type field in SDP (e.g., “audio”, “video”, “application”).

MediaProcessorIP VARCHAR(40), NULL

IP address of the media processor.

MediaProcessorRTPPort INT, NULL Media processor local port number used by RTP protocol for this stream.

MediaProcessorRTCPPort INT, NULL Media processor local port number used by RTCP protocol for this stream.

RemoteIP VARCHAR(40), NULL

Remote IP address

RemoteRTPPort INT, NULL Remote port number used by RTP protocol for this stream.

RemoteRTCPPort INT, NULL Remote port number used by RTCP protocol for this stream.

AVERAGE_STATISTICS

A new record is added to this table or updated on CallStatisticsListener.callStatistics (…) event.


StreamId INT, Primary Key, Foreign Key

Stream identifier, primary key and foreign key to STREAM_INFO.

WireDataRate BIGINT, NOT NULL, DEFAULT 0

The data rate used by this stream, including IP, UDP and RTP overhead, in kilobits per second.

PayloadDataRate BIGINT, NOT NULL, DEFAULT 0

The data rate used by this stream, excluding IP, UDP and RTP overhead (e.g., payload data only), in kilobits per second.

PacketRate BIGINT, NOT NULL, DEFAULT 0

The packet rate for this stream, in packets per second.

FrameRate BIGINT, NOT NULL, DEFAULT 0

The frame rate for this stream, in frames per second. Typically, for audio streams frame rate equals the packet rate, while for video streams the packet rate is higher.


41

Jitter BIGINT, NOT NULL, DEFAULT 0

The average delay for incoming packets in the jitter buffer, in milliseconds. Returns 0 for RTP sending statistics.

TOTAL_STATISTICS

A new record is added to this table or updated on CallStatisticsListener.callStatistics (…) event.


StreamId INT, Primary Key, Foreign Key

Stream identifier, primary key and foreign key to STREAM_INFO.

Codec VARCHAR(64), NOT NULL

The name of the codec used for this stream. If more than one codec was used, the last codec used for the call is reported here.

VideoResolutionWidth INT, NULL

The last used video resolution width, in pixels, for this stream. NULL for non-video streams.

VideoResolutionHeight INT, NULL

The last used video resolution height, in pixels, for this stream. NULL for non-video streams.

WireBytes BIGINT, NOT NULL, DEFAULT 0

The total number of bytes sent or received, including IP/UDP/RTP overhead.

PayloadBytes BIGINT, NOT NULL, DEFAULT 0

The total number of bytes sent or received, not including IP/UDP/RTP overhead.

Packets BIGINT, NOT NULL, DEFAULT 0

The total number of packets sent or received.

Frames BIGINT, NOT NULL, DEFAULT 0

The total number of frames sent or received.

LostPackets BIGINT, NOT NULL, DEFAULT 0

The total number of packets lost in the network. Returns 0 for the RTP sending statistics.

LatePackets BIGINT, NOT NULL, DEFAULT 0

The total number of late packets (packets that are received too late to be decoded). Returns 0 for the RTP sending statistics.

DroppedPackets BIGINT, NOT NULL, DEFAULT 0

The total number of dropped packets (packets that were received in time but for any reason were not submitted for decoding). Returns 0 for the RTP sending statistics.

DroppedFrames BIGINT, NOT NULL, DEFAULT 0

The total number of dropped frames. Returns 0 for the RTP sending statistics.

SkippedFrames BIGINT, NOT NULL, DEFAULT 0

The total number of skipped frames. Returns 0 for the RTP sending statistics.

FastUpdateRequests INT, NOT NULL, DEFAULT 0

Video stream fast update requests

VideoResolution Constraints

VARCHAR(20) For video stream info – video resolution constraints

NegotiatedBandwidth NT, NOT NULL, DEFAULT 0

Negotiated bandwidth

Jitter NT, NOT NULL, Average delay time to compensate jitter, in ms;


42

Column Name Column Type Value DEFAULT 0 for incoming direction statistics only

WireDataRate NT, NOT NULL, DEFAULT 0

Bandwidth used by the call, in kbps. This parameter includes IP/UDP/RTP overhead

PayloadDataRate NT, NOT NULL, DEFAULT 0

Bandwidth used by the call, in kbps. The bandwidth does not include IP/UDP/RTP overhead, but includes codec-specific RTP headers

MinJitter NT, NOT NULL, DEFAULT 0

Minimum delay time to compensate jitter, in ms; for incoming direction statistics only

MaxJitter NT, NOT NULL, DEFAULT 0

Maximum delay time to compensate jitter, in ms; for incoming direction statistics only

LOST_STATISTICS


LostId INT, Primary Key

Lost statistics identifier, primary key. The value is automatically generated for new records.

Hostname VARCHAR(256), NOT NULL

Avistar C3 Conference™ hostname, to separate logs from different controllers


Time of the first missed record, in UTC.

Reason TEXT, NOT NULL

Error description that caused lost records.

EndTime TIMESTAMP, NOT NULL

Time when logging was restored, in UTC.

Count BIGINT, NOT NULL, DEFAULT 0

Number of missed records/updates.


43

Appendix C: Firewall Ports The table below presents the default port usage from the vantage point of an Avistar C3 Conference™ server.

Local Port Default Configurable Remote Port Usage

TCP 8443 Yes All Administrators (Dynamic TCP Port 1024 - 65534)

Avistar C3 Conference™ web-based management interface used by administrators.

Dynamic TCP Port

1024 - 65534

N/A MS SQL Server for Call Logging (TCP 1433)

Avistar C3 Conference™ accesses a MS SQL Server database to store call logging details.

TCP/UDP 5060 Yes Avistar C3 Endpoints (TCP/UDP 5060-5069) Avistar Call Control Server (TCP/UDP 5060)

When unregistered with a SIP Registrar, Avistar C3 Conference™ uses this port for SIP signaling with Avistar C3 Endpoints. When registered with an Avistar C3 Call Control™ server, this port is used for SIP signaling with the Avistar C3 Call Control™ server.

TCP 5061 Yes Standalone SIP Endpoints (TCP 5061)

Avistar Call Control Server (TCP 5061)

Avistar Media Processor (TCP 5061)

When unregistered with a SIP Registrar, Avistar C3 Conference™ uses this port for secure SIP signaling with Avistar C3 Endpoints. When registered with an Avistar C3 Call Control™ server, this port is used for secure SIP signaling with the Avistar C3 Call Control™ server. When the Avistar Conference Controller and Avistar Media Processor are hosted on different machines.

UDP 60000 - 64999

Yes All Avistar C3 Endpoints (UDP 4200-4299)

RTP audio and video traffic for conferences hosted on Avistar C3 Conference™.

Documents

1. About Avistar C3 Conference™ ........................................................................ 1. 1.1. Introduction