Nortel Unified Communications Campus Solution Conﬁguration ...

Nortel Unified Communications Campus Solution

Configuration — UnifiedCommunicationsRelease: 1.0Document Revision: 01.01

www.nortel.com

NN49000-314.

Nortel Unified Communications Campus SolutionRelease: 1.0Publication: NN49000-314Document release date: 24 April 2009

Copyright © 2009 Nortel NetworksAll Rights Reserved.

Printed in Canada and the United States of AmericaLEGAL NOTICE

While the information in this document is believed to be accurate and reliable, except as otherwise expresslyagreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OFANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document aresubject 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.

ContentsNew in this release 7

Introduction 9Nortel Professional Services 10

Unified Communications configuration prerequisites 13Unified Communications configuration procedures 13

Nortel Best Practices for Unified Communications 15Required Best Practices 15Recommended Best Practices 16

CS 1000 system configuration 17CS 1000 configuration prerequisites 18CS 1000 configuration procedures 19Configuring a new ELAN ID and VAS ID 22Enabling the ELAN connection to the switch 23Provisioning a telephone for Converged Office 24Provisioning a TLSV to associate with the telephone 25Saving the configuration 26Configuring routes and trunks 27Configuring a route list index 30Configuring a distant steering code 31Configuring a SIP gateway 32Configuring the SIP URI map 33Configuring SIP CTI services 35Configuring Signaling Server properties for SIP 37Creating the service domain in NRS 38Creating the L1 (UDP) domain in NRS 39Creating the L0 (CDP) domain in NRS 40Configuring endpoints on the NRS 41Configuring routing entries on the NRS 42Cutting over and committing changes on the NRS database 43

NAS system configuration 45NAS configuration prerequisites 47

Nortel Unified Communications Campus SolutionConfiguration — Unified Communications

NN49000-314 01.0124 April 2009

Copyright © 2008 Nortel Networks

.

4

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

OCS 2007 system configuration 65OCS 2007 configuration prerequisites 67OCS 2007 configuration procedures 69Preparing the Active Directory 70Preparing the back-end database 73Configuring OCS 2007 on the front-end servers 76Configuring and assigning server certificates to the OCS 2007 servers 78Assigning server certificates to the Web component on the OCS 2007 servers 81Verifying replication 82

Starting OCS 2007 services 83OCS 2007 services configuration procedures 84Starting the OCS 2007 server 87Configuring routes on the OCS 2007 front-end servers 88Creating a location profile 90Creating phone usages, policies, and routes 91Installing the Mediation Server 93Configuring a Mediation Server certificate 95Configuring the Mediation Server 98Starting the Mediation Server 100Installing the proxy server 101Activating the proxy server 102Configuring the server certificate for the proxy server 103Configuring the proxy server 105Installing the Multimedia Convergence Manager (MCM) 107Configuring permissions for the MCM 109Configuring the MCM 110

Configuring Active Directory and Office Communicator 113Active Directory and Office Communicator configuration procedures 114Configuring Active Directory user accounts 117


NN49000-314 01.0124 April 2009


.

5

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


NN49000-314 01.0124 April 2009


.

6


NN49000-314 01.0124 April 2009


.

7.

New in this releaseThis is the first issue of this document, Nortel Unified CommunicationsCampus Solution Configuration — Unified Communications(NN49000-314) . Because this is the first issue, all features described inthis document are new.


NN49000-314 01.0124 April 2009


.

8 New in this release


NN49000-314 01.0124 April 2009


.

9.

IntroductionUnified Communications (UC) is not a specific technology. It is anapplication foundation that integrates all your communication devicesinto a single uniform interface. This foundation enhances your individual,workgroup, and organizational productivity. UC enables you to run yourbusiness in a new way where communications are tightly coordinated withbusiness processes.

UC integrates the voice infrastructure into data applications. Now, all formsof communications are integrated including fixed and mobile voice, e-mail,instant messaging, IP-PBX, VoIP, presence, voice mail, fax, and videoconferencing. By integrating all of these systems, UC enables you to reachthe right person at the right time by using the right device.

The UC Campus solution uses the following best-in-class componentsfrom Microsoft and Nortel:

• Communication Server 1000 —This Communication Server 1000implementation includes the Media Gateway and Signaling Server.

• Microsoft Office Communications Server 2007 (OCS 2007) EnterpriseEdition—This OCS 2007 implementation includes the Mediation Serverand the Office Communicator 2007 (OC 2007). With Nortel ConvergedOffice, users can access Nortel Communication Server 1000 telephonyservices, and send and receive calls over Communication Server 1000.

• Nortel Multimedia Convergence Manager (MCM) installed on anOCS 2007 Proxy Server—This component provides interoperabilitybetween the OCS 2007 and the Communication Server 1000. In theUC Campus environment, the MCM software is located between theMediation Server and Communication Server 1000. MCM has twomain components: MCM Service, which handles call processing, andMCM Management Console, which interfaces with the MCM Servicefor configuration, administration, and maintenance. The MCM callprocessing service handles SIP telephony traffic between CS 1000 andOCS 2007.


NN49000-314 01.0124 April 2009


.

10 Introduction

ATTENTIONUC Campus uses MCM and Converged Office as a gateway betweenCommunication Server 1000 and OCS 2007. This configuration enables you touse all of the Nortel Converged Office services.

In the UC Campus Solution, the Nortel Communication Server 1000provides enterprise-class Voice over IP services and the Microsoft OfficeCommunications Server (OCS) 2007 provides Unified Communicationsservices including presence and instant messaging. With integrationservices provided by MCM, the CS 1000 and OCS 2007 work together toprovide a complete unified communications system.

The following figure illustrates the basic high-level architecture of theUnified Communications infrastructure. This document describes how tointegrate the various elements, including the deployment of the NortelApplication Switch to load-balance traffic to multiple OCS Proxy/MCMsand to multiple OCS Front Ends. With this configuration a highly resilientimplementation is achieved, with no single point of failure in the SIPsignalling path.

Figure 1Unified Communications architecture

Nortel Professional ServicesNortel Global Services offers solutions that combine comprehensivenetwork expertise, world class partners and global reach. For the UCCampus Solution, Nortel Global Services provides a complete range ofservices for the products described in the rest of this document. For further


NN49000-314 01.0124 April 2009


.

Nortel Professional Services 11

details on services to complement the design, deployment and supportof a UC Campus Solution, see Nortel Unified Communications CampusSolution Fundamentals (NN49000-100.) .


NN49000-314 01.0124 April 2009


.

12 Introduction


NN49000-314 01.0124 April 2009


.

13.

Unified Communications configurationprerequisites

• You have basic programming and provisioning skills for theCommunication Server 1000. Nortel recommends that you completeproduct-specific training before you begin the systems integration. Acomplete list of courses is available at www.nortel.com.

• You are skilled in Microsoft Active Directory, Domain Name Service,and DHCP services.

• You performed a network health check in the planning phase of theintegration to ensure appropriate network bandwidth and to identify theprotocols, payload size, and codecs to use.

• You established a system baseline so that the CommunicationServer 1000 and OCS 2007 systems are configured and working in astand-alone environment.

Unified Communications configuration proceduresThis work flow shows the sequence of tasks you need to perform tointegrate the Unified Communications components. To link to anyprocedure, go to “Unified Communications configuration navigation” (page14).


NN49000-314 01.0124 April 2009


.

http://www.avaya.com

14 Unified Communications configuration prerequisites

Figure 2CS 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)


NN49000-314 01.0124 April 2009


.

15.

Nortel Best Practices for UnifiedCommunications

Nortel developed Best Practices for the UC Campus Solution afterextensive testing in the lab and implementing many networks in thefield. When implemented properly, these Best Practices ensure that yournetwork will be stable and reliable.

The two types of Best Practices are:

• required

• recommended

Required Best Practices reflect the UC Campus architecture and matchthe Nortel prevalidated configuration.

Recommended Best Practices are Nortel suggestions based on yearsof experience. In most implementations, these Best Practices improvenetwork reliability and performance. However, Nortel recognizes that theymay not be relevant for all networks so they are not required.

For additional planning and Best Practices information, obtain thefollowing publication from the Nortel Technical Support Portal site(http://support.nortel.com/go/main.jsp): Load Balancing Microsoft OfficeCommunication Server 2007 in a Consolidated Topology with ApplicationSwitch Technical Configuration Guide (NN48500-530.)

Required Best PracticesYou must implement these Best Practices to be eligible for UC CampusSolution 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 Serverside.

• Use Direct Access mode.


NN49000-314 01.0124 April 2009


.

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 PracticesNortel recommends these Best Practices as suggestions to improve yournetwork. 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 inhot standby mode and use the preferred link connecting to the MasterVRRP NAS.

• When the server is directly connected to the Horizontal Stack SwitchCluster, configure teaming in load balancing mode.

• Enable DOS attack protection on client-side ports.

• Add SIP and TLS services to separate groups. This allows fasterfailover 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 SQLserver.


NN49000-314 01.0124 April 2009


.

17.

CS 1000 system configurationThis chapter describes how to integrate the Communication Server 1000system with Microsoft Office Communications Server 2007 (OCS2007) Enterprise Edition services. For more information about theCommunication Server 1000 and the UC Campus voice applications, seeNortel Unified Communications Campus Solution Configuration — VoiceServices (NN49000-314.)

The basic architecture for the UC Campus voice services includes thefollowing components:

• Communication Server 1000E in High Availability mode

• IP Phone sets


NN49000-314 01.0124 April 2009


.

18 CS 1000 system configuration

CS 1000 configuration prerequisites

• Integrate OCS 2007 with Communication Server 1000 when bothsystems are installed and a baseline of operation is achieved andtested.

• The Communication Server 1000 system has adequate licenses for thenumber of required SIP ports. Converged Office includes the licensesfor TLSV, SIP CTI TR87, and AST.

• The Communication Server 1000 Call Server is configured.

• The Communication Server 1000 dialing plan is configured andworking.

• A Communication Server 1000 D-channel is configured and working.

• A Communication Server 1000 Signaling Server node is installed andworking.

• Network Routing Service (NRS) is enabled. NRS can be either SIPProxy Server (SPS) or SIP Redirect Server (SRS).

• You have Enterprise Common Manager (ECM) logon access withadministrator privileges.


NN49000-314 01.0124 April 2009


.

Recommended Best Practices 19

CS 1000 configuration procedures

This task flow shows the sequence of tasks you need to perform tointegrate the Communication Server 1000 system with OCS 2007. To linkto any procedure, go to “CS 1000 configuration navigation” (page 20).

Figure 3CS 1000/OCS 2007 integration procedues


NN49000-314 01.0124 April 2009


.


Figure 4CS 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)


