Commissioning - Avaya Support

Nortel Media Application Server 6.0 for AS 5300

Commissioning

NN44470-301

Document status: StandardDocument issue: 01.03Document date: 04 March 2009Product release: Release 6.0Job function: Installation and CommissioningType: NTPLanguage type: English

Copyright © 2008-2009 Nortel Networks. All Rights Reserved.

LEGAL NOTICEThis document contains Nortel confidential and proprietary information. It is not to be copied, disclosed or distributed in any manner, in whole or in part, without Nortel’s express written authorization. While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice.

Nortel, the Nortel logo and the Globemark are trademarks of Nortel Networks.

All other trademarks are the property of their respective owners.

Nortel Media Application Server 6.0 for AS 5300Commissioning

NN44470-301 01.03 StandardRelease 6.0 04 March 2009

Copyright © 2008-2009, Nortel Networks

Contents

New in this release 6Features 6

MAS and AS 5300 integration 6MAS applications 6

Other changes 7

Introduction 8

Installation and commissioning work flow 9

MAS and AS 5300 integration 13Multiple MAS configuration 15Logical entity overview 16Duplex configuration for Co-resident Application Deployment (including Meet Me) 17Co-resident Application Deployment (excluding Meet Me) with a separate two-node

Meet Me configuration 18Dedicated Deployment 19Starting the MAS Management Console software 21Enabling TCP TLS and cipher on the MAS 22Importing a Certificate and Key on the MAS 23Importing a Trust Store 24Enable SOAP TLS 25Adding the Session Manager Service IP as a trusted node 26Enabling SNMP service on the MAS node 27Restarting the MAS platform 28Obtaining the MAS IP address 29Adding the MAS node to Network Data and Mtc in the AS 5300 System Management

Console 30Enrolling the MAS node in the Network Elements in the AS 5300 System

Management Console 31Confirming a newly enrolled MAS node 33Adding a Service Node 34Adding a Logical Entity 35Adding Applications as a service to a domain 36Adding applications as a routable services to a domain 37

- 4 -Contents




Obtain a keycode 38Accessing the Keycode Retrieval System 40Registering a new system with KRS 41Adding servers to KRS 42Generating a keycode 46

MAS Commissioning 51Configuring licensing 52Adding a SIP trusted node 53Deleting a SIP trusted node 54Adding a SIP route 55Deleting a SIP route 57Configuring a SIP route 58Configuring audio codec settings 60Configuring video codec settings 62Configuring digit relay settings 64Configuring media security options 67Configuring conference settings 69Configuring silence suppression 71

Configure continuous streaming 72Creating a local directory for the Directory Provider 73Configuring the RSS URL 74Configuring the SHOUTCast primary server 75Configuring the SHOUTCast backup server 76Adjusting the continuous streaming volume 77

Configure clusters 78Configuring clock synchronization using an SNTP time source server 79Configuring content stores for duplex configurations 80Configuring content stores for N-Way configurations on Node 1 and Node 2 82Configuring content stores for N-Way configurations on Node 3 to Node N 85Configuring a duplex controller peer ring 87Configuring a N-Way controller peer ring 89

Ad Hoc Conferencing commissioning 91Configuring Ad Hoc Conferencing parameters on the MAS platform 92Configuring the routable services information for the Ad Hoc Conferencing logical

entity 94

Announcements commissioning 95Configuring the Announcements parameters on the MAS platform 96Setting the locale (or language) of your announcements 97Placing announcement files on the MAS 98Configuring treatment routable services information for the Announcement logical

entity 100

- 5 -Contents




Configuring branding routable services information for the Announcement logical entity 103

Meet Me Conferencing commissioning 105Configuring Meet Me Conferencing parameters on the MAS platform 106Adding .wav files for wait music 109Creating an alias for Meet Me pooled entity 110Configure audio recording delivery for Meet Me Conferencing 111Configuring user-specific Meet Me Conferencing service data 112

Music on Hold commissioning 114Configuring the Music on Hold parameters on the MAS platform 115Placing music files on the MAS 116Configuring routable services information for the Music on Hold logical entity 118Enabling the Music on Hold application in the end user service packages 119

Unified Communications commissioning 120Configuring the Unified Communications parameters on the MAS Platform 122Creating a message retrieval alias for a Unified Communications pooled entity 124Creating express messaging aliases for Unified Communications pooled entity 125Adding a voice mail server host 126Adding a SIP voice mail server 127Provisioning voice mail user-specific data 128Provisioning Unified Communications service user-specific data 129

Common procedures 130Starting the MAS platform 131Stopping the MAS platform 132Restarting the MAS platform 133Locking the MAS platform 134Locking the MAS platform using Pending Lock 135Unlocking the MAS platform 136Locking MAS applications in the MAS console 137Locking MAS applications in the MAS Console using Pending Lock 138Unlocking MAS applications in the MAS Console 139Establishing a Remote Desktop connection 140Configuring SIP general settings 141Viewing SIP trusted nodes 144Configuring QoS settings 145




New in this releaseThe following sections detail what’s new in Nortel Media Application Server 6.0 for AS 5300 Commissioning (NN44470-301).

Navigation• Features (page 6)

• Other changes (page 7)

FeaturesSee the following sections for information about feature changes.

• MAS and AS 5300 integration (page 6)

• MAS applications (page 6)

MAS and AS 5300 integrationThe Media Application Server (MAS) 6.0 supports integration with the Application Server (AS) 5300. You must integrate the MAS with the AS 5300 to run applications such as Meet Me Conferencing and Unified Communications. For more information, see MAS and AS 5300 integration (page 13).

MAS applicationsThe MAS 6.0 for AS 5300 release supports the following applications.

• Ad Hoc Conferencing, see Ad Hoc Conferencing commissioning (page 91).

• Announcements, see Announcements commissioning (page 95).

• Meet Me Conferencing, see Meet Me Conferencing commissioning (page 105).

• Music on Hold, see Music on Hold commissioning (page 114).

• Unified Communications, see Unified Communications commissioning (page 120).

- 7 -New in this release

CommissioningNN44470-301 01.03 StandardRelease 6.0 04 March 2009

Copyright © 2008-2009, Nortel Networks Nortel Networks Confidential

Other changesThe MAS 6.0 documentation suite contains reorganized content from the MAS 5.1, 5.0, and 4.0 documentation suites.




IntroductionThis document describes how to commission and configure the Media Application Server (MAS) platform and all applications that you can install on the MAS.

Prerequisites• The MAS must be installed and the administration and security options

must be configured before you begin the MAS commissioning procedures in this document. For information, see Installation and commissioning work flow (page 9).

• For more information about the Provisioning Client and provisioning tasks (such as adding nodes, adding a logical entity, and adding nodes or logical entities to a domain), see Nortel AS 5300 Administration (NN42040-600), Nortel AS 5300 Security (NN42040-601) and Nortel AS 5300 Configuration (NN42040-500).

Navigation• Installation and commissioning work flow (page 9)

• MAS and AS 5300 integration (page 13)

• MAS Commissioning (page 51)

• Configure continuous streaming (page 72)

• Configure clusters (page 78)

• Ad Hoc Conferencing commissioning (page 91)

• Announcements commissioning (page 95)

• Meet Me Conferencing commissioning (page 105)

• Music on Hold commissioning (page 114)

• Unified Communications commissioning (page 120)

• Common procedures (page 130)




Installation and commissioning work flow

This section provides an overall work flow that you must follow to properly install and commission the Media Application Server (MAS) for the Application Server (AS) 5300 release. The following table outlines the installation and commissioning process.

Attention: You must complete the steps in the following table in the order provided. The MAS must be installed and you must complete the administration and security procedures before you being the MAS commissioning procedures in this document.

Step Document Prerequisites

1 Install the MAS. Nortel Media Application Server 6.0 for AS 5300 Installation (NN44470-300)

You must have completed the steps outlined in Installation and commissioning work flow part 1 (page 10).

2 Configure administration and security options on the MAS.

Nortel Media Application Server 6.0 for AS 5300 Administration and Security (NN44470-600)

You must have completed the steps outlined in Installation and commissioning work flow part 2 (page 11).

3 Commission the MAS. Nortel Media Application Server 6.0 for AS 5300 Commissioning (NN44470-301)

Complete the steps outlined in Installation and commissioning work flow part 3 (page 12).

- 10 -Installation and commissioning work flow




Installation and commissioning work flow part 1














MAS and AS 5300 integrationComplete the procedures in this section to integrate the Media Application Server (MAS) and the Application Server (AS) 5300.

Prerequisites• You must complete every procedure in this chapter on every MAS node in

your cluster.

• For detailed information about the AS 5300, refer to the AS 5300 documentation.

• You must create a domain on the AS 5300.

• You must assign an IPCM cluster if you want to provision IP clients.

• You must create users.

Navigation• Multiple MAS configuration (page 15)

• Logical entity overview (page 16)

• Duplex configuration for Co-resident Application Deployment (including Meet Me) (page 17)

• Co-resident Application Deployment (excluding Meet Me) with a separate two-node Meet Me configuration (page 18)

• Dedicated Deployment (page 19)

• Starting the MAS Management Console software (page 21)

• Enabling TCP TLS and cipher on the MAS (page 22)

• Importing a Certificate and Key on the MAS (page 23)

• Importing a Trust Store (page 24)

• Enable SOAP TLS (page 25)

• Adding the Session Manager Service IP as a trusted node (page 26)

• Enabling SNMP service on the MAS node (page 27)

• Restarting the MAS platform (page 28)

- 14 -MAS and AS 5300 integration




• Obtaining the MAS IP address (page 29)

• Adding the MAS node to Network Data and Mtc in the AS 5300 System Management Console (page 30)

• Enrolling the MAS node in the Network Elements in the AS 5300 System Management Console (page 31)

• Confirming a newly enrolled MAS node (page 33)

• Adding a Service Node (page 34)

• Adding a Logical Entity (page 35)

• Adding Applications as a service to a domain (page 36)

• Adding applications as a routable services to a domain (page 37)





Multiple MAS configurationThe following graphic provides the building blocks required for developing a multiple MAS configuration that has multiple applications installed.

Multiple MAS configuration building blocks





Logical entity overviewThe following graphic provides a graphical overview of the steps required to create a logical entity in the Provisioning Client on the AS 5300. For detailed information, see Adding a Logical Entity (page 35).

Logical entity overview





Duplex configuration for Co-resident Application Deployment (including Meet Me)

The duplex configuration for Co-resident Application Deployment (including Meet Me) is a configuration where five applications (Ad Hoc Conferencing, Announcements, Meet Me, Music on Hold, and Unified Communications) are installed on each node in the configuration. The following diagram is an example of a small system that contains two MAS nodes and two redundant AS 5300 nodes. In this example, Node 1 and Node 2 are in a duplex cluster configuration.

Duplex configuration for Co-resident Application Deployment (including Meet Me) example





Co-resident Application Deployment (excluding Meet Me) with a separate two-node Meet Me configuration

Co-resident Application Deployment (excluding Meet Me) with a separate two-node Meet Me is a configuration that includes four MAS applications (Ad Hoc Conferencing, Announcements, Music on Hold, and Unified Communications) installed in one cluster. The following is an example of a medium size system configuration. The four applications are installed on Node 1 and Node 2 in one cluster. Meet Me Conferencing is installed on Node 3 and Node 4 in a separate cluster.

Co-resident Application Deployment (excluding Meet Me) with a separate two-node Meet Me example





Dedicated DeploymentThe following graphic is an example of a Dedicated Deployment. The Dedicated Deployment example has the following clusters.

• Nodes 1 and 2 are a cluster dedicated to Unified Communications.

• Nodes 3 and 4 are a cluster dedicated to Ad Hoc Conferencing.

• Nodes 5 and 6 are a cluster dedicated to Announcements.

• Nodes 7 and 8 are a cluster dedicated to Music on Hold.

• Nodes 9 to 16 are a 7 + 1 cluster configuration dedicated to Meet Me Conferencing.





Dedicated Deployment example





Starting the MAS Management Console softwareUse this procedure to start the MAS Console.

