3com IP Conferencing Module Administration Guide

IP Conferencing Module Administration Guide

3Com® Convergence Applications Suite VCX System Release 7.2

http://www.3com.com/

Part Number 900-0409-01 Published October 2006

3Com Corporation 350 Campus Drive Marlborough, MA 01752-3064

Copyright © 2006, 3Com Corporation. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without written permission from 3Com Corporation.

3Com Corporation reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of 3Com Corporation to provide notification of such revision or change.

3Com Corporation provides this documentation without warranty of any kind, either implied or expressed, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. 3Com may make improvements or changes in the product(s) and/or the program(s) described in this documentation at any time.

UNITED STATES GOVERNMENT LEGENDS:

If you are a United States government agency, then this documentation and the software described herein are provided to you subject to the following:

United States Government Legend: All technical data and computer software is commercial in nature and developed solely at private expense. Software is delivered as Commercial Computer Software as defined in DFARS 252.227-7014 (June 1995) or as a commercial item as defined in FAR such is provided with only such rights as are provided in 3Com’s standard commercial license for the Software. Technical data is provided with limited rights only as provided in DFAR 252.227-7015 (Nov

1995) or FAR portion of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunction with guide.

Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or may not be registered in other countries.

3Com and the 3Com logo are registered trademarks of 3Com Corporation. VCX is a trademark of 3Com Corporation.

Other brand and product names may be registered trademarks or trademarks of their respective holders.

52.227-14 (June 1987), whichever is applicable. You agree not to remove or deface any

2.101(a) and as

CONTENTS

ABOUT THIS GUIDE

Conventions 7

Notices 7

Text 8 Related Documentation 8 Comments 9

1 3COM IP CONFERENCING MODULE OVERVIEW

Overview 11 Conference Types 12 Conference Feature Matrix 13 Conference Names (IDs) 14 Access Controls 15

Public Conferences 15

Restricted Conferences 15

Scheduled and Meet Me 15 Instant and Emergency 15

Licensing 16

Maximum Server Capacity 16

G.729 Codec Assignment 16

Media Type 16 Port Type Assignment 17

Total Number of Ports Available 18

Port Usage per Conference 18

Overbook Ports for Scheduled Conferences 18 Distributed Conferencing 18

Conference Distribution Mechanism 19

Conference Server Roles (Routing and Hosting) 19

Database Redundancy 19

High Availability 20

Hostname Usage 20

System Upgrades 20 Configuration Options 20

Configuration Option 1: Single Server 20 Configuration Option 2: Dual Server 20 Configuration Option 3: Four to Twelve Servers 21 Distributed Conferencing example (multiple servers) 22

Distributed Presence 22

Mapping Table for Presence and Conference Provisioning 23

Global Directory of VCX Users 23 Audio CODECs 24 Video CODECs 24

2 ADMINISTRATIVE SETUP

Logging in through the Web Console 25

Regular User Privileges 25

Administrative Privileges 26

Logging in as an Administrator 26

Logging in as a Regular User 27

Logging out 28 Managing User Accounts 28

Assigning Administrative Privileges 28

Changing the Super User’s Password 29

Adding an E-mail Address 29

Adding Another User’s E-mail Address 29

3 SYSTEM CONFIGURATION

Configuring the Global Parameters 31 Configuring the Conference Server Parameters 32 Configuring the Conferencing Parameters 34

Configuring the Digit Map for DTMF Dialout 37

Programming the Digit Map 38

Configuring the User Database Import Parameters 39

Multi-office Configuration 40 Managing the Local Domain Configuration 40

4 PRESENCE SERVER

What is the Presence Server? 43 Configuring the Presence Server 44 Configuring Distributed Presence 46

Conference Provisioning 47 Global Directory of Users 47 Adding Distributed Presence/Conference Provisioning Entries 48 Editing Distributed Presence/Conference Provisioning Entries 49

Starting and Stopping the Presence Server 50

5 MAINTENANCE AND TROUBLESHOOTING