NN49000-314 01.0124 April 2009


.

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” (page43)


NN49000-314 01.0124 April 2009


.


Configuring a new ELAN ID and VAS ID

Define and configure the ELAN ID for the AML link and the associatedVAS ID in the configuration record. Perform this procedure only if an ELANID and VAS ID are not available.

Procedure steps

Step Action

1 Connect to the Call Server.

2 Enter LD 17.

3 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 nextavailable number from 32 to 127.

7 After the CTYP prompt, enter ELAN.

8 After the DES prompt, enter a relevant description such asELAN1. .

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 ELANID.

13 After the ELAN prompt, enter the number entered for the ELANID.

14 After the SECU prompt, enter YES.

15 To exit the overlay, enter ****.

16 To view the new ELAN, enter LD 22.

17 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 inhyperterminal.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 23

Enabling the ELAN connection to the switch

Perform this procedure to enable the LD 48 ELAN connection to theswitch.

Procedure steps

Step Action


2 Enter LD 48.

3 Enter ENL ELAN to enable the ELAN.


5 To view the status of the ELAN, enter STAT ELAN.

--End--


NN49000-314 01.0124 April 2009


.


Provisioning a telephone for Converged Office

Provision the user telephone. You must do this before you provisionTelephony Services (TLSV) so that you can associate the telephone withthe TLSV.

Procedure steps

Step Action


2 Enter LD 20.


4 After the REQ prompt, enter NEW to create a new telephoneentry.

5 After the TYPE prompt, enter the type of phone such as 1140.

6 After the TN prompt, enter the terminal number in the format ofaaa. bbb.ccc.ddd (<loop>.<shelf>.<card slot>.<card channel>).

7 After the DES prompt, enter a relevant description for thetelephone 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.

ATTENTIONDo not configure CLS as CDMV or CDMO. They cause the users tobe treated as MCS users.

11 After the AST prompt, enter the SCR key location, which isusually the primary location of 0.

12 After the KEY prompt, enter 0 SCR <xxxx> and the line numberof the telephone.


--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 25

Provisioning a TLSV to associate with the telephone

Provision a TLSV with the same DN as a user in a Multiple AppearanceDirectory Number (MADN) arrangement. This offers incoming voice callsto the user’s DN on their Microsoft Office Communicator Client 2007 (OCC2007) as well as any telephones configured with the same DN.

Prerequisite• Provision the user’s telephone so that you can associate it with TLSV.

Procedure steps

Step Action


2 Enter LD 11.


4 After the REQ prompt, enter NEW to create a new telephoneentry.

5 After the TYPE prompt, enter TLSV.

6 After the TN prompt, enter the terminal number in the format ofaaa. bbb.ccc.ddd (<loop>.<shelf>.<card slot>.<card channel>).

7 After the DES prompt, enter a relevant description for thetelephone 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.

ATTENTIONDo not configure CLS as CDMV or CDMO. They cause the users tobe treated as MCS users.

11 After the KEY prompt, enter 0 SCR <xxxx> and the line numberof the telephone.

12 After the KEY prompt, enter 1 HOT p <x> <yyyy> and thedistant steering code.


--End--


NN49000-314 01.0124 April 2009


.


Saving the configuration

Perform this procedure to save your configuration changes.

Procedure steps

Step Action


2 Enter LD 43.

3 Enter EDD.


--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 27

Configuring routes and trunks

Perform this procedure to configure routes and trunks for SIP channelson the Communication Server 1000 system. If you use an existingconfiguration, perform these procedures to confirm the settings required forOCS 2007.

Procedure steps

Step Action

1 In Enterprise Common Manager (ECM), expand the Routes andTrunks 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 definitionsUse the data in the following table to configure the route configurationproperties.

Variable Value

Route Number (ROUT) Type the next available route number.Example: 5

Designator field for trunk (DES) Type a relevant description.Example: SIP

Trunk Type (TKTP) TIE

Incoming and Outgoing trunk (ICOG) Incoming and outgoing (IOA)

Access Code for the trunk route (ACOD) Type a relevant access code for your system.Example: 7905

The route is for a virtual trunk route (VTRK) Enable

Zone for codec selection and bandwidthmanagement (ZONE)

Type a relevant zone for your system.Example: 2


NN49000-314 01.0124 April 2009


.


Variable Value

Node ID of signaling server of this route (NODE) Type the node number for your system.Example: 5

Protocol ID for the route (PCID) SIP

Integrated Services Digital Network option(ISDN)

Enable

Mode of operation (MODE) Route uses ISDN Signaling Link (ISLD)

D channel number (DCH) Type the channel configured for your system.Example: 1

Interface type for route (IFC) Meridian 1 SL1

Private Network Identifier (PNI) Type the identifier for your system.

Network Calling Name Allowed (NCNA) Enable

Network Call Redirection (NCRD) Enable

Trunk Route Optimization (TRO) Enable

Channel Type (CHTY) B-Channel (BCH)

Call Type for outgoing direct dialed TIE route(CTYP)

Select your dialing plan.Example: CDP or UDP

SIGO ESN5

Trunk configuration variable definitionsUse the data in the following table to configure the trunk configurationproperties.

Variable Value

Multiple trunk input number (MTINPUT) Select the number of trunks to add.This creates a number of TN trunks. Ensurethat you have enough unused TNs in a span tocover this number of trunks.

Trunk data block (TYPE) IPTI

Terminal Number (TN) 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: 100 0 1 20

Designator field for trunk (DES) Type a relevant description for the TNs.

Route number, Member number (RTMB) Type the route number and trunk start.The route number is the one in which you arecreating the TN. The member number is thetrunk you create.Example: 5 1

Card Density (CDEN) Select the card density type.Example: 8D


NN49000-314 01.0124 April 2009


.

Procedure steps 29

Variable Value

Start arrangement Incoming (STRI) Select Wink or Fast Flah (WNK).

Start arrangement Outgoing (STRO) Select Wink or Fast Flah (WNK).

Trunk Group Access Restriction (TGAR) Type the number for your system.Example: 1

Channel ID for this trunk (CHID) Type a relevant ID for the trunk.Example: 2222

Increase or decrease the member numbers(INC)

If you select Increase Channel and Membernumber (yes), several TNs are createddepending on the values of the MTINPUT andTN parameters.


NN49000-314 01.0124 April 2009


.


Configuring a route list index

Perform this procedure to configure a route list index (RLI) for your SIPchannels. This coordinates with the route configured above. If you use anexisting RLI, perform this procedure to verify the data.

Procedure steps

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 activatethe Add button, and then click Add .

7 For ROUT, select the route that you previously created.

8 Click Submit.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 31

Configuring a distant steering code

Perform this procedure to configure a new Distant Steering Code (DSC).The DSC coordinates with the RLI configured above.

Procedure steps

Step Action

1 In ECM, select Dialing and number plans, ElectronicSwitched Network.

2 Select Coordinated Dialing Plan (CDP), Distant SteeringCode (DSC).

3 Select Add to add a new DSC.

4 For Please enter a distant steering code, type a new DSC (forexample, 5505).

5 In the Flexible Length field, enter the number of digits (from 0 to10) that the system expects to receive before accessing a trunkand outpulsing these digits.

6 In the DSP field, select the Directory Number (DN) to use forCLID.

7 In the Route List field, select the RLI number created.

8 Click Submit.

--End--


NN49000-314 01.0124 April 2009


.


Configuring a SIP gateway

Perform this procedure to configure your SIP gateway settings. For moreinformation, see IP Peer Networking Installation and Commissioning(NN43001-313.)

Procedure steps

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 wishto modify.

4 Expand the SIP GW Settings heading.

5 In the Primary Proxy or Redirect (TLAN) IP address field, typethe IP address of your proxy or redirect server.

6 In the Port field, type the SIP port number (usually 5060 bydefault).

7 In the Supports Registration field, select Enable.

8 In the Primary Proxy or Redirect server flag field, selectEnable.

9 In the Transport Protocol field, select TCP.

10 Configure the SIP Gateway settings for your secondary proxyor redirect server, if applicable.

--End--


NN49000-314 01.0124 April 2009


.

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 andCommissioning (NN43001-313.)

ATTENTIONConfigure the SIP URI map based on the network engineered dial plan valuesthat 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 proxyor redirect server, if applicable.

--End--

Variable definitionsUse the data in the following table to set the SIP URI properties.

Variable Value

Public E.164/National domain name Type the public E.164/National domain for yoursystem.Example: +1

Public E.164/Subscriber domain name Type the Public E.164/Subscriber domain namefor your system.Example: +1506

Public E.164/Unknown domain name Type the Public E.164/Unknown domain namefor your system.Example: PublicUnknown.This parameter is optional.

Public E.164/Special Number domain name Type the Public E.164/Special Number domainname for your system.Example: PublicSpecial.This parameter is optional.

Private/UDP domain name Type the Private/UDP domain name for yoursystem.Example: UDP


NN49000-314 01.0124 April 2009


.


Variable Value

Private/CDP domain name Type the Private/CDP domain name for yoursystem, including the DP domain name.Example: CDP.UDP

Private/Special Number domain name Type the Private/Special Number domain namefor your system.Example: PrivateSpecialThis parameter is optional.

Private/Unknown (vacant number routing)domain name

Type the Private/Unknown domain name foryour system.Example: PrivateUnknownThis parameter is optional.