Procedure steps

Step Action

1 Click Start > All Programs > Nortel Networks Media Server > Media Application Server Console.

OR

Double-click the Media Application Server Console icon on your desktop.

--End--





Enabling TCP TLS and cipher on the MASUse this procedure to enable the TCP TLS and cipher on the MAS.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Security > General.

2 In the General window, double-click Enable TCP TLS Transport.

3 In the Enable TCP TLS Transport Properties window, select Enabled in the Value list.

4 Click OK.

--End--

Variable definitions

Variable Value

Enable TCP TLS Transport If Enable TCP TLS Transport is enabled, TLS is used for all external TCP connections.

The default value is Disabled.

Attention: Check this parameter value and set to Enable.





Importing a Certificate and Key on the MASUse this procedure to optionally import a certificate and key on the MAS for security. A default certificate and key is configured when the MAS is installed.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Security > Internal Certificates.

2 In the Internal Certificates window, right-click Sip Tls.

3 Select Import Certificate and Key.

4 In the Import Certificate window, type default in the Password box.

5 Click Import.

6 In the Import Certificate window, locate the directory C:\certs.

7 In the C:\certs directory, select mcpdefault.b64.

8 Click Open.

9 On the Import Certificate window, click OK.

--End--





Importing a Trust StoreUse this procedure to optionally import a trust store on the MAS. A default staging certificate is configured when the MAS is installed.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Security > Trust Store.

2 Right-click Trust Store.

3 Select Import CA.

4 In the Import a CA window, type MCPDefault in the Friendly Name box.

5 Click Continue.

6 In the Import CA window, locate the C:\certs directory.

7 In the C:\certs directory, select mcpdefault.pem.

8 Click Open.

9 Click OK.

--End--





Enable SOAP TLSUse this procedure to enable SOAP TLS on the MAS.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Management > General.

2 In the General window, double-click Enable SOAP TLS Transport.

3 In the Enable SOAP TLS Transport window, select Enabled in the Value list.

4 Click OK.

5 Double-click Trusted SOAP Nodes.

6 In the Trusted SOAP Nodes Properties window, type the IP address of AS 5300 Provisioning Client in the Value box.

7 Click OK.

--End--


Variable Value

Enable SOAP TLS Transport If Enable SOAP TLS Transport is enabled, the SOAPServer will accept requests over TLS.


Trusted SOAP Nodes A list of trusted SOAP nodes separated by a semicolon (;).





Adding the Session Manager Service IP as a trusted nodeAdd the Session Manager Service IP as a trusted node in the MAS Console.

Prerequisites• For more information about restarting the MAS, see Restarting the MAS

platform (page 133).

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Signaling > SIP > Trusted Nodes.

2 Right-click Trusted Nodes.

3 Select New SIP Trusted Node.

4 In the Add SIP Trusted Node window, type the IP address of the Session Manager Service IP in the Host or IP box.

5 Click Add.

6 If you are finished making changes, restart the MAS Console.

--End--





Enabling SNMP service on the MAS nodeThe AS 5300 System Manager can request logs and events for reporting and troubleshooting purposes when the SNMP service is enabled on the MAS.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Management > General.

2 In the General window, double-click SNMP Delivery of Alarms via Traps.

3 In the SNMP Delivery of Alarms via Traps Properties window, in the Value list, select Enabled.

4 Click OK.

5 Double-click SNMP Delivery of Logs via Traps.

6 In the SNMP Delivery of Logs via Traps Properties window, in the Value list, select Enabled.

7 Click OK.

8 Double-click SNMP Community String.

9 In the SNMP Community String Properties window, in the Value box, type Public.

10 Click OK.

11 Double-click SNMP Element Manager Network Address.

12 In the SNMP Element Manager Network Address Properties window, in the Value box, type the network address and port number of the SNMP element manager.

Type the address in the format IPAddress:Port. For example, 1.1.1.1:12124.

13 Click OK.

--End--





Restarting the MAS platformUse this procedure to restart the MAS. If you restart the MAS, all active sessions are terminated and all applications are restarted.

Procedure steps

Step Action

1 In the MAS Console, right click Control Panel.

2 Select Operations > Restart to restart the MAS.

--End--





Obtaining the MAS IP addressUse this procedure to obtain the IP address of the MAS.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > IP Interfaces.

2 In the IP Interfaces window, double-click IP Interface Assignment For All Traffic Classes.

3 In the IP Interface Assignment For All Traffic Classes Properties window, the IP address is displayed in the Value box.

You require this IP address for integrating the MAS and AS 5300. Maintain a copy of the MAS IP address.

4 Click OK.

--End--





Adding the MAS node to Network Data and Mtc in the AS 5300 System Management Console

Use this procedure to add the MAS node in the System Management Console.

Prerequisites• Complete the procedure Obtaining the MAS IP address (page 29).

Procedure steps

Step Action

1 In the MCP System Management Console, expand Network Data and Mtc.

2 Click Addresses.

3 In the Addresses window, click the Add button to add a new entry.

The Add button is a blue plus (+) sign.

4 In the Add Address window, type the logical name in the Logical Name box.

The logical name is the name that you want to assign to the MAS you are adding. The logical name does not have to be the host name of the IP address associated with the MAS.

5 In the IP Address box, type the IP address of the MAS node that you want to add.

6 Click Apply.

7 Repeat step 1 to step 6 for each MAS node that you want to add.

--End--





Enrolling the MAS node in the Network Elements in the AS 5300 System Management Console

Use this procedure to enroll the MAS node in the System Management Console.

Prerequisites• For information about creating an SNMP profile, see Nortel AS 5300

Configuration (NN42040-500), Nortel AS 5300 Administration (NN42040-600), or Nortel AS 5300 Security (NN42040-601).

Procedure steps

Step Action

1 In the MCP System Management Console, expand Network Elements.

2 Click Media Application Servers.

3 In the Media Application Servers window, click the Add button to add a new entry.

The Add button is a blue plus (+) sign.

4 In the Add Media Application Server window, enter the values required.

For a list and description of the values you must complete, see Variable definitions (page 31).

5 Click Apply after all values are completed.

6 Repeat step 3 to step 5 for each logical entity that you created for the MAS nodes.

--End--


Variable Value

ShortName A short descriptive name for the MAS node. The maximum length is 6 characters.

For example, MAS1.

LongName A long descriptive name for the MAS node. The maximum length is 32 characters.

For example, MAS_Node_1_Tower_5.

(1 of 2)





Address Select the logical entity that you previously created. For more information, see Adding the MAS node to Network Data and Mtc in the AS 5300 System Management Console (page 30).

FPM The destination for logs and alarms.

For example, SystemManager.

SNMP Profile The SNMP profile.

Physical Site The site domain name.

Polling Interval The polling interval. The possible values are 1 to 120 seconds.

The default value is 60 seconds.

Enable SIP UDP Port The SIP UDP port is enabled by default. The default port is 5060.

Enable SIP TCP Port The SIP TCP port is disabled by default. The default port is 5060.

Enable SIP TLS Port The SIP TLS port is disabled by default. The default port is 5061.

Variable Value

(2 of 2)





Confirming a newly enrolled MAS nodeUse this procedure to confirm that the MAS was successfully added in the System Management Console.

Procedure steps

Step Action

1 In the MCP System Management Console, select Views > Logical View.

2 In the Logical View window, expand Media Application Servers.

3 Ensure that the MAS node you just created appears under Media Application Servers.

--End--





Adding a Service NodeUse this procedure to add a service node in the Provisioning Client.

Prerequisites• Complete the procedure Adding the MAS node to Network Data and Mtc

in the AS 5300 System Management Console (page 30).

Procedure steps

Step Action

1 In the Provisioning Client, expand Service Nodes.

2 Click Add Node.

3 In the Add Node window, type a name for the service name in the Node Name box.

4 In the Node Address area, select the Address Name option button.

5 In the Address Name list, select the MAS name that you previously created.

The MAS name was created in the procedure Adding the MAS node to Network Data and Mtc in the AS 5300 System Management Console (page 30).

6 In the Node Type list, select Generic.

7 In the Location list, select a location for the Node.

8 In the Is Trusted area, select the True option button.

9 In the Behind 1-to1 NAT area, select the True or False option button.

10 In the Enhanced IM area, select the True or False option button.

11 In the Dual CLI area, select the True or False option button.

12 Click Add.

13 Under Service Nodes, click List Node.

14 In the List Nodes window, click Domains beside the node you created in step 12.

15 In the Assign Domains to Node window, select the domain you want to add the node to in the Available Domains list.

16 Click Add.

17 Click Save.

--End--





Adding a Logical EntityUse this procedure to add a logical entity in the Provisioning Client.

Prerequisites• Complete the procedure Adding a Service Node (page 34).

Procedure steps

Step Action

1 In the Provisioning Client, expand Service Nodes.

2 Click Add Logical Entity.

3 In the Add Logical Entity window, type a relevant name for the logical entity in the Entity Name box.

4 In the Routable Services box, select all applications that you want to assign to the logical entity.

5 In the Selection Algorithm list, select the desired algorithm.

The options available are Sequential, Weighted Average, or Round Robin. Nortel recommends selecting Round Robin.

6 In the Add route(s) to logical entity area, type a name for the route assigned to the logical entity in the Name box.

7 In the Node list, select the node that you created in Adding a Service Node (page 34).

8 Ensure the applications selected in step 4 are highlighted.

9 Click Add Entity.

10 Under Service Nodes, click List Logical Entity.

11 In the Logical Entities window, click Domains beside the logical entity you just created.

12 In the Assign Domains to Logical Entity window, select the domain you want to add the logical entity to in the Available Domains list.

13 Click Add.

14 Click Save.

--End--





Adding Applications as a service to a domainUse this procedure to add applications to a domain in the Provisioning Client.

Prerequisites

Attention: For the MAS 6.0 for AS 5300 release, you must disable the delivery of voice messages to an e-mail address.

Procedure steps

Step Action

1 In the Provisioning Client, expand Services.

2 Click Assign Services.

3 In the Assign Services window, select the domain you want to assign the applications to in the Select a domain list.

4 Click Continue.

5 In the Assign services to domains window, under Unified Communications, ensure the Voice Email Delivery Enabled check box is cleared.

6 In the Assign services to domains window, modify other options for each application as required.

For more information, see the application specific documentation. For example, for Meet Me Conferencing, see Nortel Media Application Server 6.0 for AS 5300 Meet Me Conferencing Fundamentals (NN44470-103).

7 Click Save.

--End--





Adding applications as a routable services to a domainUse this procedure to add applications as routable services to a domain.

Procedure steps

Step Action

1 You must add each application as a routable service to a domain. For more information about adding each application as a routable service to a domain, see the application specific sections of this document.

For example, if you installed Meet Me Conferencing, refer to Meet Me Conferencing commissioning (page 105).

--End--




Obtain a keycodeUse the Keycode Retrieval System (KRS) to obtain a license keycode for your configuration.

Navigation• Accessing the Keycode Retrieval System (page 40)

• Registering a new system with KRS (page 41)

• Adding servers to KRS (page 42)

• Generating a keycode (page 46)

Obtaining a keycode taskflowYou must complete the procedures in this module in the order displayed in the following task flow.

- 39 -Obtain a keycode




Obtaining a keycode taskflow





Accessing the Keycode Retrieval SystemUse this procedure to access the Keycode Retrieval System (KRS) to obtain a keycode.

Procedure steps

Step Action

1 Go to the Nortel Web site (www.nortel.com).

2 From the Support & Training menu, select Online Self-Service > Keycode Retrieval.

3 On the Keycode Retrieval System (KRS) Web page, under STEP 1, select GLOBAL LOGIN.

4 Under STEP 2, select MULTIMEDIA COMMUNICATION PORTFOLIO/CS2K-SS/BCP.

5 Click GO.

6 On the LOG IN Web page, type your user ID in the User ID box.

7 In the Password box, type your password.

8 Click Log In.

--End--

http://www.avaya.com





Registering a new system with KRSUse this procedure to register a new system with KRS.

