Nortel Unified Communications Campus Solution Configuration Unified Communications. Release: 1.0 Document Revision:

Transcription

1 Configuration Unified Communications Release: 1.0 Document Revision: NN

2 Release: 1.0 Publication: NN Document release date: Copyright 2009 Nortel All Rights Reserved. Networks Printed in Canada and the United States of America LEGAL NOTICE While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice. Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks. All other trademarks are the property of their respective owners.

3 . Contents 3 New in this release 7 Introduction 9 Nortel Professional Services 10 Unified Communications configuration prerequisites 13 Unified Communications configuration procedures 13 Nortel Best Practices for Unified Communications 15 Required Best Practices 15 Recommended Best Practices 16 CS 1000 system configuration 17 CS 1000 configuration prerequisites 18 CS 1000 configuration procedures 19 Configuring a new ELAN ID and VAS ID 22 Enabling the ELAN connection to the switch 23 Provisioning a telephone for Converged Office 24 Provisioning a TLSV to associate with the telephone 25 Saving the configuration 26 Configuring routes and trunks 27 Configuring a route list index 30 Configuring a distant steering code 31 Configuring a SIP gateway 32 Configuring the SIP URI map 33 Configuring SIP CTI services 35 Configuring Signaling Server properties for SIP 37 Creating the service domain in NRS 38 Creating the L1 (UDP) domain in NRS 39 Creating the L0 (CDP) domain in NRS 40 Configuring endpoints on the NRS 41 Configuring routing entries on the NRS 42 Cutting over and committing changes on the NRS database 43 NAS system configuration 45 NAS configuration prerequisites 47

4 4 NAS configuration procedures 48 Configuring NAS VLAN 2 51 Configuring NAS uplink ports 52 Disabling NAS STP 53 Configuring the NAS layer 3 Gateway interfaces 54 Configuring OCS 2007 real server IP addresses 55 Configuring the new group and adding real servers 56 Configuring a NAS virtual IP address 57 Adding additional services to the virtual group 58 Configuring NAS SLB ports for client and server processing 59 Enabling NAS SLB service 60 Applying and saving configuration changes 61 Verifying services 62 OCS 2007 system configuration 65 OCS 2007 configuration prerequisites 67 OCS 2007 configuration procedures 69 Preparing the Active Directory 70 Preparing the back-end database 73 Configuring OCS 2007 on the front-end servers 76 Configuring and assigning server certificates to the OCS 2007 servers 78 Assigning server certificates to the Web component on the OCS 2007 servers 81 Verifying replication 82 Starting OCS 2007 services 83 OCS 2007 services configuration procedures 84 Starting the OCS 2007 server 87 Configuring routes on the OCS 2007 front-end servers 88 Creating a location profile 90 Creating phone usages, policies, and routes 91 Installing the Mediation Server 93 Configuring a Mediation Server certificate 95 Configuring the Mediation Server 98 Starting the Mediation Server 100 Installing the proxy server 101 Activating the proxy server 102 Configuring the server certificate for the proxy server 103 Configuring the proxy server 105 Installing the Multimedia Convergence Manager (MCM) 107 Configuring permissions for the MCM 109 Configuring the MCM 110 Configuring Active Directory and Office Communicator 113 Active Directory and Office Communicator configuration procedures 114 Configuring Active Directory user accounts 117

5 5 Configuring the Active Directory user server 118 Installing Office Communicator 119 Configuring the OCC 2007 calling device 120

6 6

7 . New in this release 7 This is the first issue of this document, Nortel Unified Communications Campus Solution (NN ). Because this is the first issue, all features described in this document are new.

8 8 New in this release

9 . Introduction 9 Unified Communications (UC) is not a specific technology. It is an application foundation that integrates all your communication devices into a single uniform interface. This foundation enhances your individual, workgroup, and organizational productivity. UC enables you to run your business in a new way where communications are tightly coordinated with business processes. UC integrates the voice infrastructure into data applications. Now, all forms of communications are integrated including fixed and mobile voice, , instant messaging, IP-PBX, VoIP, presence, voice mail, fax, and video conferencing. By integrating all of these systems, UC enables you to reach the right person at the right time by using the right device. The UC Campus solution uses the following best-in-class components from Microsoft and Nortel: Communication Server 1000 This Communication Server 1000 implementation includes the Media Gateway and Signaling Server. Microsoft Office Communications Server 2007 (OCS 2007) Enterprise Edition This OCS 2007 implementation includes the Mediation Server and the Office Communicator 2007 (OC 2007). With Nortel Converged Office, users can access Nortel Communication Server 1000 telephony services, and send and receive calls over Communication Server Nortel Multimedia Convergence Manager (MCM) installed on an OCS 2007 Proxy Server This component provides interoperability between the OCS 2007 and the Communication Server In the UC Campus environment, the MCM software is located between the Mediation Server and Communication Server MCM has two main components: MCM Service, which handles call processing, and MCM Management Console, which interfaces with the MCM Service for configuration, administration, and maintenance. The MCM call processing service handles SIP telephony traffic between CS 1000 and OCS 2007.

10 10 Introduction ATTENTION UC Campus uses MCM and Converged Office as a gateway between Communication Server 1000 and OCS This configuration enables you to use all of the Nortel Converged Office services. In the UC Campus Solution, the Nortel Communication Server 1000 provides enterprise-class Voice over IP services and the Microsoft Office Communications Server (OCS) 2007 provides Unified Communications services including presence and instant messaging. With integration services provided by MCM, the CS 1000 and OCS 2007 work together to provide a complete unified communications system. The following figure illustrates the basic high-level architecture of the Unified Communications infrastructure. This document describes how to integrate the various elements, including the deployment of the Nortel Application Switch to load-balance traffic to multiple OCS Proxy/MCMs and to multiple OCS Front Ends. With this configuration a highly resilient implementation is achieved, with no single point of failure in the SIP signalling path. Figure 1 Unified Communications architecture Nortel Professional Services Nortel Global Services offers solutions that combine comprehensive network expertise, world class partners and global reach. For the UC Campus Solution, Nortel Global Services provides a complete range of services for the products described in the rest of this document. For further