Unknown/Unknown domain name Type the Unknown/Unknown domain name foryour system.Example: UnknownUnknownThis parameter is optional.


NN49000-314 01.0124 April 2009


.

Procedure steps 35

Configuring SIP CTI services

Perform this procedure to configure the SIP Computer TelephonyIntegration (CTI) services. For more information, see IP Peer NetworkingInstallation and Commissioning (NN43001-313.)

ATTENTIONThe SIP CTI services must match the values that you defined in the SIP URImap.

Procedure steps

Step Action

1 Expand the SIP CTI Services heading.

2 Configure the SIP CTI services parameters according to thefollowing variable definitions table.

3 Configure the SIP CTI services settings for your secondary proxyor redirect server, if applicable.

--End--

Variable definitionsUse the data in the following table to set the SIP CTI services properties.

Variable Value

Service Enabled Enable

You must reboot the Signaling Server for theenabling of SIP CTI to take effect. A systemreboot takes the Signaling Server out of service.Reboot during a time that will not impact service.

Support TLS Enpoints Only Disable

Customer Number 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 CountryAs National Calls

Enable if applicable.

National Prefix Enter number according to your dialing plan.

International Prefix Enter number according to your dialing plan.

Location Code Call Prefix Enter number according to your dialing plan.

Special Number Prefix Enter number according to your dialing plan.


NN49000-314 01.0124 April 2009


.


Variable Value

Subscriber Prefix Enter number according to your dialing plan.

Dialing Plan Select the dialing plan for your engineeredsystem.Example: CDP

Calling Device URI format Select phone-context=<SIP URI Map Entries>

Home Location Code Enter number according to your dialing plan.

Country Code (CCC) Enter number according to your dialing plan.

Area Code (Area Code) Enter number according to your dialing plan.

#Digits to Strip and Prefix to Insert Enter number according to your dialing plan.


NN49000-314 01.0124 April 2009


.

Procedure steps 37

Configuring Signaling Server properties for SIP

Perform this procedure to configure the SIP signaling server properties.For more information, see IP Peer Networking Installation andCommissioning (NN43001-313.)

Procedure steps

Step Action

1 Expand the Signaling Servers, Signaling Server [yourSignaling Server IP] Properties heading.

2 Configure the SIP Signaling Server.

3 Click Save and Transfer.

4 Click OK.

--End--

Variable definitionsUse the data in the following table to set the SIP Signaling Serverproperties.

Variable Value

Enable IP Peer Gateway (Virtual Trunk TPS) Select H.323 and SIP.Selecting both H.323 and SIP allows for a dualnetwork and takes H.323 into consideration, ifyou use devices requiring that protocol.

Enable SIP proxy/Redirect Server Enable only if you use co-resident NRS.

Local SIP TCP/UDP port to listen to Type the default SIP port number (usually5060). Ensure that this value coordinates withyour end devices.

SIP Domain name Type the SIP domain name to be usedthroughout the system configuration.Example: convergedoffice.com

SIP Gateway Endpoint Name Type the Gateway endpoint name to beregistered in the NRS.

SIP Gateway Authentication Password If you enable security and use authenticationin the NRS when you create endpoints, thispassword is used for authentication.

Enable Gatekeeper Enable

Network Service Role Issue only if you use co-resident NRS. Optionsare Primary, Alternate, and Failsafe.


NN49000-314 01.0124 April 2009


.


Creating the service domain in NRS

Perform this procedure to create a SIP service domain on a NetworkRouting Server (NRS) if one is not already created. On redundant NRSsystems, perform all configurations on the primary NRS.

Procedure steps

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 activeto 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 youpreviously configured.

7 For Domain description, enter a relevant description for thedomain being used.

8 Click Save.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 39

Creating the L1 (UDP) domain in NRS

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 youprovisioned in the SIP URI Map. Some parameters are optional for yoursystem. For a system with full Basic Automatic Route Selection/NetworkAutomatic Route Selection (BARS/NARS) or a UDP dialing plan, you mustconfigure the applicable parameters for your engineered dialing plan.

Procedure steps

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 thedomain used.

5 For E.164 country code, enter the E.164 country code for yoursystem.

6 For E.164 area code, enter the E.164 area code for yoursystem.

7 Configure other optional parameters as required for your system.

8 Click Save.

--End--


NN49000-314 01.0124 April 2009


.


Creating the L0 (CDP) domain in NRS

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 youprovisioned in the SIP URI Map. Some parameters are optional for yoursystem. For a system with full BARS/NARS or a UDP dialing plan, youmust configure the applicable parameters for your engineered dialing plan.

Procedure steps

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 thedomain used.

5 For E.164 country code, enter the E.164 country code for yoursystem.

6 For E.164 area code, enter the E.164 area code for yoursystem.

7 Configure other optional parameters as required for your system.

8 Click Save.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 41

Configuring endpoints on the NRS

Perform this procedure to configure the MCM Gateway endpoints on theNetwork Routing Service (NRS). You must perform this procedure foreach MCM node on the system. On NRS redundant systems, perform allconfiguration on the primary NRS.

ATTENTIONUC Campus Solution uses the Multimedia Convergence Manager (MCM) andConverged Office as a gateway between Communication Server 1000 and OCS2007. This configuration enables you to use all of the Nortel Converged Officeservices. However, UC Campus also supports using the Communication Server1000 as a direct PSTN gateway to OCS 2007 without MCM and ConvergedOffice. 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 (forexample, 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 MCMgateway 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 5060.

12 Click Save.

--End--


NN49000-314 01.0124 April 2009


.


Configuring routing entries on the NRS

Perform this procedure to add a routing entry for each MCM gatewayendpoint. The Signaling Server endpoint is already configured accordingto your dial plan. On NRS redundant systems, perform all configurationon the primary NRS.

ATTENTIONUC Campus Solution uses the Multimedia Convergence Manager (MCM) andConverged Office as a gateway between Communication Server 1000 and OCS2007. This configuration enables you to use all of the Nortel Converged Officeservices. However, UC Campus also supports using the Communication Server1000 as a direct PSTN gateway to OCS 2007 without MCM and ConvergedOffice. 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 L0domain are selected.

3 Select the Endpoint for which you want to add a route, and clickAdd.

4 Select the DN Type.

5 Type the DN prefix.The DN prefix is the DSC that you created in the Configuring aDistant Steering Code procedure. The DN prefix can be up to30 characters in length and can include the characters 0 to 9,#, -, ?. The first character of the DN prefix must be numeric (forexample, 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 thecost of using the route. Configure the route cost based on theengineered dial plan for your network.

7 Click Save.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 43

Cutting over and committing changes on the NRSdatabase

Perform this procedure to switch between the active and standby databaseaccess pointers. This swaps the primary and standby databases so thatconfiguration changes take effect.

Procedure steps

Step Action

1 In NRS Manager, expand System.

2 Select Database.

3 Click Cut Over.

4 Click Commit.

--End--


NN49000-314 01.0124 April 2009


.



NN49000-314 01.0124 April 2009


.

45.

NAS system configurationThe UC Campus Solution uses the Nortel Application Switch (NAS) toprovide security, resiliency, and load balancing. This chapter describes theNAS role as a load balancer.

For load balancing, a pair of NAS devices in Active Standby mode withan Inter-Switch Link (ISL) between them load balance the OCS 2007front-end servers. Network Load Balancing uses a distributed algorithm toload balance TCP/IP network traffic across a number of hosts, enhancingthe scalability and availability of mission critical, IP-based services, suchas Web, VPN, Streaming Media, and Firewalls. Network Load Balancingalso provides high availability by detecting host failures and automaticallyredistributing traffic to remaining operational hosts.

The following figure shows the relationship of the two load-balancing NASdevices relative to the other elements in the UC Campus Data Center.


NN49000-314 01.0124 April 2009


.

46 NAS system configuration

Figure 5UC Campus Data Center showing NAS


NN49000-314 01.0124 April 2009


.

Procedure steps 47

NAS configuration prerequisites

• Integrate OCS 2007 with Communication Server 1000 when bothsystems are installed and a baseline of operation is achieved andtested.

• Install NAS.

• Connect and configure a management Ethernet port.

• Reserve three IP addresses per VLAN for assignment to the HighAvailable NAS pair.

• Reserve one IP address to assign a virtual IP address for the OCS2007 pool. An entry is required in the DNS server to resolve the OCS2007 pool host name to this IP address.


NN49000-314 01.0124 April 2009


.


NAS configuration procedures

This task flow shows the sequence of tasks you need to perform toconfigure NAS. To link to any procedure, go to “NAS configurationnavigation” (page 50).


NN49000-314 01.0124 April 2009


.

Procedure steps 49

Figure 6NAS configuration procedures


NN49000-314 01.0124 April 2009


.


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)


NN49000-314 01.0124 April 2009


.

Procedure steps 51

Configuring NAS VLAN 2

Perform this procedure to create a new VLAN named VLAN 2.

Procedure steps

Step Action

1 Configure the server VLAN by entering the following command:

/config/l2/vlan 2/ena/name "<vlan name>"/def <portsused for front ends, multiple ports use spaces>

2 When prompted to confirm changing the PVID for VLAN ports,enter y.

--End--


NN49000-314 01.0124 April 2009


.


Configuring NAS uplink ports

Perform this procedure to configure the uplink ports.

Procedure steps

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--


NN49000-314 01.0124 April 2009


.

Procedure steps 53

Disabling NAS STP

Perform this procedure to disable Spanning Tree Protocol (STP) on theNAS.

Procedure steps

Step Action

1 Disable STP by entering the following command:

/config/l2/stg 1/off

--End--


NN49000-314 01.0124 April 2009


.


Configuring the NAS layer 3 Gateway interfaces

Perform this procedure to create Gateways for VLAN 1 and VLAN 2.

Procedure steps

Step Action

1 Configure the layer 3 interface for VLAN 1 by entering thefollowing command:

/config/l3/if 1/add <layer 3 ip for vlan 1>/mask <subnetmask>/vlan 1/en

2 Configure the layer 3 interface for VLAN 2.