Prerequisites• Complete the procedure Accessing the Keycode Retrieval System

(page 40).

Procedure steps

Step Action

1 On the KEYCODE RETRIEVAL SYSTEM Web page, click Create.

2 On the Product Registration Web page, type a name for your site in the Site Name box.

3 In the City box, type the name of the city where your site is located.

4 In the Country list, select the country where your site is located.

5 In the State/Prov box, select the state or province where your site is located.

6 Click Continue.

--End--





Adding servers to KRSUse this procedure to add servers to KRS.

Prerequisites• You must know the MAC address of all servers in your system.

• Complete the procedure Accessing the Keycode Retrieval System (page 40) and Registering a new system with KRS (page 41).

• In this procedure, you are adding the the Management and Accounting Server (Core) first, followed by the Media Application Servers.

Procedure steps

Step Action

1 On the Keycode Retrieval System Web page, select Core in the Create list.

2 Click Create.

3 In the first box under Core, type the first MAC address of the server.

4 Click Add.

See Procedure job aid: Adding the first Core MAC address (page 43) for an example of adding the first Core MAC address.

5 If you want to remove a MAC address, click Remove.

6 In the second box under Core, type the second MAC address of the server.

7 If you are installing a second Core server as a redundant server, go to step 8. If you are installing only one Core server, go to step 12.

8 Click Add.

9 In the third box under Core, type the first MAC address of the second Core server.

10 Click Add.

11 In the fourth box under Core, type the second MAC address of the second Core server.

12 In the Create list, select Media Server.

13 Click Create.

14 Under Media Server, type the first MAC address of the MAS.

15 Click Add.

16 Under Media Server, type the second MAC address of the MAS.

See Procedure job aid: Adding a Media Server (page 44) for an example of adding a Media Server.





17 Repeat step 12 to step 16 for all Media Application Servers in your configuration.

18 After you have added both MAC addresses for the last MAS, click Continue.

19 On the Product Registration Web page, review your configuration.

See Procedure job aid: Configuration summary (page 44) for an example of a configuration summary.

20 If you want to make changes to your configuration, click Cancel and repeat this procedure.

21 If the configuration details are correct, click Save.

22 On the Product Registration Web page, the message Thank you for registering your product. is displayed.

--End--

Procedure job aid: Adding the first Core MAC addressThe following graphic displays an example of adding the first Core MAC address in KRS.





Procedure job aid: Adding a Media ServerThe following graphic displays and example of adding a Media Server in KRS.

Procedure job aid: Configuration summaryThe following graphic displays an example of a configuration summary in KRS.









Generating a keycodeUse this procedure to generate a keycode.

Procedure steps

Step Action

1 On the Product Registration Web page, under Product Control, click Gen KC with Purchase Order.

For more information, see Procedure job aid: Gen KC with Purchase Order (page 47).

2 On the Generate Keycode With Purchase Order Web site, type the MAC address of the server that you want to generate a keycode for in the Enter System Id box.

3 Click Continue.

All MAC addresses registered to the server are displayed.

4 Type the purchase order information for the order that contained the AS 5300 licenses in one of the boxes provided.

You can enter information in one of the following boxes. Ensure that you type the information in the correct box. For more information, see Procedure job aid: Entering purchase order information (page 48).

• Nortel Order # (COEO)

• Customer PO #

• Alternate/Other Order #

• Customer ID #

5 Click Search.

The KRS displays all associated purchase orders.

6 In the Purchase Order list, select the option button for the purchase order that is appropriate for your system.

For an example of options available, see Procedure job aid: Selecting purchase order codes (page 48).

7 Click Continue.

The KRS displays the contents of the selected purchase orders.

8 In the Purchase Order Details list, select a specific quantity for each item.

OR

Click Add All to select all items for the purchase order.

See Procedure job aid: Purchase order details (page 49) for an example of the contents of a purchase order.





9 Click Continue.

The KRS assigns unique authorization codes for each item selected and the quantity of each item selected is displayed in the QTY. TAKEN column.

10 Click Continue.

11 Review the details of the System Profile table.

The System Profile table displays a summary of all features that KRS is going to generate a keycode for.

12 If the summary is accurate, click Generate Keycode.

The KRS indicates that keycodes are generating. After the keycodes are generated, the Retrieve Keycode page is displayed.

13 Click Download Keycode to save the keycode.

--End--

Procedure job aid: Gen KC with Purchase OrderThe following graphic displays the Gen KC with Purchase Order option in the KRS.





Procedure job aid: Entering purchase order informationThe following graphic displays an example of entering purchase order information.

Procedure job aid: Selecting purchase order codesThe following graphic displays and example of purchase order codes that you can select. Note that only sample numbers are displayed.





Procedure job aid: Purchase order detailsThe following graphic displays and example of purchase order details for a purchase order. Note that only sample numbers are displayed.








MAS CommissioningUse the procedures in this module to commission the Media Application Server (MAS) platform.

Prerequisites• After you have completed the changes that you want to make, you must

restart the MAS platform. For more information, see Restarting the MAS platform (page 133).

Navigation• Configuring licensing (page 52)

• Adding a SIP trusted node (page 53)

• Deleting a SIP trusted node (page 54)

• Adding a SIP route (page 55)

• Deleting a SIP route (page 57)

• Configuring a SIP route (page 58)

• Configuring audio codec settings (page 60)

• Configuring video codec settings (page 62)

• Configuring digit relay settings (page 64)

• Configuring media security options (page 67)

• Configuring conference settings (page 69)

• Configuring silence suppression (page 71)

- 52 -MAS Commissioning




Configuring licensingUse this procedure to configure licensing in the MAS Console.

Prerequisites• You must complete all procedures in the module Obtain a keycode

(page 38).

• For more information about restarting the MAS, see Restarting the MAS platform (page 133).

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Licensing.

2 In the Licensing window, double-click License Server.

3 In the License Server Properties window, select Disabled in the Value list.

4 Click OK.

5 Right-click Licensing.

6 Select Refresh.

7 Double-click Nodal License Key.

8 In the Nodal License Key Properties window, paste the license key in the Value box.

9 Click OK.


--End--


Variable Value

License Server If License Server is enabled, the configured license server is used for all resident applications instead of the nodal license key. When enabled, a provisioned nodal key is ignored.

Nodal License Key The nodal license key. The nodal license key must be present when the License Server is disabled. The key is ignored when a license server is enabled.





Adding a SIP trusted nodeThe MAS process traffic only from SIP trusted nodes. Use this procedure to add a SIP trusted node in the MAS Console.

Prerequisites• If you use a host name, you must use a Domain Name System (DNS)

server to resolve the host name.

• A SIP trusted node must exist for each proxy that is forwarding incoming calls to the MAS.


Procedure steps

Step Action


2 Right-click Trusted Nodes.

3 Select New SIP Trusted Node.

4 In the Add SIP Trusted Node window, type the host name or IP address in the Host or IP box.

5 Click Add.


--End--





Deleting a SIP trusted nodeUse this procedure to delete a SIP trusted node in the MAS console.

Procedure steps

Step Action


2 In the Trusted Nodes window, select the trusted node to delete.

3 Right-click the trusted node to delete.

4 Select Delete.

--End--





Adding a SIP routeUse SIP routes to define all proxy servers that the MAS node communicates with. SIP routes are used for outbound calls and can identify the SIP proxy that defines outbound calls. Use this procedure to add a SIP route in the MAS Console.

Prerequisites• You must use the wildcard domain.

• Define all SIP trusted nodes. For more information, see Adding a SIP trusted node (page 53).

• For the MAS 6.0 for AS 5300 release, there is only one SIP route.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Signaling > SIP > Routes.

2 Right-click Routes.

3 Select New SIP Route.

4 In the Add SIP Route window, enter the values required.

For a list and description of the values you must complete, see Variable definitions (page 55).

You must select wildcard domain and the Enabled check box to activate the SIP route.

5 Click Add.

6 Restart the MAS platform.

--End--


Variable Value

Domain Name of the domain associated with the SIP route. You must select the wildcard domain.

Trusted Node Trusted node associated with this route.

(1 of 2)





Transport SIP transport method. The accepted values are TCP, TLS, or UDP.

Attention: The SIP transport method you select must match the method selected in Enrolling the MAS node in the Network Elements in the AS 5300 System Management Console (page 31).

Remote Port Remote port on which the route accepts SIP requests.

Priority Priority values with a range of 0 to 65535. The lowest value is the highest priority.

The default priority is 0.

Weight Priority values with a range of 0 to 65535.

The default priority is 10.

Roles Select the Roles that this SIP route performs. The Roles available are Proxy and Registrar.

Attention: For the MAS 6.0 for AS 5300 release, you must select Proxy.

Enabled Indicates whether the selection of this route can be enabled or disabled. Routes are typically enabled. You can disable a route to temporarily remove it without reconfiguring the system.

Variable Value

(2 of 2)





Deleting a SIP routeUse this procedure to delete a SIP route in the MAS Console.

Procedure steps

Step Action


2 In the Routes window, right-click the route to delete.

3 Select Delete.

--End--





Configuring a SIP routeUse this procedure to configure a SIP route in the MAS Console.

Prerequisites• The SIP route must be defined. For more information, see Adding a SIP

route (page 55).

Procedure steps

Step Action


2 Expand the Routes list.

3 Select the route to configure.

4 In the Route window, double-click each route setting to configure.

For a list and description of the settings that you can configure, see Procedure job aid (page 58).

5 After you configure each option, click OK.

--End--

Procedure job aidYou can configure the following route settings in the MAS Console.





Property Description

Server Keepalive Specifies the mechanism used by the MAS to determine the status of the route. The following options are available.

Disabled – Route status monitoring is disabled.

Keep Alive Using OPTIONS – Route status is monitored using the SIP OPTIONS message. Route status update is based on the OPTIONS response.

• 200 – Active

• 503 – Inactive

• 504/No Response – Inactive or Down

• Other – Online (applies to AS 5300)


SIP Route Type Specifies the type of route and indicates if special treatments are required.

Attention: For the MAS 6.0 for AS 5300 release, you must select Standard SIP.

SIP Server Poll Timer (msec) Interval that the route is polled for status. The mechanism used to determine the status is based on the configuration setting of Server Keepalive.

The default value is 30000 milliseconds.





Configuring audio codec settingsConfigure audio codec settings in the MAS Console to determine which codecs are enabled and the preferred order of the codecs. The MAS uses enabled codecs and codec order when the MAS negotiates audio codecs with a client endpoint for an inbound or outbound session.

Prerequisites• The supported codecs are G.711-ULAW, G.711-ALAW, G.729A, and

EVRC-0.


Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Media Settings.

2 Right-click Media Settings.

3 Select Configure Audio Codecs.

4 To add an audio codec, on the Audio Codec Configuration window, select an audio codec to enable in the Available list.

5 Click Add.

6 Repeat step 4 and step 5 for all available audio codecs that you want to enable.

7 To remove an audio codec from the Enabled list, select the audio codec that you want to remove.

8 Click Remove.

9 Repeat step 7 and step 8 for each codec that you want to remove.

10 To change the priority of an audio codec, select an audio codec from the Enabled list.

11 In the Enabled list, click Up or Down to change the priority of the audio codec.

The audio codec at the top of the Enabled list has the highest priority.

12 Repeat step 10 and step 11 for all enabled audio codecs until the audio codecs in the Enabled list are prioritized as required.

13 On the Audio Codec Configuration window in the Allowed ptimes area, select the ptimes (packet times) that are required for each codec.

14 In the Default list, set the default ptime for each codec.

15 Click OK.






--End--

Procedure job aidThe following graphic shows an example of the Audio Codec Configuration window.





Configuring video codec settingsConfigure video codec settings in the MAS Console to determine which codecs are enabled, and the preferred order of the codecs. The MAS uses enabled codecs and codec order when the MAS negotiates video codecs with a client endpoint for an inbound or outbound session.

Prerequisites• The supported codecs are H.263, H.263+, H.263++, and NNVC.

Procedure steps

Step Action



3 Select Configure Video Codecs.

