Installation Planning Guide for Cisco Unified MeetingPlace Release 6.x
Database Planning
Downloads: This chapterpdf (PDF - 931.0KB) The complete bookPDF (PDF - 4.56MB) | Feedback

Database Planning

Table Of Contents

Database Planning

Information Types

Company-Specific Information

System Configuration Information

Telephony Configuration Information

Cisco Unified MeetingPlace Port Access Types

Defining Telephony Access

Creating Port Groups

Configuring Individual Ports

Monitoring Cisco Unified MeetingPlace with SNMP

Server Configuration

Cisco Unified MeetingPlace Port Types

User Information

Creating User Groups

Planning for Groups and Teams

Creating User Profiles

Importing User Profile and Group Information

Importing with Cisco Unified MeetingPlace Directory Services

Importing Files Manually

Required File Format

Database Planning Worksheets

Worksheet 5-1: Usage Parameters

Worksheet 5-2: Scheduling Parameters

Worksheet 5-3: Company Information

Worksheet 5-4: Flex Fields

Worksheet 5-5: Telephony Access

Worksheet 5-6: Ports

Worksheet 5-7: Port Groups

Worksheet 5-8: System Parameters

Worksheet 5-9: Reservationless Meetings Requirements

Worksheet 5-10: Reservationless Meetings Systemwide Parameters

Worksheet 5-11: Network Management Information

Worksheet 5-12: Network Management Communities

Worksheet 5-13: Server Configuration

Worksheet 5-14: NS Site Configuration

Worksheet 5-15: Multiserver Meeting Requirements

Worksheet 5-16: Other Cisco Unified MeetingPlace Servers

Worksheet 5-17: User Groups

Worksheet 5-18: User Profiles


Database Planning


This chapter describes the categories of information you need for configuring the Cisco Unified MeetingPlace Audio Server database, and contains the following sections:

Information Types

Company-Specific Information

System Configuration Information

User Information

Database Planning Worksheets

Information Types

Table 5-1 describes the four types of information in the Cisco Unified MeetingPlace database.

Table 5-1 Database Information Types 

Information Type
Description

Company specific

Tailors Cisco Unified MeetingPlace for your company. It includes general information, administrative information, and information that controls meeting scheduling. See the "Company-Specific Information" section.

System configuration

Identifies the Cisco Unified MeetingPlace hardware and software. It also describes the interface between the system, the phone network, and the LAN. See the "System Configuration Information" section.

User

Identifies who has access to Cisco Unified MeetingPlace functions and which system functions are available to each person. See the "User Information" section.

Meeting settings

Identifies the various meeting categories that have been created. See the "Database Planning Worksheets" section.


Company-Specific Information

Company-specific information includes general information about your company and parameters that tailor the way Cisco Unified MeetingPlace operates. This information limits the total number of user licenses that can be involved in meetings at one time and determines meeting scheduling criteria. It also defines systemwide defaults for managing meetings.

Table 5-2 describes the information you need to decide the default scheduling and usage parameters that Cisco Unified MeetingPlace should use, and to define port availability for meetings.

Table 5-2 Company-Specific Information 

Information
Description

Usage parameters

Usage parameters establish default values for the parameters that control basic Cisco Unified MeetingPlace operations. These parameters govern security, alarm handling, getting assistance, and outdial. The Usage Parameters window includes a default time zone for the location of the system. This time zone is calibrated to the system's internal clock.

Scheduling parameters

Meeting scheduling parameters control the meetings scheduled at your location. The settings determine how many conference ports on your system can be reserved for meetings at one time.

Meeting guard times

The Scheduling Parameters window includes meeting guard times, which ensure that meetings do not overlap each other and that two meetings are not scheduled back to back with the same meeting ID.

Guard times may also determine how early someone can call into a meeting before its scheduled start time, how long a meeting can be extended, and when ports should be released. Back-to-back reservationless meetings are allowed regardless of guard times. The guard time for reservationless meetings is equal to 0 (zero).

Company information

Company information describes your organization, such as the company name and address, and the names and phone numbers of primary contacts for Cisco Unified MeetingPlace service representatives, and of contacts for system help.

Flex fields

System administrators can customize specific meeting fields to your particular business needs. Use flex fields to track company- or site-specific information by profile or meeting.

Flex fields record information to specify the type of field, title associated with the field, import title used for reporting, protection level of the field, whether users must choose field values from a list of possible entries (which you create), and whether a flex field requires a value.


System Configuration Information

System configuration information controls how Cisco Unified MeetingPlace operates at your organization. You provide information describing the telephony and video configuration, and describing the LAN to which Cisco Unified MeetingPlace is connected.

This section contains the following information:

Telephony Configuration Information

Creating Port Groups

Configuring Individual Ports

Monitoring Cisco Unified MeetingPlace with SNMP

Server Configuration

Cisco Unified MeetingPlace Port Types

Telephony Configuration Information

Telephony configuration information includes port access information that determines which services are available to callers.

The information also describes the type of signaling used by each port. Because multiple ports can use the same signaling, the database lets you organize any of the 1,152 Cisco Unified MeetingPlace ports into port groups. Port groups define signaling information for multiple ports simultaneously.

This section describes the information you need to:

Assign an access type to each port.

Decide whether to define port groups.

Cisco Unified MeetingPlace Port Access Types

The Cisco Unified MeetingPlace services available to callers are determined by the port access type that the system assigns to the call. Cisco Unified MeetingPlace includes three port access types, as described in Table 5-3.

Table 5-3 Port Access Types 

Port Access Type
Description

Meeting access

Allows callers to attend meetings.

Profile access

Allows callers to attend meetings, schedule meetings, and listen to recorded meetings and messages, and change information in their user profiles. (For more information, see the "User Information" section.) Callers without user profiles cannot schedule meetings and do not have user profile privileges.

Combined access

Available only to users with user profiles. Combined access allows callers to attend meetings, schedule meetings, listen to recorded meetings and messages, and change information in their user profiles.


When Cisco Unified MeetingPlace receives dialed number information (DID/DNIS), the port access type the system assigns to a call is determined by the access type assigned to the phone number used to reach it.

When Cisco Unified MeetingPlace does not receive dialed number information, the port access type that the system assigns to a call is determined by the access type you assign to the port that is handling the call.

Defining Telephony Access

Table 5-4 describes the telephony access by country.

Table 5-4 Telephony Access 

Country  
Telephony Access

European Union

Cisco Unified MeetingPlace can receive both DDI/DNIS and ANI/CLI (the European equivalent of ANI) when it is connected to the phone network through E1 PRI trunks.

Hong Kong

Cisco Unified MeetingPlace can receive both DNIS and Automatic Number Identification (ANI) when it is connected to the phone number through T1 PRI trunks.

U.S. and Canada

Cisco Unified MeetingPlace can receive dialed number information (DID/DNIS or DDI information) when it is connected to the phone network through T1 trunks using E&M Wink Start signaling. When the system receives dialed number information, you can assign different port access types to blocks of phone numbers and reserve the numbers in each block for certain uses.

Dialed Number Information (DNI) digits can be received with T1 PRI trunks. In addition, T1 PRI can provide Calling Party Number information, which T1 CAS does not usually provide.


For example, you can assign the following:

Meeting access to one block of numbers to reserve those numbers for callers who only want to attend a meeting.

Profile access to a third block for callers with profiles.

Combined access to a fourth block for all callers.

If Cisco Unified MeetingPlace receives dialed number information, you must decide how many numbers to reserve for each use. If the system does not receive dialed number information, the configuration information you provide for each port determines the port access types.

Creating Port Groups

To configure multiple ports at one time, organize ports into port groups. The configuration information you enter for the port group, which includes a port access type, applies by default to all ports assigned to the group in the absence of either individual port configuration information or a DID/DNIS access plan.

Port groups are optional, although a port must belong to a port group to be used for outdial.

Default port groups are assigned as follows:

Port Group 0 for PSTN

Port Group 1 for IP

Port Group 2 for E1

Port Group 3 for T1 PRI

Configuring Individual Ports

Some configuration information for individual ports is included in a port group definition. Unless you want different information for an individual port than for the group, you only provide this information for the group. Individual port information takes precedence over port group information.

Port configuration information includes a port access type. When Cisco Unified MeetingPlace receives dialed number information, the DID/DNIS access plan determines which type is assigned to a call. If, however, the system cannot use the DID/DNIS or DDI information it receives from the network (for example, the network passes incorrect digits to Cisco Unified MeetingPlace), the configuration information you provide for individual ports determines the port access type.

If your system does not receive dialed number information, decide which access types to assign to each port or group of ports that connect Cisco Unified MeetingPlace to the phone network.

Monitoring Cisco Unified MeetingPlace with SNMP

You can monitor Cisco Unified MeetingPlace by using the Cisco Unified MeetingPlace SNMP option. This feature uses the Simple Network Management Protocol (SNMP) Release 1 and supports MIB-II.

If your server has an SNMP management tool, you can configure this feature to give you network status information and management access to Cisco Unified MeetingPlace through your network management system. Trap messages are sent to all configured trap community addresses in the following circumstances:

The system starts up (coldstart trap).

The system generates an alarm (there several different trap types).

The SNMP option consists of two components that you must configure:

Network Management Information, which determines the UDP port number used for SNMP queries and allows SNMP queries to be disabled (for higher security).

Network Management Communities, which determine the IP address(es) where trap messages will be sent and the community names used for queries (like a password).


Caution You must load MIB files into the monitoring system and configure them for the trap messages to display properly. For more information, refer to "Cisco Unified MeetingPlace SNMP" appendix of the Administration Guide for Cisco Unified MeetingPlace Audio Server at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_maintenance_guides_list.html.

Server Configuration

Using Worksheet 5-13: Server Configuration and Worksheet 5-14: NS Site Configuration, you enter address information for the Cisco Unified MeetingPlace server on your LAN. Default information is filled in during installation, but you can make changes based on your worksheet information. The parameters also include the number of conference and access ports on each server at your organization.

Using Worksheet 5-16: Other Cisco Unified MeetingPlace Servers, you enter information about your organization's other Cisco Unified MeetingPlace servers if you conduct multiserver meetings, whether manual or automatic. These other servers may be geographically dispersed in other states or countries. For more information about multiserver meetings, refer to "About Multiserver Meetings" section in the "Setting Up Cisco Unified MeetingPlace Audio Server" chapter of the Administration Guide for Cisco Unified MeetingPlace Audio Server at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_maintenance_guides_list.html.

Cisco Unified MeetingPlace Audio Server is not aware of DNS. You cannot ping hostnames or use DNS hostnames for configuration.

Cisco Unified MeetingPlace Port Types

The ports that connect Cisco Unified MeetingPlace to the phone and video network are classified as access ports and conference ports. All ports are access ports, and a subset of access ports are preconfigured as conference ports. However, there is no difference between an access port and a conference port.

When the system needs ports to set up a conference call or add people to a call in progress, it allocates them from the pool of available conference ports. If your access ports have all been preconfigured as conference ports and the system requires all available ports, it takes them all. Except for the people attending meetings, no callers can reach Cisco Unified MeetingPlace (for example, to schedule a meeting).

The following safeguards ensure that ports are always available for uses other than conference calls, such as scheduling meetings:

Some conference ports are classified as contingency ports. The system keeps these ports in reserve so that people who are participating in a meeting can reach a contact or attendant for assistance. A meeting scheduling parameter determines how many ports in your system are contingency ports.

Some remaining conference ports are classified as floater ports (or floating ports). Floater ports float between meetings, and are used when an additional caller joins a meeting that is already full. A meeting scheduling parameter determines how many ports are floater ports.

Sometimes your access ports are not all preconfigured as conference ports. The number of conference port licenses you acquire, as listed on your order schedule, is the number of conference ports in your system.

Figure 5-1 shows the uses for access ports and conference ports.

Figure 5-1 Access Ports and Conference Ports Uses

1

Access ports reserved to schedule and listen to recorded meetings

3

Floater ports, reserved to handle unexpected meeting attendance

2

Contingency ports reserved to handle call transfers to contacts for attendant

4

Ports in use or reserved for meetings


User Information

Most people who use Cisco Unified MeetingPlace must be assigned a user profile. User profiles identify and define the limits of user access. The information in each person's user profile identifies the person as an end user, a contact, attendant, or system administrator. User profiles also contain administrative and preference information.

Because multiple users might share common attributes, the database includes user groups, with which you enter information for several users simultaneously. You can also import profile information from another database (for example, from your voice-mail or e-mail system).

A user profile is required for anyone who wants to schedule a meeting, including vendors, consultants, and other people who may not work for your company. People who use Cisco Unified MeetingPlace only to attend meetings or to listen to recorded meetings do not need user profiles.

Synchronization between the Cisco Unified MeetingPlace database and a corporate database is automatic if you have Cisco Unified MeetingPlace Directory Services installed. For more information, refer to the Administration Guide for Cisco Unified MeetingPlace Directory Services at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_maintenance_guides_list.html.