/config/l3/if 2/add <layer 3 IP for vlan 2>/mask <subnetmask>/vlan 2/en/apply

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 55

Configuring OCS 2007 real server IP addresses

Perform this procedure to configure real OCS 2007 server IP addresses.

Procedure steps

Step Action

1 Configure the IP address for the first OCS 2007 front-end serverby entering the following command:

/config/slb/real 1/rip <real ip of ocs frontend server#1>/ena/name “<relevant description for entry>”/tmout30

2 Configure the IP address for the second OCS 2007 front-endserver.

/config/slb/real 2/rip <real ip of ocs frontend server#2>/ena/name “<relevant description for entry>”/tmout30

--End--


NN49000-314 01.0124 April 2009


.


Configuring the new group and adding real servers

Perform this procedure to create a new group and assign the real OCS2007 servers to the group.

Procedure steps

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>"/metricleastconns/health tcp

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 57

Configuring a NAS virtual IP address

Perform this procedure to configure a NAS virtual IP address for publicaccess 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 TCPfor client connections. This IP address is associated with the OCS 2007front-end pool host name.

Procedure steps

Step Action

1 Configure a public virtual IP address for the group by enteringthe following command:

/config/sl/virt 1/en/vip <virtual IP assigned to OCSfront end pool>/dname <relevant domain name>/service5060/gr 1/hname <relevant host name>

--End--


NN49000-314 01.0124 April 2009


.


Adding additional services to the virtual group

Perform this procedure for each service port you add to enable additionalOCS 2007 communications. Create the 5061 service to allow TLS clientconnections and the 444 service for communication between internalcomponents that manage conferencing and the conferencing servers.

Procedure steps

Step Action

1 Configure additional services to the virtual group by entering thefollowing commands:

/config/sl/virt 1/service 5061/gr 1

/config/sl/virt 1/service 444/gr 1

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 59

Configuring NAS SLB ports for client and serverprocessing

Perform this procedure to configure the Server Load Balancing (SLB) portson the NAS.

Procedure steps

Step Action

1 Enable the server-side port 9 for SLB by entering the followingcommand:

/config/slb/port <port where front end server #1 pluggedin>/server ena/client ena/proxy ena

2 Enable the server-side port 10 for SLB.

/config/slb/port <port where front end server #2 pluggedin>/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--


NN49000-314 01.0124 April 2009


.


Enabling NAS SLB service

Perform this procedure to enable SLB on the NAS.

Procedure steps

Step Action

1 Enable SLB by entering the following command:

/config/sl/on

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 61

Applying and saving configuration changes

Perform this procedure to save your configuration.

Procedure steps

Step Action

1 Enter Apply to apply the configuration changes.

2 Enter Save to save the configuration.

--End--


NN49000-314 01.0124 April 2009


.


Verifying services

Perform this procedure to verify your NAS configuration.

Procedure steps

Step Action

1 Display the current state of the server by entering the followingcommand:

/i/slb/dump

2 Under Virtual server state, verify that virtual port 5061 isdefined, and both OCS 2007 front-end servers are listed as up.

The following is just an example of output from this command. Itdoes not reflect all configurations.

Real server state:1: Server1FE, 00:1a:4b:db:eb:fa, vlan 1, port 1, health 4, upReal server group 1 , Workload Manager noneVirtual services:sip: vport sip, rtspslb none, mirrorvirtual server: 1, IP4 10.10.108.1265061: vport 5061, rtspslb none, mirrorvirtual server: 1, IP4 10.10.108.126444: vport 444, rtspslb none, mirrorvirtual server: 1, IP4 10.10.108.126

2: Server2FE, 00:1b:78:08:24:0a, vlan 1, port 2, health 4, upReal server group 1 , Workload Manager noneVirtual services:sip: vport sip, rtspslb none, mirrorvirtual server: 1, IP4 10.10.108.1265061: vport 5061, rtspslb none, mirrorvirtual server: 1, IP4 10.10.108.126444: vport 444, rtspslb none, mirrorvirtual server: 1, IP4 10.10.108.126

Virtual server state:1: IP4 10.10.108.126, 00:00:5e:00:01:02, vnamepoolex.example.com, dname example.comvirtual ports:sip: rport sip, group 1, OCS2007Pool, backup none, rtspslbnone, mirrorreal servers:1: Server1FE, backup none, 0 ms, group ena, up2: Server2FE, backup none, 1 ms, group ena, up


NN49000-314 01.0124 April 2009


.

Procedure steps 63

5061: rport 5061, group 1, OCSPool, backup none, rtspslbnone, mirrorreal servers:1: Server1FE, backup none, 0 ms, group ena, up2: Server2FE, backup none, 0 ms, group ena, up

444: rport 444, group 1, OCSPool, backup none, rtspslbnone, mirrorreal servers:1: Server1FE, backup none, 0 ms, group ena, up2: Server2FE, backup none, 0 ms, group ena, up

IDS group state:

Redirect filter state:

Port state:1: proxy, server, client2: proxy, server, client3: proxy, client4: proxy, client9: proxy, client10: proxy, client11: proxy, client12: proxy, client23: client

--End--


NN49000-314 01.0124 April 2009


.



NN49000-314 01.0124 April 2009


.

65.

OCS 2007 system configurationThis chapter describes how to configure the Microsoft OfficeCommunications Server 2007 (OCS 2007) Enterprise Edition. Only theEnterprise Edition has the scaling capability to support a large UC CampusSolution deployment with multiple servers.

The OCS 2007 comprises the following key components:

• OCS 2007 Enterprise Edition servers connected as a pool. Thisincludes various servers for pool services such as AV Conferencing,Web components, and Web Conferencing.

• Active Directory to store user and server information and to provideauthorization for OCS users.

• SQL Server 2000 SP4 or SQL Server 2005 SP1 or higher to use withOSC pool.

• Nortel recommends that a Dynamic DNS server be available for theOCS domain.

• Microsoft Office Communicator is a required client.

With the combination of Office Communications Server 2007 andCommunication Server 1000, users can make or receive calls throughtheir Communication Server 1000 desktop phone or through OfficeCommunicator 2007.

The following steps and figure illustrate how the remote call control featureis used to make a call to a mobile phone. The following steps correspondto the numbers in the figure.

Step Action

1 A Converged Office user selects Call from their OC client toplace a call to Chris’ mobile phone number from their CS 1000telephone.


NN49000-314 01.0124 April 2009


.

66 OCS 2007 system configuration

2 The Office Communications Server 2007 sends a call request tothe CS 1000.

3 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 establishedbetween the two phones.

--End--

Figure 7OCS 2007 architecture

For more information, see Nortel Converged Office Fundamentals —Microsoft Office Communications Server 2007 (NN43001-121.)

ATTENTIONThe Microsoft configuration procedures in this document are provided for yourconvenience and are based on Microsoft OCS 2007 technical documentation.For more information about configuring OCS 2007 and the most recentconfiguration instructions, go to www.microsoft.com.


NN49000-314 01.0124 April 2009


.

http://www.microsoft.com

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 2or 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 orlater. Nortel recommends Windows Server 2003 Release 2.

• Separate computers are dedicated for hosting OCS 2007 and ActiveDirectory global catalog or domain controllers. Nortel does not supportinstalling OCS on the same computer as an Active Directory globalcatalog or domain controllers is not supported.

• All domains in which you deploy OCS 2007 use Windows 2003 nativemode or later. You cannot deploy OCS 2007 in a mixed mode domain.Members of universal groups can include other groups and accountsfrom any domain in the domain tree or forest and can be assignedpermissions in any domain in the domain tree or forest. Universalgroup support, combined with administrator delegation, simplifiesmanaging an OCS 2007 deployment.

• A back-end database is installed on a separate computer fromOCS 2007. Nortel does not support installing a back-end database ona 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 installthe back-end database.

• The Fully Qualified Domain Name (FQDN) of each server is correct.Check that FQDNs are correct by pinging each host.

ATTENTIONNortel does not support changing the FQDN of an OCS component afterdeployment.

• No applications use ports 5060 and 5061. These ports are used tosend SIP communications.

• Microsoft .NET Framework 2.0 is installed on the OCS 2007 servers.The OCS 2007 configuration tool checks for Microsoft .NET Frameworkand provides the option to install it.

ATTENTIONThe Microsoft .NET Framework is also included on the OCS 2007 DVD.

• A Certification Authority for enterprise, standalone, or public isavailable.


NN49000-314 01.0124 April 2009


.


• Internet Information Services (IIS) 6.0 or later is installed and enabledon the OCS 2007 servers.

• For deployments within a domain that is outside of theforest root, the deploying user or user group is added to theRTCDomainServerAdmins security group.

• Check that the TEMP environment variable folder is not encrypted.If the TEMP environment variable folder is encrypted, change thevariable to point to a folder that is not encrypted.

• SQL Server, SQL Server 2000 Client Tools (for connecting to SQL2000 SP4 or later), or the Microsoft SQL Server 2005 BackwardCompatibility 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 thenecessary components to allow communication with the back-end SQLservers.

• Microsoft Visual C++ Redistributable Package (included in theOCS 2007 package vcredist_x86.exe) and Unified CommunicationsManaged API V1.0 Redistributable Package (included in the OCS 2007package UCMARedist.msi) are installed on the proxy server.


NN49000-314 01.0124 April 2009


.

OCS 2007 configuration navigation 69

OCS 2007 configuration procedures

This task flow shows the sequence of tasks you need to perform toconfigure OCS 2007 Active Directory and Office Communicator. To link toany procedure, go to “OCS 2007 configuration navigation” (page 69).

Figure 8OCS 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 2007servers” (page 78)

• “Assigning server certificates to the Web component on the OCS 2007servers” (page 81)

• “Verifying replication” (page 82)


NN49000-314 01.0124 April 2009


.


Preparing the Active Directory

Before installing OCS 2007, you must prepare the Active DirectoryService. Perform this procedure to prepare the schema from a domaincontroller and then prepare the forest and domain from the OCS 2007server.

Procedure steps

Step Action

1 Log on to the Domain Controller.

