BW-SAConferenceServerModule9-R120

7/28/2019 BW-SAConferenceServerModule9-R120

1/252

BroadWorks SystemAdministration

Module 9: Conferencing Server

Release 12 Version 1

May 2005


2/252

249 2005 BroadSoft, Inc. Proprietary and Confidential; Do Not Copy, Duplicate, or Distribute

Module 9 Objectives

At the end of th is module, you wi ll be able to:

Identify Conferencing Server featuresConfigure the Conferencing Server


3/252


Conferencing Server

Appl ication Server

Conference Server

SIP

SIP

Conference Server

SIP

SIP

SIP

Appl ication ServerAppl ication Server

Conference ServerConferencing Server

SIP

SIP

Conference ServerConferencing Server

SIP

SIP

RTP

Conferencing Server

Functions

As conference calls are initiated from IP phones, the Application Server brokers delivery toan appropriate Conference Server in the network based on user and service profiles.

The Application Server remains in the call in order to provide centralized fault, accounting

and performance metrics.


4/252


Conferencing Server Features

Audio and web conferencing

Scheduled, recurring, reservation-less, and ad-hoc

Meet-me dial-in numbersWeb collaboration scheduled, recurring

Share Microsoft PowerPoint, Excel, and Word files

Secure SSL and password protection

Web brow ser viewable, no client required

Moderator contro lShare Microsoft PowerPoint, Excel, and Word files

Dial-out capabilit y

Mute, hold, drop, and add participants

DTMF and web portal interfaces

In-call functions

Roll call, hand raising, optional leaderPIM integration

Automated e-mail invi tat ions and Out look calendar entr ies


5/252


Conferencing Server Features

Reporting

Web-based reportingDepartment and project codes

RecordingRecording and playback of individual conferences

Access code generationAutomat ic , pre-ass igned, or user-defined


6/252


Outdialing

INVITE

200 OK

200 OK

-

2-way media

NOTIFY Service info-

BYE

AS cu ts CDR

1) Collect conference code

2) Send service info event to AS

-

App licat ion

Server

Conferencing

Server

INVITE

ACK

ACK

200 OK

BYE

200 OK

200 OK


7/252


Conferencing Server Configuration Steps

Configuration steps:

1. Configure TCP/IP settings.

2. Configure and perform data replication.

3. Configure system settings

4. Enter proxies.

5. Update voice prompts.

6. Configure prompt sets.

7. Configure Music-On-Hold settings .

8. Install digital certificate.

9. Add a remote s ite.

10. Configure stacking.

11. Edit DAS rules.12. Change administrators password.


8/252


Configuration Menu


9/252


Configure TCP/IP Settings

Primary Conferencing Server


10/252


Configure Data Replication


To display this web page, select the Configuration menu and thenData Replication.


11/252


Perform Data Replication


Data Replication

Once the Data Replication configuration is complete, ensure thatData Replication isoperating. You should see the log shown on both servers. Display this log by selectingthe Monitoring menu and then Data Replication.

Replicate Data from Primary to Secondary Conferencing Server

For a fresh install on the secondary Conferencing Server:

1. From the Data Replication web page on the primary Conferencing Server, clickReplicate.

2. Once complete, to verify that replication was performed successfully list the users oneach server. To do this, select the Provisioning menu and click List Users. The list foreach server should be the same.

3. If there is no bridge on the primary Conferencing Server, add one and verify that the datadisplays on both Conferencing Servers. Then delete the bridge and ensure that the datais removed from both Conferencing Servers.


12/252


System Configuration

System Configuration

To establish the system configuration:

1. Select System Options.

2. Type information in each of the fields and click Save.

International Dialing Prefix: The digits used before dialing international calls from the site

where the Conferencing Server is installed.

National Dialing Prefix: The digit(s) required to make domestic toll calls.

Country Code: The country code of the location where the Conferencing Server isinstalled.

Webserver Admin Email: The e-mail address of the system administrator. Web Serveralerts are sent to this address.

Default Caller ID For Default Organization : The caller ID to be provided by theConferencing Server to the PSTN on outgoing calls.

Always Use per -Organization Default Caller ID: Indicates that this ID should always besent by the Conferencing Server to the PSTN on outgoing calls.

