MAS Installation and Commissioning

Transcription

1 MAS Installation and Commissioning NN

2 Document status: Standard Document version: 0113 Document date: 8 November 2007 All Rights Reserved Sourced in Canada The information in this document is subject to change without notice The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty Users must take full responsibility for their applications of any products specified in this document The information in this document is proprietary to Nortel Networks Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks IBM, Lotus, Lotus Notes, BladeCenter and BladeCenter T are trademarks of International Business Machines Microsoft, and Windows are trademarks of Microsoft Cisco is a trademark of Cisco Systems Inc All other trademarks are the property of their respective owners

3 3 Revision history November 2007 Standard 0113 This document is up-issued to address CR Q September 2007 Standard 0112 This document is up-issued to address CR Q August 2007 Standard 0111 This document is up-issued to address CR Q July 2007 Standard 0110 This document is up-issued to support the MAS 40 alignment program June 2007 Standard 0108 Updated document to correct minor issue with reference to DC power May 2007 Standard 0107 This document is up-issued to support multiapplication MAS March 2007 Standard 0106 This document is up-issued to support Multimedia Communication Server 5100 Release 40 This document addresses CR Q , Q , Q , and Q January 2007 Standard 0101 This document is issued to support Multimedia Communication Server 5100 Release 40 NN Standard 40 8 November 2007

4 4 Revision history NN Standard 40 8 November 2007

5 5 Contents New in this release 13 Features 13 BCP/MAS co-residency 13 BCT for MAS 14 IBM x MAS OAM/fault integration 14 MAS Radvision support 14 MAS Web Collaboration multilingual support 14 Meet Me enhancements 15 Other changes 15 How to get help 17 Finding the latest updates on the Nortel Web site 17 Getting help from the Nortel Web site 17 Getting help over the phone from a Nortel Solutions Center 17 Getting help from a specialist by using an Express Routing Code 18 Getting help through a Nortel distributor or reseller 18 Regulatory and license information 19 Red Hat Software 19 Safety information 20 Overview 23 Hardware platform 23 BCP/MAS co-residency 24 Operating system (OS) 24 MAS services 25 MAS software installation and upgrade requirements 25 MAS service installation types and road maps 26 Single service instances 26 Multiple service instance installation 34 MAS service upgrades 35 Related documents 36 IBM BladeCenter T installation and commissioning 37 Installation overview 37 Installation roadmap 37 NN Standard 40 8 November 2007

6 6 Contents Prerequisites 38 IP network topology 38 IP address resource allocation 38 Blade service configuration 39 Management module 39 Cable the management module 39 Configure the management module 40 Connect to the management module Web interface 42 Management module firmware version 43 Management module configuration 45 Restart the management module 46 Backup the management module configuration 46 Restore the management module configuration 47 Ethernet Switch Module 48 Cable the ESM 48 Configure the ESM IP address 50 Connect to the ESM Web interface 51 Determine the ESM software version 52 Configure the ESM 53 Configure VLANs 55 SNMP configuration 56 Restart the ESM 56 HS20 BladeServer 57 Determine the BladeServer firmware version 57 Disable local power control 64 Load the operating system image 65 Load the MAS application on the Blade 65 MAS operating system configuration 67 MAS Platform installation 71 MAS service installation 75 Multiapplication MAS deployment 77 Port limits 78 Multiapplication MAS installation 78 Management Console 79 Common procedures 81 Start the Media Application Server Management Console 81 Access the MAS Console using RDP (alternate method) 81 Deactivate the Media Application Server 82 Start the MAS to provide service 82 Lock the MAS 83 Check for active sessions on the MAS 85 End an active session on the MAS 85 NN Standard 40 8 November 2007

7 Contents 7 Unlock the MAS 85 Configure MAS services on the System Management Console 86 Enable service access to the MAS service 87 Create a Terminal Services install disk 90 MAS Ad Hoc Conferencing service 93 Configure the MAS Platform and MAS Ad Hoc Conferencing service 93 Configure MAS Ad Hoc Conferencing 97 MAS Announcements service 101 Configure the MAS platform and MAS Announcements service 101 Domain-level language support for Announcements 105 Place treatment or source files on a MAS 105 Place announcement files on a server that can be accessed by the Announcement MAS 106 Transfer and configure the announcements 106 Custom voice prompts 114 MAS IM Chat service 123 Configure the MAS platform and MAS IM Chat service 123 MAS Meet Me Conferencing service 127 Configure the MAS platform and the MAS Meet Me Conferencing service 127 Configuring hold music 138 Configure Meet Me Conferencing 139 Configure audio recording 142 Configure user-specific Meet Me Conferencing service data 142 Meet Me Conferencing and Web Collaboration 144 MAS Music On Hold service 147 Configure the MAS platform and MAS Music on Hold service 147 Place music files on a MAS Music on Hold 151 Place music files on a server that can be accessed by the Music on Hold Media Application Server 152 Enable service access to the Music on Hold service 154 MAS Meet Me Web Collaboration service 157 Installation overview 157 Installation requirements 158 Web Collaboration scaled installation 159 MAS software 162 Security configuration 163 Web Collaboration server ports 163 Install the Meet Me Web Collaboration server 163 Preinstallation downloads 163 Configure network IP addresses and port filtering 164 Install Network Services 165 Configure Local Security Policy settings 166 NN Standard 40 8 November 2007

8 8 Contents Install Microsoft Internet Explorer 168 Install Microsoft Internet Information Services 169 Install Microsoft Office Install Microsoft SQL Server Desktop Engine 171 Install SSL (optional) 172 Install the Web Collaboration Server software 178 Configure Web Collaboration Administration 179 Modify the license key after installation 180 Install Web Collaboration on the Meet Me Conferencing server 180 Web Collaboration upgrades 181 Upgrade Web Collaboration from Release 3x to Release Web Server Security Hardening (optional) 183 Enable Web Collaboration on the MCS 184 Configure Web Collaboration in the Service Package 184 Reinstalling the Windows Server 2003 operating system 185 MAS services upgrades 187 General information about MAS software upgrades 187 Media Application Server services upgrades 187 Supported software upgrade paths 188 Upgrade to Release 4x software upgrade procedures 188 MAS upgrade 189 Multiapplication MAS upgrade procedures 192 MAS registration and keycodes 195 Overview 195 Register your MCS system and generate keycodes 195 Generate keycodes for a Media Application Server 207 Expand a system by adding a Media Application Server 216 Changing MAS hardware 227 Hardware replacement 227 Fault management 229 MAS fault management strategy 229 MAS OAM/Fault Integration 229 Maintenance 231 Change the hostname after initial deployment 231 BCT configuration worksheet 233 Appendix A DivX Multipoint Video conferencing 237 Network Engineering 237 Overview 237 Upgrades 242 Fault Management 242 Configuration Management 243 Accounting 244 NN Standard 40 8 November 2007

9 Contents 9 Performance Management 244 Security and Administration 245 Configuration 245 Setting video switching 245 Configuring the Meet Me conferencing service 246 Configure the Ad Hoc conferencing service 248 Assign video for the Meet Me conferencing service in a domain 250 Add video to a Meet Me conferencing service package 252 Enabling Ad Hoc video conferencing for a domain 253 User Guide 253 Appendix B BCP Installation on the IBM BladeCenter T Platform 255 Configuration information 256 Other required information 256 Installing the BCP software 256 Beginning the BCP Installation 257 Final steps 262 Tables Table 1 Treatment reasons list in Available Reasons field 111 Table 2 Branding for calls between users within subdomains of a domain 114 Table 3 List of MCS voice prompts in the English l16 directory 117 Table 4 BCT worksheet 233 Table 5 Network bandwidth guidelines 241 Table 6 MCS network component dependencies 242 Table 7 Operational measurements for video 244 Table 8 Information required for installation and commissioning on the BCT platform 256 Procedures Procedure 1 Road map to single MAS service installation 26 Procedure 2 Road map for multiapplication MAS installation 28 Procedure 3 Road map to duplex MAS service installation 30 Procedure 4 Road map to n-way MAS service installation 33 Procedure 5 Road map to MAS multiple service instance installation 34 Procedure 6 Road map for BCT installation and commissioning 38 Procedure 7 Attaching the Ethernet cable 40 Procedure 8 Configuring the management module for the network 41 Procedure 9 Connecting to the management module Web interface 42 Procedure 10 Determining the management module firmware version 43 Procedure 11 Updating the management module firmware 44 Procedure 12 Configuring the external and internal management module network interfaces 45 Procedure 13 Restarting the management module from the management module Web interface 46 Procedure 14 Backing up the management module configuration using the Web interface 46 Procedure 15 Restoring the management module configuration file 47 NN Standard 40 8 November 2007

10 10 Contents Procedure 16 Configuring the ESM IP address 50 Procedure 17 Connecting to the ESM Web interface 51 Procedure 18 Connecting to the ESM Web interface using the management module 52 Procedure 19 Determining the ESM software version 52 Procedure 20 Configuring the ESM through the management module Web interface 53 Procedure 21 Accessing general switch properties 54 Procedure 22 Configuring the external ports 55 Procedure 23 Configuring the trunk groups 55 Procedure 24 Configuring VLANS 56 Procedure 25 Restarting the ESM 56 Procedure 26 Determining the BladeServer firmware version 57 Procedure 27 Updating the Windows BladeServer firmware 58 Procedure 28 Updating the Linux BladeServer firmware 60 Procedure 29 Disabling local power control 64 Procedure 30 Preparing to load or install the MAS application 65 Procedure 31 Configuring MAS OS for your network 67 Procedure 32 Installing the Media Application Server platform 71 Procedure 33 Installing the MAS service software 75 Procedure 34 Installing multiple applications 78 Procedure 35 Connecting to the MAS Console using RDP 82 Procedure 36 Deactivating and verifying offline state of the MAS and MAS service 82 Procedure 37 Starting the MAS 83 Procedure 38 Delayed locking of the MAS 84 Procedure 39 Immediate locking of the MAS 84 Procedure 40 Ending an active session 85 Procedure 41 Unlocking the MAS 86 Procedure 42 Configuring the component information on the System Management Console 86 Procedure 43 Creating a pooled entity for a MAS service 87 Procedure 44 Configuring Routable Services information for MAS service pooled entity 89 Procedure 45 Enabling MAS service in the end user service packages 89 Procedure 46 Creating the Terminal Service install disk 91 Procedure 47 Configuring the MAS platform and MAS Ad Hoc Conferencing service 93 Procedure 48 Configuring the routable services information for Ad Hoc logical entity 97 Procedure 49 Adding the Ad Hoc Conferencing service to the domain 98 Procedure 50 Enabling the Ad Hoc Conferencing service in the service packages 98 Procedure 51 Configuring the MAS platform and Announcements service parameters 101 Procedure 52 Configuring the duplex MAS platform and Announcements service parameters 104 Procedure 53 Configuring the locale (or language) of your announcements 105 Procedure 54 Logging on to the Announcements MAS 107 NN Standard 40 8 November 2007

11 Contents 11 Procedure 55 Transferring announcement files to the Announcement MAS 107 Procedure 56 Configuring the announcement files on the MAS 108 Procedure 57 Configuring treatment routable services information for the Announcement logical entity 110 Procedure 58 Configuring branding routable services information for the Announcement logical entity 113 Procedure 59 Replacing existing MCS voice prompts with custom prompts 116 Procedure 60 Configuring the MAS platform and MAS IM Chat service 123 Procedure 61 Configuring the MAS platform on all Meet Me servers 128 Procedure 62 Configuring the MAS platform on the second Meet Me Procedure 63 server 130 Configuring the MAS platform on the n-way Meet Me servers 133 Procedure 64 Configuring MAS Meet Me Conferencing 136 Procedure 65 Adding wav files for hold music 139 Procedure 66 Create an alias for Meet me pooled entity 140 Procedure 67 Configure domain parameters for Meet Me Conferencing service 140 Procedure 68 Add Meet Me Conferencing service to domain 141 Procedure 69 Configuring the audio recording feature 142 Procedure 70 Provisioning Meet Me Conferencing service user-specific data 143 Procedure 71 Installing the Meet Me Web Collaboration software 144 Procedure 72 Configuring the Meet Me Web Collaboration software 145 Procedure 73 Provisioning Meet Me Web Collaboration service user-specific data 145 Procedure 74 Configuring the Media Application Server platform 147 Procedure 75 Configuring the additional parameters for the duplex Media Application Server platform 149 Procedure 76 Logging on to the Music on Hold MAS 152 Procedure 77 Transferring music files to the Music on Hold MAS 152 Procedure 78 Configuring the music files on the Media Application Server 153 Procedure 79 Configuring Routable Services information for the Music on Hold logical entity 154 Procedure 80 Enabling the Music on Hold service in the end user service packages 156 Procedure 81 Downloading Internet Explorer 60 and MSDE 164 Procedure 82 Configuring network IP addresses and port filtering 164 Procedure 83 Installing Network Services 166 Procedure 84 Configuring Local Security Policy settings 166 Procedure 85 Installing Internet Explorer Procedure 86 Installing IIS for Windows 2000 Server 169 Procedure 87 Installing IIS for Windows Server Procedure 88 Installing Microsoft Office Procedure 89 Installing MSDE 171 Procedure 90 Creating the server1ssl certificate request 172 Procedure 91 Obtaining the server1sslcer certificate 173 NN Standard 40 8 November 2007

12 12 Contents Procedure 92 Installing the server1ssl security certificate 174 Procedure 93 Creating the server2ssl certificate request 174 Procedure 94 Obtaining the server2sslcer certificate 175 Procedure 95 Installing the server2ssl certificate 176 Procedure 96 Adding the certificates to the system 176 Procedure 97 Installing the Web Collaboration Server software 178 Procedure 98 Configuring Web Collaboration Administration 179 Procedure 99 Modifying the license key after installation 180 Procedure 100 Installing Web Collaboration on the Meet Me Conferencing server 180 Procedure 101 Upgrading the server software 181 Procedure 102 Upgrading from Release 3x to Release Procedure 103 Securing the Microsoft IIS Web Server 183 Procedure 104 Enabling Web Collaboration on the Meet Me Conferencing server 184 Procedure 105 Configuring Web Collaboration in the Service Package 184 Procedure 106 Reinstalling the operating system 185 Procedure 107 Backup system configuration data on the existing MAS 189 Procedure 108 Upgrading the MAS 190 Procedure 109 Registering your MCS system and generating keycodes 196 Procedure 110 Generating Media Application Server keycodes 207 Procedure 111 Adding an additional Media Application Server to your system 216 Procedure 112 Replacing or upgrading the hardware 227 Procedure 113 Changing the hostname 231 Procedure 114 Configuring Video Switching Hysteresis 245 Procedure 115 Enabling video for Meet Me conferencing 247 Procedure 116 Configuring the Ad Hoc conferencing service 249 Procedure 117 Assigning video for the Meet Me conferencing service in a domain 250 Procedure 118 Creating a new service package with video 252 Procedure 119 Adding video to an existing service package 253 Procedure 120 Beginning the BCP install process 257 Procedure 121 Restoring a system data backup archive 259 Procedure 122 Restoring a full service data backup 259 Procedure 123 Restoring a partial service data backup 260 Procedure 124 Finishing the BCP installation 262 NN Standard 40 8 November 2007

13 13 New in this release The following sections detail what is new in MAS Installation and Commissioning (NN ) for Release 40 "Features" (page 13) "Other changes" (page 15) Features See the following sections for information about feature changes: "BCP/MAS co-residency" (page 13) "BCT for MAS" (page 14) "IBM x3550" (page 14) "MAS OAM/fault integration" (page 14) "MAS Radvision support" (page 14) "MAS Web Collaboration multilingual support" (page 14) "Meet Me enhancements" (page 15) The following sections summarize the impact of each feature on the Media Application Server (MAS) and MAS applications BCP/MAS co-residency This feature enables the Border Control Point (BCP) and Media Application Server (MAS) applications to co-reside in the same IBM BladeCenter T chassis For example, you can use the same chassis for BCP, MAS Ad Hoc Conferencing, and MAS Announcements at the same time Each application runs on its own server card (known as a blade) in the chassis Co-residency reduces hardware costs and provides a flexible growth strategy for existing systems NN Standard 40 8 November 2007

14 14 New in this release BCT for MAS This feature provides the evolution of the Media Application Server to the IBM BladeCenter T chassis which is NEBS-3-/ETSI-compliant Network Equipment Building System 3 (NEBS-3) compliant hardware adheres to strict requirements for withstanding high temperatures, violent shaking, lightning strikes, airborne contaminants, fires and electrostatic discharge CAUTION Install only Nortel-certified software on the IBM BladeCenter T Do not install software updates obtained directly from IBM IBM x3550 The MAS platform is now supported on the IBM x3550 server The IBM x3550 is a direct replacement for the IBM x336 and comes with Windows Server 2003 preloaded MAS OAM/fault integration This feature provides the integration of the log and alarm notifications from MAS into the MCS Fault and Performance Manager (FPM) Provisioning the MAS servers on the MCS system allows the management server to receive logs and alarms from the MAS, increasing the visibility of MAS problems When the FPM restarts, it queries the alarm state of each MAS server configured on the MCS and reflects the state of each server on the System Management Console You can configure the FPM to request periodic updates to the MAS alarm state is provided, to ensure synchronization between the MCS and MAS MAS Radvision support This feature covers internal changes to the MCS 5100 software and is related to the Radvision (RV) Stack Integration feature The feature is internal to the MCS and has no user impacts MAS Web Collaboration multilingual support With the MAS Web Collaboration multilingual support feature, the Web Collaboration service can support multiple languages The Web Collaboration user interface and the prompts are available in multiple languages The MAS Web Collaboration service supports the following languages: English Parisian French NN Standard 40 8 November 2007

15 Other changes 15 German Latin America Spanish Japanese Korean Simplified Chinese Traditional Chinese Portuguese Meet Me enhancements This feature provides enhanced usability and management capabilities to the MAS Meet Me Conferencing service The introduction of an operator gives increased management of Meet Me conferences by allowing the operator to control the individual calls (mute, unmute, terminate) The operator can control the meeting in the same manner as a chairperson Additional features enable the chairperson and the participants to perform the following tasks: start the conference before the chairperson arrives assume the role of the chair after the chairperson leaves call the operator without leaving the conference The MAS Meet Me Conferencing service provides the ability to create an audio recording of a conference The chairperson or operator requests that the audio recording start and stop The resulting audio files are sent to the chairperson by Other changes This document is new for MCS 5100 Release 40 It contains information and procedures previously located in the MCS 5100 Release 35 MAS Services Guides NN Standard 40 8 November 2007

16 16 New in this release NN Standard 40 8 November 2007

17 17 How to get help This chapter explains how to get help for Nortel products and services Finding the latest updates on the Nortel Web site The content of this documentation was current at the time the product was released To check for updates to the latest documentation for Multimedia Communication System (MCS) 5100, go to wwwnortelcom and navigate to the Technical Documentation page for MCS 5100 Getting help from the Nortel Web site The best way to get technical support for Nortel products is from the Nortel Technical Support Web site: wwwnortelcom/support This site provides access to software, documentation, bulletins, and tools to address issues with Nortel products From this site, you can: download software, documentation, and product bulletins search the Technical Support Web site and the Nortel Knowledge Base for answers to technical issues arrange for automatic notification of new software and documentation for Nortel equipment open and manage technical support cases Getting help over the phone from a Nortel Solutions Center If you do not find the information you require on the Nortel Technical Support Web site, and you have a Nortel support contract, you can also get help over the telephone from a Nortel Solutions Center In North America, call NORTEL ( ) Outside North America, go to the following Web site to obtain the telephone number for your region: wwwnortelcom/callus NN Standard 40 8 November 2007

18 18 How to get help Getting help from a specialist by using an Express Routing Code To access some Nortel Technical Solutions Centers, you can use an Express Routing Code (ERC) to quickly route your call to a specialist in your Nortel product or service To locate the ERC for your product or service, go to: wwwnortelcom/erc Getting help through a Nortel distributor or reseller If you purchased a service contract for your Nortel product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller NN Standard 40 8 November 2007

19 19 Regulatory and license information This chapter contains regulatory and license information Red Hat Software Passthrough End User License Agreement This section governs the use of the Red Hat Software and any updates to the Red Hat Software, regardless of the delivery mechanism and is governed by the laws of the state of New York in the USA The Red Hat Software is a collective work under US Copyright Law Subject to the following terms, Red Hat, Inc ("Red Hat") grants to the user ("Customer") a license to this collective work pursuant to the GNU General Public License Red Hat Enterprise Linux (the "Red Hat Software") is a modular operating system consisting of hundreds of software components The end user license agreement for each component is located in the component s source code With the exception of certain image files identified below, the license terms for the components permit Customer to copy, modify, and redistribute the component, in both source code and binary code forms This agreement does not limit Customer s rights under, or grant Customer rights that supersede, the license terms of any particular component The Red Hat Software and each of its components, including the source code, documentation, appearance, structure and organization are owned by Red Hat and others and are protected under copyright and other laws Title to the Red Hat Software and any component, or to any copy, modification, or merged portion shall remain with the aforementioned, subject to the applicable license The "Red Hat" trademark and the "Shadowman" logo are registered trademarks of Red Hat in the US and other countries This agreement does not permit Customer to distribute the Red Hat Software using Red Hat s trademarks If Customer makes a commercial redistribution of the Red Hat Software, unless a separate agreement with Red Hat is executed or other permission granted, then Customer must modify any files identified as "REDHAT-LOGOS" and "anaconda-images" to remove all images containing the "Red Hat" trademark or the "Shadowman" logo As required by US law, Customer represents and warrants that it: (a) understands that the Software is subject to export controls under the US Commerce Department s Export Administration Regulations ("EAR"); NN Standard 40 8 November 2007

20 20 Regulatory and license information (b) is not located in a prohibited destination country under the EAR or US sanctions regulations (currently Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria); (c) not export, re-export, or transfer the Software to any prohibited destination, entity, or individual without the necessary export license(s) or authorizations(s) from the US Government; (d) not use or transfer the Red Hat Software for use in any sensitive nuclear, chemical or biological weapons, or missile technology end-uses unless authorized by the US Government by regulation or specific license; (e) understands and agrees that if it is in the United States and exports or transfers the Software to eligible end users, it, as required by EAR Section 74017(e), submit semi-annual reports to the Commerce Department s Bureau of Industry & Security (BIS), which include the name and address (including country) of each transferee; and (f) understands that countries other than the United States may restrict the import, use, or export of encryption products and that it shall be solely responsible for compliance with any such import, use, or export restrictions Red Hat may distribute third party software programs with the Red Hat Software that are not part of the Red Hat Software These third party programs are subject to their own license terms The license terms either accompany the programs or can be viewed at If Customer does not agree to abide by the applicable license terms for such programs, then Customer may not install them If Customer wishes to install the programs on more than one system or transfer the programs to another party, then Customer must contact the licensor of the programs If any provision of this agreement is held to be unenforceable, that shall not affect the enforceability of the remaining provisions Copyright 2003 Red Hat, Inc All rights reserved "Red Hat" and the Red Hat "Shadowman" logo are registered trademarks of Red Hat, Inc "Linux" is a registered trademark of Linus Torvalds All other trademarks are the property of their respective owners WARNING Do not contact Red Hat for technical support on your Nortel version of the Linux base operating system If you require technical support for the Nortel version of the Linux base operating system, contact Nortel technical support through your regular channels Safety information This section contains important safety information NN Standard 40 8 November 2007

21 Safety information 21 NN Standard 40 8 November 2007

22 22 Regulatory and license information NN Standard 40 8 November 2007

23 23 Overview WARNING Do not contact Red Hat for technical support on your Nortel version of the Linux base operating system If technical support is required for the Nortel version of the Linux base operating system, contact Nortel technical support through your regular channels This chapter gives an overview of the hardware platform options, operating system, co-residency, installation, configuration and upgrading of the Media Application Server (MAS) Hardware platform When selecting the hardware platform for a Media Application Server, you must consider several factors, such as the engineering requirements of your network and the services that you plan to run on the MAS The Media Application Server supports the following hardware platforms: small-to-medium system (IBM xseries 3550, IBM xseries 336, or IBM xseries 335) large system (IBM eserver BladeCenter or IBM BladeCenter T chassis, equipped with HS20 Blade servers) In general, install only a single service on a Media Application Server (x3550, x335, x336, or HS20 Blade) However, there are exceptions to this rule The Music on Hold and Announcement services can exist on the same Media Application Server Another exception is for a special case of MAS applications running on the IBM x3550, x335, or x336 platform A single MAS hardware platform solves customer needs for cost-effective small implementations of multiple MAS services The multiple application MAS (on an IBM x3550, x335, or x336 hardware platform) can work with the Enterprise micro system to deliver multiple services for up to 250 subscribers (maximum) It can also be used NN Standard 40 8 November 2007

24 24 Overview as a service evaluation platform in 4-server and 8-server configurations For more information about installing multiple applications on a single MAS, see "Multiapplication MAS deployment" (page 77) Border Control Point (BCP), and MAS applications can co-reside in the same BladeCenter T (BCT) chassis The BCP and MAS applications run on separate HS20 Blades For more information about this option, see "BCP/MAS co-residency" (page 24) For more information about the hardware, see Media Application Server Planning and Engineering (NN ) BCP/MAS co-residency Both the Border Control Point (BCP) and Media Application Server (MAS) applications can co-reside in the same BCT chassis The resulting BCP and MAS co-residency provides an enhanced solution for initial deployments (including internal lab environments) and for a more flexible growth strategy for existing deployments The BCT chassis is used as a pooled resource for either BCP or MAS components to optimize chassis capacity, reducing the number of chassis required in some deployments For more information about co-residency, see Media Application Server Planning and Engineering (NN ) Co-residency of BCP and MAS applications is governed by the following rules: BCP applications are populated starting at blade 1 of the chassis, and working down the chassis MAS applications are populated starting at blade 8 of the chassis, and working up the chassis When more than eight applications are required, additional BCTs can be added to the system ATTENTION After an HS20 Blade is configured as a MAS server, it cannot be reconfigured as a BCP at the customer site The server must be returned to Nortel for repair Operating system (OS) The IBM x3550 server comes preinstalled and preconfigured with a MAS-hardened Windows Server 2003 image IBM x335 and x336 servers come preinstalled and preconfigured with a standard MAS-hardened Windows 2000 Server image NN Standard 40 8 November 2007

25 MAS software installation and upgrade requirements 25 The HS20 Blades for MAS the BladeCenter T or ebladecenter come preinstalled and preconfigured with a standard MAS-hardened Windows 2000 Server image Blades for the Border Control Point come preinstalled and preconfigured with a standard BCP-hardened Linux image MAS services The MAS services consist of the following services: Ad Hoc Conferencing service for more information, see MAS Ad Hoc Conferencing Fundamentals (NN ) Announcements service for more information, see MAS Announcements Fundamentals (NN ) IM Chat service for more information, see MAS IM Chat Fundamentals (NN ) Meet Me Conferencing service for more information, see MAS Meet Me Conferencing Fundamentals (NN ) Music on Hold service for more information, see MAS Music on Hold Fundamentals (NN ) Web Collaboration service for more information, see MAS Meet Me Web Collaboration Fundamentals (NN ) Note: In some of the configuration displays, the Unified Communications service appears MCS 5100 does not support Unified Communications, so these parameters are ignored MAS software installation and upgrade requirements Before you can install or upgrade the MAS software, you need the following: MAS hardware ATTENTION You must install and configure the BCT using "IBM BladeCenter T installation and commissioning" (page 37), before you install the software on the Blade servers MAS installation CDs Table 4 "BCT worksheet" (page 233) if installing MAS in a BCT MCS 5100 Release Notes Media Application Server Planning and Engineering (NN ) MCS Planning and Engineering (NN ) NN Standard 40 8 November 2007

26 26 Overview CAUTION Failure to install You must follow the installations in the order specified in the road map procedures MAS service installation types and road maps The following subsections outline the differences in the installation procedures used to install and configure the Media Application Server services for "Single service instances" (page 26) (one service node) "Multiple service instance installation" (page 34) (multiple pooled entities) ATTENTION The process for installing and configuring the MAS Web Collaboration service differs from the other MAS services Single service instances Single service instances involve the MAS as a single service node "Simplex deployment installation " (page 26) "Simplex deployment installation for multiapplication MAS" (page 28) "Duplex deployment installation" (page 29) "n-way deployment installation" (page 31) Simplex deployment installation A simplex deployment refers to one MAS service for each MAS server Simplex MAS service installation road map To install the Web Collaboration service in a simplex architecture, see "MAS Meet Me Web Collaboration service" (page 157) To install the other MAS services in a simplex architecture, follow Procedure 1 "Road map to single MAS service installation" (page 26) Procedure 1 Road map to single MAS service installation Step Action 1 "MAS registration and keycodes" (page 195) 2 "MAS operating system configuration" (page 67) NN Standard 40 8 November 2007

27 MAS service installation types and road maps 27 3 "MAS Platform installation" (page 71) 4 "MAS service installation" (page 75) 5 "Start the Media Application Server Management Console" (page 81) 6 "Deactivate the Media Application Server" (page 82) 7 For the MAS Ad Hoc Conferencing service, configure the MAS platform and service as described in "Configure the MAS Platform and MAS Ad Hoc Conferencing service" (page 93) 8 For the MAS Announcements service, configure the MAS platform and service as described in "Configure the MAS platform and MAS Announcements service" (page 101) 9 For the MAS IM Chat service, configure the MAS platform and service as described in "Configure the MAS platform and MAS IM Chat service" (page 123) 10 For the MAS Meet Me Conferencing service, configure the MAS platform and service as described in "Configure the MAS platform and the MAS Meet Me Conferencing service" (page 127) 11 For the MAS Music on Hold service, configure the MAS platform and service as described in "Configure the MAS platform and MAS Music on Hold service" (page 147) 12 "Start the MAS to provide service" (page 82) 13 For the MAS Music on Hold service, configure the music files as described in Procedure 78 "Configuring the music files on the Media Application Server" (page 153) 14 "Configure MAS services on the System Management Console" (page 86) 15 "Enable service access to the MAS service" (page 87) 16 For the MAS Ad Hoc Conferencing service, perform Procedure 49 "Adding the Ad Hoc Conferencing service to the domain" (page 98) 17 For the MAS Meet Me Conferencing service, perform Procedure 68 "Add Meet Me Conferencing service to domain" (page 141) 18 For the MAS Meet Me Conferencing service, "Configure user-specific Meet Me Conferencing service data" (page 142) End NN Standard 40 8 November 2007