2 Select Start, Run and type dsa.msc.

3 Right-click the domain and select Raise Domain FunctionalLevel to ensure that the Domain Controller is operating inWindows 2003 native mode.

4 Navigate to the installation directory for OCS 2007 (for example,E:\OCS2007\Setup\i386).

5 Double-click the setup.exe file.The Deployment Wizard page appears.

6 Select Deploy Pool in a Consolidated Topology.The Prepare Active Directory for Office Communications Serverpage appears.

7 Select Prepare Active Directory.

8 Select Step 1: Prep Schema and click Run.This can take several minutes.The Directory Location of Schema Files page appears.

9 Click Next.The Ready to Prepare Schema page appears.

10 Click Next.The Completion page appears.

11 Select the View the log when you click Finish check box, andthen click Finish.

12 Switch to the Deployment Log and click Expand All in theupper-right corner. Verify that the result of each task is Success.

13 Select Step 3: Prep Forest and click Run.This can take several minutes.The Welcome page appears.

14 Click Next.The Select System Container in the Root Domain page appears.

15 Click Next.The Location of Universal Groups page appears.


NN49000-314 01.0124 April 2009


.

Procedure steps 71

16 For Domain, verify that the Active Directory forest domain isselected.

17 Click Next.The Specify the SIP Domain Used for Default Routing pageappears.

18 Verify that the SIP domain is selected in the Select SIP domainmenu.

19 Click Next.The Ready to Prepare Forest page appears.


21 Select the View the log when you click Finish check box, andthen click Finish.


23 Select Step 5: Prep Current Domain and click Run.This can take several minutes.The Welcome page appears.

24 Click Next.The Domain Preparation Information page appears.

25 Click Next.The Ready to Prepare Domain page appears.


27 Select the View the log check box.

28 Click Finish.

29 Switch to the Deployment Log and click Expand All in theupper-right corner.

30 Verify that the result of each task is Success.

31 On the Completion page, click Finish.The Prepare Active Directory for Office Communications Serverpage appears.

32 Click Back.Notice that Step 1: Prepare Active Directory appears. Complete.

33 From the domain controller, select Start, Run and enterexplorer.


NN49000-314 01.0124 April 2009


.


34 Using Windows Explorer, create three shared directories:

• OCS 2007 content folder (for example, \\rome\ocscontent)

• OCS 2007 meta data folder (for example, \\rome\ocsmetadata)

• OCS 2007 Address Book folder (for example, \\rome\ocsaddressbook)

The domain controller contains content for the OCS 2007 systemusing these file directory shares.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 73

Preparing the back-end database

Perform this procedure to configure the SQL Server, create SQL databasecomponents for the pool, and configure the pool.

Prerequisite• You must install SQL Server 2000 SP4 or SQL Server 2005 SP1.

Procedure steps

Step Action

1 On the DNS server, create a host record for allpool.innlab.nortel.com that resolves to the VIP address 192.167.130.45.

2 Log on to the SQL Server (OCSDB1) using domain credentials.


4 Double-click the setup.exe file.The Deployment Wizard page appears.

5 Click Deploy Pool in a Consolidated Topology.The Deploy Enterprise Pool in a Consolidated Topology pageappears.

6 For Create an enterprise pool, select Run.The Welcome page appears.

7 Click Next.The Create Enterprise Pool page appears.

8 Type a Pool Name (for example, allpool).

9 For Domain, type the domain name (for example,innlab.nortel.com).

10 For Pool FQDN, type the Fully Qualified Domain Name for thepool (for example, allpool.innlab.nortel.com).

11 For SQL Server Instance, type the SQL server and instancein the format <server>|<instance name> (for example,ocsdb1\msql2005).If only one instance is configured on the DB, the instance nameis not required.

12 Click Next.

13 For Internal Web Farm FQDN, enter the Fully Qualified DomainName in the format <pool name.domain> (for example,allpool.innlab.nortel.com).


NN49000-314 01.0124 April 2009


.


14 Click Next.

15 For Reuse Existing Database, select Replace any existingdatabase.

16 Click Next.The Locations for User Database page appears.

17 Select Next.The Meeting Content and Archive Location page appears.

18 For Meeting Content Location, type the path of the OCS 2007content folder (for example, \\rome\ocscontent).

19 For Meeting Metadata Location, type the path of the OCS 2007metadata folder (for example, \\rome\ocsmetadata).

20 Click Next.The Address Book Server page appears.

21 Type the path of the OCS 2007 Address Book folder (forexample, \\rome\ocsaddressbook).

22 Click Next.The Archive and Call Detail Recording page appears.

23 Click Next.The Ready to Create Enterprise Pool page appears.


25 Select the View the log when you click Finish check box.

26 Click Finish.



29 Back on the Deploy Enterprise Pool in a Consolidated Topologypage, for Configure pool, select Run.The Welcome page appears.

30 Click Next.

31 Click Next on the Administrative Tools page if it appears.If Administrative tools are not installed, the option to do soappears.

32 On the Server or Pool to Configure page, select the FQDN (forexample, allpool.innlab.nortel.com).

33 Click Next.The Load Balancer Configuration Parameters page appears.

34 Select SNAT mode.

35 Click Next.The SIP Domains page appears.


NN49000-314 01.0124 April 2009


.

Procedure steps 75

36 Ensure that the domain is already added (for example,innlab.nortel.com).

37 Click Next.The Client Logon Settings page appears.

38 Select the Some or all clients will use DNS SVR recordscheck box.

39 Select the Use this server or pool to authenticate andredirect automatic client logon request check box.

40 Click Next.The SIP Domains for Automatic Logon page appears.

41 Ensure that the SIP domain is supported by the server, or selectPool for automatic logon.

42 Click Next.The External User Access Configuration page appears.

43 Select the Do not configure external access now check box.

44 Click Next.The Ready to Configure Server or Pool Screen page appears.



47 Click Finish.



--End--


NN49000-314 01.0124 April 2009


.


Configuring OCS 2007 on the front-end servers

Perform this procedure to configure the OCS 2007 front-end servers.

Procedure steps

Step Action

1 Log on to the first OCS 2007 front-end server using domaincredentials.

ATTENTIONThe sequence in which you configure the front-end servers is thedefault sequence in which you use servers in your network.

2 Navigate to the installation directory for OCS 2007 (for example,E:\OCS2007), and double-click the setup.exe file.The Deployment Wizard page appears.


4 For Step 5: Add Servers to the Pool, select Run.The Welcome page appears.

5 Click Next.

6 If the License Agreement appears, agree to the terms and clickNext.The Location for Server Files page appears.

7 Choose the installation folder.

8 Click Next.The Ready to Install Components page appears.

9 Click Next.This can take several minutes to complete.The Select a Pool page appears.

10 Select the FQDN for the pool (for example, allpool.innlab.nortel.com).

11 Click Next.The Select Main Service Account page appears.

12 Create a new RTCService Account with a password if one doesnot yet exist.

13 Click Next.The Component Service Account page appears.

14 Create a new RTCComponentService Account with apassword if one does not yet exist.


NN49000-314 01.0124 April 2009


.

Procedure steps 77

15 Click Next.The Select Guest Account page appears.

16 Create a new RTCGuestAccessUser Account with a passwordif one does not yet exist.

17 Click Next.The Ready to Activate Components page appears.This can take several minutes to complete.The Completion page appears.


19 Click Finish.



22 Exit the Deployment Wizard.

23 Repeat this procedure for each front-end server in the network.

--End--


NN49000-314 01.0124 April 2009


.


Configuring and assigning server certificates to theOCS 2007 servers

Perform this procedure to assign certificates. Certificates are a keybuilt-in component of OCS 2007 and required for features that use securecommunications.

Procedure steps

Step Action

1 Log on to the OCS 2007 server that you configured usingdomain credentials.

2 Select Start, Run.

3 Type http://<issuing CA server>/certsrv.

4 Click OK.

5 For Select a task, select Download a CA certificate,certificate chain, or CRL.

6 Under Download a CA Certificate, certificate chain or CRL,select Download a CA certificate chain.

7 In the File Download dialog, click Save.

8 Save the .P7B file to the hard disk on the server.

9 Navigate to the OCS 2007 installation directory (for example,E:\OCS2007\Setup\i386), and double-click the setup.exe file.The Deployment Wizard page appears.


11 Click Run for Step 6: Configure Certificate to start theCommunication Certificate Wizard.The Welcome page appears.

12 Select Import a certificate chain from a .p7b file.

13 Click Next.The Import Certificate Chain page appears.

14 Click Browse to locate the .P7B file.

15 Select the .P7B file.

16 Click Next.

17 Click Finish.


NN49000-314 01.0124 April 2009


.

Procedure steps 79

18 In the Deploy Enterprise Pool in a Consolidated Topology page,click Run for Step 6: Configure Certificate.The Welcome page appears.

19 Click Next.The Available Certificate Tasks page appears.

20 Verify that Create a new certificate is selected.

21 Click Next.The Delayed or Immediate Request page appears.

22 Verify that Send the request immediately to an onlinecertification authority is selected.

23 Click Next.The Name and Security Settings page appears.

24 For the Name of the new certificate, verify that the OCS 2007Enterprise Edition front-end server host name is entered (forexample, OCSFRONTEND1).Ensure that the Bit length is 1024.

25 Clear the Mark cert as exportable check box.

26 Click Next.The Organization Information page appears.

27 For Organization, type the parent domain (for example,nortel.com).

28 For Organizational unit, type the organizational unit name (forexample, lab).

29 Click Next.The Your Server Subject Name page appears.

30 For Subject Name, verify that the FQDN is selected (forexample, allpool.innlab.nortel.com).

31 For Subject Alternate Name, verify that sip.<domain name> isselected (for example, sip.innlab.nortel.com).The Geographical Information page appears.

32 For Country/Region, select your country.

33 For State/Province, type your state or province.

34 For City/Locality, type your city.

35 Click Next.The Choose a Certification Authority page appears.

36 For Certification Authorities, verify that your Certification Authority is detected and listed (for example, rome.innlab.nortel.com).