4 To add a video codec, on the Video Codec Configuration window, select a video codec to enable in the Available list.

5 Click Add.

6 Repeat step 4 and step 5 for all available video codecs that you want to enable.

7 To remove a video codec from the Enabled list, select the video codec that you want to remove.

8 Click Remove.

9 Repeat step 7 and step 8 for each codec that you want to remove.

10 In the Enabled list, select a video codec.

11 Click the Up or Down buttons to change the priority of the video codec in the Enabled list.

The video codec at the top of the Enabled list has the highest priority.

12 Repeat step 10 and step 11 for all enabled video codecs until the video codecs in the Enabled list are prioritized as required.

13 On the Video Codec Configuration window, enable the Allowed Frame Rates required for each codec.

14 Configure the Default Rate for each codec.

15 Configure the Preferred Format for each codec.

16 Configure the Annex Profile for each codec, if it is required.

Nortel recommends selecting an Annex Profile of 0.

17 Click OK.





--End--

Procedure job aidThe following graphic shows an example of the Video Codec Configuration window.





Configuring digit relay settingsConfigure digit relay settings in the MAS Console to determine what digit relay settings are enabled and the preferred order of the settings. The MAS uses digit relay settings and the order of the settings when the MAS negotiates digit relay with a client endpoint for an inbound or outbound session.

Prerequisites• The supported digit relay methods are INFO Digits and RFC2833.

• The RFC2833 payload type is determined dynamically by default.

Procedure steps

Step Action



3 Select Configure Digit Relay.

4 To add a digit relay method, on the Configure Digit Relay window, select a digit relay method to enable in the Available list.

5 Click Add.

Attention: If no Digit Relay Methods are enabled, in-band DTMF detection is implemented. Nortel does not recommend in-band DTMF detection because it degrades system capacity.

6 Repeat step 4 and step 5 for each digit relay method that you want to enable.

7 To remove a digit relay method from the Enabled list, select the method that you want to remove.

8 Click Remove.

9 Repeat step step 7 and step 8 for each method that you want to remove.

10 To change the priority of a digit relay method, select a method in the Enabled list.

11 In the Enabled list, click Up or Down to change the priority of the digit relay method.

The digit relay method at the top of the Enabled list has the highest priority.

12 Repeat step 10 and step 11 for all enabled digit relay methods until the digit relay methods in the Enabled list are prioritized as required.

13 If a fixed payload type is required, clear the Assign RFC 2833 Payload Type Dynamically check box.





Typically, the RFC 2833 Payload type is assigned dynamically and the Assign RFC 2833 Payload Type Dynamically check box is selected. However, certain client endpoints requires that you use a fixed payload type. The valid range for the payload type is 100 to 127.

14 In the Specify Type box, enter the fixed payload type.

15 Click OK.

--End--

Procedure job aidThe following graphic shows an example of the Configure Digit Relay window.









Configuring media security optionsConfigure media security options on the MAS.

Attention: Ensure that the media security options that you configure on the MAS are the same as the media security options configured on the AS 5300.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration.


3 Select Configure Media Security.

4 In the Media Security Configuration window, select the required security policy in the Security Policy list.

For information about the options available, see Variable definitions (page 68).

5 Click OK.

6 Restart the MAS to apply the changes.

--End--

Procedure job aidThe following graphic shows an example of the Media Security Configuration window.






Variable Value

Security Policy • Security Disabled – If the security policy is Security Disabled, RTP is used.

• Security Enforced – If the security policy is Security Enabled, SRTP is used.

• Best Effort – SDP Offer/Answer Negotiation for Best-Effort SRTP is supported. If the media security policy is best effort, SRTP is used through negotiation if the remote endpoint supports SRTP. Otherwise, RTP is used.

Crypto Suites A crypto suite specifies the exact algorithms and their parameters used for performing key exchange, key derivation, and message encryption.

There are two crypto suites supported:

• AES_CM_128_HMAC_SHA1_80

• AES_CM_128_HMAC_SHA1_32

Attention: Nortel recommends that you select AES_CM_128_HMAC_SHA1_80 because it is more secure.

Priority The priority option places the crypto suites in order within an offered Session Description Protocol (SDP). The highest priority is 1, and the lowest priority is 9.

Lifetime The default lifetime is 2^31.

The possible values are 2^1 to 2^31.

KDR The Key Derivation Rate (KDR) is a parameter input to the underlying SRTP library.

The default value is 0. The possible values are 1 to 24.

MKI The Master Key Identifier length has a range of 0 to 4 bytes.





Configuring conference settingsUse this procedure to configure conference settings in the MAS Console.

Procedure steps

Step Action


2 In the Media Settings window, double-click each conference setting to configure.

For a list and description of the settings you can configure, see Procedure job aid (page 69).


--End--

Procedure job aidYou can configure the following settings for conferencing in the MAS Console.


Automatic Gain Control Enable or disable automatic gain control.

The default value is Enabled.

Customized Replacement Video

Use customer supplied replacement video files if this property is enabled.


Force Video Fast Update Usage for H.263 Channels

Use VFU requests on H.263 channels, even if it appears that periodic IntraFrames exist.


Lock Video Format on First Party in Conference

After you enable this property, the first party determines the video format. If the first party is audio-only, the conference uses no video. If this property is disabled, the first party with active video determines the video format.






Replacement Video For Active Speaker

After you enable this property, the active speaker receives replacement video in conferences where one or more than two (but not two) parties are enabled to speak.


Silent Conference Teardown Delay (sec)

Number of seconds a conference must be silent before it terminates (0 indicates no termination).

The default value is 3600 seconds (1 hour).






Configuring silence suppressionConfigure the silence suppression options in the MAS Console so that information transmits over the network only when someone is speaking. Background noise is not transmitted over the network when silence suppression is enabled and reduces the bandwidth required.

Procedure steps

Step Action


2 In the Media Settings window, double-click each silence suppression setting to configure.



--End--

Procedure job aidYou can configure the following settings for silence suppression in the MAS Console.


Silence Suppression CN Level The silence suppression comfort noise level in dB as defined by RFC3389.

The default is -127 dB.

Silence Suppression Interval (ms)

The number of milliseconds between successive 3389 RTP SS packets.

The default is Disabled.

Silence Suppression Threshold (ms)

The number of milliseconds before transmitted RTP silence is suppressed with 3389 SS packets.

The default is 20 ms.

Silent Conference Teardown Delay (sec)

Number of seconds a conference must be silent before it is terminated. 0 indicates no termination.

The default is 3600 seconds.




Configure continuous streamingThe Media Application Server (MAS) platform supports continuous streaming of pretranscoded audio. Applications can use the continuous streaming audio to provide announcements, music, and other types of audio information for a conference session.

Prerequisites• After you have completed all the required changes, restart the MAS

platform.

Navigation• Creating a local directory for the Directory Provider (page 73)

• Configuring the RSS URL (page 74)

• Configuring the SHOUTCast primary server (page 75)

• Configuring the SHOUTCast backup server (page 76)

• Adjusting the continuous streaming volume (page 77)

- 73 -Configure continuous streaming




Creating a local directory for the Directory ProviderCreate a local directory to store audio files for playback by the Directory Provider. The audio files play during the conference presession and when a conference is on hold. The audio files play alphabetically.

Procedure steps

Step Action

1 Open to the directory %BASEDIR%\platdata\StreamSource\ChannelRoot.

%BASEDIR% is the directory where the MAS software is installed.

2 Create a directory for the audio files.

The directory name is the channel name that the application specifies to stream audio from.

3 Place the audio files in the directory.

--End--





Configuring the RSS URLConfigure the URL of the Real Simple Syndication (RSS) document to enable the RSS Provider for audio playback. The RSS Provider downloads the content of the RSS document and is played by the Directory Provider.

Prerequisites• The maximum size of the RSS document is 260 KB.

Procedure steps

Step Action


2 In the Media Settings window, double-click Continuous Streaming Audio RSS URL.

3 In the Continuous Streaming Audio RSS URL Properties window, specify the URL of the RSS document in the Value box.

4 Click OK.

--End--


Variable Value

Continuous Streaming Audio RSS URL

An RSS URL used to feed audio content to the streaming audio source.





Configuring the SHOUTCast primary serverConfigure SHOUTCast to stream audio content from a SHOUTCast server.

Procedure steps

Step Action


2 In the Media Settings window, double-click Continuous Streaming SHOUTCast Primary URL.

3 In the Continuous Streaming SHOUTCast Primary URL Properties window, type the URL of the SHOUTCast server in the Value box.

4 Click OK.

--End--


Variable Value

Continuous Streaming SHOUTCast Primary URL

A SHOUTCast URL used to feed audio content to the streaming audio source.





Configuring the SHOUTCast backup serverConfigure an optional backup SHOUTCast server for use if the primary server is unreachable.

Prerequisites• Configure the SHOUTCast primary server. For more information, see

Configuring the SHOUTCast primary server (page 75).

• If the primary and backup SHOUTCast URL is unreachable, the Directory Provider is used. For more information, see Creating a local directory for the Directory Provider (page 73).

Procedure steps

Step Action


2 In the Media Settings window, double-click Continuous Streaming SHOUTCast Backup URL.

3 In the Continuous Streaming SHOUTCast Backup URL Properties window, type the URL of the SHOUTCast backup server in the Value box.

4 Click OK.

--End--


Variable Value

Continuous Streaming SHOUTCast Backup URL

A backup SHOUTCast URL is used to feed audio content to the streaming audio source when the primary URL cannot be contacted.





Adjusting the continuous streaming volumeUse this procedure to configure the continuous streaming volume level for all methods of continuous streaming.

Prerequisites• The decibel range is -24 to 24.

Procedure steps

Step Action


2 In the Media Settings window, double-click Continuous Streaming Volume Adjustment (dB).

3 In the Continuous Streaming Volume Adjustment (dB) Properties window, type the volume level in decibels (dB) in the Value box.

4 Click OK.

--End--


Variable Value

Continuous Streaming Volume Adjustment (dB)

Continuous Streaming volume level adjustment in dB. The decibel range is -24 to 24.

The default value is -10.




Configure clustersA Media Application Server (MAS) cluster is a collection of MAS nodes that work together and can be viewed as one node. A MAS cluster shares the SNTP server for clock synchronization, persistent content storage, and the controller peer ring.

Prerequisites• After you have completed all the required changes, restart the MAS

platform.

• You must have at least two MAS platforms in a cluster.

Navigation• Configuring clock synchronization using an SNTP time source server

(page 79)

• Configuring content stores for duplex configurations (page 80)

• Configuring content stores for N-Way configurations on Node 1 and Node 2 (page 82)

• Configuring content stores for N-Way configurations on Node 3 to Node N (page 85)

• Configuring a duplex controller peer ring (page 87)

• Configuring a N-Way controller peer ring (page 89)

- 79 -Configure clusters




Configuring clock synchronization using an SNTP time source serverConfigure clock synchronization using an SNTP time source to ensure all nodes have the same time stamp. Nortel recommends that you configure clock synchronization using an SNTP time source server for all nodes in a cluster.

Prerequisites• You must configure clock synchronization for all MAS nodes in a cluster.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Clustering.

2 In the Clustering window, double-click SNTP Source Server.

3 In the SNTP Source Server Properties window, type the IP address or hostname of an SNTP time source server in the Value box.

4 Click OK.

--End--


Variable Value

SNTP Source Server The IP address or hostname of an SNTP time source server. Specify localhost to designate this server as a time source.





Configuring content stores for duplex configurationsUse this procedure to configure content stores for a cluster that has two MAS nodes (referred to as Node 1 and Node 2).

Prerequisites• You must identify which server is the master server and which server is the

peer master server.

• For more information about content stores, the master server, and peer master server, see Nortel Media Application Server 6.0 for AS 5300 Fundamentals (NN44470-100).

Procedure steps

Step Action


Attention: You must configure Node 1 and Node 2 to be master content stores. Complete step 1 to step 10 for Node 1 and Node 2.

2 In the Clustering window, double-click Content Store Local Function.

3 In the Content Store Local Function Properties window, select Master in the Value list.