28 28 Overview Simplex deployment installation for multiapplication MAS The multiapplication MAS deployment enables you to install the following MAS services on the same server: Ad Hoc Conferencing service Meet Me Conferencing service Music on Hold service Announcements service IM Chat service ATTENTION The MAS Web Collaboration service cannot be deployed in a multiapplication MAS For a multiapplication MAS deployment, you can install from two to five MAS services on the same MAS platform You can install the MAS services in any order To install the multiapplication MAS, follow Procedure 2 "Road map for multiapplication MAS installation" (page 28) Procedure 2 Road map for multiapplication MAS installation Step Action 1 "MAS registration and keycodes" (page 195) 2 "MAS operating system configuration" (page 67) 3 "MAS Platform installation" (page 71) 4 Install the required service software (for MAS Ad Hoc, Meet Me, Music on Hold, Announcements, and IM Chat), one after another, as described in"multiapplication MAS installation" (page 78) ATTENTION Do not perform a restart of the Windows operating system until you finish installing the last MAS service 5 After you install all of the MAS services, restart the Windows operating system 6 "Start the Media Application Server Management Console" (page 81) 7 "Deactivate the Media Application Server" (page 82) NN Standard 40 8 November 2007

29 MAS service installation types and road maps 29 8 For the MAS Ad Hoc Conferencing service, configure the MAS platform and service as described in "Configure the MAS Platform and MAS Ad Hoc Conferencing service" (page 93) 9 For the MAS Announcements service, configure the MAS platform and service as described in "Configure the MAS platform and MAS Announcements service" (page 101) 10 For the MAS IM Chat service, configure the MAS platform and service as described in "Configure the MAS platform and MAS IM Chat service" (page 123) 11 For the MAS Meet Me Conferencing service, configure the MAS platform and service as described in "Configure the MAS platform and the MAS Meet Me Conferencing service" (page 127) 12 For the MAS Music on Hold service, configure the MAS platform and service as described in "Configure the MAS platform and MAS Music on Hold service" (page 147) 13 "Start the MAS to provide service" (page 82) 14 For the MAS Music on Hold service, configure the music files as described in Procedure 78 "Configuring the music files on the Media Application Server" (page 153) 15 "Configure MAS services on the System Management Console" (page 86) 16 "Enable service access to the MAS service" (page 87) 17 For the MAS Ad Hoc Conferencing service, perform Procedure 49 "Adding the Ad Hoc Conferencing service to the domain" (page 98) 18 For the MAS Meet Me Conferencing service, perform Procedure 68 "Add Meet Me Conferencing service to domain" (page 141) 19 For the MAS Meet Me Conferencing service, "Configure user-specific Meet Me Conferencing service data" (page 142) End Duplex deployment installation No additional mirroring (duplicating) configuration steps are required in non-simplex deployment installations of the MAS services You can use the simplex deployment installation procedure (for each service) when installing the secondary node of a duplex deployment, with one difference When creating a service node for each service, do not create a new MAS service node Instead, edit the existing MAS service logical entity created during NN Standard 40 8 November 2007

30 30 Overview the installation and configuration of the first MAS service node (for example, adhoc_entity) Add a route to the secondary node in the existing service node definition In general, you install and configure each node in the duplex deployment using the same steps as the simplex deployment installation However, duplex deployments require minor adjustments to those installation and configuration procedures, allowing mirroring between the two servers to occur The differences in installation and configuration for duplex deployments are as follows: System configuration parameter mirroring During configuration of the MAS platform software, you must configure additional parameters so the two servers can communicate with each other for mirroring purposes After you configure the simplex system configuration parameters of the MAS platform software, configure the additional platform system configuration parameters that allow mirroring to occur between the two MAS nodes Logical entity reuse When configuring the logical entity datafill for the secondary MAS node, a new pool is not created In Procedure 43 "Creating a pooled entity for a MAS service" (page 87), do not create a new MAS service node Instead, edit the existing MAS service logical entity that was created during installation and configuration of the first MAS service server node (for example, meetme_pool) Add a route to the secondary node in this existing service node definition Procedure 3 Road map to duplex MAS service installation Step Action 1 "MAS registration and keycodes" (page 195) 2 "MAS operating system configuration" (page 67) 3 "MAS Platform installation" (page 71) 4 "MAS service installation" (page 75) 5 "Start the Media Application Server Management Console" (page 81) 6 "Deactivate the Media Application Server" (page 82) 7 For the MAS Ad Hoc Conferencing service, configure the MAS platform and service as described in "Configure the MAS Platform and MAS Ad Hoc Conferencing service" (page 93) NN Standard 40 8 November 2007

31 MAS service installation types and road maps 31 8 For the MAS Announcements service, configure the MAS platform and service as described in "Configure the MAS platform and MAS Announcements service" (page 101) 9 For the MAS IM Chat service, configure the MAS platform and service as described in "Configure the MAS platform and MAS IM Chat service" (page 123) 10 For the MAS Meet Me Conferencing service, configure the MAS platform and service as described in "Configure the MAS platform and the MAS Meet Me Conferencing service" (page 127) 11 For the MAS Music on Hold service, configure the MAS platform and service as described in "Configure the MAS platform and MAS Music on Hold service" (page 147) 12 "Start the MAS to provide service" (page 82) 13 For the MAS Music on Hold service, configure the music files as described in Procedure 78 "Configuring the music files on the Media Application Server" (page 153) 14 "Configure MAS services on the System Management Console" (page 86) 15 "Enable service access to the MAS service" (page 87) 16 For the MAS Ad Hoc Conferencing service, perform Procedure 49 "Adding the Ad Hoc Conferencing service to the domain" (page 98) 17 For the MAS Meet Me Conferencing service, perform Procedure 68 "Add Meet Me Conferencing service to domain" (page 141) 18 For the MAS Meet Me Conferencing service, "Configure user-specific Meet Me Conferencing service data" (page 142) End n-way deployment installation No additional mirroring configuration steps are required in non-simplex deployment installations of the MAS service You can use the simplex deployment installation flowchart (for each MAS service) when installing another node of an n-way deployment, with one difference When creating a service node for each MAS service, do not create a new service node for each MAS service Instead, edit the existing MAS logical entity created during installation and configuration of the first MAS service node (for example, adhoc_entity) Add a route to the new node in the existing logical entity definition NN Standard 40 8 November 2007

32 32 Overview In general, you can install and configure each node in the n-way deployment using the same steps as the simplex deployment installation procedure However, because there can be at most two active content storage components in a scaled service node, you must make minor adjustments to those installation and configuration procedures to allow the following: Content storage mirroring The first two Media Application Server nodes act as the content storage component for the rest of the multiserver deployment Additional parameters must be configured on these two servers so that content storage data can be mirrored between the two nodes Remote content storage access The remaining (third, fourth, or fifth) Media Application Server nodes must be able to access the content stores located on the first two Media Application Server nodes of the scaled service node Disabling local content storage Additional parameters must be configured on the remaining (third, fourth, or fifth) Media Application Server nodes so that their local content storage components are deactivated Expanding the Controller Peer ring When additional nodes are added, the Controller Peer ring of servers must be modified to include the new node The second node of an n-way (up to five) deployment is installed as if the deployment is a duplex deployment These two servers provide the content storage for the entire MAS service logical entity The remaining nodes of an n-way (up to five) deployment are installed and configured using the same steps as described in the simplex deployment installation However, deployment of the third, fourth, or fifth server requires minor adjustments to those installation and configuration procedures, allowing these nodes to access the content storage, located on the first two Media Application Servers of the multiserver deployment The differences in installation and configuration of the third, fourth, and fifth servers in a multiserver deployment are as follows: Content storage remote access configuration During configuration of the Media Application Server platform software, you must configure additional parameters so that the third, fourth, and fifth Media Application Server nodes can communicate with the content storage components located on the first two Media Application Server nodes After you configure the simplex system configuration parameters of the Media Application Server platform software, configure the additional platform system configuration parameters to allow remote access to the content storage components located on the first two Media Application Server nodes of the multiserver deployment NN Standard 40 8 November 2007

33 MAS service installation types and road maps 33 Disabled local content storage The third, fourth, or fifth server nodes do not use their local content storage component; instead they rely on the content storage components hosted by the first two server nodes of the multiserver deployment The MAS services that support n-way deployment describe which system configuration parameters must be changed to disable the local content storage component for the third, fourth, or fifth servers Logical entity reuse When you configure the service node datafill for the third, fourth, or fifth Media Application Server node, do not create a new pool Instead, edit the existing MAS service logical entity that was created during the installation and configuration of the first MAS service server node (for example, meetme_pool) Add a route to the third, fourth, or fifth node in this existing service node definition Procedure 4 Road map to n-way MAS service installation Step Action 1 "MAS registration and keycodes" (page 195) 2 "MAS operating system configuration" (page 67) 3 "MAS Platform installation" (page 71) 4 "MAS service installation" (page 75) 5 "Start the Media Application Server Management Console" (page 81) 6 "Deactivate the Media Application Server" (page 82) 7 For the MAS Ad Hoc Conferencing service, configure the MAS platform and service as described in "Configure the MAS Platform and MAS Ad Hoc Conferencing service" (page 93) 8 For the MAS Announcements service, configure the MAS platform and service as described in "Configure the MAS platform and MAS Announcements service" (page 101) 9 For the MAS IM Chat service, configure the MAS platform and service as described in "Configure the MAS platform and MAS IM Chat service" (page 123) 10 For the MAS Meet Me Conferencing service, configure the MAS platform and service as described in "Configure the MAS platform and the MAS Meet Me Conferencing service" (page 127) 11 For the MAS Music on Hold service, configure the MAS platform and service as described in "Configure the MAS platform and MAS Music on Hold service" (page 147) NN Standard 40 8 November 2007

34 34 Overview 12 "Start the MAS to provide service" (page 82) 13 For the MAS Music on Hold service, configure the music files as described in Procedure 78 "Configuring the music files on the Media Application Server" (page 153) 14 "Configure MAS services on the System Management Console" (page 86) 15 "Enable service access to the MAS service" (page 87) 16 For the MAS Ad Hoc Conferencing service, perform Procedure 49 "Adding the Ad Hoc Conferencing service to the domain" (page 98) 17 For the MAS Meet Me Conferencing service, perform Procedure 68 "Add Meet Me Conferencing service to domain" (page 141) 18 For the MAS Meet Me Conferencing service, "Configure user-specific Meet Me Conferencing service data" (page 142) End Multiple service instance installation In addition to scaling a simplex MAS service instance into a duplex installation, scaling can also be achieved by creating additional MAS service pooled entities Each additional MAS service node can also be scaled as either a simplex or duplex installation Installation procedures for additional service instances are identical to single service installations as outlined in the simplex deployment installation procedure However, to differentiate between service instances, each additional MAS service instance logical entity must have a unique name Procedure 5 Road map to MAS multiple service instance installation Step Action 1 "MAS registration and keycodes" (page 195) 2 "MAS operating system configuration" (page 67) 3 "MAS Platform installation" (page 71) 4 "MAS service installation" (page 75) 5 "Start the Media Application Server Management Console" (page 81) 6 "Deactivate the Media Application Server" (page 82) NN Standard 40 8 November 2007

35 MAS service upgrades 35 7 For the MAS Ad Hoc Conferencing service, configure the MAS platform and service as described in "Configure the MAS Platform and MAS Ad Hoc Conferencing service" (page 93) 8 For the MAS Announcements service, configure the MAS platform and service as described in "Configure the MAS platform and MAS Announcements service" (page 101) 9 For the MAS IM Chat service, configure the MAS platform and service as described in "Configure the MAS platform and MAS IM Chat service" (page 123) 10 For the MAS Meet Me Conferencing service, configure the MAS platform and service as described in "Configure the MAS platform and the MAS Meet Me Conferencing service" (page 127) 11 For the MAS Music on Hold service, configure the MAS platform and service as described in "Configure the MAS platform and MAS Music on Hold service" (page 147) 12 "Start the MAS to provide service" (page 82) 13 For the MAS Music on Hold service, configure the music files as described in Procedure 78 "Configuring the music files on the Media Application Server" (page 153) 14 "Configure MAS services on the System Management Console" (page 86) 15 "Enable service access to the MAS service" (page 87) 16 For the MAS Ad Hoc Conferencing service, perform Procedure 49 "Adding the Ad Hoc Conferencing service to the domain" (page 98) 17 For the MAS Meet Me Conferencing service, perform Procedure 68 "Add Meet Me Conferencing service to domain" (page 141) 18 For the MAS Meet Me Conferencing service, "Configure user-specific Meet Me Conferencing service data" (page 142) End MAS service upgrades MAS upgrades consist of two types: upgrades from one release to another upgrades within a release because of Maintenance Releases of the software NN Standard 40 8 November 2007

36 36 Overview These upgrades are handled the same for all the MAS services For more information about upgrades, see "MAS service upgrades" (page 35) Related documents The Multimedia Communication Server (MCS) documentation suite consists of the following: MCS components Border Control Point Fundamentals (NN ) New in this Release (NN ) MCS 5100 Overview (NN ) MAS components MAS Ad Hoc Conferencing Fundamentals (NN ) MAS Announcements Fundamentals (NN ) MAS IM Chat Fundamentals (NN ) MAS Meet Me Conferencing Fundamentals (NN ) MAS Meet Me Web Collaboration Fundamentals (NN ) MAS Music on Hold Fundamentals (NN ) Engineering guides MCS 5100 Planning and Engineering (NN ) Media Application Server Planning and Engineering (NN ) Installation, commissioning, and upgrade guides MCS Installation Guide (NN ) Operation, administration, maintenance, and performance guides Routine Maintenance (NN ) Alarm and Log Reference (NN ) Operational Measurements Reference (NN ) NN Standard 40 8 November 2007

37 37 IBM BladeCenter T installation and commissioning This chapter describes the installation and commissioning procedures for the BladeCenter T chassis This chapter includes the following sections: "Installation overview" (page 37) "Prerequisites" (page 38) "Management module" (page 39) "Ethernet Switch Module" (page 48) "HS20 BladeServer" (page 57) Installation overview The IBM BladeCenter T (BCT) unit is a rack-mounted, high-density, high-performance bladeserver system developed for Network Equipment Building System (NEBS) telecommunications network applications requiring additional physical robustness beyond the standard BladeCenter unit The BCT unit uses HS20 Blade servers, switches, and other components that are common to the IBM BladeCenter product line There are a number of components that must be installed and configured The basic manuals for the IBM BCT are the IBM Hardware Maintenance Manual, and the IBM Installation and User s Guide The documentation supplied by Nortel describes how this platform is used to implement the Media Application Server For more information about configuring Border Control Point on the IBM BCT platform, see Appendix "BCP Installation on the IBM BladeCenter T Platform" (page 255) and Border Control Point Fundamentals (NN ) Installation roadmap Follow Procedure 6 "Road map for BCT installation and commissioning" (page 38) to install and commission the BCT NN Standard 40 8 November 2007

38 38 IBM BladeCenter T installation and commissioning Procedure 6 Road map for BCT installation and commissioning Step Action 1 "Management module" (page 39) 2 "Ethernet Switch Module" (page 48) 3 "HS20 BladeServer" (page 57) End Prerequisites "IP network topology" (page 38) "IP address resource allocation" (page 38) "Blade service configuration" (page 39) IP network topology For the recommended network setup, the following rules and guidelines apply The BCT management module and Ethernet switch modules must reside on the same subnet The actual IP addresses and subnet mask are subnet-specific and are outside the scope of this document The blade servers should reside on a different subnet from the BCT modules The actual IP addresses and subnet mask for the blades are subnet-specific and are outside the scope of this document The rationale behind this network setup is that the BCT modules reside on a secure management subnet, while the blade servers themselves reside on a normal traffic network Therefore, the management functions of the BCT are not accessible from the normal network IP address resource allocation Before you can configure the BCT modules and blades, a sufficient number of IP addresses must be available The IP address requirements for the various modules and blades are as follows: The primary management module requires two IP addresses, one each for the external and internal interfaces Each Ethernet switch module requires one IP address NN Standard 40 8 November 2007

39 Management module 39 Each HS20 Blade server requires one IP address Note: A dual-slot blade server, despite occupying two slots, requires only one IP address The add-on blade is for storage only Blade service configuration Specific Blade configurations to implement MAS service redundancy are not described in this document Redundancy is handled using BCT hardware redundancy (for example, redundant power supply and management modules) only Management module The management module controls the operations of the IBM BCT chassis and its components There are two types of management modules: regular Management Module (MM) and Advanced Management Module (AMM) The MM version is found only in older systems The AMM version is the Restriction of Hazardous Substances (RoHS) compliant Management Module Note 1: You only configure the primary management module; the secondary management module need not be explicitly configured If the primary management module fails, the secondary management module inherits the configuration from the primary management module Both management modules must connect to the same network subnet Note 2: There are two types of Input/Output (IO) Modules: Nortel Layer 2-3 and Nortel Layer 2-7 Older systems have Layer 2-7; newer systems have Layer 2-3 For more details about installing the management module, see the following sections: "Cable the management module" (page 39) "Configure the management module" (page 40) "Connect to the management module Web interface" (page 42) "Management module configuration" (page 45) "Restart the management module" (page 46) "Backup the management module configuration" (page 46) Cable the management module Cabling the management module involves: "Ethernet port connection" (page 40) "Console port connection" (page 40) NN Standard 40 8 November 2007

40 40 IBM BladeCenter T installation and commissioning Ethernet port connection The management module Ethernet port provides network access to the management functions of the BCT The management module and the Ethernet Switch Modules are reached through this port Procedure 7 Attaching the Ethernet cable Step Action 1 Connect one end of a Category 5 (or higher) Ethernet cable to the Ethernet port on the management module 2 Connect the other end of the Ethernet cable to a switch providing access to a protected management network 3 If the BCT has no power, apply power to start the BladeCenter 4 Check the Ethernet LEDs to ensure the network connection is working Interpret the LEDs as follows: Ethernet link LED: This green LED is lit when there is an active connection through the port to the network Ethernet activity LED: This green LED flashes when there is activity through the port over the network link End Console port connection The console port actually consists of three physical connectors: the keyboard connector, the video connector, and the mouse connector These connectors provide standard PC-style console access to the BladeServers, depending on which BladeServer is selected to have access to the console device Console administration takes place using the remote network console provided by the management module This physical console is convenient for on-site operations Configure the management module If the management module is configured with a site-specific static IP address, skip this section NN Standard 40 8 November 2007

41 Management module 41 If site-specific IP address is not configured, the management module is configured with the correct IP configuration in these sections: "Management module IP reset" (page 41) "IP configuration setup" (page 41) Management module IP reset The management module provides an IP reset button to reset the IP configuration of the management module network interfaces to their factory default settings Use a straightened paper clip to press the recessed button ATTENTION Pressing the IP reset button erases all configured IP addresses for the management module After the reset, the management module loses connection with any switch modules and blade servers Pressing the IP reset button also restarts the management module Note: An IP reset does not reset the management module password IP configuration setup After restarting the BladeCenter management module (and assuming that a site-specific static IP address was not assigned to the management module external network interface), the BladeCenter looks for a Dynamic Host Configuration Protocol (DHCP) server on the network After two minutes, the DHCP search times out and the default static IP configuration for the management module is used The factory default IP configuration settings are: IP address Subnet mask Hostname MMxxxxxxxxxxxx, (where xxxxxxxxxxxx is the burned-in MAC address on the management module) Because the factory default IP address is a non-routable private address, a special network setup is required to configure the management module Procedure 8 Configuring the management module for the network Step Action 1 Unplug the existing Ethernet cable, if present, from the Ethernet port of the management module NN Standard 40 8 November 2007

42 42 IBM BladeCenter T installation and commissioning 2 Connect a network management station (for example, a laptop) directly to the Ethernet port of the management module using a crossover network cable 3 From the network management station, connect to the management module Web interface, using the management module factory default IP address 4 Configure the management module with the required site-specific static IP address configuration 5 Restart the management module 6 Reconnect the original Ethernet cable to the Ethernet port of the management module End Note: If no Ethernet cable was originally present, see "Cable the management module" (page 39) for the necessary management module Ethernet cabling instructions After restarting, the management module is configured with the new IP address To verify the IP address, connect to the management module Web interface from a remote network management station using the newly-configured static IP address Connect to the management module Web interface The management module provides a Web interface for accessing the management functions CAUTION If the management module is not configured with a site-specific static IP address, you must first configure the management module with the correct IP address (see "IP configuration setup" (page 41)) Procedure 9 Connecting to the management module Web interface Step Action At the network management station, 1 Open a Web browser 2 In the search bar, enter NN Standard 40 8 November 2007

43 Management module 43 where xxxxxxxx is the IP address defined for the management module remote interface A window appears, prompting for a user name and password ATTENTION The User Name and Password fields are case-sensitive If the user name or the password are changed from the default values, use the new values instead 3 In the User Name field, enter USERID 4 In the Password field, enter PASSW0RD (using the number zero [0], not the letter O) 5 Click OK The Welcome window appears 6 Enter a timeout value for the current Web session (for security purposes) 7 Click Continue The BladeCenter management and configuration window appears End Management module firmware version Use the management module Web interface to determine the management module firmware version Procedure 10 Determining the management module firmware version Step Action 1 Log on to the management module Web interface 2 On the Monitors menu, click Firmware VPD 3 Scroll to the bottom of the page and examine the firmware files listed in the Management Module Firmware VPD section Ensure that the following three files are listed: CNETBRUSPKT, CNETMNUSPKT, and CNETRGUSPKT NN Standard 40 8 November 2007

44 44 IBM BladeCenter T installation and commissioning 4 Compare the file versions listed with the versions on the approved version list included with the packing materials If the versions do not match, you must update the firmware End Management module firmware updates Run this procedure only if the firmware is out of compliance with the approved firmware list Note: Firmware should be current at the time the hardware leaves the configuration facility Subsequent firmware updates are provided through normal support channels, when necessary Perform the following procedure to update the management module firmware using the management module Web interface Procedure 11 Updating the management module firmware Step Action 1 Log on to the management module Web interface 2 On the MM Control menu, click Firmware Update 3 Click Browse to locate the firmware file to use for the upgrade 4 Click on the applicable PKT file and click Open The file (including the full path) appears in the box beside the Browse button 5 Click Update to begin the update process A progress indicator appears as the file is transferred to temporary storage on the management module 6 Verify that the file type shown on the Confirm Firmware Update page is what you intended to update If not, click Cancel 7 Click Continue to complete the update process A progress indicator appears as the firmware update progresses ATTENTION Remain in this window until the update process is complete and a status page appears to indicate that the update was successful Additional instructions are displayed, if necessary NN Standard 40 8 November 2007

