Microsofr OCS

Enterprise: Common
Solution Integration Guide for

Communication Server 1000
Release 5.0/Microsoft Office
Communications Server 2007
NN49000-309
.
Document status: Standard
Document version: 01.01
Document date: 7 April 2008
Copyright © 2008, Nortel Networks

All Rights Reserved.
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
.
4 Contents
Applying and saving configuration changes 53

Verifying services 54
Local site configuration 55
Local site configuration prerequisites 55
Local site configuration procedures 56
Preparing the Active Directory schema, forest and domain 57
Preparing the back-end database 59
Configuring OCS 2007 on the front-end servers 63
Verifying replication 68
Starting services and forcing Address Book synchronization 68
Client configuration 89
Client configuration procedures 89
Configuring Active Directory 89
Configuring OCC 2007 clients 93
Testing 97
Testing prerequisites 97
Testing procedures 97
Call scenario 1 98
Call scenario 2 98
Call scenario 3 99
Call scenario 4 100
Call scenario 5 101
Troubleshooting 103
Troubleshooting procedures 103
Running AML traces 103
Running DCH traces 104
Running SIP CTI traces 105
Running SIP call traces 105
Capturing MCM logs 106
Running OCS 2007 Application Proxy traces 106
Running OCS 2007 Mediation Server traces 107
Running OCS 2007 front-end server traces 108
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
5
How to get help

This chapter explains how to get help for Nortel products and services.
Finding the latest updates on the Nortel Web site

The content of this documentation is current at the time of product release.
To check for updates to the latest documentation and software, go to the
Nortel Technical Support Web site:
www.nortel.com/support
Getting help from the Nortel Web site

The best way to get technical support for Nortel products is from the Nortel
Technical Support Web site:
www.nortel.com/support
This site provides quick access to software, documentation, bulletins, and
tools to address issues with Nortel products. From this site, you can:
• download software, documentation, and product bulletins
• search the Technical Support Web site and the Nortel Knowledge Base
for answers to technical issues
• sign up for automatic notification of new software and documentation
for Nortel equipment
• open and manage technical support cases
Getting help over the phone from a Nortel Solutions Center

If you do not find the information you require on the Nortel Technical Support
Web site, and you have a Nortel support contract, you can also get help
over the phone from a Nortel Solutions Center.
In North America, call 1-800-4NORTEL (1-800-466-7835).
Outside North America, go to the following Web site to obtain the phone
number for your region:
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
6 How to get help
www.nortel.com/callus
Getting help from a specialist by using an Express Routing Code

To access some Nortel Technical Solutions Centers, you can use an Express
Routing Code (ERC) to quickly route your call to a specialist in your Nortel
product or service. To locate the ERC for your product or service, go to:
www.nortel.com/erc
Getting help through a Nortel distributor or reseller

If you purchase a service contract for your Nortel product from a distributor
or authorized reseller, you can contact the technical support staff for that
distributor or reseller.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
7
About this document

This document describes the planning, configuration, and troubleshooting
of the integration of the Communication Server 1000 (CS 1000) system
with Microsoft Office Communications Server 2007 (OCS 2007) Enterprise
Edition services. OCS 2007 Enterprise Edition provides a highly extensible
platform to deliver Voice over IP (VoIP), instant messaging, video, and
collaboration tools for large-scale deployments supporting up to 50,000
users. Integrate OCS 2007 with CS 1000 when both systems have been
installed and a baseline of operation has been achieved and tested.
The following systems and software releases are covered in this guide:
• CS 1000 Release 5.0
• OCS 2007 Enterprise Edition
This document is intended to be a stand-alone guide, covering the

prerequisites to and implementation of a successful CS 1000/OCS 2007
integration. A minimum skill set and level of understanding are assumed.
References to other NTPs, engineering guides, or troubleshooting guides
are made for informational purposes.
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
Server 2007
NN49000-309 01.01 Standard
.
8 About this document
• Dialing Plans: Description (553-3001-183)

• IP Line Description, Installation, and Maintenance (553-3001-365)
• IP Peer Networking Installation and Configuration Guide (553-3001-213)
• IP Phones: Description, Installation, and Operation (553-3001-368)
• Keycode Installation Guide (NN40010-301)
• Signaling Server: Installation and Configuration (553-3001-212)
• Telephones and Consoles: Description, Installation, and Operation
(553-3001-367)
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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.
An example of a CS 1000/OCS 2007 network topology is shown in Figure 1

"CS 1000/OCS 2007 network topology " (page 10).
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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
Server 2007
NN49000-309 01.01 Standard
.
you begin the systems integration. A complete list of courses is available

at www.nortel.com.
• You are skilled in Microsoft Active Directory, Domain Name Service,
and DHCP services.
• A network health check is completed in the planning phase of the
integration, to ensure appropriate network bandwidth and identify the
protocols, payload size, and codecs to be used.
• A system baseline is established so that the CS 1000 and OCS 2007
systems are configured and working in a stand-alone environment. Use
Table 1 "Pre-integration checklist" (page 11) to complete the system
baseline.
• The services, protocols, and ports required for OCS 2007 network
communications are available. See Table 3 "OCS 2007 communications"
(page 17) and Table 4 "Windows Messenger and Office Communicator
client communications" (page 19).
• System parameters required to successfully complete the integration
are recorded. Record the parameters listed in Table 2 "Integration
parameters" (page 16) during the initial planning phase of the integration.
Complete the checklist below to ensure that your system baseline

requirements are met.
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
Server 2007
NN49000-309 01.01 Standard
.
12 Overview
6 Verify that the PCA

parameter is set to ON.
The Network Numbering Plan Dialing Plans: Description Are you using a Uniform
is implemented. (553- 3001-183) Dialing Plan (UDP) or a
Coordinated Dialing Plan
(CDP), or both?
Are you also using a Group
Dialing Plan (GDP), a
North American Numbering
Plan (NANP), or a Flexible
Numbering Plan (FNP)?
CS 1000 software is Release To check the CS 1000
5.0. software release:
Log on, enter LD 22, and
type PRT ISS.
OR
1 Log on to Element
Manager.
2 On the left navigation pane,
select Home.
The System Overview page
appears.
3 The software release is
referred to as Release.
Signaling Server software The Signaling Server
is Release 5.0, and all software should be the
required software patches most recent GA release
are installed. compatible with your Call
Server software version.
To check the software
release of the Signaling
Server:
1 Log on to Element
Manager.
select Home.
The System Overview page
appears.
3 Refer to the Signaling
Server Details section for the
Software Version.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.

Basic installation, setup, Communication Server
and configuration of the Call 1000M and Meridian 1:
Server components and Small System Installation and
the Signaling Server are Configuration (553-3011-210)
complete.
Communication Server
1000M and Meridian 1:
Large System Installation and
Configuration (553-3021-210)
1000S: Installation and
Configuration (553-
3031-210)
1000E: Installation and
Configuration (553-
3041-210)
Signaling Server: Installation
and Configuration (553-
3001-212)
Primary, alternate, and Signaling Server: Installation The NRS requires IP
fail-safe Network Routing and Configuration (553- telephony node configuration
Service (NRS) are configured 3001-212) files. These files are installed
at installation and initial setup and configured during the
of the Signaling Server. Signaling Server software
installation as a basic
configuration step.
Digital Data Block IP Peer Networking To configure a Digital Data
configuration is complete Installation and Configuration Block:
in LD 73. Guide (553-3001-213)
2 Enter LD 73.
3 Enter NEW.
4 Enter DDB.
5 Press Enter to accept all
defaults.
6 Perform a data dump.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
14 Overview