11 Nortel Professional Services 11 details on services to complement the design, deployment and support of a UC Campus Solution, see Nortel Unified Communications Campus Solution Fundamentals (NN ).

12 12 Introduction

13 . Unified Communications configuration prerequisites 13 You have basic programming and provisioning skills for the Communication Server Nortel recommends that you complete product-specific training before you begin the systems integration. A complete list of courses is available at You are skilled in Microsoft Active Directory, Domain Name Service, and DHCP services. You performed a network health check in the planning phase of the integration to ensure appropriate network bandwidth and to identify the protocols, payload size, and codecs to use. You established a system baseline so that the Communication Server 1000 and OCS 2007 systems are configured and working in a stand-alone environment. Unified Communications configuration procedures This work flow shows the sequence of tasks you need to perform to integrate the Unified Communications components. To link to any procedure, go to Unified Communications configuration navigation (page 14).

14 14 Unified Communications configuration prerequisites Figure 2 CS 1000/OCS 2007 integration tasks Unified Communications configuration navigation CS 1000 system configuration (page 17) NAS system configuration (page 45) OCS 2007 system configuration (page 65) Starting OCS 2007 services (page 83) Configuring Active Directory and Office Communicator (page 113)

15 . Nortel Best Practices for Unified Communications 15 Nortel developed Best Practices for the UC Campus Solution after extensive testing in the lab and implementing many networks in the field. When implemented properly, these Best Practices ensure that your network will be stable and reliable. The two types of Best Practices are: required recommended Required Best Practices reflect the UC Campus architecture and match the Nortel prevalidated configuration. Recommended Best Practices are Nortel suggestions based on years of experience. In most implementations, these Best Practices improve network reliability and performance. However, Nortel recognizes that they may not be relevant for all networks so they are not required. For additional planning and Best Practices information, obtain the following publication from the Nortel Technical Support Portal site ( Load Balancing Microsoft Office Communication Server 2007 in a Consolidated Topology with Application Switch Technical Configuration Guide (NN ) Required Best Practices You must implement these Best Practices to be eligible for UC Campus Solution support services. Do not deploy one armed mode configurations on the NAS. Use PIP on server ports. Use Layer 3 on the NAS to separate the Client side from the Server side. Use Direct Access mode.

16 16 Nortel Best Practices for Unified Communications Use session mirroring for SIP & TLS. Enable both client and server processing on all server ports. Use VRRP with tracking on all Layer 4 ports. Recommended Best Practices Nortel recommends these Best Practices as suggestions to improve your network. They are not a required part of the UC Campus Solution. Use GBIC ports for uplinks. When the server is directly connected to the NAS, configure teaming in hot standby mode and use the preferred link connecting to the Master VRRP NAS. When the server is directly connected to the Horizontal Stack Switch Cluster, configure teaming in load balancing mode. Enable DOS attack protection on client-side ports. Add SIP and TLS services to separate groups. This allows faster failover for individual services. Use Microsoft Clustering for high availability on a SQL Server. Dedicate a SQL server for each pool, with one SQL instance per SQL server.

17 . CS 1000 system configuration 17 This chapter describes how to integrate the Communication Server 1000 system with Microsoft Office Communications Server 2007 (OCS 2007) Enterprise Edition services. For more information about the Communication Server 1000 and the UC Campus voice applications, see Configuration Voice Services (NN ) The basic architecture for the UC Campus voice services includes the following components: Communication Server 1000E in High Availability mode IP Phone sets

18 18 CS 1000 system configuration CS 1000 configuration prerequisites Integrate OCS 2007 with Communication Server 1000 when both systems are installed and a baseline of operation is achieved and tested. The Communication Server 1000 system has adequate licenses for the number of required SIP ports. Converged Office includes the licenses for TLSV, SIP CTI TR87, and AST. The Communication Server 1000 Call Server is configured. The Communication Server 1000 dialing plan is configured and working. A Communication Server 1000 D-channel is configured and working. A Communication Server 1000 Signaling Server node is installed and working. Network Routing Service (NRS) is enabled. NRS can be either SIP Proxy Server (SPS) or SIP Redirect Server (SRS). You have Enterprise Common Manager (ECM) logon access with administrator privileges.

19 CS 1000 configuration procedures Recommended Best Practices 19 This task flow shows the sequence of tasks you need to perform to integrate the Communication Server 1000 system with OCS To link to any procedure, go to CS 1000 configuration navigation (page 20). Figure 3 CS 1000/OCS 2007 integration procedues

20 20 CS 1000 system configuration Figure 4 CS 1000/OCS 2007 integration procedures (cont.) CS 1000 configuration navigation Configuring a new ELAN ID and VAS ID (page 22) Enabling the ELAN connection to the switch (page 23) Provisioning a telephone for Converged Office (page 24) Provisioning a TLSV to associate with the telephone (page 25)

21 CS 1000 configuration navigation 21 Saving the configuration (page 26) Configuring routes and trunks (page 27) Configuring a route list index (page 30) Configuring a distant steering code (page 31) Configuring a SIP gateway (page 32) Configuring the SIP URI map (page 33) Configuring SIP CTI services (page 35) Configuring Signaling Server properties for SIP (page 37) Creating the service domain in NRS (page 38) Creating the L1 (UDP) domain in NRS (page 39) Creating the L0 (CDP) domain in NRS (page 40) Configuring endpoints on the NRS (page 41) Configuring routing entries on the NRS (page 42) Cutting over and committing changes on the NRS database (page 43)

22 22 CS 1000 system configuration Configuring a new ELAN ID and VAS ID Procedure steps Define and configure the ELAN ID for the AML link and the associated VAS ID in the configuration record. Perform this procedure only if an ELAN ID and VAS ID are not available. Step Action 1 Connect to the Call Server. 2 Enter LD For prompts not specifically mentioned in the following steps, press Enter to accept the default. 4 After the REQ prompt, enter CHG. 5 After the TYPE prompt, enter ADAN. 6 After the ADAN prompt, enter NEW ELAN xx. The xx is the next available number from 32 to After the CTYP prompt, enter ELAN. 8 After the DES prompt, enter a relevant description such as ELAN1.. 9 After the REQ prompt, enter CHG. 10 After the TYPE prompt, enter VAS. 11 After the VAS prompt, enter NEW. 12 After the VSID prompt, enter the number entered for the ELAN ID. 13 After the ELAN prompt, enter the number entered for the ELAN ID. 14 After the SECU prompt, enter YES. 15 To exit the overlay, enter ****. 16 To view the new ELAN, enter LD At the REQ prompt, enter PRT and then ADAN. A list of all provisioned IDs appears. 18 To save a text file of the output, use the capture text function in hyperterminal. --End--

23 Enabling the ELAN connection to the switch Procedure steps 23 Procedure steps Perform this procedure to enable the LD 48 ELAN connection to the switch. Step Action 1 Connect to the Call Server. 2 Enter LD Enter ENL ELAN to enable the ELAN. 4 To exit the overlay, enter ****. 5 To view the status of the ELAN, enter STAT ELAN. --End--

24 24 CS 1000 system configuration Provisioning a telephone for Converged Office Procedure steps Provision the user telephone. You must do this before you provision Telephony Services (TLSV) so that you can associate the telephone with the TLSV. Step Action 1 Connect to the Call Server. 2 Enter LD For prompts not specifically mentioned in the following steps, press Enter to accept the default. 4 After the REQ prompt, enter NEW to create a new telephone entry. 5 After the TYPE prompt, enter the type of phone such as After the TN prompt, enter the terminal number in the format of aaa. bbb.ccc.ddd (<loop>.<shelf>.<card slot>.<card channel>). 7 After the DES prompt, enter a relevant description for the telephone entry. 8 After the CUST prompt, enter a number for this customer. 9 After the ZONE prompt, enter a number for this zone. 10 After the CLS prompt, enter CDMR T87A. ATTENTION Do not configure CLS as CDMV or CDMO. They cause the users to be treated as MCS users. 11 After the AST prompt, enter the SCR key location, which is usually the primary location of After the KEY prompt, enter 0 SCR <xxxx> and the line number of the telephone. 13 To exit the overlay, enter ****. --End--

25 Procedure steps 25 Provisioning a TLSV to associate with the telephone Prerequisite Provision a TLSV with the same DN as a user in a Multiple Appearance Directory Number (MADN) arrangement. This offers incoming voice calls to the user s DN on their Microsoft Office Communicator Client 2007 (OCC 2007) as well as any telephones configured with the same DN. Provision the user s telephone so that you can associate it with TLSV. Procedure steps Step Action 1 Connect to the Call Server. 2 Enter LD For prompts not specifically mentioned in the following steps, press Enter to accept the default. 4 After the REQ prompt, enter NEW to create a new telephone entry. 5 After the TYPE prompt, enter TLSV. 6 After the TN prompt, enter the terminal number in the format of aaa. bbb.ccc.ddd (<loop>.<shelf>.<card slot>.<card channel>). 7 After the DES prompt, enter a relevant description for the telephone entry. 8 After the CUST prompt, enter a number for this customer. 9 After the ZONE prompt, enter a number for this zone. 10 After the CLS prompt, enter T87D TLSVM. ATTENTION Do not configure CLS as CDMV or CDMO. They cause the users to be treated as MCS users. 11 After the KEY prompt, enter 0 SCR <xxxx> and the line number of the telephone. 12 After the KEY prompt, enter 1 HOT p <x> <yyyy> and the distant steering code. 13 To exit the overlay, enter ****. --End--

26 26 CS 1000 system configuration Saving the configuration Procedure steps Perform this procedure to save your configuration changes. Step Action 1 Connect to the Call Server. 2 Enter LD Enter EDD. 4 To exit the overlay, enter ****. --End--

27 Procedure steps 27 Configuring routes and trunks Procedure steps Perform this procedure to configure routes and trunks for SIP channels on the Communication Server 1000 system. If you use an existing configuration, perform these procedures to confirm the settings required for OCS Step Action 1 In Enterprise Common Manager (ECM), expand the Routes and Trunks heading. 2 Select Routes and Trunks. 3 Select Add route for the customer number you want to use. 4 Configure the parameters for the route. 5 Click Submit. 6 On the newly created route, click Add trunk. The Trunk Property Configuration page appears. 7 Configure the trunk parameters. 8 Click Save. --End-- Route configuration variable definitions Use the data in the following table to configure the route configuration properties. Variable Route Number (ROUT) Designator field for trunk (DES) Trunk Type (TKTP) Incoming and Outgoing trunk (ICOG) Access Code for the trunk route (ACOD) The route is for a virtual trunk route (VTRK) Zone for codec selection and bandwidth management (ZONE) Value Type the next available route number. Example: 5 Type a relevant description. Example: SIP TIE Incoming and outgoing (IOA) Type a relevant access code for your system. Example: 7905 Enable Type a relevant zone for your system. Example: 2

28 28 CS 1000 system configuration Variable Node ID of signaling server of this route (NODE) Protocol ID for the route (PCID) Integrated Services Digital Network option (ISDN) Mode of operation (MODE) D channel number (DCH) Interface type for route (IFC) Private Network Identifier (PNI) Network Calling Name Allowed (NCNA) Network Call Redirection (NCRD) Trunk Route Optimization (TRO) Channel Type (CHTY) Call Type for outgoing direct dialed TIE route (CTYP) SIGO Value Type the node number for your system. Example: 5 SIP Enable Route uses ISDN Signaling Link (ISLD) Type the channel configured for your system. Example: 1 Meridian 1 SL1 Type the identifier for your system. Enable Enable Enable B-Channel (BCH) Select your dialing plan. Example: CDP or UDP ESN5 Trunk configuration variable definitions Use the data in the following table to configure the trunk configuration properties. Variable Multiple trunk input number (MTINPUT) Trunk data block (TYPE) Terminal Number (TN) Designator field for trunk (DES) Route number, Member number (RTMB) Card Density (CDEN) Value Select the number of trunks to add. This creates a number of TN trunks. Ensure that you have enough unused TNs in a span to cover this number of trunks. IPTI Enter a valid TN, in the format (L)oop (S)helf (C)ard (U)nit. This is the starting TN for multiple trunk input. Example: Type a relevant description for the TNs. Type the route number and trunk start. The route number is the one in which you are creating the TN. The member number is the trunk you create. Example: 5 1 Select the card density type. Example: 8D

29 Procedure steps 29 Variable Start arrangement Incoming (STRI) Start arrangement Outgoing (STRO) Trunk Group Access Restriction (TGAR) Channel ID for this trunk (CHID) Increase or decrease the member numbers (INC) Value Select Wink or Fast Flah (WNK). Select Wink or Fast Flah (WNK). Type the number for your system. Example: 1 Type a relevant ID for the trunk. Example: 2222 If you select Increase Channel and Member number (yes), several TNs are created depending on the values of the MTINPUT and TN parameters.

30 30 CS 1000 system configuration Configuring a route list index Procedure steps Perform this procedure to configure a route list index (RLI) for your SIP channels. This coordinates with the route configured above. If you use an existing RLI, perform this procedure to verify the data. Step Action 1 In ECM, expand the Dialing and number plans heading. 2 Select Electronic Switched Network. 3 Expand Network Control and Services. 4 Select Route List Block. RLI is the unit within a route list block. 5 In Please enter route list index, enter a new valid RLB number. 6 Click outside the Please enter route list index box to activate the Add button, and then click Add. 7 For ROUT, select the route that you previously created. 8 Click Submit. --End--

31 Procedure steps 31 Configuring a distant steering code Procedure steps Perform this procedure to configure a new Distant Steering Code (DSC). The DSC coordinates with the RLI configured above. Step Action 1 In ECM, select Dialing and number plans, Electronic Switched Network. 2 Select Coordinated Dialing Plan (CDP), Distant Steering Code (DSC). 3 Select Add to add a new DSC. 4 For Please enter a distant steering code, type a new DSC (for example, 5505). 5 In the Flexible Length field, enter the number of digits (from 0 to 10) that the system expects to receive before accessing a trunk and outpulsing these digits. 6 In the DSP field, select the Directory Number (DN) to use for CLID. 7 In the Route List field, select the RLI number created. 8 Click Submit. --End--

32 32 CS 1000 system configuration Configuring a SIP gateway Procedure steps Perform this procedure to configure your SIP gateway settings. For more information, see IP Peer Networking Installation and Commissioning (NN ) Step Action 1 In ECM, select System, IP Network. 2 Select Nodes: Server, Media Cards. 3 In the Node configuration area, click Edit for the node you wish to modify. 4 Expand the SIP GW Settings heading. 5 In the Primary Proxy or Redirect (TLAN) IP address field, type the IP address of your proxy or redirect server. 6 In the Port field, type the SIP port number (usually 5060 by default). 7 In the Supports Registration field, select Enable. 8 In the Primary Proxy or Redirect server flag field, select Enable. 9 In the Transport Protocol field, select TCP. 10 Configure the SIP Gateway settings for your secondary proxy or redirect server, if applicable. --End--

33 Procedure steps 33 Configuring the SIP URI map Perform this procedure to configure the SIP Uniform Resource Identifier (URI) map. For more information, see IP Peer Networking Installation and Commissioning (NN ) ATTENTION Configure the SIP URI map based on the network engineered dial plan values that is unique to your network. Procedure steps Step Action 1 Expand the SIP URI Map heading. 2 Configure the SIP URI parameters. 3 Configure the SIP URI map settings for your secondary proxy or redirect server, if applicable. --End-- Variable definitions Use the data in the following table to set the SIP URI properties. Variable Public E.164/National domain name Public E.164/Subscriber domain name Public E.164/Unknown domain name Public E.164/Special Number domain name Private/UDP domain name Value Type the public E.164/National domain for your system. Example: +1 Type the Public E.164/Subscriber domain name for your system. Example: Type the Public E.164/Unknown domain name for your system. Example: PublicUnknown. This parameter is optional. Type the Public E.164/Special Number domain name for your system. Example: PublicSpecial. This parameter is optional. Type the Private/UDP domain name for your system. Example: UDP

34 34 CS 1000 system configuration Variable Private/CDP domain name Private/Special Number domain name Private/Unknown (vacant number routing) domain name Unknown/Unknown domain name Value Type the Private/CDP domain name for your system, including the DP domain name. Example: CDP.UDP Type the Private/Special Number domain name for your system. Example: PrivateSpecial This parameter is optional. Type the Private/Unknown domain name for your system. Example: PrivateUnknown This parameter is optional. Type the Unknown/Unknown domain name for your system. Example: UnknownUnknown This parameter is optional.

35 Procedure steps 35 Configuring SIP CTI services Perform this procedure to configure the SIP Computer Telephony Integration (CTI) services. For more information, see IP Peer Networking Installation and Commissioning (NN ) ATTENTION The SIP CTI services must match the values that you defined in the SIP URI map. Procedure steps Step Action 1 Expand the SIP CTI Services heading. 2 Configure the SIP CTI services parameters according to the following variable definitions table. 3 Configure the SIP CTI services settings for your secondary proxy or redirect server, if applicable. --End-- Variable definitions Use the data in the following table to set the SIP CTI services properties. Variable Service Enabled Value Enable Support TLS Enpoints Only Customer Number You must reboot the Signaling Server for the enabling of SIP CTI to take effect. A system reboot takes the Signaling Server out of service. Reboot during a time that will not impact service. Disable Type the number used for the customer. Example: 0 Maximum Associations per DN Select a number from 1 to 10. Place International Calls Within This Country As National Calls National Prefix International Prefix Location Code Call Prefix Special Number Prefix Enable if applicable. Enter number according to your dialing plan. Enter number according to your dialing plan. Enter number according to your dialing plan. Enter number according to your dialing plan.

36 36 CS 1000 system configuration Variable Subscriber Prefix Dialing Plan Calling Device URI format Home Location Code Country Code (CCC) Area Code (Area Code) #Digits to Strip and Prefix to Insert Value Enter number according to your dialing plan. Select the dialing plan for your engineered system. Example: CDP Select phone-context=<sip URI Map Entries> Enter number according to your dialing plan. Enter number according to your dialing plan. Enter number according to your dialing plan. Enter number according to your dialing plan.

37 Procedure steps 37 Configuring Signaling Server properties for SIP Procedure steps Perform this procedure to configure the SIP signaling server properties. For more information, see IP Peer Networking Installation and Commissioning (NN ) Step Action 1 Expand the Signaling Servers, Signaling Server [your Signaling Server IP] Properties heading. 2 Configure the SIP Signaling Server. 3 Click Save and Transfer. 4 Click OK. --End-- Variable definitions Use the data in the following table to set the SIP Signaling Server properties. Variable Enable IP Peer Gateway (Virtual Trunk TPS) Enable SIP proxy/redirect Server Local SIP TCP/UDP port to listen to SIP Domain name SIP Gateway Endpoint Name SIP Gateway Authentication Password Enable Gatekeeper Network Service Role Value Select H.323 and SIP. Selecting both H.323 and SIP allows for a dual network and takes H.323 into consideration, if you use devices requiring that protocol. Enable only if you use co-resident NRS. Type the default SIP port number (usually 5060). Ensure that this value coordinates with your end devices. Type the SIP domain name to be used throughout the system configuration. Example: convergedoffice.com Type the Gateway endpoint name to be registered in the NRS. If you enable security and use authentication in the NRS when you create endpoints, this password is used for authentication. Enable Issue only if you use co-resident NRS. Options are Primary, Alternate, and Failsafe.

38 38 CS 1000 system configuration Creating the service domain in NRS Procedure steps Perform this procedure to create a SIP service domain on a Network Routing Server (NRS) if one is not already created. On redundant NRS systems, perform all configurations on the primary NRS. Step Action 1 In ECM, select NRS Manager. 2 Select and expand Numbering Plans. 3 In the right pane, click Standby database to switch from active to standby database view. 4 In the left pane, click Domains. 5 In the right pane, click Add. The View Service Domain Property page appears. 6 For Domain name, enter the SIP domain name that you previously configured. 7 For Domain description, enter a relevant description for the domain being used. 8 Click Save. --End--

39 Procedure steps 39 Creating the L1 (UDP) domain in NRS Procedure steps Perform this procedure to create an L1 Uniform Dialing Plan (UDP) service domain, if one is not already created. On redundant NRS systems, perform all configuration on the primary NRS. Configure the NRS L1 domain using the same parameters that you provisioned in the SIP URI Map. Some parameters are optional for your system. For a system with full Basic Automatic Route Selection/Network Automatic Route Selection (BARS/NARS) or a UDP dialing plan, you must configure the applicable parameters for your engineered dialing plan. Step Action 1 In the right pane, select L1 Domains (UDP) (1). 2 Click Add. 3 For Domain name, type a relevant domain name (for example, UDP). 4 For Domain description, enter a relevant description for the domain used. 5 For E.164 country code, enter the E.164 country code for your system. 6 For E.164 area code, enter the E.164 area code for your system. 7 Configure other optional parameters as required for your system. 8 Click Save. --End--

40 40 CS 1000 system configuration Creating the L0 (CDP) domain in NRS Procedure steps Perform this procedure to create an L0 Coordinated Dialing Plan (CDP) service domain, if one is not already created. On redundant NRS systems, perform all configuration on the primary NRS. Configure the NRS 01 domain using the same parameters that you provisioned in the SIP URI Map. Some parameters are optional for your system. For a system with full BARS/NARS or a UDP dialing plan, you must configure the applicable parameters for your engineered dialing plan. Step Action 1 In the right pane, select L0 Domains (CDP) (1). 2 Click Add. 3 For Domain name, type a relevant domain name (for example, CDP). 4 For Domain description, enter a relevant description for the domain used. 5 For E.164 country code, enter the E.164 country code for your system. 6 For E.164 area code, enter the E.164 area code for your system. 7 Configure other optional parameters as required for your system. 8 Click Save. --End--

41 Procedure steps 41 Configuring endpoints on the NRS Perform this procedure to configure the MCM Gateway endpoints on the Network Routing Service (NRS). You must perform this procedure for each MCM node on the system. On NRS redundant systems, perform all configuration on the primary NRS. ATTENTION UC Campus Solution uses the Multimedia Convergence Manager (MCM) and Converged Office as a gateway between Communication Server 1000 and OCS This configuration enables you to use all of the Nortel Converged Office services. However, UC Campus also supports using the Communication Server 1000 as a direct PSTN gateway to OCS 2007 without MCM and Converged Office. This procedure is required only if you use MCM. Procedure steps Step Action 1 In the right pane, click Endpoints. 2 Ensure that you select the correct Service domain, L1 domain, and L0 domain. 3 Click Add. 4 For Endpoint name, type a relevant endpoint name (for example, convergedoffice_ocs). 5 For Endpoint description, type a relevant endpoint description. 6 For Endpoint authentication, select Authentication off. 7 For Static endpoint address type, select IP version 4. 8 For H.323 support, select H.323 not supported for the MCM gateway endpoints. 9 For SIP support, select Dynamic SIP endpoint. 10 For SIP transport, enable the transport protocol type for TCP. 11 Type a value for the SIP TCP port Click Save. --End--

42 42 CS 1000 system configuration Configuring routing entries on the NRS Perform this procedure to add a routing entry for each MCM gateway endpoint. The Signaling Server endpoint is already configured according to your dial plan. On NRS redundant systems, perform all configuration on the primary NRS. ATTENTION UC Campus Solution uses the Multimedia Convergence Manager (MCM) and Converged Office as a gateway between Communication Server 1000 and OCS This configuration enables you to use all of the Nortel Converged Office services. However, UC Campus also supports using the Communication Server 1000 as a direct PSTN gateway to OCS 2007 without MCM and Converged Office. This procedure is required only if you use MCM. Procedure steps Step Action 1 In the right pane, click Routes. 2 Ensure that the correct Service domain, L1 domain, and L0 domain are selected. 3 Select the Endpoint for which you want to add a route, and click Add. 4 Select the DN Type. 5 Type the DN prefix. The DN prefix is the DSC that you created in the Configuring a Distant Steering Code procedure. The DN prefix can be up to 30 characters in length and can include the characters 0 to 9, #, -,?. The first character of the DN prefix must be numeric (for example, 4100). Use the same DN prefix for each end point. 6 Enter the Route cost. The default route cost is 1. The lower the number, the lower the cost of using the route. Configure the route cost based on the engineered dial plan for your network. 7 Click Save. --End--

43 Procedure steps 43 Cutting over and committing changes on the NRS database Procedure steps Perform this procedure to switch between the active and standby database access pointers. This swaps the primary and standby databases so that configuration changes take effect. Step Action 1 In NRS Manager, expand System. 2 Select Database. 3 Click Cut Over. 4 Click Commit. --End--

44 44 CS 1000 system configuration

45 . NAS system configuration 45 The UC Campus Solution uses the Nortel Application Switch (NAS) to provide security, resiliency, and load balancing. This chapter describes the NAS role as a load balancer. For load balancing, a pair of NAS devices in Active Standby mode with an Inter-Switch Link (ISL) between them load balance the OCS 2007 front-end servers. Network Load Balancing uses a distributed algorithm to load balance TCP/IP network traffic across a number of hosts, enhancing the scalability and availability of mission critical, IP-based services, such as Web, VPN, Streaming Media, and Firewalls. Network Load Balancing also provides high availability by detecting host failures and automatically redistributing traffic to remaining operational hosts. The following figure shows the relationship of the two load-balancing NAS devices relative to the other elements in the UC Campus Data Center.

46 46 NAS system configuration Figure 5 UC Campus Data Center showing NAS

47 Procedure steps 47 NAS configuration prerequisites Integrate OCS 2007 with Communication Server 1000 when both systems are installed and a baseline of operation is achieved and tested. Install NAS. Connect and configure a management Ethernet port. Reserve three IP addresses per VLAN for assignment to the High Available NAS pair. Reserve one IP address to assign a virtual IP address for the OCS 2007 pool. An entry is required in the DNS server to resolve the OCS 2007 pool host name to this IP address.

48 48 NAS system configuration NAS configuration procedures This task flow shows the sequence of tasks you need to perform to configure NAS. To link to any procedure, go to NAS configuration navigation (page 50).

49 Procedure steps 49 Figure 6 NAS configuration procedures

50 50 NAS system configuration NAS configuration navigation Configuring NAS VLAN 2 (page 51) Configuring NAS uplink ports (page 52) Disabling NAS STP (page 53) Configuring the NAS layer 3 Gateway interfaces (page 54) Configuring OCS 2007 real server IP addresses (page 55) Configuring the new group and adding real servers (page 56) Configuring a NAS virtual IP address (page 57) Adding additional services to the virtual group (page 58) Configuring NAS SLB ports for client and server processing (page 59) Enabling NAS SLB service (page 60) Applying and saving configuration changes (page 61) Verifying services (page 62)

51 Procedure steps 51 Configuring NAS VLAN 2 Procedure steps Perform this procedure to create a new VLAN named VLAN 2. Step Action 1 Configure the server VLAN by entering the following command: /config/l2/vlan 2/ena/name "<vlan name>"/def <ports used for front ends, multiple ports use spaces> 2 When prompted to confirm changing the PVID for VLAN ports, enter y. --End--

52 52 NAS system configuration Configuring NAS uplink ports Procedure steps Perform this procedure to configure the uplink ports. Step Action 1 Configure the uplink ports by entering the following command: /config/l2/trunk 1/add <uplink port #1>/add <uplink port #2>/ena --End--

53 Procedure steps 53 Disabling NAS STP Procedure steps Perform this procedure to disable Spanning Tree Protocol (STP) on the NAS. Step Action 1 Disable STP by entering the following command: /config/l2/stg 1/off --End--

54 54 NAS system configuration Configuring the NAS layer 3 Gateway interfaces Procedure steps Perform this procedure to create Gateways for VLAN 1 and VLAN 2. Step Action 1 Configure the layer 3 interface for VLAN 1 by entering the following command: /config/l3/if 1/add <layer 3 ip for vlan 1>/mask <subnet mask>/vlan 1/en 2 Configure the layer 3 interface for VLAN 2. /config/l3/if 2/add <layer 3 IP for vlan 2>/mask <subnet mask>/vlan 2/en/apply --End--

55 Procedure steps 55 Configuring OCS 2007 real server IP addresses Procedure steps Perform this procedure to configure real OCS 2007 server IP addresses. Step Action 1 Configure the IP address for the first OCS 2007 front-end server by entering the following command: /config/slb/real 1/rip <real ip of ocs frontend server #1>/ena/name <relevant description for entry> /tmout 30 2 Configure the IP address for the second OCS 2007 front-end server. /config/slb/real 2/rip <real ip of ocs frontend server #2>/ena/name <relevant description for entry> /tmout 30 --End--

56 56 NAS system configuration Configuring the new group and adding real servers Procedure steps Perform this procedure to create a new group and assign the real OCS 2007 servers to the group. Step Action 1 Configure the group by entering the following command: /config/slb/group 1/ipver v4/add 1/add 2/name "<relevant name for virtual group>"/metric leastconns/health tcp --End--

57 Procedure steps 57 Configuring a NAS virtual IP address Procedure steps Perform this procedure to configure a NAS virtual IP address for public access to the OCS 2007 front-end pool. Create a new virtual IP address, assign group 1 to the IP address, and create the 5060 service to use TCP for client connections. This IP address is associated with the OCS 2007 front-end pool host name. Step Action 1 Configure a public virtual IP address for the group by entering the following command: /config/sl/virt 1/en/vip <virtual IP assigned to OCS front end pool>/dname <relevant domain name>/service 5060/gr 1/hname <relevant host name> --End--

58 58 NAS system configuration Adding additional services to the virtual group Procedure steps Perform this procedure for each service port you add to enable additional OCS 2007 communications. Create the 5061 service to allow TLS client connections and the 444 service for communication between internal components that manage conferencing and the conferencing servers. Step Action 1 Configure additional services to the virtual group by entering the following commands: /config/sl/virt 1/service 5061/gr 1 /config/sl/virt 1/service 444/gr 1 --End--

59 Procedure steps 59 Configuring NAS SLB ports for client and server processing Procedure steps Perform this procedure to configure the Server Load Balancing (SLB) ports on the NAS. Step Action 1 Enable the server-side port 9 for SLB by entering the following command: /config/slb/port <port where front end server #1 plugged in>/server ena/client ena/proxy ena 2 Enable the server-side port 10 for SLB. /config/slb/port <port where front end server #2 plugged in>/server ena/client ena/proxy ena 3 Enable the client-side port 27 for SLB. /config/slb/port <uplink port #1>/client ena 4 Enable the client-side port 28 for SLB. /config/slb/port <uplink port #2>/client ena --End--

60 60 NAS system configuration Enabling NAS SLB service Procedure steps Perform this procedure to enable SLB on the NAS. Step Action 1 Enable SLB by entering the following command: /config/sl/on --End--

61 Applying and saving configuration changes Procedure steps 61 Procedure steps Perform this procedure to save your configuration. Step Action 1 Enter Apply to apply the configuration changes. 2 Enter Save to save the configuration. --End--

62 62 NAS system configuration Verifying services Procedure steps Perform this procedure to verify your NAS configuration. Step Action 1 Display the current state of the server by entering the following command: /i/slb/dump 2 Under Virtual server state, verify that virtual port 5061 is defined, and both OCS 2007 front-end servers are listed as up. The following is just an example of output from this command. It does not reflect all configurations. Real server state: 1: Server1FE, 00:1a:4b:db:eb:fa, vlan 1, port 1, health 4, up Real server group 1, Workload Manager none Virtual services: sip: vport sip, rtspslb none, mirror virtual server: 1, IP : vport 5061, rtspslb none, mirror virtual server: 1, IP : vport 444, rtspslb none, mirror virtual server: 1, IP : Server2FE, 00:1b:78:08:24:0a, vlan 1, port 2, health 4, up Real server group 1, Workload Manager none Virtual services: sip: vport sip, rtspslb none, mirror virtual server: 1, IP : vport 5061, rtspslb none, mirror virtual server: 1, IP : vport 444, rtspslb none, mirror virtual server: 1, IP Virtual server state: 1: IP , 00:00:5e:00:01:02, vname poolex.example.com, dname example.com virtual ports: sip: rport sip, group 1, OCS2007Pool, backup none, rtspslb none, mirror real servers: 1: Server1FE, backup none, 0 ms, group ena, up 2: Server2FE, backup none, 1 ms, group ena, up

63 Procedure steps : rport 5061, group 1, OCSPool, backup none, rtspslb none, mirror real servers: 1: Server1FE, backup none, 0 ms, group ena, up 2: Server2FE, backup none, 0 ms, group ena, up 444: rport 444, group 1, OCSPool, backup none, rtspslb none, mirror real servers: 1: Server1FE, backup none, 0 ms, group ena, up 2: Server2FE, backup none, 0 ms, group ena, up IDS group state: Redirect filter state: Port state: 1: proxy, server, client 2: proxy, server, client 3: proxy, client 4: proxy, client 9: proxy, client 10: proxy, client 11: proxy, client 12: proxy, client 23: client --End--

64 64 NAS system configuration

65 . OCS 2007 system configuration 65 This chapter describes how to configure the Microsoft Office Communications Server 2007 (OCS 2007) Enterprise Edition. Only the Enterprise Edition has the scaling capability to support a large UC Campus Solution deployment with multiple servers. The OCS 2007 comprises the following key components: OCS 2007 Enterprise Edition servers connected as a pool. This includes various servers for pool services such as AV Conferencing, Web components, and Web Conferencing. Active Directory to store user and server information and to provide authorization for OCS users. SQL Server 2000 SP4 or SQL Server 2005 SP1 or higher to use with OSC pool. Nortel recommends that a Dynamic DNS server be available for the OCS domain. Microsoft Office Communicator is a required client. With the combination of Office Communications Server 2007 and Communication Server 1000, users can make or receive calls through their Communication Server 1000 desktop phone or through Office Communicator The following steps and figure illustrate how the remote call control feature is used to make a call to a mobile phone. The following steps correspond to the numbers in the figure. Step Action 1 A Converged Office user selects Call from their OC client to place a call to Chris mobile phone number from their CS 1000 telephone.

66 66 OCS 2007 system configuration 2 The Office Communications Server 2007 sends a call request to the CS The CS 1000 sets up a call from the user s phone to Chris mobile phone number. 4 Chris answers his mobile phone and a media path is established between the two phones. --End-- Figure 7 OCS 2007 architecture For more information, see Nortel Converged Office Fundamentals Microsoft Office Communications Server 2007 (NN ) ATTENTION The Microsoft configuration procedures in this document are provided for your convenience and are based on Microsoft OCS 2007 technical documentation. For more information about configuring OCS 2007 and the most recent configuration instructions, go to

67 Procedure steps 67 OCS 2007 configuration prerequisites Domain controllers run Microsoft Windows 2000 Server Service Pack 4 (SP4), Windows Server 2003 SP1, or Windows Server 2003 Release 2 or later. Nortel recommends Windows Server 2003 Release 2. Global catalog servers are running Windows 2000 Server SP4, Windows Server 2003 SP1, or Windows Server 2003 Release 2 or later. Nortel recommends Windows Server 2003 Release 2. Separate computers are dedicated for hosting OCS 2007 and Active Directory global catalog or domain controllers. Nortel does not support installing OCS on the same computer as an Active Directory global catalog or domain controllers is not supported. All domains in which you deploy OCS 2007 use Windows 2003 native mode or later. You cannot deploy OCS 2007 in a mixed mode domain. Members of universal groups can include other groups and accounts from any domain in the domain tree or forest and can be assigned permissions in any domain in the domain tree or forest. Universal group support, combined with administrator delegation, simplifies managing an OCS 2007 deployment. A back-end database is installed on a separate computer from OCS Nortel does not support installing a back-end database on a server that also hosts an OCS 2007 component. Nortel does support SQL Server 2000 SP4 and SQL Server 2005 SP1. Windows Script Hosting 5.6 is installed on the server where you install the back-end database. The Fully Qualified Domain Name (FQDN) of each server is correct. Check that FQDNs are correct by pinging each host. ATTENTION Nortel does not support changing the FQDN of an OCS component after deployment. No applications use ports 5060 and These ports are used to send SIP communications. Microsoft.NET Framework 2.0 is installed on the OCS 2007 servers. The OCS 2007 configuration tool checks for Microsoft.NET Framework and provides the option to install it. ATTENTION The Microsoft.NET Framework is also included on the OCS 2007 DVD. A Certification Authority for enterprise, standalone, or public is available.

68 68 OCS 2007 system configuration Internet Information Services (IIS) 6.0 or later is installed and enabled on the OCS 2007 servers. For deployments within a domain that is outside of the forest root, the deploying user or user group is added to the RTCDomainServerAdmins security group. Check that the TEMP environment variable folder is not encrypted. If the TEMP environment variable folder is encrypted, change the variable to point to a folder that is not encrypted. SQL Server, SQL Server 2000 Client Tools (for connecting to SQL 2000 SP4 or later), or the Microsoft SQL Server 2005 Backward Compatibility Components (for connecting to SQL 2005 SP1 or later) must be installed on the Windows 2003 servers used to create a pool, or on the front-end servers requiring access to the pool. This adds the necessary components to allow communication with the back-end SQL servers. Microsoft Visual C++ Redistributable Package (included in the OCS 2007 package vcredist_x86.exe) and Unified Communications Managed API V1.0 Redistributable Package (included in the OCS 2007 package UCMARedist.msi) are installed on the proxy server.

69 OCS 2007 configuration procedures OCS 2007 configuration navigation 69 This task flow shows the sequence of tasks you need to perform to configure OCS 2007 Active Directory and Office Communicator. To link to any procedure, go to OCS 2007 configuration navigation (page 69). Figure 8 OCS 2007 configuration procedures OCS 2007 configuration navigation Preparing the Active Directory (page 70) Preparing the back-end database (page 73) Configuring OCS 2007 on the front-end servers (page 76) Configuring and assigning server certificates to the OCS 2007 servers (page 78) Assigning server certificates to the Web component on the OCS 2007 servers (page 81) Verifying replication (page 82)