37 Click Next.The Request Summary page appears.


NN49000-314 01.0124 April 2009


.


38 Verify the settings and then click Next.The Completion page appears.

39 Click Assign.

40 When you are prompted by the Communications CertificateWizard, click OK.The Completion page appears.

41 Click Finish.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 81

Assigning server certificates to the Web componenton the OCS 2007 servers

Perform this procedure to assign certificates to the OCS 2007 Webcomponent. Certificates are a key built-in component of OCS 2007 andrequired for features that use secure communications.

Procedure steps

Step Action

1 Select Start, Control Panel, Administrative Tools, ComputerManagement.

2 Expand Services and Applications, Internet InformationServices (IIS) Manager, Web Sites.

3 Right-click Default Web Site and select Properties.

4 Click the Directory Security tab.

5 Under Secure communications, click Server Certificate.The Welcome to the Web Server Certificate Wizard pageappears.

6 Click Next.

7 Click Assign an existing certificate.

8 Click Next.

9 Select the certificate that you requested using the CertificateWizard, assuming that the certificate matches the name of theWeb Components Server or pool.

10 Click Next.The SSL Port page appears.

11 Verify that SSL uses port 443.

12 Click Next.

13 Review the certificate details, and then click Next to assign thecertificate.

14 Click Finish to exit.

15 Click OK to close the Default Web Site Properties page.

--End--


NN49000-314 01.0124 April 2009


.


Verifying replication

Perform this procedure to complete the necessary checks to both OCS2007 front-end servers.

Procedure steps

Step Action

1 Log on to each OCS 2007 front-end server (for example,OCSFRONTEND1 and OCSFRONTEND2) using domaincredentials.


3 Type cmd.

4 Click OK.The DOS window appears.


6 To verify replication on an OCS 2007 Enterprise Edition server,enter the following command:

LcsCmd /server /action:CheckLCServerState /role:ee/PDCRequired:FALSE

7 Open the HTML log file created by the command.The HTML file location appears on the command line.

8 Open the HTML document and click Expand All in theupper-right corner. Verify that the result of each task is Success.

--End--


NN49000-314 01.0124 April 2009


.

83.

Starting OCS 2007 servicesThe procedures in this chapter describe how to start OCS 2007 services,validate the installation, and force a synchronization of the Address Bookserver database on each OCS 2007 front-end server.


NN49000-314 01.0124 April 2009


.

84 Starting OCS 2007 services

OCS 2007 services configuration procedures

This task flow shows the sequence of tasks you need to perform tostart OCS 2007 services. To link to any procedure, go to “OCS servicesconfiguration navigation” (page 85).

Figure 9OCS services configuration procedures


NN49000-314 01.0124 April 2009


.

OCS services configuration navigation 85

OCS services configuration navigation• “Starting the OCS 2007 server” (page 87)

• “Configuring routes on the OCS 2007 front-end servers” (page 88)

• “Creating a location profile” (page 90)

• “Creating phone usages, policies, and routes” (page 91)

• “Installing the Mediation Server” (page 93)

• “Configuring a Mediation Server certificate” (page 95)

• “Configuring the Mediation Server” (page 98)

• “Starting the Mediation Server” (page 100)

• “Installing the proxy server” (page 101)

• “Activating the proxy server” (page 102)

• “Configuring the server certificate for the proxy server” (page 103)


NN49000-314 01.0124 April 2009


.


• “Configuring the proxy server” (page 105)

• “Installing the Multimedia Convergence Manager (MCM)” (page 107)

• “Configuring permissions for the MCM” (page 109)

• “Configuring the MCM” (page 110)


NN49000-314 01.0124 April 2009


.

Procedure steps 87

Starting the OCS 2007 server

Perform this procedure to start the OCS 2007 server.

Procedure steps

Step Action

1 Log on to the OCS 2007 front-end server using domaincredentials.

2 Navigate to the installation directory for OCS 2007 anddouble-click the setup.exe file.The Deployment Wizard page appears.


4 For Step 9: Start Services, select Run.This may take several minutes to complete.The Welcome to the Start Services Wizard appears.

5 Click Next.A list of services appears.

6 Review the list of services and click Next.


8 Click Finish.


--End--


NN49000-314 01.0124 April 2009


.


Configuring routes on the OCS 2007 front-endservers

Perform this procedure to configure routes on the OCS 2007 front-endservers.

Procedure steps

Step Action

1 Log on to the second OCS 2007 front-end server using domaincredentials.

2 Select Start, All Programs, Administrative Tools, OfficeCommunications Server 2007 to launch the OCS 2007Management Console.

3 In the left pane, select Forest, Enterprise Pools, AllPool.

4 Right-click the Front Ends folder and select Properties.The Front End properties page appears.

5 Select the Routing tab.

6 Click the Add button.The Add Static Route page appears.

7 For Domain, type your Active Directory domain.

8 Select IP address and type the IP address of the MCM/Proxyserver.

9 For Transport, select TCP.

10 Ensure that Port is set to 5060.

11 Click OK.

12 Select the Host Authorization tab.

13 Click the Add button.The Add Authorized Host page appears.

14 Select IP address and type the IP address of the MCM/Proxyserver.

15 Select the Throttle As Server check box.

16 Select the Treat As Authenticated check box.

17 Click OK.

18 In the Front End Properties window, click Apply and then OK.

19 Expand the Front Ends folder.

20 Select and right-click the first OCS 2007 front-end server in thepool, and select Properties.


NN49000-314 01.0124 April 2009


.

Procedure steps 89

21 Select the General tab.

22 In the Connections area click the Add button.The Add Connection page appears.

23 For IP Address, select All.

24 Ensure that the Port is configured as 5060.


26 Click OK.

27 Repeat Step 20 through Step 26 for each server in the pool.

28 In the Front End Properties window, click Apply and then OK.

--End--


NN49000-314 01.0124 April 2009


.


Creating a location profile

Perform this procedure to create a location profile.

Procedure steps

Step Action


2 Select Start, Programs, Administrative Tools, OfficeCommunications Server 2007.

3 Right-click Forest and select Properties, Voice Properties.The Voice Properties page appears.

4 Select the Location Profiles tab.

5 Click Add.

6 For Location Profile, enter a name and description.

7 Click Add in the Normalization Rules area.The Add Normalization Rule page appears.

8 Type a meaningful name and description for the newnormalization rule.

9 Enter the Phone pattern and Translation pattern expressionthat apply to your dialing plans. For more information, clickHelper.

10 Enter a Sample dialed number to test your translation.

11 Click OK.

12 Click OK to close the Add Location Profile page and apply thechanges.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 91

Creating phone usages, policies, and routes

Perform this procedure to create phone usages, policies, and routes.

Procedure steps

Step Action


2 Select Start, Programs, Administrative Tools, OfficeCommunications Server 2007.

3 Right-click Forest and select Properties, Voice Properties.The Voice Properties page appears.

4 Select the Phone Usages folder.

5 Click Add.

6 Type a meaningful name and description for the new usagerecord.

7 Click OK.

8 Select the Policy.

9 For Global Policies, select Default Policy.

10 In the Defined Policies list, select the Default Policy and clickEdit.

11 Ensure that the Allow Simultaneous Ringing of Phones checkbox is selected.

12 For Phone Usages, select Default Usage.

13 Click Configure.The Configure Phone Usage Records page appears.

14 Select Default Usage from the Available list and then select the> button to add it to the Configured list.

15 Click OK.

16 Click OK to apply the changes to the policy.

17 Select the Routes tab.

18 Click the Add button.The Add Route page appears.

19 Type a meaningful name and description for the route.

20 For Target Regular Expression, type an expression thatmatches your dial plan (for example, [\d\d\d\d]).For more information, click the Helper button.


NN49000-314 01.0124 April 2009


.


21 In the Gateways pane, click the Add button.The Add Route Gateway page appears.

22 Select the FQDN for your mediation server and click OK.

23 Click the Configure button.The Configure Phone Usage Records page appears.

24 Select Default Usage from the Available list, and then click the> button to add it to the Configured list.

25 Click OK.

26 Click OK to apply the changes to the route.

27 Click OK to apply the changes to the server voice properties.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 93

Installing the Mediation Server

Perform this procedure to install the Mediation Server, which provides localsignaling and codec translation services for Microsoft Office Communicator(OC) clients.

Procedure steps

Step Action

1 Log on to the OCS 2007 Mediation Server using domaincredentials.

2 Navigate to the installation directory for OCS 2007 (for example,E:\OCS2007\Setup\I386).

3 Double-click setup.exe.The Deployment Wizard page appears.

4 Click Deploy Other Server Roles.The Deploy Other Server Roles page appears.

5 Click Deploy Mediation Server.The Deploy Mediation Server page appears.

6 Select Install for Step 1: Install files for Mediation Server.The Welcome page appears.

7 Click Next.

8 If the License Agreement appears, agree to the terms and selectNext.

9 In the Location for Server Files page, choose the installationfolder.

10 Click Next.The Confirm Installation page appears.

11 Click Next.This can take several minutes to complete. The InstallationComplete page appears.

12 Click Close.

13 In the Deploy Mediation Server page, select Run for Step 2:Activate Mediation Server.The Welcome page appears.

14 Click Next.The Select Service Account page appears.

15 Select Use An Existing Account.

16 Enter a Password for the account.


NN49000-314 01.0124 April 2009


.


17 Click Next.The Ready to Activate Mediation Server page appears.



20 Click Finish.

21 Switch to the Deployment Log and click Expand All in theupper-right hand corner.


23 Exit the Deployment window.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 95

Configuring a Mediation Server certificate

Perform this procedure to configure and assign a server certificate to theMediation Server.

Procedure steps

Step Action

1 Log on to the Mediation Server that you configured using domaincredentials.


3 Type http://<issuing CA server>/certsrv.

4 Click OK.


6 Under Download a CA Certificate, certificate chain or CRL,select Download a CA certificate chain.

7 In the File Download dialog, click Save.

8 Save the .P7B file to the hard disk on the server.