If no value is specified for a user group field, the default is the value for that field in the guest profile. Ensure you have the correct information by reviewing the guest profile settings before you enter user profiles and user groups.

This section contains the following information:

Creating User Groups

Planning for Groups and Teams

Creating User Profiles

Importing User Profile and Group Information

Creating User Groups

When you have several users with common attributes, create a user group with those attributes. Then, assign the individual users to the user group. Doing so saves the time and energy of creating and maintaining duplicate information, and reduces errors. The information defined for the user group applies to every user who belongs to the group. (For more information, see the "Creating User Profiles" section.)

Each person who belongs to the user group must also have an individual user profile. When their profile information differs from the information for their user group, the user profile information takes precedence.

We recommend that you create user groups before you create user profiles. You can set up user groups in the following ways:

Set up groups based on a user's class of service (as described in the "Planning for Groups and Teams" section).

Define groups by region, department, or level of management, and then assign a contact to represent each functional group. Additionally, your company may define particular groups by their billing codes.

Planning for Groups and Teams

As you plan a database, understanding the differences between the following terms is important:

"Teams" define users who will most likely attend the same meeting. Users can belong to multiple teams.

"Groups" define users with a shared set of attributes, such as common system settings (for example, classes of service and regions) and common business characteristics (for example, departments, levels of management, and billing codes). Users are assigned to only one group.

Table 5-5 shows user groups defined by class of service (COS).

Table 5-5 Planning Groups and Teams 

 
Sample 1:
Restricted Users
Sample 2:
Standard Users
Sample 3:
Executive Users
Group Information

Name

Minimum Privilege

Standard Privilege

Executive Privilege

Number

1

2

3

Billing code

Your choice (optional)

Your choice (optional)

Your choice (optional)

Default mtg category

Your choice

Standard

Your choice

Group active?

Yes

Yes

Yes

Group Defaults

User ID of contact

Your choice (optional)

Your choice (optional)

Your choice (optional)

Time zone

Your choice

Your choice

Your choice

Language

Your choice

Your choice

Your choice

Abbreviated prompts?

No

No

No

Meeting Recording Defaults

Able to record mtgs? (COS)

No

Yes

Yes

Record meetings?

No

Yes

Yes

Who can access

Anyone

Anyone

Anyone

Auto-start recording?

No

No

No

Attachment access ordering

Play most recent first

Play most recent first

Play most recent first

Display mtg to everyone?

No

No

No

Outdial Meeting Defaults

Can call out from mtgs? (COS)

No

Yes

Yes

Can schedule guest outdial mtgs? (COS)

No

Yes

Yes

Allow outdials to guests from web? (COS)

No

Yes

Yes

Max outdials per mtg (COS)

0

5

Unrestricted

Can call other servers? (COS)

No

Yes

Yes

Ask for profile password?

No

No

No

Digit translation table (COS)

0

Your choice

Your choice

Meeting Preferences

Allow Internet access?

No

No

Yes

Restrictions

Scheduling restrictions (COS)

Near Term Mtg Limit (5)

Unrestricted

Unrestricted

Max mtg length (min) (COS)

60

Same as system default

Same as system default

Max # of attachments (COS)

0

5

30

Max # teams allowed (COS)

0

10

60

Receiving Notifications

Enable to receive?

Yes

Yes

Yes

Include attachments

Yes

Yes

Yes

Type of e-mail system

Your choice

Your choice

Your choice

Preferred delivery method

None

Your choice

Your choice

Alternate delivery method

Non

Your choice

Your choice


Creating User Profiles

Any user who will schedule meetings in Cisco Unified MeetingPlace must have a user profile. User profiles identify each user to the system and classify the system access that each user requires.

The classification assigned to a user determines which Cisco Unified MeetingPlace features the user can access. When users attend meetings, Cisco Unified MeetingPlace identifies them by their user profiles and assigns them privileges based on their profiles. For example, a profile determines whether a person can outdial during a meeting.

To allow users without profiles to attend meetings, a guest profile (profile number 0000) resides on the system. This profile defines the privileges of all guests and is used whenever users do not identify themselves to the system. System administrators can modify the guest profile but they cannot delete it.

The guest profile acts as a template. When you create a user profile, the profile derives its attributes from the guest profile. However, the guest profile does not provide values for the first name, last name, user ID, and profile number fields.

Because two users cannot have the same user ID or profile number, the values for these fields must be unique. We recommend the following values for assigning to user IDs and profile numbers, which will be easy for your users to remember:

User ID

Network login, first name followed by last initial, or e-mail address.

Profile number

Employee number or phone/extension number.


After you create user profiles, users can change their meeting preferences.

Each user profile includes a time zone setting. Set the time zone to reflect the geographical location in which users do business. When a user schedules a meeting, the system uses the home time zone setting to determine the time. For guest profiles, set the time zone to the location of the Cisco Unified MeetingPlace system.

Remember the following information:

For a description of each parameter in a user's profile, see Worksheet 5-18: User Profiles.

One of the most important settings in the guest profile is whether to allow users to outdial. To help prevent unauthorized outdialing from your system, we recommend that guest participants not be allowed to outdial.

Reservationless meetings use profile numbers as reservationless meeting IDs. When the Reservationless Meetings feature is turned on, profile numbers cannot match existing meeting IDs. If you try to create a profile number that matches an existing meeting ID, the system notifies you of the conflict. To resolve the conflict, either change the meeting ID or assign a different profile number for the user.

Importing User Profile and Group Information

If the information required for user profiles or user groups already exists in another database, such as an e-mail directory, a voice-mail directory, or a human resources database, you can import the profile information directly into the Cisco Unified MeetingPlace database.

This section contains the following information:

Importing with Cisco Unified MeetingPlace Directory Services

Importing Files Manually

Required File Format

Importing with Cisco Unified MeetingPlace Directory Services

Using a directory service, a company can store information about all its resources and personnel in one place, and allow other applications to access that information from a single source. Using the Directory Services integration application decreases the cost of managing information, which increases control and consistency of information, and makes security uniform across applications.

Directory Services synchronizes information in your corporate directory server with information in Cisco Unified MeetingPlace Audio Server. It interacts with common corporate directories such as Microsoft Active Directory and Netscape Directory Server through Lightweight Data Access Protocol (LDAP).

Information about new employees is entered into the corporate directory when they join the organization. Directory Services detects the addition and instantly creates a profile for new employees. As employees change departments and offices, their contact information changes. To ensure that Cisco Unified MeetingPlace has the most accurate information, changes to a person's information in the corporate directory are recognized and replicated on Directory Services. These automatic profile updates ease system use and limit calls to the help desk.

For more information, refer to the Administration Guide for Cisco Unified MeetingPlace Directory Services at http://www.cisco.com/en/us/products/sw/ps5664/ps5669/prod_maintenance_guides_list.html.

Importing Files Manually

If you do not have Cisco Unified MeetingPlace Directory Services installed, you must complete a manual file import. To simplify this process, you can import only those fields that contain profile- or group-specific information, such as user IDs, profile numbers, group names, group numbers, and contact information (such as e-mail addresses and phone numbers).

For specifications on the database fields, refer to the "File Import Specifications" appendix of the Administration Guide for Cisco Unified MeetingPlace Audio Server at http://www.cisco.com/en/us/products/sw/ps5664/ps5669/prod_maintenance_guides_list.html.

Required File Format

The import file must be a .csv file or a comma-delimited ASCII file (an unformatted or flat file). The first line of the file is a group of keywords that acts as a header and identifies the order in which data appears in all subsequent lines.

For example, if each line of information starts with the first name of the user and then lists the person's last name, user ID, profile number, phone number, contact user ID, group name, and time zone code, it would look like this:

fnm,lnm,uid,prfnum,phnum,ctcuid,name,tzcode
Chris,Lee,Lee,206,5551234,Patton,system,87
Pat,Park,Park,202,5556789,Patton,system,87

Before creating an import file, remember the following information:

Any spaces placed at the beginning or end of a value is automatically deleted during the import process unless the value and the leading or ending spaces are enclosed in double quotation marks (" "). Spaces within a value (for example using Tech Support as a billing code) are imported without being deleted.

Any commas used in a value must be enclosed in double quotation marks, as in "Lee,Chris" for a user ID.

Text types are not case sensitive.

Database Planning Worksheets

Use the worksheets below when you populate the Cisco Unified MeetingPlace Audio Server database. The database worksheets are arranged in the order in which they are described in this chapter. When you are ready to enter the information in the database, you may rearrange the worksheets in any order.

Worksheet 5-1: Usage Parameters

Worksheet 5-2: Scheduling Parameters

Worksheet 5-3: Company Information

Worksheet 5-4: Flex Fields

Worksheet 5-5: Telephony Access

Worksheet 5-6: Ports

Worksheet 5-7: Port Groups

Worksheet 5-8: System Parameters

Worksheet 5-9: Reservationless Meetings Requirements

Worksheet 5-10: Reservationless Meetings Systemwide Parameters

Worksheet 5-11: Network Management Information

Worksheet 5-12: Network Management Communities

Worksheet 5-13: Server Configuration

Worksheet 5-14: NS Site Configuration

Worksheet 5-15: Multiserver Meeting Requirements

Worksheet 5-16: Other Cisco Unified MeetingPlace Servers

Worksheet 5-17: User Groups

Worksheet 5-18: User Profiles

Worksheet 5-1: Usage Parameters

Usage parameters establish default values for the parameters that control basic Cisco Unified MeetingPlace operations.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.)

Field
Description
Default
Options and
Field Size
Value
Security

Min profile pwd length

Minimum number of characters in password that protects each phone access user profile. When 0, the password must be changed with each access.

Recommended: Same length as internal phone extensions.

6

Numeric—
0 to 11

 

Change profile pwd (days)

Frequency (in days) users must change passwords for phone access user profiles. When 0, password must be changed at each access.

Follow your company guidelines for similar telecommunications systems.

90

Numeric—
0 to 3650*

 

Min user pwd length

Minimum number of characters in each person's MeetingTime/Cisco Unified MeetingPlace Web Conferencing password.

Follow your company guidelines for similar e-mail and network-based systems.

5

Numeric—
0 to 11

 

Change user pwd (days)

Frequency (in days) users must change their MeetingTime/
Cisco Unified MeetingPlace Web Conferencing password. When 0, password must be changed at each access.

Follow your company guidelines for similar telecommunications systems.

90

Numeric—
0 to 3650*

 

Min meeting pwd length

Minimum number of characters in passwords for meetings. Follow your company guidelines for similar telecommunications systems.

This is an optional password to secure individual meetings.

0

Numeric—
1 to 11

 

Max profile login attempts

Number of unsuccessful login attempts by phone allowed to each user before system locks user's profile.

Follow your company's guidelines for similar telecommunications systems.

Deactivated profiles must be reactivated by the system administrator before users can regain access to their profile.

3

Numeric—
1 to 32767*

 

Disable Telnet?

When Yes, turns off Telnet access (when SSH is installed). System must be restarted for this setting to take effect.

No

Yes/No

 
Alarm Handling

Call out on major alarm?

Whether Cisco Unified MeetingPlace calls system administrator if an error condition affects system operation. Hardware and software failures and high-temperature conditions are major alarm conditions.

Recommended: Yes.

No

Yes/No

 

Call out on minor alarm?

Whether Cisco Unified MeetingPlace calls system administrator because of minor error condition (such as a trunk malfunction, or repeated login attempts)

No

Yes/No

 

Phone number to call

Phone number called by system if alarm occurs. The system checks for alarm conditions every 10 minutes. System outdials immediately to Alarm Out Call Phone Number and leaves recorded message about alarm. System continues to leave message every 30 minutes until alarm is cleared.

This prompt indicates alarm condition: "Hello, this is the Cisco Unified MeetingPlace system. An error has occurred which requires your attention."

Recommended: Phone or pager number of system administrator.

0

Alphanumeric—
0 to 32

 
Time Settings

24 hour time?

Time format in which meetings are scheduled.

When Yes, meetings are scheduled using 24-hour time. When No, time is 12-hour format (AM/PM)

No

Yes/No

 
Prompt Settings

Disable music?

Replaces music prompts with silence. For use with systems that use IP codecs that do not support music well, such as G.729a.

No

Yes/No

 
Assistance

Dial attendant on timeout?

Whether callers are transferred to attendant if they do not enter a number at the first voice menu.

No

Yes/No

 
Outdial Mtgs

# of retry attempts

Number of times the system tries to call each person, when outdial is Yes for a meeting.

This setting also determines the number of times the system goes through a user's Find Me sequence.

2

Numeric—
0 to 5

 

Delay between retries (sec)

Number of seconds between outdial retries.

This setting also determines the number of seconds between each set of Find Me calls.

300

Numeric—
1 to 900*

 
Multiserver Mtgs

# of retry attempts

In multiserver meetings, number of times the primary server tries to call each secondary server.

3