Power Cycling 53 Managing the Status of Key Processes 53 Managing the Status of the Conference Servers 55 Database Backup and Restore 57

Backing up the Database 57 Restoring the Database 58 Restoring the Database on the Master (primary) Server 59

Manual Database Switchover 60

Manual Switchover to Master Database 61 Manual Switchover to Slave Database 61

Managing the Error and Debug Log Files 61

Log File Size Limits 62

Maximum Log File Size 62

Maximum Disk Space Usage 62 Viewing the Log Files 63 Changing the Log File Threshold for an Application 63

Changing or upgrading the License Key 65

6 OBTAINING SUPPORT FOR YOUR PRODUCT

Register Your Product 67 Purchase Value-Added Services 67 Troubleshoot Online 68 Access Software Downloads 68 Telephone Technical Support and Repair 68 Contact Us 69

7 ACKNOWLEDGEMENT OF THIRD PARTY SOFTWARE

Supplementary Copyright Information 71

Net-SNMP License 71 Xerces License 72

GLOSSARY

INDEX

ABOUT THIS GUIDE

This guide describes how to set up, maintain, and provision the 3Com® IP Conferencing Module of the 3Com Convergence Applications Suite.

This guide is for network operations, internal support, and Voice over Internet Protocol (VoIP) systems planning personnel. Users of this document should have a thorough knowledge of telecommunications, IP telephony technology, and networks.

Release Notes are issued with some products. If the information in the release notes differs from the information in this guide, follow the instructions in the release notes.

Conventions This section describes notice, text, and figure conventions.

Notices Tab le 1 lists notice icons.

Ta bl e 1 Notice Icon Descriptions

Icon Notice Type Description

Information note Information that describes important features or

Caution Information that alerts you to potential loss of

Warning

instructions

data or potential damage to an application, system, or device

Information that alerts you to potential personal injury

8 ABOUT THIS GUIDE

Te xt Ta bl e 2 lists text conventions.

Ta bl e 2 Text Convention Descriptions

Convention Description

Screen displays This typeface represents information as it appears on the

screen.

Commands The word “command” means that you must enter the

command exactly as shown and then press Return or Enter. Commands appear in bold. Example:

To remove the IP address, enter the following command:

SETDefault !0 -IP NETaddr = 0.0.0.0

Words in italics Italics are used to:

n Emphasize a point.

n Denote a new term at the place where it is defined in

the text.

n Identify menu names, menu commands, and software

button names. Examples:

From the Help menu, select Contents.

Click OK.

Comments 9

The following documents are a part of the IP Messaging Module:

n IP Messaging Module Product Overview

n IP Messaging Module Quick Reference Guide - 3Com Native Interface

n IP Messaging Module User Guide - 3Com Native Interface

n IP Messaging Module Quick Reference Guide - Traditional Interface

n IP Messaging Module User Guide - Traditional Interface

n IP Messaging Module Operations and System Administration Guide

n E-Mail Reader Application Quick Start Guide

The following documents are a part of the IP Conferencing Module:

n IP Conferencing Module Installation Guide

n IP Conferencing Module User Guide

n IP Conferencing Module Administration Guide

n Convergence Center Client User and Administration Guide

The following documents provide information on products that support this release:

n Enterprise Management Suite User Guide

n Enterprise Management Suite Getting Started Guide

n V7111 Analog Media Gateway Fast Track Installation Guide

n V7111 Analog Media Gateway User Guide

n V6000 Analog Media Gateway Fast Track Installation Guide

n V6000 Analog Media Gateway User Guide

n V7122 Digital Media Gateway Fast Track Installation Guide

n V6100 Digital Media Gateway Fast Track Installation Guide

n V7122 and V6100 Digital Media Gateway User Guide

Comments Send e-mail comments about this guide or about any Voice product

documentation to:

VOICE_Techcomm_comments@3com.com

Include the following information with your comments:

n Document title

10 ABOUT THIS GUIDE

n Document part number (found on the front page)

n Page number