9 Navigate to the OCS 2007 installation directory (for example,E:\OCS2007\Setup\i386) and double-click the setup.exe file.The Deployment Wizard page appears.


11 Click Deploy Other Server Roles.

12 Click Deploy Mediation Server.The Deploy Mediation Server page appears.

13 Click Run for Step 4: Configure Certificate.The Welcome page appears.


15 Select Import a certificate chain from a .p7b file.

16 Click Next.The Import Certificate Chain page appears.

17 Click Browse to locate the .P7B file.

18 Select the .P7B file.

19 Click Next.


NN49000-314 01.0124 April 2009


.


20 Click Finish.

21 In the Deploy Mediation Server page, click Run for Step 4:Configure Certificate.The Welcome page appears.


23 Verify that Create a new certificate is selected.

24 Click Next.The Delayed or Immediate Request page appears.

25 Verify that Send the request immediately to an onlinecertification authority is selected.

26 Click Next.The Name and Security Settings page appears.

27 For the Name of the new certificate, verify that the OCS 2007Enterprise Edition Mediation Server name is entered.Keep the Bit length as 1024.

28 Clear the Mark cert as exportable check box.

29 Click Next.The Organization Information page appears.

30 For Organization, type the parent domain (for example,nortel.com).

31 For Organizational unit, type the organizational unit name (forexample, lab).

32 Click Next.The Your Server’s Subject Name page appears.

33 For Subject Name, verify that the FQDN is selected (forexample, allpool.innlab.nortel.com).

34 For Subject Alternate Name, verify that sip.<domain name> isselected (for example, sip.innlab.nortel.com).The Geographical Information page appears.

35 For Country/Region, select your country.

36 For State/Province, type your state or province.

37 For City/Locality, type your city.

38 Click Next.The Choose a Certification Authority page appears.

39 For Certification Authorities, verify that your Certification Authority is detected and listed (for example, rome.innlab.nortel.com).



NN49000-314 01.0124 April 2009


.

Procedure steps 97

41 Verify the settings and then click Next.The Completion page appears.

42 Click Assign.

43 When prompted by the Communications Certificate Wizard, clickOK.The Completion page appears.

44 Click Finish.

--End--


NN49000-314 01.0124 April 2009


.


Configuring the Mediation Server

Perform this procedure to configure the Mediation Server.

Procedure steps

Step Action

1 Log on to the OCS 2007 Mediation Server using domaincredentials.

2 Select Start, Administration Tools, Office CommunicationsServer 2007.

3 Expand the appropriate forest node.

4 Expand the Mediation Servers node.

5 Right-click the Mediation Server to be configured and selectProperties.


7 Verify that the FQDN matches that of the one given to theMediation Server you selected.


9 Type cmd.The command prompt window appears.

10 Type nslookup <FQDN of Mediation Server>, using the FQDNdisplayed in the General tab from Step 6.

11 For Communication Server Listening IP Address, type theIP address returned when you configured the Mediation Servercertificate.

12 For Gateway listening IP address, select the other IP address(that is, the one not already selected in Step 11).

13 From the A/V Edge Server list, select the A/V Edge Server thathosts the A/V Authentication Service for this Mediation Server.

14 For Default Location Profile, select the default location profilefor the Mediation Server.

15 Verify that the default Media Port Range is 60000 to 64000.

16 Select the Next Hop Connections tab.

17 For FQDN, select the FQDN of the pool.

18 Verify that the Port is set to the default port of 5061 for TLS.

19 For PSTN Gateway Next Hop Address, type the IP address ofthe PSTN Gateway to be associated with the Mediation Server


NN49000-314 01.0124 April 2009


.

Procedure steps 99

(that is, the SIP Proxy Server/SIP Redirect Server or node IPaddress).

ATTENTIONThe Mediation Server uses the SIP Proxy Server or SIP RedirectServer to negotiate with the NRS.

20 For Port, accept the default of 5060 for TCP.

21 Click OK.

--End--


NN49000-314 01.0124 April 2009


.


Starting the Mediation Server

Perform this procedure to start the Mediation Server.

Procedure steps

Step Action

1 Log on to an OCS 2007 front-end server using domaincredentials.

2 Select Start, Administrative Tools.

3 Select Office Communications Server 2007.

4 Expand the Mediation Servers node.

5 Right-click on the appropriate Mediation Server and select Start.

6 Click Start, Run.

7 Type services.msc.

8 Verify that Office Communications Server Mediation appearsin the list of services.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 101

Installing the proxy server

Perform this procedure to installing the proxy server.

Procedure steps

Step Action

1 Log on to the server intended for the OCS 2007 proxy serverusing your domain credentials.

2 Select Start, Run and enter cmd.

3 Navigate to the OCS 2007 installation directory (for example,E:\OCS2007\Setup\I386\setup).

4 At the command prompt, enter server.msi SERVER=PROXYSKU=EE.The Proxy Setup Wizard appears.

5 Click Next.

6 Accept the License Agreement and click Next.

7 Type your Username and Organization if necessary, and clickNext.

8 Accept the default location for the proxy files and click Next.The Confirmation page appears.

9 Click Next.The installation process begins. This process can take severalminutes.

10 When the Installation Complete page appears, click Close.

--End--


NN49000-314 01.0124 April 2009


.


Activating the proxy server

Perform this procedure to activate the proxy server.

Procedure steps

Step Action

1 Log on to the OCS 2007 proxy server using domain credentials.

2 Select Start, Run and enter cmd.

3 Navigate to the OCS 2007 installation directory (for example,E:\OCS2007\Setup\I386\setup).

4 At the command prompt, enter lcscmd /server /password:<password>/action:activate /role:proxy, where <password> is yourdesired proxy server password.

5 Verify that the status message “Action completed successfully”appears at the end of the script.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 103

Configuring the server certificate for the proxyserver

Perform this procedure to configuring and assign the server certificate forthe proxy server.

Procedure steps

Step Action


2 Select Start, Run and enter http://<name of issuing CAServer>/certsrv.


4 For Download a CA Certificate, Certificate Chain, or CRL,select Download CA certificate chain.A File Download dialog appears.

5 Click Save and save the .p7b file to the hard disk on the server.

6 Select Start, Programs, Administrative Tools, ComputerManagement.

7 Expand Services and Applications in the left pane.

8 Right-click Microsoft Office Communications Server 2007 andselect Certificates.The Certificates Wizard appears.


10 Select Import a certificate chain from a .p7b file and clickNext.The Import Certificate Chain page appears.

11 Select Browse to locate the .p7b file, locate the file and clickNext.

12 Click Finish.

13 Right-click Microsoft Office Communications Server 2007 andselect Certificates.The Certificates Wizard appears.


15 Select Create a new certificate and click Next.The Delayed or Immediate Request page appears.


NN49000-314 01.0124 April 2009


.


16 Select Send the request immediately to an onlinecertification authority and click Next.The Name and Security Settings page appears.

17 Verify that the proxy server Name is configured for the newcertificate.

18 Ensure that the bit length is 1024.

19 Clear the Mark cert as exportable check box, and then clickNext.The Organization Information page appears.

20 Type the name of your Organization (for example, nortel.com).

21 Type the name of your Organizational unit (for example, lab).

22 Click Next.

23 For Subject Name, verify that ocsproxy.innlab.nortel.com isselected.

24 For Subject Alternate Name, verify that sip.innlab.nortel.comis selected.

25 Click Next.The Geographical Information page appears.

26 Select your Country/Region.

27 Select your State/Province.

28 Select your City/Locality.

29 Click Next.The Choose a Certification Authority (CA) page appears.

30 For Certification Authorities, verify that your CertificationAuthority is detected and listed.In the network example in this guide, a root CA is configured onthe domain controller, so rome.innlab.nortel.com is configuredautomatically.


32 Verify the settings and click Next.The Completion page appears.

33 Click Assign.The Communications Certificate Wizard appears.

34 Click OK.

35 Click Finish.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 105

Configuring the proxy server

Perform this procedure to configure the proxy server.

Procedure steps

Step Action


2 Select Start, Programs, Administrative Tools, ComputerManagement.

3 Expand Services and Applications in the left pane.

4 Right-click Microsoft Office Communications Server 2007 andselect Properties.


ATTENTIONIf you are using protocols not specified in this document, ensure thatyou select the appropriate protocols here.

6 In the Connections area, click Add.The Add Connections page appears.

7 For IP Address, select All.

8 Ensure that the Port is the default 5060.


10 Click OK.

11 Select the Host Authorization tab.

12 Click Add.

13 Select IP Address and enter the IP address of the NRS/SRSserver.

14 Select the Throttle As Server check box.

15 Select the Treat As Authenticated check box.

16 Click OK.

17 Repeat steps 13 to 16 for the OCS 2007 front-end servers,Gateway server listening IP address of the Mediation Server,Communication Server 1000 listening IP address of theMediation Server, proxy/MCM server, and the CommunicationServer 1000 node IP.

18 Click OK to close the Properties dialog box and apply thechanges.


NN49000-314 01.0124 April 2009


.


19 Right-click Microsoft Office Communications Server 2007 andselect Start.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 107

Installing the Multimedia Convergence Manager(MCM)

Perform this procedure to install the Multimedia Convergence Manager(MCM).

ATTENTIONUC Campus Solution uses the Multimedia Convergence Manager (MCM) andConverged Office as a gateway between Communication Server 1000 and OCS2007. With this configuration, you can use all of the Nortel Converged Officeservices. However, UC Campus also supports using the Communication Server1000 as a direct PSTN gateway to OCS 2007 without MCM and ConvergedOffice. This procedure is required only if you use MCM.

Procedure steps

Step Action

1 Log on to the server intended for the Multimedia ConvergedManager server using your domain credentials.

2 Navigate to the installation directory for the MCM software (forexample, D:\MCM Setup\).

3 Double-click the setup.exe file to launch the installer.The Welcome page appears.

4 Click Next.

5 Select the folder location in which to install the MCM files, andclick Next.The MCM Information page appears.

6 Click Next.The Confirm Installation page appears.

