Avaya Video Conferencing Manager Deployment Guide Issue 1 June 2010
© 2010 Avaya Inc. All Rights Reserved. Notices While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes.
License types Designated System(s) License (DS). End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User.
Welcome to Avaya Video Conferencing Manager Avaya Video Conferencing Manager is a comprehensive management software solution for network administrators who manage video and voice communications systems in an IP environment. With Avaya Video Conferencing Manager, network administrators can do the following: • Monitor and manage multi-vendor video and voice communications devices across the entire enterprise from a web browser.
About this Guide This guide is for network administrators or anyone who manages video and voice communications systems in an IP environment and who needs to know how to install, upgrade, use, or maintain Avaya Video Conferencing Manager.
Deployment Overview The following diagram shows the high-level tasks and associated dependencies involved in deploying Avaya Video Conferencing Manager for the first time. Use this diagram as a guide when preparing a schedule to include in your deployment plan. The tasks associated with Microsoft Exchange Server integration appear in blue with dotted line connectors.
Planning for Integration with Microsoft Exchange Server The most important decision to make when planning an Avaya Video Conferencing Manager deployment is whether to enable Microsoft Exchange Server integration when you install Avaya Video Conferencing Manager.
This feature also enables the meeting organizer to convert a video call from one that is placed automatically by Avaya Video Conferencing Manager to one that is placed manually by meeting participants. For more information about enabling and using this feature, refer to “Specifying a Preferred Method of Participation” on page 83.
Microsoft Exchange Server Integration Overview Integrating Avaya Video Conferencing Manager with Microsoft Exchange Server includes the following tasks: 1. Create an email account in Microsoft Exchange Server for Avaya Video Conferencing Manager. This is the email account Avaya Video Conferencing Manager monitors to provide scheduling integration with Microsoft Exchange Server and Microsoft Outlook. Set the size of this mailbox to 500MB.
- Avaya Video Conferencing Manager email password. This is the password for the email account described in task 1. 4. After installing or upgrading Avaya Video Conferencing Manager, you can deploy the integration in one of the following ways. Refer to “Configuring Microsoft Exchange Server” on page 36 for detailed configuration steps for these options.
Option 2: Create a resource mailbox in Microsoft Exchange Server for each video or voice communications system managed by Avaya Video Conferencing Manager. Forward each mailbox to the Avaya Video Conferencing Manager mailbox. In Avaya Video Conferencing Manager, associate the managed video or voice communications system with the email address of the mailbox resource.
Preparing Your Environment Whether you are installing Avaya Video Conferencing Manager for the first time or upgrading from a previous release, ensure that your environment meets the hardware and software prerequisites, including port access and client support requirements, in “Planning to Install Avaya Video Conferencing Manager Software” on page 14. Gathering Device Usernames and Passwords After you install Avaya Video Conferencing Manager, you can use it to discover and manage supported devices.
You can also forward traps from all managed video and voice communications devices to third party monitoring systems using the Northbound Settings page in Avaya Video Conferencing Manager Administrator or on a device-specific basis using the Northbound tab in the Device details page for a single device. For more information refer to “Using Avaya Video Conferencing Manager Administrator” on page 88 and “Forwarding SNMP Traps with Northbound Settings” on page 53.
Developing a Training Plan Use the procedures in this manual and information about user roles to assist you in developing a training plan and training materials customized to your environment. If you enabled Microsoft Exchange Server integration with your installation, both Avaya Video Conferencing Manager users and Microsoft Outlook users will need to know how to schedule video and voice calls through Microsoft Outlook.
Hardware Avaya Video Conferencing Manager supports the following minimum server configuration: • 2.4GHz Pentium 4 processor • 1GB RAM • At least 500MB of free hard disk drive space (Avaya recommends 4GB) Note: Dual NIC cards are not supported on the Avaya Video Conferencing Manager server.
The Avaya Video Conferencing Manager installation program installs an OpenLDAP server, the Microsoft .NET Framework 2.0 if not already installed, and PostgreSQL v8.3. You must be logged in as a user with administrator privileges to install these programs. Before you run the installation program, ensure that the following prerequisites are met on the computer on which you intend to install Avaya Video Conferencing Manager: • You have administrator rights to install the applications.
Client Support You can access the Avaya Video Conferencing Manager user interface from a computer equipped with the following: • A supported web browser (refer to the Release Notes at support.avaya.com) • 256MB memory • Adobe Flash Player (refer to the Release Notes at support.avaya.com for supported versions) Note: Adobe Flash Player is included with the Avaya Video Conferencing Manager installation program as an optional installation step, or you can download it directly from www.adobe.com.
Avaya Video Conferencing Manager supports management of video communications devices through standard APIs such as those listed in the following table. Communication with these devices is through default ports provided for FTP, SNMP, and HTTP.
Installing Avaya Video Conferencing Manager Before installing Avaya Video Conferencing Manager, ensure that your environment meets all hardware and software requirements described in “Planning to Install Avaya Video Conferencing Manager Software” on page 14.
Installing Windows Components Before installing Avaya Video Conferencing Manager, you must install the following Microsoft Windows components on the server: • Application Server Console • ASP.NET • Enable Network COM+ Access • Enable Network DTC Access • Internet Information Server (IIS) To install the Microsoft Windows components, follow these steps: 1. From the Windows Control Panel, choose Add or Remove Programs and click Add/Remove Windows Components in the left panel. 2.
Running the Installation Program The Avaya Video Conferencing Manager installation program installs and prompts you to configure the Avaya Video Conferencing Manager software and an OpenLDAP server.
2. To configure Avaya Video Conferencing Manager, enter values for the following fields. Note: The SMTP server and email addresses are required for alerts. a. SMTP Server—Enter the fully qualified domain name of the SMTP server for your organization. b. To Email Address—Enter the email address of the recipient who will receive alerts. c. From Email Address—Enter the email address that will appear as the From address of an alert message. For example: Avaya_Video_Conferencing_Manager@example.com) d.
4. Complete the LDAP server configuration by entering values in the following fields: a. In the OpenLDAP Settings area, complete the following: • From the OpenLDAP Server IP list, select the IP address for the OpenLDAP server. OpenLDAP installs on the same server as Avaya Video Conferencing Manager. • Specify a Port to use. The default is port 389. • Specify the domain suffix for the OpenLDAP directory tree structure. For example, example.com. b.
5. By default, Enable Exchange server integration with Avaya Video Conferencing Manager is selected. Complete the following fields: - If your Microsoft Exchange Server requires HTTPS access, select the Exchange server requires HTTPS access check box. - Click either Exchange 2003 or Exchange 2007 to specify which version of Microsoft Exchange Server you wish to integrate with Avaya Video Conferencing Manager. - Enter the Microsoft Exchange Server’s IP address in Exchange Server address.
8. Click Configure and then click OK. Note: If the installation fails, refer to “Troubleshooting Avaya Video Conferencing Manager” on page 95. If you must reinstall Avaya Video Conferencing Manager after fixing the problem, ensure that you uninstall the OpenLDAP server and the PostgreSQL database before attempting to install again. Refer to “Removing Avaya Video Conferencing Manager” on page 99. 9. Click Finish. The Avaya Video Conferencing Manager installation is complete. 10.
• If OpenSSL exists on the server, ensure that the version is 0.9.7 or later or delete the LIBEAY32.dll and SSLEAY32.dll files (located in the C:\windows\system32 folder). The Avaya Video Conferencing Manager installation program installs a compatible version of these files if OpenSSL does not exist on the server. Caution: If the Avaya Video Conferencing Manager installation program detects an earlier version of OpenSSL, an error message appears indicating that you must delete the LIBEAY32.
Configuring Your Environment After installing Avaya Video Conferencing Manager, configure your environment by completing the following tasks: • Access Avaya Video Conferencing Manager from your web browser. • Activate Avaya Video Conferencing Manager with a license key. • Specify default passwords for device management. • Discover the devices on your network. • Familiarize yourself with the Avaya Video Conferencing Manager Dashboard.
4. Enter a User name and Password. These values are the user name and password that you entered for user authentication in step 4 on page 23. Note: If cookies are enabled on your browser, Avaya Video Conferencing Manager remembers the user name and password for subsequent sessions if you select the Remember me check box. 5. Press the Enter key or click the LOGIN button. The Avaya Video Conferencing Manager Dashboard appears.
Activating Avaya Video Conferencing Manager without Internet Access To activate Avaya Video Conferencing Manager manually without Internet access, follow these steps: 1. Call the Avaya Video Technical Center at 800-242-2121 extension 15626 requesting an unlock key for your license key. The following information is required: - Customer name - Sold to or Functional location - Purchase Order number - MAC address - License key - Channel Partner or reseller (if applicable) 2.
Specifying Default Passwords for Device Management When Avaya Video Conferencing Manager attempts to manage devices, it uses the device logon information that you specify for each make of supported third-party device in the Password page. Note: Avaya Video Conferencing Manager automatically uses the default command line interface user (auto) and password (avaya) when attempting to manage Avaya devices.
By default, Avaya Video Conferencing Manager uses SNMP to show detailed information about a discovered device, such as its make, model, and software version. The community string is a password used to access the device when you are sending SNMP traps. If the community string is correct, the device responds with the requested information. If the community string is incorrect, the device simply discards the request and does not respond. The default value of the community string is public.
5. The Start managing once discovered check box is selected by default. This enables Avaya Video Conferencing Manager to attempt to log into a device after discovering it, maintain communication with the device, and enables you to manage the device through Avaya Video Conferencing Manager. Consider clearing this check box if you have fewer licenses in Avaya Video Conferencing Manager than devices on your network or you do not wish to manage certain devices in Avaya Video Conferencing Manager. 6.
Using the Avaya Video Conferencing Manager Dashboard The Avaya Video Conferencing Manager Dashboard provides a comprehensive view of your video and voice communications systems and their status, at a glance.
1. Device Inventory—lists the number of known devices and the total number of licenses purchased and in use 2. Upgrades—lists scheduled and in-progress device upgrades 3. Call History—lists call history and statistics at a glance 4. Alarms—lists current alarms and alarm history 5. Calls—lists current and scheduled calls Click any row in these sections of the dashboard to obtain more detailed information or perform a variety of management tasks. 6.
Icon Mouse-over Text Description Packages Upload upgrade packages to Avaya Video Conferencing Manager. Available to administrators and engineers only. Password Specify default passwords for devices and protocols. Available to administrators only. User Management Add or import, delete, or modify Active Directory or OpenLDAP users. License Manager Activate Avaya Video Conferencing Manager software. Available to administrators only.
Configuring Microsoft Exchange Server If you enabled integration with Microsoft Exchange Server when you installed Avaya Video Conferencing Manager, you can add Microsoft Exchange Server mailbox resources for your managed video and voice communications systems and MCUs. Once you create the mailbox resources in Microsoft Exchange and register your managed communications systems with those mailboxes, Microsoft Outlook users can schedule those devices as required participants or locations in meeting requests.
3. Enter the Full name, and User logon name and click Next. 4. Enter and confirm the user’s password, select Password never expires and click Next. 5. Select Create an Exchange mailbox and enter an Alias, Server, and Mailbox Store. Click Next. 6. Click Finish. 7. Configure forwarding of the messages sent to this mailbox to include Avaya Video Conferencing Manager’s listener mailbox. a. Right-click the user you created in step 5 and select Properties.
Microsoft Exchange Server 2007 The following instructions apply specifically to Microsoft Exchange Server 2007. If you are using Microsoft Exchange Server 2003, refer to “Microsoft Exchange Server 2003” on page 36.
10. Right-click and select Reset Password. 11. Enter and confirm the password and select Password never expires. 12. If you are creating a mailbox for an MCU, skip to step 16. 13. In Microsoft Outlook Web Access, log on to the email account for the video communications system and click Options in the upper right-hand corner of the window. 14. In the Options menu click Resource Settings and enable Automatically process meeting requests and cancellations. 15. Click the Save button. 16.
5. Enter the mailbox resource you created for it and click Register. Avaya Video Conferencing Manager confirms successful registration both by changing the yellow envelope icon from to and by writing a confirmation message to the Status box below the list of devices. Note: If the mailbox registration fails, Avaya Video Conferencing Manager writes an error message to the Status box below the list of devices.
For more information about access to specific functionality for each user role, refer to “Appendix A: User Role Access” on page 101. Note: New users are automatically assigned the Operator role. Refer to “Adding a User Account” on page 41 for details about adding a user. Refer to “Modifying a User Account” on page 42 for details about changing a user’s role.
Adding Users from OpenLDAP If you chose OpenLDAP for user authentication when you installed Avaya Video Conferencing Manager, you can add new users as follows: 1. Click the User Management icon on the navigation bar. 2. Click the Add User button. 3. Enter a login name for the user. 4. Enter a user name for the user. 5. Enter an email address for the user. 6. Click the Update button and enter a password for the new user. Note: Passwords for OpenLDAP users are case sensitive. 7. Click Submit. 8.
Managing Devices After you discover and enable Avaya Video Conferencing Manager to manage devices, you can perform a variety of management tasks on these devices from the Devices page. For information about discovering devices, refer to “Discovering Devices” on page 31. To access the Devices page, click the Devices icon on the navigation bar or click any device category in Device Inventory on the Avaya Video Conferencing Manager Dashboard.
• Depending on the device type and its status, one or more of the following icons may appear in the far-right column. Text that describes an icon’s meaning appears when you mouse over the icon. Icon Description This icon appears only if you opted to enable Microsoft Exchange Server integration when you installed Avaya Video Conferencing Manager and only for managed devices that can be scheduled in a call using the Microsoft Exchange Server integration feature.
Status Icons The following icons represent the device status. Mouse over an icon to view text that describes the icon. Icon Status Discovered To enable Avaya Video Conferencing Manager to manage this device, right-click the device entry, and then click Start managing. Login failed. Update the password. Refer to “Managing Device Passwords” on page 58 to update the password. Responding Unreachable Rebooting Managing Updating device information Deleting External device.
Icon Status Call in progress Two-way inbound call Two-way outbound call Multipoint inbound call Multipoint outbound call Displaying Devices On the Display list, choose the category of devices to view. Display categories include the following: Display Category Description All All discovered and external devices Managed: all Devices that are managed by Avaya Video Conferencing Manager.
Display Category Description MCUs All managed multipoint control units Gateways All managed gateways Gatekeepers All managed gatekeepers Unmanaged Devices with a Discovered or Login failed status icon in the Status column Devices in a call All managed devices that are currently in a call Devices being upgraded All managed devices currently being upgraded External Devices All external devices. For more information, refer to “Adding a New External Device” on page 48.
To search for a single device, enter any alphanumeric string in the Search field located in the lower right corner of the page. The search field is case sensitive. Adding a New External Device You can add an external device to the Devices page to identify devices that are frequently used in calls but may be unreachable by Avaya Video Conferencing Manager, such as a device that you do not wish to manage in Avaya Video Conferencing Manager or a device not on your organization’s network.
Refreshing Device Information You can refresh information that appears on the Devices page for all devices or for a single device. Refresh Information for all Devices 1. On the Actions menu, click Refresh all. 2. Click Submit. Refresh Information for a Single Device 1. Right-click the device entry. 2. Click Refresh. Accessing Device Management Features Management tasks that you can perform depend on the device’s type and status. Right-click a device entry to view the tasks available for that device.
Task Device Type Description View Alarms Managed video and voice communications devices except Sony PCS-XG80 Opens the Alarms page and shows the alarms for the device. For more information about alarms, refer to “Managing Device Alarms” on page 63. Create Template Managed Avaya and LifeSize video communications systems only Create a configuration template from an existing managed Avaya video communications system.
Task Device Type Description Reboot All devices except gatekeepers and Sony PCS-XG80 Reboots the device. The device must not be in use. You can safely reboot the device when the Responding icon appears as the device status. Refer to “Rebooting a Device” on page 59. Delete Device All devices Deletes a device entry from the Devices page and from all scheduled calls and events. If the device is the host in a scheduled call, the call is deleted.
• If the device is an Avaya video communications system, you can also access many of the configuration preferences that are available in the device’s web administration interface and show video snapshots. Note: For external devices, Avaya Video Conferencing Manager offers a device details page on which you can record information about the device. For more information about external devices, refer to “Adding a New External Device” on page 48.
4. On the System information tab, locate the Generic properties page. 5. In the Service prefix list, click the service prefix you wish to use. The maximum bandwidth and maximum participants for that prefix appear below the list. Note: If the service prefix you select is subsequently deleted on the MCU, Avaya Video Conferencing Manager chooses the next available prefix with the highest bandwidth allowed. If no services are registered on the MCU, a scheduled call with this MCU fails. 6. Click Save.
By default, trap forwarding is enabled. To disable trap forwarding, clear the Enable Avaya Video Conferencing Manager Northbound Settings check box on the Northbound Settings page in Avaya Video Conferencing Manager Administrator and refresh your browser. If you disable trap forwarding, the Northbound tab on the Device details page does not appear. For more information about using Avaya Video Conferencing Manager Administrator, refer to “Using Avaya Video Conferencing Manager Administrator” on page 88.
Setting or Clearing MCU Affinity You can use cascading MCUs to connect calls between two groups of participants. Each groups' communication is channeled through one MCU, and the MCUs pass the bundled communication between each other, greatly reducing the bandwidth needed for the groups to communicate with each other. To use this optional feature when scheduling a call, the devices in the call must be assigned affinity to an MCU. Assigning MCU affinity to devices has additional benefits.
For more information about using cascading MCUs when scheduling a call, refer to “Using Cascading MCUs” on page 78. Registering a Device to a Gatekeeper You can register a managed device to a managed gatekeeper by completing the following steps: 1. Access the Devices page. 2. On the Display list, click Managed: all. 3. Locate the entry for the device that you wish to register with a gatekeeper and click the register with gatekeeper icon in the far-right column.
Sending a Message to a Device You can send a message to a managed video communications device to appear in the display connected to the device. The message appears in a dialog box with an OK button for users to acknowledge and close the message. Note: This feature is available only for managed Avaya, LifeSize, Polycom, and Tandberg video communications systems. If not acknowledged, the message closes after 10 seconds on Avaya and LifeSize video communications systems only.
Accessing a Device’s Web User Interface You can open the web user interface of any discovered device to access the configuration options on that device. Refer to the documentation included with your device for more information. To open a device's web user interface, follow these steps: 1. Access the Devices page. 2. Right-click the device that you wish to access. 3. Select Launch browser interface.
Changing a Device Password You can use Avaya Video Conferencing Manager to change the password stored on a device only if the device is managed in Avaya Video Conferencing Manager. Changing a password on a managed device changes the password stored on the device and automatically updates the password that Avaya Video Conferencing Manager stores in its database and uses to contact the device. To change the password on a managed device, follow these steps: 1. Access the Devices page. 2.
Deleting a Device Deleting a device from Avaya Video Conferencing Manager results in the following actions: • Avaya Video Conferencing Manager removes the device from the Devices page and from all scheduled calls and events in which the device is a participant. • If the device is a participant in a call scheduled through Microsoft Outlook and Microsoft Exchange Server integration is enabled, Avaya Video Conferencing Manager notifies the meeting organizer of the change.
Managing a Device Through Email If you enabled and configured Microsoft Exchange Server integration with your Avaya Video Conferencing Manager installation, Avaya Video Conferencing Manager administrators can send management commands to managed video communications devices using email. The To field of the email message must contain the email address of one or more managed devices. Administrators can send an email as plain-text, HTML, or rich-text.
Command Applies to these Makes Action Executed on Device BACKUP Avaya BACK-UP LifeSize Backs up the current device settings as a template. BACK UP CALLSTATS Avaya CALL STATS LifeSize CALL STATISTICS Polycom Retrieves the calls statistics for all video communications systems to which the email is sent. Tandberg Sony DESCRIBE All managed devices Retrieves the details of the devices to which the command was sent.
Command Applies to these Makes Action Executed on Device AUTOSH Avaya Executes a command line interface (CLI) command on an Avaya or LifeSize device. Enter AUTOSH in the Subject field and the CLI command in the body of the message (for example, get system name). LifeSize Avaya Video Conferencing Manager sends an individual response email (success or failure) to indicate the result of the action taken on each of the devices on which a command was executed.
Alarms are color-coded to assist you in identifying alarms by severity. Color Severity Red High Orange Medium Green Low Purple Information You can sort alarms by clicking any column heading on the Active alarms or History alarms tabs. On the Active alarms tab, use the Filter by list to view a list of alarms by severity, alarms assigned to you, or new alarms since the last time you logged in to Avaya Video Conferencing Manager.
• Export alarms on the History alarms tab. Use the Export/Backup list to export all or selected history alarms as a CSV or XML file. You can also access these export options by right-clicking an alarm on the History alarms tab. Upgrading Devices Upgrading a device from Avaya Video Conferencing Manager includes the following tasks: 1. Download the upgrade package from the device manufacturer to a location on your network that is accessible to Avaya Video Conferencing Manager. 2.
Using Templates to Configure Devices Templates in Avaya Video Conferencing Manager are stored configurations for Avaya or LifeSize video communications systems that you can apply to a single device or multiple devices simultaneously. Use templates when you want to ensure that these managed devices are consistently configured across your organization to achieve any of the following goals: • Quickly configure new video communications systems that are added to your network.
Creating and Editing Templates To create a template, follow these steps: 1. Click Templates in the navigation bar. 2. On the Actions menu, choose either Create template to create a new template or Create template from device to create a template based on the configuration of an existing device. 3. Click Submit. 4.
4. Check for template application errors. On the Actions list, select View logs and click Submit. The View logs dialog box appears and indicates the status of the operation. The Failed parameters list identifies parameters that were not updated correctly during the template application. Comparing a Template You can compare a template immediately to an existing device’s configuration, or schedule a template comparison for a future date and time.
6. Click Ok. 7. Name the backup file and save it. Restoring a Device from a Backup To restore settings from a backup file to a device, follow these steps: 1. Click the Templates icon in the navigation bar. 2. Choose Restore device on the Actions menu. 3. Click Submit. The Restore device dialog box appears. 4. Choose the device to restore. 5. Choose a backup from those available. Note: A backup can only be restored on the device from which it was generated. 6. Click Ok.
Scheduling Calls and Other Device Events On the Events page, you can schedule and view scheduled calls, upgrades, template events, calls or upgrades in progress, devices taken offline, and events for a particular time frame. Click the Events icon in the navigation bar and choose an option from the Display list. You can also do the following: • Sort a list by clicking a heading. For example, to sort events by status, click the Status heading.
Icon Description Call pending Call terminated Call failed Updating event information Template comparison pending Template comparison in progress Template comparison successful Upgrade in progress Upgrade failed Upgrade pending Upgrade successful Device offline scheduled 70 Avaya Video Conferencing Manager Deployment Guide
Icon Description Device offline terminated Device offline completed Device offline in progress Device offline failed The following event icons can appear in the Type column to indicate additional details about an event: Icon Description A recurring event A call scheduled from Microsoft Exchange Server. An adhoc call initiated by an Avaya Video Conferencing Manager administrator using the email-based CALL command. For more information, refer to “Managing a Device Through Email” on page 61.
To schedule template actions, follow these steps: 1. Click the Events icon on the navigation bar. 2. On the Actions list, choose Schedule Template. 3. Click Submit. 4. Enter the details for the template action. a. Enter a name for the action. b. Enter a start date and time and an end date and time. c. Select the Make, Model and Version. If you select common for Model, the action only affects the settings that the devices share with the template. d.
Scheduling a Device Software Upgrade To schedule the application of one or more software upgrade packages to your devices, follow these steps: 1. Click the Events button in the navigation bar. 2. Choose Schedule Upgrade from the Actions menu. Note: On the Devices page, you can also right-click a managed device, or select multiple devices of the same make and model, and then right-click to schedule an upgrade. 3.
Scheduling Offline Time for a Device You can take a managed device (excluding gatekeepers and gateways) offline for a specified period of time so that Avaya Video Conferencing Manager users (and Microsoft Outlook users if Microsoft Exchange Server integration is enabled) cannot use the device in any scheduled events or manage the device in Avaya Video Conferencing Manager during that time period.
f. When you are finished viewing or modifying the conflicting events, click Confirm at the bottom of the Events page to delete or modify the conflicting events and create the offline event. The device offline event appears on the Events page as a scheduled event. Scheduling a Conference in Avaya Video Conferencing Manager To schedule conferences from Avaya Video Conferencing Manager, follow these steps: 1. Click the Events icon on the navigation bar. 2. Choose Schedule Call from the Actions list. 3.
c. If you need to add an external device that is not available for selection in the Add Device dialog box, click Add External Device. In the Add External Device dialog box that appears, specify the protocol to use to connect to the device, enter the IP address or number to use to dial the device, and click the plus icon. d. You can add an MCU to the call by clicking the Add MCU button, selecting one from the list that appears, and clicking Add.
7. Click Call Now to begin the call immediately or Schedule Call to begin the call at the specified time. If the call is not configured properly, an error message appears asking you to configure the call. Click Configure for Avaya Video Conferencing Manager to choose a valid configuration for the call. Note: You may encounter a configuration error indicated by an error icon that requires your intervention.
Using Cascading MCUs You can use cascading MCUs to connect calls between two groups of participants. Each groups' communication is channeled through one MCU, and the MCUs pass the bundled communication between each other, greatly reducing the bandwidth needed for the groups to communicate with each other. For example, eight participants on a network in Japan want to conference with a group of seven participants on a network in Europe.
Modifying or Deleting Scheduled Conferences To modify or delete a scheduled conference, follow these steps: 1. Click the Events icon on the navigation bar. The Events page appears. 2. On the Display menu, click Display Scheduled Events. 3. Right-click the event entry for the call you wish to modify or delete and do one of the following: - To delete a scheduled conference, right-click the event entry you wish to delete and choose Delete Schedule.
Viewing a Call in Progress You can view a call in progress by completing the following steps: 1. From Avaya Video Conferencing Manager Dashboard, do one of the following: - Click Currently in progress under Calls. - Click the Events icon in the navigation bar. On the Events page, select Calls in progress on the Display list. 2. Right-click a call and select Add or Remove Participants.
If none of the devices that the meeting organizer invites to the call is capable of hosting the call, Avaya Video Conferencing Manager automatically adds an available MCU to the schedule and includes the device in the email confirmation that it sends to the meeting organizer. Cascading MCUs are not available through Microsoft Outlook.
If a PIN is required for the call and Avaya Video Conferencing Manager is configured to automatically generate a PIN for calls scheduled with an MCU from Microsoft Outlook, Avaya Video Conferencing Manager sends the PIN to the meeting organizer in the confirmation email when the call is scheduled. The PIN can be modified only in Avaya Video Conferencing Manager. If modified, Avaya Video Conferencing Manager sends an email to the meeting organizer indicating the new PIN.
Specifying a Preferred Method of Participation If you enabled and configured Microsoft Exchange Server integration with Avaya Video Conferencing Manager, you can allow human participants in video calls scheduled in Avaya Video Conferencing Manager through Microsoft Outlook to specify a video communications system through which they can be reached. To be included in the scheduled call, the device must be an external device that is not managed by Avaya Video Conferencing Manager.
When this feature is enabled and a meeting organizer schedules a video call in Avaya Video Conferencing Manager through a meeting invitation in Microsoft Outlook, Avaya Video Conferencing Manager sends a confirmation email to all human participants. The email includes the conference details: the date and start time of the call, the call reservation type, and the IP addresses of the video devices that are scheduled to participate in the call.
The confirmation email sent from Avaya Video Conferencing Manager to participants who are not managed devices indicates the commands available and its usage to the invitees. The following rules must be observed by invitees who wish to reply: • The confirmation email includes a conference identifier in the body of the message. Invitees who reply must include the conference identifier in the reply. • The reply must be plain text. Other text formats are not supported in this release.
Generating Reports Avaya Video Conferencing Manager provides powerful, graphical report generation capabilities for collected performance data. You can generate data and graphical reports that you can export to PDF or CSV formats. You can also subscribe to a recurring report that is sent to the email address associated with your user account. To view reports, follow these steps: 1. Click the Reports button on the navigation bar. 2. Use the hierarchy listing on the left to expand the view. 3.
• Codec Reports show transmit, receive and resolution reports on communications systems. • Conference Audit Reports contain conference-specific statistics. • User Reports show user-specific usage details. • Billing Reports show the estimated cost of calls over a specified date range by device or by location. • Diagnostic Reports represent diagnostic information related to audio and video jitter and packet loss by location or device.
Using Avaya Video Conferencing Manager Administrator Avaya Video Conferencing Manager Administrator is a web-based tool that you can use to view the status of services and modify the following configuration settings for Avaya Video Conferencing Manager: • application (such as location, system logs, device polling frequency, and the time-out interval for automatic logout) • alarms • database management • billing information • conferences • email • OpenLDAP • SNMP trap forwarding • Microsoft
• System Logs: Avaya recommends that you change the log setting only when directed by Avaya to troubleshoot an issue with Avaya Video Conferencing Manager. The default setting is ERROR. Changing this setting to DEBUG or WARNING may produce large log files. • Monitoring: Device polling frequency (in minutes) sets the time interval after which Avaya Video Conferencing Manager polls the status of managed devices. The default is 5 minutes.
Restoring the Avaya Video Conferencing Manager Database from a Backup Once you have created a copy of your database, you can recover or restore the files if needed in the event of an equipment failure. 1. Click Browse and locate the proper .BAK file. 2. Click Restore Database. Caution: This process cannot be undone. Billing Information Avaya Video Conferencing Manager uses billing information to estimate the cost of calls placed with your audio and video communications devices.
• Call Statistics Monitoring Interval: Enter the time interval after which call statistics are polled for calls placed with Avaya Video Conferencing Manager. Note: Call statistics monitoring is set to 3 minutes by default. This setting may cause high CPU usage for the LSCService.exe process during calls and slow response to tasks performed with the user interface.
Video Settings Enter the threshold figures for: • Transmit Jitter: Enter a value between 1 and 1000. The default is 100. • Receiver Jitter: Enter a value between 1 and 1000. The default is 100. • Transmit Packet Loss %: Enter a value between 1 and 100. The default is 5. • Receive Packet Loss %: Enter a value between 1 and 100. The default is 5. • Transmit F/S: Enter a value between 1 and 60. The default is 7. • Receiver F/S: Enter a value between 1 and 60. The default is 7.
Port Status lists the status of ports required by Avaya Video Conferencing Manager. When the Avaya Video Conferencing Manager service is stopped, none of these ports should be in use. If one or more are in use, some other application or service is using those ports and may interfere with the proper execution of Avaya Video Conferencing Manager.
6. Click Save to save your changes. Note: To remove a trap destination, click its IP address in the list box and click Delete. Microsoft Exchange Settings If you chose to integrate Avaya Video Conferencing Manager with Microsoft Exchange Server during the Avaya Video Conferencing Manager installation process, you can modify the configuration settings for the integration using Avaya Video Conferencing Manager Administrator.
• Maximum number of days for schedules to be allowed within: Set the scope of valid conference scheduling in the box. • Microsoft Exchange Server IP: Enter the IP address of the Microsoft Exchange Sever. • Microsoft Exchange Server Domain: Enter the Microsoft Exchange server domain. • Microsoft Exchange User: User name of the Avaya Video Conferencing Manager account in Microsoft Exchange.
Exporting Page Views At the top of most pages in Avaya Video Conferencing Manager an option to export the current view as a PDF document appears. This feature is useful for troubleshooting purposes when you are working with Avaya Technical Services representatives.
• Data folders from a previous, removed PostgreSQL installation exist and the Avaya Video Conferencing Manager installation program cannot delete them. Delete the folders and then run the Avaya Video Conferencing Manager installation program. • During a new installation of Avaya Video Conferencing Manager, an installation of OpenLDAP or PostgreSQL already exists. Remove the existing OpenLDAP or PostgreSQL installation and then run the Avaya Video Conferencing Manager installation program.
Web Sites in IIS Function Improperly After an Upgrade During an upgrade, the Avaya Video Conferencing Manager installation program changes the ASP.NET version of all web sites installed in IIS to v2.0. Other web sites installed in IIS that are not running in their own application pools and that rely on an earlier version of Microsoft .NET Framework may function improperly after the upgrade. To work around this issue, do the following after performing the upgrade: 1. Open the IIS Manager.
- Click LDAP Settings. Ensure that the IP address that you selected for the OpenLDAP server in step 4 on page 23 is correct. If it is not, click Configure. The LDAP Settings dialog box appears. Select the correct IP address and click Save. If you are still unable to connect to the web server, you may need to reassign the server certificate to correct the problem. Complete the following steps: 1. Access Start->Run, enter inetmgr, and press Enter. 2. Expand the tree to expose the Default Web Site node. 3.
5. On the Start menu, click Run. The Run dialog box appears. 6. Enter inetmgr in the Open list box. 7. Expand the tree to expose the Default Web Site node. 8. Remove AvayaAuraVideoSystemManager. 9. In the Default Web Site directory, remove AvayaAura.aspx 10. Right click Default Web Site node, and then click Properties. 11. Click the Documents tab and remove AvayaAura.aspx from the list of files. 12. Restart your computer to ensure that the changes take effect.
Appendix A: User Role Access The following table describes the scope of access to functionality in Avaya Video Conferencing Manager for each user role.
Page Name Functionality Administrator Engineer Operator Devices (continued) Set MCU Affinity Yes Yes No Update license Yes Yes No Register email address to device Yes Yes No Register gatekeeper Yes Yes No Send a message to a device Yes Yes Yes Discover devices Yes Yes No Add a new device Yes Yes No Refresh all Yes Yes No Update password Yes Yes No Change password Yes Yes No View alarms Yes Yes No Refresh device Yes Yes No Schedule upgrade Yes Yes No
Page Name Functionality Administrator Engineer Operator Devices (continued) Update device IP in list entry Yes No No Modify device details Yes No No Manage devices Yes No No Create templates Yes No No View events Yes Yes Yes Schedule calls Yes Yes Yes Add or remove participants to a call Yes Yes Yes Drop a call Yes Yes Yes Redial completed calls Yes Yes Yes View call details Yes Yes Yes Show call statistics Yes Yes Yes View system calendar Yes Yes Yes Sc
Page Name Functionality Administrator Engineer Operator Events (continued) Schedule template events Yes No No Delete scheduled template events Yes No No Schedule device offline Yes No No Reports Generate all reports Yes Yes Yes Templates Create templates Yes No No Back up or restore a device Yes No No View logs Yes No No View list Yes Yes Yes Upload Yes Yes No Delete Yes Yes No Password Specify default passwords for devices and protocols Yes No No User Ma
Page Name Functionality Administrator Engineer Operator Help Access help for using Avaya Video Conferencing Manager Yes Yes Yes Avaya Video Conferencing Manager Administrator Access Avaya Video Conferencing Manager Administrator Yes No No Not applicable. Feature available when Microsoft Exchange integration is enabled.
Appendix B: Alarms by Category authentication Alarm ID Description Default Status ID_LOGIN_FAIL Invalid username or password. OFF Alarm ID Description Default Status ID_CALL_STATS_HIGH_JITTER Audio or video jitter has exceeded the configured threshold value. ON ID_CALL_STATS_POOR_FPS Frames per second has fallen below the configured threshold value. ON ID_CUMULATIVE_PKT_LOSS_AUDIO Cumulative packet loss exceeded the configured threshold value.
conference Alarm ID Description Default Status ID_ABNORMAL_CALL_TERMINATION Abnormal termination of the conference. ON ID_CALL_PENDING_TERMINATION Conference $1$ is pending termination. ON ID_CONF_CANNOT_EXTEND_NEXT_CALL_READY The conference cannot be extended since the calling station has already been scheduled to participate in another conference during the requested time period. ON ID_CONF_DELETED_FROM_CONF_TBL Deleted conference $1$ from the conference table.
conference (Continued) Alarm ID Description Default Status ID_CONF_EXTEND_FAILED_INVALID_DEV_STATUS Failed to extend conference $1$. Invalid device status. ON ID_CONF_EXTENED Extended conference $1$. ON ID_CONF_EXTENSION_FAILURE_1 Failed to extend the conference $1$. ON ID_CONF_EXTENSION_NOT_PREFERRED The user decided not to extend the conference. ON ID_CONF_EXTENSION_STOPPED_BY_USER The user decided not to extend the conference $1$.
conference (Continued) Alarm ID Description Default Status ID_CONF_LAUNCH_FAILED_NO_DEV Failed to launch conference $1$. No managed devices found. ON ID_CONF_SAVE_FAIL_DB_ERROR Failed to save conference $1$. A database error occurred. ON ID_CONF_SAVE_FAIL_SW_UPGRADE_CONFLICT Failed to save conference $1$. ON ID_CONF_SAVE_FAILED Failed to save conference $1$. No managed devices were found. ON ID_CONF_SAVE_FAILED_DUE_TO_CONFIG_SCHEDULES Failed to save conference $1$.
conference (Continued) Alarm ID Description Default Status ID_DEL_CONF_FAILED_CONF_LAUNCHED Failed to delete the conference $1$ from the conference table. The conference has already been dialed or terminated. ON ID_DEL_CONF_FAILED_DB_ERROR Failed to delete conference $1$ from the conference table; a database error occurred. ON ID_DEL_CONF_FAILED_DB_ERROR_1 Failed to delete the conference from the conference table; a database error occurred.
conference (Continued) Alarm ID Description Default Status ID_FAILED_CONF_TERMINATION Failed to terminate the conference. ON ID_FAILED_TO_FIND_CALL_STATION Failed to launch conference $1$. Unable to find a calling station to dial the conference. ON ID_FAILED_UPDATE_CONF_STATUS_TO_TERMINATED Failed to update the status of the conference $1$ to terminated. ON ID_IMPROPER_CONF_TERMINATION Improper termination: $1$. ON ID_NO_MANAGED_DEV_SELECTED_FOR_CONF No managed devices are selected.
conference (Continued) Alarm ID Description Default Status ID_UNABLE_TO_MAKE_CALLS_NO_SERVICE_PREFIX Unable to make a call to $1$ from $2$. MCU does not have any valid service prefix. ON ID_UNABLE_TO_UPDATE_CONF_TO_INPROGRESS Unable to update the status of the conference $1$. A database error occurred. ON ftp Alarm ID Description Default Status ID_FTP_DEV_DOWNLOAD_FAILED Could not download the files from the device using FTP.
ldap Alarm ID Description Default Status ID_COUNTRY_STATE_INFO_MODIFY_FAILED Failed to modify the country/state information in LDAP ON ID_DEV_ADDED_TO_LDAP The device was added successfully to LDAP. ON ID_DEV_INFO_MODIFIED_IN_LDAP Device information was modified successfully in LDAP. ON ID_FAILED_TO_MODIFY_DEV_INFO_IN_LDAP Failed to modify the device information in LDAP. ON ID_LDAP_ADD_FAIL_DUPLICATE_ENTRY Failed to add the device to LDAP. A duplicate entry exists.
Avaya (Continued) Alarm ID Description Default Status ID_LSC_CALL_CONNEC Call connected ON ID_LSC_CALL_CONNECTED Call connected. ON ID_LSC_CALL_DISCONNEC Call disconnected. ON ID_LSC_CALL_DISCONNECTED Call disconnected. ON ID_LSC_CH_CONN Channel connected. ON ID_LSC_CH_DISONN Channel disconnected. ON ID_LSC_CHANGE_IN_PRI_PORT_STATUS The PRI port status changed. ON ID_LSC_CHANNEL_CONNECTED Channel connected. ON ID_LSC_CHANNEL_DISCONNECTED Channel disconnected.
Avaya (Continued) Alarm ID Description Default Status ID_LSC_INCOMING_CALL Device received a call. ON ID_LSC_ISDN_LINE_DOWN ISDN line down. ON ID_LSC_ISDN_LINE_ERR Error with ISDN line. ON ID_LSC_ISDN_LINE_UP ISDN line up. ON ID_LSC_PEI_BRI_CABLE_IN A BRI cable is plugged in. ON ID_LSC_PEI_BRI_CABLE_OUT A BRI cable is unplugged. ON ID_LSC_PRI_PORT_DOWN PRI port is down. ON ID_LSC_PRIPORT_UP The PRI port is up. ON ID_LSC_SYS_ALARM This alarm is deprecated.
Avaya (Continued) Alarm ID Description Default Status ID_LSC_V35_UP This alarm is deprecated. Setting the status has no effect. OFF Avaya Video Conferencing Manager Alarm ID Description Default Status ID_ADD_USER $1$ $2$ has been added. ON ID_ALARM_EMAIL_INFO This alarm is deprecated. Setting the status has no effect. ON ID_BACKUP_HISTORY_ALARMS_TO_PATH Back up history alarms to $1$. ON ID_CALL_STATS_ALARM A call statistics threshold violation has occurred.
Avaya Video Conferencing Manager (Continued) Alarm ID Description Default Status ID_DEV_INFO_MODIFY_FAILURE_IN_EXCHG Failed to modify the device information in the Microsoft Exchange Server. ON ID_DELETE_USER $1$ $2$ has been deleted. ON ID_DEV_INFO_UPDATED_IN_EXCHG_SRVR Device information updated successfully in the Microsoft Exchange Server. ON ID_DEV_MAC_NULL The MAC address of the device is null. ON ID_DEV_STATUS_INAPPROPRIATE_FOR_DEL Device deletion failed.
Avaya Video Conferencing Manager (Continued) Alarm ID Description Default Status ID_FAILED_DEV_REBOOT Failed to reboot the device. ON ID_FAILED_DEVICE_DEL_FROM_ADDR_BOOK Failed to delete device from address book. ON ID_FAILED_TO_BACKUP_HISTORY Failed to backup history alarms. ON ID_FAILED_TO_EXPORT_HISTORY Failed to export history alarms. ON ID_FILE_NOT_FOUND File not found. ON ID_FILE_UPLOAD_FAILED Failed to upload files. Filename cannot be empty.
Avaya Video Conferencing Manager (Continued) Alarm ID Description Default Status ID_LSC_SERVER_SHUTDOWN Attempting to shut down the Avaya Video Conferencing Manager server at $1$. ON ID_LSC_SERVER_SHUTDOWN_FAILED Avaya Video Conferencing Manager server shutdown failed at $1$. ON ID_LSC_SERVER_STARTUP Avaya Video Conferencing Manager server started at $1$ by $2$. ON ID_MIB_LOAD_FAILED Failed to load the MIB files. Check for MIB files.
Avaya Video Conferencing Manager (Continued) Alarm ID Description Default Status ID_MODIFY_CONF_NO_MATCH Failed to modify conference $1$. No matching conference found. ON ID_MODIFY_CONF_NO_MATCH_1 Failed to modify conference. No matching conference found. ON ID_MODIFY_USER $1$ $2$ has been modified. ON ID_NO_FILES_DOWNLOAD No files to download. ON ID_NO_MORE_LICENSES No licenses left. ON ID_PARAM_KEY_UNAVAILABLE This alarm is deprecated. Setting the status has no effect.
Avaya Video Conferencing Manager (Continued) Alarm ID Description Default Status ID_UNKNOWN_ERROR An unknown error has occurred. ON ID_UPDATE_PWD_ON_DEV_FAILED Failed to update the password on the device. ON ID_USER_FAILED_TO_LOGIN User $1$ failed to log in. ON ID_USER_NOT_REGISTERED You are not registered with Avaya Video Conferencing Manager. ON ID_USR_PWD_PAIR_FAIL Username/password pair failed on the device.
Polycom (Continued) Alarm ID Description Default Status ID_POLYCOM_GDS_DOWN This alarm is deprecated. Setting the status has no effect. ON ID_POLYCOM_GDS_OFF This alarm is deprecated. Setting the status has no effect. ON ID_POLYCOM_GDS_UP This alarm is deprecated. Setting the status has no effect. ON ID_POLYCOM_INTF_TYPE_CHANGE The interface type changed. ON ID_POLYCOM_IP_ADDR_CHANGE The IP address changed. ON ID_POLYCOM_JITTER_EXCESSIVE Jitter is excessive.
Polycom (Continued) Alarm ID Description Default Status ID_POLYCOM_MAIN_CAM_UP Main camera is running. ON ID_POLYCOM_MIC_CHANGE Microphone change. ON ID_POLYCOM_PERCENT_PACK_LOSS_EXSS Percentage of packet loss is excessive. ON ID_POLYCOM_TIME_SERVER_DOWN Time server is not running. ON ID_POLYCOM_TIME_SERVER_OFF Time server is off. ON ID_POLYCOM_TIME_SERVER_ON Time server is on. ON ID_POLYCOM_TIME_SERVER_UP Time server is running. ON ID_POLYCOM_USER_ASSIST This alarm is deprecated.
software upgrade (Continued) Alarm ID Description Default Status ID_SW_UPGRADE_FAILED_LOGIN The software upgrade failed because of a login failure. ON ID_SW_UPGRADE_FAILED_PACKAGE_NOT_FOUND The software upgrade failed because the file $1$ does not exist. ON ID_SW_UPGRADE_FINISHED The software upgrade has finished. The device will reboot. ON ID_SW_UPGRADE_START The software upgrade has started.
ssh Alarm ID Description Default Status ID_SSH_SESSION_FAILED Failed to open an SSH session on the device. ON Tandberg Alarm ID Description Default Status ID_TANDBERG_AUTH_FAIL Authentication failure. ON ID_TANDBERG_CALL_MODE_CHANGE Call mode change. ON ID_TANDBERG_COLD_START This alarm is deprecated. Setting the status has no effect. ON ID_TANDBERG_DISCONNECT This alarm is deprecated. Setting the status has no effect. ON ID_TANDBERG_FINISHED_UPGRADE Upgrade finished.
telnet Alarm ID Description Default Status ID_TELNET_FAILED Telnet authentication failed for the specified password. ON ID_TELNET_SESSION_FAILED Could not open a Telnet session on the device. ON ID_TELNET_SESSION_LOST Cannot execute the command on the device since the Telnet session to the requested device is lost.