n Your name and organization (optional)

Example:

IP Conferencing Module User Guide System Release 7.1

Part Number 900-0350-01 Page 25

Please address all questions regarding 3Com software to your authorized 3Com representative.

3COM IP CONFERENCING

MODULE OVERVIEW

This chapter provides an overview of the principal features of the 3Com IP Conferencing Module conferences or presence services.

This chapter includes the following topics:

n Overview

n Conference Types

n Conference Feature Matrix

n Conference Names (IDs)

n Access Controls

n Licensing

n Port Ty pe Assignment

n Distributed Conferencing

n Distributed Presence

™

. Study it before attempting to configure

n Audio CODECs

n Video CODECs

Overview The 3Com IP Conferencing Module is a multi-party conference

management program that supports a variety of communication modes and conference types. Users can participate in conferences that include voice, video, desktop sharing services, and instant messaging.

The 3Com IP Conferencing Module supports a variety of communication modes:

n Voice for Session Initiation Protocol (SIP) devices and analog phones

n Video for the 3Com Convergence Center Client

12 CHAPTER 1: 3COM IP CONFERENCING MODULE OVERVIEW

n Desktop sharing for the 3Com Convergence Center Client

n Instant messaging for the 3Com Convergence Center Client.

The 3Com Convergence Center Client includes the Presence Server, which collects and distributes the online status information of users.

Conference Types The following conference types are supported:

Scheduled — When a user sets up a scheduled conference, the required system resources are reserved for a defined period of time. After the conference ends, the resources become available again. User access can be restricted (password-protected) or public (accessible to anyone who knows the conference name). Scheduled conferences are configured on the web console.

Meet Me — Meet Me conferences are “always on,” without a scheduled start and end time. They are intended for informal meetings organized by regular users, and can be started only if sufficient resources are available on the system. User access can be restricted or public. Meet Me conferences are configured on the web console.

Ad Hoc — An Ad Hoc conference starts when the first user joins it. No configuration is required on the 3Com IP Conferencing Module. To activate the conference, the user simply dials a special prefix that has been set up by the administrator. Other users can join the conference by dialing the same prefix; no password is required. Ad Hoc conferences offer the same features as Meet-Me conferences for a maximum of six participants.

Instant — An instant conference starts as soon as the first participant calls it and dials the Conference Start PIN. The system then calls all other conference participants, who can join immediately or call the conference at a later time. If calling at a later time, users will be required to enter a password if the conference is restricted. Instant conferences can be configured by regular users on the web console.

Emergency — Emergency conferences are the same as instant conferences with the following exceptions:

n The system can be programmed to alert users that an emergency

conference is in progress by continuously ringing an alarm, flashing light, or other notification device.

Conference Feature Matrix 13

n Individual user extensions can be programmed with a line monitoring

feature that causes a lamp to flash whenever an emergency conference is in progress. The user connects to the conference by pressing the button located beside the lamp.

n Emergency conferences can be configured only by administrators.

Conference Feature Matrix

Ta bl e 3 lists the features that are available with each type of

conference—scheduled, Meet Me, Ad Hoc, Instant, and Emergency. For detailed feature descriptions, refer to the conference programming instructions in the IP Conferencing Module User Guide.

Ta bl e 3 Conference feature matrix

Conference Type

Feature

Set up on web console Yes Yes Yes Yes

Set up by dialing a special prefix Yes

Defined start and end time Yes

Recurrence option Yes

Number of ports allocated for conference users (default)

Maximum number of participants per conference (global limit)

Maximum duration of conference defined by conference creator/moderator

Supported media types (subject to licensing):

Audio Yes Yes Yes Yes Yes

Instant Messaging Yes Yes Yes Yes Yes

Video Yes Yes Yes

Desktop Sharing Yes Yes Yes

Conference types:

Public - No authentication. Yes Yes

Restricted - Password authentication. Yes Yes Yes Yes

Web console controls available to moderators:

Participant access control lock Yes Yes Yes Yes

Extend conference Yes