General A larm Email: The e-mail address of the person who is notified of general alarms

(typically the system administrator).General Alert Email: The e-mail address of the person who is notified of general alerts

(typically the system administrator).

Smart Mail Relay Host: The address of a smart mail relay host (if you are using one).

Executive Ports: The number of ports on the system you want to reserve for theexclusiveuse of high priority users.

continued


13/252

Immediate SMTP Logou t: Not applicable to standard AudioPresenter configurations. Youcan leave this blank.

SMTP Delete Mail: Not applicable to standard AudioPresenter configurations. You canleave this blank.

Max Legs Per Call: Used to limit the number of DS0s that can be included in a singleconference. The default maximum number of legs in a conference is 96.

Time Zone: The time zone of the location where the server is installed.

Port Usage Notification Threshold: If the number of concurrent ports being used on theserver reaches this number, an alert e-mail is sent to the e-mail address specified in theVoice Interface Alert e-mail field.

Conference URLs: Determines whether conference URLs (including those that are usedfor web presentations) are protected (encrypted) by SSL (https) or not (http). If you selecthttps, be sure that port 443 is open on any firewall you have deployed between theConferencing Server and the Internet.

Document Timeout: This is the length of time that uploaded documents remains on theConferencing Server after a call has expired. The server periodically deletes documentsthat are on the server past this timeout period.

User Login Timeout: The period of time of user inactivity before a users browser sessionwith the Conferencing Server is automatically terminated. The timeout should be set longenough so that users are logged out during a call but short enough so that an open session

does not constitute a potential security issue. This is because a session may remain openduring a conference call and that session may be used for call control at some point wellafter that call has started. The default is eight hours.

NOTE: If users check the box Automatically log me in on this computeron their sign-inpage, this timeout does not apply to that user on that computer.

Minimum IVR Access Code Length: This is the minimum number of digits required by theIVR in a valid conference access code. The factory default is seven.

Single Leg Timeout: Used to limit the time that a DS0 can be included in a singleconference.

Port Reservation Enabled: This setting allows users to specify the number of ports theyexpect to use when scheduling a one-time or recurring conference. If a conference isscheduled for a time when there are fewer than the port reservation number of ports free,

an Are you sure?warning message is displayed. The user may then choose to proceed,thus overbooking the system. Note that extensive use of ad-hoc calling may cause ports tobe unavailable even when they appeared free when the conference was scheduled.Similarly, use of reservation-less calls will cause more ports to appear reserved than willever be in use.

Reservation Warning Threshold: If the total number of scheduled ports hits this thresholdnumber, then the user receives feedback that the server may be full at that time. The usercan then schedule the conference for a time when the server will be less heavily loaded.

Use HTTPS Only: Used to specify the web server interface format.

Set Date/Time: The local date and time where the server is physically installed. This timeautomatically adjusts for daylight savings, based on the time zone setting (above).


14/252


Enter Proxies

Configure Proxies

To configure the proxies:

1. Select Proxies.

2. Type information in each of the fields. For installations usingVoIP connections to theConferencing Server, these fields are used to enter the UDP proxies. UDP over IP

adds the ability to address multiple endpoints within a single network node to IP. Anexample set of entries is as follows:

UDPUSERNAME=br oadwor ks@domai nname. com

UDPPHONENAME=

UDPAUTHNAME=anyt hi ng

UDPAUTHPW=anyt hi ng

UDPREALM=domai nname. com

UDPSERVERI P=xxx. yyy. zzz. www( proxy ser ver I P address)

UDPSERVERPORT=5061

UDPFI RSTEXTFI RST=

UDPLASTEXTFI RST=UDPFI RSTEXTSECOND=

UDPLASTEXTSECOND=

3. Click Save.


15/252


Configure Prompt Sets

Configure Prompt Sets

To add a new prompt set:

1. In the Prompt set file text box, specify the prompt set file. Click Browse to locate the seton your machine.

2. Custom prompts should be stored in 8 kHz, 8 bit, monophonic, mu-law format. In

network environments where A-law encoding is used, the internal prompts should still bestored in mu-law format.

3. In the Prompt set name dialog box, specify the name.