PTI or DTI trunks (DLOP) IP Peer Networking To check PTI or DTI trunks:
configuration is complete in Installation and Configuration
1 Log on to Element
LD 17. Guide (553-3001-213)
Manager.
2 Select Routes and Trunks
> Digital Trunk Interface.
3 Select Digital Trunk
Interface Data Block (DDB).
4 Check that the configuration
is complete.
The PTI or DTI trunks
configuration is a prerequisite
to a fully configured CS 1000
system communicating with
the outside world.
A basic node is configured in IP Line Description, This node information
Element Manager. Installation, and Maintenance is updated through the
(553- 3001-365) integration process.
Voice Gateway Media Card To check that Media Gateway
configuration is complete Cards are installed:
if IP to PSTN translation is
1 Log on to Element
required.
Manager.
2 On the left side navigation
pane, expand the System
tab.
3 Expand the Software tab.
4 Select Voice Gateway
Media Card.
The Voice Gateway Media
Card (VGMC) Loadware
Upgrade page appears.
5 Select Open all nodes.
Attention: The servers and
Media Cards installed and
configured are listed under
each node. Any installed
Voice Gateway Media Card
is listed under Type.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.

H.323 Virtual Trunk package To check that the package is
399 is installed. loaded:
2 Log on to the Signaling
Server.
3 Enter LD 22.
4 Enter PRT.
5 Enter PKG 399.
6 The package is loaded if
you do not receive a “package
is restricted” message.
IPT is Release 3.0 or newer if To check that IPT Trunk
you are using IP Trunk cards. cards are installed:
1 Log on to Element
Manager.
select System > IP Network
> Nodes: servers, Media
Cards.
4 Click Edit next to the
appropriate Node to display
a list of cards.
5 Expand the Card heading.
6 Expand listing for each
card and check the Card
Processor Type.
OCS 2007
OCS 2007 is deployed in a
test domain at the root level
and configured as a Central
Forest.
The SQL server is installed support.microsoft.com The SQL server must be SQL
as a domain user account Server 2000 SP4 or SQL
with local administrator Server 2005 SP1
permissions on the
server using Windows
authentication.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
16 Overview

OCS 2007 servers are When you create a pool,
connected together through the server is activated
a pool. when back-end services are
identified. Add additional
OCS 2007 servers to the pool
during installation activation.
An IP load balancer is The IP load balancer
installed. balances layer 4 TCP
traffic and route traffic away
from failed nodes in the
OCS 2007 pools. The IP
load balancer is not required
to decrypt Transport Layer
Security (TLS) or parse SIP
messages.
A dynamic DNS server is DNS host records are
available for the OCS 2007 applied to resolve the
domain. addresses of the OCS 2007
pools and enable client
connectivity for Microsoft
Office Communicator clients.
Office Communicator 2007
client is installed with all
required software patches
and hotfixes.
Use the worksheet below to record your system information to aid in

commissioning. Example values are provided to help you as you walk
through this document.
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
Server 2007
NN49000-309 01.01 Standard
.
Parameter Example Value

Pool FQDN for front-end server allpool.innlab.nortel.com
1
Server FQDN for front-end ocsfrontend1.innlab.nortel.com
server 1
IP address for front-end server 192.167.130.40
1
Pool FQDN for front-end server allpool.innlab.nortel.com
2
Server FQDN for front-end ocsfrontend2.innlab.nortel.com
server 2
IP address for front-end server 192.167.130.41
2
DNS entries
Virtual IP address (VIP) allpool.innlab.nortel.com
192.167.130.45
OCS 2007 backend database ocsdb1.innlab.nortel.com
192.167.140.42
OCS 2007 front-end server 1 ocsfrontend1.innlab.nortel.com
192.167.130.40
OCS 2007 front-end server 2 ocsfrontend2.innlab.nortel.com
192.167.130.41
DNS service (SRV) records
_sipinternal Protocol: TCP
Port: 5060
Host providing service:
allpool.innlab.nortel.com
_sipinternaltls Protocol: TCP
Port: 5061
Host providing service:
allpool.innlab.nortel.com
Table 3
OCS 2007 communications
Service Protocol Port(s) Description
DNS UDP/TCP 53 Used for name
resolution.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
18 Overview

HTTP TCP 80 For RPC over HTTP
to communicate
using the Windows
Messenger client.
Used for fetching
Certificate Revocation
Lists (CRLs).
Kerberos UDP 88 Used for authenticating
clients and users.
DCOM TCP 135 Used for installation
and management.
LDAP UDP/TCP 389 Used for fetching CRLs
and for Active Directory
access.
HTTPS TCP 443 SIP/TLS/PSOM/STUN
SQLSERVER UDP/TCP 1433 Microsoft default ports
for SQLSERVER.
SQL Monitor UDP/TCP 1434 Microsoft Default ports
for SQL Server Monitor.
STUN UDP 3478 STUN used for the A/V
edge server.
SIP TCP TCP 5060 The server listens on
this default fixed port for
SIP communications.
The client sends data
to the default port
of the server. This
is for less secure
communications. The
default port of the
server is 5060.
SIP TLS TCP 5061 By default, the server
listens on port 5061
(TCP). The server will
send to the client only
over the client’s secure
TLS session
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.

SIP MTLS TCP 5061 Used for server-to-serv
er connections.
Can also be used
by secure client
connection topologies.
This is the only
recommended, secure
SIP port.
RTP TCP 50,000–52,999 A/V edge server video
streams.
Table 4
Windows Messenger and Office Communicator client communications
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
Server 2007
NN49000-309 01.01 Standard
.
20 Overview

File Transfer TCP 6891–6900 The Windows
Messenger file transfer
protocol uses the Trivial
File Transfer Protocol
(TFTP) running over
TCP. The port range
is fixed and cannot be
changed.
Audio and Video UDP 1024–65535 Audio uses a pair
of User Datagram
Protocol (UDP) ports
for a Real-time Protocol
(RTP) stream to
transmit data.
Video uses Real-time
Transport Protocol
(RTCP) to control the
session stream.
By default, the ports
used are dynamic.
However, the ports can
be controlled through
Group Policy registry
settings.
Integration tasks
This work flow shows you the sequence of tasks you perform to integrate
the CS 1000 system with OCS 2007.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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
Server 2007
NN49000-309 01.01 Standard
.
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)
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
Server 2007
NN49000-309 01.01 Standard
.
Task Reference
8. "Running OCS 2007 front-end server traces" (page

108)
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
24 Overview
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
25
CS 1000 system configuration

This section describes the steps to configuring the Communication Server
1000 (CS 1000) Call Server for Microsoft Office Communication Server
2007 (OCS 2007).
Call Server configuration prerequisites

• The CS 1000 system has adequate licenses for the number of required
SIP ports, PCA, SIP CTI TR87, and AST.
• The CS 1000 Call Server is configured.
• The CS 1000 dialing plan is configured and working.
• A CS 1000 D-channel is configured and working.
• A CS 1000 Signaling Server node is installed and working.
• Network Routing Service (NRS) is enabled. NRS can be either SIP
Proxy Server (SPS) or SIP Redirect Server (SRS).
• You have Enterprise Common Manager logon access with administrator
privileges.
Call Server configuration procedures

• "Configuring SIP channel resources, phones, and PCA" (page 25)
• "Configuring the CS 1000 system" (page 30)
Configuring SIP channel resources, phones, and PCA

Perform the procedures below to configure SIP channel resources, user
telephones, and PCA on the CS 1000 using the command prompt.
Configuring a new ELAN ID and VAS ID (LD 17)

Step Action
Define and configure the ELAN ID for the AML link and its associated VAS
ID in the configuration record. Perform this procedure only if an ELAN ID
and VAS ID are not available.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
26 CS 1000 system configuration
2 Enter LD 17.
3 Enter the appropriate values as described in the following tables.

For prompts not listed in the following table, press Enter to accept
the default.
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
4 To exit the overlay, enter ****.
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—
Enabling the ELAN connection to the switch (LD 48)

Step Action

2 Enter LD 48.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
3 Enter ENL ELAN to enable the ELAN.
5 To view the status of the ELAN, enter STAT ELAN.
—End—
Provisioning a telephone for Converged Office

Step Action
The user telephone must be provisioned prior to the PCA, so that PCA is
associated with the telephone.
In the examples in this procedure, an i2004 model NTDU92 is configured.
For information about configuring other models, see IP Phones: Description,
Installation, and Operation (553-3001-368) and Telephones and Consoles:
Description, Installation, and Operation (553-3001-367).