Scheduled Meet-me Ad Hoc Instant Emergency

25 + 5

floater ports

Set by

administrator

8 hrs

shared between Meet-me/Ad hoc/Instant/Emergency

Set by

administrator

Always Public

3 to 30

Set by

administrator

Yes Yes

100

14 CHAPTER 1: 3COM IP CONFERENCING MODULE OVERVIEW

Table 3 Conference feature matrix (continued)

Audio control: Open mode, Moderator Lecture mode, Isolate Participant mode

Video control: Open mode, Moderator Lecture mode, Isolate Participant mode

Disconnect participants Yes Yes Yes Yes

Touch tone controls available to moderators:

Terminate conference Yes Yes Yes Yes

Dial out and add participants to conference Yes Yes Yes Yes

Participant access control lock Yes Yes Yes Yes

Extend conference Yes

Mute and un-mute all participant voices Yes Yes Yes Yes

Mute and un-mute own voice Yes Yes Yes Yes

Hear a private roll call of all participants Yes Yes Yes Yes

Touch tone controls available to all participants:

Mute and un-mute own voice Yes Yes Yes Yes

Hear a private roll call of all participants Yes Yes Yes Yes

Automated conference announcements:

First in conference Yes Yes Yes Yes

Next in conference Yes Yes Yes Yes

Leave conference Yes Yes Yes Yes

End of conference first warning Yes

End of conference final warning Yes

Yes Yes Yes Yes

Yes Yes

Conference Names (IDs)

Every conference is identified by a unique SIP Uniform Resource Identifier (SIP URI) that is assigned when the conference is created. The SIP URI has a name portion and a server host portion. For example:

sip:7000@10.1.0.238

name server host

Only the name portion is required to connect the conference. Internal callers (callers within the enterprise) can simply dial the name and be connected directly. External callers (callers on the PSTN) must first dial the

Access Controls 15

Conference Attendant and then dial the name when prompted. Optionally, callers can dial the full SIP URI to reach the conference.

Conference names are always numeric (e.g. 7000). When users create a new conference, they can select a name from a block of numbers made available by the administrator (for example, any number between 7200 and 7299), or they can leave the conference name field blank, in which case the system will automatically assign a name from the available block of numbers.

In a multi-server configuration, the servers share a common range of numeric conference names (IDs). It is not possible to assign separate ranges to the individual servers in the pool.

Access Controls Conferences can be created with or without access controls.

Public Conferences Public conferences are unrestricted and open to anyone without the need

to authenticate or enter a passcode. The caller is only required to know the numeric conference ID.

Restricted

Conferences

Users access a restricted conference by authenticating themselves to the system. The authentication method varies depending on the conference type.

Scheduled and Meet Me

To access a restricted Scheduled or Meet Me conference, users are required to dial the numeric conference name and then enter a passcode to authenticate themselves and be added to the Participant Control List for the conference.

Instant and Emergency

When a restricted Instant or Emergency starts, the system calls a list of users and invites them to participate. Users who answer this call and press the # key are automatically authenticated and connected to the conference. Users who call the conference after it has started will be prompted to authenticate themselves by entering the Join PIN.

Users can call a conference after it has started by dialing the numeric conference name, or, if their extension has been programmed to support

16 CHAPTER 1: 3COM IP CONFERENCING MODULE OVERVIEW

Emergency Conference Notification, by pressing the appropriate line key on their telephone.

Licensing The 3Com IP Conferencing Module is activated by a set of license keys

that you must acquire from 3Com. There is a separate license key for each application:

n conference server

n conference attendant server

n presence server

The following feature levels are also controlled by the license keys:

Maximum Server

Capacity

G.729 Codec

Assignment

Media Type Defines which media types are supported by the conferences hosted on

For the conference server, this feature controls how many users can participate in conferences simultaneously. For example, if you purchase a license for 100 users, then a maximum of 100 ports are available on the server at any one time for conference participants.

For the conference attendant, this feature controls how many users can connect to the attendant IVR simultaneously.