45 Management module 45 8 Repeat step 4 through step 7 for each packet to be updated 9 Restart the management module End Note: This procedure does not affect the BladeServer power status Management module configuration Perform the following procedure to configure the external and internal management module network interface, using the management module Web interface Procedure 12 Configuring the external and internal management module network interfaces Step Action 1 Log on to the management module Web interface 2 On the MM Control menu, click Network Interfaces 3 In the External Network Interface (eth0) section, change the DHCP option to Disabled Use static IP configuration 4 In the eth0 section, configure the Hostname (optional), IP address, Subnet mask, and Gateway address fields 5 In the Internal Network Interface (eth1) section, change the Interface option to Enabled 6 In the eth1 section, configure the IP address, Subnet mask, and Gateway address fields CAUTION The subnet mask for the internal interface must be the same as the subnet mask used for the external interface In addition, the assigned IP address must be in the same subnet as the external interface IP address (so the management module can route external ESM management packets to the ESMs 7 Click Save 8 Restart the management module End NN Standard 40 8 November 2007

46 46 IBM BladeCenter T installation and commissioning Restart the management module Perform the following procedure to restart the management module from the management module Web interface Procedure 13 Restarting the management module from the management module Web interface Step Action 1 Log on to the management module Web interface 2 On the MM Control menu, click Restart MM 3 Click Restart 4 Click OK to confirm that you want to restart the management module The management module restarts The current connection to the management module is lost You must reconnect to the management module Web interface (using the newly-configured IP address for the external interface, if changed) End Backup the management module configuration After you configure the management module, save the configuration file to external media (for example, CD or DVD) Then, if the configuration in the management module becomes damaged or the management module is replaced, you can restore the saved configuration file to the management module You can also use the saved configuration as a base image to configure multiple management modules having similar configurations Perform the following procedure to backup the management module configuration Procedure 14 Backing up the management module configuration using the Web interface Step Action 1 Log on to the management module Web interface 2 On the MM Control menu, click General Settings 3 Verify that the Name, Contact, Location, Date, and Time fields are correct NN Standard 40 8 November 2007

47 Management module 47 4 On the MM Control menu, click Configuration File 5 In the Backup MM Configuration section, click view the current configuration summary to verify that the displayed configuration is the one to save 6 Click Backup to save the current management module configuration to a file 7 When prompted by the browser, save the file to disk A backup configuration file is created on the computer from which you accessed the management module Web interface (for example, the network management station) You can then copy this configuration file to external media for safekeeping End Restore the management module configuration If you save a backup of the management module configuration, you can restore the saved configuration file to a management module if the management module configuration is damaged or the management module is replaced Perform the following procedure to restore the management module configuration file Procedure 15 Restoring the management module configuration file Step Action 1 Log on to the management module Web interface 2 On the MM Control menu, click General Settings 3 Verify that the Name, Contact, Location, Date and Time fields are correct 4 On the MM Control menu, click Configuration File 5 In the Restore MM Configuration section, click Browse to locate the backed-up configuration file to restore 6 Click Restore to restore the backed-up configuration OR Click Modify and Restore to modify the backed-up configuration before restoring The Restore MM Configuration screen appears NN Standard 40 8 November 2007

48 48 IBM BladeCenter T installation and commissioning 7 Verify that the configuration for the management module is correct 8 Click Restore Configuration After successful completion, a message indicates that the management module needs to be restarted 9 Restart the management module End Ethernet Switch Module The Ethernet Switch Module (ESM) enables communication between the individual BladeServers and the outside world The BCT contains two ESMs for link redundancy Note: Although two ESMs are installed and connected to the network, only one ESM is active at any given time The second ESM is for hardware redundancy only and is on standby until the first ESM fails Active is defined as having traffic pass through the ESM When ESM1 and ESM2 are both installed, ESM1 is the default active ESM ESM2 is a redundant standby ESM that becomes active only if and when ESM1 fails As long as ESM1 is active, no traffic passes through ESM2 This section describes: "Cable the ESM" (page 48) "Configure the ESM IP address" (page 50) "Connect to the ESM Web interface" (page 51) "Determine the ESM software version" (page 52) "Configure the ESM" (page 53) "Configure VLANs" (page 55) "SNMP configuration" (page 56) "Restart the ESM" (page 56) Cable the ESM ATTENTION Do not connect the ESM to your network until it is completely installed and configured NN Standard 40 8 November 2007

49 Ethernet Switch Module 49 The ESM provides six external Gigabit Ethernet ports The ports on each ESM must be spread across the available external network routers for maximum redundancy You can use multilink trunking to cable or configure the BladeCenter T Multilink trunking (MLT) is a Nortel method for link aggregation, allowing multiple Ethernet links to be aggregated as a single logical trunk and terminating at an aggregation switch (for example, Passport 8600) The link aggregation method supported by the ESM is compatible with MLT and allows two or more links from an ESM to be considered as a single logical trunk between the ESM and the external switch or router The ESM does not explicitly support split multilink trunking (SMLT), but is capable of functioning as an SMLT client In fact, the ESM is completely unaware of whether or not the aggregated links terminate at an SMLT-configured switch The ESM is configured identically for both the MLT and SMLT configuration scenarios Only one ESM configuration is described in this document Multilink trunking Nortel recommends that the BCT use MLT-based topology In an MLT network topology, the two BladeCenter ESMs are mapped to two Passport 8600 Ethernet switches Up to six external ports for each ESM (two recommended) are aggregated together The ESMs are mapped to different port blades on the Passport 8600, creating intraswitch redundancy on the Passport 8600 Note: Install InterSwitch Trunking (IST) between the Passport switches to send traffic between the aggregation switches IST provides an alternate route, in case MLT on one of the switches fails Network considerations It is not possible to enumerate all possible network-side configurations (for example, Passport 8600) that can result from the MLT network topologies that is, which specific ports and blades should be used on the Passport However, some general network considerations are provided here The supported configuration requires a fully-populated pair of ESMs on the BladeCenter T At least two ports on each ESM are connected to the network, providing fully-redundant 2 Gigabit bandwidth from the ESM Only one ESM is active at any given time, so that only 2 Gigabits are available (not 4 Gigabits for both ESMs) MLT is a method specific to Nortel switch equipment such as the Passport 8600 You can substitute similar equipment from other manufacturers (for example, the Cisco Etherchannel) to connect to the BCT NN Standard 40 8 November 2007

50 50 IBM BladeCenter T installation and commissioning Specific MLT and SMLT configurations are not within the scope of this document The network engineer must be sufficiently well-versed in the art of network configuration The only guideline is that the aggregated links from each ESM are created as separate MLTs For the configuration described in this document, the external ports for the ESMs and the Blades are all grouped on the same virtual LAN (VLAN) When configuring VLANs on both the ESM and Passport sides, make certain that the VLAN IDs used at both ends are the same configure the Passport to match the ESM or vice versa, but make certain they match The configuration of the ESM stops at Layer 2; therefore Layer 3 considerations at the switch level, such as Virtual Router Redundancy Protocol (VRRP), are outside the scope of this document Configure the ESM IP address Use the management module Web interface to configure the static ESM IP address Procedure 16 Configuring the ESM IP address Step Action 1 Log on to the management module Web interface 2 On the I/O Module Tasks menu, click Management The I/O Module Management window appears 3 Scroll to the Bay n section where n is 1 4, which is the bay number for the ESM to be configured 4 In the New Static IP Configuration section for the ESM, configure the IP address, Subnet mask, and Gateway address fields ATTENTION The IP address for the ESM must be on the same subnet as the management module The subnet mask must be the same as the subnet mask for the management module The gateway address is configured with the IP address of the management module internal interface (eth1 in the management module configuration) If two management modules are present, use the address of the primary module NN Standard 40 8 November 2007

51 Ethernet Switch Module 51 5 Click Save 6 Restart the ESM End Connect to the ESM Web interface The ESM provides a Web interface for accessing its management functions ATTENTION The ESM must be configured with a site-specific static IP address If this is not the case, you must first configure the ESM with the correct IP address by following "Configure the ESM IP address" (page 50) If the ESM is configured to disallow management over its external ports, an alternate method to access the ESM Web interface is used This alternate method uses the management module to access the ESM Web interface To connect to the ESM Web interface, perform one of the following procedures: Procedure 17 "Connecting to the ESM Web interface" (page 51) Procedure 18 "Connecting to the ESM Web interface using the management module" (page 52) Procedure 17 Connecting to the ESM Web interface Step Action 1 At the network management station, open a Web browser 2 In the search bar, enter where xxxxxxxx is the IP address of the ESM 3 A window appears to prompt you for a user name and password ATTENTION The User Name and Password fields are case-sensitive If the user name or the password are changed from the default values, use the new values instead 4 In the User Name field, enter admin NN Standard 40 8 November 2007

52 52 IBM BladeCenter T installation and commissioning 5 In the Password field, enter admin 6 Click OK The ESM management and configuration window appears End Procedure 18 Connecting to the ESM Web interface using the management module Step Action 1 Log on to the management module Web interface 2 On the I/O Module Tasks menu, select Configuration 3 Scroll down to the Bay n section where n is 1 4, which is the bay number for the ESM to be configured 4 Click Advanced Configuration The Advanced Configuration for I/O Module n appears 5 Scroll to the Start Telnet/Web Session section 6 Click Start Web Session A new browser window appears, displaying the ESM Web interface End Determine the ESM software version Perform the following procedure to determine the ESM software version Procedure 19 Determining the ESM software version Step Action 1 Access the BCT management module 2 On the Monitors menu, select Firmware VPD The Firmware VPD window appears 3 Locate the I/O Module Firmware VPD heading and note the corresponding level of the software for the switch module NN Standard 40 8 November 2007

53 Ethernet Switch Module 53 End Updating the switch software Note: Switch software should be current at time the system leaves the configuration facility Subsequent updates are provided through normal support channels when necessary If the switch software is not in compliance with the approved version, an upgrade is required as described in the Nortel Layer 2-7 GbE Switch Module for IBM BladeCenter Installation Guide Configure the ESM Configure the Gigabit Ethernet switch module as described in the following sections: "Enable the external ports" (page 53) "General switch properties" (page 54) "Configure external ports" (page 54) "Configure the trunk group" (page 55) Enable the external ports By default, the external ports on the ESM are disabled You configure access to the ESM external ports through the management module Web interface Procedure 20 Configuring the ESM through the management module Web interface Step Action 1 Log on to the management module Web interface 2 On the I/O Module Tasks menu, click Admin/Power/Restart The I/O Module Power/Restart window appears 3 Scroll to the I/O Module Advanced Setup section 4 Configure the External ports option to Enabled and change the Fast POST option to Enabled 5 Click Save 6 On the I/O Module Tasks menu, click Configuration The I/O Module Configuration window appears NN Standard 40 8 November 2007

54 54 IBM BladeCenter T installation and commissioning 7 Scroll to the Bay n (Ethernet SM) section where n is 1 4, which is the bay number for the ESM to be configured 8 Click Advanced Configuration 9 Scroll to the Advanced Setup section 10 Nortel recommends that you do not allow for management of the ESM using its external ports To configure this, change the External management over all ports field to Disabled 11 Change the Preserved new IP configuration on all resets to Enabled 12 Click Save End General switch properties Perform the following procedure to access general switch properties Procedure 21 Accessing general switch properties Step Action 1 Log on to the ESM web interface 2 Double-click the System folder 3 Click General 4 Verify the configuration properties 5 Click Submit at the bottom of the page to apply any changes End Note: The ESM Web interface links are underlined in blue However, you must click on the folder icon to expand or collapse the tree level Configure external ports Perform the following procedure to configure external ports NN Standard 40 8 November 2007

55 Ethernet Switch Module 55 Procedure 22 Configuring the external ports Step Action 1 Log on to the ESM web interface 2 Click Switch Ports and change the fields for each external port (EXT1-6) 3 Ensure the port state is enabled 4 Ensure that Spanning-Tree Protocol (STP) is disabled 5 Ensure that Flow control and Auto-negotiation are enabled 6 Click Submit to apply any changes End Configure the trunk group Perform the following procedure to configure the necessary link aggregation settings on the ESM external ports Procedure 23 Configuring the trunk groups Step Action 1 Log on to the ESM web interface 2 Select Trunk Groups under the Layer 2 folder and click on the entry for Trunk Group 1 3 Verify that the trunk group is enabled and that ports Ext1, Ext2, Ext3, Ext4, Ext5, and Ext6 are members 4 Click Submit to apply the changes End Configure VLANs For the configuration described in this document, only a single VLAN is used when configuring the network and ESM It is essential that the VLAN ID assigned on the Passport 8600 switches and on the ESM are the same For the purposes of configuring the ESM, it is assumed that a VLAN ID was assigned on the Passport 8600 NN Standard 40 8 November 2007

56 56 IBM BladeCenter T installation and commissioning Perform the following procedure to configure the necessary VLAN settings Procedure 24 Configuring VLANS Step Action 1 Log on to the ESM web interface 2 Under the Virtual LANs folder, select Add VLAN 3 In the VLAN ID field, enter the VLAN ID of the Passport In the VLAN Name field, enter a suitable VLAN name 5 Add ports Ext1, Ext2, Ext3, Ext4, Ext5, and Ext6 6 Click Submit 7 Click Save to commit the changes before you restart the ESM End SNMP configuration You can configure the ESM to support management using a third-party, SNMP-based network management system However, this procedure is outside the scope of this document Restart the ESM You use the management module Web interface to reset the ESM To reset the ESM, perform the following procedure Procedure 25 Restarting the ESM Step Action 1 Verify that all configuration changes in the ESM management module committed and click Save 2 Log on to the management module Web interface 3 On the I/O Module Tasks menu, click Admin/Power/Restart 4 On the I/O Module Power/Restart window, select the ESM to restart using the corresponding check box 5 Click Restart Module(s) and Run Standard Diagnostics NN Standard 40 8 November 2007

57 HS20 BladeServer 57 The existing connection and Web interface session to the ESM is lost After restarting, you must reconnect to the ESM End HS20 BladeServer The HS20 BladeServer (known as a Blade) is the computation unit within the BCT or ebladecenter You can have up to eight Blades in a single BCT chassis, depending on the individual blade configuration This section describes "Determine the BladeServer firmware version" (page 57) "Disable local power control" (page 64) "Load the operating system image" (page 65) "Load the MAS application on the Blade" (page 65) Determine the BladeServer firmware version To determine a BladeServer firmware version from the management module Web interface, perform the following procedure Procedure 26 Determining the BladeServer firmware version Step Action 1 Log on to the management module Web interface 2 On the Monitors menu, click Firmware VPD 3 Scroll to the Blade Server Firmware VPD section, and for each of the available blades, examine the three firmware versions (BIOS, Diagnostics, and Blade sys mgmt proc) listed 4 For each available blade, compare the versions listed with the versions on the approved version list included with the packing materials If the versions do not match, upgrade the firmware End NN Standard 40 8 November 2007

58 58 IBM BladeCenter T installation and commissioning Update the BladeServer firmware If the firmware is not in compliance with the approved firmware version, see one of the following sections: "Update the Windows operating system BladeServer firmware" (page 58) "Update the Linux operating system BladeServer firmware" (page 60) Note: The Blade firmware should be current when the system leaves the configuration facility Subsequent firmware updates are provided through normal support channels, when necessary Update the Windows operating system BladeServer firmware Use the following procedure to update the BladeServer running the Windows operating system WARNING When updating the firmware on the BladeServer, you must perform the updates in the following order: 1 Update the BIOS 2 Update the DIAGNOSTIC 3 Update the BMC firmware If only the BIOS or DIAGNOSTIC firmware needs updating, you must also reinstall the BMC firmware (for the same version), so that the correct VPD reporting appears in the MM ATTENTION Some VPD errors may appear during the install of the software, but they clear during the install of the BMC firmware and reboot Procedure 27 Updating the Windows BladeServer firmware Step Action From the Management Module Web interface, 1 On the Blade Tasks menu, click Remote Control The Remote Control window appears 2 Click Start Remote Control A new window appears 3 Under Change KVM owner, select the applicable blade to update NN Standard 40 8 November 2007

59 HS20 BladeServer 59 4 Place the CD with the update software in the media tray on the BladeCenter-T chassis OR Place the CD in the local CD drive of the PC being used to connect to the server 5 If the CD is in the local drive of the PC, under the Remote Disk menu, select the appropriate drive and move it to the box on the right 6 Mount the drive to the server 7 If the CD is in the media tray on the BladeCenter-T chassis, make sure that the Change media tray owner menu has the appropriate server selected 8 From the Windows desktop (in the remote access window to the BladeServer), navigate to the CD drive 9 To update the BIOS: a Select the BIOS exe file The installer window appears b Select Perform Update OR Select Schedule Update c Click Next d Verify that the newly updated versions of the BIOS firmware appear when queried 10 To update the DIAGNOSTICS: a Select the DIAGNOSTICS exe file The installer window appears b Select Perform Update OR Select Schedule Update c Click Next d Verify that the newly updated versions of the DIAGNOSTICS firmware appear when queried 11 To update the BMC: a Select the BMC exe file The installer window appears b Select Perform Update NN Standard 40 8 November 2007

60 60 IBM BladeCenter T installation and commissioning OR Select Schedule Update c Click Next d Verify that the newly updated versions of the BMC firmware appear when queried Note: You are prompted for a reboot of the server You can reboot immediately or schedule the reboot for a later time End Update the Linux operating system BladeServer firmware Use the following procedure to update the BladeServer running the Linux operating system WARNING When updating the firmware on the BladeServer, you must perform the updates in the following order: 1 Update the BIOS 2 Update the DIAGNOSTIC 3 Update the BMC firmware If only the BIOS or DIAGNOSTIC firmware needs updating, you must also reinstall the BMC firmware (for the same version), so that the correct VPD reporting is displayed in the MM ATTENTION Some VPD errors may appear during the install of the software, but they clear during the install of the BMC firmware and reboot Procedure 28 Updating the Linux BladeServer firmware Step Action From the Management Module Web interface, 1 On the Blade Tasks menu, click Remote Control The Remote Control window appears 2 Click Start Remote Control A new window appears NN Standard 40 8 November 2007

61 HS20 BladeServer 61 ATTENTION Ensure that your Web browser software allows pop-up windows from the MM IP address 3 Under Change KVM owner, select the applicable blade to update in the menu 4 Place the CD with the update software in the media tray on the BladeCenter-T chassis OR Place the CD in the local CD drive of the PC being used to connect to the server 5 If the CD is in the local drive of the PC, under the Remote Disk menu, select the appropriate drive and move it to the box on the right Click Mount Drive to mount the drive to the server WARNING Disruptions in the network connection can require remounting of the drive 6 If the CD is in the media tray on the BladeCenter-T chassis, make sure that the Change media tray owner menu has the appropriate server selected 7 Log on to the BladeServer with root privileges At the BladeServer command line, 8 Enter the following command: modprobe usb-storage 9 Enter the following commands: cd /mnt mkdir remotecd cd / 10 If the CD is in the local BladeCenter chassis media tray, enter the following commands: mount /mnt/cdrom cd /mnt/cdrom 11 If the CD is in the local PC, enter the following commands: NN Standard 40 8 November 2007

62 62 IBM BladeCenter T installation and commissioning mount /dev/scd1 /mnt/remotecd cd /mnt/remotecd 12 Enter the following command: ls A list of the directories on the CD appears 13 To update the BIOS: a Enter the following command: cd xxxxxxxxx where xxxxxxxxx is the BIOS directory b Enter the following command: cp XXXXsh / where XXXX is the BIOS file name c Enter the following commands: cd / chmode 555 XXXsh /XXXsh where XXXX is the BIOS file name ATTENTION If you performed the BIOS update, you must perform the DIAGNOSTICS update 14 To update the DIAGNOSTICS: a Enter the following command: cd xxxxxxxxx where xxxxxxxxx is the DIAGNOSTICS directory b Enter the following command: cp XXXXsh / where XXXX is the DIAGNOSTICS file name NN Standard 40 8 November 2007

63 HS20 BladeServer 63 c Enter the following commands: cd / chmode 555 XXXsh /XXXsh where XXXX is the DIAGNOSTICS file name ATTENTION If you performed the DIAGNOSTICS update, you must perform the BMC update 15 To update the BMC: a Enter the following command: cd xxxxxxxxx where xxxxxxxxx is the BMC directory b Enter the following command: cp XXXXsh / where XXXX is the BMC file name c Enter the following commands: cd / chmode 555 XXXsh /XXXsh where XXXX is the BMC file name Note: When you run the BMC update script, the message Device busy for revalidation appears twice The actual BMC update occurs during the reboot of the BladeServer WARNING Before the next step, unmount the CD drive using the management module Remote Console controls and change the owner of the CD tray to a different Blade 16 Enter the following command: NN Standard 40 8 November 2007

64 64 IBM BladeCenter T installation and commissioning reboot The system reboots During the reboot, the system presents a number of status indicators 17 Verify that the newly updated firmware versions appear when queried (see Procedure 26 "Determining the BladeServer firmware version" (page 57)) End Disable local power control The HS20 BladeServer provides a local power control button to power on or power off the Blade This local power control can be disabled as part of the BCT configuration To disable local power control for the Blades using the management module Web interface, perform the following procedure Procedure 29 Disabling local power control Step Action 1 Log on to the management module Web interface 2 On the Blade Tasks menu, click Power/Restart 3 On the Blade Power/Restart screen, select the target blade servers using the corresponding check boxes 4 Click Disable Local Power Control, located near the bottom of the screen A window appears to notify you of the selected operation When the operation is complete, the screen refreshes to show the updated status of the blade servers The Local Pwr Control column shows Disabled for the target blade servers ATTENTION Power control for the Blades is now handled through the management module Web interface Use the Blade Power/Restart screen in the Web interface by first selecting the target blade servers, then clicking Power On Blade or Power Off Blade End NN Standard 40 8 November 2007

65 HS20 BladeServer 65 Load the operating system image Installation of the Blade operating system is performed at the configuration facility prior to shipping the system The procedure for reloading the base operating system is outside the scope of this document Load the MAS application on the Blade To load or install the MAS application, perform the following procedure Procedure 30 Preparing to load or install the MAS application Step Action 1 Enable Keyboard, Video and Mouse (KVM) console access to the target Blade by pressing the KVM select button on the target Blade 2 Enable access to the BladeCenter T media for the target Blade by clicking media select on the target Blade 3 Wait 30 seconds to allow the target Blade to access the USB peripherals 4 Follow the standard installation procedures for installing the MAS application, as described in "MAS service installation types and road maps" (page 26) End NN Standard 40 8 November 2007

66 66 IBM BladeCenter T installation and commissioning NN Standard 40 8 November 2007

67 67 MAS operating system configuration The Media Application Server (MAS) hardware comes with the operating system preinstalled and preconfigured for optimal performance The following procedure covers the remaining configuration steps needed to get the MAS hardware working with your network topology ATTENTION The MAS x335 and BladeCenter hardware come provisioned with an IP address of The MAS x336 hardware comes provisioned with an IP address of You use a PC to configure the MAS OS remotely, using the Terminal Services Advanced Client (TSAC) The PC can connect directly to the MAS using an Ethernet crossover (twisted) cable, or both the PC and the MAS can connect into a hub using standard Ethernet cables Procedure 31 Configuring MAS OS for your network Step Action At MAS server, 1 Power up the MAS server for the first time, and mount the MAS CD in CD-ROM drive At the administrator s PC, 2 Select Start > Programs > Terminal Services Client > Terminal Services Client The Terminal Services Client window appears 3 In the Server field, enter the IP address of the MAS Use the IP address in Example 1 for MAS x335 and BladeCenter server Use the IP address in Example 2 for MAS x336 server Example 1: Example 2: NN Standard 40 8 November 2007

68 68 MAS operating system configuration 4 Click Connect to start a connection to the MAS At the logon window, 5 Enter the default user name Example: NortelMASAdmin 6 Enter the default password Example: nortel At the operating system desktop, 7 Right-click My Computer and select Properties The System Properties window appears 8 Select the Network Identification tab 9 Click Properties and assign a host name to the system The computer name must be 15 characters or less 10 Click OK ATTENTION Do not reboot when prompted At the Start menu, 11 Select Start > Run The Run dialog box appears 12 Type regedit and click OK The Registry Editor window appears 13 Navigate to HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > Tcpip > Parameters 14 Update the NV Hostname field with the host name of the server, as configured in step 9 ATTENTION The computer name and the NV Hostname must match to ensure proper system functioning 15 Press F3 to search for the next instance of NV Hostname and configure the new name NN Standard 40 8 November 2007

69 MAS operating system configuration Continue to press F3 until all instances of NV Hostname are changed 17 Select Registry > Exit to save your changes and close the Registry Editor window At the Start menu, 18 Select Start > Settings > Network and Dial-up Connections The Network and Dial-up Connections window appears 19 Right-click the MASTeam icon and select Properties The MASTeam Properties window appears 20 Select Internet Protocol (TCP/IP) and click Properties The Internet Protocol (TCP/IP) Properties window appears 21 Enter the static IP address and subnet mask for your network topology ATTENTION You must change the IP address and subnet mask Do not configure WINS or any other Advanced settings 22 Click OK 23 Click OK 24 Reboot the server End NN Standard 40 8 November 2007

70 70 MAS operating system configuration NN Standard 40 8 November 2007

71 71 MAS Platform installation This chapter describes the platform installation procedures for most Media Application Server (MAS) services ATTENTION For the installation procedures for the MAS Meet Me Web Collaboration service, see "MAS Meet Me Web Collaboration service" (page 157) Procedure 32 Installing the Media Application Server platform Step Action At the Media Application Server, 1 Locate the MAS platform installation program and double-click the executable The Media Application Server Install Wizard appears 2 Click Next The License Agreement statement appears 3 Select I accept the terms of the license agreement 4 Click Next The Network Information window appears 5 Enter the Service Logical IP address (also called Network Service Descriptor, or NSD), and SIP UDP port for each Session Manager Server that must communicate with the MAS ATTENTION The MAS accepts incoming service requests only from IP addresses and ports specified in this list to prevent unauthorized nodes from sending service requests directly to the MAS NN Standard 40 8 November 2007

72 72 MAS Platform installation 6 Click Next The License Key window appears 7 If the license configured for this MAS is available, enter it into the License Key field Note: If the license key is not available, you can use the MAS Management Console to enter it later 8 Click Next The Primary Destination Folder window appears 9 If you want to install the MAS software into a different directory, click the Change button to select a different destination drive partition or directory ATTENTION Nortel recommends that you use the default destination drive partition and folder 10 Click Next The Content Storage Destination Folder window appears 11 If you want to locate the MAS Content Storage into a different directory, click Change to select a different destination drive partition or directory ATTENTION Nortel recommends that you use the default destination drive partition and folder However, if the HS20 Blade has the dual SCSI expansion unit connected to it, then the content store destination should be the SCSI drive partition (E:) 12 Click Next The Ready to Install the Program window appears 13 Click Install Note: You can click Cancel to cancel the installation When the installation is complete, the InstallShield Wizard Completed window appears 14 Click Finish to end the installation program NN Standard 40 8 November 2007

73 MAS Platform installation 73 If this is a new installation or if an alternative destination directory is specified in the Primary Destination Folder or Content Store Destination Folder windows, you are prompted to restart the computer 15 Click No The server restart is performed after the service software installation is complete End NN Standard 40 8 November 2007

74 74 MAS Platform installation NN Standard 40 8 November 2007

75 75 MAS service installation This chapter describes the installation procedures for most Media Application Server (MAS) services ATTENTION For the installation procedures for multiapplication MAS, see "Multiapplication MAS deployment" (page 77) For the installation procedures for the MAS Meet Me Web Collaboration service, see "MAS Meet Me Web Collaboration service" (page 157) In this chapter, the term MAS service means the MAS Ad Hoc Conferencing, MAS Announcements, MAS IM Chat, MAS Meet Me Conferencing, or MAS Music on Hold Use this procedure to install the MAS service software Procedure 33 Installing the MAS service software Step Action At the Media Application Server, 1 Locate the MAS service installation program and double-click the executable The Media Application Server Install Wizard appears 2 Click Next The License Agreement window appears 3 Select I accept the terms of the license agreement 4 Click Next For Meet Me Conferencing, the Install Default Music Files window appears For all other MAS services, the Ready to Install the Program window appears NN Standard 40 8 November 2007

76 76 MAS service installation 5 For Meet Me Conferencing, click Next The default music files are installed 6 Click Install to perform the installation of the service Note: You can click Cancel to cancel the installation When the installation is complete, the InstallShield Wizard Completed window appears 7 Click Finish to end the installation program 8 If installing other MAS services on this server, repeat from step1 until all services are installed 9 For the Meet Me Conferencing service, if Web Collaboration service is required, perform Procedure 71 "Installing the Meet Me Web Collaboration software" (page 144) 10 For first time installations, a On the Windows Start menu, click Start > Shut Down The Shut Down Windows window appears b Select Restart from the menu and click OK to restart the server End NN Standard 40 8 November 2007

77 77 Multiapplication MAS deployment This chapter explains the engineering, installation, and configuration guidelines for deploying multiple applications on a single Media Application Server (MAS) platform for MCS 5100 systems Previous to this capability, each application on the MAS had to reside on its own separate hardware computing platform This restriction is lifted for a special case of MAS applications running on the IBM x3550, x335, or x336 platform A single MAS hardware platform solves customer needs for cost-effective, small implementations of multiple MAS services, with the exception of Web Collaboration The multiple application MAS (on an IBM x3550, x335, or x336 hardware platform) can work with the Enterprise micro system to deliver multiple services for up to 250 subscribers (maximum) It can also be used as a service evaluation platform in 4-server and 8-server configurations ATTENTION This multiple application configuration of the MAS supports a subscriber count (in a domain or served subdomain) of up to 250 and is a standalone service that is not available to any pooling of ports across other MAS units For the maximum port limits for each application, see "Port limits" (page 78) The following applications can reside on the same Media Application Server hardware platform: Ad Hoc Audio and Video Conferencing Meet Me Audio and Video Conferencing or Meet Me Premium Audio and Video Conferencing Music on Hold Announcements IM Chat NN Standard 40 8 November 2007

78 78 Multiapplication MAS deployment ATTENTION You cannot install Web Collaboration as part of a multiapplication MAS deployment In this deployment, the applications are distributed through subdomain implementations For information about the IBM x3550, x335, or x336 platform specifications and other MAS considerations, see MCS Media Application Server Planning and Engineering (NN ) Port limits The following table shows the defined maximum port limits for applications Application Number of ports (audio only) Number of ports (video) Ad Hoc Conferencing 20 (G711 or G729) 10 (G711 or G729) Meet Me (Premium) Conferencing 60 (G711 or G729) 50 (G711 or G729) Music on Hold 20 (G711 or G729) 10 (G711 or G729) Announcements 20 (G711 or G729) 10 (G711 or G729) IM Chat These maximum port restrictions are fixed for each application If one or more applications are not installed, this does not change the maximum port limits for the other applications Multiapplication MAS installation Perform the following procedure to install multiple applications on the MAS Procedure 34 Installing multiple applications Step Action 1 Install one Media Application Server platform as described in Procedure 32 "Installing the Media Application Server platform" (page 71) Note: One key file is built in the Keycode Retrieval System (KRS) for this MAS unit As the MAS is identified in the KRS system for registered system, the Media Access Control (MAC) addresses are identified, the server license authorization code is applied, and then the authorization codes for ports of each of the MAS applications are applied to the key The key file generated NN Standard 40 8 November 2007

79 Management Console 79 by KRS is then applied during the initial configuration step, as required in MAS installation and commissioning 2 Install each application Do not restart the Media Application Server until all of the applications are installed For installation procedures, see Procedure 33 "Installing the MAS service software" (page 75) 3 Continue with the deployment of each application as described in the following sections: "MAS Ad Hoc Conferencing service" (page 93) "MAS Announcements service" (page 101) "MAS IM Chat service" (page 123) "MAS Meet Me Conferencing service " (page 127) "MAS Music On Hold service" (page 147) End Management Console The following figure shows the Management Console for a MAS platform with multiple applications NN Standard 40 8 November 2007

80 80 Multiapplication MAS deployment For more information about monitoring and managing different services, see the appropriate MAS service fundamentals guide NN Standard 40 8 November 2007

81 81 Common procedures This chapter contains the following common procedures for Media Application Server (MAS) installations: "Start the Media Application Server Management Console" (page 81) "Deactivate the Media Application Server" (page 82) "Start the MAS to provide service" (page 82) "Lock the MAS" (page 83) "Unlock the MAS" (page 85) "Configure MAS services on the System Management Console" (page 86) "Enable service access to the MAS service" (page 87) In this chapter, the term MAS service means MAS Ad Hoc Conferencing, MAS Announcements, MAS IM Chat, MAS Meet Me Conferencing, or MAS Music on Hold Start the Media Application Server Management Console After you install the MAS software, use the MAS Management Console to configure the MAS and the MAS services To access the MAS Management Console from the MAS server, click Start > Programs > Nortel Networks Media Application Server > Media Application Server Console Access the MAS Console using RDP (alternate method) You can also use the Remote Desktop Protocol (RDP) to access the MAS Console RDP provides remote access capabilities to the MAS platform where the MAS Console application is running NN Standard 40 8 November 2007

82 82 Common procedures Procedure 35 Connecting to the MAS Console using RDP Step Action At the administrator s PC, 1 Click Start > Programs > Accessories > Communications > Remote Desktop Connection 2 Enter the IP address for the MAS server you want to connect to 3 Enter the user name and password to log on to the server End Deactivate the Media Application Server After the MAS is rebooted, the MAS and the MAS service (or services) start Thus, the MAS and the MAS service start after you complete installation of the MAS software and before you configure the MAS service Before you can configure the MAS service, you must deactivate the service Procedure 36 Deactivating and verifying offline state of the MAS and MAS service Step Action At the Media Application Server console tree, 1 Right-click the Control Panel icon in the console tree to display the shortcut menu 2 Select Operations > Stop to deactivate the MAS service The Media Application Server stops and the status shows offline 3 Right-click Control Panel and select View System Components 4 Verify that all the individual subcomponents have successfully stopped All subcomponents show the offline status End Start the MAS to provide service After you successfully configure the MAS and the MAS service, you start the MAS NN Standard 40 8 November 2007

83 Lock the MAS 83 Procedure 37 Starting the MAS Step Action At the Media Application Server console tree, 1 Select the Control Panel icon to view the offline status of the MAS 2 If the Details panel displays the individual MAS components, right-click the Control Panel icon and select View System Components to turn off the component view of the MAS 3 Right-click the Control Panel icon in the console tree to display the shortcut menu 4 Select Operations > Start to bring the MAS into operation The MAS starts The status indicates online 5 Right-click Control Panel and select View System Components 6 Verify that all the individual subcomponents have successfully started All subcomponents show the online state End Lock the MAS CAUTION Temporary loss of service In the simplex deployment, only one MAS runs the MAS service Therefore, if you lock the Media Application Server in the simplex deployment, a service outage occurs until you unlock the MAS Before you can perform maintenance on the MAS (such as a software upgrade), you must take the MAS out of service To do this, the MAS must not accept any new incoming transactions and it must end all existing transactions Existing transactions can end either naturally (over time) or existing transactions can end immediately, where the MAS interrupts and terminates existing transactions while the users are still connected You can place the MAS in a Pending Lock state to allow calls to end gradually, rather than interrupting them While in the Pending Lock state, existing calls continue on the MAS while all new incoming service requests are rejected NN Standard 40 8 November 2007

84 84 Common procedures For information about how to check for active sessions, see "Check for active sessions on the MAS" (page 85) For information about how to end active sessions, see "End an active session on the MAS" (page 85) To lock the MAS, perform the steps in one of the following procedures: Procedure 38 "Delayed locking of the MAS" (page 84) Procedure 39 "Immediate locking of the MAS" (page 84) Procedure 38 Delayed locking of the MAS Step Action At the MAS Console, 1 Right-click the Control Panel icon in the console tree to display the Control Panel shortcut menu 2 Select Operations > Pending Lock The MAS is placed in the Pending Lock state The status of the MAS indicates online 3 Right-click Control Panel and select View System Components 4 Verify that all the individual subcomponents are in the Pending Lock state The status of the subcomponents indicates online End Procedure 39 Immediate locking of the MAS Step Action At the MAS Console, 1 Right-click the Control Panel icon in the console tree to display the Control Panel shortcut menu 2 Select Operations > Lock The MAS is placed in the Locked state The status of the MAS indicates online 3 Right-click Control Panel and select View System Components NN Standard 40 8 November 2007

85 Unlock the MAS 85 4 Verify that all the individual subcomponents are in the Locked state The status of the subcomponents indicates online End Check for active sessions on the MAS Before you deactivate the MAS, check for active sessions being serviced on the MAS Nortel recommends that you allow the number of active sessions to drop to zero (or to an acceptably low number) before you lock or deactivate the MAS completely At the MAS Console, click the Active Sessions icon in the console tree to display a list of any active sessions on the MAS in the Details panel Note: You can right-click the Active Sessions icon and select Refresh from the shortcut menu to refresh the contents in the Details panel End an active session on the MAS Sometimes it is necessary to manually end a specific active session on the Media Application Server without ending other active sessions Perform the steps in the following procedure to end an active session on the Media Application Server Procedure 40 Ending an active session Step Action At the MAS Console, 1 Click Active Sessions in the console tree A list of active sessions on the MAS appears in the Details panel 2 Right-click on an active session to display the shortcut menu for the active session 3 Select Delete to end the active session End Unlock the MAS After you perform maintenance (such as a software upgrade) on the MAS, you unlock the MAS to accept new incoming service requests NN Standard 40 8 November 2007

86 86 Common procedures Procedure 41 Unlocking the MAS Step Action At the MAS Console, 1 Right-click the Control Panel icon in the console tree to display the Control Panel shortcut menu 2 Select Operations > Unlock The MAS service is placed in the Unlocked state 3 Right-click Control Panel and select View System Components 4 Verify that all the individual subcomponents are in the Unlocked state End Configure MAS services on the System Management Console For the MAS service information to appear in the Provisioning Client, you must configure the service in the System Management Console For information about the System Management Console, see the System Management Console User Guide (NN ) Procedure 42 Configuring the component information on the System Management Console Step Action From a browser window, 1 Enter the IP address of the Multimedia Communication Server (MCS) server you are accessing and the applicable port number in the address bar of the browser Example: A browser window with a link to the System Management Console appears 2 Click Launch MCP System Management Console 3 You are prompted for a UserID and Password Enter the correct parameters 4 If a current administrative session is active (for instance, on another administrator s PC), select ForceOut to terminate the other session NN Standard 40 8 November 2007

87 Enable service access to the MAS service 87 5 Click OK The MCP System Management Console window appears 6 Expand Network Elements 7 Expand Provisioning Managers 8 Expand PROV1 9 Click Configuration Parameters The PROV1 Configuration Parameters window appears 10 Verify that the Parm Group menu shows Conf 11 If the Name field does not contain the correct URLPrefix, click on the name and click -/+ a Make your configuration changes b Click Save End Enable service access to the MAS service Enabling service access allows the network to route service requests to the MAS service Configuring service access to the MAS service consists of the following steps: Procedure 43 "Creating a pooled entity for a MAS service" (page 87) For the Music on Hold service, see "Enable service access to the Music on Hold service" (page 154) For all other MAS services, see Procedure 44 "Configuring Routable Services information for MAS service pooled entity" (page 89) Procedure 45 "Enabling MAS service in the end user service packages" (page 89) Procedure 43 Creating a pooled entity for a MAS service Step Action From the Provisioning Client, 1 In the domain where access to the MAS service is required, select Pooled Entities > Add Pooled Entity The Add Pooled Entity page appears NN Standard 40 8 November 2007

88 88 Common procedures 2 In the Entity Name field, enter the name of the pooled entity Example: chat-pool ATTENTION You cannot use under scores or spaces in the name You can use hyphens in the name 3 In the Routable Services menu, select the applicable MAS service 4 In the Selection Algorithm menu, select Weighted Average 5 In the Location menu, select the location for the pooled entity services The location field enables the domain administrator to associate the pooled entity resource to a system domain location The system domain location hierarchy is provisioned by the system administrator to map components (such as the MAS) and gateways to a location Associating a location to a pooled resource helps determine when a media portal is required for a voice path 6 In the Route field, a Enter the route used to connect to a Media Application Server where an instance of the MAS service resides This is the IP address of the MAS and the name of service You must prefix the IP address with sip: and you must add the following suffix to the IP address: ;nt im=nt im 20;trusted Example: sip: ;nt im=nt im 20;trusted There can only be a single MAS in each domain on which the MAS service is running Therefore, you can only configure one route to a single MAS within the pooled entity b Enter the Selection Weight (from 0 to 10) to use when routing MAS service requests Keep the following guidelines in mind when assigning weights to routes: Routes with a zero weight are disabled A higher weight means that the MAS (defined by this route) receives more incoming service requests You can only have one route for the MAS service Therefore any weight number from 1 to 10 has the same effect The percentage of the total weight for each route is calculated automatically NN Standard 40 8 November 2007

89 Enable service access to the MAS service 89 c Click Add to add the new route to the Routes Selected list d To modify the existing route weights, highlight the applicable route, change the weight value in the Weight (0-10) box, and click Add 7 Click Save when done OR Click Cancel to exit the Add Pooled Entity page without saving changes 8 Repeat step1 through step7 for each service installed on the server End Procedure 44 Configuring Routable Services information for MAS service pooled entity Step Action From the Provisioning Client, 1 In the domain where access to the MAS service is required, select Routable Services > <Service> > Assign Pool The Select <Service> Pool window appears 2 On the Select Pool menu, select the name of the pooled entity created in Procedure 43 "Creating a pooled entity for a MAS service" (page 87) Example: chat-pool 3 Click Save when done 4 Repeat step1 through step3 for each service installed on the server End Procedure 45 Enabling MAS service in the end user service packages Step Action From the Provisioning Client, 1 In the domain where access to the MAS service instance is required, select Service Package > List Packages The List of packages for domain page appears for the domain NN Standard 40 8 November 2007

90 90 Common procedures 2 Click Details-Modify for the service package in which the MAS service is to be enabled The Package details page appears for the selected service package 3 Select the <Service> check box 4 If the <Service> field contains subfields, fill them in For example, configure the Meet Me Conferencing Maximum Number of Participants subfield ATTENTION The values in the subfields cannot exceed the configuration parameters for the MAS service 5 Click Save and Enforce Now to immediately enable the MAS service for all users on this domain who are actively subscribed to this service package OR Click Save and Enforce Later to enable the MAS service for all users on this domain when they resubscribe to this service package when reconnecting to the network or when their service package subscription is automatically refreshed 6 Repeat step 1 through step 4 for each domain that requires MAS service access 7 Repeat step1 through step5 for each MAS service installed on the server End Create a Terminal Services install disk ATTENTION Terminal Service install disk creation is only required if the Management Server does not have access to the Terminal Services Installer through alternate means such as Internet download If you create the install disks, you need two disks for the terminal service installation program NN Standard 40 8 November 2007

91 Create a Terminal Services install disk 91 Procedure 46 Creating the Terminal Service install disk Step Action At the OS Start menu, 1 Select Start > Settings > Control Panel The system Control Panel window appears 2 Double-click the Administrative Tools folder 3 Double-click the Terminal Services Client Creator icon 4 Select Terminal Services for 32-bit x86 windows 5 Click OK to begin creation of the installation disks The Insert Floppy window appears 6 Insert a disk into the floppy disk drive 7 Click OK 8 Follow the instructions that appear on the screen After you complete this procedure, you can use these disks to install Terminal Services on other computers End NN Standard 40 8 November 2007

92 92 Common procedures NN Standard 40 8 November 2007

93 93 MAS Ad Hoc Conferencing service This chapter contains Ad Hoc Conferencing service configuration procedures ATTENTION Ad Hoc DivX video conferencing is enabled (or disabled) for a subdomain, based on how the Media Application Server (MAS) within the subdomain is licensed (keycoded) If DivX video conferencing is enabled for the MAS by means of the respective license keys, then DivX video conferencing is enabled for all Ad Hoc conferences that are hosted on the MAS Similarly, if DivX video conferencing is not enabled, then DivX video is not available for any Ad Hoc conferences Configure the MAS Platform and MAS Ad Hoc Conferencing service You must configure both the MAS platform and the Ad Hoc Conferencing service Procedure 47 Configuring the MAS platform and MAS Ad Hoc Conferencing service Step Action ATTENTION This procedure assumes that the MAS is offline If the MAS has not been deactivated, then deactivate it using "Deactivate the Media Application Server" (page 82) before you continue with this procedure At the MAS console, 1 From the console tree panel, select Services > System > Configuration The Details panel displays all configuration data for the MAS platform 2 Double-click a system configuration parameter to display the properties window for that configuration parameter NN Standard 40 8 November 2007

94 94 MAS Ad Hoc Conferencing service ATTENTION The MAS Console displays the entire list of system parameters This procedure only discusses the parameters associated with the Ad Hoc Conferencing service 3 Use the following table to enter or modify the parameter values for the MAS platform Parameter Name Field information Description Conference Port Range Starting Port License Alarm Threshold License Key Local Hostname or IP Address Local SIP UDP Port Type = integer Range = Default = Type = integer Range = Default = 90 Type = string Range = characters Default = blank Type = IP address Default = Local IP address Type = integer Range = Default = 5060 The Conference Media Processor uses a range of ports to provide service This value specifies the lower limit of the range RTP/RTCP starting port range The threshold (as a percentage of available licenses) after which subsequent calls cause an alarm to be raised The license key for the MAS server The IP address of the MAS server Note: If this value is changed, the OS network setting must be changed to match, to avoid service interruption The local UDP port for SIP messaging (default is 5060) Media Processing Units Default = 350 Do not modify this optional value without consulting Media Application Server Planning and Engineering (NN ) The value for this optional parameter is the number of Media Processing Units available for this server This value is influenced by the number of processors, speed of processors, and other performance characteristics of the server NN Standard 40 8 November 2007

95 Configure the MAS Platform and MAS Ad Hoc Conferencing service 95 Parameter Name Field information Description Session Manager Server(s) SNMP Community String SNMP Management Server SNTP Source Server SysLog Server Video Switching Hysteresis (ms) Type = a list of semicolon-delimited IP addresses and ports for the Session Manager Default = blank Type = a semicolon delimited list of SNMP Community Strings Default = public Type = IP address Default = blank Valid values = local host, , or a valid IP address of a designated SNTP time source server Default = xx Type = IP address Default = blank Type = integer Range = Default = 600 This optional item contains a semicolon delimited list of IP addresses and ports of Session Manager Modules Each listed server is considered a trusted node and requests from those servers do not require authentication The first entry in the list is used for outbound messages from the media server A value must be provided to enable transfers and other outbound requests from the MAS server This optional item contains a semicolon delimited list of SNMP Community Strings Note: For information on changing the default value of public, see the section on Network Considerations in Media Application Server Planning and Engineering (NN ) This optional item contains the IP address of an SNMP server This optional item is the IP address of an SNTP time source server Specify localhost or to designate the local server as a time source If the local server is designated as a time source, the Windows time service automatically restarts to accept the configuration change For most deployments, the SNTP Source Server can be the Management Server This optional value is the IP address or host name and port of a SysLog server The default port is 514 This optional value is the time in milliseconds that a participant must assume the role of dominant speaker before the software begins transmitting their DivX video image to other conference participants NN Standard 40 8 November 2007

96 96 MAS Ad Hoc Conferencing service Parameter Name Field information Description Note: Changing the default value may result in an unpleasant user experience 4 Click OK 5 Repeat step 2 through step 4 for each parameter in the table 6 From the console tree panel, select Services > Adhoc Conferencing > Configuration The Details panel displays all configuration data for the Ad Hoc Conferencing service 7 Use the following table to configure the Ad Hoc Conferencing service parameters Parameter name Field information Description Send Accounting INFO (YES/NO) Video Enabled (YES/NO) Valid values: Yes, No Default = Yes Valid values: Yes, No Default = No When enabled, SIP INFO messages are sent to convey accounting information Enable or disable DivX video for a MAS Note: This parameter does not enable DivX video if the appropriate keycode was not generated for this MAS However, this parameter does allow you to disable DivX video on a MAS, thereby overriding a keycode that permits the service ATTENTION You must consistently configure this DivX video parameter for all MAS that are grouped within the same pooled entity in a subdomain This means that either all MAS (in the pooled entity) must have DivX video enabled, or all must have DivX video disabled End NN Standard 40 8 November 2007

97 Configure MAS Ad Hoc Conferencing 97 Configure MAS Ad Hoc Conferencing To configure MAS Ad Hoc Conferencing, perform the following procedures Procedure 48 "Configuring the routable services information for Ad Hoc logical entity" (page 97) Procedure 49 "Adding the Ad Hoc Conferencing service to the domain" (page 98) Procedure 50 "Enabling the Ad Hoc Conferencing service in the service packages" (page 98) Procedure 48 Configuring the routable services information for Ad Hoc logical entity Step Action From the Provisioning Client, 1 In the domain where access to the Ad Hoc Conferencing service is required, select Routable Services > Ad Hoc Conference > Assign Locations The Select Ad Hoc Conferencing Pool page appears 2 From the Select Poollist, select the name of the logical entity created in previous steps Example: adhoc_entity 3 Click Next An Add Locations for page appears NN Standard 40 8 November 2007

98 98 MAS Ad Hoc Conferencing service 4 In Locations for, select the location that this service node services Example: Other 5 Click Save End Procedure 49 Adding the Ad Hoc Conferencing service to the domain Step Action From the Provisioning Client, 1 Select Services > Assign Services The Assign Services window appears 2 From the Select a domain list, select the domain where you want to add the Ad Hoc Conferencing service Example: nortelcom 3 Click Continue The Assign services to domains window appears 4 Select Ad Hoc Conferencing 5 From the Maximum Number of Ports list, select the maximum number of conference ports for any single conference Example: 10 6 Click Save 7 Repeat step 1 through step 6 for each domain where you require access to the Ad Hoc Conferencing service End Procedure 50 Enabling the Ad Hoc Conferencing service in the service packages Step Action From the Provisioning Client, 1 In the domain where you require access to the Ad Hoc Conferencing service instance, select Service Package > List Packages NN Standard 40 8 November 2007

99 Configure MAS Ad Hoc Conferencing 99 The List of packages for domain page appears for this domain 2 Click Details-Modify for the service package for which you want to enable the Ad Hoc Conferencing service The Package details page appears for the selected service package 3 Select Ad Hoc Conferencing and specify the maximum number of conference ports in the associated list Example: 10 4 Click Save and Enforce Now to immediately enable the Ad Hoc Conferencing service for all users on this domain who are actively subscribed to this service package OR Click Save and Enforce Later to enable the Ad Hoc Conferencing service for all users on this domain when users reconnect to the network or when their service package subscription is automatically refreshed 5 Repeat step1 through step 4 for each service package where access to the Ad Hoc Conferencing service is required End NN Standard 40 8 November 2007

100 100 MAS Ad Hoc Conferencing service NN Standard 40 8 November 2007

101 101 MAS Announcements service This chapter describes the MAS Announcements service configuration Configure the MAS platform and MAS Announcements service This section describes the configuration of the MAS platform and MAS Announcements service parameters For simplex deployments, follow Procedure 51 "Configuring the MAS platform and Announcements service parameters" (page 101) For duplex deployments, follow Procedure 51 "Configuring the MAS platform and Announcements service parameters" (page 101) and Procedure 52 "Configuring the duplex MAS platform and Announcements service parameters" (page 104) Procedure 51 Configuring the MAS platform and Announcements service parameters Step Action ATTENTION This procedure assumes that the Media Application Server is offline If the MAS has not already been deactivated, then deactivate it using "Deactivate the Media Application Server" (page 82) before continuing with this procedure At the Media Application Server console 1 From the console tree panel, select Services > System > Configuration The Details panel displays all configuration data for the Media Application Server platform ATTENTION The MAS Console displays the entire list of system parameters This procedure only discusses the parameters associated with the Announcements service NN Standard 40 8 November 2007

102 102 MAS Announcements service 2 Use the parameters in the following table to configure the Announcements service Parameter name Field information Description Content Store Servers IVR Audio Port Range Starting Port License Alarm Threshold License Key Local Content Store Activated Local Hostname or IP Address Local SIP UDP Port Type = string of semicolon-delimited IP addresses Default = local IP address Type = integer Range = Default = Type = integer Range = Default = 90 Type = string Range = characters Default = blank Value = YES, NO Default = YES Type = IP address Default = Local IP address Type = integer Range = Default = 5060 This item contains a semicolon-de limited list of MAS servers hosting Content Stores The Multimedia Controller uses the Content Stores defined in this list The IVR Media Processor uses a range of ports to provide service This value specifies the lower limit of the range The threshold (as a percentage of available licenses) after which subsequent calls cause an alarm to be raised The license key for the MAS server Whether or not the local content store is active on the MAS server The IP address of the MAS server Note: If this value is changed, the OS network setting must be changed to match, to avoid service interruption The local UDP port for SIP messaging Media Processing Units Default = 350 Do not modify this optional value without consulting Media Application Server Planning and Engineering (NN ) The value for this optional parameter is the number of Media Processing Units available for this server This value is influenced by the number of processors, speed of processors, and other performance characteristics of the server NN Standard 40 8 November 2007

103 Configure the MAS platform and MAS Announcements service 103 Parameter name Field information Description Session Manager Server(s) SNMP Community Strings SNMP Management Server SNTP Source Server Syslog Server Type = semicolon-delimited list of IP addresses and ports of Session Managers Default = blank Type = a semicolon delimited list of SNMP Community Strings Default = public Type = IP address Default = blank Valid values = local host, , or a valid IP address of a designated SNTP time source server Default = xx Type = IP address Default = blank This item contains a semicolon-d elimited list of IP addresses and ports of SIP Application Modules Each listed server is considered a trusted node and requests from those servers do not require authentication The first entry in the list is used for outbound messages from the media server A value must be provided to enable transfers and other outbound requests from the MAS server This optional item is the IP address of an SNTP time source server Specify localhost or to designate the local server as a time source If the local server is designated as a time source, the Windows time service automatically restarts to accept the configuration change For most deployments, the SNTP Source Server should be the Management Server This optional item contains the IP address of an SNMP server This optional item is the IP address of an SNTP time source server Specify localhost or to designate the local server as a time source If the local server is designated as a time source, the Windows time service automatically restarts to accept the configuration change For most deployments, the SNTP Source Server should be the Management Server This optional value is the IP address or host name and port of a SysLog server The default port is 514 End NN Standard 40 8 November 2007

104 104 MAS Announcements service Procedure 52 Configuring the duplex MAS platform and Announcements service parameters Step Action ATTENTION Perform this for duplex Announcements service deployments only At the Media Application Server Console 1 From the console tree panel, select Services > System > Configuration 2 Use the parameters in the following table to configure the Announcements service Parameter name Field information Description Content Store Mirrored Peer Server Content Store Servers Controller Peer Primary Server Enable RTFT (YES/NO) Type = IP address Default = blank Note: Must contain at valid IP address Type = string Values = semicolon-delimite d list of IP addresses Default = local IP address Type = IP address Default = blank Note: Must contain at least one valid MAS IP address Valid Values: YES, NO Default: NO This item contains the IP address of the peer Content Store for mirrored deployments For a duplex deployment, it should contain the IP address of the peer MAS This item contains a semicolon-delimited list of servers hosting Content Stores The Multimedia Controller uses the Content Stores defined in this list For a duplex deployment, it should contain the IP address of the local MAS This item contains the IP address of the primary CPLink MAS for duplex deployments For a duplex deployment, it should contain the IP address of the peer MAS Whether or not Real-Time File Transfer (RTFT) is used to transfer data between content store components ATTENTION Do not modify this value Local Content Store Activated Valid Values: YES, NO Default: NO Whether or not the local content store is active on the MAS For a duplex deployment, both content stores should be activated NN Standard 40 8 November 2007

105 Place treatment or source files on a MAS 105 End Domain-level language support for Announcements You can view the list of languages supported by the Announcements service by going to the Domain Locales page of the Provisioning Client You must ensure that languages in which your announcement files are recorded are supported by the Announcements service In addition, you must configure (at the domain level) each language that you plan to use Procedure 53 Configuring the locale (or language) of your announcements Step Action At the Provisioning Client, 1 In the domain where access to the Announcements service is needed, select Domain > Domain Locales The Domain Locales page appears 2 Place a check mark beside each language that you want to use for the Announcements service 3 Click Update The system responds The Domain Locales were updated successfully End Place treatment or source files on a MAS ATTENTION The Announcements service does not support external media source files All media source files must be in Wave File format and be resident on the MAS on which the Announcements service is running (simplex deployment) one of the MAS (duplex deployment) in the logical entity NN Standard 40 8 November 2007

106 106 MAS Announcements service You must physically transfer announcement files to one MAS within the MAS service instance (logical entity) You place the announcement files on only one MAS in the service instance, because announcement files are replicated by the system throughout the service instance The announcement files that you place on the MAS must meet certain criteria These announcement files must be in Wave File format encoded as a single channel (mono) linear 16-bit bit stream using pulse code modulation (PCM) that is sampled at 8 khz At run time, the MAS transcodes the announcement files to the client settings, encoding the digital bit stream using the G711 or G729 transmission algorithm The announcement files are transmitted with a packet time of 10, 20, 30, or 60 milliseconds To place announcement files on a MAS, you perform the following procedures: "Place announcement files on a server that can be accessed by the Announcement MAS" (page 106) "Transfer and configure the announcements" (page 106) Place announcement files on a server that can be accessed by the Announcement MAS Copy the announcements files to a server that allows passive FTP access from the Announcements MAS Transfer and configure the announcements The transfer and configure steps use the following procedures: Procedure 54 "Logging on to the Announcements MAS" (page 107) Procedure 55 "Transferring announcement files to the Announcement MAS" (page 107) Procedure 56 "Configuring the announcement files on the MAS" (page 108) Procedure 57 "Configuring treatment routable services information for the Announcement logical entity" (page 110) Procedure 58 "Configuring branding routable services information for the Announcement logical entity" (page 113) NN Standard 40 8 November 2007

107 Place treatment or source files on a MAS 107 Procedure 54 Logging on to the Announcements MAS Step Action At the administrator PC, 1 Select Start > Programs > Administrative Tools > Terminal Services Manager The Terminal Services Manager window appears 2 Right-click the server you want to connect to 3 Click Connect to start a connection to the MAS server End Procedure 55 Transferring announcement files to the Announcement MAS Step Action At the MAS on which the announcement files are to be transferred, 1 Launch the passive FTP client, located in the tools folder of the MAS platform files on the D drive of the MAS Note: You can also launch the Microsoft Internet Explorer application (from the Start > Programs > Internet Explorer menu) and use the passive FTP functionality of the browser to transfer the announcement files 2 Within the FTP client window, type the command (for example, ftp ) to establish a passive FTP connection to the remote server on which you placed the announcement files 3 Supply your user ID, and password when prompted 4 Use the passive FTP client to get the announcement files from the remote server to the D drive of the Announcements MAS Note: The remote server is the one on which the announcement files were placed in "Place announcement files on a server that can be accessed by the Announcement MAS" (page 106) ATTENTION You must place the announcement files on the D drive of the Media Application Server The C drive does not have enough free space NN Standard 40 8 November 2007

108 108 MAS Announcements service End Procedure 56 Configuring the announcement files on the MAS Step Action At the MAS on which the announcement files reside, 1 Select Start > Programs > Accessories > Command Prompt The Command Prompt screen appears 2 To create an announcement folder, in which to group the announcement files, enter: provtool annc_create_folder <domain> where <domain> is the provisioned domain or subdomain in which the Announcements service is available Example: provtool annc_create_folder nortelcom 3 To upload an announcement file into the announcement folder, enter the following (on one line): provtool annc_upload_media <domain> <media file> <language> <country> where <domain> is the provisioned domain or subdomain in which the Announcements service is available <media file> is the name of the branding or treatment file (in Wave File format) Include the path to the file You need not include the wav suffix <language> is the language of the recorded announcement You can specify the language as the full name (for example, English) or as a two-letter ISO code (for example, EN) <country> is an optional parameter and is the country where the language is spoken You can specify the country as the full country name (for example, United States of America) or with the ISO two-letter, three letter, or two-digit country code (for example, US) Example: provtool annc_upload_media nortelcom D:\temporarily_unavailable english US NN Standard 40 8 November 2007

109 Place treatment or source files on a MAS To support the same announcement in multiple languages, you must use the same media file name (for example, welcome) when you provision the announcement in each of the supported languages For example, if you want to upload a welcome announcement to a Media Application Server in English, French, and Japanese, (where the domain is nortelcom) you use the following commands: provtool annc_upload_media nortelcom welcome en provtool annc_upload_media nortelcom welcome fr provtool annc_upload_media nortelcom welcome jp As a result, three welcome announcements (in English, French, and Japanese) are provisioned on a Media Application Server Note that the media file name welcome (shown in bold text for emphasis) is identical in each command When you configure the welcome announcement in the Provisioning Client (see Procedure 57 "Configuring treatment routable services information for the Announcement logical entity" (page 110), or Procedure 58 "Configuring branding routable services information for the Announcement logical entity" (page 113)), you do not specify the language, only the media file name The Session Manager determines the appropriate language from the SIP messages and informs the MAS software of the appropriate language to play 5 Repeat step 3 and step4 for each announcement file that you want to upload to the announcement folder Note: For a complete list of commands available using the Provisioning Tool, enter: provtool help ATTENTION To delete audio files from a MAS (either single audio files or an entire folder), you must first lock the MAS For information about locking the Media Application Server, see "Lock the MAS" (page 83) After you delete the files, you must unlock the MAS (see Procedure 41 "Unlocking the MAS" (page 86)) End NN Standard 40 8 November 2007

110 110 MAS Announcements service Procedure 57 Configuring treatment routable services information for the Announcement logical entity Step Action From the Provisioning Client, 1 In the domain where access to the Announcements service is required, select Routable Services > Treatments/Causes > Create Treatment/Cause Files The Create Treatment Files window appears Note: In this step you are identifying the treatment files (in Wave File format) that you have already placed on one MAS in the Announcements logical entity (service instance) 2 From the list of treatment pooled entities available in this domain, choose one to which you want to assign a treatment file and click Edit Files Note: You created the pooled entities for treatments in Procedure 43 "Creating a pooled entity for a MAS service" (page 87) A new window appears to define treatment files for the service node 3 In the New File field, enter the name of a treatment file, and click Add Note: You must have already physically uploaded this treatment file onto one of the MAS in this service node The name of the treatment file must match the name of the file that was provisioned on the MAS (see Procedure 56 "Configuring the announcement files on the MAS" (page 108)) 4 Repeat step 3 for each additional treatment file that you want to add A list of treatment files now appears in the Current Files field 5 Click Save The message "Treatment files were modified successfully" appears 6 In the domain where access to the Announcements service is needed, select Routable Services > Treatments/Causes > Assign Pool The Modify Treatment Announcements Pool window appears 7 From the menu, select the logical pooled entity you created for treatments NN Standard 40 8 November 2007

111 Place treatment or source files on a MAS 111 Note: You created the pooled entities for treatments in Procedure 43 "Creating a pooled entity for a MAS service" (page 87) 8 Select the treatment service node and click Next The Assign Treatment files window appears 9 Define a group name in the Group Name field Note: You use the group name to logically associate one or more treatment (cause) reasons with treatment audio files 10 In the Available reasons field, scroll through the list of treatment reasons and select one or more of the reasons, by clicking Add Note: The Available Reasons field contains all the SIP cause messages that are supported in the current release of the Announcements service, as shown in the following table For further information, on SIP cause message triggers that are generated in a network, see RFC 3261 SIP: Session Initiation Protocol Table 1 Treatment reasons list in Available Reasons field Treatment (cause) reason 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 Message number NN Standard 40 8 November 2007

112 112 MAS Announcements service Treatment (cause) reason 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 SERVER_INTERNAL_ERROR 500 NOT_IMPLEMENTED 501 BAD_GATEWAY 501 SERVICE_UNAVAILABLE 503 GATEWAY_TIMEOUT 504 VERSION_NOT_SUPPORTED 505 BUSY_EVERYWHERE 600 DECLINE 603 DOES_NOT_EXIST_ANYWHERE 604 NOT_ACCEPTABLE 606 Message number 11 From the list of Available Files, click Add for the treatment audio files that are played when any of the treatment reasons that you selected in step 10 are generated 12 In the Repeat menu, select the number of times the treatment audio files must be repeated before the call is terminated Note: The possible values are 1 to 9, or infinite 13 In the Route field, you can specify a route to which the call is directed after the treatment has played The route can be either a URL or telephone number Note: If you plan to route the call to a number after the treatment, then you cannot select the infinite value for the Repeat field NN Standard 40 8 November 2007

113 Place treatment or source files on a MAS 113 End Procedure 58 Configuring branding routable services information for the Announcement logical entity Step Action From the Provisioning Client, 1 In the domain where access to the Announcement service is needed, select Routable Services > Branding> Create Branding Files The Create Branding Files window appears Note: In this step, you are identifying the branding files (in Wave File format) that you have already placed on one MAS in the branding logical entity (service instance) 2 From the list of branding pooled entities available in this domain, choose one to which you want to assign branding files and click Edit Folders Note: You created the pooled entities for treatments in Procedure 43 "Creating a pooled entity for a MAS service" (page 87) A new page appears to define branding files for the service node 3 In the New File field, enter the name of a branding file, and click Add Note: You must already have physically uploaded this branding file onto one of the MAS in this logical entity 4 Repeat step 3 for each additional branding file that you want to add A list of branding files now appears in the Current Files field 5 Click Save The system responds with the message Branding files were modified successfully 6 In the domain where access to the Announcements service is needed, select Routable Services > Branding > Assign Branding Files The Modify Branding Announcements Pool page appears 7 From the menu, select the logical entity you created for branding announcements NN Standard 40 8 November 2007

114 114 MAS Announcements service Note: You created this logical entity in previous steps 8 Click Next when you have selected the branding logical entity The Assign Branding files page appears 9 From the Available Files field, click on a branding file you want to use and click Add 10 Repeat step 9 for each additional branding file you want to include in this branding service node 11 If you want users that are provisioned within this domain to hear the branding announcements, then place a check mark in the Play Between Subscribers in this Domain check box Note: For information about how configuration choices at the subdomain level determine whether users hear the branding message, see Table 2 "Branding for calls between users within subdomains of a domain" (page 114) End Table 2 Branding for calls between users within subdomains of a domain Subdomain axyzcom Parent domain xyzcom Subdomain bxyzcom Domain xyzcom Branding for calls between users within axyzcom Branding for calls within bxyzcom True True True True True True False False False False False False True False True True True False False True False False False True False False True False True False False True False False False True Branding for calls between users of axyzcom and bxyzcom Custom voice prompts You can replace the existing Nortel-supplied voice prompts with custom voice prompts These voice prompts are not the branding and treatment announcements that are discussed previously NN Standard 40 8 November 2007

115 Custom voice prompts 115 Voice prompts are audio files supplied by Nortel such as the ConfEndingwav Wave file on which a voice states: The chairperson has left the conference The conference end in one minute These Nortel-supplied voice prompts are stored on the same Announcements MAS on which the branding announcements and treatment audio files are stored One reason why you might want to customize voice prompts is to replace an existing Nortel-supplied voice prompt with one that was recorded in a different dialect For example, you might want to substitute your own Cantonese voice prompts for the Mandarin voice prompts that are supplied by Nortel ATTENTION The Announcements service does not support external media source files All media source files (in this case customized voice prompts) must be in Wave File format and be resident on the Media Application Server on which the Announcements service is running (simplex deployment) one of the Media Application servers (duplex deployment) in the service node All voice prompts must be recorded in linear 16-bit PCM 8 KHz Wave File format ATTENTION When replacing existing voice prompts, you can only replace them using the same language (for example, English with English, or French with French) Nortel does not support adding new languages, due to the differences in the way times, dates, and numbers are spoken In each new release of MAS, new extensions to an existing service are added These new services may require that you make changes to your customized voice prompts You may need to rerecord some menu prompts and any additional functional prompts Keep this in mind when deciding how you contract and employ your voice talent Nortel can provide you with prompt and professional audio talent for any project For further information, the audio professionals at audio@nortelcom The Nortel audio professionals have male and female voice talent from around the world As a prerequisite to replacing existing Nortel-supplied MCS voice prompts with your own custom voice prompts, you must first transfer your new custom voice prompt Wave files to the Announcements MAS server To accomplish this, perform the following three procedures: Procedure 56 "Configuring the announcement files on the MAS" (page 108) NN Standard 40 8 November 2007

116 116 MAS Announcements service Procedure 54 "Logging on to the Announcements MAS" (page 107) Procedure 55 "Transferring announcement files to the Announcement MAS" (page 107) After you perform these three procedures, you are ready to perform the next step, Procedure 59 "Replacing existing MCS voice prompts with custom prompts" (page 116) Procedure 59 Replacing existing MCS voice prompts with custom prompts Step Action At the administrator s PC, 1 Log on to the Announcements MAS (the MAS on which the existing MCS voice prompts currently reside) by performing the procedure "Start the Media Application Server Management Console" (page 81) The Announcements MAS Windows desktop appears on the administrator s PC 2 Click the My Computer icon and navigate to the directory D:\Program Files\Nortel Networks\MAS The My Computer window appears 3 Make a copy of the Announcements folder ATTENTION Be careful not to delete, rename, or move the original Announcements folder The Announcements folder contains Wave format announcement and treatment files, as well as the Nortel-supplied MCS voice prompts (which you customize) 4 Rename the copied folder to AnnouncementsCustom 5 Open the AnnouncementsCustom folder and navigate to the meetme\default folder The default folder appears Note: All the Nortel-supplied MCS voice prompts are contained in the l16 folder The other directories are CODEC caches Voice prompt files are arranged in the directory structure according to the locale (established during provisioning) For example, the US English version of a given meetme file is located in the meetme\default\us\en\l16 directory The French version is located in the meetme\default\fr\fr\l16 directory NN Standard 40 8 November 2007

117 Custom voice prompts Open the l16 folder (in the AnnouncementsCustom directory) that contains the voice prompts you want to customize The appropriate l16 folder window appears 7 Replace the current MCS voice prompt files in the appropriate l16 folder (within AnnouncementsCustom directory) with your custom announcement files ATTENTION You must name each custom voice prompt file with the same file name of the voice prompt file it is replacing Use the information contained in Table 3 "List of MCS voice prompts in the English l16 directory" (page 117) to identify the content of the various MCS voice prompt files 8 Uninstall the Meet Me Conferencing service software, then reinstall the Meet Me Conferencing service software Note 1: To uninstall, then reinstall the Meet Me Conferencing service software, perform the procedures that are outlined in "MAS service upgrades" (page 35) Note 2: You are only required to uninstall, then reinstall the Meet Me Conferencing service software once to activate your new custom voice prompts After that, whenever you upgrade the Meet Me service software, the system automatically copies all the voice prompt files from the AnnouncementsCustom folder to the Announcements folder Note 3: To return the system to the original MCS voice prompts, you must remove or rename the AnnouncementsCustom directory, then uninstall and reinstall the Meet Me Conferencing service software End Table 3 List of MCS voice prompts in the English l16 directory File name Adminwav AudioEmoticonsOffwav AudioEmoticonsOnwav beepwav ChairCodewav English file content Please contact your local administrator Audio emoticons disabled Audio emoticons enabled beep Please enter the chairperson PIN followed by the pound key NN Standard 40 8 November 2007

118 118 MAS Announcements service File name ChairConfCtrlMenuChatnCo llabwav ChairConfCtrlMenuNoChat ChairConfCtrlMenuNoChat Collabwav ChairConfCtrlMenuNoChat CollabRecwav English file content Press star one to turn on and off audio emoticons Press star two to start or stop a conference chat room Press star three to turn on or off entry and exit notification Press star four to lock the conference Press star five to unlock the conference Press star six to mute your line Press star seven to unmute your line Press star eight to change conference continuation on chair exit Press star pound for the number of conference parties Press pound, pound or eight, eight to mute all other parties Press nine, nine to unmute all other parties Press nine one to start a collaboration session, press nine two to end the collaboration session For audio emoticons, use two zero through two nine Press zero zero for an operator Press star one to turn on and off audio emoticons Press star three to turn on or off entry and exit notification Press star four to lock the conference Press star five to unlock the conference Press star six to mute your line Press star seven to unmute your line Press star eight to change conference continuation on chair exit Press star pound for the number of conference parties Press pound, pound or eight, eight to mute all other parties Press nine, nine to unmute all other parties For audio emoticons, use two zero through two nine Press zero, zero for an operator Press star one to turn on and off audio emoticons Press star three to turn on or off entry and exit notification Press star four to lock the conference Press star five to unlock the conference Press star six to mute your line Press star seven to unmute your line Press star eight to change conference continuation on chair exit Press star pound for the number of conference parties Press pound, pound or eight, eight to mute all other parties Press nine, nine to unmute all other parties Press nine one to start a collaboration session, press nine two to end the collaboration session For audio emoticons, use two zero through two nine Press zero, zero for an operator Press star one to turn on and off audio emoticons Press star three to turn on or off entry and exit notification Press star four to lock the conference Press star five to unlock the conference Press star six to mute your line Press star seven to unmute your line Press star eight to change conference continuation on chair exit Press *9 to toggle conference recording Press star pound for the number of conference parties Press pound, pound or eight, eight to mute all other parties Press nine, nine to unmute all other parties Press nine one to start a collaboration session, press nine two to end the collaboration session For audio emoticons, use two, zero through two nine Press zero, zero for an operator NN Standard 40 8 November 2007

119 Custom voice prompts 119 File name ChairConfCtrlMenuNoChat NoOperwav ChairConfCtrlMenuWithCh at ChairConfCtrlMenuWithCha tnooperwav ChairEnterwav ChairInfoContinuewav ChairInfoTerminatewav ChairNoTerminatewav ChairTerminatewav ChatAlreadyLaunched ChatLaunched ChatLaunchFail ChatRoomDoesNotExist ChatTerminated CollabBadClientwav CollabErrorwav English file content Press star one to turn on and off audio emoticons Press star three to turn on or off entry and exit notification Press star four to lock the conference Press star five to unlock the conference Press star six to mute your line Press star seven to unmute your line Press star eight to change conference continuation on chair exit Press star pound for the number of conference parties Press pound, pound or eight, eight to mute all other parties Press nine, nine to unmute all other parties For audio emoticons, use two zero through two nine Press star one to turn on and off audio emoticons Press star two to start or stop a conference chatroom Press star three to turn on or off entry and exit notifications, Press star four to lock the conference press star 5 to unlock the conference Press star six to mute your line Press star seven to unmute your line Press star eight to change conference continuation on chair exit Press star pound for the number of conference parties Press pound, pound or eight, eight to mute all other parties press nine, nine to unmute all other parties For audio emoticons use two zero through two nine Press zero, zero for an operator Press star one to turn on and off audio emoticons Press star two to start or stop a conference chat room Press star three to turn on or off entry and exit notification Press star four to lock the conference Press star five to unlock the conference Press star six to mute your line Press star seven to unmute your line Press star eight to change conference continuation on chair exit Press star pound for the number of conference parties Press pound, pound or eight, eight to mute all other parties Press nine, nine to unmute all other parties For audio emoticons, use two zero through two nine Please press one when you are ready to enter the conference You will now be placed into conference The conference will be allowed to continue when you disconnect You will now be placed into conference The conference will be terminated when you disconnect The conference will be allowed to continue when you disconnect The conference will be terminated when you disconnect A chat room already exists for this conference A chat room has been created for this conference The chat room feature is currently unavailable This conference does not currently have a chat room The chat room for this conference has been terminated Collaboration requires the use of a multimedia client The Collaboration session has failed to start Please contact your local administrator NN Standard 40 8 November 2007

120 120 MAS Announcements service File name CollabOpenWebwav CollabSessionStartwav CollabStartwav CollabStopwav ConfEndingwav ConfEndingNowwav ConferenceFullwav ConferenceIsLocked ConferenceLocked ConferenceMuted ConferencePlacementwav ConferenceUnlocked ConferenceUnmuted ConfirmDeletewav DidNotArrivewav emotse0wav emotse1wav emotse2wav emotse3wav emotse4wav emotse5wav emotse6wav emotse7wav emotse8wav emotse9wav EnterAccesswav EnterBleepwav EnterStarwav EnterStarStandBywav EntryExitOffwav English file content Please open the web page sent to your multimedia client The Collaboration session has started The Collaboration session has started Please publish your materials using the Web page pushed to your multimedia client The Collaboration session has stopped The chairperson has left the conference The conference will end in one minute Your conference is now ending The conference you are attempting to join has reached its maximum number of participants Goodbye The conference you are attempting to join is locked Goodbye Conference locked Conference muted You will now be placed into conference Conference unlocked Conference unmuted Press one to confirm deletion of your conference greeting The chairperson has not arrived You will now be disconnected Goodbye Please enter your conference access code followed by the pound key Beep If you are the chairperson, please press the star key now If you are the chairperson, please press the star key now Otherwise stay on the line Entry and exit notification disabled NN Standard 40 8 November 2007

121 Custom voice prompts 121 File name EntryExitOnwav ExitBleepwav FastStartJoinwav Goodbyewav IntroMXMMediaConfMwav IntroVidConfwav InvalidAccessCodeAdminw av InvalidAccessCodeOperwa v InvalidChairwav InvalidPINwav MenuConfOptionswav NonChairConfCtrlMenuNoE moticons NonChairConfCtrlMenuNoE moticonsnooperwav NonChairConfCtrlMenuWith Emoticonswav NonChairConfCtrlMenuWith EmoticonsNoOperWavwav NotArrivedwav OnlyPersonwav Operatorwav OptionContinuewav OptionTerminatewav ParticipantsMutedwav ParticipantsUnmutedwav PartiesInThisConferencew av English file content Entry and exit notification enabled beep Press one to join the conference Goodbye MCS Multimedia Conferencing (with music) Nortel Video Conferencing The access code you have provided is not valid Please contact your local administrator The access code you have provided is not valid Please hold for an operator The chairperson PIN you have provided is not valid Please reenter the chairperson PIN followed by the pound key If you are not the chairperson, please press the star key The chairperson PIN you have provided is not valid Press 1 to start the conference Press 2 if this conference will require a passcode Press 3 for conference options Press star six to mute your line Press star seven to unmute your line Press star pound for the number of conference parties Press zero, zero for an operator Press star six to mute your line Press star seven to unmute your line Press star pound for the number of conference parties Press star six to mute your line Press star seven to unmute your line Press star pound for the number of conference parties For audio emoticons, use two zero through two nine Press zero, zero for an operator Press star six to mute your line Press star seven to unmute your line Press star pound for the number of conference parties For audio emoticons, use two zero through two nine The chairperson has not arrived Please continue to hold You are the only person in this conference Please hold for an operator The conference will be allowed to continue when you disconnect (duplicate) The conference be terminated when you disconnect (duplicate) Current Participants Muted Participants may unmute their line by pressing star seven Current Participants Unmuted parties in this conference NN Standard 40 8 November 2007

122 122 MAS Announcements service File name PasscodeCreatewav PasscodeInvalidwav PasscodeOptionwav PasscodePromptwav PasscodeReEnterwav PasscodeRequiredwav permgreetingconfirmwav PermGreetingDeletedwav Press00wav Press9Returnwav ReEnterAccesswav SayYourNamewav SystemLockdownwav TdOperatorwav TdStandBywav TdTryLaterwav TempGreetingConfirmwav TempGreetingDeletedwav ThankYouwav ThankYouStandBywav ThereArewav ThereArewav +%n+ Parties InThisConferencewav tmp_sorryaudioemoticons Disabledwav UserMutedwav UserUnmutedwav WaitForChairwav WaitForChairJoinwav English file content Please enter a passcode followed by the pound key The passcode you have provided is not valid Press two if this conference require a passcode Please enter the passcode followed by the pound key Please reenter the passcode followed by the pound key This conference requires a passcode Your permanent greeting is now active Permanent greeting deleted Press zero, zero for an operator Press nine to return to the previous menu The access code you have provided is not valid Please reenter the access code followed by the pound key At the sound of the tone, please say your name and press the pound key I m sorry Emergency maintenance is being performed on this system Please try your call again Goodbye We are experiencing technical difficulties Please hold for an operator We are experiencing technical difficulties Please stand by We are experiencing technical difficulties Please hang up and try your call again Your temporary greeting is now active It be deleted when this conference ends Temporary greeting deleted Thank you Thank you Please stand by There are There are <number> of parties in this conference The chairperson has disabled audio emoticons for this conference Muted Unmuted You will be placed into conference when the chairperson arrives You will join the conference when the chairperson arrives NN Standard 40 8 November 2007

123 123 MAS IM Chat service This chapter describes the MAS IM Chat service configuration Configure the MAS platform and MAS IM Chat service Use the following procedure to configure the MAS platform and IM Chat service CAUTION When the node is added in the Provisioning Client, the Enhanced IM option must be set to True for IM Chat to function properly For more information, see the Provisioning Client User Guide (NN ) Procedure 60 Configuring the MAS platform and MAS IM Chat service Step Action ATTENTION This procedure assumes that the Media Application Server is offline If the MAS has not already been deactivated, perform "Deactivate the Media Application Server" (page 82) before attempting to configure the IM Chat service software From the MAS Console, 1 From the console tree panel, select Services > System > Configuration The Details panel displays all configuration data for the Media Application Server platform ATTENTION The MAS Console displays the entire list of system parameters This procedure only discusses the parameters associated with the Announcements service NN Standard 40 8 November 2007

124 124 MAS IM Chat service 2 Double-click on a system configuration parameter to display the properties dialog window for that configuration parameter Use the values from the following table to configure the following parameters for the Media Application Server Name of parameter Type Description License Alarm Threshold License Key Local Hostname or IP Address Local SIP UDP Port SNMP Community Strings Type = integer Range = 1 to 100 Default = 90 Type = string Range = 1 to 1024 characters Default = blank Type = IP Address Default = Local IP address Type = Integer Range = 1 to Default = 5060 Type = semicolon-delimited list of SNMP Community Strings Default = public The threshold (as a percentage of available licenses) after which subsequent calls cause an alarm to be raised The license key for the Media Application Server on which the IM Chat service is running The IP address of the Media Application server on which the IM Chat service is running Note: If this value is changed, the OS network setting must be changed to match, to avoid service interruption The local UDP port for SIP messaging on the Media Application server on which the IM Chat service is running This optional item contains a semicolon-delimited list of SNMP Community Strings Note: For information on changing the default value of public, see the section on Network Considerations in Media Application Server Planning and Engineering (NN ) SNMP Management Server Type = IP address (or host name) and port (for example :9162) Default = blank This optional item contains the IP address of a third-party SNMP server 3 Click OK to save your changes 4 From the console tree panel, select Services > Chat > Configuration The Details panel displays all configuration data for the IM Chat service NN Standard 40 8 November 2007

125 Configure the MAS platform and MAS IM Chat service To configure the IM Chat service parameters, double-click on the parameter to display the properties dialog window for that parameter The following table describes the parameters to be configured Name of parameter Type Description Administrator(s) Type = string This field consists of a semicolon delimited list of IM Chat administrators Idle Duration Inactivity Duration Invitation Response Duration Maximum Message Length Maximum participants Per Room Type = integer Range = to ms Default = Type = integer Range = to Default = Type = integer Range = to Default = Type = integer Range = 100 to 1500 Default = 400 Type = integer Range = 2 to 250 Default = 100 The maximum time in milliseconds that a user (who starts an IM Chat session) has to join an IM Chat When the time is reached, the session is terminated by the system The maximum time, in milliseconds, during which there are no messages sent in a chat room (by the users who have joined the room) If no messages are sent before this value is reached, then all IM Chat sessions in this room are terminated by the system The maximum time, in milliseconds, that a individual has to respond to a an invitation to join an IM Chat The maximum message length (in characters) that a user, in an IM Chat session, can send Messages that exceed this limit are segmented and sent as multiple messages This is the maximum number of participants that are allowed in a single IM Chat NN Standard 40 8 November 2007

126 126 MAS IM Chat service Name of parameter Type Description Maximum Rooms System Rooms Type = integer Range = 1 to 250 Default = 100 Type = string Range = 0 to 256 characters Default = blank The maximum number of IM Chat rooms that are allowed This is a list of predefined chat rooms that are created by an IM Chat administrator The list is delimited by semicolon The maximum length of a room name is 20 characters The maximum total length for all room names is 256 characters 6 Click OK to save your changes End NN Standard 40 8 November 2007

127 127 MAS Meet Me Conferencing service This chapter describes the Meet Me Conferencing service configuration CAUTION Possible failure to establish service In order for the Meet Me Conferencing service to support instant message chat sessions, the Media Application Server (on which you install the Meet Me Conferencing service) must be on the public side so that clients can communicate directly with this Media Application Server (MAS) Configure the MAS platform and the MAS Meet Me Conferencing service Both the MAS platform and the Meet Me Conferencing service must be configured Configuration takes the following steps: 1 For all Meet Me servers, perform Procedure 61 "Configuring the MAS platform on all Meet Me servers" (page 128) 2 For the second server in a duplex configuration, perform Procedure 62 "Configuring the MAS platform on the second Meet Me server" (page 130) 3 For the third, fourth or fifth server in an n-way configuration, perform Procedure 63 "Configuring the MAS platform on the n-way Meet Me servers" (page 133) 4 For all Meet Me servers, perform Procedure 64 "Configuring MAS Meet Me Conferencing" (page 136) NN Standard 40 8 November 2007

128 128 MAS Meet Me Conferencing service Procedure 61 Configuring the MAS platform on all Meet Me servers Step Action ATTENTION This procedure assumes that the MAS is offline If the MAS has not already been deactivated, then deactivate it (see "Deactivate the Media Application Server" (page 82)) before you continue with this procedure At the MAS console, 1 From the console tree panel, select Services > System > Configuration The Details panel displays all configuration data for the MAS platform 2 Double-click on a system configuration parameter to display the properties window for the configuration parameter ATTENTION The MAS Console displays the entire list of system parameters This procedure only discusses the parameters associated with the Meet Me Conferencing service 3 Enter or modify the parameter value, using the following table Parameter name Field information Description Conference Port Range Starting Port Content Store Servers IVR Audio Port Range Starting Port Type = integer Range = Default = Type = semicolon-delimited list of IP addresses Default = Local IP address Note: Must contain at least one valid IP Address of a MAS hosting a Content Store Type = integer Range = Default = The Conference Media Processor uses a range of ports to provide service This value specifies the lower limit of the range RTP/RTCP starting port range This item contains a semicolon-delimited list of Media Application Servers hosting Content Stores The Multimedia Controller uses the Content Stores defined in this list The Interactive Voice Recording (IVR) Media Processor uses a range of ports to provide service This value specifies the lower limit of the range NN Standard 40 8 November 2007

129 Configure the MAS platform and the MAS Meet Me Conferencing service 129 Parameter name Field information Description License Alarm Threshold License Key Local Content Store Activated Local Hostname or IP Address Local SIP UDP Port Media Processing Units Session Manager Server(s) SNMP Community String SNMP Management Server Type = integer Range = Default = 90 Type = string Range = characters Default = blank Valid Values = YES, NO Default = YES Type = IP address Default = Local IP address Type = integer Range = Default = 5060 Default = 350 Type = a list of semicolon-delimited IP addresses and ports for the Session Manager Default = blank Type = a semicolon delimited list of SNMP Community Strings Default = public Type = IP address Default = blank The threshold (as a percentage of available licenses) after which subsequent calls cause an alarm to be raised The license key for the MAS server Whether or not the local content store is active on the MAS The IP address of the MAS server Note: If this value is changed, the OS network setting must be changed to match, to avoid service interruption The local UDP port for SIP messaging (default is 5060) Do not modify this optional value without consulting Media Application Server Planning and Engineering (NN ) The value for this optional parameter is the number of Media Processing Units available for this server This value is influenced by the number of processors, speed of processors, and other performance characteristics of the server This optional item contains a semicolon delimited list of IP addresses and ports of Session Manager Module(s) Each listed server is considered a trusted node and requests from those servers do not require authentication The first entry in the list is used for outbound messages from the media server A value must be provided to enable transfers and other outbound requests from the MAS server This optional item contains a semicolon delimited list of SNMP Community Strings Note: For information on changing the default value of public, see the section on Network Considerations in Media Application Server Planning and Engineering (NN ) This optional item contains the IP address of an SNMP server NN Standard 40 8 November 2007

130 130 MAS Meet Me Conferencing service Parameter name Field information Description SNTP Source Server SysLog Server Video Switching Hysteresis (ms) Service Administratio n Server Valid values = local host, , or a valid IP address of a designated SNTP time source server Default = xx Type = IP address Default = blank Type = integer Range = Default = 600 Type = IP address This optional item is the IP address of an SNTP time source server Specify localhost or to designate the local server as a time source If the local server is designated as a time source, the Windows time service automatically restarts to accept the configuration change For most deployments, the SNTP Source Server should be the Management Server This optional value is the IP address or host name and port of a SysLog server The default port is 514 This optional value is the time in milliseconds that a participant must assume the role of dominant speaker before the software begins transmitting their DivX video image to other conference participants Note: Changing the default value may result in an unpleasant user experience This optional value is the IP address of the Provisioning server, where information about established MAS sessions, such as Meet Me sessions, is delivered 4 Click OK 5 Repeat step 2 through step 4 for each parameter in the table 6 Click OK to save your changes End Procedure 62 Configuring the MAS platform on the second Meet Me server Step Action ATTENTION This procedure assumes that the MAS is offline If the MAS has not already been deactivated, then deactivate it using "Deactivate the Media Application Server" (page 82) before continuing with this procedure NN Standard 40 8 November 2007

131 Configure the MAS platform and the MAS Meet Me Conferencing service 131 At the MAS console, 1 From the console tree panel, select Services > System > Configuration The Details panel displays all configuration data for the MAS platform 2 Double-click on a system configuration parameter to display the properties window for the configuration parameter ATTENTION The MAS Console displays the entire list of system parameters This procedure only discusses the parameters associated with the Meet Me Conferencing service 3 Enter or modify the parameter value, using the following table Parameter name Field information Description Content Store Mirrored Peer Server Content Store Servers Controller Peer Backup Server Enable RTFT (YES/NO) Local Content Store Activated Type = IP address Default = blank Note: Must contain a single IP address Type = IP address Default = blank Note: Must contain at least one valid IP Address of a MAS Type = IP address Default = blank Note: Must contain at least one valid IP Address of a MAS Valid Values = YES, NO Default = NO Valid Values = YES, NO Default = YES This item contains the IP address of the peer Content Store for mirrored deployments For a duplex deployment, it should contain the IP address of the peer MAS This item contains a semicolon delimited list of Media Application Servers hosting Content Stores The Multimedia Controller uses the Content Stores defined in this list For a duplex deployment, it should contain the IP address of the local MAS This item contains the IP address or host name of the backup Controller Peer server for this MAS For a duplex deployment, it should contain the IP address of the local MAS Whether or not Real-Time File Transfer is used to transfer data between content store components Do not modify this value Whether or not the local content store is active on the MAS For a duplex deployment, both content stores should be activated NN Standard 40 8 November 2007

132 132 MAS Meet Me Conferencing service Parameter name Field information Description Stream Source Destination Server(s) Local SIP UDP Port Media Processing Units Session Manager Server(s) Service Administratio n Server Type = semicolon-delimited list of MAS IP addresses Default = Local IP address Type = integer Range = Default = 5060 Default = 350 Type = a list of semicolon-delimited IP addresses and ports for the Session Manager Default = blank Type = IP address This item contains a semicolon-delimited list of IP addresses of destination server(s) that should receive media from the local stream source component For a duplex deployment, it should contain the IP address of the local MAS The local UDP port for SIP messaging (default is 5060) Do not modify this optional value without consulting Media Application Server Planning and Engineering (NN ) The value for this optional parameter is the number of Media Processing Units available for this server This value is influenced by the number of processors, speed of processors, and other performance characteristics of the server This optional item contains a semicolon delimited list of IP addresses and ports of Session Manager Module(s) Each listed server is considered a trusted node and requests from those servers do not require authentication The first entry in the list is used for outbound messages from the media server A value must be provided to enable transfers and other outbound requests from the MAS server This optional value is the IP address of the Provisioning server, where information about established MAS sessions, such as Meet Me sessions, is delivered 4 Click OK 5 Repeat step 2 through step 4 for each parameter in the table 6 Click OK to save your changes End NN Standard 40 8 November 2007

133 Configure the MAS platform and the MAS Meet Me Conferencing service 133 Procedure 63 Configuring the MAS platform on the n-way Meet Me servers Step Action ATTENTION This procedure assumes that the MAS is offline If the MAS has not already been deactivated, then deactivate it using "Deactivate the Media Application Server" (page 82) before continuing with this procedure At the MAS console, 1 From the console tree panel, select Services > System > Configuration The Details panel displays all configuration data for the MAS platform 2 Double-click on a system configuration parameter to display the properties window for the configuration parameter ATTENTION The MAS Console displays the entire list of system parameters This procedure only discusses the parameters associated with the Meet Me Conferencing service 3 Enter or modify the parameter value, using the following table Parameter name Field information Description Content Store Mirrored Peer Server Content Store Servers Type = IP address Default = blank Type = IP address Default = Local IP address This item contains the IP address of the peer Content Store for mirrored deployments For the third, fourth, or fifth nodes in an multiserver deployment, it should be left blank This item contains a semicolon delimited list of Media Application Servers hosting Content Stores The Multimedia Controller uses the Content Stores defined in this list For the third, fourth, or fifth nodes in an multiserver deployment, it should contain the IP addresses of the first two MAS nodes (the two nodes with active content storage components) NN Standard 40 8 November 2007

134 134 MAS Meet Me Conferencing service Parameter name Field information Description Controller Peer Backup Server Controller Peer Primary Server Enable RTFT (YES/NO) Local Content Store Activated Stream Source Destination Server(s) Service Administratio n Server Type = IP address Default = blank Note: Must contain at least one valid IP Address of a MAS Type = IP address Default = blank Note: Must contain at least one valid IP Address of a MAS Valid Values = YES, NO Default = NO Valid Values = YES, NO Default = YES Type = semicolon-delimited list of MAS IP addresses Default = Local IP address Type = IP address This item contains the IP address or host name of the backup Controller Peer server for this MAS For information on configuring the Controller Peer relationships among the server nodes in 3-way, 4-way and 5-way deployments, see Figure 1 "Controller Peer ring configuration (3-way)" (page 135), Figure 2 "Controller Peer ring configuration (4-way)" (page 135), and Figure 3 "Controller Peer ring configuration (5-way)" (page 136) This item contains the IP address or host name of the primary Controller Peer server for this MAS For information on configuring the Controller Peer relationships among the server nodes in 3-way, 4-way and 5-way deployments, see Figure 1 "Controller Peer ring configuration (3-way)" (page 135), Figure 2 "Controller Peer ring configuration (4-way)" (page 135), and Figure 3 "Controller Peer ring configuration (5-way)" (page 136) Whether or not Real-Time File Transfer is used to transfer data between content store components Do not modify this value Whether or not the local content store is active on the MAS For the third, fourth, or fifth nodes in an multiserver deployment, it should be changed to NO This item contains a semicolon-delimited list of IP addresses of destination server(s) that should receive media from the local stream source component For the third, fourth, or fifth nodes in an multiserver deployment, it should contain the IP addresses of the first two MAS nodes (the two nodes with active content storage components) This optional value is the IP address of the Provisioning server, where information about established MAS sessions, such as Meet Me sessions, is delivered NN Standard 40 8 November 2007

135 Configure the MAS platform and the MAS Meet Me Conferencing service 135 Figure 1 Controller Peer ring configuration (3-way) Figure 2 Controller Peer ring configuration (4-way) NN Standard 40 8 November 2007

136 136 MAS Meet Me Conferencing service Figure 3 Controller Peer ring configuration (5-way) 4 Click OK 5 Repeat step 2 through step 4 for each parameter in the table 6 Click OK to save your changes End Procedure 64 Configuring MAS Meet Me Conferencing Step Action ATTENTION This procedure assumes that the MAS is offline If the MAS has not already been deactivated, then deactivate it using "Deactivate the Media Application Server" (page 82) before continuing with this procedure At the MAS console, 1 From the console tree panel, select Services > MeetMe Conferencing > Configuration The Details panel displays all configuration data for the Meet Me Conferencing service 2 Use the following table to configure the Meet Me Conferencing service parameters NN Standard 40 8 November 2007

137 Configure the MAS platform and the MAS Meet Me Conferencing service 137 Parameter name Field information Description Chat Enabled (YES/NO) Instant Messages Enabled (YES/NO) Inter- Announcement Wait Time (ms) Max Chairperson PIN Attempts Max Participant Access Code Attempts Max Participant Passcode Attempts Max Wait Segments Passcodes Enabled (YES/NO) Send Accounting INFO (YES/NO) Timer: First Digit (ms) Timer: Inter-Digit (ms) Valid Values = YES, NO Default = YES Valid Values = YES, NO Default = YES Type = integer Range = (5 seconds to 125 minutes) Default = (2 minutes) Type = integer Range = 0 25 Default = 3 Type = integer Valid Values = 0 25 Default = 3 Type = integer Valid Values = 0 25 Default = 3 Type = integer Range = Default = 10 Valid Values = YES, NO Default = YES Valid values = YES, NO Default = YES Type = integer Range = (1 second to 5 minutes) Default = 7000 (7 seconds) Type = integer Range = (1 second to 5 minutes) Default = 5000 (5 seconds) When enabled, a chat room can be launched by the conference chair person This item specifies whether the Meet Me Conferencing service should send IMs to the chairperson when events occur in the chairperson s conference bridge (for example, when a user joins the bridge) This item contains the duration in milliseconds between plays of the announcement chairperson has not arrived Please continue to hold This item contains the number of times to allow retry attempts after an invalid chairperson PIN is entered This item contains the number of times to allow retry attempts after an invalid access code is entered This item contains the number of times to allow retry attempts after an invalid passcode is entered This item contains the number of times to play the chair has not yet arrived announcement before the caller is disconnected This item specifies whether a chairperson have the ability to add a passcode to their conference bridge that participants must enter after they enter the access code for the bridge When enabled, SIP INFO messages are sent to convey accounting information This item contains the duration in milliseconds to wait for the first DTMF tone from the caller This item contains the duration in milliseconds to wait between DTMF tones before timing out NN Standard 40 8 November 2007

138 138 MAS Meet Me Conferencing service Parameter name Field information Description Timer: Star First Digit (ms) Video Enabled (YES/NO) Type = integer Range = (1 second to 5 minutes) Default : 3000 (3 seconds) Valid values = Yes, No Default = No This item contains the duration in milliseconds to wait for the caller to press the star (*) key This item allows you to enable, or disable DivX video for a MAS Note: This parameter does not enable DivX video if the appropriate keycode has not been generated for this MAS However, this parameter does allow you to disable DivX video on a MAS, thereby overriding a keycode that permits the service ATTENTION You must consistently configure this DivX video parameter for all MAS that are grouped within the same pooled entity in a subdomain This means that either all MAS (in the pooled entity) must have DivX video enabled, or all must have DivX video disabled 3 Click OK 4 Repeat step 2 through step 3 for each parameter in the table 5 Click OK to save your changes End Configuring hold music The Meet Me Conferencing service has the capability to provide music, advertisements, and/or informational audio to participants who are put on hold while waiting for the chairperson to arrive and start the conference A directory containing an audio file or files is used by the Media Application Server s Local Stream Source feature to stream one audio source to one or more users As users are put on hold, they pick up the audio stream in progress, not from the beginning NN Standard 40 8 November 2007

139 Configure Meet Me Conferencing 139 The Local Stream Source feature supports audio wav files encoded as 16-bit, 8kHz, PCM All the files in the directory are played in alphabetical order Continuous playback is achieved by repeating the sequence The directory of music must be manually populated and duplicated on each server containing the Local Stream Source instances If no audio files are present in the folder, then silence is the default hold behavior Updates to the directory can be made while the system is online The music files survive during upgrades For redundancy, a multiple server system has two Stream Source instances (located on the same servers as the Content Stores: The third server does not stream, as indicated by the Stream Source Destination Server(s) configuration item being blank in the Management Console) Each Stream Source streams locally to itself and the third server, if present Each Media Application Server has a connection to each instance Only one of the connections is used, while the other is on active stand by as a backup Procedure 65 Adding wav files for hold music Step Action At the Media Application Server, 1 Navigate to the MAS install directory The default destination directory is D:\Program Files\Nortel Networks\MAS 2 Navigate to the StreamSource\ChannelRoot\Audio subdirectory 3 Copy the wav files to this directory End Configure Meet Me Conferencing Perform the following procedures: Procedure 66 "Create an alias for Meet me pooled entity" (page 140) Procedure 67 "Configure domain parameters for Meet Me Conferencing service" (page 140) Procedure 68 "Add Meet Me Conferencing service to domain" (page 141) NN Standard 40 8 November 2007

140 140 MAS Meet Me Conferencing service Procedure 66 Create an alias for Meet me pooled entity Step Action From the Provisioning Client, 1 In the domain where access to the Meet Me Conferencing service is needed, select Routable Services > Meet Me > Create Aliases A Create Aliases for Meet Me Conferencing page appears 2 In the Alias field, enter the alias for the Meet Me Conferencing pooled entity Example: In the Select Pool drop-down menu, select the name of the pooled entity created in Procedure 43 "Creating a pooled entity for a MAS service" (page 87) Example: meetme_pool 4 In the Locale menu, select the locale the pooled entity services Example: English ATTENTION This selection determines the language used for voice prompts and announcements during conferences this pooled entity services 5 Click Save End Procedure 67 Configure domain parameters for Meet Me Conferencing service Step Action From the Provisioning Client, 1 Select Domains and then select the domain name where Meet Me Conferencing service access is required A Details for domain page appears 2 Use the Chair Ends Meet Me Conference radio button to select whether or not the Media Application Server ends a conference when the chairperson leaves NN Standard 40 8 November 2007

141 Configure Meet Me Conferencing In the Meet Me Entry/Exit Indication menu, select whether or not the Meet Me Conferencing service generates tones when participants enter or leave a conference Example: TRUE 4 Use the Meet Me IM Enabled radio button to select whether or not the Meet Me Conferencing service sends instant messages to the chairperson when conference events occur Example: TRUE 5 In the Meet Me Operator User ID field, enter the user name of the Meet Me Conferencing operator Example: meetme_operator 6 Click Modify End Procedure 68 Add Meet Me Conferencing service to domain Step Action From the Provisioning Client, 1 Select Services > Assign Services An Assign Services page appears 2 In the Select a domain menu, select the domain where the Meet Me Conferencing service is to be added Example: nortelcom 3 Click Continue An Assign services to domains details page appears 4 Select the Meet Me Conferencing check box 5 In the Maximum Number of Participants field, enter the maximum number of conference participants for any single conference Example: 32 6 Select the Premium Conferencing Enabled check box to allow the option to enable premium conferencing for any service package defined in this domain NN Standard 40 8 November 2007

142 142 MAS Meet Me Conferencing service 7 If you want to assign the DivX video conferencing feature to this domain, then select the Video Conferencing Enabled check box Note: Checking this box allows you to enable the DivX video conferencing feature for service packages defined in this domain 8 If you want to assign the Web Collaboration feature to this domain, then select the Web Collaboration Enabled check box Note: You must have the Meet Me Web Collaboration Manager installed on the Meet Me server to support this feature 9 If you want to enable the Audio Recording feature, select the Audio Recording Enabled check box 10 Click Save 11 Repeat Steps 1 through 8 for each domain where access to the Meet Me Conferencing service is required End Configure audio recording Procedure 69 Configuring the audio recording feature Step Action 1 Install SMTP server on a PC (for example, with IP address: ) 2 Add your account and user (for example, joe@abccom) 3 Configure for the Provisioning: Details for domain / Default UC Properties, type Default SMTP Server ( ) 4 Restart the MAS End Configure user-specific Meet Me Conferencing service data After the Meet Me Conferencing service has been added to all required user service packages, the administrator can enter user-specific Meet Me Conferencing service data using the User Meet Me Conferencing Properties page The system attempts to auto-populate the Access Code by using the user s business telephone number If a system-wide unique value is found, NN Standard 40 8 November 2007

143 Configure user-specific Meet Me Conferencing service data 143 the system also autopopulates the Chair PIN with a random set of digits; otherwise the Access Code field is left blank When the Access Code field is blank or if a different value is required, the administrator can manually enter a 4-to-10 digit access code The supplied access code must be unique system-wide, and is automatically verified before saving The following information can be specified for each configured conference user: Chair Ends Conference When selected, the conference ends one minute after the chairperson leaves the conference After one minute, all connected parties are disconnected, and all conference resources are freed If this options is not selected, the conference remains up until all participants leave Chair PIN This PIN is used by the conference chairperson to start the conference The PIN is a 4-to-10 digit number and can be automatically regenerated or manually changed Access Code all participants must enter this access code that uniquely identifies the conference they want to join This is often just the chairperson s phone number The Access Code is a 4-to-10 digit number that is unique system-wide Send instant messages When selected, the conference service sends instant messages to the chairperson when conference events occur (for example, when a user joins the bridge) Tones enabled When selected, the conference service generates tones when conference events occur (for example, when a user joins the bridge) Procedure 70 Provisioning Meet Me Conferencing service user-specific data Step Action From the Provisioning Client, 1 Access the user s profile data 2 Select Meet Me Properties The User Meet Me Conferencing Properties page appears for the selected user 3 If you want the conference to end when the chairperson leaves, select Chair Ends Conference 4 If Chair PIN is not automatically generated, manually enter a 4-to-10 digit number OR NN Standard 40 8 November 2007

144 144 MAS Meet Me Conferencing service Click Re-Generate PIN to automatically create a new Chair PIN 5 If a unique Access Code is not automatically generated, manually enter a system-wide unique 4-to-10 digit number 6 If you want the conference service to send instant messages to the chairperson when conference events occur, select Send instant messages 7 Optionally, change the Entry/exit Announcements option 8 Click Save 9 If Web Collaboration is required, perform Procedure 72 "Configuring the Meet Me Web Collaboration software" (page 145) End Meet Me Conferencing and Web Collaboration To use Web Collaboration from a Meet Me Conference, you must install the Meet Me Web Collaboration Manager on the Meet Me Conferencing Server Perform the following procedures to install the Web Collaboration service after Meet Me is completely installed and configured Follow Procedure 71 "Installing the Meet Me Web Collaboration software" (page 144) to install the Meet Me Web Collaboration Manager software Perform Procedure 72 "Configuring the Meet Me Web Collaboration software" (page 145) Follow Procedure 73 "Provisioning Meet Me Web Collaboration service user-specific data" (page 145) to enable the Web Collaboration in a conference Procedure 71 Installing the Meet Me Web Collaboration software Step Action At the Media Application Server, 1 Locate the MeetMeWebCollab installation program and double-click the executable The Media Application Server Install Wizard appears 2 Click Next The License Agreement window appears NN Standard 40 8 November 2007

145 Meet Me Conferencing and Web Collaboration Select I accept the terms of the license agreement 4 Click Next The Ready to Install the Program window appears 5 Click Install to perform the actual installation Note: You can press Cancel to cancel the installation When complete, the InstallShield Wizard Completed window appears 6 Click Finish to end the installation program End Procedure 72 Configuring the Meet Me Web Collaboration software Step Action At the MAS Console 1 Select Services > MeetMe Web Collaboration Conference Manager > Configuration 2 Configure the IP address of the Web Collaboration server into the Web Collaboration Primary Server IP field 3 If Secure Socket Layer is being used, configure the Enable SSL (YES/NO) field to YES OR If Secure Socket Layer is not being used, configure the Enable SSL (YES/NO) field to NO 4 Enter the Web Collaboration server host name into the Web Collaboration Primary Server Hostname field 5 Click OK to save your changes End Procedure 73 Provisioning Meet Me Web Collaboration service user-specific data Step Action From the Provisioning Client, NN Standard 40 8 November 2007

146 146 MAS Meet Me Conferencing service 1 Access the user s profile data 2 Select Customize Service Package The Service package customization page appears for the selected user 3 Scroll to themeet Me Conferencing section 4 Configure Web Collaboration Enabled as required 5 Click Save End NN Standard 40 8 November 2007

147 147 MAS Music On Hold service This chapter describes the configuration of the MAS Music on Hold service Configure the MAS platform and MAS Music on Hold service To configure the platform and service, perform the following procedures: Procedure 74 "Configuring the Media Application Server platform" (page 147) For a duplex deployment, Procedure 75 "Configuring the additional parameters for the duplex Media Application Server platform" (page 149) Music on Hold has no service-specific configuration required Procedure 74 Configuring the Media Application Server platform Step Action ATTENTION This procedure assumes that the MAS is offline If the MAS has not already been deactivated, then deactivate it using "Deactivate the Media Application Server" (page 82) before continuing with this procedure At the MAS console, 1 From the console tree panel, select Services > System > Configuration 2 The Details panel displays all configuration data for the Media Application Server platform ATTENTION The MAS Console displays the entire list of system parameters This procedure only discusses the parameters associated with the Music on Hold service NN Standard 40 8 November 2007

148 148 MAS Music On Hold service 3 Use the following table to configure the Music on Hold service parameters Parameter name Field information Description Content Store Servers Type = a semicolon-delimit ed list of IP addresses Default = Local IP address This item contains a semicolon delimited list of MAS servers hosting Content Stores The Multimedia Controller uses Note: Must contain at the Content Stores defined in this list least one valid IP address of a MAS server hosting a Content Store IVR Audio Port Range Starting Port License Alarm Threshold License Key Local Content Store Activated Local Hostname or IP Address Local SIP UDP Port Media Processing Units Type = integer Range = Default = Type = integer Range = Default = 90 Type = string Range = characters Default = blank Valid Values = YES, NO Default = YES Type = IP address Default = Local IP address Note: Must contain one valid IP address of the MAS server Type = integer Range = Default = 5060 Type = integer Default = 350 The IVR Media Processor uses a range of ports to provide service This value specifies the lower limit of the range The threshold (as a percentage of available licenses) after which subsequent calls cause an alarm to be raised The license key for the MAS server Whether or not the local content store is active on the MAS server The IP address of the MAS server Note: If this value is changed, the OS network setting must be changed to match, to avoid service interruption The local UDP port for SIP messaging (default is 5060) Do not modify this value without consulting Media Application Server Planning and Engineering (NN ) This parameter is the number of Media Processing Units available for this server This value is influenced by the number of processors, speed of processors, and other performance characteristics of the server NN Standard 40 8 November 2007

149 Configure the MAS platform and MAS Music on Hold service 149 Parameter name Field information Description Session Manager Server(s) SNMP Community Strings SNMP Management Server Syslog Server Type = semicolon-delimited list of IP addresses and ports of Session Managers Default = blank Type = semicolon-delimited list of SNMP Community Strings Default = public Type = IP address Default = blank type = string Default = blank Note: Must contain one valid IP address of the SysLog server This item contains a semicolon-delimited list of IP addresses and ports of Session Managers Each listed server is considered a trusted node and requests from those servers do not require authentication The first entry in the list is used for outbound messages from the media server A value must be provided to enable transfers and other outbound requests from the MAS server This optional item contains a semicolon-delimited list of SNMP Community Strings Note: Note: For information on changing the default value of public, see the section on Network Considerations in Media Application Server Planning and Engineering (NN ) This optional item contains the IP address of a third-party SNMP server IP address or host name and port of a SysLog server The default port is Click OK 5 Repeat step 2 through step 4 for each parameter in the table End Procedure 75 Configuring the additional parameters for the duplex Media Application Server platform Step Action ATTENTION This procedure assumes that the MAS is offline If the MAS has not already been deactivated, then deactivate it using "Deactivate the Media Application Server" (page 82) before continuing with this procedure NN Standard 40 8 November 2007

150 150 MAS Music On Hold service At the MAS console, 1 From the console tree panel, select Services > System > Configuration 2 The Details panel displays all configuration data for the Media Application Server platform ATTENTION The MAS Console displays the entire list of system parameters This procedure only discusses the parameters associated with the Music on Hold service 3 Use the following table to configure the Music on Hold service parameters Parameter name Field information Description Content Store Mirrored Peer Server Content Store Servers Controller Peer Primary Server Enable RTFT (YES/NO) Local Content Store Activated Type = IP address Default = blank Note: Must contain a single valid IP address Type = semicolon-delimited list of IP addresses Default = Local IP address Note: Must contain at least one valid IP address of a MAS server hosting a Content Store Type = IP address Default = blank Note: Must contain at least one valid IP address of a MAS Valid Values = YES, NO Default = NO Valid Values = YES, NO Default = YES This item contains the IP address of the peer Content Store for mirrored deployments For a duplex deployment, it should contain the IP address of the peer MAS This item contains a semicolon-delimited list of Media Application Servers hosting Content Stores The Multimedia Controller uses the Content Stores defined in this list For a duplex deployment, it should contain the IP address of the local MAS This item contains the IP address of the primary CPLink MAS for duplex deployments For a duplex deployment, it should contain the IP address of the peer MAS Whether or not Real-Time File Transfer is used to transfer data between content store components Do not modify this value Whether or not the local content store is active on the MAS For a duplex deployment, both content stores should be activated 4 Click OK NN Standard 40 8 November 2007

151 Place music files on a MAS Music on Hold Repeat step 2 through step 4 for each parameter in the table End Place music files on a MAS Music on Hold ATTENTION The Music on Hold service does not support external media source files All media source files must be in Wave File format and be resident on the Media Application Server on which the Music on Hold service is running (simplex deployment) or the music files must be on one of the Media Application servers (duplex deployment) in the logical entity You must physically transfer music files to one Media Application Server within the Music on Hold service node You place music files on only one Media Application Server in the service instance, because music files are replicated by the system throughout the service instance The music files that you place on the MAS must meet certain criteria These music files must be in Wave File format encoded as a single channel (mono) linear 16-bit bit stream using pulse code modulation (PCM) that is sampled at 8 khz At run time, the MAS transcodes the music files to the client settings, encoding the digital bit stream using the G711 or G729 transmission algorithm The music files are transmitted with a packet time of 10, 20, 30, or 60 milliseconds To place music files on a MAS, you must perform the following procedures: To place music files on a MAS, you must perform each of the following procedures: "Place music files on a server that can be accessed by the Music on Hold Media Application Server" (page 152) Procedure 76 "Logging on to the Music on Hold MAS" (page 152) Procedure 77 "Transferring music files to the Music on Hold MAS" (page 152) Procedure 78 "Configuring the music files on the Media Application Server" (page 153) NN Standard 40 8 November 2007

152 152 MAS Music On Hold service Place music files on a server that can be accessed by the Music on Hold Media Application Server Place the files on a server that allows passive FTP access from the Music on Hold MAS Note: The Music on Hold MAS is the MAS to which the music files are transferred Procedure 76 Logging on to the Music on Hold MAS Step Action At the administrator s PC, 1 Select Start > Programs > Administrative Tools > Terminal Services Manager The Terminal Services Manager window appears 2 Select the host name from Available Servers 3 Click Connect to start a connection to the MAS server End Procedure 77 Transferring music files to the Music on Hold MAS Step Action At the MAS on which the music files are to be transferred, 1 Launch the passive FTP client, located in the tools folder of the MAS platform files on the D drive of the Music on Hold MAS Note: Alternatively, you can launch the Microsoft Internet Explorer application (from the Start > Programs > Internet Explorer menu), and use the passive FTP functionality of the browser to transfer the announcement files 2 Within the FTP client window, input the command (for example, ftp ) to establish a passive FTP connection to the remote server on which you placed the announcement files 3 When prompted, enter your user ID and password 4 Use the passive FTP client to get the music files from the remote server to the D drive of the Music on Hold Media Application Server NN Standard 40 8 November 2007

153 Place music files on a MAS Music on Hold 153 Note: The remote server is the one on which the announcement files were placed in "Place music files on a server that can be accessed by the Music on Hold Media Application Server" (page 152) ATTENTION You must place the music files on the D drive of the Media Application Server The C drive does not have enough space for the files End Procedure 78 Configuring the music files on the Media Application Server Step Action At the MAS on which the music files reside, 1 Launch the DOS Command Prompt screen, by selecting Start > Programs > Accessories > Command Prompt The Command Prompt screen appears 2 Create a music folder on the Music on Hold MAS in which to group the music files, by entering provtool moh_create_folder <domain> <folder> where <domain> is the provisioned domain or subdomain in which the Music on Hold service is available <folder> is the named set of music files (similar to a standard file system directory or folder) Example provtool moh_create_folder nortelcom MOH_music 3 Upload music files into the music folder, by entering provtool moh_upload_media <domain> <folder> <media file> where <domain> is the provisioned domain or subdomain in which the Music on Hold service is available <folder> is the named set of music files (similar to a standard file system directory or folder) NN Standard 40 8 November 2007

154 154 MAS Music On Hold service <media file> is the name of the music file (in Wave File format) that you want to place in the music folder (you must include the path to the file) Example provtool moh_upload_media nortelcom MOH_music D:\music1wav Note: For a complete list of commands available using the Provisioning Tool, enter the following command: provtool help ATTENTION To delete audio files from a Media Application Server (either single audio files, or an entire folder), you must first lock the Media Application Server For information on locking the Media Application Server, see "Lock the MAS" (page 83) After you finished deleting the files, you must unlock the Media Application Server (see "Unlock the MAS" (page 85)) End Enable service access to the Music on Hold service Enabling service access allows the network to route Music on Hold service requests to the Music on Hold service Configuring service access to the Music on Hold service consists of the following steps: Procedure 79 "Configuring Routable Services information for the Music on Hold logical entity" (page 154) Procedure 80 "Enabling the Music on Hold service in the end user service packages" (page 156) The configuration tasks described here use provisioning tasks that are described in detail in the Provisioning Client User Guide (NN ) Procedure 79 Configuring Routable Services information for the Music on Hold logical entity Step Action From the Provisioning Client, 1 In the domain where you require access to the Music on Hold service, select Routable Services > Music on Hold > Create Music Folder A Create Music Folders page appears NN Standard 40 8 November 2007

155 Place music files on a MAS Music on Hold 155 Note: In this step you are identifying the music folder (or folders), containing music files in Wave File format, that you already placed on one of the MAS in the Music-on-Hold service nodes (service instance) 2 From the list of Music on Hold pooled entities available in this domain, choose one to which you want to assign a music folder or folders, and click Edit Folders Note: You created the pooled entities for Music on Hold in Procedure 43 "Creating a pooled entity for a MAS service" (page 87) A new page appears where you define music folders for the service node 3 In the New Folder field, enter the name of a music folder, and click Add Note: You must have already physically uploaded this music folder (containing music files in Wave File format) onto one of the MAS in this service node by performing "Place music files on a MAS Music on Hold" (page 151) 4 Repeat step 3 for each additional music folder that you want to add A list of music folders appears in the Current Folders field 5 Click Save The system responds with the message Music Folders were modified successfully 6 In the domain where access to the Music on Hold service is needed, select Routable Services > Music on Hold > Assign Music Folders The Modify Music on Hold Pool page appears 7 From the Select Pool menu, select the logical entity you have created for the Music on Hold service 8 Select the Music on Hold logical entity and click Next The Assign Folder page appears 9 Select from the Select Folder field the Music on Hold folder that you defined in step 3 10 Click Save A confirmation screen appears NN Standard 40 8 November 2007

156 156 MAS Music On Hold service End Procedure 80 Enabling the Music on Hold service in the end user service packages Step Action From the Provisioning Client 1 In the domain where access to the Ad Hoc Conferencing service instance is needed, select Service Package > List Packages The List of Packages for domain page appears for this domain 2 Click Details-Modify for the service package in which the Ad Hoc Conferencing service is to be enabled The Package Details page appears for the selected service package 3 Select Music on Hold 4 Save the change: Click Save and Enforce Now to immediately enable the service for all users on this domain who are actively subscribed to this service package Click Save and Enforce later to enable the service for all users on this domain when they resubscribe to this service package This occurs when a user reconnects to the network or when their service package subscription is automatically refreshed 5 Repeat steps 1 to 4 for each service package where access to the service is needed End NN Standard 40 8 November 2007

157 157 MAS Meet Me Web Collaboration service This chapter describes the Meet Me Web Collaboration service installation and commissioning The installation method for Web Collaboration differs from the other MAS services ATTENTION Before you start installing the Web Collaboration service, you must install the Meet Me Conferencing service For installation information, see "MAS service installation types and road maps" (page 26) Installation overview The following figure illustrates a basic Meet Me Installation NN Standard 40 8 November 2007

158 158 MAS Meet Me Web Collaboration service The figure below shows a Meet Me Web Collaboration installation, which has a Web Collaboration server installed behind the Meet Me Pool Installation requirements CAUTION Do not install the MAS Base software on an IBM x335, x336, Blade Center, or BladeCenter T system that is being used as a Web Collaboration Server Installation of the Web Collaboration Server requires the following: IBM x3550, x335, x336, Blade Center, or BladeCenter T systems with standard Media Application Server (MAS) 40 image/windows 2000 Server or Windows Server 2003 operating system Two network IP addresses Microsoft Internet Explorer 60 or later Microsoft SQL Server 2000 Desktop Engine (MSDE) Microsoft Office 2003 (Word, Excel, PowerPoint), English version only Nortel MAS Web Collaboration Server Installer Optional: Two SSL 128 Super Certs (required if https is to be used) WARNING Follow the steps precisely and in order, or the installation can fail NN Standard 40 8 November 2007

159 Web Collaboration scaled installation 159 The following figure shows the installation order Note: Microsoft Office 2003 is not supplied by Nortel Web Collaboration scaled installation One standalone Web Collaboration server supports 1000 ports Web Collaboration servers cannot be configured in clusters That is, at most, one Web Collaboration server is mated with a MAS Meet Me server pool In this way, the number of ports supported by the largest Meet Me pool (five servers) does not exceed the number of ports a single Web Collaboration server can handle A Web Collaboration server can even serve multiple, smaller Meet Me pools For example, two duplex Meet Me pools can use one Web Collaboration server Pool Options The following figure shows the single five-way pool configuration NN Standard 40 8 November 2007

160 160 MAS Meet Me Web Collaboration service A second configuration offers a dedicated server per pool, as shown in the following figure NN Standard 40 8 November 2007

161 Web Collaboration scaled installation 161 And a third configuration allows a shared server across pools NN Standard 40 8 November 2007

162 162 MAS Meet Me Web Collaboration service MAS software One standalone Web Collaboration server supports 1000 ports They cannot be configured in clusters That is, at most, one Web Collaboration server is mated with a MAS Meet Me server pool In this way, the number of ports supported by the largest Meet Me pool (five servers) does not exceed the number of ports a single Web Collaboration server can handle A Web Collaboration server can serve multiple, smaller Meet Me pools For example, two duplex Meet Me pools can use one Web Collaboration server NN Standard 40 8 November 2007

163 Install the Meet Me Web Collaboration server 163 Security configuration All Web communications with participant Web browsers can be encrypted using SSL (Secure Socket Layer) through the HTTPS protocol IIS on the Web Collaboration server must be setup for SSL by an administrator The MAS Console provides optional control of SSL Navigate to Nortel MAS Console > Services > Web Collaboration > Configuration and set the SSL Enabled property as required Web Collaboration server ports The Web Collaboration server uses http or https protocols to communicate with the MAS-Meet Me server and participants in the Web Collaboration session The Web Collaboration server has two IP addresses The Primary IP communicates with the MAS Meet Me server and with client browsers for Presentations Application Sharing mode communicates with the clients using the Secondary IP Public Internet access For public Internet access using Web Collaboration, you must configure the firewall as follows: Source: Any Destination: <Primary Collab IP address> Ports: TCP 80 and 443 Source: Any Destination: <Secondary Collab IP address> Ports: TCP 80 and 443 Note: If you are not using SSL, you do not need to open port 443 on the firewall Install the Meet Me Web Collaboration server To install the Meet Me Web Collaboration server, perform the following set of procedures Preinstallation downloads You require Internet Explorer 60 and Microsoft SQL Server 2000 Desktop Engine (MSDE) for the installation, which you can download at wwwmicrosoftcom NN Standard 40 8 November 2007

164 164 MAS Meet Me Web Collaboration service Procedure 81 Downloading Internet Explorer 60 and MSDE Step Action 1 From the Microsoft home page (wwwmicrosoftcom), navigate to Product Resources->Downloads->Product Technology->Internet Explorer->Go 2 Save the downloaded file (ie6setupexe) to a temporary folder (for example, D:\ie6install) 3 From a command prompt window, navigate to the temporary folder that contains the ie6setupexe file and enter the following command ie6setupexe /c:"ie6wzdexe /d /s:""#e" 4 Accept the default settings for Windows 2000 Server to set up the offline installer 5 from the Microsoft home page, navigate to Product Resources->Downloads->Product Technology->SQL Server->Go->Microsoft SQL Desktop Engine Save the downloaded file to a temporary folder (for example, D:\msdeinstall) 7 If you are using the Windows Server 2003 operating system, download Server 2003 Service Pack 1 from wwwmicrosoftcom End Configure network IP addresses and port filtering You must configure the MASTeam network adaptor with two different IP addresses, as described in the following procedure The primary IP address is used with the MAS Meet Me server and client browsers for document publishing Application sharing mode uses the secondary IP address Procedure 82 Configuring network IP addresses and port filtering Step Action From the administrator s PC: 1 Select Start > Control Panel > Network Connections > MASTeam 2 On the MASTeam Status dialog box, click Properties NN Standard 40 8 November 2007

165 Install the Meet Me Web Collaboration server On the MASTeam Properties dialog box, select Internet Protocol (TCP/IP) 4 Click Properties 5 On the Internet Protocol (TCP/IP) Properties dialog box, enter the primary IP address, the Subnet mask, and the Default gateway 6 Click Advanced 7 On the Advanced TCP/IP Settings dialog box, under IP Addresses, click Add 8 On the TCP/IP Address dialog box, enter the secondary IP address and the Subnet mask 9 Click Add 10 On the Advanced TCP/IP Settings dialog box, click the Options tab 11 Select TCP/IP Filtering and click Properties 12 On the TCP/IP Filtering dialog box, ensure that Enable TCP/IP Filtering (all adapters) is selected 13 Select Permit Only, and then click Add 14 On the Add Filter dialog box, enter 80 and click OK 15 On the TCP/IP Filtering dialog box, click Add 16 On the Add Filter dialog box, enter 443 and click OK 17 On the TCP/IP Filtering dialog box, click Add 18 On the Add Filter dialog box, enter 3389 and click OK 19 Click OK to save and close the dialog boxes 20 If you are prompted to reboot the server, click No End Install Network Services Perform the steps in the following procedure to install Network Services NN Standard 40 8 November 2007

166 166 MAS Meet Me Web Collaboration service Procedure 83 Installing Network Services Step Action From the administrator s PC: 1 Select Start > Control Panel > Network Connections > MASTeam 2 On the MASTeam Status dialog box, click Properties 3 On the MASTeam Properties dialog box, click Install 4 On the Select Network Component Type dialog box, select Service and click Add 5 On the Select Network Service dialog box, select File and Printer Sharing for Microsoft Networks, and then click OK 6 On the MASTeam Properties dialog box, click Install 7 On the Select Network Component Type dialog box, select Client and click Add 8 On the Select Network Client dialog box, select Client for Microsoft Networks, and then click OK 9 Close the MASTeam Properties dialog box and the MASTeam Status dialog box End Configure Local Security Policy settings To modify a security setting, double-click the policy entry in the right pane to edit the value and ensure settings match the verified values To add a user to the policy, edit the policy entry, and then select Add User or Group > Advanced > Find Now (select the search result entry in the bottom panel) Procedure 84 Configuring Local Security Policy settings Step Action 1 Select Start > Programs > Administrative Tools > Local Security Policy NN Standard 40 8 November 2007

167 Install the Meet Me Web Collaboration server 167 Figure 4 Local Security Settings - Password Policy 2 Select Account Policies > Password Policy 3 Ensure that Minimum password length and Password must meet complexity requirements are disabled 4 Select Local Policies > User Rights Assignment 5 Ensure that Access this computer from the network contains the value Everyone 6 Ensure that Deny Access to this computer from the network and Deny logon locally are empty Figure 5 Local Security Settings - User Rights Assignment NN Standard 40 8 November 2007

168 168 MAS Meet Me Web Collaboration service Figure 6 Local Security Settings window 7 Select Local Policies > Security Options 8 If you have the Windows Server 2003 operating system, ensure that Network access: Let Everyone permissions apply to anonymous users is enabled 9 Close the Local Security Settings window End Install Microsoft Internet Explorer If you do not already have Internet Explorer 60 or later installed, perform the steps in the following procedure to install it Procedure 85 Installing Internet Explorer 60 Step Action 1 Navigate to the temporary folder you created in "Preinstallation downloads" (page 163) 2 Double-click ie6setupexe 3 Accept all default values 4 Reboot the server End NN Standard 40 8 November 2007

169 Install the Meet Me Web Collaboration server 169 Install Microsoft Internet Information Services Use the procedure for your operating system to install Microsoft Internet Information Services (IIS) Procedure 86 Installing IIS for Windows 2000 Server Step Action 1 Select Start > Settings > Add/Remove Programs 2 Click Add/Remove Windows Components 3 Select Internet Information Services (IIS), and then click Details Figure 7 Internet Information Services (IIS) dialog box 4 Select (check) all components except NNTP and click OK 5 Click Next 6 On the Terminal Services Setup dialog box, select Remote administration mode, and then click Next 7 On the Files Needed dialog box, click Browse to navigate to the IIS I386 folder (from CD or zip file) 8 From the I386 folder, select ADMXPROXDL_ and click Open 9 On the Files Needed dialog box, click OK 10 When the IIS configuration is complete, click Finish NN Standard 40 8 November 2007

170 170 MAS Meet Me Web Collaboration service 11 Close the Add/Remove Programs dialog box End Procedure 87 Installing IIS for Windows Server 2003 Step Action 1 Install Server 2003 Service Pack 1 from the executable you downloaded earlier (see "Preinstallation downloads" (page 163)) 2 Select Start > Control Panel > Add/Remove Programs 3 Click Add/Remove Windows Components 4 On the Windows Components dialog box, ensure that only Accessories and Application Server are checked 5 Select Application Server and click Details 6 On the Application Server dialog box, ensure that only Enable Network COM+ Access and Internet Information Services (IIS) are checked 7 Select Internet Information Services (IIS) and click Details 8 Under Subcomponents of Internet Information Services (IIS), enable (check) the following subcomponents only (ensure all other subcomponents are cleared): Common Files File Transfer Protocol (FTP) Service Internet Information Services Manager SMTP Service World Wide Web Service 9 Click OK 10 On the Application Server dialog box, click OK 11 On the Windows Component dialog box, click Next 12 When the configuration is complete, click Finish End NN Standard 40 8 November 2007

171 Install the Meet Me Web Collaboration server 171 Install Microsoft Office 2003 Perform the steps in the following procedure to install Microsoft Office 2003 Install the English version only Procedure 88 Installing Microsoft Office 2003 Step Action 1 Run the Office setup executable file from the CD 2 When prompted, enter the CD key and click Next 3 In the User/Organization field, enter your user or organization name and click Next 4 Select I accept the terms of the license agreement and click Next 5 Select Custom 6 Set the Install to directory to D:\Program Files\Microsoft Office\ and click Next 7 Select Word, Excel, and PowerPoint to install and click Next 8 Click Install This step can take several minutes 9 Select Check the Web for updates and additional downloads and click Finish (optional) To perform this step, you must have a DNS server configured End Install Microsoft SQL Server Desktop Engine Perform the steps in the following procedure to install Microsoft SQL Server Desktop Engine (MSDE) Procedure 89 Installing MSDE Step Action 1 Execute the self-extracting installer from the preinstallation download steps and unzip the msde files to a temporary folder (for example, D:\msdeinstall) 2 In the unzipped msde files folder, right-click setupini and select Open with > Notepad NN Standard 40 8 November 2007

172 172 MAS Meet Me Web Collaboration service 3 Add the following lines below the [Options] keyword: SAPWD="admin" SECURITYMODE=SQL 4 In the unzipped msde folder, double-click setupexe 5 When prompted, click Yes to restart the server 6 After the server restarts, check to see if MSSQL service is started and running End Install SSL (optional) If your network requires the installation of Secure Socket Layer (SSL) for the MAS Meet Me Web Collaboration service, perform these procedures Procedure 90 "Creating the server1ssl certificate request" (page 172) Procedure 91 "Obtaining the server1sslcer certificate" (page 173) Procedure 92 "Installing the server1ssl security certificate" (page 174) Procedure 93 "Creating the server2ssl certificate request" (page 174) Procedure 94 "Obtaining the server2sslcer certificate" (page 175) Procedure 95 "Installing the server2ssl certificate" (page 176) Procedure 96 "Adding the certificates to the system" (page 176) Procedure 90 Creating the server1ssl certificate request Step Action At the management PC, 1 Under Admin Tools, open the Internet Service Manager (ISM), which loads the Internet Information Server snap-in for the Microsoft Management Console (MMC) 2 Right-click the Default Website and click Properties 3 Click the Directory Security tab, and then click Server Certificate to start the Web Server Certificate Wizard 4 Click Next 5 Select Create a new certificate 6 Click Next NN Standard 40 8 November 2007

173 Install the Meet Me Web Collaboration server Select Prepare the request now, but send it later 8 Click Next and enter the following: a Server name: server1ssl b Bit length: 1024 c If your users may be coming from countries with encryption restrictions, select Server Gated Cryptography 9 Click Next and enter the following: a Organization: Domainname Inc b Organizational Unit: Operations 10 Click Next and enter the Common Name: server1domainnamecom 11 Click Next and enter your country, state, and city Example: Country: US State: Massachusetts City: Billerica 12 Click Next and enter: C:\SSLcerts\wipssltxt 13 Click Next 14 Review the summary and, if necessary, go back and make changes 15 Click Next 16 Click Finish 17 Click OK End Procedure 91 Obtaining the server1sslcer certificate Step Action 1 Send the wipssltxt to the company that creates your Certificate 2 After you have received the completed certificate, copy it to C:\SSLcerts\server1sslcer End NN Standard 40 8 November 2007

174 174 MAS Meet Me Web Collaboration service Procedure 92 Installing the server1ssl security certificate Step Action 1 Finish processing the request within IIS to install the certificate to the server and enable SSL 2 Open the Internet Information Services MMC 3 Right-click the Default Website on and click Properties 4 Click the Directory Security tab 5 Click Server Certificate and click Next 6 Select Process the pending request and install the certificate and click Next 7 Enter the path and file name of the certificate as follows: C:\SSLcerts\server1sslcer 8 Click Next twice, and then click Finish to complete the wizard 9 Click the Website tab, and verify that the SSL Port text box is populated with the port Click OK End Procedure 93 Creating the server2ssl certificate request Step Action 1 Right-click the Data Site Website and click Properties 2 Click the Directory Security tab, and then click Server Certificate to start the Web Server Certificate Wizard 3 Click Next 4 Select Create a new certificate 5 Click Next 6 Select Prepare the request now, but send it later NN Standard 40 8 November 2007

175 Install the Meet Me Web Collaboration server Click Next and enter the following: a Name: server2ssl b Bit length: 1024 c If your users may be coming from countries with encryption restrictions, select Server Gated Cryptography 8 Click Next and enter the following: a Organization: Domainname Inc b Organizational Unit: Operations 9 Click Next and enter the Common Name as follows: server2domainnamecom 10 Click Next and enter your country, state, and city Example: Country: US State: Massachusetts City: Billerica 11 Click Next and enter the following: C:\SSLcerts\server2ssltxt 12 Click Next 13 Review the summary and, if necessary, go back and make changes 14 Click Next 15 Click Finish 16 Click OK End Procedure 94 Obtaining the server2sslcer certificate Step Action 1 Send the wip2ssltxt to the company that creates your Certificate 2 After you have received the completed certificate, copy it toc:\sslcerts\server2sslcer End NN Standard 40 8 November 2007

176 176 MAS Meet Me Web Collaboration service Procedure 95 Installing the server2ssl certificate Step Action 1 Finish processing the request within IIS to install the certificate to the server and enable SSL 2 Open the Internet Information Services MMC, right-click Data Site Website on and click Properties 3 Click the Directory Security tab, and then click Server Certificate 4 Click Next 5 Select Process the pending request and install the certificate 6 Click Next and enter the path and file name of the certificate as follows:c:\sslcerts\server2sslcer 7 Click Next twice 8 Click Finish to complete the wizard 9 Click the Website tab, and make sure that the SSL Port text box is populated with the port Click OK End Procedure 96 Adding the certificates to the system Step Action 1 Back up or Export a Web Server Certificate(s) from IIS 50 2 Select Start > Run, type MMC, and then click OK 3 From the Console Menu list, select Add/Remove Snap-in 4 Click Add 5 Find and highlight Certificates and click Add 6 Select Computer account 7 Click Next NN Standard 40 8 November 2007

177 Install the Meet Me Web Collaboration server Select Local computer 9 Click Finish 10 Click Close 11 Click OK 12 Expand Certificates 13 Expand Personal 14 Select Certificates From the right side you see a list of your certificates 15 Right click on server1domainnamecom and select All Tasks 16 Click Export The Certificate Export Wizard starts 17 Click Next 18 Select Yes to export the private key 19 Click Next 20 Select Personal Information Exchange and Enable strong protection 21 Ensure that Include all certificates and Delete the private key are cleared 22 Click Next 23 Enter and confirm the following: The password is: server1ssl The file name: C:\SSLcerts\server1backpfx 24 Click Next 25 Click Finish 26 On The export was successful message box, click OK To backup the certificate for the Data Site 27 Right click on server2domainnamecom and select All Tasks 28 Click Export The Certificate Export Wizard starts NN Standard 40 8 November 2007

178 178 MAS Meet Me Web Collaboration service 29 Click Next 30 Select Yes to export the private key 31 Click Next 32 Select Personal Information Exchange and Enable strong protection 33 Ensure that Include all certificates and Delete the private key are cleared 34 Click Next 35 Enter and confirm the following: The password is: server2ssl The file name: C:\SSLcerts\server2backpfx 36 Click Next 37 Click Finish 38 On The export was successful message box, click OK 39 Close the window End Install the Web Collaboration Server software Perform the steps in the following procedure to install the Web Collaboration server software Procedure 97 Installing the Web Collaboration Server software Step Action At the management PC: 1 Execute the Web Collaboration Server Installshield program 2 On the Welcome dialog box, click Next 3 On the License Agreement dialog box, select I accept the terms in the License Agreement and click Next 4 On the Network Information dialog box, in the Primary field, enter the name of the primary Web server (for example, NN Standard 40 8 November 2007

179 Install the Meet Me Web Collaboration server 179 server1domaincom) or the primary IP address (the IP address assigned to Local Area Connection) 5 In the Secondary field, enter the secondary Web server name (for example, server2domaincom) or the secondary IP address (the IP address assigned to Local Area Connection 2) and click Next 6 On the Ready to Install the Program dialog box, click Install 7 On the Web Collaboration Server License Key dialog box, in the Enter License Key field, enter the Web Collaboration server license key and clickok Note: If the license key is not yet available, click OK to complete the installation and perform Procedure 99 "Modifying the license key after installation" (page 180) to enter and apply the license key Although the installation completes successfully, the Web Collaboration Server cannot provide service until you supply a valid license key The following steps may take several minutes Do not attempt to close the CMD windows To test the Microsoft Office 2003 installation, Microsoft Word, PowerPoint, and Excel windows appear 8 Close each Microsoft Office window 9 Click Finish to complete the installation 10 When prompted to restart the server, click Yes End Configure Web Collaboration Administration Perform the steps in the following procedure to configure Web Collaboration Administration Procedure 98 Configuring Web Collaboration Administration Step Action At the management PC, 1 To log on to WebInterpoint Administration: a Open Internet Explorer and enter the following address: NN Standard 40 8 November 2007

180 180 MAS Meet Me Web Collaboration service b Log on with the user name admin and the password admin 2 Change the Admin Password a From the left side of the window, click Change Password b In the New Password field, enter a new password c In the Confirm New Password field, enter the password again d Click OK End Modify the license key after installation Perform the steps in the following procedure to modify the license key after installing the Web Collaboration server software Procedure 99 Modifying the license key after installation Step Action At the management PC, 1 Select Start > Programs > Nortel Web Collaboration Server > License Key Management 2 On the Web Collaboration Server Modify License Key dialog box, in the Enter the License Key field, enter the Web Collaboration server license key 3 Click Apply 4 Restart the server to apply the changes End Install Web Collaboration on the Meet Me Conferencing server To install Web Collaboration onto the Meed Me Conferencing server, perform the following procedure Procedure 100 Installing Web Collaboration on the Meet Me Conferencing server Step Action On the Meet Me Conferencing server, NN Standard 40 8 November 2007

181 Install the Meet Me Web Collaboration server Perform Procedure 97 "Installing the Web Collaboration Server software" (page 178) 2 Perform Procedure 98 "Configuring Web Collaboration Administration" (page 179) End Web Collaboration upgrades Web Collaboration upgrades use: "Upgrade the Web Collaboration Server software Maintenance Release" (page 181) "Upgrade Web Collaboration from Release 3x to Release 40" (page 182) ATTENTION This section only covers upgrades to the stand-alone Web Collaboration server For information on the upgrades of the other MAS servers, see "MAS service upgrades" (page 35) Upgrade the Web Collaboration Server software Maintenance Release Follow these steps to upgrade the server software ATTENTION This section only covers upgrades to the stand-alone Web Collaboration server For information on the upgrades of the other MAS servers, see "MAS service upgrades" (page 35) Procedure 101 Upgrading the server software Step Action At the management PC, 1 Select Start > Settings > Add/Remove Programs > Nortel Networks Web Collaboration Server and click Remove 2 Install the new software load as described in "Install the Web Collaboration Server software" (page 178) End NN Standard 40 8 November 2007

182 182 MAS Meet Me Web Collaboration service Upgrade Web Collaboration from Release 3x to Release 40 Use the following procedure to upgrade from Release 3x ATTENTION This section only covers upgrades to the stand-alone Web Collaboration server For information on the upgrades of the other MAS servers, see "MAS service upgrades" (page 35) Procedure 102 Upgrading from Release 3x to Release 40 Step Action At the management PC, 1 Click Start > Settings > Control Panel > Add/Remove Programs 2 Remove Nortel Networks Web Collaboration Server 3 Remove WebInterpoint Server 4 Close the Add/Remove Programs window 5 Right-click My Computer and select Manage 6 Choose Services/Applications > Services and stop the MSSQLSERVER service ATTENTION The MSSQLSERVER must be stopped in order for the MSDE uninstall to work properly 7 Click Control Panel > Add/Remove Programs, and remove Microsoft SQL Server Desktop Engine 8 Click Administrator Tools > Data Sources (ODBC) System DSN tab, remove localpc data source 9 Click Control Panel > Add/Remove Programs > Add Remove Windows Components, clear IIS and select Next to remove 10 Remove the following folders: C:\Program Files\Microsoft SQL Server and D:\inetpub\wwwroot\* 11 Reboot the server (required after uninstalling WIP) 12 Follow the full install procedure for IIS, MSDE and reboot 13 After the reboot, run the WebCollab Server installer NN Standard 40 8 November 2007

183 Install the Meet Me Web Collaboration server 183 End Web Server Security Hardening (optional) Perform the following steps to secure the Microsoft IIS Web Server: Procedure 103 Securing the Microsoft IIS Web Server Step Action At the management PC, 1 Download the IIS lockdown tool from wwwmicrosoftcom/technet/security/tools/locktoolmspx 2 Run the IIS lockdown tool executable and the Welcome to the Internet Information Services Lockdown Wizard window appears 3 Click Next The License Agreement window appears 4 Select I agree, then click Next The Select Server Template window appears 5 Select the Dynamic Web server (ASP enabled) entry, enable the View template settings checkbox, and select Next to display the Internet Services window 6 Enable the Web service (HTTP) and File Transfer service (FTP) checkboxes, ensure other checkboxes are not enabled, and select Next to display the Script Maps window 7 Enable all of the Script Maps except for Active Server Pages (asp), and select Next to display the Additional Security window 8 Enable all of the settings except for Scripts and Writing to content directories, and select Next to display the URLScan window 9 Enable Install URLScan filter on the server, and select Next twice to apply the settings The dialog Applying Security Settings is displayed when the tool completes 10 Select Next to complete the process and the Completing the Internet Information Services Lockdown Wizard appears 11 Select Finish to exit the IIS lockdown tool NN Standard 40 8 November 2007

184 184 MAS Meet Me Web Collaboration service End Note: To restore the server to its previous settings (undo IIS lockdown setting changes), run the tool again Enable Web Collaboration on the MCS The Meet Me Conferencing service must be properly installed following the instructions in "MAS service installation types and road maps" (page 26) Configuration includes: Meet Me Conferencing service added to the domain The Meet Me Routable service in the domain is configured with a pool to route to the MAS Web Collaboration extends Meet Me functionality Procedure 104 Enabling Web Collaboration on the Meet Me Conferencing server Step Action Using the Provisioning Client, 1 Go toprovisioning >Services > Assign Services 2 Under the Meet Me Conferencing heading, enable Web Collaboration by checking the Web Collaboration Enabled box End Configure Web Collaboration in the Service Package To configure Web Collaboration in the Service Package, perform the following procedure Procedure 105 Configuring Web Collaboration in the Service Package Step Action At the Provisioning Client, 1 Go to Provisioning > Domains > yourdomain > Service Package > List Packages 2 Select Details-modify NN Standard 40 8 November 2007

185 Install the Meet Me Web Collaboration server Under the Meet Me Conferencing heading, enable or disable Web Collaboration End Note: The number of Web Collaboration ports is based on the maximum number of participants value specified for the Meet Me Conferencing service Reinstalling the Windows Server 2003 operating system Perform the steps in the following procedure to reinstall the Windows Server 2003 operating system in the case of failure Procedure 106 Reinstalling the operating system Step Action 1 Insert the Windows Server 2003 restore CD into the DVD drive of the Media Application Server 2 Reboot the server from the CD The system prompts you to press any key to boot from the CD 3 Press any key to continue 4 If necessary, repartition the drive (10 GB to the first partition, remainder of the drive to the second partition) 5 Select the first partition for the installation 6 Select Format the partition using the NTFS file system 7 Press Enter From this point, the installation of Windows Server 2003 is automatic When the installation is complete, you are prompted with a Windows Server 2003 logon screen End NN Standard 40 8 November 2007

186 186 MAS Meet Me Web Collaboration service NN Standard 40 8 November 2007

187 187 MAS services upgrades This chapter provides information about MAS services upgrade procedures General information about MAS software upgrades Upgrades are performed using many of the same procedures as those used during installation However, the order of the procedures is slightly different for upgrades Note 1: Configuration data is preserved during the upgrade Note 2: In the event of hardware replacement or upgrades, see "Hardware replacement" (page 227) ATTENTION This section describes upgrades for all MAS servers, other than the stand-alone Web Collaboration server For the Web Collaboration server upgrade, see <ref> Media Application Server services upgrades The MAS services are installed using an intuitive InstallShield installation program For every new release, or patch release of the MAS service executable, a new installation program is created During an upgrade, the installation program stops the current MAS service instance, replaces its executable, and restarts the MAS service instance again Note: Patch releases are cumulative, the latest patch bundle installation program contains all previous patches CAUTION In simplex MAS deployments, performing a software upgrade results in a temporary service outage The duration of the service outage is less than five minutes In scaled MAS deployments (for example, duplex deployments), no service outage occurs if servers are upgraded one at a time NN Standard 40 8 November 2007

188 188 MAS services upgrades During a Media Application Server framework upgrade, the MAS service instance running on the targeted Media Application Server becomes temporarily unavailable in the network This MAS service instance becomes available after the service is restarted (upon successful restarting of the Media Application Server framework) In scaled networks, continuous access to the Media Application Server service during upgrades is achieved by performing Media Application Server upgrades one server at a time Prior to upgrading an instance of the MAS service, or of the Media Application Server that instance is running on, the service is set to Pending Lock While the service is in the pending lock state, all new MAS service requests are rejected by this instance, and are routed to one of the remaining in-service MAS service instances (located on different Media Application Servers) Existing conferencing traffic on the instance to be upgraded can be allowed time to clear on its own, as conferences end When the target instance has no more (or an acceptable minimal amount of) active traffic on it, the service is set to Locked Once locked, the MAS service (and or the Media Application Server hosting that service) can be upgraded After the upgrade is complete, the service can be restarted and unlocked Once the service is unlocked, incoming MAS service requests are handled by the service instance, instead of being routed to another MAS service instance located on a different Media Application Server Nortel recommends that upgrades be performed during the maintenance window, or at some other off peak usage time Placing the upgrade target service instance in the Pending Lock state several hours prior to the actual maintenance window helps ensure that a minimum number of conferences, if any, are still present on the upgrade target when the service is actually upgraded during the maintenance window Supported software upgrade paths The following software upgrade paths are supported for the Media Application Server service: Release 3x to Release 40 Release 4x to Release 4x Both these paths use the same procedures Upgrade to Release 4x software upgrade procedures This procedure outlines the steps required to install a new version of MAS on the same server with the old version Note: These steps ensure the Meet Me Conferencing user properties are restored NN Standard 40 8 November 2007

189 Upgrade to Release 4x software upgrade procedures 189 MAS upgrade These steps are required in the installation of a new version of MAS on the same server with the old version of MAS If a new MAS is installed on a new server, you need not perform this step ATTENTION For Meet Me Web Collaboration service upgrade procedures, see "Upgrade the Web Collaboration Server software Maintenance Release" (page 181) System data includes all configuration parameters which are visible in the MAS Console A System Data backup and restore can be performed with the system online and unlocked, however the MAS must be restarted after restoration in order for the configuration parameter changes to take effect Procedure 107 Backup system configuration data on the existing MAS Step Action From the system management MAS console, 1 Create a System Data backup archive Click Control Panel > Backup/Restore > System Data > Create Backup Archive The system backup selection displays the dialog that prompts the user for the archive name and destination The filename can be changed, but defaults to the MASSYS prefix indicating a system data archive followed by the host name, date and timestamp The destination folder should be D:\MASBackup 2 Create a Service Data Backup Archive Click Control Panel > Backup/Restore > Service Data Full > Create Backup Archive Service data includes user data which resides in the Content Storage area A partial service backup archives all data except multimedia files A full service backup includes all data included in a partial backup in addition to multimedia files The full service data backup selection displays the dialog that prompts the user for the archive name and destination The filename can be changed, but defaults to the MASSVC_FULL prefix indicating a full service data archive followed by the host name, date and timestamp The destination folder should be D:\MASBackup 3 Transfer the Backup Files to a temporary location The previously created zip file archives for System Configuration and Service data must be transferred to an FTP server using the MAS passive-mode FtpClient command line tool NN Standard 40 8 November 2007

190 190 MAS services upgrades a Open a command prompt window using Start > Programs > Accessories > Command Prompt b Enter D: The working directory changes to the D: (data) drive c Enter cd MASBackup (or folder where the zip files were previously stored) The current directory becomes the backup folder d Enter FtpClient d (destdir) put (ftpserver) (username) (password) (file) where ftpserver is the host name or IP Address of the remote FTP Server username is the FTP Username password is the FTP Password destdir is the Remote Host Destination file is the Backup ZIP file name FtpClient launches the command to send files using FTP Example: FtpClient d D:\MASarchive put masserver1 ftpuser ftppwd *zip Backup archives and zip files can be placed on a Web Server for installation on the new MAS End Procedure 108 Upgrading the MAS Step Action 1 Install and commission the new MAS Server (or upgrade) The new MAS (platform and services) should be installed (or upgraded) in accordance with "MAS service installation types and road maps" (page 26) If installing new hardware, a new MAS License Key is required 2 Transfer Backup File Archives from the temporary location to the new server a Create a new folder named D:\MASBackup NN Standard 40 8 November 2007

191 Upgrade to Release 4x software upgrade procedures 191 b Retrieve the System Configuration and Service data backup zip files using HTTP with Internet Explorer and download into the D:\MASBackup folder 3 Restore the System Data Backup Archive Note: This step is required in case of a new version of MAS is installed on the same server with old version of MAS If a new MAS is installed on a new server, do not perform this step a To restore System configuration data from the previously created backup archive, select Control Panel > Backup/Restore > System data > Restore b Select Open on the previously archived system backup file to restore the data After system data restoration, the server must be restarted c Click Control Panel > Operations > Restart 4 Restore the Service Data Backup a Shut down the MAS component software b After the MAS stops, select the restore menu option c Click Control Panel > Backup/Restore > Service data Full > Restore d Select the backup archive restore from the dialog to perform the extraction of the files in the Content Storage area 5 Update the system configuration It may be required to change the IP Address of the MAS server (in the System Management Console, folder Network Data and Mtc/Addresses) on the MCS, if the IP Address of the MAS server was changed The Session Manager server property in the MAS console should be updated with the new IP address of the Session Manager End NN Standard 40 8 November 2007

192 192 MAS services upgrades Multiapplication MAS upgrade procedures This section outlines the supported upgrade paths and software upgrade procedures for the multiapplication MAS deployment The underlying assumption is that you are upgrading a MAS server with MAS service to a multiapplication MAS server The multiapplication MAS deployment enables you to install the following MAS services on the same MAS platform: Ad Hoc Conferencing service Meet Me Conferencing service Music on Hold service Announcements service IM Chat service ATTENTION For the multiapplication MAS deployment, you install from two to five MAS services on the same MAS platform; however, in order to simplify the explanation, this document assumes that you are installing all five MAS services You may install the five MAS services in any order Multiapplication MAS software upgrades This list outlines the procedures you use to upgrade the software on a MAS platform from the single application MAS to the multiapplication MAS deployment Place the MAS in Pending Lock state Check for active sessions Lock the MAS system Deactivate the MAS system Uninstall the MAS service software Are you upgrading the MAS platform software as well as the MAS service software? If so, uninstall and reinstall MAS platform software If not, install the MAS service software Install Meet Me, Music on Hold, Announcements and IM Chat service software, one after another Activate the MAS service Unlock the MAS system Note: To perform a multiapplication MAS maintenance release upgrade, use the procedure in "Multiapplication MAS software upgrades" (page 192) The steps are the same for an upgrade and a maintenance release upgrade, with one exception When you are told, in the procedure, to NN Standard 40 8 November 2007

193 Upgrade to Release 4x software upgrade procedures 193 uninstall the MAS service software, you must also uninstall all the other MAS services (one after another) that are part of the multiapplication MAS deployment NN Standard 40 8 November 2007

194 194 MAS services upgrades NN Standard 40 8 November 2007

195 195 MAS registration and keycodes This chapter describes the procedures for registering your MCS system and generating the keycodes Overview During the installation of Media Application Server (MAS) software, you must supply a keycode (license key) for the features installed on the MAS Before you can install the MAS software, you must register your site and generate the keycode for the MAS features (or services) that you have purchased You must input the keycode during software installation Note: For the multiapplication MAS deployment, you need only one keycode The following table describes the action and the procedure required to register and obtain your keycode If you are installing a new MCS with MAS installing a new MAS adding a new MAS server to an existing MAS system Then follow Procedure 109 "Registering your MCS system and generating keycodes" (page 196) Procedure 110 "Generating Media Application Server keycodes" (page 207) "Expand a system by adding a Media Application Server" (page 216) Register your MCS system and generate keycodes Before you can begin generating keycodes, you must first register (or create) your site on the Keycode Retrieval System (KRS) Web page The site normally consists of one or more Management and Accounting servers (known as the Core) and one or more Media Application Servers (known as the Media Server) NN Standard 40 8 November 2007

196 196 MAS registration and keycodes Each server have two MAC addresses You must determine those MAC addresses because you need to identify them to the KRS during the site registration process The following screen shots show a simple configuration and generation of one keycode for the management and accounting servers MCS Core, and one keycode for the Media Application Server Procedure 109 Registering your MCS system and generating keycodes Step Action At the management PC 1 Open your Web browser and go to the following URL: wwwnortelcom 2 From the main Nortel Web page, expand the Support and Training menu, and select Keycode Retrieval The Keycode Retrieval window appears 3 In the Step 1 field, use the menu to select the location of the KRS server to which you want to log on Example North American Login NN Standard 40 8 November 2007

197 Register your MCS system and generate keycodes In the Step 2 field, use the menu to select Multimedia Communication Portfolio as the product family whose keycodes you want to register 5 Click Go to jump to the secure Log In page NN Standard 40 8 November 2007

198 198 MAS registration and keycodes 6 Enter your User ID, password, and click Log In The Keycode Retrieval System page appears NN Standard 40 8 November 2007

199 Register your MCS system and generate keycodes Click Create to register a new system A screen appears where you identify your company site 8 Fill in the company name for your site, and the city, then use the menus to select the country, and state (or province), then click Continue Note: The location of North America is assumed for the rest of this procedure A screen appears where you indicate the type of server you are registering 9 Select which server you want to enter MAC addresses for and click Create Note: This procedure assumes that you are adding the Management and Accounting Server (Core) first, followed by a Media Application Server A page appears where you add the first MAC address NN Standard 40 8 November 2007

200 200 MAS registration and keycodes 10 Enter the first MAC address of the server and click Add 11 Repeat step10 for the second MAC address of the server Note: If you make an error, you can remove one or both and begin again If you have a second Core server that is going to be installed as a redundant server, enter all four MAC addresses at this time 12 Repeat steps 9, 10, and 11 for the Media Application Server Note: In step 9 you must select MEDIA SERVER In steps 10 and 11, you must add the two MAC addresses for the Media Application Server NN Standard 40 8 November 2007

201 Register your MCS system and generate keycodes If you have a second Media Application Server for your system, you must repeat steps 9, 10, and 11 for the second MAS, since only two MAC addresses can be associated with any one Media Application Server If you do not have a second Media Application Server, proceed now to step After you add both MAC addresses of the last Media Application Server, click Continue The system displays a summary page of your entries NN Standard 40 8 November 2007

202 202 MAS registration and keycodes 15 Click Save to complete registering your system (or click Cancel and begin again) The system displays the following Web page NN Standard 40 8 November 2007

203 Register your MCS system and generate keycodes Click Gen KC with Auth Code (in the side bar) to generate keycodes for this site A page appears where you identify your system 17 To generate your keycodes, enter one of the MAC addresses of the server to which you want to apply your authorization code Note: The example Web page in the figure shows the MAC addresses of the CORE 18 Click Add The KRS automatically searches for and pulls up both MAC addresses associated with the CORE The system displays both MAC addresses NN Standard 40 8 November 2007

204 204 MAS registration and keycodes 19 Click Continue A page appears where you identify the software version of your system NN Standard 40 8 November 2007

205 Register your MCS system and generate keycodes Select the proper Software Version for your system and click Continue A page appears where you enter your Auth Code 21 Enter the authcode number for the feature you want to enable Note: Use your system Authorization codes to build your license key file 22 Select Add to have the KRS accept the authcode The KRS validates the authcode and ensures that the features represented are valid for your server type (CORE or MAS) If validated successfully you will be allowed to enter more authcodes until you have entered all the codes for your server 23 After the process is complete, click Continue A summary of the features appears The following example shows a summary of the features represented by all the sample authcodes entered This screen shows the current features enabled and the new features to be added to your server In a new installation there are no features displayed 24 If the list is correct, click Continue NN Standard 40 8 November 2007

206 206 MAS registration and keycodes The KRS indicates that it is generating your keycodes and saving the results in its database After generating the keycodes, the system shows the Retrieve Keycode page where you can view the features enabled for the server From this page, you can download the keycode (see the figures below) The screens show the features of your keycode and the option to download the keycode to your local PC Note: The two following figures are two sections of a single Web page Because of the large size of the Web page, it is shown as two figures NN Standard 40 8 November 2007

207 Generate keycodes for a Media Application Server To download the keycode, click Download Keycode 26 You are asked to save the keycode file to your PC The file is provided with a product-specified naming convention 27 Download the new license key file to the MgmtSvr hard drive You need the license key during the installation of Media Application Server software End Generate keycodes for a Media Application Server This procedure instructs you how to generate keycodes for the Media Application Server This procedure assumes that you have already registered your site on the KRS (Keycode Retrieval System) Web page Procedure 110 Generating Media Application Server keycodes Step Action At the management PC, NN Standard 40 8 November 2007

208 208 MAS registration and keycodes 1 If you are already logged on to the Keycode Retrieval System (and you have registered your site), then go to step 8; otherwise, proceed with step 2 2 Open your Web browser and go to wwwnortelcom/indexhtml 3 From the main Nortel Web page, expand the Support and Training menu, and select the Keycode Retrieval command 4 In the Step 1 field, use the menu to select the location of the KRS server to which you want to log on Example North American Login NN Standard 40 8 November 2007

209 Generate keycodes for a Media Application Server In the Step 2 field, use the menu to select Multimedia Communication Portfolio as the product family whose keycodes you want to register 6 Click Go to jump to the secure Log In page NN Standard 40 8 November 2007

210 210 MAS registration and keycodes 7 Enter your User ID and password, then click Log In The Keycode Retrieval System page appears NN Standard 40 8 November 2007

211 Generate keycodes for a Media Application Server Click the Gen KC with Auth Code link (in the side bar) to proceed to Generate Keycodes for the Media Application Server A page is displayed where you identify your system 9 To generate your keycodes, enter one of the MAC addresses of the Media Application Server to which you want to apply your authorization code 10 Click Add The KRS automatically searches for and pulls up both MAC addresses associated with the Media Application Server The window now displays both MAC addresses NN Standard 40 8 November 2007

212 212 MAS registration and keycodes 11 Click Continue The system displays a page where you identify the software version of your system NN Standard 40 8 November 2007

213 Generate keycodes for a Media Application Server Select the proper Software Version for your system, then click Continue The system displays a page where you enter your Auth Code 13 Enter the authcode number for the feature you want to enable Note: Use your system Authorization codes to build your license key file 14 Select Add to have the KRS accept the authcode The KRS validates the authcode and ensures that the features represented are valid for your server type (CORE or Media Server) If validated successfully, you can enter more authcodes until you have entered all the codes for your server 15 After this process is complete, click Continue The system displays a summary of the features Note: The following example shows a summary of the features represented by all the sample authcodes entered This screen shows the current features enabled and the new features to be added to your server In a new installation there are no features displayed NN Standard 40 8 November 2007

214 214 MAS registration and keycodes 16 If the list is correct, click Continue The KRS indicates that it is generating your keycodes and saving the results in its database After generating the keycodes, the system shows the Retrieve Keycode page where you can view the features enabled for the server From this page you can download the keycode (see the figures below) The screens show the features of your keycode and the option to download the keycode to your local PC Note: The following two figures are two sections of a single Web page Because of the large size of the Web page, it is shown as two figures NN Standard 40 8 November 2007

215 Generate keycodes for a Media Application Server To download the keycode, click Download Keycode 18 You are asked to save the keycode file to your PC The file is provided with a product-specified naming convention NN Standard 40 8 November 2007

216 216 MAS registration and keycodes 19 Download the new license key file to the MgmtSvr hard drive End Expand a system by adding a Media Application Server Perform the steps in the following procedure to add another Media Application Server to your system Note: This procedure assumes that you have already registered your system Procedure 111 Adding an additional Media Application Server to your system Step Action At the management PC, 1 Determine the MAC address of the new Media Application Server that you are adding to the system 2 If you are already logged on to the Keycode Retrieval System (and you have registered your site), then go to step 8; otherwise, proceed with 3 3 Open your Web browser and go to the following URL: wwwnortelcom NN Standard 40 8 November 2007

217 Expand a system by adding a Media Application Server From the main Nortel Web page, expand the Support and Training menu and select the Keycode Retrievalcommand 5 In the Step 1 field, use the menu to select the location of the KRS server to which you want to log on Example North American Login NN Standard 40 8 November 2007

218 218 MAS registration and keycodes 6 In the Step 2 field, use the menu to select Multimedia Communication Portfolio as the product family whose keycodes you want to register 7 Click Go to jump to the secure Log In page NN Standard 40 8 November 2007

219 Expand a system by adding a Media Application Server Enter your User ID and password, and then click Log In The Keycode Retrieval System page appears NN Standard 40 8 November 2007

220 220 MAS registration and keycodes 9 Click the Product Registration link (in the side bar) A page appears where you identify your site name 10 Enter the site name you want to edit, or any of the MAC addresses previously associated with the site and click Search When the site is found by the KRS system, the system displays the site name in a menu NN Standard 40 8 November 2007

221 Expand a system by adding a Media Application Server Click Continue The information that you entered when you first registered the site appears You can edit this information if you want NN Standard 40 8 November 2007

222 222 MAS registration and keycodes 12 After you are satisfied the information is correct, click Continue The system displays a page where you can add the new Media Application Server 13 Add the new MAS to your system by selecting MEDIA SERVER from the menu, then click Create The system displays an empty MEDIA SERVER field for entering MAC data NN Standard 40 8 November 2007

223 Expand a system by adding a Media Application Server Enter a MAC address for the new Media Application Server in the MEDIA SERVER field, then click Add 15 Repeat step 14 for the second MAC address, then go to step 16 The system displays both of the MAC addresses that you have entered NN Standard 40 8 November 2007

224 224 MAS registration and keycodes 16 Verify the MAC addresses you entered are correct and click Continue A summary page appears NN Standard 40 8 November 2007

225 Expand a system by adding a Media Application Server Verify the data is correct and click Save, or click Cancel You have completed the procedure to add the Media Application Server to your system; however, you still need to generate keycodes for this Media Application Server End NN Standard 40 8 November 2007

226 226 MAS registration and keycodes NN Standard 40 8 November 2007

227 227 Changing MAS hardware This chapter describes the steps that are required if the MAS hardware must be changed This change can be due to replacing defective hardware updating to newer versions of the same hardware platform updating to a newer hardware platform Hardware replacement In the event of a hardware replacement or upgrade, follow these steps Procedure 112 Replacing or upgrading the hardware Step Action From the management PC, 1 If possible, perform the data backup procedures on the old hardware, as described in Routine Maintenance (NN ) 2 Decommission the old hardware 3 Install the new hardware 4 Install the Media Application Server services 5 Restore the data backup End NN Standard 40 8 November 2007

228 228 Changing MAS hardware NN Standard 40 8 November 2007

229 229 Fault management This chapter provides information on the following topics: "MAS fault management strategy" (page 229) "MAS OAM/Fault Integration" (page 229) MAS fault management strategy The MAS platform software is configured as an operating system service (NT service) that is started and monitored by the operating system (OS) automatically If any MAS platform software subcomponent fails, the OS restarts the component immediately and a log is generated An alarm is also raised to report this condition until the component is registered with the remainder of the system, at which point the alarm is cleared The Media Application Server (MAS) generates alarms in response to fault conditions that degrade or interrupt operation of the service In general, MAS alarms may require you to take action to correct the fault condition MAS services rely on the MAS platform software to provide alarm generation mechanisms After you, or the system, have corrected a fault, the MAS software automatically clears the alarm condition All alarms are logged, and a second log is generated to record the new status after an alarm is cleared The MAS platform software also provides an event logging mechanism The event logging mechanism is a standardized and centralized way to report relevant software and hardware events MAS OAM/Fault Integration The MCP Media Application Server (MAS) was developed separately from the core MCP Provisioning, Management and Database server components This feature integrates MAS fault reporting into the MCP console MAS deployment, operations and management (OAM) functionality are outside the scope of this feature for release 40 NN Standard 40 8 November 2007

230 230 Fault management The feature begins the integration of the MAS OAM into the MCP 40 console This effort is limited in scope to the inclusion of log and alarm notifications from the MAS to the MCP console via SNMP traps MAS deployment continue to be implemented by a dedicated installer Existing MAS servers can be provisioned within the MCP console allowing the management server to receive communications from each MAS Similarly the MCP management SNMP address server be provisioned in the existing MAS console SNMP agent functionality is implemented on the MAS platform This agent send SNMP trap messages to the MCP FPM and provide access to the platform alarm table These traps contain the pertinent alarm, fault and logging information The FPM in turn update the alarm snapshot in the MCP console Upon restart the FPM query all associated MAS servers to determine their alarm state then reflect that view to the MCP console The FPM can also be configured to update the MAS alarm snapshot on regular intervals In this manner the alarm views can be brought back into synchronization in the event the SNMP UDP trap messages do not reach the FPM Note: When configuring Web Collaboration, the SNMP service is started to allow MCS management console to show MAS and WebCollab alarms For more information about Fault Management, see Alarm and Log Reference (NN ) NN Standard 40 8 November 2007

231 231 Maintenance This chapter describes some MAS maintenance procedures related to installation and commissioning For routine maintenance of MAS, see Routine Maintenance (NN ) Change the hostname after initial deployment Use this procedure to change the hostname after initial network deployment Procedure 113 Changing the hostname Step Action At the management PC, 1 Start the Notepad program 2 Select File > Open 3 Navigate to D: > Program Files > Nortel > Nortel Networks > MAS > Conference Manager > configini and click Open 4 Find the line containing [ESAServerList] 5 Replace the configured hostname with the new hostname 6 Select File > Save 7 Restart the MAS server 8 Ensure that Web Collaboration works with the new hostname End NN Standard 40 8 November 2007

232 232 Maintenance NN Standard 40 8 November 2007

233 233 BCT configuration worksheet Table 4 BCT worksheet A shared BladeCenter T (BCT) chassis is populated by filling Border Control Point (BCP) resources from the top downward (for example, slot 1 through slot 8), and filling Media Application Server (MAS) resources from the bottom upward (for example, slot 8 through slot 1) This method reduces complexity and simplifies maintainability It also ensures that open slots in a shared chassis are available for growth of either BCP or MAS components Reversing this process is possible also, with the BCP components from bottom upward and the MAS components from top downward Successful configuration of the MAS and BCP depends on the accurate capture of configuration information The information that is required for provisioning the BCT should be collected prior to installation If you configure all eight Blades on the BCT, you keep a record of eight individual slots (one for each Blade, each with its own set of attributes) The following table should be completed BCT Configuration Information Slot Attribute Example Value 1 Service: Host card network address (Portal address) Host card netmask Host card default gateway Host card IP failover active Hostname Timezone YES RTP_04 US/Central Timeserver IP address NN Standard 40 8 November 2007

234 234 BCT configuration worksheet 2 Service: 3 Service: 4 Service: 5 Service: Host card network address (Portal address) Host card netmask Host card default gateway Host card IP failover active Hostname Timezone YES RTP_04 US/Central Timeserver IP address Host card network address (Portal address) Host card netmask Host card default gateway Host card IP failover active Hostname Timezone YES RTP_04 US/Central Timeserver IP address Host card network address (Portal address) Host card netmask Host card default gateway Host card IP failover active Hostname Timezone YES RTP_04 US/Central Timeserver IP address Host card network address (Portal address) Host card netmask Host card default gateway Host card IP failover active Hostname Timezone YES RTP_04 US/Central Timeserver IP address NN Standard 40 8 November 2007

235 BCT configuration worksheet Service: 7 Service: 8 Service: Host card network address (Portal address) Host card netmask Host card default gateway Host card IP failover active Hostname Timezone YES RTP_04 US/Central Timeserver IP address Host card network address (Portal address) Host card netmask Host card default gateway Host card IP failover active Hostname Timezone YES RTP_04 US/Central Timeserver IP address Host card network address (Portal address) Host card netmask Host card default gateway Host card IP failover active Hostname Timezone YES RTP_04 US/Central Timeserver IP address NN Standard 40 8 November 2007

236 236 BCT configuration worksheet NN Standard 40 8 November 2007

237 237 Appendix A DivX Multipoint Video conferencing The DivX Multipoint Video conferencing feature adds video capabilities to the existing Media Application Server (MAS) Meet Me and Ad Hoc conferencing services The following chapter documents how to provision video for the MAS Meet Me and Ad Hoc conferencing features and is divided into the following sections: "Network Engineering" (page 237) "Configuration" (page 245) "User Guide" (page 253) Network Engineering This feature is initially targeted to support up to 100 simultaneous video participants (streams) for each server The actual procedure for handling resource (port) allocation is unchanged Video is added through the licensing of audio ports on the MAS A smaller number of audio ports is typically allocated for each MAS (or by pool) for video-enabled servers For example, if a MAS is keyed for 100 ports of G711 audio and 100 ports of G729 audio but is not keyed for video, then the MAS can potentially support 200 audio ports If instead the MAS is keyed for 50 ports of G711 and 50 ports of G729 but is also keyed for video, then the MAS can not only potentially support 100 audio ports but can also potentially support 100 video ports as well Overview This feature provides support for the DivX video codec when used in conjunction with the MAS conferencing services The video for an active speaker in a conference is tracked and streamed to the other participants The only codec supported for video conferencing is DivX Video is available NN Standard 40 8 November 2007

238 238 Appendix A DivX Multipoint Video conferencing for Multimedia PC Client and Multimedia Web Client users This feature supports up to 100 simultaneous video participants (streams) for each server Audio-only clients can participate in video conferences although they cannot send or receive video This feature supports all audio codecs and clients currently supported by the MAS (no new audio codec support is provided as part of this feature) This feature is supported on the IBM xseries 335, 336, and 3550, the IBM XBlade, the IBM eserver BladeCenter, and the IBM BladeCenter Telecom The xseries 306 platform is not supported by this feature CAUTION Only Nortel-certified software may be installed on the IBM BladeCenter T Do not install software updates obtained directly from IBM Negotiation of video parameters Prior to the arrival of the Meet Me conference chair at a conference, each party that arrives in the conference is placed on music-on-hold (audio only; video is temporarily suspended for video-capable parties) Upon the chair s arrival, the audio and video begin transmitting as each party subsequently joins the conference The chair first negotiates with the MAS to determine a compatible video parameter set For this feature, the only video codec supported by the MAS (and, therefore, available for video negotiation) is the DivX codec; however, the MAS supports all video resolutions supported by the Nortel Multimedia PC and Web clients Once the chair negotiates a compatible video parameter set (video codec and resolution) with the MAS, this set becomes the default video parameter set to be used when negotiating with subsequent parties in the conference For each party that subsequently joins the conference, the video negotiation mechanism attempts to find a suitable match between the party s offered (video) Session Description Protocol (SDP) and the default video parameter set established by the chair If a matching parameter set is successfully negotiated, the party can send/receive video as part of the conference; if a suitable match is not found, the party cannot send/receive video for this conference The frame rate is not a video parameter setting A user s video frame rate is not forced to the conference chair s frame rate The MAS adjusts the frame rate downward for lower-bandwidth parties That is, if a particular party supports a frame rate lower than the frame rate of the current active speaker s video stream, then the MAS sends some subset of the active NN Standard 40 8 November 2007

239 Network Engineering 239 speaker s video stream to the lower-bandwidth party Neither does the MAS adjust the frame rate upward for higher-bandwidth parties - that is, if a particular party supports a frame rate higher than the frame rate of the current active speaker s video stream The MAS simply sends the full video stream to the higher-bandwidth party For completeness, a number of special negotiation cases are addressed: Conference chair is audio-only: If the conference chair is not video-capable, no video codec or resolution is negotiated as part of the conference s default video parameter set and is therefore not present for negotiation with any subsequent parties Because of this, video is negotiated out of all parties capabilities sets; the conference effectively becomes an audio conference Conference chair is video receive-only: If the conference chair is video-enabled but is capable only of receiving video, the default video parameter set (video codec, video resolution) is still negotiated as usual; the chair simply does not transmit video (and, obviously, can never gain the video focus) All other video-enabled parties in the conference still negotiate to the chair s video codec and resolution, but, other than that, their abilities to send/receive video are unaffected by the chair s video receive-only status Conference chair is transferred: When the conference chair s party transfers or, similarly, drops out of and then subsequently reenters the conference, that party loses its chair-specific privileges and becomes another party in the conference As such, the default video parameter set for the conference remains frozen at its originally negotiated settings; it is not renegotiated upon the [former] chair s re-entry into the conference, and the [former] chair, upon re-entry, is subject to the constraints of this default video parameter set Switched video support When there are multiple video-enabled users in a conference, the MAS determines what video content to deliver to all the users Video switching is employed by the MAS to determine video content During the conference, each video-enabled party receives the video stream from one, and only one, other video-enabled party Although the video stream can change many times during the course of a conference, only one video stream is delivered to a party at any given instant The MAS conferencing engine, as part of its audio processing for a conference, computes the most active speaker at given intervals Using this information, the MAS makes a decision on which video stream to send to a given party The basic video switching rules are At a given point during a conference, all video-enabled conference parties, except for the current active speaker, receive the active speaker s video stream NN Standard 40 8 November 2007

240 240 Appendix A DivX Multipoint Video conferencing At the same time, the active speaker receives a placeholder video stream, stored at and delivered from the MAS directly Examples of placeholder content are a blank screen or some simple text/graphics indicating that the party is the current active speaker The general video switching rules are modified when the active speaker is an audio-only party (that is, no video present) All video-enabled conference parties receive a placeholder video, similar to the active speaker s placeholder video in the basic decision rule Examples of placeholder content are a blank screen or some simple text/graphics indicating that the current active speaker is an audio-only party The MAS does not decompress or decode the incoming video streams The MAS reflects the video streams based on the current choice of active speaker All parties in the conference irrespective of whether or not they can send video, still receive the mixed audio stream for the conference Video switching hysteresis The MAS video switching mechanism tracks the active speaker for a video conference and employs a specified amount of video switching hysteresis That is, a video-enabled speaker must be deemed to be the most active speaker for some specified amount of time before actually gaining the video focus The intent behind this delayed switch-over is to prevent the video focus from switching unintentionally (and too frequently) between video streams due to spurious active speaker decisions, for example, a brief noise spike that causes a speaker to (unintentionally) be deemed the most active speaker at a given point in time Video switching hysteresis does not actually delay the delivery of video streams to the end parties upon a change in active speaker Video streams continue to be delivered to video-enabled parties during this switch-over interval What the hysteresis does do is delay the change from displaying the previous active speaker s video to displaying the new active speaker s video in the outgoing video streams For more information, see "Setting video switching" (page 245) Network bandwidth Unlike audio media streams, which have a fixed bandwidth for each stream, video media streams typically have a variable bit rate for each stream The bit rate of a video stream (more accurately, of the output of the DivX video codec) depends on the nature of the video content being encoded, for example, the visual complexity or detail of the scene and the amount of motion present in the scene NN Standard 40 8 November 2007

241 Network Engineering 241 For the application being considered by this feature (video conferencing), a typical scene consists of "head and shoulders" video with limited, constrained motion, for example, a speaker sitting at his office desk The network video bandwidth guidelines provided in Table 5 "Network bandwidth guidelines" (page 241) are given with this typical application in mind The following table shows typical figures derived from empirical evidence; they cannot be considered as absolute guidelines owing to the variable bit rate nature of the video Though they accurately reflect the time-averaged behavior of the video content supported by this feature, temporary spikes in the video bit rate are possible Table 5 Network bandwidth guidelines Video setting client Very Low Low Medium High Description Enables video over dialup connection 160x120 video resolution, 2 frames/second (fps) Enables video over ISDN / DSL / cable modem 160x120 video resolution, 8fps Enables video in an office through high-speed LAN 320x240 video resolution, 10 fps Enables video in an office through high-speed LAN 352x288 video resolution, 15 fps Video bandwidth, client (typical) kilobits / second (kbps) kbps 12 Mbps kbps 30 Mbps kbps 80 Mbps Video bandwidth, network (by server) 2000 kbps, or 2 megabits / second (Mbps) QoS markings The MAS originates QoS DiffServ (DS) markings for outbound media packets For the specific QoS DS markings to be used, see Media Application Server Planning and Engineering (NN ) Key coding A license key attribute determines whether or not a MAS conference server has video enabled for its conferences The video license key enables video for each server (not by channel or by conference) The video license key only enables or disables the use of (DivX) video It does not, for example, restrict the number of concurrent codec instances or channels as is done with audio codecs NN Standard 40 8 November 2007

242 242 Appendix A DivX Multipoint Video conferencing Note: All servers pooled within a subdomain must be keyed identically For example, all servers must be either be keyed with video enabled or all keyed with video disabled RTCP feedback is not employed to dynamically adapt to network congestion (Note that this is actually a limitation of the MAS and is not specific to this feature) Bridged conferences Bridged (chained) video conferences may not behave as expected If there is a single dominant speaker in a bridged video conference, then the active speaker s video is switched as expected If there is no single dominant speaker, there may be unexpected video switching For example, if there are two equally active parties (one in each half of a bridged video conference) then a different active speaker is chosen in each half of the bridge As a result, the active speaker video shown in one half of the bridge is different from the active speaker video shown in the other half Another bridging issue occurs when the bridged leg is chosen as the active speaker In this case, every party in the bridged conference receives the placeholder video Normally, the placeholder video should only be seen by the active speaker Dependencies For a description of MCS network component dependencies, see the following table Table 6 MCS network component dependencies MCS Component Session Manager Border Control Point MCS network dependency Expected to be able to forward video-related lines in the SDP, for example, a=rtpmap attributes specifying the video RTP mapping(s) Expected to be able handle video Realtime Transport Protocol Upgrades In the MAS Management Console, the Video Conferencing Enabled option for the Meet Me conferencing service defaults to a disabled (unchecked) state upon system upgrade Fault Management For more information, see MAS Meet Me Conferencing Fundamentals (NN ) NN Standard 40 8 November 2007

243 Network Engineering 243 MAS Ad Hoc Conferencing Fundamentals (NN ) Operational Measurements Reference (NN ) Logs and Alarms No additional logs and alarms are required for this feature beyond those already supported and implemented by the MAS For more information, see MAS Meet Me Conferencing Fundamentals (NN ) MAS Ad Hoc Conferencing Fundamentals (NN ) Alarm and Log Reference (NN ) Configuration Management This section describes the tasks required to configure video for the Ad Hoc conferencing and Meet Me conferencing services More than one MAS may be pooled for a subdomain, and, in this case, load balancing among the servers is performed to, for example, select the least-utilized server for hosting a MAS conference Because of this, all servers pooled within the same subdomain must be provisioned identically (that is, all provisioned with video for conferencing or all provisioned without video for conferencing) If this is not done, the situation may arise that a subscriber or not have video available based solely on which server within a pool happens to be selected at any given time; the subscriber could have video available one time, but not have it available the next time The availability of video is subject to how the servers in the pool are keyed through their respective license keys That is, if the servers are not keyed to enable video, then video not be available for MAS conferencing, regardless of whether video conferencing is enabled through service package provisioning If video is enabled through the Management Console for each server for conferencing, then all servers pooled for a subdomain must be configured likewise through their respective Management Consoles If the use of video is provisioned for a subdomain, a mix of audio-only and audio/video conferences can be supported (the audio-only conferences are simply audio/video conferences with no video present) However, a subdomain that is not provisioned with video can obviously only host audio conferences Network configuration Network configuration is unchanged; see the individual MAS service documents for more information NN Standard 40 8 November 2007

244 244 Appendix A DivX Multipoint Video conferencing Media Application Server configuration After network configuration is complete, the Media Application Server platform software and the Ad Hoc conferencing service software must be configured using the Media Application Server Console The administrator must configure both system-level configuration and Ad Hoc conferencing service-specific parameters For more information, see the individual MAS service documents To configure the video switching parameter, see "Setting video switching" (page 245) Service configuration Video must be enabled in Meet Me conferencing service packages and for the domain of the Ad Hoc conferencing service For more information, see "Add video to a Meet Me conferencing service package" (page 252) and "Enabling Ad Hoc video conferencing for a domain" (page 253) Accounting Codecs (including video codecs) are already captured as part of the existing Accounting Manager functionality For the entire Nortel service schema, see Accounting Manager Fundamentals(NN ) Performance Management For more information, see the following documents: MAS Meet Me Conferencing Fundamentals(NN ) MAS Ad Hoc Conferencing Fundamentals(NN ) Performance Measurements, Operational Measurements, and Statistics The following table lists the additional operational measurement required for video Table 7 Operational measurements for video OM Type Description NumVideoParties Gauge Number of video-enabled users currently in active conference sessions on the MAS For more information, see MAS Meet Me Conferencing Fundamentals(NN ) MAS Ad Hoc Conferencing Fundamentals(NN ) NN Standard 40 8 November 2007

245 Configuration 245 Security and Administration There are no changes or additions to security and administration with regards to video For more information, see MAS Meet Me Conferencing Fundamentals(NN ) MAS Ad Hoc Conferencing Fundamentals(NN ) Configuration The following list outlines the steps to provision multipoint video as part of the existing Meet Me and Ad Hoc conferencing services: MAS Management Console: "Setting video switching" (page 245) MAS Management Console: "Configuring the Meet Me conferencing service" (page 246) MAS Management Console: "Configure the Ad Hoc conferencing service" (page 248) Setting video switching The Media Application Server (MAS) video switching mechanism tracks the active speaker for a video conference, and employs a specified amount of video switching hysteresis That is, a video-enabled speaker must be deemed to be the active speaker for a specified amount of time before actually gaining the video focus The value for the video switching hysteresis for a conference server can be set through the Video Switching Hysteresis (ms) parameter in milliseconds (ms) Tip: A default value is provided Take care when setting custom values for Video Switching Hysteresis (ms), as incorrect settings can create an unpleasant user experience For example, too small a value can lead to the video switching too often, as the video switching becomes more sensitive to background noise; likewise, too large a value can lead to a noticeable lag in switching to a new active speaker s video Configure Video Switching Hysteresis Procedure 114 Configuring Video Switching Hysteresis Step Action At the MAS Management Console, 1 Select Services > System > Configuration NN Standard 40 8 November 2007

246 246 Appendix A DivX Multipoint Video conferencing 2 Double-click Video Switching Hysteresis (ms) A configuration window appears 3 Enter a Value for video switching hysteresis A restart is required for this setting to take effect 4 Click Ok End Configuring the Meet Me conferencing service In addition to the administrator-level provisioning of video for the Meet Me conferencing service, the use of video for the Meet Me conferencing service must be enabled for each server through the MAS console of that server NN Standard 40 8 November 2007

247 Configuration 247 The MAS console configuration parameter Video Enabled for the Meet Me conferencing service enables video through the MAS console (see figure on the following page) The default value for Video Enabled is NO (disabled) and must be explicitly set to YES (enabled) to enable video for the Meet Me conferencing service Use of this configurable parameter enables an operator to disable video for Meet Me conferencing, overriding any keycoding that enables video for the service, without having to explicitly re-key the MAS to disable video Tip: In order to enable video for the Meet Me conferencing service through the Management Console, the MAS must initially be keycoded to enable video If the MAS is not keycoded to enable video for Meet Me conferencing, then toggling the Video Enabled parameter through the Management Console have no effect That is, video cannot be enabled for Meet Me conferencing through the Management Console if it has not been provisioned through keycoding for the server in question Enable video for Meet Me conferencing Procedure 115 Enabling video for Meet Me conferencing Step Action At the Media Application Server Console 1 Select the Services > MeetMe Conferencing > Configuration icon The Details panel displays all configuration data for the Meet Me conferencing service NN Standard 40 8 November 2007

248 248 Appendix A DivX Multipoint Video conferencing 2 Use the values from following table to configure the video parameter for the Meet Me conferencing service Name of parameter Fields Description Video Enabled (YES/NO) Optionality: Optional Valid Values: YES/NO When enabled, video streaming is enabled during Meet Me conferencing Default: NO End Configure the Ad Hoc conferencing service In addition to the administrator-level keycoding of video for the Ad Hoc conferencing service, the use of video for the Ad Hoc conferencing service can be enabled and disabled on a for each server through the Management Console for that server The Video Enabled parameter for Ad Hoc NN Standard 40 8 November 2007

249 Configuration 249 conferencing enables and disables video through the Management Console The default value for Video Enabled is NO (disabled) and must be set to YES (enabled) to enable video for Ad Hoc conferencing Use of this configurable parameter enables an operator to disable video for Ad Hoc conferencing, overriding any keycoding that enables video for the service, without having to explicitly re-key the MAS to disable video Tip: To enable video for the Ad Hoc conferencing service through the Management Console, the MAS must initially be keycoded to enable video If the MAS is not keycoded to enable video for Ad Hoc conferencing, then toggling the Video Enabled parameter through the Management Console have no effect That is, video cannot be enabled for Ad Hoc conferencing through the Management Console if it was not provisioned through keycoding for the server in question Procedure 116 Configuring the Ad Hoc conferencing service Step Action At the MAS Management Console, 1 From the console tree panel, select the Services > Adhoc Conferencing > Configuration icon The Details panel displays all configuration data for the Ad Hoc Conferencing service NN Standard 40 8 November 2007

250 250 Appendix A DivX Multipoint Video conferencing 2 Use the values from following table to configure the video parameter for the Ad Hoc Conferencing service Name of parameter Fields Description Video Enabled (YES/NO) Optionality: Optional Valid Values: YES, NO When enabled, video streaming is enabled during Ad Hoc conferencing Default: NO End Assign video for the Meet Me conferencing service in a domain Through the Provisioning Client, an administrator must assign the video conferencing service to a domain before video conferencing is available for use in service packages for that domain This is accomplished by enabling (checking) the Video Conferencing Enabled option in the Provisioning Client for the existing Meet Me conferencing service Procedure 117 Assigning video for the Meet Me conferencing service in a domain Step Action At the Provisioning Client, 1 Select Provisioning > Services > Assign Services NN Standard 40 8 November 2007

251 Configuration Ensure that the Meet Me conferencing service is assigned 3 Enable the Video Conferencing Enabled option for the service 4 Click Save End After the video conferencing service option is provisioned for use within a domain, the service can be added to a new or existing service package NN Standard 40 8 November 2007

252 252 Appendix A DivX Multipoint Video conferencing Add video to a Meet Me conferencing service package Assigning video to a Meet Me service package gives the user the ability to create a Meet Me video conference It does not affect the user s ability to join a Meet Me video conference because any user can join a conference without the need of a service package option Create a new service package with video Procedure 118 Creating a new service package with video Step Action At the Provisioning Client 1 Select Domains > "Domain Name" > Service Package > Create Package from the Provisioning Client main page NN Standard 40 8 November 2007

253 User Guide Select Meet me Conferencing 3 Select the Video Conferencing Enabled option for the service 4 Click Save End Procedure 119 Adding video to an existing service package Step Action 1 Go to Provisioning > Domains > "Domain Name" > Service Package > List Packages 2 Select the service package to be modified and click Details > Modify 3 Ensure that the Meet Me conferencing service is enabled 4 Select the Video Conferencing Enabled option for the service 5 Click Save End Enabling Ad Hoc video conferencing for a domain The service package provisioning changes described in the previous sections apply only to the Meet Me conferencing service Video for Ad Hoc conferencing is provisioned differently owing to the different ways in which Meet Me and Ad Hoc conferencing manage subscriber data Video for Ad Hoc conferencing is enabled for a subdomain based solely on how the servers within the subdomain are keyed If video is enabled for the servers through their respective license keys, then video is enabled for all Ad Hoc conferences hosted on the servers; similarly, if video is not enabled for the servers, then video not be available for any Ad Hoc conferences User Guide You must have the following in order to send or receive video during conferences: either Meet Me conferencing or Ad Hoc conferencing services with video enabled in your service package a Multimedia PC Client or Multimedia Web Client NN Standard 40 8 November 2007

254 254 Appendix A DivX Multipoint Video conferencing Preferences > Video parameters set to send, or receive only For information about setting video parameters, see Multimedia PC Client User Guide (NN ) NN Standard 40 8 November 2007

255 Appendix B BCP Installation on the IBM BladeCenter T Platform 255 This appendix describes the installation of a Border Control Point on the IBM BladeCenter T Platform The appendix is organized as follows: "Configuration information" (page 256) "Installing the BCP software" (page 256) The RTP Media Portal on the IBM BladeCenter T (BCT) platform provides significant capacity and robustness Each of the eight BladeServers in the chassis is an individual Border Control Point (BCP) Each BCP can be used independently or they can be grouped into an N+1 cluster In a cluster, one of the BladeServers acts as a hot standby and take over if one of the remaining N BladeServers fails You must complete the installation and configuration process for each BladeServer in the chassis Installation and configuration on the BCT platform involves the following steps: assembly of the hardware configuration of the BladeServer BIOS installation of the software on the BladeServer Installing the RTP Portal software requires only a single disc The complete base system can be installed in approximately 15 minutes or less NN Standard 40 8 November 2007

256 256 Appendix B BCP Installation on the IBM BladeCenter T Platform Configuration information CAUTION Install only Nortel-certified software on the IBM BladeCenter T Do not install software updates obtained directly from IBM Successful configuration of the BCP depends on the accurate capture of configuration information Before installation, collect the information that is required for provisioning the BCP Complete the following table before you proceed Table 8 Information required for installation and commissioning on the BCT platform 1 Border Control Point Configuration Information Slot Attribute Example Value Host card network address (Portal address) Host card netmask Host card default gateway Host card IP failover active Hostname Timezone YES RTP_04 US/Central Timeserver IP address If you configure all eight BCPs on the BCT, you replicate this table seven times, keeping a record of eight individual slots (one for each BCP, and each with its own set of attributes) Other required information The following information is required to fully configure a BCP: a root password for the host a password for the Nortel user a password for the sysadmin user Installing the BCP software Installing the BCP from a CD is a simple process The machine is booted from CD, the information in the table is requested by the installation software, and then the software is copied to the hard drive and the machine is configured NN Standard 40 8 November 2007