2 Enter LD 11.

the default.
Table 7
LD 11 - Provisioning a telephone
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
Server 2007
NN49000-309 01.01 Standard
.

CUST xx Customer number (for example,
0).
ZONE xx Zone number (for example, 1).
CLS CDMR T87A Note: Do not configure CLS as
CDMV or CDMO. This would
cause the users to be treated
as MCS users.
AST xx SCR key location.
Usually 0, which is primary
location.
KEY 0 SCR xxxx Enter the line number of the
telephone, where xxxx is the
phone number.
Requires an available unused
number in the system (for
example, 7600).
Note: The numbers created for
OCS 2007 Converged Office
users must be routable in the
NRS dialing plan.
—End—
Provisioning a PCA to associate with the telephone

Step Action
A PCA must be configured with the same DN as the user in an MADN
arrangement. This offers incoming voice calls to the user’s DN on their OCC
2007 as well as any telephones configured with the same DN.

2 Enter LD 11.

the default.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Table 8
LD 11 - Provisioning PCA
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—
Saving the configuration

Step Action
Perform the procedure below to save any configuration changes.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
2 Enter LD 43.
3 Enter EDD.
—End—
Configuring the CS 1000 system

Perform the procedures below to configure the CS 1000 system. If you are
using an existing configuration, perform these procedures to confirm the
settings required for OCS 2007 Converged Office.
Configuring routes and trunks

Step Action
Perform the procedure below to configure routes and trunks for SIP
channels.
1 In Element Manager, expand the Routes and Trunks heading.

2 Select Routes and Trunks.
3 Select Add route for the customer number you want to use.
4 Configure the parameters for the route 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
Server 2007
NN49000-309 01.01 Standard
.
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
Server 2007
NN49000-309 01.01 Standard
.
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—
Configuring RLI (RLB)

Step Action
Perform the procedure below to configure an RLI for your SIP channels.
This coordinates with the route configured above. If you use an existing RLI,
perform this procedure to verify the data.
1 In Element Manager, 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 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
Server 2007
NN49000-309 01.01 Standard
.
7 For ROUT, select the route created in the procedure "Configuring

routes and trunks" (page 30) (for example, 5).
8 Click Submit.
—End—
Configuring a Distant Steering Code

Step Action
Perform the procedure below to configure a new Distant Steering Code
(DSC) for Converged Office. The DSC coordinates with the RLI configured
above.
1 In Element Manager, select Dialing and number plans > Electronic

Switched Network.
2 Select Coordinated Dialing Plan (CDP) > Distant Steering Code
(DSC).
3 Select Add to add a new DSC.

4 For Please enter a distant steering code, type a new DSC (for
example, 5505).
5 Configure the DSC parameters as shown in the table below.
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
Server 2007
NN49000-309 01.01 Standard
.
Configuring SIP Gateway Settings

Step Action
Perform the procedure below to configure your SIP Gateway settings. For
more information, see IP Peer Networking Installation and Commissioning
(NN43001-313).
1 In Element Manager, select System > IP Network.

2 Select Nodes: Server, Media Cards.
3 In the Node configuration area, click Edit for the node you wish to
modify.
4 Expand the SIP GW Settings heading.
5 Configure the SIP Gateway parameters as shown in the table below.

Complete the TLS Security options as required for your site.
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
6 Configure the SIP Gateway settings for your secondary proxy or

redirect server, if applicable.
—End—
Configuring the SIP URI Map

Step Action
Perform the following procedure to verify or configure the SIP URI Map. For
(NN43001-313).
1 Expand the SIP URI Map heading.
2 Configure the SIP URI Map parameters as shown in the table below.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Note: The SIP URI Map must be based on the network’s

engineered dial plan values and is unique to your network.
This document cannot provide examples for all possible
configurations.
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.
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
Private/Unknown (vacant number routing) Type the Private/Unknown domain name for your
domain name system.
Example: PrivateUnknown
Unknown/Unknown domain name Type the Unknown/Unknown domain name for
your system.
Example: UnknownUnknown
3 Configure the SIP URI Map settings for your secondary proxy or
redirect server, if applicable.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
—End—
Configuring SIP CTI services

Step Action
Perform the procedure below to verify or configure the SIP CTI services. For
(NN43001-313).
1 Expand the SIP CTI Services heading.
2 Configure the SIP CTI services parameters as shown in the table

below.
Note: The CTI prefix parameters in Table 14 "SIP CTI services
parameters" (page 36) must match the values defined in the CS
1000 SIP URI Map. The values used in the SIP URI Map vary
considerably from customer to customer and must be populated
based on the network’s engineered dial plan values.
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
Server 2007
NN49000-309 01.01 Standard
.
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—
Configuring Signaling Server properties for SIP

Step Action
Perform the procedure below to verify or configure the Signaling Server
properties for SIP. For more information, see IP Peer Networking Installation
and Commissioning (NN43001-313).
1 Expand the Signaling Servers > Signaling Server [your Signaling

Server IP] Properties heading.
2 Configure or verify the Signaling Server parameters as shown in

the table below.
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
Server 2007
NN49000-309 01.01 Standard
.
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.
3 Click Save and Transfer.

4 Click OK.
—End—
Creating the service domain in NRS

Step Action
Perform the procedure below to create a SIP service domain if one is not
already created. On redundant NRS systems, perform all configuration
on the primary NRS.
1 Open NRS Manager from the Enterprise Common Manager login.

2 Expand and select Numbering Plans.
3 In the right-hand pane, click Standby database to switch from active

to standby database view.
4 In the left-hand pane, click Domains.
5 In the right-hand pane, click Add.

The View Service Domain Property page appears.
6 For Domain name, enter the SIP domain name previously
configured in the procedure "Configuring Signaling Server properties
for SIP" (page 37) (for example, mcc3100.com).
7 For Domain description, enter a relevant description for the domain

being used.
8 Click Save.
—End—
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Creating the L1 (UDP) domain in NRS