Numeric—
0 to 5

 

Delay between retries (sec)

Number of seconds between retries after a remote server outdial connection failure.

300

Numeric—
1 to 900*

 

Times to retry sending a setup character

In multiserver meetings, the maximum number of times the primary server retries sending the setup character when no response occurs.

3

Numeric—
0 to 5

 
Pager Settings

Prefix string

Number string required by certain paging services in some counties. Cisco Unified MeetingPlace adds this string at beginning of all pages.

Keep this field blank if users' paging services do not require prefix string.

Numeric and command characters
(# and *)—0 to 3

 

Suffix string

Number string required by certain paging services in some counties. Cisco Unified MeetingPlace adds this string at the end of all pages.

Keep this field blank if users' paging services do not require suffix string.

Numeric and command characters
(# and *)—0 to 3

 
Network Shadow Server

Shadow attached?

Whether a Cisco Unified MeetingPlace shadow network is attached to your system.

Read-only

SNA Settings

RSNA Enabled?

Whether the Reservationless Single Number Access feature is enabled

No

Yes/No

 
Email/GW Mapping

cc:Mail

Cisco Unified MeetingPlace mailbox for delivering meeting notifications to cc:Mail users.

Keep this setting at 0.

0

Numeric—0 to 4

 

Lotus Notes

Cisco Unified MeetingPlace mailbox for delivering meeting notifications to IBM Lotus Notes users.

For organizations with both Cisco Unified MeetingPlace for Lotus Notes and Cisco Unified MeetingPlace for Outlook installed, each integration must use a different mailbox on the Cisco Unified MeetingPlace system. To ensure that the integrations use different mailboxes, change either the Lotus Notes or Microsoft Exchange field to 2.

0

Numeric—0 to 4

 

Microsoft Mail

Cisco Unified MeetingPlace mailbox for delivering meeting notifications to Microsoft Mail users.

Keep this setting at 0.

0

Numeric—0 to 4

 

Microsoft Exchange

Cisco Unified MeetingPlace mailbox for delivering notifications to Microsoft Outlook users.

For organizations with both Cisco Unified MeetingPlace for Lotus Notes and Cisco Unified MeetingPlace for Outlook installed, each integration must use a different mailbox on the Cisco Unified MeetingPlace system. To ensure that the integrations use different mailboxes, change either the Lotus Notes or Microsoft Exchange field to 2.

0

Numeric—0 to 4

 

Qualcomm Eudora

Cisco Unified MeetingPlace mailbox for delivering meeting notifications to Qualcomm Eudora users.

Keep this setting at 0.

0

Numeric—0 to 4

 

Netscape Messenger

Cisco Unified MeetingPlace mailbox for delivering meeting notifications to Netscape Messenger users.

Keep this setting at 0.

0

Numeric—0 to 4

 

Other

Cisco Unified MeetingPlace mailbox for delivering meeting notifications to other types of mail users.

Keep this setting at 0.

0

Numeric—0 to 4

 
Miscellaneous

Minutes before auto logoff

Number of minutes the system waits before logging an idle system off MeetingTime.

 

Numeric—
1 to 65535*

 

Preserve mute status

Q&A meetings only: Whether to preserve speakers' mute status during Q&A meetings, when users are removed from the floor or placed in the waiting room.

 

Yes/No

 

Note The following fields are read only and provide information related to the Windows server running Cisco Unified MeetingPlace Web Conferencing.

Data Meetings

Data mtg IP address

IP address of Cisco Unified MeetingPlace Web Conferencing server.

Read-only

CGI path

Alias name of CGI script directory.

Read-only

CGI name

Executable name of CGI script program used to launch web conferencing sessions.

Read-only

HTTP port

Port number of Cisco Unified MeetingPlace Web Conferencing server.

Read-only

Data conferencing active?

Active state of Cisco Unified MeetingPlace Web Conferencing server.

Read-only


Worksheet 5-2: Scheduling Parameters

Meeting scheduling parameters control the meeting schedules at your location, and the settings determine how many of the conference ports on your system can be reserved for meetings at one time.

Use this worksheet to plan the Cisco Unified MeetingPlace scheduling parameters.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.)

Field
Description
Default
Options and
Field Size
Value
Scheduling Parameters

Max meeting length (min)

Maximum number of minutes for the length of a meeting. Users cannot schedule meetings longer than this amount.

Recommended: Consider length of typical meetings for your company and users.

240

Numeric—
15 to 1440*

 

Max ports per meeting

Number of conference ports that can be reserved for individual meetings.

Recommended: Consider meeting sizes typically conducted by your company and users.

8

Minimum 2;
maximum is lesser of 550 or number of conference ports licensed for your system

 

Maximum size that a rsvnless conf. can grow to

After a reservationless meeting has started, the maximum number of conference ports that it can use as participants join the meeting.

550

Minimum 0.
Maximum cannot exceed the number of conference ports purchased for your system.

 

Maximum size that a sched. conf. can grow to

After a scheduled meeting has started, the maximum number of conference ports that it can use as participants join the meeting.

550

Minimum 0.
Maximum cannot exceed the number of conference ports purchased for your system.

 

Minimum mtg ID length

Minimum number of characters in meeting IDs.

When configuring your system with minimum meeting ID number less than 4 digits, system automatically assigns 4-digit meeting ID numbers to new meetings when scheduler does not choose a vanity ID number.

4

Numeric—
1 to 9

 

Max adv days to schedule

How many days in advance people can schedule meetings.

60

Numeric—
1 to 330*

 

Max agenda recdg (sec)

Maximum length (in seconds) of a pre-recorded agenda. The system does not let users record an agenda longer than this amount. Users cannot record an agenda longer than this amount.

60

Numeric—
12 to 600*

 

Max mtg name recdg (sec)

Maximum length (in seconds) of a pre-recorded meeting name.

4

Numeric—
0 to 24

 

Max user name recdg (sec)

Maximum length (in seconds) of a pre-recorded user name.

4

Numeric—
4 to 24

 

Days until mtg stats purged

Number of days historical meeting data is stored on system.

60

Numeric—
0 to 365*

 

Default meeting type

Whether by default meetings are All Speaker or Lecture. Users can change this setting for individual meetings.

All Speaker

All Speaker/Lecture

 

Enable resched recrrng mtgs?

Whether users can reschedule recurring meetings using MeetingTime or Cisco Unified MeetingPlace Web Conferencing.

When Yes, users can apply change to a single meeting in the chain or all future occurrences of meeting.

No

Yes/No

 
Immediate Meetings

# of ports to schedule

Default for number of participants (locations) for immediate meetings. Users can change this setting when they initiate an immediate meeting.

4

Minimum 2; maximum cannot exceed number of conference ports in your system.

When scheduling, the real maximum is limited by the number of actual ports displayed in the server configuration.

 

Length of mtg (min)

Default length (in minutes) of immediate meetings. Users can change this setting when they initiate immediate meetings.

30

Numeric—
2 to 1440*

 
Video Meetings

Default # of ports to schedule

Default number of video participants (locations) for video conferences. Users can change this setting when they initiate a conference with video.

0

Numeric—
0 to 550

Maximum cannot exceed number of conference ports in your system.

When scheduling, the real maximum is limited by the number of actual video ports displayed in the server configuration.

 

Max ports per meeting

Maximum number of video ports that can be scheduled for a conference.

12

Numeric—
0 to 550

 

Block dial in

Whether Cisco Unified MeetingPlace blocks video endpoints from dialing in.

No

Yes, No

 

Local MCU Prioritization setting

The prioritization level for the local MCUs.

Delay

Local, Delay, Bandwidth

 

Outdial all video term. at mtg start

Whether Cisco Unified MeetingPlace blast outdials the invited video participants.

No

Yes, No

 

Admit unresolved PSTN/ISDN calls

Whether Cisco Unified MeetingPlace allows video endpoints without user profiles to dial in.

This setting affects only PSTN/ISDN calls. IP calls are not affected by this setting.

Yes

Yes, No

 

Sched. only if all video term are available

Whether Cisco Unified MeetingPlace requires that all invited video participants be available before the conference can be scheduled.

Yes

Yes, No

 

Video service code

Users select a video service code when they schedule meetings. Use this field to specify the default video service code for meetings.

This service code must match a valid MCU service code.

ASCII text—

 
Meeting Ports

Mtg start guard time (min)

Number of minutes before scheduled meeting start time that ports are reserved for meeting. (For example, if value is 5 and meeting is scheduled from 8:00 AM to 9:00 AM, ports are reserved from 7:55 AM to 9:00 AM, allowing early arrivals.)

Recommended: 0 (because most users schedule extra time). This parameter does not apply to reservationless meetings.

0

Numeric—
0 to 1440*

 

Mtg end guard time (min)

Number of minutes after scheduled meeting that ports remain reserved. (For example, if value is 5 and meeting is scheduled from 8:00 AM to 9:00 AM, ports are reserved from 8:00 AM to 9:05 AM, allowing for overrun.)

Recommended: 0, to ensure consecutive meetings can be scheduled. This parameter does not apply to reservationless meetings.

0

Numeric—
0 to 1440*

 

Mtg ID start guard time (min) or DID start guard time (min)

Number of minutes before scheduled start time that associated meeting ID or DID/DNIS number is reserved. This value and Mtg ID End Guard Time control when meeting IDs are available for reuse and when system recognizes a meeting ID.

If users try joining meeting before this time, they hear: "This is not a recognized meeting ID number." After this time, callers hear: "The meeting has not started."

Recommended: 30. This parameter does not apply to reservationless meetings.

To ensure DID/DNIS meeting numbers are available for reuse, compare the number of simultaneous conferences to be held on your system with the number of DID/DNIS meeting numbers available. If they are about the same, decrease this value.

30

Numeric—
0 to 1440*

 

Mtg ID end guard time (min) or DID end guard time (min)

Number of minutes after scheduled end time that associated meeting ID or DID/DNIS number is reserved and when system recognizes a meeting ID.

If users join a meeting during Mtg ID End Guard Time period, they hear: "The meeting has ended." After this time, they hear: "This is not a recognized meeting ID number."

Recommended: 30. This parameter does not apply to reservationless meetings.

30

Numeric—
0 to 1440*

 
Run-time Parameters

Extend meeting (min)

Number of minutes meetings are extended if time runs over and ports are available. Callers are warned that meeting will end, but they can extend meeting if ports are available.

Recommended: 15.

If a meeting is not extended because all ports are in use, callers hear: "This meeting will end in two minutes."

15

Numeric—
0 to 60*

 

Early mtg start (min)

Maximum minutes before scheduled start time that early arrivals can enter meeting. This time is added to Mtg Start Guard Time. (For example, if meeting start time is 9:00 AM, Early Mtg Start Minutes is 15, and Mtg Start Guard Time is 15, and ports are available, callers can enter meeting at 8:30 AM.)

For video conferences, this value must match the value the Early Meeting Start parameter on the Video Administration for Cisco Unified MeetingPlace server.

Recommended: 15. This parameter does not apply to reservationless meetings.

0

Numeric—
0 to 60*

 

Disconnect empty port (min)

Number of minutes that reserved ports are held after everyone hangs up, even if scheduled end time has not arrived. This time allows for longer meetings when people might break and then return.

Recommended: At least 15. This parameter does not apply to reservationless meetings.

15

Numeric—
0 to 30*

 

Early mtg release time (min)

Number of minutes before scheduled end time that ports are released if not in use. (For example, if meeting is scheduled from 8:00 AM to 9:30 AM, Early Mtg Release Time Minutes is 15, and everyone hangs up at 8:30 AM, ports are released at 9:15 AM.)

The Cisco Unified MeetingPlace Video Administration, when used, must have the same setting.

Recommended: 15.

15

Numeric—
0 to 30*

 
Auto-answer Parameters

Mtg controls device

Whether the meeting controls the auto-answer device.

No

Yes/No

 

Connected until mtg ends

Whether auto-answer devices remain connected until meetings end.

When Yes, disconnect timeout value is same as Disconnect Empty Port (min). When No, disconnect timeout value is 0.

Yes

Yes/No

 
MeetingNotes Settings

FF/RR playback incrmt (sec)

Number of seconds Cisco Unified MeetingPlace fast-forwards or rewinds when users press 1 or 3 while listening to meeting recordings on phone.

120

Numeric—
4 to 3600*

 

Max mtg recdg length (min)

Maximum recording time (in minutes) allowed for each meeting.

Recommended: Same as Max Meeting Length parameter.

240

Numeric—
0 to 1440*

 

Max mtg message length (sec)

Maximum length (in seconds) for pre-recorded single meeting messages.

60

Numeric—
15 to 1800*

 

Max voice comment (sec)

Maximum length (in seconds) for voice comments.

Numeric—
15 to 1800*

 

Warning at end of recdg?

Whether users hear warning that meeting recording is about to end.

When Yes, attendees are warned that meeting recording is about to end. When No, attendees hear the final two-minute warning.

Yes

Yes/No

 

# of days to retain

Number of days after a meeting that recordings remain stored.

7

Numeric—
0 to 60*

 
Prompt Information

End of mtg warning (min)

Number of minutes before scheduled end time when end-of-meeting warning is issued.

10

Numeric—
0 to 15*

 

Speak mtg access num?

Whether users scheduling meetings from phone hear the phone access number where their meeting is scheduled.

When No, users hear only the phone access number for meetings scheduled on a server other than their scheduling home server.

No

Read-only

 
Svr-Svr Connection

Initiate

In multiserver meetings, when the primary Cisco Unified MeetingPlace Audio Server system establishes its connection to a secondary Audio Server system.

At sched-
uled start time

At scheduled start time/When first person enters

 

Terminate

In multiserver meetings, when the primary Cisco Unified MeetingPlace Audio Server system terminates its connection to a secondary Audio Server system.

When meeting ends

When meeting ends/When last person leaves

 

Automatic multi-svr mtgs?

Whether users have access to automatic multiserver meetings

Yes

Read-only

 
Miscellaneous

Max team voice name (sec)

Maximum number of characters in a team ID.

24

Numeric—0 to 24

 

Min team number length

Minimum number of characters in a team ID.

9

Numeric—1 to 19

 
Scheduler Notifications

After # no-show recurring mtgs

Number of no-show recurring meetings after which system sends e-mail message to meeting scheduler to suggest canceling a recurring meeting chain.

1

Numeric—
1 to 100*

 

Periods before recurring mtg ends

Number of meetings before the predefined end of a recurring meeting chain when the system should send an e-mail to meeting scheduler warning that the chain is about to end and prompting to start a new one.

2

Numeric—
1 to 100*

 

Worksheet 5-3: Company Information

Site information records information that describes your company, such as your company name, address, and the names and phone numbers for people who will be the primary contacts for your installation partner or Cisco Advanced Services representative, as well as whom you should call when you need help with the Cisco Unified MeetingPlace system.

Use this worksheet to plan your company information.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.)