4 Click OK.

5 Double-click Content Store Peer Master Server.

6 In the Content Store Peer Master Server Properties window, type the IP address of the peer master node in the Value box.

If you are configuring Node 1, enter the IP address of Node 2 in the Value box for this step. If you are configuring Node 2, enter the IP address of Node 1 in the Value box for this step.

7 Click OK.

8 Double-click Content Store Remote Server(s).

9 In the Content Store Remote Server(s) Properties window, ensure the Value box is empty.

10 Click OK.

--End--






Procedure job aidThe following diagram provides a graphical view of a content store duplex configuration.

Content store duplex configuration

Variable Value

Content Store Local Function Select Master to make the local Content Store one of at most two Master Content Stores in the cluster. Stand alone Content Stores also have a value of Master. To deactivate the local Content Store, select Idle and configure the Content Store Remote Server(s) parameter if it is appropriate for the application.

The default value is Master.

Content Store Peer Master Server

If this is a Master Content Store, enter the single address of the peer Master Content Store. If the Content Store Local Function is set to Idle, or this is a stand alone Master, then leave this field empty. Using an IP Address is recommended. If a hostname is used, DNS must be enabled in the network.

Content Store Remote Server(s)

If the Content Store Local Function has the value Master, leave this field empty. If the Content Store Local Function has the value Idle, enter the addresses of the clustered remote Content Stores available for use by this server. Use a semicolon (;) between the entries. For example, address1;address2. Using IP Addresses is recommended. If hostnames are used, DNS must be enabled in the network.

MAS Node 1

Content Store – Master

MAS Node 2


Peer Master

Peer Master





Configuring content stores for N-Way configurations on Node 1 and Node 2

Configure content stores for the first two nodes in a cluster that has three or more MAS nodes. The number of MAS nodes in the cluster is referred to as N; the first two nodes are Node 1 and Node 2.

Prerequisites

Attention: You must configure Node 1 and Node 2 as master content stores.

Procedure steps

Step Action

1 In the MAS Console of Node 1 and Node 2, expand Configuration > Clustering.

Attention: To configure content stores for N-Way configurations, complete step 1 to step 10 on the first two nodes, Node 1 and Node 2.


3 In the Content Store Local Function Properties window, select Master in the Value list.

4 Click OK.


6 In the Content Store Peer Master Server Properties window, type the IP address of the peer master node in the Value box.

7 Click OK.

8 Double-click Content Store Remote Server(s).

9 In the Content Store Remote Server(s) Properties window, ensure the Value box is empty.

10 Click OK.

11 Configure the remaining nodes in the cluster.

See Configuring content stores for N-Way configurations on Node 3 to Node N (page 85).

--End--






Procedure job aidThe following diagram provides a graphical view of a content store N-Way configuration.

Variable Value











Content store N-Way configuration

MAS Node 1


MAS Node 2

Content Store – MasterPeer Master

Peer Master

MAS Node 3

Content Store – Idle

MAS Node N

Content Store – Idle. . .

Content reads or writes from MAS 3 to MAS N





Configuring content stores for N-Way configurations on Node 3 to Node N

Use this procedure to configure content stores on Node 3 to Node N in a cluster that has three or more MAS nodes. The number of MAS nodes in the cluster is referred to as N.

Prerequisites• Configure content stores on Node 1 and Node 2. For more information,

see Configuring content stores for N-Way configurations on Node 1 and Node 2 (page 82).

Procedure steps

Step Action

1 On Node 3 to Node N in the N-Way configuration, open the MAS Console.

Attention: You must complete step 2 to step 10 for Node 3 to Node N in an N-Way configuration.



4 In the Content Store Local Function Properties window, select Idle in the Value list.

5 Click OK.

6 In the Content Store Remote Server(s) Properties window, type the IP address of Node 1 and Node 2 of this configuration in the Value box.

Separate the IP address with a semicolon (;).

7 Click OK.


9 In the Content Store Peer Master Server Properties window, ensure the Value box is empty.

10 Click OK.

--End--






Variable Value











Configuring a duplex controller peer ringApplications use a controller peer ring to send and receive events between MAS nodes in a cluster. Use this procedure to configure a controller peer ring with two MAS nodes.

Procedure steps

Step Action

1 In the MAS Console of the first node, expand Configuration > Clustering.

2 In the Clustering window of Node 1, double-click Controller Peer Primary Server.

3 In the Controller Peer Primary Server Properties window, type the IP address of Node 2 in the Value box.

4 Click OK.

5 Double-click Controller Peer Backup Server.

6 In the Controller Peer Backup Server Properties window, type the IP address of Node 1 (for a duplex configuration, this is the address of the MAS) in the Value box.

7 Click OK.

8 In the MAS Console of the second node, expand Configuration > Clustering.

9 In the Clustering window of Node 2, double-click Controller Peer Primary Server.

10 In the Controller Peer Primary Server Properties window, type the IP address of Node 1 in the Value box.

11 Click OK.


13 In the Controller Peer Backup Server Properties window, type the IP address of Node 2 (for a duplex configuration, this is the address of the machine) in the Value box.

14 Click OK.

--End--






Procedure job aidThe following diagram provides a graphical view of a duplex controller peer ring configuration.

Duplex controller peer ring configuration

Variable Value

Controller Peer Primary Server Enter the address of this server's primary peer in the Controller Peer Ring. Using an IP address is recommended. If a hostname is used, DNS must be enabled in the network.

Controller Peer Backup Server Enter the address of this server's backup peer in the Controller Peer Ring. Using an IP Address is recommended. If a hostname is used, DNS must be enabled in the network.

MAS Node 1 MAS Node 2

Backup Backup

Primary Primary





Configuring a N-Way controller peer ringApplications use a controller peer ring to send and receive events between MAS nodes in a cluster. Use this procedure to configure a controller peer ring with three or more MAS nodes. The number of MAS nodes is referred to as N.

Procedure steps

Step Action

1 In the MAS Console of node N, expand Configuration > Clustering.

Node N is the current MAS node.

2 In the Clustering window, double-click Controller Peer Primary Server.

3 In the Controller Peer Primary Server Properties window, type the IP address of node N+1 in the Value box.

4 Click OK.


6 In the Controller Peer Backup Server Properties window, type the IP address of node N+2 in the Value box.

7 Click OK.

8 Repeat step 1 to step 7 for all nodes in the N-Way controller peer ring.

--End--


Procedure job aidThe following diagram provides a graphical view of a N-Way controller peer ring configuration where N is 4 MAS nodes.

Variable Value

Controller Peer Primary Server Enter the address of this server's primary peer in the Controller Peer Ring. Using an IP address is recommended. If a hostname is used, DNS must be enabled in the network.

Controller Peer Backup Server Enter the address of this server's backup peer in the Controller Peer Ring. Using an IP Address is recommended. If a hostname is used, DNS must be enabled in the network.





4-Way controller peer ring configuration

Primary Primary Primary PrimaryMAS Node 1

MAS Node 2

MAS Node 3

MAS Node 4

BackupBackup

Backup

Backup




Ad Hoc Conferencing commissioningThe Ad Hoc Conferencing service is based on the Media Application Server (MAS) platform and enables the network to support both ad hoc (on demand) conferencing and consultative call transfers.

Prerequisites• For more information about the Provisioning Client and provisioning tasks

(such as adding nodes, adding a logical entity, and adding nodes or logical entities to a domain), see Nortel AS 5300 Administration (NN42040-600), Nortel AS 5300 Security (NN42040-601), and Nortel AS 5300 Configuration (NN42040-500).

• You must create the domain for Ad Hoc Conferencing in the Provisioning Client.

• You must assign the service package the domain with Ad Hoc Conferencing enabled in the Provisioning Client.

• Ensure the MAS is installed and configured. For more information, see Nortel Media Application Server 6.0 for AS 5300 Installation (NN44470-300).

• For more information about Ad Hoc Conferencing, see Nortel Media Application Server 6.0 for AS 5300 Ad Hoc Conferencing Fundamentals (NN44470-104).

Navigation• Configuring Ad Hoc Conferencing parameters on the MAS platform

(page 92)

• Configuring the routable services information for the Ad Hoc Conferencing logical entity (page 94)

- 92 -Ad Hoc Conferencing commissioning




Configuring Ad Hoc Conferencing parameters on the MAS platformUse this procedure to configure parameters specific to Ad Hoc Conferencing on the MAS. This procedure is optional, the default parameters are sufficient.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Applications > Packaged > Adhoc Conferencing.

2 In the Ad Hoc Conferencing window, double-click each option that you want to configure.

For more information about the options available, see Procedure job aid (page 92).

3 Click OK after you configure each option.

--End--

Procedure job aidYou can configure the following parameters in the MAS Console for Ad Hoc Conferencing.

Parameter Name Description

Entry Exit Tones When enabled, entry and exit tones are played for all Adhoc conferences. When disabled, the ONT Entry Exit Tones configuration setting applies for Adhoc conferences originated by Optical Network Terminals (ONT).


Long Call Duration (min) Maximum allowed duration of a call, in minutes.

The default value is 1440 minutes.

Maximum Number of Ports Defines the maximum number of ports allowed in an Adhoc conference. If this value is set to zero, then the maxparty parameter on the incoming message is used to define the maximum number of ports.

The default value is 0.

(1 of 2)





ONT Entry Exit Tones When enabled, entry and exit tones are played for Adhoc conferences originated by ONTs. When disabled, the Entry Exit Tones configuration setting applies.

The default value is Enabled

ONT Originator Release Ends Conference

When enabled, an Adhoc conference originated by an ONT ends when the originator hangs up. When disabled, the Originator Release Ends Conference configuration setting applies.


Originator Release Ends Conference

When enabled, an Adhoc conference ends after the originator hangs up. When disabled, the ONT Originator Release Ends Conference configuration setting applies for Adhoc conferences originated by ONTs.


Send Accounting INFO When enabled, SIP INFO messages are sent to convey accounting information.


Video Capability Negotiation When enabled and properly licensed, video capability is available.



(2 of 2)





Configuring the routable services information for the Ad Hoc Conferencing logical entity

Use this procedure to assign the Ad Hoc Conferencing Pool to the MAS logical entity.

Procedure steps

Step Action

1 In the Provisioning Client, expand Domains.

2 In the Domains list, expand the domain for the Ad Hoc Conferencing application.

3 Under the Ad Hoc Conferencing domain, select Routable Services > Ad Hoc Conference > Assign Locations.

4 In the Select Ad Hoc Conferencing Pool window, select a pool in the Select Pool list.

For example, select adhoc_pool in the Select Pool list.

5 Click Next.

6 In the Add locations for <pooled entity name> window, locate the Locations for area.

7 In the Locations for area, select the locations that the pooled entity services.

8 Click Save.

--End--




Announcements commissioningThe Announcements application can share information with users after predefined events occur in the system. Two types of announcements are provisioned: treatment (cause) announcements that inform callers of the status of their calls and branding announcements that identify company or product names for commercial purposes.



• You must create the domain for domain for Announcements in the Provisioning Client.

• You must assign the service package to the domain with Announcements enabled in the Provisioning Client.

• For more information about Announcements, see Nortel Media Application Server 6.0 for AS 5300 Announcements Fundamentals (NN44470-105).

Navigation• Configuring the Announcements parameters on the MAS platform

(page 96)

• Setting the locale (or language) of your announcements (page 97)

• Placing announcement files on the MAS (page 98)

• Configuring treatment routable services information for the Announcement logical entity (page 100)

• Configuring branding routable services information for the Announcement logical entity (page 103)

- 96 -Announcements commissioning




Configuring the Announcements parameters on the MAS platformUse this procedure to configure parameters specific to Announcements on the Media Application Server (MAS). This procedure is optional, the default parameters are sufficient.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Applications > Packaged > Announcements.

2 In the Announcements window, double-click each option that you want to configure.

For more information about the options that you can configure, see Procedure job aid (page 96).

3 Click OK after you configure each option.

--End--

Procedure job aidYou can configure the following options for Announcements.