Step Action
Perform the procedure below to create an L1 (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 the parameters provisioned
earlier in the SIP URI Map. Some parameters may be optional for your
system. For a system with full BARS/NARS or a UDP dialing plan, you must
configure the applicable parameters for your engineered dialing plan.
1 In the right-hand pane, select L1 Domains (UDP) (1).

2 Click Add.
3 For Domain name, type a relevant domain name (for example,

UDP).
used.
5 For E.164 country code, enter the E.164 country code for your
system.
6 For E.164 area code, enter the E.164 area code for your system.
7 Configure other optional parameters as required for your system.

8 Click Save.
—End—
Creating the L0 (CDP) domain in NRS

Step Action
Perform the procedure below to create an L0 (CDP) service domain if one is
not already created. On redundant NRS systems, perform all configuration
on the primary NRS.
Configure the NRS L0 domain using the same the parameters provisioned
earlier in the SIP URI Map. Some parameters may be optional for your
system. For a system with full BARS/NARS or a UDP dialing plan, you must
configure the applicable parameters for your engineered dialing plan.
1 In the right-hand pane, select L0 Domains (CDP) (1).
2 Click Add.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
3 For Domain name, type a relevant domain name (for example,

CDP).

used.
5 For E.164 country code, enter the E.164 country code for your
system.
6 For E.164 area code, enter the E.164 area code for your system.
7 Configure other optional parameters as required for your system.
8 Click Save.
—End—
Configuring endpoints on the NRS

Step Action
Perform the procedure below to configure the MCM Gateway endpoints on
the Network Routing Service (NRS). You must perform this procedure for
each MCM node on the system. On NRS redundant systems, perform all
configuration on the primary NRS.
1 In the right-hand pane, click Endpoints.
2 Ensure that the correct Service domain, L1 domain, and L0

domain are selected.
3 Click Add.
4 For Endpoint name, type a relevant endpoint name (for example,

convergedoffice_ocs).
5 For Endpoint description, type a relevant endpoint description.
6 For Endpoint authentication, select Authentication off.

7 For Static endpoint address type, select IP version 4.
8 For H.323 support, select H.323 not supported for the MCM
gateway endpoints.
9 For SIP support, select Dynamic SIP endpoint.
10 For SIP transport, enable the transport protocol type for TCP.
11 Type a value for the SIP TCP port 5060.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
12 Click Save.
—End—
Configuring routing entries on the NRS

Step Action
Perform the procedure below to add a routing entry for each MCM gateway
endpoint. The Signaling Server endpoint is already configured according
to your dial plan.
On NRS redundant systems, perform all configuration on the primary NRS.
1 In the right-hand pane, click Routes.

2 Ensure that the correct Service domain, L1 domain, and L0
domain are selected.
3 Select the Endpoint for which you want to add a route and click Add.
4 Select the DN Type.
5 Type the DN prefix.

The DN prefix is the DSC created in the procedure "Configuring a
Distant Steering Code" (page 33). The DN prefix can be up to 30
characters in length, and can include the characters 0–9, #, -, ?. The
first character of the DN prefix must be numeric (for example, 4100).
Use the same DN prefix for each end point.
6 Enter the Route cost.

The default route cost is 1. The lower the number, the less expensive
the cost of using the route. Configure the route cost based on the
engineered dial plan for your network.
7 Click Save.
—End—
Cutting over and committing changes on the NRS Database

Step Action
Perform the procedure below to switch between the active and standby
database access pointers. This swaps the primary and standby databases
so that configuration changes take effect.
1 In NRS Manager, expand System.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
2 Select Database.
3 Click Cut Over.
4 Click Commit.
—End—
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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.
An example of a local site is shown in Figure 3 "OCS 2007 single site

topology" (page 44).
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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
Server 2007
NN49000-309 01.01 Standard
.
Configuring NAS VLAN 2 45
NAS configuration prerequisites

• NAS is installed and software is Release 22.0 or later. Release 23.2 is
recommended.
• A management Ethernet port is connected and configured.
• Two IP addresses are available to assign Gateway layer 3.
• One IP address is available to assign a virtual IP address for the OCS
2007 pool. An entry is required in the DNS server to resolve the OCS
2007 pool host name to this IP address.
NAS configuration procedures

The sequence of NAS configuration procedures is as follows:
• "Configuring NAS VLAN 2" (page 45)
• "Configuring NAS uplink ports" (page 46)
• "Disabling NAS STP" (page 47)
• "Configuring the NAS layer 3 Gateway interfaces " (page 47)
• "Configuring OCS 2007 real server IP addresses" (page 48)
• "Configuring OCS 2007 real servers for VLAN and port assignment
on NAS" (page 49)
• "Configuring the new group and adding real servers" (page 50)
• "Configuring a NAS virtual IP address for public access to the OCS 2007
front-end pool" (page 51)
• "Configuring NAS SLB ports for client and server processing " (page 52)
• "Enabling NAS SLB service" (page 53)
• "Applying and saving configuration changes" (page 53)
• "Verifying services" (page 54)
Configuring NAS VLAN 2

Perform the procedure below to create a new VLAN named VLAN 2.
Step Action
1 Configure the server VLAN.

Syntax:
/c/l2/vlan 2/ena/name "[vlan name]"/def [ports
used for front ends, multiple ports use spaces]
Example:
/c/l2/vlan 2/ena/name "192_167_130_0"/def 9 10
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
The system responds:

VLAN number 2 with name "VLAN 2" created.
Current status: disabled
New status: enabled
Current VLAN name:
New VLAN name: 192_168_100_0
2 When prompted to confirm changing the PVID for VLAN ports, enter
y.
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
Pending new ports for VLAN 2: 9 10
Pending new ports for VLAN 2: 9 10
—End—
Configuring NAS uplink ports

Step Action
1 Configure the uplink ports.

Syntax:
/c/l2/trunk 1/add [uplink port #1]/add [uplink
port #2]/ena
Example:
/c/l2/trunk 1/add 27/add 28/ena
Port 27 added.
Port 28 added.
New status: enabled
—End—
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Configuring the NAS layer 3 Gateway interfaces 47
Disabling NAS STP

Perform the procedure below to disable Spanning Tree Protocol (STP).
Step Action
1 Disable STP.
Syntax:
/c/l2/stg 1/off
Current Spanning Tree 1 setting: ON
New Spanning Tree 1 setting: OFF
—End—
Configuring the NAS layer 3 Gateway interfaces

Perform the procedure below to create Gateways for VLAN 1 and VLAN 2.
Step Action
1 Configure the layer 3 interface for VLAN 1.

Syntax:
/c/l3/if 1/add [layer 3 ip for vlan 1]/mask
[subnet mask]/vlan 1/en
Example:
/c/l3/if 1/add 192.167.140.1/mask
255.255.255.0/vlan 1/en
Current IP address: 0.0.0.0
New pending IP address: 192.167.140.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: 1
New status: enabled
2 Configure the layer 3 interface for VLAN 2.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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
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
New status: enabled
—End—
Configuring OCS 2007 real server IP addresses

Perform the procedure below to configure real OCS 2007 server IP
addresses.
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
Current real server IP address: 0.0.0.0
New pending real server IP address:
192.167.130.40
New status: enabled
Current real server name:
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Configuring OCS 2007 real servers for VLAN and port assignment on NAS 49
New real server name: OCSFRONTEND1

Current timeout: 10
New pending timeout: 30
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
Current real server IP address: 0.0.0.0
New pending real server IP address:
192.167.130.41
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
1 Assign the first real server to VLAN 2 and port 9.

Syntax:
/c/slb/real 1/ids/idsvlan 2/idsport [port you have
OCS front end server #1 plugged into]
Example:
/c/slb/real 1/ids/idsvlan 2/idsport 9
2 Assign the second real server to VLAN 2 and port 10.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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—
Configuring the new group and adding real servers

Perform the procedure below to create a new group and assign the real
OCS 2007 servers to the group.
Step Action
1 Configure the group.

Syntax:
/c/slb/group 1/ipver v4/add 1/add 2/name
"[relevant name for virtual group]"/metric
Hash/health tcp
Example:
/c/slb/group 1/ipver v4/add 1/add 2/name
"allpool"/metric Hash/health tcp
Real server 1 added to real server group 1.
Real server 2 added to real server group 1.
New real server group name: allpool
Current metric: leastconns
New pending metric: hash
Current health check type: tcp
New pending health check type: tcp
—End—
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Adding additional services to the virtual group 51
Configuring a NAS virtual IP address for public access to the OCS

2007 front-end pool
Perfrom the procedure below to create a new virtual IP address, assign
group 1 to the IP address, and create the 5061 service to allow TLS client
connections. If you are using TCP for client connections, the 5060 service
is required. This IP address is associated with the OCS 2007 front-end
pool host name.
Step Action
1 Configure a public virtual IP address for the group.

Syntax:
/c/sl/virt 1/en/vip [virtual IP assigned to OCS
front end pool]/service 5061/gr 1
Example:
/c/sl/virt 1/en/vip 192.167.130.45/service 5061/gr
1
New status: enabled
Current virtual server IP address: 0.0.0.0
New pending virtual server IP address:
192.167.130.45
Current real server group: 1
New pending real server group: 1
—End—
Adding additional services to the virtual group

Perform the procedure below to add the following service ports to enable
additional OCS 2007 communications:
• port 135 — perform pool lever WMI operations over DCOM
• port 444 — communication between the internal components that
manage conferencing and the conferencing servers
• port 443 — HTTPS traffic to the pool URLs
Perform this procedure for each service port added.
Step Action
1 Configure a public virtual IP address for the group.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Syntax:
/c/sl/virt 1/service [service port number]/gr 1
Current real server group: 1
New pending real server group: 1
—End—
Configuring NAS SLB ports for client and server processing

Step Action
1 Enable the server-side port 9 for SLB.

Syntax:
/c/slb/port [port where front end server #1
plugged in]/ser e
Example:
/c/slb/port 9/ser e
Current server processing: disabled
New server processing: enabled
2 Enable the server-side port 10 for SLB.

Syntax:
/c/slb/port [port where front end server #2
plugged in]/ser e
Example:
/c/slb/port 10/ser e
3 Enable the client-side port 27 for SLB.

Syntax:
/c/slb/port [uplink port #1]/client e
Example:
/c/slb/port 27/client e
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Applying and saving configuration changes 53

4 Enable the client-side port 28 for SLB.

Syntax:
/c/slb/port [uplink port #2]/client e
Example:
/c/slb/port 28/client e
—End—
Enabling NAS SLB service

Step Action
1 Enable SLB.
Syntax:
/c/sl/on
Current status: OFF
New status: ON
—End—
Applying and saving configuration changes

Step Action
1 Enter Apply to apply the configuration changes.
2 Enter Save to save the configuration.
—End—
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Verifying services
Step Action
1 Enter /i/slb/dump to display the current state of the server

on-screen. Under Virtual server state, verify that virtual port
5061 is defined, and both OCS 2007 front-end servers are listed
as up.
Example output:
Real server state:
1: OCSFRONTEND1, 00:0c:29:90:03:74, vlan 2, port
9, health 4, up
Real server group 1 , Workload Manager none
Virtual services:
5061: vport 5061, rtspslb none
virtual server: 1, IP4 192.167.130.45
2: OCSFRONTEND2, 00:0c:29:d0:9d:77, vlan 2, port
10, health 4, up
Real server group 1 , Workload Manager none
Virtual services:
5061: vport 5061, rtspslb none
virtual server: 1, IP4 192.167.130.45
Virtual server state:
1: IP4 192.167.130.45, 00:09:97:76:c6:0e
virtual ports:
5061: rport 5061, group 1, OCS2007Pool, backup
none, rtspslb none
real servers:
1: OCSFRONTEND1, backup none, 12 ms, group ena,
up
2: OCSFRONTEND2, backup none, 6 ms, group ena, up
IDS group state:
Redirect filter state:
Port state:
27: client
28: client
9: server
10: server
—End—
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
55
Local site configuration

This section describes the steps required to provide High Availability and
load balancing to a single site with a Microsoft Office Communication Server
2007 (OCS 2007) pool.
An example of a single site network topology is shown in Figure 3 "OCS

2007 local site architecture" (page 44).
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.
Local site configuration prerequisites

• Domain controllers are running Microsoft Windows® 2000 Server
Service Pack 4 (SP4), Windows Server 2003 SP1, or Windows Server
2003 R2 or later. Windows Server 2003 R2 is recommended.
• Global catalog servers are running Windows 2000 Server SP4, Windows
Server 2003 SP1, or Windows Server 2003 R2 or later. Windows Server
2003 R2 is recommended.
• Separate computers are dedicated for hosting OCS 2007 and Active
Directory global catalog or domain controllers. Installing OCS
Communication Server on the same computer as an Active Directory
global catalog or domain controllers is not supported.
• All domains in which you deploy OCS 2007 are using Windows 2003
native mode or later. You cannot deploy OCS 2007 in a mixed mode
domain. Members of universal groups can include other groups and
accounts from any domain in the domain tree or forest and can be
assigned permissions in any domain in the domain tree or forest.
Universal group support, combined with administrator delegation, greatly
simplifies managing an OCS 2007 deployment.
• A back-end database is installed on a separate computer from OCS
2007. Installation of a back-end database on a server that also hosts
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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.
• A Certification Authority for enterprise, standalone, or public is available.

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

The sequence of Local site configuration procedures is as follows:
• "Preparing the Active Directory schema, forest and domain" (page 57)
• "Preparing the back-end database" (page 59)
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Preparing the Active Directory schema, forest and domain 57
• "Configuring OCS 2007 on the front-end servers" (page 63)

• "Verifying replication" (page 68)
• "Starting services and forcing Address Book synchronization " (page 68)
Preparing the Active Directory schema, forest and domain

Before installing OCS 2007, you must prepare the Active Directory Service.
Perform the procedure below to prepare the schema from a domain
controller and then prepare the forest and domain from the OCS 2007
server.
Step Action
1 Log onto the Domain Controller (for example, rome).
2 Select Start > Run and type dsa.msc.

3 Right-click the domain and select Raise Domain Functional Level
to ensure that the Domain Controller is operating in Windows 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 Server
page appears.
7 Select Prepare Active Directory .
8 Select Step 1: Prep Schema and click Run.

This may 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, 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.
13 Select Step 3: Prep Forest and click Run.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.

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.
16 For Domain, verify that the Active Directory forest domain is

selected.
17 Click Next.
The Specify the SIP Domain Used for Default Routing 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.
21 Select the View the log when you click Finish check box, and
then click Finish.
23 Select Step 5: Prep Current Domain and click Run.
24 Click Next.
The Domain Preparation Information page appears.
25 Click Next.
The Ready to Prepare Domain page appears.
26 Click Next.
27 Select the View the log check box.
28 Click Finish.
corner.
30 Verify that each task’s result is Success.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
31 On the Completion page, click Finish.

The Prepare Active Directory for Office Communications Server
page appears.
32 Click Back.
Notice that Step 1: Prepare Active Directory appears. Complete.
33 From the domain controller, select Start > Run and enter explorer.
34 Using Windows Explorer, create three shared directories:

• OCS 2007 content folder (for example, \\rome\ocscontent)
• OCS 2007 metadata folder (for example, \\rome\ocsmetadata)
• OCS 2007 Address Book folder (for example, \\rome\ocsad-
dressbook)
The domain controller will contain content for the OCS 2007 system
using these file directory shares.
—End—
Preparing the back-end database

Perform the procedure below to configure the SQL Server, create SQL
database components for the pool, and configure the pool.
You must install SQL Server 2000 SP4 or SQL Server 2005 SP1 before
performing this procedure.
Step Action
1 On the DNS server, create a host record for allpool.innlab.nor-

tel.com that resolves to the VIP address 192.167.130.45.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
2 Log onto the SQL Server (OCSDB1) using domain credentials.

4 Double-click the setup.exe file.

5 Click Deploy Pool in a Consolidated Topology.
The Deploy Enterprise Pool in a Consolidated Topology page
appears.
6 For Create an enterprise pool, select Run.

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 the pool
(for example, allpool.innlab.nortel.com).
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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.
25 Select the View the log when you click Finish check box.
26 Click Finish.
corner.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Note: A DNS warning appears if a pool host record is not

configured.
29 Back on the Deploy Enterprise Pool in a Consolidated Topology

page, for Configure pool, select Run.
30 Click Next.
31 If Administrative tools are not installed, the option to do so is

displayed. Click Next on the Administrative Tools page if it appears.
32 On the Server or Pool to Configure page, select the FQDN (for
example, 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.
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.
39 Select the Use this server or pool to authenticate and redirect

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 select

Pool 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.
45 Click Next.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
47 Click Finish.
corner.
—End—
Configuring OCS 2007 on the front-end servers

Perform the procedures in this section to configure the OCS 2007 front-end
servers and assign certificates. Certificates are a key built-in component to
OCS 2007 and required for features using secure communications.
Configuring OCS 2007 servers

Step Action
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.

E:\OCS2007) and double-click the setup.exe file.
appears.
4 For Step 5: Add Servers to the Pool, select Run.

5 Click Next.
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
Server 2007
NN49000-309 01.01 Standard
.
This may 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 not already

created.
13 Click Next.
The Component Service Account page appears.
14 Create a new RTCComponentService Account with a password if

not already created.
15 Click Next.
The Select Guest Account page appears.
16 Create a new RTCGuestAccessUser Account with a password if

not already created.
17 Click Next.
The Ready to Activate Components page appears.

19 Click Finish.
corner.
22 Exit the Deployment Wizard.
23 Repeat this procedure for each front-end server in the network.
—End—
Configuring and assigning server certificates to the OCS 2007 servers

Step Action
1 Log onto the OCS 2007 server configured in the procedure

"Configuring OCS 2007 servers" (page 63) using domain credentials.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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.

appears.
11 Click Run for Step 6: Configure Certificate to start the

Communication Certificate Wizard.
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.
18 In the Deploy Enterprise Pool in a Consolidated Topology page, click

Run for Step 6: Configure Certificate.
19 Click Next.
The Available Certificate Tasks page appears.
20 Verify that Create a new certificate is selected.
21 Click Next.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
The Delayed or Immediate Request page appears.
22 Verify that Send the request immediately to an online

certification 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 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).
28 For Organizational unit, type the organizational unit name (for

example, lab).
29 Click Next.
The Your Server’s Subject Name page appears.
30 For Subject Name, verify that the FQDN is selected (for example,
31 For Subject Alternate Name, verify that sip.<domain name> is
selected (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).
Note: In this document, a root Certification Authority is
configured on the domain controller.
37 Click Next.
The Request Summary page appears.
38 Verify the settings and then click Next.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
39 Click Assign.
40 When prompted by the Communications Certificate Wizard, click OK.

41 Click Finish.
—End—
Assigning server certificates to the Web component on the OCS 2007

servers
Step Action
1 Select Start > Control Panel > Administrative Tools > Computer
Management.
2 Expand Services and Applications > Internet Information

Services (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 page appears.
6 Click Next.
7 Click Assign an existing certificate.

8 Click Next.
9 Select the certificate that you requested using the Certificate

Wizard, assuming that the certificate matches the name of the Web
Components Server or pool.
10 Click Next.
The SSL Port page appears.
11 Verify that port 443 will be used for SSL.

12 Click Next.
13 Review the certificate details, and then click Next to assign the
certificate.
14 Click Finish to exit.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
15 Click OK to close the Default Web Site Properties page.
—End—
Verifying replication
Perform the procedure below to complete the necessary checks to both
OCS 2007 front-end servers.
Step Action
1 Log onto each OCS 2007 front-end server (for example,

OCSFRONTEND1 and OCSFRONTEND2) using domain
credentials.
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 is displayed on the command line.
For example:
.Check the log file "C:\DOCUME~1\ADMINI~1.VMW\LO-
CALS~1\Temp\LCS Server…..html”
8 Open the HTML document and click Expand All in the upper-right
—End—
Starting services and forcing Address Book synchronization

Perform the procedure below to start the services, validate the installation,
and force a synchronization of the Address Book server database on each
OCS 2007 front-end server.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Starting the OCS 2007 servers

Step Action
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.

appears.
4 For Step 9: Start Services, select Run.

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—
Configuring routes on the OCS 2007 front-end servers

Step Action
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.
5 Select the Routing tab.

6 Click the Add button.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
The Add Static Route page appears.

Note: In the figure below, the title of the Add Static Route page
differs from that shown.
Figure 4
Add Static Route
7 For Domain, type your Active Directory domain.
8 Select IP address and type the IP address of the MCM/Proxy server.
9 For Transport, select TCP.

10 Ensure that Port is set to 5060.
11 Click OK.
12 Select the Host Authorization tab.

The Add Authorized Host page appears.
Note: In the figure below, the title of the Add Authorized Host
page differs from that shown.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Figure 5
Add Authorized Host
14 Select IP address and type the IP address of the MCM/Proxy server.
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 the pool,
and select Properties.
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 Leave Port set to 5060.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
26 Click OK.
27 Repeat Step 20through Step 26 for each server in the pool.
28 In the Front End Properties window, click Apply and then OK.
—End—
Creating a location profile

Step Action
credentials.
2 Select Start > Programs > Administrative Tools > Office

Communications Server 2007.
3 Right-click Forest and select Properties > Voice Properties.
The Voice Properties page appears.
4 Select the Location Profiles tab.

6 For Location Profile, enter a name and description.

7 Click the Add button in the Normalization Rules area.
The Add Normalization Rule page appears.
8 Type a meaningful name and description for the new normalization

rule.
9 Enter the Phone pattern and Translation pattern expression that
apply to your dialing plans. For more information, click the Helper
button.
Note: The Translation patterns used in this document are for
example purposes only. Several valid translation patterns may
be used. Choose the pattern that matches your engineered
dialing plan. For more information, click the Helper button.
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 the
changes.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
—End—
Creating phone usages, policies, and routes

Step Action
credentials.
2 Select Start > Programs > Administrative Tools > Office
Communications 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 usage record.
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 click Edit.
11 Ensure that the Allow Simultaneous Ringing of Phones check
box 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.

The Add Route page appears.
19 Type a meaningful name and description for the route.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
20 For Target Regular Expression, type an expression that matches

your dial plan (for example, [\d\d\d\d]).
For more information, click the Helper button.
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—
Installing the Mediation Server

Step Action
1 Log onto the OCS 2007 Mediation Server using domain credentials.

E:\OCS2007\Setup\I386).
3 Double-click setup.exe.
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.

7 Click Next.
8 If the License Agreement is displayed, agree to the terms and select

Next.
9 In the Location for Server Files page, choose the installation folder.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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.
13 In the Deploy Mediation Server page, select Run for Step 2:

Activate Mediation Server.
14 Click Next.
The Select Service Account page appears.
15 Select Use An Existing Account.

16 Enter a Password for the account.
17 Click Next.
The Ready to Activate Mediation Server page appears.
18 Click Next.
The Completion page appears

20 Click Finish.
21 Switch to the Deployment Log and click Expand All in the

upper-right hand corner.
23 Exit the Deployment window.
—End—
Configuring and assigning the server certificate to the Mediation Server

Step Action
1 Log onto the Mediation Server configured in the procedure "Installing

the Mediation Server" (page 74)using domain credentials.

3 Type http://<issuing CA server>/certsrv.
4 Click OK.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.

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.

E:\OCS2007\Setup\i386) and double-click the setup.exe file.

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.
14 Click Next.
15 Select Import a certificate chain from a .p7b file.
16 Click Next.
17 Click Browse to locate the .P7B file.
18 Select the .P7B file.
19 Click Next.
20 Click Finish.
21 In the Deploy Mediation Server page, click Run for Step 4:

Configure Certificate.
22 Click Next.
23 Verify that Create a new certificate is selected.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
24 Click Next.
25 Verify that Send the request immediately to an online

certification authority is selected.
26 Click Next.
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.
30 For Organization, type the parent domain (for example, nortel.com).
31 For Organizational unit, type the organizational unit name (for

example, lab).
32 Click Next.
The Your Server’s Subject Name page appears.
33 For Subject Name, verify that the FQDN is selected (for example,
34 For Subject Alternate Name, verify that sip.<domain name> is
selected (for example, sip.innlab.nortel.com).
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.

is detected and listed (for example, rome.innlab.nortel.com).
Note: In this document, a root Certification Authority is
configured on the domain controller.
40 Click Next.
41 Verify the settings and then click Next.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
42 Click Assign.
43 When prompted by the Communications Certificate Wizard, click OK.

44 Click Finish.
—End—
Configuring the Mediation Server

Step Action
1 Log onto the OCS 2007 Mediation Server using domain credentials.
2 Select Start > Administration Tools > Office Communications

Server 2007.
3 Expand the appropriate forest node.
4 Expand the Mediation Servers node.

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

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

9 Type cmd.
The command prompt window appears.
10 Type nslookup <FQDN of Mediation Server>, using the FQDN

displayed in the General tab from Step 6.
11 For Communication Server Listening IP Address, type the IP
address returned in the procedure "Configuring and assigning the
server certificate to the Mediation Server" (page 75).
12 For Gateway listening IP address, select the other IP address (that

is, the one not already selected in Step 11).
13 For Default Location Profile, select the default location profile for
the Mediation Server.
14 Verify that the default Media Port Range is 60000 to 64000.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
15 Select the Next Hop Connections tab.
16 For FQDN, select the FQDN of the pool.
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.
19 For Port, accept the default of 5060 for TCP.
20 Click OK.
—End—
Starting the Mediation Server

Step Action
1 Log onto an OCS 2007 front-end server using domain credentials.

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

the list of services.
—End—
Installing the proxy server

Step Action
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
Server 2007
NN49000-309 01.01 Standard
.

E:\OCS2007\Setup\I386\setup).
4 At the command prompt, enter server.msi SERVER=PROXY

SKU=EE.
The Proxy Setup Wizard appears.
5 Click Next.
6 Accept the License Agreement and click Next.

7 Type your Username and Organization if not already populated,
and click Next.
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.
10 When the Installation Complete page appears, click Close.
—End—
Activating the proxy server

Step Action
1 Log onto the OCS 2007 proxy server using domain credentials.
2 Select Start > Run and enter cmd.

E:\OCS2007\Setup\I386\setup).
4 At the command prompt, enter lcscmd /server /password:<pass-

word>/action:activate /role:proxy, where <password> is your
desired proxy server password.
5 Verify that the status message “Action completed successfully”

appears at the end of the script.
—End—
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Configuring and assigning the server certificate for the proxy server
Step Action
2 Select Start > Run and enter http://<name of issuing CA
Server>/certsrv.

chain, or CRL.
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 server’s hard disk.
6 Select Start > Programs > Administrative Tools > Computer
Management.
7 Expand Services and Applications in the left-hand pane.

8 Right-click Microsoft Office Communications Server 2007 and
select Certificates.
The Certificates Wizard appears.
9 Click Next.
10 Select Import a certificate chain from a .p7b file and click Next.
11 Select Browse to locate the .p7b file, locate the file and click Next.
12 Click Finish.

select Certificates.
The Certificates Wizard appears.
14 Click Next.
15 Select Create a new certificate and click Next.
16 Select Send the request immediately to an online certification

authority and click Next.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
17 Verify that the proxy server Name is configured for the new
certificate.
18 Leave the bit length of 1024 as is.

19 Clear the Mark cert as exportable check box, and then click Next.
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 is

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

is selected.
25 Click Next.
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.
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.
32 Verify the settings and click Next.

33 Click Assign.
The Communications Certificate Wizard appears.
34 Click OK.
35 Click Finish.
—End—
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Configuring the proxy server

Step Action
2 Select Start > Programs > Administrative Tools > Computer

Management.
3 Expand Services and Applications in the left-hand pane.

select Properties.

Note: If you are using protocols not specified in this document,
ensure that you select the appropriate protocols here.
6 In the Connections area, click Add. The Add Connections page

appears.
Figure 6
Add Connection
7 For IP Address, select All.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
8 Leave Port at 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/SRS server.
14 Select the Throttle As Server check box.

15 Select the Treat As Authenticated check box.
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.
18 Click OK to close the Properties dialog and apply the changes.

select Start.
—End—
Installing the Multimedia Convergence Manager

Step Action
1 Log onto the server intended for the Multimedia Converged Manager
server using your domain credentials.
2 Navigate to the installation directory for the MCM software (for

example, D:\MCM Setup\).
3 Double-click the setup.exe file to launch the installer.
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
Server 2007
NN49000-309 01.01 Standard
.
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.

Note: By default, the passwords for "RTCComponentService",
"RTCGuestAccessUser", "RTCProxyService", and "RTCService"
users are automatically reset in 90 days.
11 Click OK.
The installation continues.
12 When the Installation Complete page appears, click Close.
—End—
Configuring permissions for the Multimedia Convergence Manager

Step Action
1 Log onto the Multimedia Convergence Manager server using domain

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 the Advanced button.
7 Click Find Now.

8 In the search results, locate and select the MCMService user and
click OK.
9 Click OK.
10 Double-click the RTC Server Local Group group.
11 Click Add.
12 Click the Advanced button.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
13 Click Find Now.
14 In the search results, locate and select the MCMService user and
click OK.
15 Click OK.
—End—
Configuring the Multimedia Convergence Manager

Step Action
1 Log onto the Multimedia Convergence Manager server using domain

credentials.
2 Select Start > Programs > Multimedia Convergence Manager to

launch the Multimedia Convergence Manager application.
3 In the Multimedia Convergence Manager application, select Tools >

Configuration.
4 In the Network Topology area, for Call Server, select CS 1000.
5 Depending on your deployment, select SRS, SPS, or Direct

Connect.
6 Do one of the following:

If you selected SRS or SPS, enter the Primary IP, Secondary IP,
Registration ID, Registration IP, and, if applicable, the Mode.
If you selected Direct Connect, enter the CS 1000 SIP GW IP.
Note: If the SIP domain for OCS 2007 does not match the SIP
service domain 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 Mediation

Server IP, and click Add.
Repeat this step for any additional Mediation Servers in the pool.
Note: The Mediation Pool Identifier is the same as the sip-gw-id
header of the Call Server.
11 Click OK.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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 selected

Called Phone Context (for example, CDP.UDP).
15 In the Network Dial Plan area, select the appropriate Dial Plan for
your deployment, and Access Code if applicable.
16 Ensure that the Enable RCC Authorization check box is selected 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 are Running
and that the Primary SPS/SRS status is Active.
Figure 7
Multimedia Convergence Manager Configuration
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
—End—
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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.
Client configuration procedures

• "Configuring user accounts" (page 89)
• "Installing OCC 2007" (page 93)
Configuring Active Directory

Perform the procedures below to configure OCS 2007 user accounts in
Active Directory.
Configuring user accounts

Step Action
Repeat this procedure for each user connecting to OCS 2007.
1 Log onto an OCS 2007 server, or another server joined to an

Active Directory domain having the Office Communications Server
Administration Tools installed, using an account in the Domain
Admins group.
2 Select Start > Run and enter dsa.msc.
3 Expand your SIP domain.
4 Right-click Users, or another folder in which to create your users,

select New, and click User.
5 Complete the New Object - User Wizard.
6 Right-click the new user you want to enable for Office

Communications Server and select Properties.
7 Click the Communications tab.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
90 Client configuration
Figure 8
User Properties
8 Select the Enable user for Office Communications Server check

box.
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—
Configuring the user server

Step Action
1 Log onto an OCS 2007 server, or another server joined to an

Active Directory domain having the Office Communications Server
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Configuring Active Directory 91
Administration Tools installed, using an account in the Domain

Admins group.
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.

Figure 9
User Properties
6 Click Configure.
The User Options page appears.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Figure 10
User Options
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 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
Server 2007
NN49000-309 01.01 Standard
.
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—
Configuring OCC 2007 clients

Perform the procedures below to install Microsoft Office Communicator
Client 2007 (OCC 2007) on client machines.
Installing OCC 2007 on client machines

Step Action
1 Download and open Communicator.msi.
2 On the Welcome to Microsoft Office Communicator 2007 Setup

page, click Next.
3 Review the license agreement, and then select I accept the terms
in the License Agreement and click Next.
4 Accept the default installation directory, or click Browse and browse

to another directory.
5 Click Next.
6 Click Finish.
7 Open Microsoft Office Communicator 2007.

8 In the top left-hand 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.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Figure 11
Advanced Connection Settings
11 Select Manual configuration. For both Internal server name or IP

address and External server name or IP address, type the server
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 then sign in.
15 From the left-hand corner of Office Communicator, select Options.

16 Select the Phones tab.
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—
Changing the preferred device

Step Action
PBX control is required to change these settings.
1 Select Start > Programs > Microsoft Office Communicator 2007

to launch OCC 2007.
2 Select Tools.
3 Select Call Forward Settings.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
The Call Forwarding Settings page appears.

Figure 12
Call Forwarding Settings
4 For My preferred calling device, select either Phone or Computer.
5 Click OK to apply the changes.
—End—
Figure 13
PBX control
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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)
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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
1 Log into OCC 2007 on client A.
2 Select Tools > Call Forwarding Settings.
3 In the Outgoing Calls area, for Preferred Outgoing Device, select

Computer.
4 Click OK.
5 Repeat steps 1–4 for client B.

6 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.
7 If you do not receive the incoming call notification message on client
B, or if you experience a one-way communication speech path,
verify your client’s configuration. If the problem persists, capture the
relevant logs and contact your next level of support for assistance.
—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
1 Log into OCC 2007.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Call scenario 3 99

Computer.
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.
6 Click the notification message on the OCC 2007 client to answer

the call.
7 If you do not receive the incoming call notification message on the
OCC 2007 client, or if you experience a one-way communication
speech path, verify your client’s configuration. If the problem
persists, capture the relevant logs and contact your next level of
support for assistance.
—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
1 Log into OCC 2007.

Phone.
4 Click OK.
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.
6 Lift the handset on telephone B to answer the call.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
100 Testing

OCC 2007 client, telephone B does not ring, or you experience
a one-way communication speech path, verify your client’s
configuration. If the problem persists, capture the relevant logs and
contact your next level of support for assistance.
—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


Phone.
4 Click OK.
5 Repeat steps 1–4 for client B.
6 Use the Click to call feature on client A or the dialpad on telephone A

to place a call to client B.
7 Lift the handset on telephone B to answer the call.

OCC 2007 client, telephone B does not ring, or you experience
a one-way communication speech path, verify your client’s
configuration. If the problem persists, capture the relevant logs and
contact your next level of support for assistance.
—End—
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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

Computer.
4 Click OK.
5 Log into OCC 2007 on client B.

Phone.
8 Click OK.
9 From client A, enter the phone number of client B and select Click
to call.
10 Lift the handset on the telephone associated with client B to answer

the call.
11 If you do not receive the incoming call notification message on

client B, the telephone associated with client B does not ring, or
you experience a one-way communication speech path, verify your
client’s configuration. If the problem persists, capture the relevant
logs and contact your next level of support for assistance.
—End—
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
102 Testing
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
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)
Running AML traces

Perform the procedure below to run AML traces.
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
Server 2007
NN49000-309 01.01 Standard
.
104 Troubleshooting
6 Exclude the outgoing polling messages for the ELAN link and specify
the priority (for example, ENXO MSGI <link #><Priority>).
—End—
Priority Description
1 System priority messages
2 Signaling priority messages
3 Call processing priority messages
4 Administration priority messages
Running DCH traces

Perform the procedure below to run DCH traces.
Running DCH traces on a busy system may cause a system outage. Nortel
recommends that you run DCH traces during non-peak hours.
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>).
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
Server 2007
NN49000-309 01.01 Standard
.
Running SIP call traces 105
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.
Running SIP CTI traces

Perform the procedure below to run SIP CTI traces.
Step Action
1 Connect to the Signaling Server.
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>).
—End—
0 Default summary view
1 Detailed view
Running SIP call traces