Field
Description
Default
Options and
Field Size
Value
Site Info

Company name

Your company's name.

Alphanumeric—
0 to 63

 

Address1
Address2
Address3
Address4

Your company's address.

Alphanumeric—
0 to 63

 

System SW version

Cisco Unified MeetingPlace Audio Server release number. Default information shipped with your system.

Predefined

Field cannot be changed

 

Language1
Language2
Language3
Language4

Languages installed with your Cisco Unified MeetingPlace system.

Field cannot be changed

 
Contact Info

MeetingPlace system mgr

Name of onsite person for your installation partner or Cisco Advanced Services representative to contact.

Alphanumeric—
0 to 63

 

Phone number

Phone number of Cisco Unified MeetingPlace system administrator (named in previous field).

Alphanumeric—
0 to 17

 

Alt phone number

Alternative phone number for Cisco Unified MeetingPlace system administrator (usually a pager or fax number).

Alphanumeric—
0 to 17

 

Telecom mgr

Name of onsite telecommunications person for your installation partner or Cisco Advanced Services representative to contact.

Alphanumeric—
0 to 17

 

Phone number

Phone number of Cisco Unified MeetingPlace telecom manager (named in previous field).

Alphanumeric—
0 to 17

 

Alt phone number

Alternative phone number for Cisco Unified MeetingPlace telecom manager (usually a pager or fax number).

Alphanumeric—
0 to 17

 

Information services mgr

Name of onsite Information Services (IS) person for Cisco service representatives to contact.

Alphanumeric—
0 to 17

 

Phone number

Phone number of Cisco Unified MeetingPlace IS administrator (named in previous field).

Alphanumeric—
0 to 17

 

Alt phone number

Alternative phone number for Cisco Unified MeetingPlace IS administrator (usually a pager or fax number).

Alphanumeric—
0 to 17

 
Vendor Info

Support phone number

Phone number for Cisco Unified MeetingPlace support information.

Your installation partner tells you this number.

Alphanumeric—
0 to 17

 

Sales phone number

Phone number for Cisco Unified MeetingPlace sales information.

Your installation partner tells you this number.

Alphanumeric—
0 to 17

 

Service contract number

Your installation partner tells you this number.

Alphanumeric—
0 to 17

 
Custom Notif Text

How to attend meeting

Detailed instructions that you provide about attending meetings. This information appears in e-mail notifications.

For example: "Welcome to <your company's name> MeetingPlace conference server. To attend a conference on the system, please call the main number and follow the voice prompts."

Alphanumeric—
0 to 499

 

How to access recorded meetings

Detailed instructions that you provide about accessing recorded meetings. This information appears in e-mail notifications.

For example: "Participants can attend meetings, leave voice comments about a meeting, and attach relevant meeting materials. To access recorded meetings over the phone, call the main number and select option 3."

Alphanumeric—
0 to 499

 

Worksheet 5-4: Flex Fields

Using flex fields, you can customize fields to your business needs. Use this worksheet to plan flex fields.

Remember the following information:

The first seven flex fields are for profile use, and the last seven flex fields are for meeting-specific use.

Flex field values are always visible to system administrators in the Configure Profiles and Groups windows.

Flex fields 4 to 7 are available only in MeetingTime 5.1 and later. Earlier releases of MeetingTime do not display these fields in the user, group, and meeting records.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.)

Field  
Description
Default
Options and
Field Size
Value

Active?

Whether this flex field is active.

When Yes, field displays in the MeetingTime profiles window and a value can be entered for it.

Yes

Yes/No

 

Title

Field title that displays in the corresponding MeetingTime window for this flex field.

Alphanumeric—
0 to 31

 

Type

Type of information the flex field holds, which also determines the format in which it is stored and interpreted.

Text

Text/Number/Yes/
No/Date

 

Import title

Field title used when importing raw profile report information containing flex field data.

Alphanumeric—
to 31

 

Protection level

Access that end users have to this flex field. Use this field to define attributes that you do not want end users to override, such as billing codes.

When Invisible, end users cannot see the field. When Read-only, end users can see but not edit the flex field. When Editable, end users can see and edit the field value.

Invisible/
Read-only/
Editable

 

Uses data from profile?

Whether this field is used for profile purposes.

Yes

Yes/No

 

Use defined choices?

Note This field is available only for Profile Flex Fields 4 to 7 and Meeting Flex Fields 4 to 7.

Whether users must choose from a list of predefined values (which you create) to enter in a flex field, or enter an unrestricted value. When Yes (default), users see list of predefined values in Schedule and Review tabs. (To define values, see the next field.)

Yes

Yes/No

 

User choice strings

Note This field is available only for Profile Flex Fields 4 to 7 and Meeting Flex Fields 4 to 7.

Use to define a list of predefined values when Use Defined Choices is Yes. (When No, no list displays.)

To define values, click User Choice Strings. Click Add, type first value (up to 23 characters), then click OK. Repeat for each value you want in the list. (Combined length of all values cannot exceed 299 characters. Do not include commas.) Click OK to save all values.

Values that you define

 

Required field?

Note This field is available only for Profile Flex Fields 4 to 7 and Meeting Flex Fields 4 to 7.

Whether a flex field requires a value when users schedule or change a meeting. Default is No. When Yes and users try to save a record that includes an empty required field, they receive an error message.

Required fields display in red in Meeting attributes (in Schedule, Attend, and Review tabs), and in Configure tab for user profile and group profile records.

A flex field in a user profile that inherits the default value from the group profile flex field satisfies the requirement to contain a value.

No

Yes/No

 

Worksheet 5-5: Telephony Access

Telephony access information describes how the Cisco Unified MeetingPlace system accesses your phone network.

Use this worksheet to plan the telephony access.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.)

Field
Description
Default
Options and
Field Size
Value
General Information

Server number

A predefined number that identifies the server. As a standalone system, the Cisco Unified MeetingPlace 8106 or 8112 server is always defined as server number 0.

Predefined

Numeric—0 to 8

 

Main phone number

Main phone number for the Cisco Unified MeetingPlace 8106 or 8112. Assigned by the phone service provider or your company's telephony network administrator.

Alphanumeric—0 to 32

 

1st alternate ph number

If your system has multiple phone numbers (such as a toll-free 1-800 number and a local phone number), you can enter these numbers in the alternate number fields. Users see these phone numbers in future versions of the e-mail notifications.

Alphanumeric—0 to 32

 

Label for notifications

Describes the 1st alternate phone (for example, a toll-free or local number). Users see these labels in future versions of the e-mail notifications.

Alphanumeric—0 to 32

 

2nd alternate ph number

If your system has more than one alternative phone number, enter the second alternate number in this field.

Alphanumeric—0 to 32

 

Label for notifications

Describes the 2nd alternative Cisco Unified MeetingPlace number in the e-mail notifications.

Alphanumeric—0 to 32

 

3rd alternate ph number

If your system has more than two alternate phone numbers, enter the third alternate number in this field.

Alphanumeric—0 to 32

 

Label for notifications

Describes the 3rd alternative Cisco Unified MeetingPlace number in the e-mail notifications.

Alphanumeric—0 to 32

 
Video Information

Main video ph number

Main phone number for the Cisco Unified MeetingPlace Video Integration MCS. Assigned by the phone service provider or your company's telephony network administrator.

Numeric

 

1st alternate ph number

If your system has multiple phone numbers (such as a toll-free 1-800 number and a local phone number), you can enter these numbers in the alternate number fields. Users see these phone numbers in future versions of the e-mail notifications.

Numeric

 

2nd alternate ph number

If your system has more than one alternative phone number, enter the second alternate number in this field.

Numeric

 

Note If you are not using Direct Inward Dial (DID) or Direct Dialing Inward (DDI), skip the rest of this table.

DID start number

Determines where the range of DID/DNIS or DDI digits in use begins.

Alphanumeric—0 to 20

 

Number of DID digits

Defines the number of digits the system receives.

0

Numeric—
0/ 2 to 6

 

DID block size

Total range of DID/DNIS or DDI digits in use. This value is assigned by the phone service provider or your company's telephony network administrator.

0

Numeric—
0/Number for total range of DID/DNIS or DDI digits in use (usually a multiple of 100, as in 100, 200, 400)

 
DID Assignments
U.S., Canada, Hong Kong, European Union
Type, Start, Size
 

Access range 1

Access range 2

Access range 3

Access range 4

Access range 5

Access range 6

Access range 7

Access range 8

Access range 9

Access range 10

Blocks of DID/DNIS or DDI numbers and the access type assigned to each block. Create up to 10 blocks of numbers. Possible types are DID Meeting, Profile, Combined Access. When dialed, DID/DNIS or DDI number does not provide direct access to a meeting, profile, or combined access.

Recommended: One DID/DNIS or DDI number assigned to each type of access: meeting, profile, and combined access. Remaining blocks of numbers can be set for meeting IDs.

Note For DID Meeting access, do not specify a range greater than 1. Instead, specify individual numbers to access, with a range of 1 (for example, DID Meeting 2131,1). Otherwise, meetings with IDs outside the range cannot be scheduled.

Access type:
None/ DID Meeting/ Profile/Combined

Starting number:
Numeric—0 to 15

DID block size:
Numeric—0/
A number indicating total range of DID/DNIS or DDI digits in use

___ ___ ___

___ ___ ___

___ ___ ___

___ ___ ___

___ ___ ___

___ ___ ___

___ ___ ___

___ ___ ___

___ ___ ___

___ ___ ___


Worksheet 5-6: Ports

The Ports parameters define the access type to assign to each port that connects the Cisco Unified MeetingPlace system to the phone network.

Use this worksheet to plan the ports parameters.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.)

Field
Description
Default
Options and
Field Size
Value
Port Information

Server number

Identifies the server. As a standalone system, the Cisco Unified MeetingPlace 8106 or 8112 server is always defined as server number 0.

Predefined

Numeric—0 to 8

 

ID number

Number that identifies the port.

Predefined

Numeric—
0 to 1151*

 

Span ID (digital trunks only)

For digital trunks, identifies individual span that controls this port (T1 only).

This number is predefined and is -1 if port is not configured.

Predefined

Numeric—
0 to 47*

 

Card ID

Identifies which card slot controls this port.

This number is predefined and is -1 if port is not configured.

Predefined

Numeric—
0 to 11

 

Port group ID

Identifies port group to which this port belongs. If you assign this port to a port group, the group configuration parameters can be used if the Use Group Defaults field is Yes.

Use -1 if port does not belong to a port group. If you assign individual ports to a port group, you can minimize port configuration data entry. Individual ports use configuration information of the port group they are assigned to.

Numeric—
0 to 11

 

Use group defaults?

Whether to use the Port Group default settings.

When Yes, remaining field values are retrieved from group profile and become read-only.

Yes

Yes/No

 

Note When the Use Group Defaults field is Yes, the following fields are retrieved from the group profile and become read-only.

Active?

Whether this port can be used now.

You can configure ports now for future use, and then inactivate port groups during servicing.

Yes