For the conference server, this feature controls the number of ports that are available for G.729 connections. For example, if you assign 30 ports from a 100-port license to G.729, then these ports can use G.729 or any other supported codec (G.711, etc). The remaining ports cannot use G.729.

For the conference attendant, this feature controls how many users can connect to the attendant IVR simultaneously with G.729.

The number of ports you make available to G.729 depends on the processing capacity of your server. If you have a high-capacity server, you can allocate more ports to G.729.

the server. You can purchase support for audio, video and desktop sharing. This feature applies only to the conference server.

All licensing parameters are defined on a per-server basis.

Port Type Assignment 17

Port Type Assignment

The 3Com IP Conferencing Module connects to the network via ports. When you configure the ports in your system, you can subdivide them by type in order to optimize resource usage. For example, if your users hold a large number of impromptu meetings, then you should allocate most of your available ports to Meet-me and Ad Hoc conferences.

Available port types are illustrated in Figure 1.

Figure 1 Distribution of Port Types

Announcement

Floater

Conference

ports

1 Announcement ports — Used to deliver messages to users who are too

early or late to connect to a conference, or who attempt to join a conference that is locked or full. Announcement ports are available to deliver messages for all conference types (scheduled, meet-me, ad hoc, instant and emergency). By default, five ports are designated as announcement ports.

Scheduled

Non-Scheduled

2 Floater ports — Enables users to join conferences that are full, and

allows conferences to start when the system is near its maximum capacity. In the first example, if a conference has reached its provisioned limit of ten users and another wants to join, the extra user can be accommodated with a floater port. In the second example, if there are three conference servers, each of which is hosting a conference, and a user attempts to start another conference, the extra conference can be accommodated with floater ports. Depending on the total number of ports available, the system may support fewer users than actually provisioned for the extra conference.

3 Scheduled ports — Ports reserved for scheduled conference users. By

default, there are 25 scheduled ports.

18 CHAPTER 1: 3COM IP CONFERENCING MODULE OVERVIEW

4 Non-Scheduled ports — Ports reserved for Meet-Me, Ad Hoc, Instant

and Emergency conference users. By default, 25 ports are reserved for these types of conferences.

Total Number of Ports

Available

Port Usage per

Conference

Overbook Ports for

Scheduled

Conferences

The total number ports that you configure should equal the maximum server capacity (total number of licensed users). This can be expressed as:

Announcement ports Floater ports Scheduled ports Non-Scheduled ports maximum server capacity

When a conference starts, three ports are automatically allocated to it. Additional ports are allocated as more users join the conference. If any users fail to join, their ports remain available for use. For example, if you configure a scheduled conference for 10 users but only six participate, four ports will remain available for use by other scheduled conferences.

Overbooking allows you to reserve more ports for conferences than are actually available. Suppose you have 100 scheduled conference ports and that these are entirely booked for meetings. If the “overbook” parameter is set to 25, you can still schedule conferences for another 25 users.

Overbooking assumes that all users who are scheduled to attend often do not attend, which usually leaves unused ports available. In the rare case that all ports are scheduled and all people attend the meeting—including those who are overbooked—the last people to call into any meeting would not be able to get through.

Distributed Conferencing

In its standard configuration, the 3Com IP Conferencing Module concentrates all applications and processes on a single server. This limits the system to supporting a maximum of 300 conference participants at any one time.

In a distributed configuration, the applications and processes are assigned to multiple servers. A fully equipped system with twelve servers in a pool (ten for conferencing; two for provisioning, presence and database redundancy) can support up to 3,000 concurrent conference participants. Smaller systems with fewer servers can also be implemented.

Distributed Conferencing 19

Users employ a single web console to set up and manage their conferences, regardless of how many servers are installed.

To achieve maximum system capacity, the IBM xSeries 346 platform is required. Capacity is reduced with the IBM xSeries 306 platform.

Conference

Distribution

Mechanism

Conference Server

Roles (Routing and

Hosting)