Answer Delay (rings) Number of rings before an incoming SIP call is answered. The duration of a ring is configurable as the Ring Interval. 0 rings implies immediate answer.

The default value is 0 rings.







Setting the locale (or language) of your announcementsUse this procedure to set the locale for the announcements. The locale you select determines the language in which the announcements are played.

Procedure steps

Step Action


2 In the Domains list, expand the domain for the Announcements application.

3 Under the domain for Announcements, select Domain Locales.

4 In the Domain Locales window, select the check box for each language that you want to use for the Announcements application.

5 In the Default column, select the option button beside the language that you want to be the default language for the Announcements application.

6 Click Update to save your selections.

--End--





Placing announcement files on the MASUse this procedure to place your announcements files on the Announcements MAS.

Prerequisites• The announcements must exist. For more information, see Nortel Media

Application Server 6.0 for AS 5300 Announcements Fundamentals (NN44470-105).

• For a list of the available announcement commands, see Nortel Media Application Server 6.0 for AS 5300 Announcements Fundamentals (NN44470-105).

Procedure steps

Step Action

1 On the Media Application Server, select Start > Command Prompt to launch the Command Prompt screen.

2 On the Command Prompt screen, create an announcement folder to group the announcement files on the Announcements MAS using the following command:

provtool annc_create_folder <domain>

3 Upload one announcement file into the announcement folder using the following command:

provtool annc_upload_media <domain> <media file> <language> [<country>]

For a description of these parameters, see Variable definitions (page 99).

4 Repeat step 3 for each announcement file that you want to upload to the announcement folder.

--End--






Procedure job aidThe following example command shows the command used to upload a Welcome file to the announcements folder.

provtool annc_upload_media nortel.com D:\annoucements\welcome en US

The following commands show examples of uploading a Welcome announcement file in two different languages: French and Japanese.

provtool annc_upload_media nortel.com D:\annoucements\welcome fr

provtool annc_upload_media nortel.com D:\annoucements\welcome jp

Variable Value

country The country parameter is the country where the language is spoken. This parameter is an optional parameter. You can specify the country as the full country name (for example, United States of America) or with the two-letter ISO code, three-letter ISO code, or two-digit country code (for example, US).

domain The domain parameter is the provisioned domain or subdomain where the Announcements application is available. For example, xyz.com.

language The language parameter is the language in which the announcement was recorded. Specify the language as a two-letter ISO code (for example, en, fr, jp).

media file The media file parameter is the name of the treatment file (in .wav file format). You must include the path to the file but you need not include the .wav extension).





Configuring treatment routable services information for the Announcement logical entity

Use this procedure to configure treatment routable services information for Announcements in the Provisioning Client.

Prerequisites• Complete the procedure Placing announcement files on the MAS

(page 98).

Procedure steps

Step Action



3 Select Routable Services > Treatments/Causes > Create Treatment/Cause Files.

4 From the list of treatment pooled entities available in this domain, click Edit Files beside the entity to which you want to assign a treatment file.

5 In the Create Treatment Files window, in the New file box, type the name of a treatment file.

Attention: The name of the treatment file must match the name of the file that was placed on the MAS. See Placing announcement files on the MAS (page 98).

6 Click Add.

7 Repeat step 5 to step 6 for each treatment file that you want to add.

A list of treatment files is displayed in the Current Files field.

8 Click Save.

9 Select Routable Services > Treatments/Causes > Assign Pool.

10 In the Modify Treatment Announcements Pool window, in the Select Pool list, select the logical pooled entity you created for treatments.

11 Click Next.

12 In the Group Name box, type a group name.

13 In the Available reasons list, select a treatment reason.

For more information about the treatment reasons available, see Procedure job aid (page 101).

14 Click Add.

15 Repeat steps step 13 to step 14 to select multiple treatment reasons.





16 In the Available Files list, select an audio file to play when a treatment reason selected in step 13 and step 14 is generated.

17 Click Add.

18 Repeat steps step 16 to step 17 to select multiple audio files.

19 In the Select Repeat (Times Played) list, select the number of times the treatment audio files must be repeated before the call is terminated.

The possible values are 1 to 9, or infinite. If you plan to route the call to a telephone number after the treatment, do not select the infinite value.

20 In the Route box, specify a route to which the call is directed after the treatment has played.

The route can be either a URL or telephone number.

21 Click Save.

--End--

Procedure job aidThe following treatment reasons are available in the Available Reasons list.

Treatment reason Message number

BAD_REQUEST 400

UNAUTHORIZED 401

PAYMENT_REQUIRED 402

FORBIDDEN 403

NOT_FOUND 404

METHOD_NOT_ALLOWED 405

NOT_ACCEPTABLE 406

PROXY_AUTHENTICATION_REQUIRED 407

REQUEST_TIMEOUT 408

CONFLICT 409

GONE 410

LENGTH_REQUIRED 411

PRECONDITION_FAILED 412

REQUEST_ENTITY_TOO_LARGE 413

REQUEST_URI_TOO_LONG 414

UNSUPPORTED_MEDIA_TYPE 415

(1 of 2)





BAD_EXTENSION 420

TEMPORARILY_UNAVAILABLE 480

CALL_LEG_TRANSACTION_DOES_NOT_EXIST 481

LOOP_DETECTED 482

TOO_MANY_HOPS 483

ADDRESS_INCOMPLETE 484

AMBIGUOUS 485

BUSY_HERE 486

REQUEST_TERMINATED 487

NOT_ACCEPTABLE_HERE 488

EVENT_NOT_SUPPORTED 489

REQUEST_PENDING 491

MCT_SUCCESS 498

MCT_FAILURE 499

SERVER_INTERNAL_ERROR 500

NOT_IMPLEMENTED 501

BAD_GATEWAY 502

SERVICE_UNAVAILABLE 503

GATEWAY_TIMEOUT 504

VERSION_NOT_SUPPORTED 505

BUSY_EVERYWHERE 600

DECLINE 603

DOES_NOT_EXIT_ANYWHERE 604

NOT_ACCEPTABLE 606

MLPP_BPA 700

MLPP_UPA 701

MLPP_BNEA 702

MLPP_VCA 703

MLPP_ICA 704

STARCODE_SUCCESS 1001

STARCODE_FAILURE 1002

Treatment reason Message number

(2 of 2)





Configuring branding routable services information for the Announcement logical entity

Use this procedure to configure branding routable services information in the Provisioning Client.

Prerequisites• You must place .wav files on the MAS. For more information, see Placing

announcement files on the MAS (page 98).

Procedure steps

Step Action



3 Select Routable Services > Branding> Create Branding Files.

4 In the Create Branding Files window, from the list of branding pooled entities available in this domain, choose one to which you want to assign branding files.

5 Click Edit Files.

6 In the Create Branding Files window, in the New File box, type the name of a branding file.

7 Click Add.

8 Repeat step 6 to step 7 for each additional branding file that you want to add.

A list of branding files is displayed in the Current Files field.

9 Click Save.

10 Select Routable Services > Branding > Assign Branding Files.

11 In the Modify Branding Announcements Pool window, from the Select Pool list, select the logical entity you created for branding announcements.

12 Click Next.

13 In the Available Files list, select a branding file you want to use.

14 Click Add.

15 Repeat step 13 to step 14 for each additional branding file you want to include in this branding service node.

16 If you want to play the branding files in a specific order, select a branding file in the Selected Files list.

17 Click Up or Down to change the order of the branding file.

18 Repeat step 16 and step 17 until the branding files are in the order you want.





19 In the Select Repeat (Times Played) list, select the number of times the branding file must be repeated before the call is terminated.

The possible values are 1 to 9, or infinite.

20 Select the Play Between Subscribers in this Domain check box if you want users that are provisioned within this domain to hear the branding announcements.

21 Click Save.

--End--




Meet Me Conferencing commissioningThe Meet Me Conferencing application provides reservationless multimedia audio and video conferencing, based upon the Media Application Server (MAS) platform. The Meet Me Conferencing application enables users to have their own private conferencing resource available for meetings at any time. The administrator provisions the application to the conference owner, or the chairperson, who in turn controls the use of the personal conference resource. This module provides the steps you must complete to commission the Meet Me Conferencing application on the MAS platform.



• You must create the domain for Meet Me Conferencing in the Provisioning Client.

• You must assign the service package to the domain with Meet Me Conferencing enabled in the Provisioning Client.

• For more information about Meet Me Conferencing, see Nortel Media Application Server 6.0 for AS 5300 Meet Me Conferencing Fundamentals (NN44470-103).

Navigation• Configuring Meet Me Conferencing parameters on the MAS platform

(page 106)

• Adding .wav files for wait music (page 109)

• Creating an alias for Meet Me pooled entity (page 110)

• Configure audio recording delivery for Meet Me Conferencing (page 111)

• Configuring user-specific Meet Me Conferencing service data (page 112)

- 106 -Meet Me Conferencing commissioning




Configuring Meet Me Conferencing parameters on the MAS platformUse this procedure to configure parameters specific to Meet Me Conferencing on the MAS. This procedure is optional, the default parameters are sufficient.

Prerequisites• You must configure the Meet Me Conferencing parameters on all nodes in

the cluster.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Applications > Packaged > MeetMe Conferencing.

2 In the MeetMe Conferencing window, double-click each option that you want to configure.

For more information about the options that you can configure, see Procedure job aid (page 106).

3 Click OK after each option is configured.

--End--

Procedure job aidYou can configure the following options for MeetMe Conferencing.



The default value is 1 ring.

Audio Recording When enabled, audio recording is available.


Chat Capability When enabled, a chat room can be launched by the conference chair person.


Default Domain Primary domain for stand alone Meet Me.

(1 of 3)





Default Locale Default Locale: Supported values are en_us, fr_fr, es_es, de_de, ja_jp, zh_tw, zh_cn, ko_kr,pt_pt,ru_ru.

The default value is en_us.

Instant Messages When enabled, instant messages will be sent to the conference chair person.


Instant Messages From User MeetMe conference instant messages (IM) are displayed as coming from this user. Valid characters are: a-z A-Z 0-9 _ . ! ~ * ' ( ) + = and -. No spaces are allowed.

The default value is MeetMeConf.

Inter-Announcement Wait Time (ms)

Duration (ms) between "chair has not yet arrived" messages.




Max. Chairperson PIN Attempts

The number of attempts allowed for chair person PIN entry.


Max. Participant Access Code Attempts

The number of attempts allowed for access code entry.


Max. Participant Passcode Attempts

The number of attempts allowed for passcode entry.


Max. Wait Segments Number of times to play "chair has not yet arrived" message before disconnecting.


Passcodes The chair person can enter a Passcode before starting a conference. Participants will be required to enter the passcode before being admitted to the conference.


Send Accounting INFO When enabled, SIP INFO messages are sent to convey accounting information.



(2 of 3)





Timer: First Digit (ms) Duration (ms) to wait for the first DTMF tone.


Timer: Inter-Digit (ms) Duration (ms) to wait between DTMF tones.


Timer: Star First Digit (ms) Duration (ms) to wait for the '*' DTMF tone.


Timer: Star Inter Digit (ms) Duration (ms) to wait for the a digit while entering the pin.


Use Default Domain Indicates if the default domain is solely used.


Video Capability Negotiation When enabled and properly licensed, video capability is available.



(3 of 3)





Adding .wav files for wait musicPlace music files in .wav format on the MAS platform. These music files are played when conference participants are waiting for a conference to begin.

Procedure steps

Step Action

1 On the MAS platform, locate the MAS installation directory.

The default destination directory is D:\Program Files\Nortel\MAS.

2 Locate the \platdata\StreamSource\ChannelRoot\Audio subdirectory.

3 Copy the .wav files you have selected for the hold music to the Audio subdirectory.

--End--





Creating an alias for Meet Me pooled entityUse this procedure to create an alias for the Meet Me Conferencing pooled entity in the Provisioning Client.

Procedure steps

Step Action


2 In the Domains list, expand the domain for the Meet Me application.

3 Select Routable Services > Meet Me > Create Aliases.

4 In the Create Aliases for Meet Me Conferencing window, in the Alias box, type the alias for the Meet Me Conferencing pooled entity