Yes/No

 

Provider

Abbreviation that identifies service provider.

Alphanumeric—0 to 17

 

Circuit ID

Number assigned by circuit provider to identify the circuit.

Alphanumeric—0 to 17

 

Card type

(U.S., Canada, Hong Kong, European Union) Whether this port is a digital T1, E1, IP, or unassigned.

Based on system configur-
ation

T1/E1/IP/None (unassigned)

 

Signaling protocol

(U.S., Canada, Hong Kong, European Union) Signaling type used by this trunk.

For T1: Options are Loop Start/Ground Start/E&M Wink Start/Clear Channel/Protocol Table for any AudioCodes-supported integration like ISDN-PRI.

For E1: Options are any E1 for any integration like Euro-ISDN or DPNSS/Protocol Table for any AudioCodes-supported integration like Euro-ISDN or QSIG.

Based on system configur-
ation

See description

 

# of DID digits expected

Number of digits sent by PBX or network.

4

Numeric—
0/
2 to 6

 

Mtg ID for direct mtg access (Digital)

Meeting that callers to this port attend when DID/DNIS digits = 0 and default access type is DID Meeting.

Use the meeting ID or DID/DNIS number of meeting into which you want callers placed.

Meeting ID number based on your Minimum Mtg ID Length and Maximum Mtg ID Length parameters

 

Default access type

Cisco Unified MeetingPlace access type applied to this port in absence of dialed number information. Your choice depends on access level you want users to have on these ports.

Combined

DID Meeting/Profile/Combined Access identifier

 

Language

Language configured for this port. Possible values are additional languages installed on your Cisco Unified MeetingPlace system.

English (USA)

No Language/
English (USA)/
Other installed language

 

Human assistance?

When meeting participants need help, the system uses another port to connect them (through call transfer) to a contact or attendant. This field value determines whether this port can be used for assistance during meetings.

Set this value to Yes, assuming attendant can be reached on this port by flash transfer.

No

Yes/No

 

Flash transfer?

Whether these ports initiate call transfers by hook flash.

No

Yes/No

 

Outdial?

Whether these ports can be used for outgoing calls.

Recommended: Yes.

Yes

Yes/No

 

Worksheet 5-7: Port Groups

To configure multiple ports at one time, organizing them into port groups.

Use this worksheet to plan the port groups.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.)

Field
Description
Default
Options and
Field Size
Value
Group Information

ID number

Number that identifies this port group. This number is predefined. Default port group for PSTN is 0; default port group for IP is 1.

Assign every line coming into Cisco Unified MeetingPlace to a port group.

0 (PSTN);

1 (IP)

Numeric—
0 to 31

 
Group Characteristics

Active?

Whether to use this port group definition. You can define ports now for use later.

Most likely, port groups will always be active. You can inactivate port groups during servicing.

Yes

Yes/No

 

Provider

Abbreviation that identifies service provider.

Alphanumeric—0 to 32

 

Circuit ID

Number assigned by circuit provider to identify the circuit.

Assigned by circuit provider

 

Card type

(U.S., Canada, Hong Kong, European Union) Whether this trunk is a digital T1, E1, IP, or unassigned.

Based on system configuration

T1/E1/IP/
None (unassigned)

 

Signaling protocol

(U.S., Canada, Hong Kong, European Union) Signaling type used by this trunk.

For T1: options are Loop Start/Ground Start/E&M Wink Start/Clear Channel/Protocol Table for any AudioCodes-supported integration like ISDN-PRI.

For E1: options are any E1 for any integration like Euro-ISDN or DPNSS/Protocol Table for any AudioCodes-supported integration like Euro-ISDN or QSIG.

Based on system configuration

See description

 

# of DID digits expected

Number of digits sent by PBX or network.

4

Numeric—
0/
2 to 6

 

Mtg ID for direct mtg access or Default digits for system

Meeting that callers to this port attend when DID/DNIS digits = 0 and default access type is DID Meeting.

Use the meeting ID or DID/DNIS number of meeting into which you want callers placed.

Meeting ID based on your Minimum Mtg ID Length and Maximum Mtg ID Length parameter

 

Default access type

Cisco Unified MeetingPlace access type applied to all ports in group in absence of dialed number information. Your choice depends on the access level you grant to users on these ports.

Combined

DID Meeting/
Profile/
Combined Access/
Loop Through Transfer

 

Language

Language selected for port group. Possible values are additional languages installed on your Cisco Unified MeetingPlace system.

English (USA)

English (USA)/
Other installed language

 

Human assistance?

When meeting participants need help, the system uses another port to connect them (through call transfer) to a contact or attendant. This field value determines whether ports in this group can be used for assistance during meetings.

Set this value to Yes, assuming attendant can be reached on this port group by flash transfer.

No

Yes/No

 

Flash transfer?

Whether these ports initiate call transfers by hook flash.

No

Yes/No

 

Outdial?

Whether these ports can be used for outgoing calls. A port must belong to a port group to be used for outdial.

Yes

Yes/No

 

Worksheet 5-8: System Parameters

The System Parameters window defines whether you are using DID/DNIS meeting access. Additionally, to eliminate clock drift on your Cisco Unified MeetingPlace system you can enter the network address of a Network Time Protocol (NTP) server from this window.

Use this worksheet to plan the system parameters.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.)

Field
Description
Default
Options and
Field Size
Value

Allow vanity mtg IDs?

Whether users may assign custom IDs to meetings they schedule. System administrators may assign vanity meeting IDs, regardless of this setting.

If your system is configured for DID/DNIS access, use this parameter (when DID Meeting Access field is Yes) to allow users to assign vanity meeting IDs to DID/DNIS meetings. (See notes after this worksheet.)

Yes

Yes/No

 
DID Settings

DID meeting access?

Whether the system receives DID or DDI information. Your configuration choices depend on the trunking configuration selected for Cisco Unified MeetingPlace.

No

Yes/No

 

Use DID for routing only?

Whether DID/DNIS number is used only to route calls to various applications. Use this field when the DID Meeting Access field value is Yes and you want a DID/DNIS number to route directly to a specific Cisco Unified MeetingPlace application.

No

Yes/No

 
NTP Server

Address 1

IP address of NTP host.

0.0.0.0

Dotted decimal format

 

Address 2

IP address of alternative NTP host.

0.0.0.0

Dotted decimal format

 

Address 3

IP address of alternative NTP host. (See notes after this worksheet.)

0.0.0.0

Dotted decimal format

 

Remember the following information:

To prevent users from assigning custom meeting IDs (such as 1234), set this value to No. Cisco Unified MeetingPlace assigns a randomly generated ID to all meetings scheduled from then on. Although vanity meeting IDs are easy for users to recognize and identify, they also make it easier for hackers or uninvited participants, to gain unauthorized access.

When the Allow Vanity Mtg IDs field is Yes, you can restrict groups or individual users from assigning vanity IDs to meetings scheduled by phone. To do so, in the Configure tab, select User Profiles or User Groups. For the Can Chg Mtg ID Via Phone attribute, choose No. User profiles inherit the group setting, but you can change it for individual users.

Alternative NTP hosts are available if one or more NTP servers is down or inaccessible. Also, if all three hosts are accessible and one is inconsistent, the inconsistent one is ignored.

Worksheet 5-9: Reservationless Meetings Requirements

This worksheet describes the system requirements for conducting reservationless meetings.

When using reservationless meetings, the server should be sized to accommodate peak usage with at least 20 percent additional capacity, to ensure there are no busy signals for end users. Cisco offers several capacity assurance programs to provide additional capacity at no cost to the customer. For more information, contact your customer support representative.

The Reservationless Meetings feature is available for the following languages:

French (Canada)

German

Japanese

French (France)

Portuguese (Brazil)

Spanish (Americas)

U.K. English

U.S. English

Action
Description
Complete

System requirements

Cisco Unified MeetingPlace 8106 or Cisco Unified MeetingPlace 8112 server with Cisco Unified MeetingPlace Audio Server Release 6.0.

 

Configuration

The port (group) must be configured for "Combined Access" and a command line utility (mtgmode) must be run.

 

Reservationless meetings with web conferencing

If reservationless meetings will include access to web conferencing:

Cisco Unified MeetingPlace Web Conferencing must be installed.

Windows 2003 server is required for dedicated use as a Web Conferencing server.

 

Worksheet 5-10: Reservationless Meetings Systemwide Parameters

Three fields in the Reservationless Mtgs action in the System tab allow you to set attributes for reservationless meetings.

Use this worksheet to plan the reservationless meeting fields.

Field
Default
Description
Options
Value

Enable reservationless

No

Allow or prevent reservationless meetings.

This field is read-only.

Yes/No

 

Owner Initiate with 2 key?

No

When No, meeting owners must enter their profile and password. When Yes, meeting owners start their reservationless meeting by pressing 1 to attend the meeting and then 2 to start the meeting (after which they must enter their password).

Yes/No

 

Allow 3rd party initiate?

Yes

Whether profile users can initiate reservationless meetings before the meeting organizer arrives.

Yes/No

 

Bill 3rd party initiator?

Yes

Whether the reservationless meeting is billed to the meeting initiator (when a third party initiates the meeting) or the meeting organizer (no matter who initiates the meeting).

Yes/No

 

Worksheet 5-11: Network Management Information

Network management information controls high-level access to the Cisco Unified MeetingPlace SNMP module and allows the system to exchange SNMP data with the rest of your network.

Use this worksheet to plan the network management information fields.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.)

Field
Description
Default
Options and
Field Size
Value

Port number

UDP port on which Cisco Unified MeetingPlace listens for incoming SNMP messages.

Recommended: Default value (port 161) unless you know that your network management software uses a different port number.

Port 161

Numeric—
Use default value

 

System contact

SNMP MIB II system contact.

This value can be set through your SNMP management workstation.

System contact un-
known

Alphanumeric—
1 to 256*

 

System location

SNMP MIB II system location.

This value can be set through your SNMP management workstation.

System contact un-
known

Alphanumeric—
1 to 256*

 

Disable SNMP Queries?

Allows all queries to be disabled, without affecting traps, for higher security.

No

Yes/No

 

Worksheet 5-12: Network Management Communities

Network management communities control the IP addresses to which SNMP messages are sent and the type of access provided in response to those messages.

Use this worksheet to plan the network management communities fields.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.)

.

Field
Description
Default
Options and
Field Size
Value

Name

Name of this network management community.

Standard public ("MeetingPlace-public") and private ("MeetingPlace-private") communities are defined.

MeetingPlace- private

Alphanumeric—
0 to 32

 

IP address

IP address to which traps are sent for trap communities.

Ignored for non-trap communities.

0.0.0.0

Dotted decimal format, as in 198.207.208.1

 

Read-Write?

When Yes, SNMP messages for this community can modify stored SNMP data.

Ignored for trap communities.

Yes

Yes/No

 

Is it a trap?

Whether this community is a trap community.

For a trap community, set this value to Yes; otherwise, No.

Queries are not enabled for trap communities. Trap communities only generate traps. Non-trap communities define permissions for queries.

No

Yes/No

 

Worksheet 5-13: Server Configuration

In the Server Configuration window you enter the Cisco Unified MeetingPlace network addresses for your system.

Use this worksheet to plan the server configuration fields.


Caution Entering incorrect information in the Network Parameters window can make the system inaccessible from the network. Make sure you enter all the information correctly.

Remember the following information:

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.)

Cisco Unified MeetingPlace Audio Server is not aware of DNS. You cannot ping hostnames or use DNS hostnames for configuration.

Field
Description
Default
Options and
Field Size
Value

Server number

Identifies the server. As a standalone system, the Cisco Unified MeetingPlace 8106 or 8112 server is always defined as server number 0.

Predefined

Numeric—0 to 8

 

Type of unit

Identifies the system as a conference server or Cisco Unified MeetingPlace integration.

Predefined

Conference Server/
MeetingPlace Gateway

 

Server hostname

Host name of this Cisco Unified MeetingPlace server on your network.

Alphanumeric—
1 to 32

 

Server description

Descriptive name of this Cisco Unified MeetingPlace server.

Alphanumeric—
0 to 32

 

Is active?

Whether this server is currently active.

Yes

Yes/No

 

Flex Menus active?

Whether Flex Menus are currently active.

No

Yes/No

 

Ethernet address

Ethernet address of this server. This value is defined by the installation partner when your Cisco Unified MeetingPlace system is physically installed.

 

IP address

Address of Cisco Unified MeetingPlace host on the network.

Dotted decimal format, as in 198.207.208.1

 

System serial #

Cisco Unified MeetingPlace serial number. Default information shipped with your Cisco Unified MeetingPlace system.

Predefined

This field cannot be changed

N/A

Modem phone number

Phone number for Cisco Unified MeetingPlace service modem on your system or remote maintenance port.

Alphanumeric—
0 to 31

 

Call out if network disconnects?

Determines if conference server should dial attendant when server is disconnected from network server.

Predefined

Yes/No

 