When a new conference starts, the system uses the “best fit” distribution mechanism to assign it to the server in the pool that has the least available capacity (assuming that G.711 will be used for all connections, and that the conference will host the maximum possible number of users). If a server cannot be found with sufficient capacity, the conference is refused.

Conferences in a distributed system are handled by a pool of up to ten servers. The individual servers in the pool can host conferences, route callers to conferences, or perform both functions. A server in the routing role completes the following steps when a caller dials a conference:

n Receives the initial SIP INVITE message from the caller to the

conference.

n Uses the “best fit” distribution method to determine which server

should host the conference, or discovers which server is already hosting the conference.

n Redirects the caller to the conference.

Routing can be performed by any conference server in the pool. Simply configure the VCX dial plan so that calls are forwarded to the appropriate destination. If you have only one conference server (an “all-in-one” implementation), then only one route is required. If you have two or more conference servers, then at least two routes are required to provide redundancy. You can optimize system efficiency by assigning the routing role to all servers in the pool, or by restricting the number of ports available for conferencing on the “routing” conference servers.

Database

Redundancy

Database redundancy is provided to ensure that the system remains available in the event that a server fails. A single database pair (master and slave) is supported. The slave maintains a copy of the master using MySQL database replication. In the event that the slave cannot communicate with the master for ten minutes, switchover occurs. Manual switchover is also possible. Manual switchover is required whenever one of the application servers attempts to connect to the

20 CHAPTER 1: 3COM IP CONFERENCING MODULE OVERVIEW

wrong database server. (Note that this set-up only provides redundancy for server failure, not network failure.)

High Availability High availability is not provided as part of the solution. Each conference

runs on a single server, and if that server fails, then the conference participants are required to re-dial the conference and connect to a different server through the distribution mechanism described above.

Hostname Usage The servers in a distributed conferencing system will have distinct host

names. However, the domain name portion of conference addresses (@domain) will be the same for all conferences.

System Upgrades Following the initial implementation, the system can be upgraded in

order to increase system capacity or provide database redundancy. For example, adding a second server to a single-server implementation will provide database redundancy.

Upgrades can be performed at any time on fully operational systems. There is no need to disable any applications that are currently running when you add a new server.

Configuration

Options

Three basic configurations are possible. The type you select depends on the number of servers that are available, plus their processing capacity.

Configuration Option 1: Single Server

If you only have one server, then all components must be installed on it. Distributed conferencing is not a feature of this “all-in-one” solution.

Components installed on single server:

n conference server/conference attendant server

n presence server (if purchased)

n VCX user database

n conferencing and presence database

n web console server.

Configuration Option 2: Dual Server

If you have two servers, then both can host conferences. Implement database redundancy by installing the master database on one server and

Distributed Conferencing 21

the slave database on the other. Implement routing redundancy by configuring the SIP server to forward SIP INVITEs to both servers.

Components installed on the primary server:

n conference server/conference attendant server

n presence server (if purchased)

n VCX user database

n conferencing and presence database (initial master)

n web console server.

Components installed on second server:

n conference server/conference attendant server

n conferencing and presence database (initial slave).

Configuration Option 3: Four to Twelve Servers

If you have between four and twelve servers, configure the first server as a “provisioning” server by installing the web console server, presence server, VCX user database, and master database on it. Configure the second server with the slave database and, optionally, the conference server. Configure all other servers in the pool with the conference server. To ensure routing redundancy, configure the SIP server to forward SIP INVITEs to at least two servers in the pool.

Components installed on primary server:

n presence server (if purchased)

n VCX user database

n conferencing and presence database (initial master)

n web console server.

Components installed on secondary server:

n conferencing and presence database (initial slave).

Components installed on all other servers:

n conference server/conference attendant server.

22 CHAPTER 1: 3COM IP CONFERENCING MODULE OVERVIEW

Distributed Conferencing example (multiple servers)

Figure 2 Distributed conferencing example configuration - Seven servers

Conference installation

conferencing conferencing conferencing conferencing