5 In the Select Pool list, select the name of the pooled entity for for Meet Me Conferencing.

6 In the Locale list, select the locale for the pooled entity services.

Attention: This selection determines the language used for voice prompts and announcements during conferences this pooled entity services.

7 Click Save.

--End--





Configure audio recording delivery for Meet Me ConferencingYou can configure the MAS to deliver conference recordings to an e-mail address.

Prerequisites

Attention: Enabling e-mail delivery of voice messages is not secure. For the MAS 6.0 for AS 5300 release, the delivery of conference recordings to an e-mail address must be disabled.

• Identify the SMTP server.

Procedure steps

Step Action


2 In the Domains list, click the domain name of the Meet Me application.

3 In the Details for domain window, locate the Default UC Properties area.

4 In the Default SMTP Server box, type the IP address of the SMTP server.

5 Click Save.

--End--





Configuring user-specific Meet Me Conferencing service dataUse this procedure to configure user-specific Meet Me Conferencing service data. You can configure options such as the chair pin, the access code, and enable or disable entry and exit tones.

Prerequisites

Attention: If you enter an e-mail address in the Audio Recording E-mail Address box, conference recordings are delivered to the address after the conference ends. For the MAS 6.0 for AS 5300 release, the delivery of conference recordings to an e-mail address must be disabled.

Procedure steps

Step Action


2 In the Domains list, expand the domain for the Meet Me application.

3 Select Users > List Users.

4 Enter the search criteria for the user and click Search.

5 For the required user, click Details in the Details column.

6 In the User details window, Click Meet Me Properties.

7 In the User Meet Me Conferencing Properties window, select the Chair Ends Conference check box if you want the conference to end after the chairperson leaves.

8 If a unique Access Code is not automatically generated in the Access Code box, type a system-wide unique 4 to 10 digit number.

9 Select the Send instant messages check box if you want the conference application to send instant messages to the chairperson when conference events occur.

10 Select the Allow Fast Start check box if you want to allow the conference to start prior to chair person arriving.

11 Select the Allow audio emoticons check box if you want emoticons to be visible.

12 In the Change the Entry/exit Announcements area, select the Play entry/exit tones option button to enable entry and exit tones when a participant joins or leaves the conference, or select Do nothing if you do not want to hear entry and exit tones.

13 Click Save.

14 Click Change Chair PIN.





15 In the Change Meet Me Chair PIN for user window, enter the new PIN in the Chair PIN box.

16 In the Confirm PIN box, reenter the PIN.

17 Click Save.

--End--




Music on Hold commissioningWith the Media Application Server (MAS) Music on Hold service, a user can receive a call, place that call on hold, and play music to the person on hold until they retrieve the call. The purpose of the music is to reassure the person on hold that the call was not disconnected or dropped.



• You must create the domain for Music on Hold in the Provisioning Client.

• You must assign the service package to the domain with Music on Hold enabled in the Provisioning Client.

• For more information about Music on Hold, see Nortel Media Application Server 6.0 for AS 5300 Music on Hold Fundamentals (NN44470-106).

Navigation• Configuring the Music on Hold parameters on the MAS platform

(page 115)

• Placing music files on the MAS (page 116)

• Configuring routable services information for the Music on Hold logical entity (page 118)

• Enabling the Music on Hold application in the end user service packages (page 119)

- 115 -Music on Hold commissioning




Configuring the Music on Hold parameters on the MAS platformUse this procedure to configure parameters specific to Music on Hold on the MAS. This procedure is optional, the default parameters are sufficient.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Applications > Packaged > Music on Hold.

2 In the Music on Hold window, double-click each option that you want to configure.

For information about the options that you can configure, see Procedure job aid (page 115).

3 Click OK after each option is configured.

--End--

Procedure job aidYou can configure the following options for Music on Hold.



The default value is 0 rings.







Placing music files on the MASYou must place music files to one MAS within the Music on Hold service node. Place music files on only one MAS in the service instance, because music files are replicated by the system throughout the service instance.

Prerequisites• The Music on Hold application does not support external media source

files. All media source files must be in .wav format and must reside on the MAS on which the Music on Hold application is running (simplex deployment), or the music files must be on one of the MAS platforms (for a duplex deployment) in the logical entity.

• The music files must in .wav format and must be encoded as a single channel (mono) linear 16-bit bit stream using pulse code modulation (PCM) that is sampled at 8 kHz.

• The music files must exist. For more information, see Nortel Media Application Server 6.0 for AS 5300 Music on Hold Fundamentals (NN44470-106).

• The music files must be placed on the D drive of the MAS.

• You must have access to the provtool on the MAS.

Procedure steps

Step Action

1 On the MAS, open a command prompt by clicking Start > Command Prompt.

2 Create a Music on Hold folder to contain the music files on the Music on Hold MAS by typing the following command.

provtool moh_create_folder <domain> <folder>

3 Upload one music file into the folder created in step 2 by typing the following command.

provtool moh_upload_media <domain> <folder> <media file>

4 Repeat step 3 for all announcement files that you want to upload.

Attention: You can repeat step 2 for each music folder that you want to create, and then repeat step 3 to add specific music files to a specific folder. For example, you can have folders for classical, instrumental, or rock music.

--End--






Procedure job aidThe following sample commands shows the commands used to upload music files (music1.wa and music2) to the music folder (MOH_music).

provtool moh_upload_media nortel.com MOH_music D:\music1.wav

provtool moh_upload_media nortel.com MOH_music D:\music2

Variable Value

domain The domain parameter is the name of the provisioned domain or subdomain where the Music on Hold application is available. For example, xyz.com.

folder The name of the folder that will contain a set of music files. (A Music on Hold folder is similar to a standard file system directory or folder.)

media file The media file parameter is the name of the music file (in .wav file format) to be placed in the music folder. The .wav file extension does not have to be included as part of the music file name.





Configuring routable services information for the Music on Hold logical entity

Use this procedure to configure routable services information for Music on Hold.

Prerequisites• Complete the procedure Placing music files on the MAS (page 116).

Procedure steps

Step Action


2 In the Domains list, expand the domain for the Music on Hold application.

3 Select Routable Services > Music on Hold > Create Music Folders.

4 In the Create Music Folders window, click Edit Folders next to the Music on Hold pool.

5 In the Create Music Folder window, in the New Folder box, type the name of a music folder.

6 Click Add.

7 Click Save.

8 Select Routable Services > Music on Hold > Assign Music Folders.

9 In the Modify Music on Hold Pool window, from the From the Select Pool list, select the logical entity you have created for the Music on Hold application.

10 Click Next.

11 In the Assign Folder window, from the Select Folder list, select the Music on Hold folder that you defined in step 5.

12 Click Save.

--End--





Enabling the Music on Hold application in the end user service packages

Use this procedure to enable Music on Hold.

Procedure steps

Step Action


2 In the Domains list, expand the domain for the Music on Hold application.

3 Under the Music on Hold domain, select Service Package > List Packages.

4 In the Service package list window, click Details-Modify for the service package on which you want to enable the Music on Hold application.

5 In the Package details window, select the Music On Hold check box.

6 Click Save and Enforce Now to immediately enable the Music on Hold application for all users on this domain who are actively subscribed to this service package

OR

Click Save and Enforce Later to enable the Music on Hold application for all users on this domain when they resubscribe to this service package. The service is enabled after a user reconnects to the network or after their service package subscription is automatically refreshed.

7 If you want to enable Music on Hold for multiple service packages, repeat step 1 to step 6 for each service package.

--End--




Unified Communications commissioning

The Unified Communications application is a voicemail application that provides users with integrated access to their voicemail messages from a preferred client device. This module provides the steps you must complete to commission the Unified Communications application on the Media Application Server (MAS) platform.



• You must create the domain for Music on Hold in the Provisioning Client.

• You must assign the service package to the domain with Music on Hold enabled in the Provisioning Client.

• For more information about Unified Communications, see Nortel Media Application Server 6.0 for AS 5300 Unified Communications Fundamentals (NN44470-102).

Navigation• Configuring the Unified Communications parameters on the MAS Platform

(page 122)

• Creating a message retrieval alias for a Unified Communications pooled entity (page 124)

• Creating express messaging aliases for Unified Communications pooled entity (page 125)

• Adding a voice mail server host (page 126)

• Adding a SIP voice mail server (page 127)

• Provisioning voice mail user-specific data (page 128)

• Provisioning Unified Communications service user-specific data (page 129)

- 121 -Unified Communications commissioning








Configuring the Unified Communications parameters on the MAS Platform

Use this procedure to configure the parameters specific to Unified Communications on the MAS.

Prerequisites• The MAS is offline.

• You must have administrative rights to the MAS Console.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Applications > Packaged > Unified Communications.

2 Double-click each of the following parameters to modify the parameter value as required, then click OK.

• Default Locale

• PA Address

• Send Accounting Info

• Use Custom E-mail Templates

For a description of the parameters in the MAS Console, see Variable definitions (page 123).

Attention: The Deposit SIP URI #1, Deposit SIP URI #2, Express SIP URI #1, Express SIP URI #2, Retrieve SIP URI #1, and Retrieve SIP URI #2 parameters are left blank.

--End--






Variable Value

Default Locale The default locale to present to users if the incoming call does not specify the locale.

This parameter is a four-letter code in the format of ab_cd where ab represents the language and cd represents the country code.

The supported options are:

• en_us—English/United States

• fr_fr—French/France

• es_es—Español (Spanish)/Spain

• de_de—Deutsch (German)/Germany

• ja_jp—Japanese/Japan

• zh_tw—Traditional Chinese/Taiwan

• zh_cn—Simplified Chinese/China

• ko_kr—Korean/Korea

• pt_pt—Portugese/Portugal

• ru_ru—Russian/Russia

PA Address The address of the Personal Agent. This parameter must be configured if Voice E-mail Delivery is enabled.

Send Accounting Info The options are Enabled or Disabled.

If enabled, the MAS sends SIP INFO messages for accounting purposes (after the user logs on).

Use Custom E-mail Template The options are Enabled or Disabled.

When enabled, customer provided e-mail templates are used.





Creating a message retrieval alias for a Unified Communications pooled entity

Use this procedure to create a message retrieval alias for Unified Communications in the Provisioning Client.

Prerequisites• In this procedure, use the logical entity that you created in Adding a

Logical Entity (page 35).

Procedure steps

Step Action


2 In the Domains list, expand the domain for the Unified Communications application.

3 Select Routable Services > Unified Communications > Create Message Retrieval Alias.

4 In the Create Aliases for UC Message Retrieval window, in the Alias box, type a message retrieval alias for the Unified Communications pooled entity.

5 In the Select Pool list, select the name of the appropriate logical entity.


This selection determines the language used for voice prompts and announcements during message retrieval sessions initiated with the alias selected.

7 Click Save.

--End--





Creating express messaging aliases for Unified Communications pooled entity

Use this procedure to create an express messaging alias for Unified Communications in the Provisioning Client.

Prerequisites• In this procedure, use the logical entity that you created in Adding a

Logical Entity (page 35).

Procedure steps

Step Action



3 Select Routable Services > Unified Communications > Create Express Messaging Aliases.

4 In the Create Aliases for UC Express Messaging window, in the Alias box, type an express messaging alias for the Unified Communications pooled entity.

5 In the Select Pool list, select the name of the logical entity.


This selection determines the language used for voice prompts and announcements during express messaging sessions initiated with the alias selected.

7 Click Save.

--End--





Adding a voice mail server hostUse this procedure to add a voice mail host in the Provisioning Client.

Procedure steps

Step Action

1 In the Provisioning Client, expand Voice Mail.

2 Click Add VMS Host.

3 In the Add Voicemail Server Host window, type a relevant name for the Unified Communications voice mail server in the Host Name box.

4 Select the Host URL option button.

5 In the Host URL box, type sip:ucmsgrtv@<your domain>;trusted.

<your domain> is the the domain of the voice mail server.

6 Click Add.

--End--