Access ports

Number of ports on this server used to schedule new meetings and listen to recorded meetings.

 

Conference ports

Total number of ports on this server, including floater and contingency ports.

 

Contingency ports

Number of conference ports held in reserve to let people reach a contact or attendant during meetings.

Recommended: 1-2 of conference ports on the system.

1

Numeric—0 to 32

 

Floater ports

Number of ports reserved as floater ports. Floater ports can be used by any meeting to accommodate unanticipated additional attendees.

Recommended: 15% of total conference ports.

2

Minimum 0; maximum cannot exceed number of conference ports in your system.

 

Overbook ports

Number of ports to allow for scheduling meetings that exceed the number of available conference ports on system.

Recommended: A number less than or equal to number of floater ports.

(See notes after this worksheet.)

0

Numeric—
0 to 1200*

 

Max recording space (min)

Total recording time (in minutes) that can be used to record meetings.

Recommended: 80% to 85% of total minutes of recording space.

0

Numeric—
0 to 85332*

 

Voice encoding method

The voice encoding method for the system.

Predefined

Mu-Law encoding
A-Law encoding

 

RFC2833 payload type

Identifies which packets in the IP voice stream contain digit information, such as, user keypresses.

101

Numeric—
96 to 127

 

For the Overbook Ports field, remember the following information:

Cisco Unified MeetingPlace uses the following calculation:

   Number of conference port licenses installed
- Number of floater ports
- Number of contingency ports
+ Number of overbooked ports 

_________________________________________  
= Maximum number of ports that can be scheduled

On a system with both reservationless and scheduled meetings, use the following guidelines to configure your system. These guidelines maximize the port utilization and capacity of your system:

If R<50%

Immediate meetings: 3

Overbook ports: N x 30%

Floater ports: N x 30%

If R>=50%

Immediate meetings:0

Overbook ports: N x 15%

Floater ports: N x (R + 25%)

[R = percentage of traffic used for reservationless meetings; N = total number of conference ports including capacity assurance (CAP); 30% can be substituted for standard operating percentage.]

On a system with reservationless only meetings, use the following guidelines to configure your system. These guidelines maximize the port utilization and capacity of your system.

If R = 100%

Immediate meetings: 4

Overbook ports: N

Floater ports: N

[R = % of traffic used for reservationless meetings; N = total number of conference ports including capacity assurance (CAP).]

Make sure the total number of scheduling ports available (including overbook ports) is equal to or greater than the largest meeting size you anticipate scheduling. For a new system, these guidelines are good defaults, but keep the current settings for a system that is already configured.

Worksheet 5-14: NS Site Configuration

NS Site configuration records describe information such as server location, the time zone where each server resides, and the phone number of the attendant, or help desk, where users are transferred if they need help during a conference.

Use this worksheet to plan the NS Site configuration fields.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.)

Field
Description
Default
Options and
Field Size
Value

NS Site number

Identifies this site.

Based on the configuration and deployment of your Cisco Unified MeetingPlace system, you might have Cisco Unified MeetingPlace servers installed in a single site, or at multiple sites.

For the Cisco Unified MeetingPlace 8106 or 8112, only site 0 is used. Other site records may be defined but they will be ignored.

Predefined

Numeric—0 to 7

 

NS Site name

A descriptive name that identifies this site.

Alphanumeric—0 to 32

 

Is active?

Whether this Cisco Unified MeetingPlace site is active.

Based on the configuration of your system, there may be multiple sites that are not currently active.

No

Yes/No

 

Attendant phone

Phone number users are sent to if they request operator assistance, do not enter a number at the first voice prompt, or try to access an inactive profile.

Make the number consistent with how you will support the system. The person called to help callers must be available for assistance, trained as a contact or attendant on Cisco Unified MeetingPlace, and have access to contact and attendant materials.

Recommended: Phone number of help desk or company receptionist.

0

0/
7- or 10-digit number

 

Time zone

Maintains system's internal clock.

Recommended: Time zone in which system is location.

local-time

Choose from full or subset list of time zone names

 

Subnet mask

Mask that completes address for Cisco Unified MeetingPlace host at this site.

Dotted decimal format

 

Broadcast address

Address used to broadcast packets on local LAN segment.

Dotted decimal format

 

Default gateway

Address of integration that accepts and routes information to other networks.

Dotted decimal format

 

Worksheet 5-15: Multiserver Meeting Requirements

This worksheet describes the requirements for scheduling and conducting multiserver meetings.


Note To ensure Cisco Unified MeetingPlace Audio Server and Cisco Unified MeetingPlace Web Conferencing compatibility, check that releases are interoperable. See the "Cisco Unified MeetingPlace Component Compatibility Matrix" section on page 1-24.


Action
Description
Complete

System requirements

Make sure all Cisco Unified MeetingPlace servers are running Cisco Unified MeetingPlace Web Conferencing.

If multiserver meetings will be scheduled using Web Conferencing, make sure that systems participating in the multiserver meeting have Web Conferencing installed.

 

Scheduling requirements

For each user who will schedule multiserver meetings, provide a user profile on each Cisco Unified MeetingPlace 8106 or 8112 server.

Enable the user profiles of those who will schedule meetings with multiserver scheduling privileges.

Create Server Information records on all Cisco Unified MeetingPlace systems for each Cisco Unified MeetingPlace 8106 or 8112 server.

To schedule multiserver meetings over the web:

Users must use a supported web browser.

Users must be able to access each site's Cisco Unified MeetingPlace Web Conferencing server.

Cisco Unified MeetingPlace Web Conferencing must be installed and running at each Cisco Unified MeetingPlace site.

To schedule multiserver meetings using MeetingTime, users must be able to access each site's Cisco Unified MeetingPlace server through their MeetingTime client software and have MeetingTime on their system.

 

Recommended server configuration

Make sure all Cisco Unified MeetingPlace servers are time synchronized using a Network Time Protocol (NTP) server.

Make sure all servers are properly named across all Cisco Unified MeetingPlace systems.

Record a voice name for the other Cisco Unified MeetingPlace servers.

Set the same guard times on all Cisco Unified MeetingPlace servers.

Set the same extend meeting parameters on all Cisco Unified MeetingPlace servers.

Record the breakout session warning prompt that will be played before participants enter a breakout session.

 

Worksheet 5-16: Other Cisco Unified MeetingPlace Servers

If your organization will conduct multiserver meetings, you must supply the information in this worksheet for the other Cisco Unified MeetingPlace servers. You may need to contact the system administrator of the other Cisco Unified MeetingPlace servers to determine these settings.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.)

Field
Description
Default
Options and
Field Size
Value

Name

Name of other Cisco Unified MeetingPlace server. This name appears in MeetingTime and Cisco Unified MeetingPlace web when users select the servers to schedule for multiserver meetings.

Alphanumeric—
1 to 19

 

ID number

ID number of other Cisco Unified MeetingPlace server. When users outdial from within a meeting to another Cisco Unified MeetingPlace server, they enter the ID number of the server to add to the meeting.

ID numbers are for Reservationless Single Number Access (RSNA) and multiserver meetings.

For RSNA, Numeric—
1 to 32767*

For multiserver meetings, Numeric—0 to 9

 

Phone number

Phone number of the other Cisco Unified MeetingPlace server. The system uses this number to dial out to the Cisco Unified MeetingPlace server to set up a multiserver meeting.

Alphanumeric—
0 to 32

 

Ethernet address

12-digit hex string representing the Ethernet address of other Cisco Unified MeetingPlace server.

 

VoIP Gateway IP Address 1

IP address of the remote server's VoIP integration.

Dotted decimal format, as in 198.207.208.1

 

VoIP Gateway IP Address 2

IP address of a second remote server's VoIP integration, if there is one.

Dotted decimal format, as in 198.207.208.1

 

Will Accept SNA Transfers?

Whether this server accepts single number access transfers.

Yes/No

 

Extended RSNA Codec

Choose a codec in order to generate an Extended RSNA Prefix value for the remote server. If you do not want to use the Extended RSNA Prefix feature, choose None.

None

None/G711uLaw/
G711aLaw/G729

 

Extended Prefix

After you choose the Extended RSNA Codec and save your changes, MeetingTime displays a value in the Extended Prefix field. You will use this value when configuring dial peers for the RSNA transfer on the voice gateway.

Read-only

 

WebPublisher location

Either the IP address or URL of Cisco Unified MeetingPlace web for other Cisco Unified MeetingPlace server.

 

Data conference active?

If Web Conferencing is installed and operational on other Cisco Unified MeetingPlace server, set this value to Yes.

Yes/No

 

Server number

As a standalone server, the Cisco Unified MeetingPlace 8106 or 8112 number is 0.

Numeric—0 to 8

 

Worksheet 5-17: User Groups

To quickly and easily enter default profile information for multiple users at one time, assign users to a user group.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.

Field
Description
Default
Options and
Field Size
Value
Group Information

Name

Name by which you want to identify group.

Recommended: A name that describes the group (Marketing).

Do not include spaces. Use an underscore character (_) instead (Field_Sales).

System

Alphanumeric—1 to 17

 

Number

Number by which you want to identify group.

0

Numeric—
0 to 17

 

Billing code

A code for generating billing reports. Can be based on your company's internal conventions (for example, department codes).

Alphanumeric—0 to 17

 

Default mtg category

Meeting category assigned to meetings the group's users schedule.

"Standard"

Selected name

 

Group active?

Whether group is active.