4. In the Language code dialog box, specify the language code for the prompt set.

5. Click Add new set to add the set or click Reset to revert to the default prompt set.


16/252


Configure Music on Hold Settings

Music On Hold

The Conferencing Server is shipped with a .WAV file that can be used to play music whilecallers are on hold. The system administrator can determine whether music is playedwhile users are on hold, and if so, which music is played. An alternative music-on-holdfile can be specified; however it should be stored in an 8 Kb/s, 8 bit, monophonic mu-law.WAV file format.

To configure Music On Hold Settings:

1. Click Music On Hold Settings.

2. Select the Enable Music on Hold checkbox to turn the feature on.

3. From the Music on Hold File Name drop-down menu, select the desired .wav file.

4. An alternative music-on-hold file can be specified. Click Browse to locate the file andthen click Upload to upload the file.


17/252


Install or Update Digital Certif icate

Digital Certif icate

The Conferencing Server allows the administrator to update or replace the digital certificateused by the web server during https (SSL) sessions or SIP (SSL) sessions. Thecertificate should be generated on a separate server by using standard tools and thespecific naming of the conferencing system for which the certificate is being generated.

To install or update digital certificate:

1. Click SSL Certificate.

2. In the Certificate text box, enter the path name of the file containing the certificate or clickBrowse to locate the file.

3. In the Key text box, enter the path name of the file containing the digital keycorresponding to the certificate or click Browse to locate the file.

4. Click Upload.


18/252


Install a New Licensing Certi ficate

Licensing Certificate

A license certificate controls the port capacity of a Conferencing Server. This certificate istied to the specific server hardware, and is loaded on the server at the time ofmanufacture. If you purchase a port upgrade from BroadSoft, or should there be a fieldrepair to your server hardware requiring a new license certificate, a BroadSoft supportrepresentative generates a new certificate. The following web screen is used to install

that new certificate on your server.

To install a new certificate:

1. Click Licensing.

2. In the Certificate text box, enter the path name of the file containing the certificate or clickBrowse to locate the file.

3. Click Upload.

4. In the Upload License file text box, enter the path name of the VMware license or clickBrowse to locate the file.

5. You must accept the terms of the Microsoft License Agreement in order to submit thelicense file for document sharing/Web presentation. Select I Accept.

6. Click Submit.


19/252


Add a Remote Site

Remote Site

BroadWorks Conferencing Servers can operate in a geographically distributed configuration.This allows conferences to take place across servers, with participants calling into thenearest server. This group of interoperating servers is called a federation.

To set up a federation of servers, each server must be aware of the other servers. You dothis by adding remote sites.

To add a remote site:

1. Click Remote Sites.

2. In the Hostname text box, enter the URL for the remote server.

3. In the Stack Name text box, enter the stack name for that server.

4. Click Add.


20/252


Configure Stacking


Stacking

BroadWorks Conferencing Servers can be interconnected in a stack for a linear expansion inuser and port capacity. To configure a stack, each servers secondary Ethernet port has tobe connected to an Ethernet switch, typically dedicated to the stack. If servers have trunkinterface cards, the Ethernet ports to those cards are also connected to the Ethernet switch.

There are two stacking methods:

Dynamic Stacking: This plug and play setting is the preferred configuration for stackswhere all servers are collocated. All servers connected via the IP Stack Backplane that isconfigured with identical Stack Names will automatically discover each other and form thestack. Since each servers secondary IP addresses will be set automatically based on itsconfigured (manually assigned) unique node ID, dynamic stacking requires that thesecondary Ethernet switch, the Stack Backplane, be dedicated to the stack with no outsideconnections.

Static Stacking: It is possible to statically configure a stacks IP addresses. Static stackingrequires that you specify the Name, Primary IP Address, and Backplane IP Address of allthe servers in the stack. You can statically configure up to 10servers in a single stack.Each server in the stack must be manually configured with these parameters. Also, forPSTN stacks, each PSTN gateway card has an Ethernet port, which will also require a staticaddress.