- master db

- user db

- web console

- presence (optional)

Primary

- slave db

- routing

SIP server

IP-PBX

- conferencing

- routing

Secondary

Distributed Presence

User 1

User 2

1 A dial plan is used to redirect the initial call to a routing conference server.

2 The routing conference server uses the “best fit” distribution mechanism

to redirect the call to the conference server with the least available capacity (assuming that G.711 will be used for all connections, and that the conference will host the maximum possible number of users).

3 The user device calls the conference server specified by the routing

conference server and the conference is set up.

By default, presence information is concentrated on a single server—the primary server of the installation. However, you can distribute presence information across the enterprise by adding more installations of the 3Com IP Conferencing Module. Each installation has a single Presence server that is associated with one or more VCX systems.

Distributed Presence 23

For example, if you have two Presence servers and six VCX systems, then you can associate each Presence server with three VCXs. illustrates this example.

Figure 3 Distributed Presence example - six VCXs and two Presence servers

Figure 3

Mapping Table for

Presence and

Conference

Provisioning

Chicago

VCX

systems

IP Conferencing Module installations

Detroit

Installation A

Primary server

includes presence

conferencing

server

New York

Secondary server

conferencing

server

Houston

Primary server

includes presence

conferencing

Dallas

Installation B

Secondary server

server

conferencing

Phoenix

server

The link between Presence servers and VCX systems is made with mapping table entries. In a distributed environment with multiple Presence servers and VCXs, identical mapping table entries must be added to each installation of the 3Com IP Conferencing Module. In a non-distributed environment with one Presence server and one VCX, only one mapping table entry is required, which defaults to the values specified during the initial software installation.

Global Directory of

VCX Users

For each entry on the mapping table, you must specify whether Conference Provisioning is either allowed or denied. Selecting “allowed” enables users on other installations to provision conferences on the 3Com IP Conferencing Module that is associated with the local Presence Server. Selecting “denied” prevents non-local users from provisioning conferences.

For details, see Adding Distributed Presence/Conference Provisioning

Entries.

In addition to adding the mapping table entries, you must also add the Global Directory of VCX users to each installation of the 3Com IP

24 CHAPTER 1: 3COM IP CONFERENCING MODULE OVERVIEW

Conferencing Module. A properly configured Global Directory that includes entries for all regional offices (Chicago, Detroit, New York, Houston, Dallas and Phoenix in the above example) enables users to track the presence status of their buddies located throughout the network. For details, see

Audio CODECs The 3Com IP Conferencing Module supports conference participants using

any combination of the supported CODECs (the audio conferencing

trans-codes as required). Currently, the following CODECs are supported:

n G.711 A-law (pcma)

n G.711 Mu–law (pcmu)

n G.729

n G.721

n DVI ADPCM

n GSM.

Configuring the User Database Import Parameters.

server

Video CODECs The 3Com IP Conferencing Module distributes H.261 and H.263 video

from each conference participant to all other conference participants.

ADMINISTRATIVE SETUP

This chapter describes how to log in to the 3Com IP Conferencing Module and maintain administrative accounts.

This chapter includes the following topics:

n Logging in through the Web Console

n Managing User Accounts

Logging in through the Web Console

Regular User

Privileges

You can log in to the 3Com IP Conferencing Module web console using Microsoft Internet Explorer or Mozilla Firefox. The 3Com IP Conferencing Module can be used by administrators to manage the system and user accounts.

For more information on presence, see Presence Server.

Account information for regular users is imported into the 3Com IP Conferencing Module from the VCX system. If user information (name, SIP address, etc.) for a regular user requires updating, this must be done on the VCX system, not the 3Com IP Conferencing Module.

A regular user has the authority to do the following in the 3Com IP Conferencing Module:

n Manage their Presence Access Control List

n Add their personal e-mail address

n Add Scheduled and Meet-me conferences

n View all Scheduled conferences*

n View their own Meet-me conferences*.

* For which the user is the conference owner or moderator.

+ 57 hidden pages