Perform the procedure below to run SIP call traces.
Step Action
1 Connect to the Signaling Server.
2 At the OAM prompt, enable SIP tracing using the SIPCallTrace

command (for example, SIPCallTrace ON).
3 Set the trace level using the SIPTraceLevel command (e.g
SIPTraceLevel <Priority>).
—End—
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
106 Troubleshooting
0 Default summary view
1 Detailed view
Capturing MCM logs

Perform the procedure below to generate MCM logs.
Step Action
1 Log into the MCM.
2 Select Tools > Log level.

The Logs page appears.
3 Optionally, select the Log Size.
4 For Log Level, select SIP and Debug.

5 Before placing a test call, press the Clear Log button.
6 To view the MCM logs, open the MCM.log file located in the directory
where MCM is installed.
—End—
Running OCS 2007 Application Proxy traces

Perform the procedure below to run OCS 2007 Application Proxy traces.
Step Action
1 Log into the proxy server.

2 Select Start > Administrative Tools > Computer Management.
The Computer Management page appears.
3 Right-click Computer management (local) > Services and

Applications > Microsoft Office Communications Server 2007.
4 Select New Debug Session.
The Office Communicator Server 2007 Logging tool appears.
5 In the Components area, select SIPStack.
6 In the Level section, select All.
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Running OCS 2007 Mediation Server traces 107
7 Select Start Logging to start the logging process.
8 Select Stop Logging to stop the logging process.
9 To view the logs in text mode, select View Log Files.