You can define groups now, and make them active later (for example, after the group's users complete training).

No

Yes/No

 

Profile type

Whether the members of the group are users or video terminals.

User

User/Video Terminal

 
Group Defaults

User ID of contact

User ID of contact or attendant who supports group's users.

Alphanumeric—0 to 17

 

Time zone

Time zone in which the users in this group are located.

Recommended: Time zone in which user group is located.

Time zone information can vary for individual users in a group. Set time zone information for each user in individual user profiles.

Local-time

Time zone name

 

Language

Language this group's users prefers.

Language information can vary for individual users in a group. Set language information for each user in individual user profiles.

English (USA)

English (USA)/
Other installed language

 

Abbreviated prompts?

When Yes, all users hear abbreviated prompts when they call Cisco Unified MeetingPlace. When No, all users hear unabbreviated prompts.

No

Yes/No

 

Scheduling home server?

The local server for users in this group.

0

Read-only

 
MeetingNotes Defaults

Able to record mtgs?

Whether users in group can record meetings.

Yes

Yes/No

 

Record meetings?

Whether by default meetings scheduled by group's users are recorded.

No

Yes/No

 

Who can access

Who can request attachments and listen to meetings recorded by group's users. When None, a recorded meeting and its attachments must be posted manually for other participants to hear.

Anyone

None/Anyone/
MeetingPlace Users/
Invited Guests

 

Auto-start recording?

For meetings scheduled to be recorded, whether by default recording starts automatically when second participant enters meeting.

Yes

Yes/No

 

Attachment access ordering

Order in which group's users hear list of attachments.

Most recent first

As submitted/
Most recent first

 

Display mtg to everyone?

Whether by default to allow Cisco Unified MeetingPlace web guests to view meetings.

No

Yes/No

 

Display rsvnless mtgs to everyone?

Whether by default to allow Cisco Unified MeetingPlace web guests to view reservationless meetings.

No

Yes/No

 
Outdial Meeting Defaults

Can call out from mtgs?

Whether group's users can outdial to others while they are in a meeting.

No

Yes/No

 

Can schedule guest outdial mtgs?

Whether group's users can schedule meetings that let guests join voice conference by web. This parameter is enabled only if this group has outdial privileges.

When No, the Allow Outdials to Guests From Web parameter is disabled for this group. When Yes, group's users can change Allow Outdials to Guests From Web for individual meetings.

No

Yes/No

 

Allow outdials to guests from Web?

For meetings scheduled by this group, whether guests can join the meetings by Web.

When Yes and a meeting is scheduled, the system can outdial to guests when they click Join Voice Conference button. When No, guests who click this button see the phone number to call to join meeting.

No

Yes/No

 

Max outdials per mtg

Number of outdials group's users can place from within one meeting.

Note This field limits only the number of times this group's users can outdial from a meeting by pressing #3. It does not restrict any other method of outdialing.

0

Numeric—
0 to 500*/
Unrestricted

 

Can call other servers?

Whether group's users can schedule multiserver meetings.

No

Yes/No

 

Ask for profile password?

Whether an invitee who was outdialed must provide a profile password before being admitted into the meeting.

Yes

Yes/No

 

Digit translation table

Translation table number to use for all outdials made by group's users. 16 translation tables are available. Default translation table is 0.

Your installation partner will work with you to configure these tables, as needed.

Yes

Yes/No

 
Meeting Preferences

Entry announcement

Announcement used when users enter meetings.

Beep+
Name

Beep only/
Beep+Name/
Silent

 

Departure announcement

Announcement used when users leave meetings.

Beep+
Name

Beep only/
Beep+Name/
Silent

 

End of mtg announcement

Whether the system announces the meeting will end in a set number of minutes.

For reservationless meetings, this parameter is not used. This announcement is not played for reservationless meetings.

Yes

Yes/No

 

Mtg extension announcement

Whether the system announces the meeting is extended by a set number of minutes.

For reservationless meetings, this parameter is not used. This announcement is not played for reservationless meetings.

No

Yes/No

 

Screened entry?

Whether meetings scheduled by this group require a meeting participant (already in the meeting) to admit people who try to join the meeting. (People wanting to enter are not admitted automatically.)

No

Yes/No

 

Skip pre-meeting options?

Whether meetings scheduled by this group's users use the Short Menu feature. Eliminates meeting ID confirmation, roll call, and agenda.

No

Yes/No

 

Disable roll call?

Whether meetings scheduled by this group's users may request roll call feature during a meeting.

Recommended: Yes when, for example, competitors could call into a meeting, meetings require caller anonymity, or you schedule large meetings.

Yes

Yes/No

 

Password required?

Whether by default meetings scheduled by this group's users require a password.

When Yes, the person who starts a reservationless meeting that is organized by this group's users can choose to create a password for the meeting. When No, the person who starts the meeting does not create one.

No

Yes/No

 

Who can attend?

Who can attend meetings scheduled by this group's users. For reservationless meetings, this parameter is not used. Anyone can attend reservationless meetings.

Anyone

Anyone/
MeetingPlace Users/
Invited Guests

 

Allow Internet access?

When the Cisco Unified MeetingPlace system is configured with a web-conferencing server in the DMZ and another behind the DMZ. When Yes, the Web portion of the meeting is held on the server in the DMZ and can be accessed by anyone. When No, the Web portion of the meeting is held on the server behind the DMZ and can be accessed only by users on the company's intranet.

No

Yes/No

 

Allow Internet Access for Reservationless

When Yes, the Web portion of reservationless meetings is held on the server in the DMZ and can be accessed by anyone. When No, the Web portion of reservationless meetings is held on the server behind the DMZ and can be accessed only by users on the company's intranet.

Yes

Yes/No

 

Lecture mtg attend sttgs

For lecture-style meetings scheduled by this group's users, the way in which listen-only participants are admitted.

When Admit as listeners and Start callers in waiting room, participants listen to music on hold until meeting is called to order. When Start mtg with floor open, participants can talk until meeting is called to order. When Reservationless mtg, lecture-style meetings scheduled by this group become reservationless meetings.

Admit as listeners

Admit as listeners/
Start callers in waiting room/
Start mtg with floor open/
Reservationless mtg

 

Host Meetings with

Whether the user will see the full meeting room or just the participant list when joining web meetings.

Full Meeting Room (if there are web port licenses available.)

Full Meeting Room/
Participant List

 

Restrictions

Scheduling restriction

Scheduling limits placed on this group's users.

When Unrestricted, users may schedule unlimited number of meetings; When Cannot Schedule, users can schedule no meetings; When Near Term Mtg Limit, users may schedule the specified number of meetings within the next six hours.

Un-
restricted

Unrestricted/
Cannot Schedule/
Near Term Mtg Limit (Numeric—
0 to 50*)

 

Use reservationless?

Whether to allow users in this group to use the reservationless meeting feature.

Yes

Y/N

 

Max mtg length (min)

Maximum number of minutes for which this group's users can schedule meetings.

240

Minimum 2; maximum is Max Mtg Length (Scheduling Parameters)

 

Max # of attachments

Maximum number of attachments allowed for meetings scheduled by this group's users.

10

Numeric—
0 to 30*

 

Sched only on home server?

Whether meetings for users in this group are restricted to the home server.

No

Read-only

 

Sched only on NS home site?

Whether meetings for users in this group are restricted to the home site.

Yes

Read-only

 

Max # teams allowed

Number of teams this group's users can create.

0

Numeric—
0 to 10,000*

 

Can chg mtg ID via phone

Whether this group's users may assign vanity IDs for meetings they schedule by phone.

This field is available only when Allow Vanity Meeting IDs (in System Parameters) is set to Yes.

Yes

Yes/No

 

Allow video scheduling?

Whether this group's users can schedule meetings with video.

No

Yes/No

 
Sending Notifications

Enabled for this mtg?

Whether this group's users send notifications for meetings.

For reservationless meetings, notifications are not sent.

Yes

Yes/No

 

Include attachments?

Whether this group's users send attachments as part of their notifications.

No

Yes/No

 

Priority

Priority of notifications for this group's users.

Normal

Low/Normal/
Urgent

 

Send if mtg changes?

Whether to send notifications when something changes in meetings (such as the time, date, password, or meeting ID), or when a message or attachments are added or deleted.

No

Yes/No

 

Include participant list?

Whether this group's users send a list of names of meeting participants as part of their notifications.

No

Yes/No

 

Include password?

For secure meetings where a password is specified, whether this group's users include the password in notifications.

No

Yes/No

 
Receiving Notifications

Enable to receive?

Whether this group's users receive notifications about meetings they are invited to (if meeting scheduler sends them).

No

Yes/No

 

Include attachments?

Whether this group's users receive attachments as part of meeting notifications.

No

Yes/No

 

Type of e-mail system

E-mail system used by this group's users. (See Table 5-6 after this worksheet.)

None

None/cc:Mail/
Lotus Notes/
Microsoft Mail/
Microsoft Exchange/
Qualcomm Eudora/
Netscape Messenger/
Other

 

Preferred delivery method

Notification delivery method for this group's users.

None

None/E-mail

 

Alternate delivery method

Alternative notification delivery method to use if the preferred method fails.

None

None/E-mail

 
Attending Meetings

Method of attending

This group's users' preferred method of joining meetings.

User will call in

User will call in/
Have system call user/
Have system page user/
Do not reserve space for user/
Have system find user

 

First search method

First number the system tries to reach users in this group.

None

None/Main/
Alternate/Pager

 

Second search method

Second number the system tries to reach users in this group.

None

None/Main/
Alternate/Pager

 

Third search method

Third number the system tries to reach users in this group.

None

None/Main/
Alternate/Pager

 

Type of pager

Type of pager service used by this group's users.

None

None/
Direct Dial/
Non Direct Dial

 

Pager phone number

Pager phone number of this group's users.

Direct Dial— 32-digit pager number/
Non Direct Dial—user's pager access code (PIN)

 
Q&A Meetings

Off at mtg startup?

Whether to turn on Q&A Meetings feature for this group's users at meeting startup.

No

Yes/No

 

Notify attendees about Q&A?

Whether to describe Q&A feature to this group's users when they attend conferences.

No

Yes/No

 

Q&A introduction

How to announce attendees being placed on the floor in meetings this group's users schedule.

Beep+
Name

Beep only/
Beep+Name/
Silent

 

Q&A departure

How to announce attendees being removed from the floor in meetings this group's users schedule.

Beep

Beep only/
Beep+Name/
Silent

 

Automatically ask next question?

Whether to automatically promote next waiting attendee to the floor in meetings this group's users schedule.

No

Yes/No

 

More than one question per site?

Whether to allow attendees in meetings scheduled by this group's users to ask more than one question at a time.

When Yes, this group's users may ask up to five questions.

No

Yes/No

 

Tell my position in line?

Whether to tell attendees in meetings scheduled by this group's users their current position in line.

No

Yes/No

 

Disable floor warning prompt?

Whether to tell attendees in meetings scheduled by this group's users they are next to ask a question (or speak) on the floor.

No

Yes/No

 
Video Meetings

Endpoint bandwidth

Bandwidth to use when connecting to VoIP. Endpoint connections are made based on the default bandwidth. (Guest connections are established with the default guest bandwidth.)

384K

128/256/384/512/758/1472/1920 kbps

 

Run meetings on video MCU only?

This value determines how the checkboxes in the Web Scheduling page are configured by default. If this is set to Yes, the web scheduling page initially has the video checkbox checked and the audio+web checkbox unchecked. The meeting scheduler can override the settings.

No

Yes/No

 

Attend preference for video prof.

For video profiles, whether the preference is for Cisco Unified MeetingPlace to automatically outdial the video end point or for the end point to dial in to meetings.

Dial-in

Dial in/Outdial

 

Flex Fields

Profile flex field 1

Profile field customized with your business information.

 

Profile flex field 2

Profile field customized with your business information.

 

Profile flex field 3

Profile field customized with your business information.

 

Profile flex field 4

Profile field customized with your business information.

 

Profile flex field 5

Profile field customized with your business information.

 

Profile flex field 6

Profile field customized with your business information.

 

Profile flex field 7

Profile field customized with your business information.

 

In Table 5-6, for the Type of E-mail System field, choose the value that corresponds to the e-mail system installed at your company.

Table 5-6 Choices for Type of E-mail System Field 

E-Mail System
Choose

cc:Mail

cc:Mail

IBM Lotus Notes

Lotus Notes

Microsoft Mail

Microsoft Mail

Microsoft Exchange

Microsoft Exchange

SMTP

Microsoft Mail, Qualcomm Eudora, Netscape Messenger

Other MAPI-compliant mail systems

Microsoft Mail


Worksheet 5-18: User Profiles

A user profile identifies the user to the Cisco Unified MeetingPlace system and defines the type of system access a user has.

For Options and Field Size values, in most cases the numeric and alphanumeric ranges given are the number of acceptable digits or characters for the field. (For example, Numeric—0 to 9 means that the field accepts any number between 0 (or nil) and 999999999.) Ranges with an asterisk (*) mean that the field accepts an actual number that falls within that range. (For example, Numeric—1 to 32767* means that the field accepts the value 3102 but not 32769.)

Field
Description
Default
Options and Field Size
Value
Identification

First name

This user's first name. Used for reporting and workstation display.

Alphanumeric—1 to 17

 

Last name

This user's last name. Used for reporting and workstation display.

Alphanumeric—1 to 17

 

User ID
(workstation access)

This user's Cisco Unified MeetingPlace ID. (Used from a workstation.) This is the key used for alphabetical sorting in the database and for scheduler identification in reports.

Recommended: Same as the network or e-mail login.

Alphanumeric—1 to 17

 

User password

Password this user uses to log in to Cisco Unified MeetingPlace from a workstation.

Alphanumeric—1 to 11

 

Last changed

Date the user password was last changed.

System-defined field

 

Profile number
(voice access)

Number that identifies this user profile. Used to connect to Cisco Unified MeetingPlace from a touch-tone phone.

Recommended: User's phone extension or voice-mail number.

Numeric—1 to 17

 

Profile password
(voice access)

This user's Cisco Unified MeetingPlace phone password.

Set this as a temporary default password. Users must change this to a personalized password when they first log in to Cisco Unified MeetingPlace.

Alphanumeric—1 to 11

 

Last changed

Date the profile password was last changed.

System-defined field

 

Profile active?

Whether this user profile is an active Cisco Unified MeetingPlace user. Only active users can log in to their profiles. Inactive users who try to log in are transferred to the attendant.

Group Default

Yes/No/Locked/
Group Default

 

Profile type

Whether this profile represents a user or a video terminal.

Group Dflt

User/Video Terminal/
Group Dflt

 

Type of user

Classification (user type) of this user.

End User

End User/Contact/
Attendant/System Mgr

 

Group name

Name of group (if any) to which this user belongs.

System

Alphanumeric—0 to 17

 

Phone number

Phone number that Cisco Unified MeetingPlace calls to reach this user (for example, to add this user to a meeting).

PBX access codes are not required. Allowed characters:
( ) , - " " space

Numeric—0 to 32

 

Alternate phone number

Alternative phone number that the system calls to reach this user (for example, to add this user to a meeting).

PBX access codes are not required. Allowed characters:
( ) , - " " space

Numeric—0 to 32

 

Pager phone number

Pager number of this user.

Group Default

Direct Dial—32-digit pager number/
Non Direct Dial—user's pager access code (PIN)

 

Type of pager

Type of pager service this user uses.

Group Default

None/
Direct Dial/
Non Direct Dial/
Group Default

 

Note If a user group is assigned to a profile, the following fields (excluding e-mail address fields) are supplied by the User Groups settings.

User ID of contact

User ID of the contact or attendant who supports this user (and has completed the contact/attendant training).

Alphanumeric—0 to 17

 

Internet e-mail address

User's Internet e-mail address. This address is used when someone is browsing meetings through Cisco Unified MeetingPlace web and requests to send mail to the meeting scheduler.

 

Time zone

Time zone of location in which this user usually does business.

Recommended: Time zone of user's location.

Set guest profile time zones to location of the Cisco Unified MeetingPlace system.

Group Default

Time Zone Name/
Group Default

 

Language

User's selected language.

Meetings scheduled by this user default to the selected language.

English (USA)

English (USA)/
Other installed language

 

Abbreviated prompts?

Whether the system plays abbreviated prompts when this person calls the system.

If this user belongs to a user group, enter a value only when it differs from the group value.

Group Default

Yes/No/Group Default

 

Billing code

A code for generating billing reports. Can be based on your company's internal conventions (for example, department codes).

Group Default

Alphanumeric—
0 to 17/
Group Default

 

Default mtg category

Meeting category assigned to meetings this user schedules.

Group Default

Selected name/
Group Default

 

Scheduling home server

The local server for this user.

0

Read-only

 
MeetingNotes Defaults

Able to record mtgs?

Whether this user can record meetings. Only the system administrator can change this field's value.

Group Default

Yes/No/Group Default

 

Record meeting?

Whether by default meetings scheduled by this user are recorded.

If this user belongs to a user group, enter a value only when it differs from the group value.

Group Default

Yes/No/Group Default

 

Who can access

Who can request attachments and listen to meetings recorded by this user.

When None, recorded meetings and their attachments must be manually posted for others to hear.

Group Default

None/Anyone/
MeetingPlace Users/
Invited Users/
Group Default

 

Auto-start recording?

For meetings scheduled to be recorded, whether by default recording starts automatically when second participant enters a meeting.

Group Default

Yes/No/Group Default

 

Attachment access ordering

Order in which users hear a list of attachments.

Group Default

Play most recent first/
Play in order submitted/
Group Default

 

Display mtg to everyone?

Whether by default to allow Cisco Unified MeetingPlace web guests to view meetings.

Group Default

Yes/No/Group Default

 

Display Meeting to Everyone for Reservationless

Whether by default to allow Cisco Unified MeetingPlace web guests to view reservationless meetings.

Group Default

Yes/No/Group Default

 
Outdial Meeting Defaults

Can call out from mtgs?

Whether a user can dial out from meetings.

To prevent guests from outdialing from within meetings, set this parameter to No in the guest profile.

Group Default

Yes/No/Group Default

 

Can schedule guest outdial mtgs?

Whether this user can schedule meetings that allow guests to join the voice conference by web. This parameter is enabled only if this user's profile has outdial privileges.

When No, the Allow Outdials to Guests From Web parameter is disabled for this user. When Yes, user can change Allow Outdials to Guests From Web setting for individual meetings.

Group Default

Yes/No/Group Default

 

Max outdials per meeting

How many outdials this user may initiate from within one meeting.

Note This field limits only the number of times this user can outdial from a meeting by pressing #3. It does not restrict any other method of outdialing.

Group Default

Numeric—0 to 500/
Unrestricted/
Group Default

 

Can call other servers?

Whether this user may schedule multiserver meetings.

Group Default

Yes/No/Group Default

 

Ask for profile password?

Whether outdialed invitees must enter a profile password to join meetings.

Group Default

Yes/No/Group Default

 

Digit translation table

Digit translation table to use for all outdials initiated by this user.

16 translation tables are available. Default translation table is 0. Your customer support representative will work with you to configure these tables, as needed.

Group Default

Numeric—0 to 15*/
Group Default

 
Meeting Preferences

Entry announcement

Announcement used when this user enters meetings.

Group Default

Beep only/
Beep+Name/
Silent/
Group Default

 

Departure announcement

Announcement used when this user leaves meetings.

If this user belongs to a user group, enter a value only when it differs from the group value.

Group Default

Beep only/
Beep+Name/
Silent/
Group Default

 

End of mtg announcement

Whether the system announces that the meeting will end in a set number of minutes.

For reservationless meetings, this parameter is not used. This announcement does not play in reservationless meetings.

If you are upgrading your system, this field defaults to the previous setting. New systems default to Yes.

Yes

Yes/No/Group Default

 

Mtg extension announcement

Whether the system announces that the meeting is extended by a set number of minutes.

For reservationless meetings, this parameter is not used. This announcement does not play in reservationless meetings.

Yes

Yes/No/Group Default

 

Screened entry?

Whether meetings scheduled by this user require a meeting participant (already in the meeting) to admit people who try to join the meeting. (People who want to enter are not admitted automatically.)

If this user belongs to a user group, enter a value only when it differs from the group value.

Group Default

Yes/No/Group Default

 

Skip pre-meeting options?

Whether meetings scheduled by this user use the short menu feature, which eliminates the meeting ID confirmation, roll call, and agenda.

Group Default

Yes/No/Group Default

 

Disable roll call?

Whether this user can request the roll call feature during meetings.

Recommended: Yes when, for example, competitors could call into a meeting, meetings require caller anonymity, or you schedule large meetings.

Group Default

Yes/No/Group Default

 

Password required?

Whether by default meetings scheduled by this user require a password.

If this user belongs to a user group, enter a value only when it differs from the group value.

When Yes, the person who starts a reservationless meeting that is organized by this user can choose to create a password for the meeting. When No, the person who starts the meeting does not create one.

Group Default

Yes/No/Group Default

 

Who can attend

Who can attend meetings scheduled by this person.

For reservationless meetings, this parameter is not used. (Anyone can attend reservationless meetings.)

Group Default

Anyone/
MeetingPlace Users/
Invited Users/
Group Default

 

Allow Internet access?

When the system is configured with a web-conferencing server in the DMZ and another behind the DMZ. When Yes, the web portion of the meeting is held on the server in the DMZ and can be accessed by anyone. When No, the web portion of the meeting is held on the server behind the DMZ and can be accessed only by users on the company's intranet.

No

Yes/No/
Group Default

 

Allow Internet Access for Reservationless

When Yes, the web portion of reservationless meetings is held on the server in the DMZ and can be accessed by anyone. When No, the web portion of reservationless meetings is held on the server behind the DMZ and can be accessed only by users on the company's intranet.

Yes

Yes/No/Group Default

 

Lecture mtg attend sttgs

For lecture-style meetings scheduled by this user, the way in which listen-only participants are admitted.

When Admit as listeners and Start callers in waiting room, participants listen to music on hold until meeting is called to order. When Start mtg with floor open, participants can talk until meeting is called to order. When Reservationless mtg, lecture-style meetings scheduled by this user become reservationless meetings.

Group Default

Admit as listeners/
Start callers in waiting room/
Start mtg with floor open/
Reservationless mtg/
Group Default

 

Host Meetings with

Whether the user will see the full meeting room or just the participant list when joining web meetings.

Full Meeting Room (if there are web port licenses available.)

Full Meeting Room/
Participant List

 

Restrictions

Scheduling restriction

Scheduling limits placed on this user.

When Unrestricted, users may schedule unlimited number of meetings; When Cannot Schedule, users can schedule no meetings; When Near Term Mtg Limit, users may schedule the specified number of meetings within the next six hours.

Group Default

Unrestricted/
Cannot Schedule/
Near Term Mtg Limit Numeric—0 to 50*/
Group Default

 

Use reservationless?

Whether this user may use reservationless meetings.

Group Default

Yes/No/Group Default

 

Max mtg length (min)

Maximum number of minutes for which this user can schedule meetings.

Group Default

Minimum 2; maximum is Max Mtg Length (Scheduling Parameters)/
Group Default

 

Max # of attachments

Maximum number of attachments that can be attached to a meeting scheduled by this user.

Group Default

Numeric—0 to 30*/
Group Default

 

Sched only on home server?

Whether meetings for this user are restricted to the home server.

No

Read-only

 

Sched only on NS home site?

Whether meetings for this user are restricted to the home site.

Yes

Read-only

 

Max # teams allowed

How many teams this user can create.

0

Numeric—0 to 10,000*/
Group Default

 

Can chg mtg ID via phone

Whether this user may assign vanity IDs for meetings scheduled by phone.

This field is available only when Allow Vanity Meeting IDs (in System Parameters) is set to Yes.

Yes (same as User Groups setting)

Yes/No

 

Allow video scheduling?

Whether this user can schedule meetings with video.

Group Default

Yes/No/Group Default

 
Sending Notifications

Enabled for this mtg?

Whether meeting scheduler sends notifications for meetings when this user schedules meetings.

For reservationless meetings, notifications are not sent.

Group Default

Yes/No/Group Default

 

Include attachments?

Whether meeting scheduler sends attachments as part of notifications when this user schedules meetings.

Group Default

Yes/No/Group Default

 

Priority

Priority given to notifications sent by this user.

Group Default

Low/Normal/Urgent/
Group Default

 

Send if mtg changes?

Whether notifications are sent when something changes in a meeting (such as the time, date, password, or meeting ID), or when a MeetingMessage or attachments are added or deleted.

Group Default

Yes/No/Group Default

 

Include participant list?

Whether to send names of meeting participants as part of notifications.

Group Default

Yes/No/Group Default

 

Include password?

For secure meetings where a password is specified, whether scheduler includes the password in notifications when this user schedules meetings.

Group Default

Yes/No/Group Default

 
Receiving Notifications

Enable to receive?

Whether this user receives meeting notifications (if meeting scheduler sends them).

Group Default

Yes/No/Group Default

 

Include attachments?

Whether this user receives attachments as part of meeting notifications.

Group Default

Yes/No/Group Default

 

E-mail address

This user's e-mail address.

Alphanumeric—
0 to 255*

 

Type of e-mail system

E-mail system used by this user. (See Table 5-7.)

Group Default

None/cc:Mail/
Lotus Notes/
Microsoft Mail/Microsoft Exchange/
Qualcomm Eudora/
Netscape Messenger/
Other/
Group Default

 

Preferred delivery method

The method by which this user receives notifications.

Group Default

None/E-mail/
Group Default

 

Alternative delivery method

Alternative method by which this user receives notifications, if the primary method fails.

Group Default

None/E-mail/
Group Default

 
Attending Meetings

Method of attending

Method by which this user is contacted to join meetings.

Group Default

User will call/
Have system call user/
Have system page user/
Do not reserve space for user/
Have system find user/
Group User

 

Ways to find user

Order in which the system calls this user to join meetings.

For this feature to work, the Method of Attending field value must be Have system find user.

None

None/Main/Alternative/
Pager (in any order)/
Group Default

 
Q&A Meetings

Off at mtg startup?

Whether to turn on Q&A Meetings feature for this user at meeting startup.

No (same as User Groups setting)

Yes/No/Group Default

 

Notify attendees about Q&A?

Whether to describe Q&A feature to this user when attending conferences.

Group Default

Yes/No/Group Default

 

Q&A introduction

How to announce attendees placed on the floor in meetings this user schedules.

Group Default

Beep only/
Beep+Name/Silent/
Group Default

 

Q&A departure

How to announce attendees being removed from floor in meetings this user schedules.

Group Default

Beep only/
Beep+Name/Silent/
Group Default

 

Automatically ask next question?

Whether to automatically promote the next waiting attendee to floor in meetings this user schedules.

Group Default

Yes/No/Group Default

 

More than one question per site?

Whether to allow attendees in meetings scheduled by this user to ask more than one question at a time.

When Yes, participants may ask up to five questions.

Group Default

Yes/No/Group Default

 

Tell my position in line?

Whether to tell attendees in meetings scheduled by this user their current position in line.

Group Default

Yes/No/Group Default

 

Disable floor warning prompt?

Whether to tell attendees in meetings scheduled by this user they are next to ask a question (or speak) on the floor.

Group Default

Yes/No/Group Default

 
Video Meetings

Endpoint bandwidth

Bandwidth to use when connecting to VoIP. Endpoint connections are made based on the default bandwidth. (Guest connections are established with the default guest bandwidth.)

256K

128 kbps/
256 kbps/
384 kbps

 

Endpoint address

Preferred endpoint address for this user. This can be a phone number, SIP address, or H.323 or H.320 endpoints.

 

Run meetings on video MCU only?

Meeting is entirely on video MCU (ad-hoc participants not allowed to join).

Group Default

Yes/No/Group Default

 

Attend preference for video prof.

Attend preference for video terminal profiles.

Group Default

Call_In/Dial_Out/Group Default

 

Video Terminal Name

Video terminal name.

Alphanumeric—0 to 64

 

Video Terminal ID

Video terminal ID.

Alphanumeric—0 to 32

 

Video Terminal Classification

Video terminal classification.

Alphanumeric—0 to 64

 

Flex Fields

Profile flex field 1

Profile fields customized with your business information.

 

Profile flex field 2

Profile fields customized with your business information.

 

Profile flex field 3

Profile fields customized with your business information.

 

Profile flex field 4

Profile fields customized with your business information.

 

Profile flex field 5

Profile fields customized with your business information.

 

Profile flex field 6

Profile fields customized with your business information.

 

Profile flex field 7

Profile fields customized with your business information.

 

In Table 5-7, for the Type of E-mail System field, choose the value that corresponds to the e-mail system installed at your company.

Table 5-7 Choices for Type of E-mail System Field 

E-Mail System
Choose

cc:Mail

cc:Mail

Microsoft Mail

Microsoft Mail

IBM Lotus Notes

Lotus Notes

Microsoft Exchange

Microsoft Exchange

SMTP

Microsoft Mail, Qualcomm Eudora, Netscape Messenger

Other MAPI-compliant mail systems

Microsoft Mail