While reasonable efforts have been made to ensure that the information in this document is complete and accurate
at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and
corrections to the information in this document without the obligation to notify any person or organization of such
changes.
Documentation disclaimer
Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of
this documentation unless such modifications, additions, or deletions were performed by Avaya. End User agree to
indemnify and hold harmless Avaya, Avaya’s agents, servants and employees against all claims, lawsuits, demands
and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this
documentation, to the extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or
documentation(s) provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or
content provided on these sites and does not necessarily endorse the products, services, or information described or
offered within them. Avaya does not guarantee that these links will work all the time and has no control over the
availability of the linked pages.
Warranty
Avaya provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the
limited warranty. In addition, Avaya’s standard warranty language, as well as information regarding support for
this product, while under warranty, is available to Avaya customers and other parties through the Avaya Support
Web site: http://www.avaya.com/support
Please note that if you acquired the product from an authorized reseller, the warranty is provided to you by said
reseller and not by Avaya.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE,
HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE APPLICABLE TO ANYONE WHO DOWNLOADS,
USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA
AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL
AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE
AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE
SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN
AVAYA AUTHORIZED RESELLER, AND AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION
AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY
INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,
YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,
DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY
AS "YOU" AND "END USER"), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A
BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE
("AVAYA").
Copyright
Except where expressly stated otherwise, no use should be made of the Documentation(s) and Product(s) provided
by Avaya. All content in this documentation(s) and the product(s) provided by Avaya including the selection,
arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and
other intellectual property laws including the sui generis rights relating to the protection of databases. You may not
modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part,
including any code and software. Unauthorized reproduction, transmission, dissemination, storage, and or use
without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law.
Third Party Components
Certain software programs or portions thereof included in the Product may contain software distributed under third
party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain
portions of the Product ("Third Party Terms"). Information regarding distributed Linux OS source code (for those
Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party
Components and the Third Party Terms that apply to them is available on the Avaya Support Web site:
http://support.avaya.com/Copyright.
Trademarks
The trademarks, logos and service marks ("Marks") displayed in this site, the documentation(s) and product(s)
provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users
are not permitted to use such Marks without prior written consent from Avaya or such third party which may own
the Mark. Nothing contained in this site, the documentation(s) and product(s) should be construed as granting, by
implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission
of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-Avaya trademarks
are the property of their respective owners.
2 NN40011-022 Issue 1.2 BCM Rls 6.0
Meet Me Conferencing
Downloading documents
For the most current versions of documentation, see the Avaya Support. Web site: http://www.avaya.com/support
Contact Avaya Support
Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The
support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see
the Avaya Web site: http://www.avaya.com/support
Using the MeetMe Conferencing application, callers can establish a multi
party teleconference up to 18 participants for BCM50 systems, or 60
participants for BCM450 systems (up to 120 participants in multiple
conferences on BCM450 systems if a Capacity Expansion Card is installed).
The conferences can either be wholly internal or a mix of both internal and
external callers. Access for internal callers is via the use of F930, external
callers access the conference by calling a specified DDI number, alternately
by being transferred to a conference. One caller acts as the chairperson and
has additional powers to start, stop, secure, eject and control the conference.
Types of MeetMe Conference:
Internal: only accessed internally does not require access to a target
line, though outside parties can be added via transfer to application DN
which is DN 301 on a default system. Internally accessed via F930
using chairpersons DN as the meeting key.
Internal/External: can be accessed by both Internal and external
parties. Those dialing in from external locations dial a MeetMe
Conference DDI number setup by the system administrator. Internally
accessed via F930 using chairpersons DN as the meeting key.
Anyone can participate in a conference, but a BCM user must have
chairperson privileges to chair a conference.
6 NN40011-022 Issue 1.2 BCM Rls 6.0
Meet Me Conferencing
MeetMe Conferencing has a special directory number (application DN, to find
use F985) used to access the MeetMe Conferencing feature. Although you
can access a conference in several ways, the system administrator should
notify both internal and external conferencing users of the Meet Me
Conferencing DN.
Required Information
To setup a MeetMe Conference the system administrator will require the
following information:
Class of Service setting for required MeetMe conference (1-16
available).
Chairperson DN.
For external access a target Line with a DDI/DID Number.
NN40011-022 Issue 1.2 BCM Rls 6.0 7
Meet Me Conferencing
MeetMe Conferencing
Collate required MeetMe Conferencing details: Refer to the Setting up a MeetMe Conference section of this guide.
Configure a COS for the required MeetMe Conferencing user requirements: Refer
to the System Settings and COS Settings section of this guide.
Setup Chairperson DN under Active Sets: Refer to the Create a Conference Bridge for a chairperson section of this guide.
Type of
MeetMe
Conference
Setup target Line Details: Refer
to the BCM System Startup user
guide.
External
Internal
Test MeetMe Conference settings
prior to Conference
MeetMe Conference details now
available to be advertised for use
Configure Chairpersons personal settings: Refer to the Process for Configuring a
MeetMe Conference section of this guide.
Test MeetMe Confrence Web Portal by logging in
both a Chairperson and a Participant: refer to the
BCM MeetMe Conference Web Portal section of
this guide
Flow Chart
This flowchart depicts all relevant steps to setup and configure the MeetMe
conferencing feature.
8 NN40011-022 Issue 1.2 BCM Rls 6.0
Meet Me Conferencing
Setting up a MeetMe Conference
Accessing Meet Me Conferencing in Element Manager
1. How access the Business Element Manager application from the Start
Menu, navigate to Start, Programs, Avaya, Business
Communications Manager, Business Element Manager.
2. Alternatively, double-click on the Business Element Manager desktop
icon.
NN40011-022 Issue 1.2 BCM Rls 6.0 9
Meet Me Conferencing
3. You will be presented with the Element Manager interface.
4. Open the Network Elements folder and select the IP Address of the
BCM.
5. Enter the User Name of the BCM in the User Name field, by default this
is nnadmin. Then enter the Password in the Password field, by default
the password is PlsChgMe!. Click the Connect button.
10 NN40011-022 Issue 1.2 BCM Rls 6.0
Meet Me Conferencing
6. A warning screen will appear, read the warning and click OK.
7. You will be presented with the Element Manager interface.
8. Select the Configuration tab, open the Applications folder, and then
click on the MeetMe Conferencing.
NN40011-022 Issue 1.2 BCM Rls 6.0 11
Meet Me Conferencing
Attribute
Value
Description
Welcome
greeting Company
greeting ID
<Blank, or a
Company
Greeting
number 1-250>
Default: Blank
The Welcome greeting is played for external callers.
If blank, the system uses the standard greeting: "Welcome
to the Meet Me Conferencing Service."
Instead the administrator can select any existing Company Greeting under Callpilot to use as a Welcome greeting for
this service.
Maximum
chairperson
wait time
(min)
<1-120>
Default: 20
minutes.
The Wait Time is the amount of time that system resources
can be tied up waiting for a conference to start. Should the
chairperson fail to login within the allotted time limit, the
system informs participants and terminates the conference.
The limit is enforced on a per-participant basis. Thus timer
starts after the last person joins the conference.
Maximum
conference
continuation
time (min)
<1-999>
Default: 120
minutes.
This attribute works with the Allow Continue option in the
chairperson's COS.
If the Allow Continue option is enabled, the Maximum
Conference Continuation Time sets the limit to the amount
of time that system resources are used after the
chairperson has left the conference. When this limit
expires, the system gives participants a one minute
System Settings and CoS Settings
To access the system and COS settings within Element Manager:
Follow Configuration > Applications > Meet Me Conferencing >
Configuration to configure system and COS settings.
The system settings are global and apply to all MeetMe conferences on the
BCM. The COS service table has 16 COS ID‟s available. They are then
assigned to chairpersons DN under the chairpersons Active Set.
Note: that the Meet Me Conferencing COS is separate and distinct from the
Mailbox COS. The Meet Me Conferencing COS is assigned to a chairperson's
DN.
System Settings
12 NN40011-022 Issue 1.2 BCM Rls 6.0
Meet Me Conferencing
Attribute
Value
Description
warning and then disconnects them.
If the Allow Continue option is disabled, the conference
ends when the chairperson leaves the conference.
Maximum
conference
limit time
(hrs)
<1-24>
Default: 12
This attribute limits the amount of time that system
resources can be used continuously for a single
conference. It's purpose is to prevent a conference from
going on indefinitely if there are multiple abandoned lines.
The limit should be high enough not to impair most
conferences.
When this limit expires, the system gives participants a one
minute warning and then disconnects them.
Maximum
last
participant
limit time
(min)
<1-120>
Default: 20
minutes
This attribute limits the amount of time that system
resources can be tied up when the conference is reduced
to a single participant. It's purpose is to prevent an
abandoned line from tying up a port unnecessarily.
Note: Any value set higher than the Maximum Conference
Continuation Time is not effective, because the system
disconnects the conference when that limit is reached.
Authorization
check period
(days)
<1-365>
Default: 60
days.
This attribute controls the Authorization Check feature.
If 0, the feature is disabled; otherwise the chairperson must
change the PIN locally at least once during this period to
maintain access.
COS ID
<1-16>
The ID of the COS.
Name
<alphanumeric>
The name of the COS.
Max
Conference
Size
BCM450:<4-60>
BCM50:<4-18>
The largest number of participants (including the
chairperson) that the chairperson can host, subject to
resource availability.
Allow
QuickStart
<check box>
The QuickStart option allows the conference to start
without the chairperson.
If selected, the chairperson can enable or disable the
Quickstart feature in the chairperson administration
interface.
If cleared, the chairperson cannot enable the Quickstart
option. The Quickstart option is disabled and does not
appear in the chairperson administration interface.
Allow
Continue
<check box>
If selected, the chairperson can enable or disable the
Conference Continuation option. The Conference
Continuation option is configured in the chairperson
Class of Service Settings
NN40011-022 Issue 1.2 BCM Rls 6.0 13
Meet Me Conferencing
administration interface and during conference.
If cleared, the chairperson cannot enable the Conference
Continuation option. The option is disabled and does not
appear in the chairperson administration interface not
during conference.
Allow
Announce
Off
<check box>
The Announcement settings are Tones, Names, and Off.
The Off setting allows the chairperson to turn
announcements off.
If selected, the value Off is offered as an Announcement
setting within the chairperson administration menu and
during conference.
If cleared, the chairperson cannot change the
Announcement option to Off. The Announcement option
remains visible in the chairperson administration menu and
during conference, but off is not offered as a setting. The
Announcement option can be Tones or Names only.
Conf
Language
<drop-down
list>
The attribute specifies the language of the participant
entry/exit and warning voice prompts.
If Primary, the voice prompts play in the Primary language
set in the VoiceMail system properties.
If Alternative, the voice prompts play in the Alternative
language set in the VoiceMail system properties.
14 NN40011-022 Issue 1.2 BCM Rls 6.0
Meet Me Conferencing
Configuring a MeetMe Conference
Select the Configuration tab, open the Applications folder, and then click on
the MeetMe Conferencing.
Creating a Conference Bridge for a Chairperson
1. To configure a MeetMe conference, either edit or confirm the system
settings in the top half of the screen, under the Configuration tab.
Ensure that an appropriate Welcome greeting for the organisation has
been recorded from within CallPilot Auto Attendant as a company
greeting. Enter the Company Greeting ID in the Welcome Greeting – Company greeting ID field then continue through and confirm the
remainder of the Configuration settings.
For details of how to record a Company Greeting Please refer to the
CallPilot Auto-Attendant Guide.
NN40011-022 Issue 1.2 BCM Rls 6.0 15
Meet Me Conferencing
2. You can make changes to the COS table directly by clicking on the
table cells. You can change the Name, Maximum Conference Size(Up
to the available keycoded licenses for the feature), Allow QuickStart,
Allow Continue, Allow Announce Off, and Conference Language for
any COS.
a. COS ID cannot be changed.
b. To change the Name, double click the Name cell of the COS
you want to change.
c. To change the Maximum Conference Size, double click the
Maximum Conference Size cell of the COS you want to change.
d. To change the following click the checkbox of the COS you want
to change:
i. Allow QuickStart – With this option enabled, the conference
begins when the first participant arrives, default is disabled
ii. Allow Continue – With this option enabled the conference
can continue even once the chairperson has left, default is
disabled
iii. Allow Announce Off – controls whether the system
announces a participant on entering the conference
e. To change the Conference Language, double click the
Conference Language cell of the COS you want to change. Click
the drop down list. Select Primary or Alternate.
Note: View the Class of Service settings section for field definitions.
3. To configure the conference settings for a chairperson follow the
following procedures :
4. Click Configuration, Telephony, Sets, Active Sets, Line Access.
16 NN40011-022 Issue 1.2 BCM Rls 6.0
Meet Me Conferencing
5. Click the DN you want to make into a Conference Bridge.
6. Click the MeetMe Conferencing tab in the bottom panel.
7. Click Create MeetMe Conference Bridge... The Create MeetMe
Conference Bridge dialog box appears. Select the required Class of
Service and click OK.
NN40011-022 Issue 1.2 BCM Rls 6.0 17
Meet Me Conferencing
8. The selected Class of Service will be shown.
9. The user now has chairperson privileges. The system updates the
MeetMe Conferencing panel.
To give external callers access directly to the MeetMe Conference, they will
need to dial a DDI number which is assigned to a target line. This target line
will need to be assigned under CallPilot Auto Attendant Lines Administration.
(Refer to the Assigning a Line to MeetMe Conferencing section of this
guide).
18 NN40011-022 Issue 1.2 BCM Rls 6.0
Meet Me Conferencing
To Change the Chairperson's COS
1. Click Configuration, Telephony, Sets, Active Sets, Line Access.
2. Click the DN you want to change.
3. Click the MeetMe Conferencing tab in the bottom panel.
4. Click the Class of Service drop down list.
5. Select a new COS value.
6. The chairperson now has a new COS.
NN40011-022 Issue 1.2 BCM Rls 6.0 19
Loading...
+ 43 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.