The View Log files page appears.
10 Select the log files you wish to view.
11 Select View to view the logs in text format.
12 To analyze the logs, click Analyze Log Files.

Note: Microsoft Office Communicator Server 2007 Resource Kit
Tools is required for the Analyze function.
13 Select the logs you wish to analyze.
14 Click Analyze.
—End—
Running OCS 2007 Mediation Server traces

Perform the procedure below to run OCS 2007 Mediation Server traces.
Step Action
1 Log into the Mediation Server.
2 Select Start > Administrative Tools > Office Communication

Server 2007.
The Microsoft Office Communications Server 2007 window appears.
3 Right-click Office Communications Server 2007 > Forest >

Mediation Server > (Mediation Server name).
4 Select New Debug Session.

5 In the Components area, select Mediation Server and S4.

Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
108 Troubleshooting


14 Click Analyze.
—End—
Running OCS 2007 front-end server traces

Perform the procedure below to run OCS 2007 front-end server traces.
Step Action
1 Log into the front-end server.
2 Select Start > Administrative Tools > Office Communication

Server 2007.
The Microsoft Office Communications Server 2007 window appears.
3 Select Office Communications Server 2007 > Forest > Enterprise
pools.
4 Right-click the pool name for which you wish to capture logging (for
example, allpool) and select Logging Tool > New Debug Session.
5 In the Components area, select SIPStack.



Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Running OCS 2007 front-end server traces 109


