Escolar Documentos
Profissional Documentos
Cultura Documentos
NN49000-309
.
Document status: Standard
Document version: 01.01
Document date: 7 April 2008
Sourced in Canada
LEGAL NOTICE
While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed
to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY
KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject
to change without notice.
Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks.
Microsoft, MS, MS-DOS, Windows, and Windows NT are trademarks of Microsoft Corporation.
All other trademarks are the property of their respective owners.
3
Contents
How to get help 5
Finding the latest updates on the Nortel Web site 5
Getting help from the Nortel Web site 5
Getting help over the phone from a Nortel Solutions Center 5
Getting help from a specialist by using an Express Routing Code 6
Getting help through a Nortel distributor or reseller 6
About this document 7
Audience 7
Related information 7
Overview 9
Integration prerequisites 10
Integration tasks 20
Navigation 21
CS 1000 system configuration 25
Call Server configuration prerequisites 25
Call Server configuration procedures 25
Configuring SIP channel resources, phones, and PCA 25
Configuring the CS 1000 system 30
NAS configuration 43
NAS configuration prerequisites 45
NAS configuration procedures 45
Configuring NAS VLAN 2 45
Configuring NAS uplink ports 46
Disabling NAS STP 47
Configuring the NAS layer 3 Gateway interfaces 47
Configuring OCS 2007 real server IP addresses 48
Configuring OCS 2007 real servers for VLAN and port assignment on NAS 49
Configuring the new group and adding real servers 50
Configuring a NAS virtual IP address for public access to the OCS 2007 front-end
pool 51
Adding additional services to the virtual group 51
Configuring NAS SLB ports for client and server processing 52
Enabling NAS SLB service 53
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
4 Contents
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
5
www.nortel.com/support
Outside North America, go to the following Web site to obtain the phone
number for your region:
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
6 How to get help
www.nortel.com/callus
www.nortel.com/erc
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
7
Audience
The intended audience for this document includes installation, planning,
and maintenance personnel.
Related information
The following NTPs are referenced in this guide:
• Communication Server 1000E: Installation and Configuration
(553-3041-210)
• Communication Server 1000M and Meridian 1: Large System
Installation and Configuration (553-3021-210)
• Communication Server 1000M and Meridian 1: Small System
Installation and Configuration (553-3011-210)
• Communication Server 1000S: Installation and Configuration
(553-3031-210)
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
8 About this document
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
9
Overview
This document describes the integration of a Communication Server 1000
(CS 1000) PBX system with Microsoft Office Communication Server 2007
(OCS 2007) Enterprise Edition. In this document, OCS 2007 is deployed in
a single Forest topology using a single domain model within Active Directory.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
10 Overview
Figure 1
CS 1000/OCS 2007 network topology
Integration prerequisites
• You have basic programming and provisioning skills for the CS 1000.
Nortel recommends that you complete product-specific training before
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Integration prerequisites 11
Table 1
Pre-integration checklist
Task Reference Comments
CS 1000
The Enterprise software Ensure that the system has
package is purchased and adequate licenses for the
installed, with appropriate number of required SIP ports,
licenses for virtual trunks, PCA, SIP CTI TR87, and
lines, and IP Phones as AST.
required.
Verify that PCA is enabled. To check that PCA is
enabled:
1 Connect to the Call Server.
2 Enter LD 21.
3 Enter PRT at the REQ
prompt.
4 Enter FTR at the TYPE
prompt.
5 Enter the customer number
at the CUST prompt.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
12 Overview
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Integration prerequisites 13
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
14 Overview
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Integration prerequisites 15
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
16 Overview
Table 2
Integration parameters worksheet
Parameter Example Value
Active Directory Server
Active Directory schema innlab.nortel.com
Active Directory forest innlab.nortel.com
Active Directory domain innlab.nortel.com
SQL Server
Server FQDN ocsdb1.innlab.nortel.com
IP address 192.167.140.42
OCS 2007 servers
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Integration prerequisites 17
Table 3
OCS 2007 communications
Service Protocol Port(s) Description
DNS UDP/TCP 53 Used for name
resolution.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
18 Overview
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Integration prerequisites 19
Table 4
Windows Messenger and Office Communicator client communications
Service Protocol Port(s) Description
TCP Mode TCP 5060 The client listens on a
dynamic port for SIP
traffic. The client sends
data to the default port
of the server. The
default port of the
server is 5060.
TLS Mode TCP 5061 The client listens over
the same connection
that is open to the
server.
By default, the server
listens on port 5061
(TCP). The server
sends to the client only
over the client’s TLS
session.
Whiteboard and TCP 1503 The Whiteboard and
Application Sharing Application Sharing
components of
Windows Messenger
use the T.120 protocol.
The port used is
fixed and cannot be
changed.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
20 Overview
Integration tasks
This work flow shows you the sequence of tasks you perform to integrate
the CS 1000 system with OCS 2007.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Integration tasks 21
Figure 2
CS 1000/OCS 2007 integration process
Navigation
The tasks in the CS 1000/OCS 2007 integration process are listed in Table
5 "Task completion checklist" (page 21). Use this checklist to implement
the integration.
Table 5
Task completion checklist
Task Reference
CS 1000 system configuration 1. "Configuring SIP channel resources, phones, and
PCA" (page 25)
2. "Configuring the CS 1000 system" (page 30)
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
22 Overview
Task Reference
NAS configuration 1. "Configuring server VLAN and uplink ports and
disabling STP" (page 46)
2. "Configuring L3 interfaces " (page 47)
3. "Configuring real server IPs" (page 49)
4. "Configuring the group" (page 50)
5. "Configuring SLB ports for client/server processing
" (page 52)
6. "Configuring a public virtual IP address" (page 51)
7. "Turning on SLB" (page 53)
8. "Applying and saving configuration changes" (page
53)
9. "Verifying services" (page 54)
Local site configuration 1. "Preparing the Active Directory schema, forest and
domain" (page 57)
2. "Preparing the back-end database" (page 59)
3. "Configuring OCS 2007 on the front-end servers"
(page 63)
4. "Verifying replication" (page 68)
5. "Starting services and forcing Address Book
synchronization " (page 68)
Client configuration 1. "Configuring user accounts" (page 89)
2. "Installing OCC 2007" (page 93)
Testing 1. "Call scenario 1" (page 98)
2. "Call scenario 2" (page 98)
3. "Call scenario 3" (page 99)
4. "Call scenario 4" (page 100)
5. "Call scenario 5" (page 101)
Troubleshooting 1. "Running AML traces" (page 103)
2. "Running DCH traces" (page 104)
3. "Running SIP CTI traces" (page 105)
4. "Running SIP call traces" (page 105)
5. "Capturing MCM logs" (page 106)
6. "Running OCS 2007 Application Proxy traces" (page
106)
7. "Running OCS 2007 Mediation Server traces" (page
107)
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Integration tasks 23
Task Reference
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
24 Overview
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
25
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
26 CS 1000 system configuration
2 Enter LD 17.
Table 6
LD 17 - Configuring the ELAN and VAS IDs
Prompt Response Description
REQ CHG
TYPE ADAN
ADAN NEW ELAN xx Where xx is the next available
number, 32–127
CTYP ELAN
DES a..a Enter a relevant description (for
example, ELAN1).
REQ CHG
TYPE VAS
VAS NEW
VSID xx Enter the number entered for
the ELAN ID above.
ELAN xx Enter the number entered for
the ELAN ID above.
SECU YES
5 To view the new ELAN, enter LD 22. Enter PRT at the REQ prompt,
then ADAN.
A list of all provisioned IDs appears. Use the capture text function in
hyperterminal to save a text file of the output.
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring SIP channel resources, phones, and PCA 27
—End—
Table 7
LD 11 - Provisioning a telephone
Prompt Response Description
REQ NEW Creates a new telephone entry.
TYPE 2004p2
TN aaa.bbb.ccc.ddd Terminal Number, where
a=loop, b=shelf, c=card slot,
d=card channel (0-31)
Example: 66 0 0 10
IP Phones require a VGMC
card. The TNs you configure for
IP Phones are virtual circuits.
Digital and analog telephones
require a digital or analog card.
The TN must be an available
TN.
DES OCSTST Enter a relevant description for
the telephone entry.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
28 CS 1000 system configuration
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring SIP channel resources, phones, and PCA 29
Table 8
LD 11 - Provisioning PCA
Prompt Response Description
REQ NEW Creates a new telephone entry.
TYPE PCA
TN aaa.bbb.ccc.ddd Terminal Number, where
a=loop, b=shelf, c=card slot,
d=card channel (0-31)
Example: 66 0 0 10
PCA is considered a virtual
circuit. The TN must be an
available TN.
DES OCSPCA Enter a relevant description for
the telephone entry.
CUST xx Customer number (for example,
0).
ZONE xx Zone number (for example, 1.
CLS T87D PCAM Do not configure CLS as CDMV
or CDMO. This would cause
the users to be treated as MCS
users.
KEY 0 SCR xxxx Enter the line number of the
telephone, where xxxx is the
phone number to associate
with as in the phone just
created. This is the SCR. It will
automatically assign the MARP
to that phone (for example,
7600).
KEY 1 HOT p x yyyy Where x represents the number
of digits for distance steering
code it is pointing at and yyyy is
the configured distance steering
code (for example, 4100).
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
30 CS 1000 system configuration
2 Enter LD 43.
3 Enter EDD.
—End—
3 Select Add route for the customer number you want to use.
4 Configure the parameters for the route as shown in the table below.
Table 9
Route configuration parameters
Parameter 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: 1117
The route is for a virtual trunk route (VTRK) Enable
Zone for codec selection and bandwidth Type a relevant zone for your system.
management (ZONE) Example: 2
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring the CS 1000 system 31
Parameter 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 Enable
(ISDN)
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 Select your dialing plan.
(CTYP) Example: CDP or UDP
SIGO ESN5
5 Click Submit.
6 On the newly created route, click Add trunk.
The Trunk Property Configuration page appears.
7 Configure the parameters for the trunk as shown in the table below.
Table 10
Trunk configuration parameters
Parameter Value
Multiple trunk input number (MTINPUT) Select the number of trunks to add.
This creates a number of TN trunks. Ensure that
you have enough unused TNs in a span to cover
this number of trunks.
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.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
32 CS 1000 system configuration
Parameter Value
Route number, Member number (RTMB) Type the route number and trunk start.
The route number is the one in which you are
creating the TN. The member number is the
trunk you are creating.
Example: 5 1
Card Density (CDEN) Select the card density type.
Example: 8D
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 Member
number (yes), several TNs are created
depending on the values of the MTINPUT and
TN parameters.
8 Click Save.
—End—
5 For Please enter route list index, enter a new valid RLB number
(for example, 3).
6 Click outside the Please enter route list index box to activate the
Add button, and then click the Add button.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring the CS 1000 system 33
8 Click Submit.
—End—
Table 11
Distant Steering Code parameters
Parameter Value
Flexible Length number of digits (FLEN) This is the number of digits the system expects to
receive before accessing a trunk and outpulsing
these digits. Type a value between 0 and 10.
Display (DSP) Select the Directory Number to be used for CLID
(DN).
Route List to be accessed for trunk steering code Select the RLI number created.
(RLI) Example: 3
6 Click Submit.
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
34 CS 1000 system configuration
3 In the Node configuration area, click Edit for the node you wish to
modify.
4 Expand the SIP GW Settings heading.
Table 12
SIP Gateway parameters
Parameter Value
Primary Proxy or Redirect (TLAN) IP address Type the IP address of your NRS or SIP
proxy/redirect server.
Port Type the SIP port number (usually 5060 by
default).
Supports Registration Enable
Primary Proxy or Redirect server flag Enable
Transport Protocol TCP
—End—
2 Configure the SIP URI Map parameters as shown in the table below.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring the CS 1000 system 35
Table 13
SIP URI Map parameters
Parameter Value
Public E.164/National domain name Type the public E.164/National domain for your
system.
Example: +1
Public E.164/Subscriber domain name Type the Public E.164/Subscriber domain name
for your system.
Example: +1506
Public E.164/Unknown domain name Type the Public E.164/Unknown domain name
for your system.
Example: PublicUnknown.
This parameter is optional.
Public E.164/Special Number domain name Type the Public E.164/Special Number domain
name for your system.
Example: PublicSpecial.
This parameter is optional.
Private/UDP domain name Type the Private/UDP domain name for your
system.
Example: UDP
Private/CDP domain name Type the Private/CDP domain name for your
system, including the DP domain name.
Example: CDP.UDP
Private/Special Number domain name Type the Private/Special Number domain name
for your system.
Example: PrivateSpecial
This parameter is optional.
Private/Unknown (vacant number routing) Type the Private/Unknown domain name for your
domain name system.
Example: PrivateUnknown
This parameter is optional.
Unknown/Unknown domain name Type the Unknown/Unknown domain name for
your system.
Example: UnknownUnknown
This parameter is optional.
3 Configure the SIP URI Map settings for your secondary proxy or
redirect server, if applicable.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
36 CS 1000 system configuration
—End—
Table 14
SIP CTI services parameters
Parameter Value
Service Enabled Enable
You must reboot the Signaling Server for the
enabling of SIP CTI to take effect. A system
reboot takes the Signaling Server out of service.
Reboot during a time that will not impact service.
Support TLS Enpoints Only Disable
Customer Number Type the number used for the customer.
Example: 0
Maximum Associations per DN Select a number between 1 and 10.
Place International Calls Within This Country As Enable if applicable.
National Calls
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.
Subscriber Prefix Enter number according to your dialing plan.
Dialing Plan Select the dialing plan for your engineered
system.
Example: CDP
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring the CS 1000 system 37
Parameter Value
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.
3 Configure the SIP CTI services settings for your secondary proxy
or redirect server, if applicable.
—End—
Table 15
Signaling Server parameters
Parameter Value
Enable IP Peer Gateway (Virtual Trunk TPS) Select H.323 and SIP.
Selecting both H.323 and SIP allows for a dual
network and takes H.323 into consideration, if
you use devices requiring that protocol.
Enable SIP proxy/Redirect Server Enable only if using co-resident NRS.
Local SIP TCP/UDP port to listen to Type the default SIP port number (usually 5060).
Ensure that this value coordinates with your end
devices.
SIP Domain name Type the SIP domain name to be used throughout
the system configuration.
Example: convergedoffice.com
SIP Gateway Endpoint Name Type the Gateway endpoint name to be
registered in the NRS.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
38 CS 1000 system configuration
Parameter Value
SIP Gateway Authentication Password If you enable security and use authentication in
the NRS when creating endpoints, the password
entered here is used for the authentication.
Enable Gatekeeper Enable
Network Service Role Issue only if using co-resident NRS. Options are
Primary, Alternate, and Failsafe.
—End—
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring the CS 1000 system 39
5 For E.164 country code, enter the E.164 country code for your
system.
6 For E.164 area code, enter the E.164 area code for your system.
—End—
2 Click Add.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
40 CS 1000 system configuration
6 For E.164 area code, enter the E.164 area code for your system.
7 Configure other optional parameters as required for your system.
8 Click Save.
—End—
8 For H.323 support, select H.323 not supported for the MCM
gateway endpoints.
9 For SIP support, select Dynamic SIP endpoint.
10 For SIP transport, enable the transport protocol type for TCP.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring the CS 1000 system 41
12 Click Save.
—End—
3 Select the Endpoint for which you want to add a route and click Add.
4 Select the DN Type.
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
42 CS 1000 system configuration
2 Select Database.
4 Click Commit.
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
43
NAS configuration
This section demonstrates the configuration of NAS to enable Microsoft
Office Communication Server (OCS) 2007 front-end server load balancing.
In the examples in this section, two front-end servers are configured. You
must include any additional front-end servers in the NAS configuration as
well.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
44 NAS configuration
Figure 3
OCS 2007 single site topology
The procedures in this section assume that the connection of the terminal
and console port is established. The default logon password is admin. In
these procedures, NAS is configured using the command line interface
(CLI) configuration tool.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring NAS VLAN 2 45
Step Action
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
46 NAS configuration
2 When prompted to confirm changing the PVID for VLAN ports, enter
y.
The system responds:
Port 9 is an UNTAGGED port and its current PVID
is 1.
Confirm changing PVID from 1 to 2 [y/n]: y
Port 10 is an UNTAGGED port and its current PVID
is 1. Confirm changing PVID from 1 to 2 [y/n]: y
Current ports for VLAN 2: empty
Pending new ports for VLAN 2: 9
Current ports for VLAN 2: empty
Pending new ports for VLAN 2: 9 10
Current ports for VLAN 2: empty
Pending new ports for VLAN 2: 9 10
—End—
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring the NAS layer 3 Gateway interfaces 47
Step Action
1 Disable STP.
Syntax:
/c/l2/stg 1/off
The system responds:
Current Spanning Tree 1 setting: ON
New Spanning Tree 1 setting: OFF
—End—
Step Action
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
48 NAS configuration
Syntax:
/c/l3/if 2/add [layer 3 IP for vlan 2]/mask
[subnet mask]/vlan 2/en/apply
Example:
/c/l3/if 2/add 192.167.130.1/mask
255.255.255.0/vlan 2/en/apply
The system responds:
Current IP address: 0.0.0.0
New pending IP address: 192.167.130.1
Pending new subnet mask: 255.255.255.0
Current subnet mask: 0.0.0.0
New pending subnet mask: 255.255.255.0
Current VLAN: 1
New pending VLAN: 2
Current status: disabled
New status: enabled
—End—
Step Action
1 Configure the IP address for the first OCS 2007 front-end server.
Syntax:
/c/slb/real 1/rip [real ip of ocs frontend
server #1]/ena/name “[relevant description for
entry]”/tmout 30
Example:
/c/slb/real 1/rip 192.167.130.40/ena/name
“OCSFRONTEND1”/tmout 30
The system responds:
Current real server IP address: 0.0.0.0
New pending real server IP address:
192.167.130.40
Current status: disabled
New status: enabled
Current real server name:
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring OCS 2007 real servers for VLAN and port assignment on NAS 49
2 Configure the IP address for the second OCS 2007 front-end server.
Syntax:
/c/slb/real 2/rip [real ip of ocs frontend
server #2]/ena/name “[relevant description for
entry]”/tmout 30
Example:
/c/slb/real 2/rip 192.167.130.41/ena/name
“OCSFRONTEND2”/tmout 30
The system responds:
Current real server IP address: 0.0.0.0
New pending real server IP address:
192.167.130.41
Current status: disabled
New status: enabled
Current real server name:
New real server name: OCSFRONTEND2
Current timeout: 10
New pending timeout: 30
—End—
Configuring OCS 2007 real servers for VLAN and port assignment
on NAS
Perform the procedure below to configure VLAN 2 and port assignments
for the real servers.
Step Action
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
50 NAS configuration
Syntax:
/c/slb/real 2/ids/idsvlan 2/idsport [port you have
OCS front end server #2 plugged into]
Example:
/c/slb/real 2/ids/idsvlan 2/idsport 10
Note: These commands do not prompt a response from the
system. To display all pending changes, including the last
commands entered, enter the diff command.
—End—
Step Action
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Adding additional services to the virtual group 51
Step Action
—End—
Step Action
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
52 NAS configuration
Syntax:
/c/sl/virt 1/service [service port number]/gr 1
The system responds:
Current real server group: 1
New pending real server group: 1
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Applying and saving configuration changes 53
—End—
1 Enable SLB.
Syntax:
/c/sl/on
The system responds:
Current status: OFF
New status: ON
—End—
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
54 NAS configuration
Verifying services
Step Action
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
55
You can configure and deploy OCS 2007 using either the command line
interface (CLI) or the guided user interface (GUI) configuration tool accessed
through the setup.exe file. This document demonstrates the configuration
of OCS 2007 using the GUI configuration tool.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
56 Local site configuration
an OCS 2007 component is not supported. SQL Server 2000 SP4 and
SQL Server 2005 SP1 are supported.
• Windows Script Hosting 5.6 is installed on the server where the
back-end database is to be installed.
• The Fully Qualified Domain Name (FQDN) of each server is correct.
Check that FQDNs are correct by pinging each host.
Note: Changing the FQDN of an OCS component after deployment
is not supported.
• No applications are using ports 5060 and 5061. These ports are used to
send SIP communications.
• Microsoft .NET Framework 2.0 is installed on the OCS 2007 servers.
The OCS 2007 configuration tool checks for Microsoft .NET Framework
and provides the option to install it.
Note: The Microsoft .NET Framework is also included on the OCS
2007 DVD.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Preparing the Active Directory schema, forest and domain 57
Step Action
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, and
then click Finish.
12 Switch to the Deployment Log and click Expand All in the upper-right
corner. Verify that each task’s result is Success.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
58 Local site configuration
14 Click Next.
The Select System Container in the Root Domain page appears.
15 Click Next.
The Location of Universal Groups page appears.
18 Verify that the SIP domain is selected in the Select SIP domain
menu.
19 Click Next.
The Ready to Prepare Forest page appears.
20 Click Next.
The Completion page appears.
21 Select the View the log when you click Finish check box, and
then click Finish.
22 Switch to the Deployment Log and click Expand All in the upper-right
corner. Verify that each task’s result is Success.
23 Select Step 5: Prep Current Domain and click Run.
This may 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.
26 Click Next.
The Completion page appears.
27 Select the View the log check box.
28 Click Finish.
29 Switch to the Deployment Log and click Expand All in the upper-right
corner.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Preparing the back-end database 59
32 Click Back.
Notice that Step 1: Prepare Active Directory appears. Complete.
33 From the domain controller, select Start > Run and enter explorer.
The domain controller will contain content for the OCS 2007 system
using these file directory shares.
—End—
Step Action
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
60 Local site configuration
10 For Pool FQDN, type the Fully Qualified Domain Name for the pool
(for example, allpool.innlab.nortel.com).
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Preparing the back-end database 61
11 For SQL Server Instance, type the SQL server and instance in the
format <server>|<instance name> (for example, ocsdb1\msql2005).
If only one instance is configured on the DB, the instance name
is not required.
12 Click Next.
13 For Internal Web Farm FQDN, enter the Fully Qualified Domain
Name in the format <pool name.domain> (for example,
allpool.innlab.nortel.com).
14 Click Next.
15 For Reuse Existing Database, select Replace any existing
database.
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 2007
content folder (for example, \\rome\ocscontent).
19 For Meeting Metadata Location, type the path of the OCS 2007
metadata 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 (for example,
\\rome\ocsaddressbook).
22 Click Next.
The Archive and Call Detail Recording page appears.
23 Click Next.
The Ready to Create Enterprise Pool page appears.
24 Click Next.
The Completion page appears.
25 Select the View the log when you click Finish check box.
26 Click Finish.
27 Switch to the Deployment Log and click Expand All in the upper-right
corner.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
62 Local site configuration
33 Click Next.
The Load Balancer Configuration Parameters page appears.
34 Select SNAT mode.
35 Click Next.
The SIP Domains page appears.
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 records check
box.
45 Click Next.
The Completion page appears.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring OCS 2007 on the front-end servers 63
47 Click Finish.
48 Switch to the Deployment Log and click Expand All in the upper-right
corner.
—End—
1 Log onto the first OCS 2007 front-end server using domain
credentials.
Note: The sequence in which the front-end servers are
configured is the default sequence in which the servers are used
in your network.
6 If the License Agreement appears, agree to the terms and click Next.
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.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
64 Local site configuration
11 Click Next.
The Select Main Service Account page appears.
13 Click Next.
The Component Service Account page appears.
15 Click Next.
The Select Guest Account page appears.
20 Switch to the Deployment Log and click Expand All in the upper-right
corner.
21 Verify that each task’s result is Success.
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring OCS 2007 on the front-end servers 65
4 Click OK.
13 Click Next.
The Import Certificate Chain page appears.
16 Click Next.
17 Click Finish.
19 Click Next.
The Available Certificate Tasks page appears.
20 Verify that Create a new certificate is selected.
21 Click Next.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
66 Local site configuration
23 Click Next.
The Name and Security Settings page appears.
24 For the Name of the new certificate, verify that the OCS 2007
Enterprise Edition front-end server host name is entered (for
example, OCSFRONTEND1).
Keep the Bit length as 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).
30 For Subject Name, verify that the FQDN is selected (for example,
allpool.innlab.nortel.com).
31 For Subject Alternate Name, verify that sip.<domain name> is
selected (for example, sip.innlab.nortel.com).
The Geographical Information page appears.
35 Click Next.
The Choose a Certification Authority page appears.
37 Click Next.
The Request Summary page appears.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring OCS 2007 on the front-end servers 67
39 Click Assign.
41 Click Finish.
—End—
1 Select Start > Control Panel > Administrative Tools > Computer
Management.
13 Review the certificate details, and then click Next to assign the
certificate.
14 Click Finish to exit.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
68 Local site configuration
—End—
Verifying replication
Perform the procedure below to complete the necessary checks to both
OCS 2007 front-end servers.
Step Action
3 Type cmd.
4 Click OK.
The DOS window appears.
8 Open the HTML document and click Expand All in the upper-right
corner. Verify that each task’s result is Success.
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Starting services and forcing Address Book synchronization 69
1 Log onto the OCS 2007 front-end server using domain credentials.
2 Navigate to the installation directory for OCS 2007 and double-click
the setup.exe file.
The Deployment Wizard page appears.
8 Click Finish.
9 Switch to the Deployment Log and click Expand All in the upper-right
corner. Verify that each task’s result is Success.
—End—
1 Log onto the second OCS 2007 front-end server using domain
credentials.
2 Select Start > All Programs > Administrative Tools > Office
Communications Server 2007 to launch the OCS 2007
Management Console.
3 In the left-hand pane, select Forest > Enterprise Pools > AllPool.
4 Right-click the Front Ends folder and select Properties.
The Front End properties page appears.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
70 Local site configuration
Figure 4
Add Static Route
11 Click OK.
12 Select the Host Authorization tab.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Starting services and forcing Address Book synchronization 71
Figure 5
Add Authorized Host
17 Click OK.
18 In the Front End Properties window, click Apply and then OK.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
72 Local site configuration
26 Click OK.
28 In the Front End Properties window, click Apply and then OK.
—End—
1 Log onto the first OCS 2007 front-end server using domain
credentials.
11 Click OK.
12 Click OK to close the Add Location Profile page and apply the
changes.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Starting services and forcing Address Book synchronization 73
—End—
1 Log onto the first OCS 2007 front-end server using domain
credentials.
2 Select Start > Programs > Administrative Tools > Office
Communications Server 2007.
5 Click Add.
6 Type a meaningful name and description for the new usage record.
7 Click OK.
10 In the Defined Policies list, select the Default Policy and click Edit.
11 Ensure that the Allow Simultaneous Ringing of Phones check
box is selected.
14 Select Default Usage from the Available list and then select the >
button to add it to the Configured list.
15 Click OK.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
74 Local site configuration
25 Click OK.
26 Click OK to apply the changes to the route.
—End—
1 Log onto the OCS 2007 Mediation Server using domain credentials.
3 Double-click setup.exe.
The Deployment Wizard page appears.
7 Click Next.
9 In the Location for Server Files page, choose the installation folder.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Starting services and forcing Address Book synchronization 75
10 Click Next.
The Confirm Installation page appears.
11 Click Next.
This may take several minutes to complete. The Installation
Complete page appears.
12 Click Close.
17 Click Next.
The Ready to Activate Mediation Server page appears.
18 Click Next.
The Completion page appears
—End—
4 Click OK.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
76 Local site configuration
14 Click Next.
The Available Certificate Tasks 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.
19 Click Next.
20 Click Finish.
22 Click Next.
The Available Certificate Tasks page appears.
23 Verify that Create a new certificate is selected.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Starting services and forcing Address Book synchronization 77
24 Click Next.
The Delayed or Immediate Request page appears.
27 For the Name of the new certificate, verify that the OCS 2007
Enterprise 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).
33 For Subject Name, verify that the FQDN is selected (for example,
allpool.innlab.nortel.com).
34 For Subject Alternate Name, verify that sip.<domain name> is
selected (for example, sip.innlab.nortel.com).
The Geographical Information page appears.
40 Click Next.
The Request Summary page appears.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
78 Local site configuration
42 Click Assign.
44 Click Finish.
—End—
1 Log onto the OCS 2007 Mediation Server using domain credentials.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Starting services and forcing Address Book synchronization 79
17 Verify that the Port is set to the default port of 5061 for TLS.
18 For PSTN Gateway Next Hop Address, type the IP address of the
PSTN Gateway to be associated with the Mediation Server (that is,
the SIP Proxy Server/SIP Redirect Server or node IP address).
Note: The Mediation Server uses the SIP Proxy Server/SIP
Redirect Server to negotiate with the NRS.
20 Click OK.
—End—
7 Type services.msc.
—End—
1 Log onto the server intended for the OCS 2007 proxy server using
your domain credentials.
2 Select Start > Run and enter cmd.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
80 Local site configuration
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 may take several
minutes.
—End—
1 Log onto the OCS 2007 proxy server using domain credentials.
2 Select Start > Run and enter cmd.
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Starting services and forcing Address Book synchronization 81
Configuring and assigning the server certificate for the proxy server
Step Action
1 Log onto the OCS 2007 proxy server using domain credentials.
2 Select Start > Run and enter http://<name of issuing CA
Server>/certsrv.
5 Click Save and save the .p7b file to the server’s hard disk.
6 Select Start > Programs > Administrative Tools > Computer
Management.
9 Click Next.
The Available Certificate Tasks page appears.
10 Select Import a certificate chain from a .p7b file and click Next.
The Import Certificate Chain page appears.
11 Select Browse to locate the .p7b file, locate the file and click Next.
12 Click Finish.
14 Click Next.
The Available Certificate Tasks page appears.
15 Select Create a new certificate and click Next.
The Delayed or Immediate Request page appears.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
82 Local site configuration
17 Verify that the proxy server Name is configured for the new
certificate.
22 Click Next.
25 Click Next.
The Geographical Information page appears.
29 Click Next.
The Choose a Certification Authority (CA) page appears.
30 For Certification Authorities, verify that your Certification Authority
is detected and listed.
In the network example in this guide, a root CA is configured on
the domain controller, so rome.innlab.nortel.com is configured
automatically.
31 Click Next.
The Request Summary page appears.
33 Click Assign.
The Communications Certificate Wizard appears.
34 Click OK.
35 Click Finish.
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Starting services and forcing Address Book synchronization 83
1 Log onto the OCS 2007 proxy server using domain credentials.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
84 Local site configuration
10 Click OK.
12 Click Add.
13 Select IP Address and enter the IP address of the NRS/SRS server.
16 Click OK.
17 Repeat Step 13 through Step 16 for the OCS 2007 front-end servers,
Gateway server listening IP address of the Mediation Server, CS
1000 listening IP address of the Mediation Server, proxy/MCM
server, and the CS 1000 node IP.
—End—
1 Log onto the server intended for the Multimedia Converged Manager
server using your domain credentials.
4 Click Next.
5 Select the folder location in which to install the MCM files, and click
Next.
The MCM Information page appears.
6 Click Next.
The Confirm Installation page appears.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Starting services and forcing Address Book synchronization 85
7 Click Next.
The MCM Service Account page appears.
11 Click OK.
The installation continues.
—End—
3 Select System Tools > Local Users and Groups > Groups.
4 Double-click the RTC Server Applications group.
5 Click Add.
6 Click the Advanced button.
9 Click OK.
11 Click Add.
12 Click the Advanced button.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
86 Local site configuration
14 In the search results, locate and select the MCMService user and
click OK.
15 Click OK.
—End—
11 Click OK.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Starting services and forcing Address Book synchronization 87
15 In the Network Dial Plan area, select the appropriate Dial Plan for
your deployment, and Access Code if applicable.
17 Click OK.
18 Click Actions.
19 Select Start.
20 Ensure the status of the MCM and OCS 2007 Proxy are Running
and that the Primary SPS/SRS status is Active.
Figure 7
Multimedia Convergence Manager Configuration
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
88 Local site configuration
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
89
Client configuration
This section describes the steps to configuring Microsoft Office
Communication Server 2007 (OCS 2007) clients to integrate with the
Communication Server 1000 (CS 1000) system.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
90 Client configuration
Figure 8
User Properties
9 For Specify Sign-in Name, type the SIP address in the format
sip:username@domain.
10 For Server or Pool, select the Enterprise pool.
11 When you are finished configuring the user, click Apply, then OK.
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring Active Directory 91
6 Click Configure.
The User Options page appears.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
92 Client configuration
Figure 10
User Options
9 For Server URI, specify the URI for your application in the following
format:
SIP:<DN>;phone-context=<dialing domain>@<service domain>
, where dialing domain = CS 1000 L1 or L0 domains as defined on
CS 1000 NRS. L0 is used for CDP and L1 is used for UDP.
Example for UDP:
sip:5015000;phone-context=udp@innlab,nortel.com.
10 For Line URI, enter a dummy telephone number with
the proper extension for the user being configured, in
the format tel:+yyyyyyyyyyy;ext=xxxx (for example,
tel:+15066744000;ext=5000).
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring OCC 2007 clients 93
Note: You must also apply the chosen numbering plan to the
PCA and MCM configurations.
11 Click OK.
12 Click OK to close the User Properties window.
—End—
3 Review the license agreement, and then select I accept the terms
in the License Agreement and click Next.
5 Click Next.
6 Click Finish.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
94 Client configuration
Figure 11
Advanced Connection Settings
13 Click OK.
14 Ensure that you are signed into Communicator.
If you are not signed in, close the Option tab and then sign in.
17 Select the Enable Integration with your phone system check box
to integrate OCC 2007 with your desktop phone.
18 Click OK to close the Options window and apply the changes.
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Configuring OCC 2007 clients 95
—End—
Figure 13
PBX control
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
96 Client configuration
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
97
Testing
This section verifies the successful integration of Microsoft Office
Communication Server 2007 (OCS 2007) with the Communication Server
1000 (CS 1000) system.
There are five basic Microsoft Office Communicator Client 2007 (OCC
2007) call scenarios that can be tested to ensure that the speech path
between OCS 2007 and the CS 1000 system is correct. The setup for these
tests is shown in the table below.
Table 16
Call scenarios
OCC 2007 in Phone mode OCC 2007 in Computer mode
(client B) (client B)
IP Phone (telephone A) x x
OCC 2007 in Phone mode x x
(client A)
OCC 2007 in Computer mode x
(client A)
Testing prerequisites
• One physical IP Phone
• Two PCs with OCC 2007 clients installed (clients A and B).
• Ensure that the system has PBX Call Control to configure the
Communicator clients to run in Phone or Computer mode.
Testing procedures
• "Call scenario 1" (page 98)
• "Call scenario 2" (page 98)
• "Call scenario 3" (page 99)
• "Call scenario 4" (page 100)
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
98 Testing
Call scenario 1
Perform the procedure below to test a call between two OCC 2007 clients
configured in Computer mode.
The purpose of this test is to prove that the signaling between two converged
OCC 2007 clients (clients A and B) is functioning properly and a two-way
speech path can be established for these clients.
Step Action
4 Click OK.
—End—
Call scenario 2
Perform the procedure below to test a call between an IP Phone and an
OCC 2007 client configured in Computer mode.
The purpose of this test is to prove that the signaling between the IP Phone
and the converged OCC 2007 client is functioning properly and a two-way
speech path can be established for the call.
Step Action
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Call scenario 3 99
4 Click OK.
5 From the IP Phone, place a call to the OCC 2007 client.
Result: On the OCC 2007 client, an incoming call notification
message appears.
—End—
Call scenario 3
Perform the procedure below to test a call between an IP Phone and an
OCC 2007 client configured in Phone mode.
The purpose of this test is to prove that the signaling between the IP Phone
(telephone A) and the telephone associated with the unconverged OCC
2007 client (telephone B) is functioning properly and a two-way speech
path can be established for the call.
Step Action
5 From the IP Phone (telephone A), place a call to the OCC 2007
client.
Result: On the OCC 2007 client, an incoming call notification
message appears.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
100 Testing
—End—
Call scenario 4
Perform the procedure below to test a call between two OCC 2007 clients
configured in Phone mode.
The purpose of this test is to prove that the signaling between the
telephones (telephones A and B) associated with two unconverged OCC
2007 clients (clients A and B) is functioning properly and a two-way speech
path can be established for the call.
Step Action
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Call scenario 5 101
Call scenario 5
Perform the procedure below to test a call between an OCC 2007 client
configured in Computer mode and an OCC 2007 client configured in Phone
mode.
The purpose of this test is to prove that the signaling between the
converged OCC 2007 client (client A) and the telephone associated with
the unconverged OCC 2007 client (client B) is functioning properly and a
two-way speech path can be established for the call.
Step Action
4 Click OK.
5 Log into OCC 2007 on client B.
8 Click OK.
9 From client A, enter the phone number of client B and select Click
to call.
Result: On client B, an incoming call notification message appears.
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
102 Testing
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
103
Troubleshooting
This section describes how to collect system logs for troubleshooting
purposes.
Troubleshooting procedures
• "Running AML traces" (page 103)
• "Running DCH traces" (page 104)
• "Running SIP CTI traces" (page 105)
• "Running SIP call traces" (page 105)
• "Capturing MCM logs" (page 106)
• "Running OCS 2007 Application Proxy traces" (page 106)
• "Running OCS 2007 Mediation Server traces" (page 107)
• "Running OCS 2007 front-end server traces" (page 108)
Step Action
2 Enter LD 48.
3 Enable the incoming messages for the ELAN (for example, ENL
MSGI <link #>).
4 Enable the outgoing messages for the ELAN (for example, ENL
MSGO <link #>).
5 Exclude the incoming polling messages for the ELAN link and
specify the priority (for example, ENXI MSGI <link #><Priority>).
Refer to the table below for Priority values.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
104 Troubleshooting
6 Exclude the outgoing polling messages for the ELAN link and specify
the priority (for example, ENXO MSGI <link #><Priority>).
Refer to the table below for Priority values.
—End—
Priority Description
1 System priority messages
2 Signaling priority messages
3 Call processing priority messages
4 Administration priority messages
Step Action
2 Enter LD 96.
3 Set the monitor output level for all incoming messages on the
D-channel (for example, SET MSGI <D-channel #> MON <Priority>).
Refer to the table below for Priority values.
Note: By default, if you do not specify the Priority level, it is set
to 0. Level 0 is easier to read, while level 2 provides more detail.
4 Set the monitor output level for all outgoing messages on the
D-channel (for example, SET MSGO <D-channel #> MON
<Priority>).
5 Enable the incoming messages for the D-channel (for example, ENL
MSGI <D-Channel #>).
6 Enable the outgoing messages for the D-channel (for example, ENL
MSGO <D-Channel #>).
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Running SIP call traces 105
Priority Description
0 Default value. Provides the lowest level
of detail.
1 Outputs the raw data.
2 Provides the highest level of details by
identifying the individual information
elements in the message and their
hexadecimal values.
Step Action
2 At the OAM prompt, enable the SIP tracing using the SIPCTITrace
command (for example, SIPCTITrace ON).
3 Set the trace level using the SIPCTITraceLevel command (for
example, SIPCTITraceLevel <Priority>).
Refer to the table below for Priority values.
—End—
Priority Description
0 Default summary view
1 Detailed view
Step Action
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
106 Troubleshooting
Priority Description
0 Default summary view
1 Detailed view
Step Action
6 To view the MCM logs, open the MCM.log file located in the directory
where MCM is installed.
—End—
Step Action
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Running OCS 2007 Mediation Server traces 107
14 Click Analyze.
—End—
Step Action
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
108 Troubleshooting
—End—
Step Action
4 Right-click the pool name for which you wish to capture logging (for
example, allpool) and select Logging Tool > New Debug Session.
The Office Communicator Server 2007 Logging tool appears.
5 In the Components area, select SIPStack.
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Running OCS 2007 front-end server traces 109
—End—
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
110 Troubleshooting
Enterprise: Common
Solution Integration Guide for Communication Server 1000 Release 5.0/Microsoft Office Communications
Server 2007
NN49000-309 01.01 Standard
Release 5.0 7 April 2008
Copyright © 2008, Nortel Networks
.
Enterprise: Common
Publication: NN49000-309
Document status: Standard
Document version: 01.01
Document date: 7 April 2008
Sourced in Canada
LEGAL NOTICE
While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing
NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR
IMPLIED. The information and/or products described in this document are subject to change without notice.
Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks.
Microsoft, MS, MS-DOS, Windows, and Windows NT are trademarks of Microsoft Corporation.
All other trademarks are the property of their respective owners.