Adding a SIP voice mail serverAdding a SIP-based voicemail server allows the administrator to configure the Session Manager to communicate with a voicemail server using SIP. The Session Manager receives information about what to query to find the location of the voicemail server. The Session Manager uses this information to send SIP calls to the voicemail server when calls are routed to voicemail.

Prerequisites• Complete the procedure Adding a voice mail server host (page 126).

Procedure steps

Step Action

1 In the Provisioning Client, expand Voice Mail.

2 Click Add SIP VMS.

3 In the Add a new SIP Voicemail Server window, type a relevant name for the SIP voicemail server in the Name box.

4 In the Type list, select SIP_VMS.

5 In the Client contact box, type voicemail.

6 In the App. Svr. Address list, select your AS 5300 Application Server.

7 In the Domains list, select the domain you want to add the SIP voicemail server to.

The domain you select must match the domain you selected in step 5 of Adding a voice mail server host (page 126).

8 In the Voicemail Host list, select the voicemail server you created previously in Adding a voice mail server host (page 126).

9 Click Submit.

The SIP-based voicemail server you added is now displayed in the list of voicemail servers.

--End--





Provisioning voice mail user-specific dataUse this procedure to provision the user’s voice mail information in the Provisioning Client. You can provision information such as the user’s voice mail server and mailbox ID.

Prerequisites• Complete the procedures Adding a voice mail server host (page 126) and

Adding a SIP voice mail server (page 127).

Procedure steps

Step Action





5 For the required user, click Details in the Details column.

6 In the User details window, click Voicemail.

7 In the User Voicemail window, in the Voicemail Server list, select the name of the voicemail server.

8 In the Voicemail field, type the mailbox ID.

The mailbox ID must be 3 to 16 digits in length and must be unique within each domain. Nortel recommends entering the users alias as the mailbox ID.

9 Click Save.

--End--





Provisioning Unified Communications service user-specific dataUse this procedure to provision user-specific information for Unified Communications.

Prerequisites• You must complete this procedure for every user.

Procedure steps

Step Action





5 Click Details for the user requiring that their Unified Communications properties be modified.

6 In the User details window, click Unified Communications Properties.

7 In the User Unified Communications Properties window, in the Account Status list, select INITIAL.

8 Ensure the E-mail Address box is cleared.

9 Click Save.

10 Click Change PIN.

11 In the PIN box, type a PIN for the user.

The PIN must be numeric and be 4 to 10 digits in length

12 In the Confirm PIN box, retype the PIN for the user.

13 Click Save.

--End--




Common proceduresThe following sections describe common procedures that you use while commissioning the Media Application Server (MAS).

Navigation• Starting the MAS platform (page 131)

• Stopping the MAS platform (page 132)

• Restarting the MAS platform (page 133)

• Locking the MAS platform (page 134)

• Locking the MAS platform using Pending Lock (page 135)

• Unlocking the MAS platform (page 136)

• Locking MAS applications in the MAS console (page 137)

• Locking MAS applications in the MAS Console using Pending Lock (page 138)

• Unlocking MAS applications in the MAS Console (page 139)

• Establishing a Remote Desktop connection (page 140)

• Configuring SIP general settings (page 141)

• Viewing SIP trusted nodes (page 144)

• Configuring QoS settings (page 145)

- 131 -Common procedures




Starting the MAS platformUse this procedure to start the MAS.

Procedure steps

Step Action

1 In the MAS Console, right-click Control Panel.

2 Select Operations > Start to start the MAS.

If the MAS is already active, the Start option appears dimmed.

--End--





Stopping the MAS platformUse this procedure to stop the MAS. If you stop the MAS, all active sessions are stopped immediately.

Procedure steps

Step Action


2 Select Operations > Stop to stop the MAS.

If the MAS is already stopped, the Stop option appears dimmed.

--End--





Restarting the MAS platformUse this procedure to restart the MAS. If you restart the MAS, all active sessions are terminated and all applications are restarted.

Procedure steps

Step Action


2 Select Operations > Restart to restart the MAS.

--End--





Locking the MAS platformUse this procedure to lock the MAS. If you lock the MAS platform, all active sessions are terminated and no new requests are allowed.

Procedure steps

Step Action


2 Select Operations > Lock to lock the MAS.

If the MAS is already locked, the Lock option appears dimmed.

--End--





Locking the MAS platform using Pending LockUse the Pending Lock option in the MAS Console to lock the MAS platform. Using this method, all active sessions are allowed to finish and no new requests are allowed. The MAS is locked after all active sessions are completed.

Procedure steps

Step Action


2 Select Operations > Pending Lock to lock the MAS after all processes finish.

If a pending lock is already requested, the Pending Lock option appears dimmed.

--End--





Unlocking the MAS platformUse this procedure to unlock the MAS. If the MAS is locked, no applications or services can function.

Procedure steps

Step Action


2 Select Operations > Unlock to unlock the MAS.

If the MAS is already unlocked, the Unlock option appears dimmed.

--End--





Locking MAS applications in the MAS consoleUse this procedure to lock an application installed on the MAS platform. If you lock an application, all active sessions are terminated and no new requests are allowed for that application.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Applications > Packaged.

2 Right-click the name of the application that you want to lock.

3 Select Operations > Lock.

If the application is already locked, the Lock option appears dimmed.

--End--





Locking MAS applications in the MAS Console using Pending LockUse this procedure to lock an application installed on the MAS platform. If you use the pending lock option, all active sessions for the application are allowed to finish and no new requests are allowed. The application is locked after all active sessions are completed.

Procedure steps

Step Action



3 Select Operations > Pending Lock.

If the application already has a pending lock, the Pending Lock option appears dimmed.

--End--





Unlocking MAS applications in the MAS ConsoleUse this procedure to unlock an application installed on the MAS platform. If an application is locked, the application is not active.

Procedure steps

Step Action



3 Select Operations > Unlock.

If the application is already unlocked, the Unlock option appears dimmed.

--End--





Establishing a Remote Desktop connectionUse the Remote Desktop Connection application to access the MAS and use the MAS Console.

Prerequisites• Configure Remote Desktop and IPSec. For more information, see Nortel

Media Application Server 6.0 for AS 5300 Administration and Security (NN44470-600).

Procedure steps

Step Action

1 Select Start > All Programs > Accessories > Communications > Remote Desktop Connection.

2 In the Remote Desktop Connection window, type the IP address of the MAS you want to connect to in the Computer box.

3 Click Connect.

--End--





Configuring SIP general settingsUse this procedure to configure general SIP settings in the MAS Console.

Procedure steps

Step Action

1 In the MAS Console, expand Configuration > Signaling > SIP > General.

2 In the General Settings window, double-click each SIP setting that you want to configure.



--End--

Procedure job aidYou can configure the following General SIP settings in the MAS Console.


Always Approve SIP TLS Certificate

If enabled, the system will always accept remote certificate over SIP TLS.


Always use SIP default outbound proxy

If you enable this property, the system routes SIP requests that do not match domain proxy configuration through the default outbound proxy if it is configured. The SIP requests are routed even if an IP address is specified in the host portion of the destination URI.


Answer Delay (rings) Number of rings before an incoming SIP call is answered. The duration of a ring is configurable using the Ring Interval engineering parameter. 0 rings is immediate answer.


Enable SIP TCP Transport If you enable this property, the system accepts SIP requests over TCP.


Enable SIP TLS Mutual Authentication

Mutual authentication option for SIP TLS.






Enable SIP TLS Transport If you enable this property, the system accepts SIP requests over TLS.


Enable SIP UDP Transport If you enable this property, the system accepts SIP requests over UDP.


Enforce SIP Route Configuration

By default, the system raises an alarm if route configuration is missing. If outgoing route configuration is not required, disable this property.


Enforce SIP TLS in Secured Media Mode

If this property is enabled, non-TLS transport is disabled in secured media mode.


Hide SIP User-Agent Header Prevents the User-Agent header from being included in SIP messaging.


Long Call Audit Refresh Timer Time in seconds to send a refresh request.


Long Call Audit Type Indicates the Long Call Audit method to employ.

The default value is INFO Ping.

Minimum Session Interval (RFC4028 Min-SE)

The minimum value for the session interval that the application can accept. RFC 4028 recommends Min-SE value of 90 seconds.


Session Expires Value (RFC4028)

The time that an element considers the call timed out, if no successful refresh transaction occurs beforehand. When enabled with reINVITE or UPDATE as the LCA type, this value is inserted into every INVITE and UPDATE transaction in the RFC4028 Session-Expires header unless it was configured to 0.


Session On Hold Teardown Delay (sec)

Number of seconds a session can be on hold before being terminated. A value of 0 Indicates no termination.







SIP Response Code When System/Application Locked

SIP Response Code to return when the system or application is locked or out of service.


SIP TCP Port SIP TCP listening port.


SIP TLS Port SIP TLS listening port.


SIP UDP Port SIP UDP listening port.


Trusted Node Access Only Prevents traffic from untrusted nodes. The call attempt is redirected with a 305 Use Proxy message if a default proxy is configured. Otherwise, the call attempt is rejected with the 603 Decline message.







Viewing SIP trusted nodesThe MAS processes traffic only from SIP trusted nodes. Use this procedure to view SIP trusted nodes in the MAS Console.

Procedure steps

Step Action


2 In the Trusted Nodes window, double-click each trusted node to view the trusted node properties.

--End--





Configuring QoS settingsUse this procedure to configure QoS settings in the MAS Console.

Procedure steps

Step Action

1 In the MAS Console, select Configuration > Media Settings.

2 In the Media Settings window, double-click each QoS setting to configure.



--End--

Procedure job aidYou can configure the following settings for QoS in the MAS Console.

Property Type of Setting Description

QOS DSCP Audio Value Flow specification Differentiated Service Code Point (DSCP) marking for SIP IP Packets.

QOS DSCP Video Value Flow specification Differentiated Service Code Point (DSCP) marking for audio IP Packets.

QOS Maximum Bandwidth Per H.263 Video Flow (Bytes)

Flow specification The QOS maximum bandwidth for H.263 video flow in bytes.


QOS Maximum Bandwidth Per NNVC Video Flow (Bytes)

Flow specification The QOS maximum bandwidth for NNVC video flow in bytes.


QOS Monitoring VQMON agent for QoS monitoring and RTCP-XR support

Enable or disable QoS monitoring and reporting.





QOS Monitoring Critical R Threshold (%)

VQMON agent for QoS monitoring and RTCP-XR support

The R-factor threshold that generates a critical alert when this threshold is crossed.

The default value is 70%.

QOS Monitoring Warning R Threshold (%)


The R-factor threshold that generates a warning alert when the threshold is crossed.

The default value is 80%

QOS Monitoring Maximum Alerts


The maximum number of alerts that can be generated during a particular interval (QOS Monitoring Alert Interval). This property is used to reduce network traffic.


QOS Monitoring Alert Interval (sec)


Assigns the minimum time between QoS alert monitoring (the alert refresh interval).


QOS Monitoring Refresh Interval (sec)

Do not modify this setting.


Assigns the minimum time between QOS statistic reporting.

The default value is 15 seconds. Do not modify this setting.

Property Type of Setting Description

Nortel Media Application Server 6.0 for AS 5300

CommissioningCopyright © 2008-2009 Nortel Networks. All Rights Reserved.Sourced in Canada and the United States.

Publication: NN44470-301Document status: StandardDocument issue: 01.03Document date: 04 March 2009Product release: Release 6.0Job function: Installation and CommissioningType: NTPLanguage type: English

LEGAL NOTICEThis document contains Nortel confidential and proprietary information. It is not to be copied, disclosed or distributed in any manner, in whole or in part, without Nortel’s express written authorization. While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice.

Nortel, the Nortel logo and the Globemark are trademarks of Nortel Networks.Microsoft Windows Server 2003, Microsoft Event Viewer, and Microsoft Management Console aretrademarks of Microsoft Corporation.All other trademarks are the property of their respective owners.

To provide feedback or report a problem with this document, go to www.nortel.com/documentfeedback.

http://www.avaya.com/documentfeedback

Documents

Commissioning - Avaya Support