14 Click Analyze.
—End—
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
110 Troubleshooting
Enterprise: Common
Server 2007
NN49000-309 01.01 Standard
.
Enterprise: Common
Solution Integration Guide for Communication Server 1000

Release 5.0/Microsoft Office Communications Server 2007
All Rights Reserved.
Publication: NN49000-309
Document status: Standard
Document version: 01.01
Document date: 7 April 2008
To provide feedback or report a problem in this document, go to

www.nortel.com/documentfeedback.
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.

Microsofr OCS

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Microsofr OCS

Caricato da

Copyright:

Formati disponibili

Enterprise: Common

Solution Integration Guide for

Copyright © 2008, Nortel Networks

Applying and saving configuration changes 53

How to get help

Finding the latest updates on the Nortel Web site

Getting help from the Nortel Web site

Getting help over the phone from a Nortel Solutions Center

In North America, call 1-800-4NORTEL (1-800-466-7835).

Getting help from a specialist by using an Express Routing Code

Getting help through a Nortel distributor or reseller

About this document

This document is intended to be a stand-alone guide, covering the

• Dialing Plans: Description (553-3001-183)

An example of a CS 1000/OCS 2007 network topology is shown in Figure 1

you begin the systems integration. A complete list of courses is available

Complete the checklist below to ensure that your system baseline