All servers in a stack must be configured with the same Stack Name and Cookie Domain.Great care should be taken in configuring the Cookie Domain correctly. If it is not configuredcorrectly, browsers will no longer be able to authenticate to the Conferencing Server, andthus the browser-based System Administration application will no longer be available. Whenthis happens, the Cookie Domain must be correctly configured using the ConsoleApplication.

You should also configure your DNS server to cycle among the servers (DNS Round Robin)in your stack when resolving the Stack Name, so that users can address the stack through asingle fully qualified domain name (FQDN).

Each server must have a unique Node ID. This Node ID will be used as the first two digits ofall conference access codes for this servers users.


21/252

After physically configuring the servers and setting up IP addresses and other server-specific settings, do the following:

1. Click Configuration.

2. Click Stacking.

The Stack Parameters dialog box displays. By default, theDynamic Stacking Method

displays.For Dynamic Stacking Method:

1. Select Dynamic.

2. In the Stack Name text box, enter the name (all servers use the same stack name).

3. In the Node ID text box, enter the node ID for the server you are configuring.

4. In the Cookie domain text box, enter the cookie domain name for the stack.

5. CheckApplication Serverand Media Serverto add those server types to the stack.

6. Click Save.

For Static Stacking Method:

1. Select Static stacking method.

2. In the Stack Name text box, enter the stack name (all servers use the same stack name).3. In the Node ID text box, enter the node ID for the server you are configuring.

4. In the Cookie Domain text box, enter the cookie domain name for the stack.

5. CheckApplication Serverand Media Serverto add those server types to the stack.

6. Specify the backplane IP address and the backplane netmask for the Local Server.

7. Specify name, primary IP, and backplane IP for the Stack 1 Server. Repeat this step foreach stack server (as needed).

8. Click Save.

NOTE: When multiple servers are configured as a stack, the systems administrators homepage shows the names of the servers in the stack. To select theserver you toadminister, click on the name of that server.


22/252


Edit DAS Rules

DAS Rules

To edit DAS Rules:

The server can be configured with rules to handle a broad range of call routing and dial planrequirements. These can be configured to handle international dialing, calling PBXextensions, and sophisticated handling of SIP call processing. The call routing rules arecalled DAS rules. DAS rules are a set of up to 20 UNIX regular expressions that areapplied to the users dialed digits. The rules are applied in order, one after the other.

The output of each rule is the input to the next one. The result is used as the dialeddigits to be processed by the Conferencing Servers call processing engine.

1. Click Configuration.

2. Click Advanced Settings.

3. Click Edit DAS Rules.

4. The Edit DAS Rules dialog box displays in the right pane.

5. Specify the DAS rule(s).

6. Click Save.


23/252

The following table shows examples of DAS rules and the functions they perform.

DAS rule Functions

s/\+(.*)/\1@/ When a digit string starts with a + it removes itand appends the AS FQDN (used for integratedmode).

s/x(.*)/\1/ When a digit string starts with an x, it removesit.

s/^\+1/1/ When a digit string starts with +1, it substitutesjust 1 (domestic US long distance call).

s/^\+x10(\d\d)/178189536\1/ If the resulting string starts with a +x10 followedby 2 digits (for four-digit extension dialing whereall extensions start with 10), it substitutes the fulloutward dial string 178189536 concatenated withthe 2 digits for the extension. This would beappropriate for dialing a four digit extension via aserver that is connected directly to the PSTN.

s/^\+/011/ If the resulting string starts with a + itsubstitutes 011 (international call).

s/^011011/011/ If the resulting string starts with 011011, then theinitial 011 is stripped.

s/^1666845(\d*)/\[email protected] If the resulting string starts with the string1666845 followed by any digits (an extension),then the result is an address comprising [email protected] (for routing VoIPcalls).


24/252


Change Administrators Password

Change Administrators Password

The system administrator currently logged in can change his or her password.

To change the administrators password:

1. Click Provisioning.

2. Click Change Current Admin Password.

3. The Change Current Admin Password dialog box displays in the right pane.

4. In theAdmin Password, enter the new password.

5. In the Confirm Admin Password, enter the password again.

6. Click Update.


25/25


Questions

Date post:	03-Apr-2018
Category:	Documents
Upload:	ochie-romero
View:	220 times
Download:	0 times

BW-SAConferenceServerModule9-R120

Documents