7 Click Next.The MCM Service Account page appears.

8 Select Create a new account.

9 For Account Name, select the default of MCMService.

10 Choose a password for the account.

ATTENTIONBy default, the passwords for RTCComponentService,RTCGuestAccessUser, RTCProxyService, and RTCService usersautomatically reset in 90 days.

11 Click OK.The installation continues.


NN49000-314 01.0124 April 2009


.


12 When the Installation Complete page appears, click Close.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 109

Configuring permissions for the MCM

Perform this procedure to configuring permissions for the MCM.

Procedure steps

Step Action

1 Log on to the Multimedia Convergence Manager server usingdomain credentials.

2 Select Start, Settings, Control Panel, Administrative Tools,Computer Management.

3 Select System Tools, Local Users and Groups, Groups.

4 Double-click the RTC Server Applications group.

5 Click Add.

6 Click Advanced.

7 Click Find Now.

8 In the search results, locate and select the MCMService userand click OK.

9 Click OK.

10 Double-click the RTC Server Local Group group.

11 Click Add.

12 Click Advanced.

13 Click Find Now.

14 In the search results, locate and select the MCMService userand click OK.

15 Click OK.

--End--


NN49000-314 01.0124 April 2009


.


Configuring the MCM

Multimedia Convergence Manager (MCM) is a software component thatNortel provides to enable voice connectivity between CS 1000 clients andthe Office Communications Server (OCS) 2007 clients. MCM enables SIPVoIP connectivity between the CS 1000 and the Office CommunicationsServer 2007 and TR/87 authorization functionality required for the OfficeCommunicator (OC) 2007 Remote Call Control capability.

MCM consists of the following modules:

• Call Processing Service – handles the Session Initiation Protocol (SIP)telephony traffic between the Communication Server 1000 and theOffice Communications Server.

• Management Console – provides real-time status of the MCM, OfficeCommunications Server, Primary Network Routing Service (NRS), andSecondary NRS. It also provides Administrative, Maintenance, andConfiguration tools.

Telephones on a Communication Server 1000E system can make directSIP calls to OCS clients when the dialed number maps to a correspondinguser’s Line URI using LDAP queries to the corporate Active Directory.MCM also allows Office Communications Server clients to originate ESNand trunk calls to corporate and external users.

For information on MCM architecture, call flow, and menu options,see Nortel Converged Office Fundamentals — Microsoft OfficeCommunications Server 2007 (NN43001-121) .

Perform the following procedure to configure MCM.

Procedure steps

Step Action

1 Log on to the Multimedia Convergence Manager server usingdomain credentials.

2 Select Start, Programs, Multimedia Convergence Manager tostart the Multimedia Convergence Manager application.

3 In the Multimedia Convergence Manager application, selectTools, Configuration.

4 In the Network Topology area, for Call Server, select CS 1000.

5 Depending on your deployment, select SRS, SPS, or DirectConnect.


NN49000-314 01.0124 April 2009


.

Procedure steps 111

6 Perform one of the following steps:

• If you selected SRS or SPS, enter the Primary IP,Secondary IP, Registration ID, Registration IP, and, ifapplicable, the Mode.

• If you selected Direct Connect, enter the CS 1000 SIP GWIP.

ATTENTIONIf the SIP domain for OCS 2007 does not match the SIP servicedomain for NRS, you must include @<service domain name>.

7 Select the Mediation Server check box.

8 Select Routing Table.

9 In the Mediation Routing Table, click Add.

10 Enter the Mediation Pool Identifier, Location, and MediationServer IP, and click Add.Repeat this step for any additional Mediation Servers in the pool.

ATTENTIONThe Mediation Pool Identifier is the same as the sip-gw-id header ofthe Call Server.

11 Click OK.

12 Click OK to return to the Configuration page.

13 In the Active Directory Configuration area, select Query Server.

14 For Incoming Call Processing Parameters, enter your selectedCalled Phone Context (for example, CDP.UDP).

15 In the Network Dial Plan area, select the Dial Plan for yourdeployment and the Access Code, if applicable.

16 Ensure that you select the Enable RCC Authorization checkbox in the SIP-CTI Authorization area.

17 Click OK.

18 Click Actions.

19 Select Start.

20 Ensure the status of the MCM and OCS 2007 Proxy areRunning and that the Primary SPS/SRS status is Active.

--End--


NN49000-314 01.0124 April 2009


.



NN49000-314 01.0124 April 2009


.

113.

Configuring Active Directory andOffice Communicator

The procedures in this chapter describe how to configure OCS 2007user accounts in Active Directory and how to install Microsoft OfficeCommunicator Client 2007 (OCC 2007) on client devices.


NN49000-314 01.0124 April 2009


.

114 Configuring Active Directory and Office Communicator

Active Directory and Office Communicatorconfiguration procedures

This task flow shows the sequence of tasks you need to perform toconfigure OCS 2007 Active Directory and Office Communicator. Tolink to any procedure, go to “Active Directory and Office Communicatorconfiguration navigation” (page 115).


NN49000-314 01.0124 April 2009


.

Active Directory and Office Communicator configuration navigation 115

Figure 10Active Directory and Office Communicator configuration procedures

Active Directory and Office Communicator configuration navigation• “Configuring Active Directory user accounts” (page 117)

• “Configuring the Active Directory user server” (page 118)


NN49000-314 01.0124 April 2009


.


• “Installing Office Communicator” (page 119)

• “Configuring the OCC 2007 calling device” (page 120)


NN49000-314 01.0124 April 2009


.

Procedure steps 117

Configuring Active Directory user accounts

Perform this procedure to configure OCS 2007 user accounts in ActiveDirectory to help integrate OCS 2007 clients with the CommunicationServer 1000 system.

Procedure steps

Step Action

1 Using an account in the Domain Admins group, log on toan OCS 2007 server or another server joined to an ActiveDirectory domain that has the Office Communications ServerAdministration Tools installed.

2 Select Start, Run and enter dsa.msc.

3 Expand your SIP domain.

4 Right-click Users or another folder in which to create users,select New, and click User.

5 Perform the steps in the New Object - User Wizard.

6 Right-click the new user to enable it for Office CommunicationsServer, and select Properties.

7 Click the Communications tab.

8 Select the Enable user for Office Communications Servercheck box.

9 For Specify Sign-in Name, type the SIP address in the formatsip:username@domain.

10 For Server or Pool, select the Enterprise pool.

11 After you configure the user, click Apply, and then OK.

--End--


NN49000-314 01.0124 April 2009


.


Configuring the Active Directory user server

Perform this procedure to configure the OCS 2007 user server in ActiveDirectory.

Procedure steps

Step Action

1 Using an account in the Domain Admins group, log on toan OCS 2007 server or another server joined to an ActiveDirectory domain that has the Office Communications ServerAdministration Tools installed.

2 Select Start, Run and enter dsa.msc.

3 Expand your domain.

4 Right-click a User and select Properties.

5 Click the Communications tab.

6 Click Configure.The User Options page appears.

7 Select the Enable Enterprise Voice check box.

8 Select the Enable PBX Integration check box.

9 For Server URI, specify the URI for your application in thefollowing format:SIP:<DN>;phone-context=<dialing domain>@<servicedomain> , where dialing domain = CS 1000 L1 or L0 domainsas defined on Communication Server 1000 NRS. L0 is used forCDP and L1 is used for UDP.

10 For Line URI, enter a dummy telephone number and configurethe correct user extension in the format tel:+yyyyyyyyyyy;ext=xxxx (for example, tel:+15066744000;ext=5000).

ATTENTIONYou must also apply the chosen numbering plan to the TLSV andMCM configurations.

11 Click OK.

12 Click OK to close the User Properties window.

--End--


NN49000-314 01.0124 April 2009


.

Procedure steps 119

Installing Office Communicator

Perform this procedure to install Microsoft Office Communicator 2007(OCC 2007) clients on client devices.

Procedure steps

Step Action

1 Download and open Communicator.msi.

2 On the Welcome to Microsoft Office Communicator 2007 Setuppage, click Next.

3 Review the license agreement, select I accept the terms in theLicense Agreement, and then click Next.

4 Accept the default installation directory, or click Browse andnavigate to another directory.

5 Click Next.

6 Click Finish.

7 Open Microsoft Office Communicator 2007.

8 In the top left corner of the window, select Tools, Options.

9 Click the Personal tab.

10 Type the sign-in address for this SIP user and click Advanced.

11 Select Manual configuration. For both Internal server name orIP address and External server name or IP address, type theserver name (for example, allpool.innlab.nortel.com).

12 For Connect using, select TLS.

13 Click OK.

14 Ensure that you are signed into Communicator.If you are not signed in, close the Option tab and sign in.

15 From the left corner of Office Communicator, select Options.

16 Select the Phones tab.

17 Select the Enable Integration with your phone system checkbox to integrate OCC 2007 with your desktop phone.

18 Click OK to close the Options window and apply the changes.

--End--


NN49000-314 01.0124 April 2009


.


Configuring the OCC 2007 calling device

Perform this procedure to change the preferred OCC 2007 calling device.

ATTENTIONPBX control is required to change these settings.

Procedure steps

Step Action

1 Select Start, Programs, Microsoft Office Communicator 2007to start OCC 2007.

2 Select Tools.

3 Select Call Forward Settings.The Call Forwarding Settings page appears.

4 For My preferred calling device, select either Phone orComputer.

5 Click OK to apply the changes.

--End--


NN49000-314 01.0124 April 2009


.

Nortel Unified Communications Campus Solution

Configuration — Unified CommunicationsCopyright © 2008 Nortel NetworksAll Rights Reserved.

Printed in Canada and the United States of AmericaRelease: 1.0Publication: NN49000-314Document revision: 01.01Document release date: 24 April 2009

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

www.nortel.comLEGAL NOTICE

While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writingNORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESSOR IMPLIED. The information and/or products described in this document are subject to change without notice.

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

All other trademarks are the property of their respective owners.

Nortel Unified Communications Campus Solution Conﬁguration ...

Documents