Task Reference Comments

6 Verify that the PCA

Task Reference Comments

Task Reference Comments

Task Reference Comments

Task Reference Comments

Use the worksheet below to record your system information to aid in

Parameter Example Value

Service Protocol Port(s) Description

Service Protocol Port(s) Description

Service Protocol Port(s) Description

8. "Running OCS 2007 front-end server traces" (page

CS 1000 system configuration

Call Server configuration prerequisites

Call Server configuration procedures

Configuring SIP channel resources, phones, and PCA

Configuring a new ELAN ID and VAS ID (LD 17)

1 Connect to the Call Server.

3 Enter the appropriate values as described in the following tables.

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

Enabling the ELAN connection to the switch (LD 48)

1 Connect to the Call Server.

3 Enter ENL ELAN to enable the ELAN.

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

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

Provisioning a telephone for Converged Office

1 Connect to the Call Server.

3 Enter the appropriate values as described in the following tables.

Prompt Response Description

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

Provisioning a PCA to associate with the telephone

1 Connect to the Call Server.

3 Enter the appropriate values as described in the following tables.

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

Saving the configuration

1 Connect to the Call Server.

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

Configuring the CS 1000 system

Configuring routes and trunks

1 In Element Manager, expand the Routes and Trunks heading.

Configuring RLI (RLB)

1 In Element Manager, expand the Dialing and number plans

3 Expand Network Control and Services.

4 Select Route List Block.

7 For ROUT, select the route created in the procedure "Configuring

Configuring a Distant Steering Code

1 In Element Manager, select Dialing and number plans > Electronic