Avaya Communication Server 1000 User Manual

Enterprise: Common

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

NN43001-326

Document status: Standard Document version: 02.01 Document date: 3 April 2009

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.

Sourced in Canada

Contents

How to get help 7

Finding the latest updates on the Nortel Web site 7 Getting help from the Nortel Web site 7 Getting help over the phone from a Nortel Solutions Center 7 Getting help from a specialist by using an Express Routing Code 8 Getting help through a Nortel distributor or reseller 8

About this document 9

Audience 9 Related information 9

Overview 11 Prerequisites 17

Knowledge requirements 17

Capturing integration parameters 18 Establishing the system baseline 19

Training 17

CS 1000 setup and IP Peer Networking conﬁguration 25

CS 1000/IP Peer Networking conﬁguration procedures 25 Conﬁguration of H.323 Trunks in the Call Server 26

Deﬁning the customer to support ISDN 27 Creating the virtual D-channel 28 Conﬁguring zones (LD 117) 31 Creating the virtual route (LD 16) 32 Creating the virtual trunks (LD 14) 34 Creating the ESN data block for CDP 36 Creating the Network Control Block (NCTL) for network access (LD 87) 38 Creating the RLB for the virtual trunk route (LD 86) 40 Creating the CDP steering codes (LD 87) 41 Checking CODEC and QoS settings 43

H.323 Gatekeeper conﬁguration 46

Conﬁguring Element Manager 46

SIP protocol conﬁguration 48

Enabling the SIP Virtual Trunk application 48

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

4 Contents

Conﬁguring the SIP Gateway 50 Conﬁguring the SIP Redirect Server and URI map 52 Conﬁguring IP networking for SIP 54

NRS conﬁguration 75

NRS conﬁguration procedures 75 Launching NRS Manager 75 Verifying and adjusting system-wide settings 76 Conﬁguring the NRS server settings (H.323 Gatekeeper or SIP) 78 Conﬁguring the service domain 80 Conﬁguring the L1 domain (UDP) 81 Conﬁguring the L0 domain (CDP) 83 Conﬁguring Gateway endpoints 86 Conﬁguring routing entries 90 Conﬁguring collaborative servers 92 Updating the database 94 Checking the status of registered endpoints 95 Checking the status of virtual D-channels 96 Checking the status of virtual trunks 97

BCM 200/400 conﬁguration 99

BCM 200/400 conﬁguration procedures 99 Conﬁguring incoming VoIP trunks 99 Verifying system license and keycodes 100 Conﬁguring VoIP trunk media parameters 101 Conﬁguring local Gateway parameters 104 Conﬁguring target lines 109 Conﬁguring VoIP lines 112

BCM 50/450 conﬁguration 119

BCM 50/450 conﬁguration procedures 119 Conﬁguring incoming VoIP trunks 119 Verifying system license and keycodes 120 Conﬁguring VoIP trunk media parameters 121 Conﬁguring local Gateway parameters 125 Conﬁguring VoIP lines 130 Conﬁguring target lines 134

Testing and troubleshooting 137

Testing and troubleshooting procedures 137 Testing 137

Testing the integration from the BCM system 138 Testing the integration from the CS 1000 system 140

Troubleshooting 140

BCM is unable to contact the gatekeeper at IP address 140 Unable to complete any calls 140

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

Cannot make calls between the CS 1000 and BCM 141 BCM fails to register to NRS 141 H.323 Gateway service is down 142

Contents 5

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

6 Contents

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

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:

ww.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:

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

•

open and manage technical support cases

Getting help over the phone from a Nortel Solutions Center

If you do not ﬁnd the information you require on the Nortel TechnicalSupport 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:

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

8 How to get help

www.nortel.com/callus

Getting help from a specialist by using an Express Routing Code

Toaccess some Nortel Technical Solutions Centers, youcan 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:

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

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

About this document

This document describes the planning, conﬁguration, and troubleshooting of the integration of the Business Communications Manager (BCM) with a Communication Server 1000 system. Integrate the CS 1000 and BCM systems 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:

•

Communication Server 1000 (CS 1000) Release 5.5

•

Business Communications Manager 200 (BCM 200) Release 4.0

•

Business Communications Manager 400 (BCM 400) Release 4.0

•

Business Communications Manager 450 (BCM 450) Release 1.0

•

Business Communications Manager 50 (BCM50) Release 3.0

This document is intended to be a stand-alone guide, covering the prerequisites to and implementation of a successful CS 1000/BCM 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:

•

BCM 4.0 Device Conﬁguration Guide (N0060600)

•

BCM 4.0 Telephony Device Installation Guide (N0060609)

•

BCM50 Networking Conﬁguration Guide (NN40020-603)

•

Communication Server 1000E: Installation and Conﬁguration

(553-3041-210)

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

10 About this document

•

Communication Server 1000M and Meridian 1: Large System Installation and Conﬁguration (553-3021-210)

•

Communication Server 1000M and Meridian 1: Small System Installation and Conﬁguration (553-3011-210)

• Communication Server 1000S: Installation and Conﬁguration

(553-3031-210)

•

Dialing Plans: Description (553-3001-183)

•

IP Line Description, Installation, and Maintenance (553-3001-365)

•

IP Peer Networking Installation and Conﬁguration Guide (553-3001-213)

•

Keycode Installation Guide (NN40010-301)

•

Signaling Server: Installation and Conﬁguration (553-3001-212)

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

Overview

An example of a Communication Server 1000/Business Communications Manager (BCM) systems integration is shown in Figure 1 "CS 1000/BCM

architecture" (page 11).

Figure 1 CS 1000/BCM architecture

CS1000 Gateway IP address CS1000 Endpoint IP address BCM 400 Endpoint IP address Signaling Server T-LAN IP Address

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

10.10.11.1

10.12.12.3

10.20.12.8

10.12.13.1

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

BCM Gateway Alias name BCM40

12 Overview

Signaling Server E-LAN IP Address Call Server E-LAN IP Address NRS IP Address NCS IP Address BCM IP Address

Figure 2 "CS 1000/BCM integration process" (page 13) shows the sequence

of procedures you perform to integrate the CS 1000 and BCM systems.

10.12.13.2

10.12.12.3

10.10.12.2

10.10.12.3

10.26.12.9

NRS Host name CS1000E_PIV

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

Figure 2 CS 1000/BCM integration process

Overview 13

The tasks in the CS 1000/BCM systems integration process are listed in Table 1 "Task Completion Checklist" (page 14). Use this checklist to implement the integration.

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

14 Overview

Table 1 Task Completion Checklist

Task Reference

Configure the H.323 Call Server

1. "Defining the customer to support ISDN" (page 27)

2. "Creating the virtual D-channel" (page 28)

3. "Configuring zones (LD 117)" (page 31)

4. "Creating the virtual route (LD 16)" (page 32)

5. "Creating the virtual trunks (LD 14)" (page 34)

6. "Creating the ESN data block for CDP" (page 36)

7. "Creating the Network Control Block (NCTL) for

network access (LD 87)" (page 38)

8. "Creating the RLB for the virtual trunk route (LD 86)"

(page 40)

9. "Creating the CDP steering codes (LD 87)" (page 41)

10. "Checking CODEC and QoS settings" (page 43)

Configure the H.323 Gatekeeper "Configuring Element Manager" (page 46) Configure the SIP protocol "Enabling the SIP Virtual Trunk application" (page 48) Configure the SIP Gateway "Configuring the SIP Gateway" (page 50) Configure the SIP Redirect

Server and URI Map Configure the SIP Call Server

"Configuring the SIP Redirect Server and URI map" (page

52)

1. "Defining the customer to support ISDN" (page 54)

2. "Creating the virtual D-channel" (page 56)

3. "Configuring zones (LD 117)" (page 59)

4. "Creating the virtual route (LD 16)" (page 60)

5. "Creating the virtual trunks (LD 14)" (page 62)

6. "Creating the ESN data block for CDP" (page 64)

7. "Creating the Network Control Block (NCTL) for

network access (LD 87)" (page 66)

8. "Creating the RLB for the virtual trunk route (LD 86)"

(page 68)

9. "Creating the CDP steering codes (LD 87)" (page 69)

10. "Checking CODEC and QoS settings" (page 71)

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

Task Reference

Configure NRS

1. "Launching NRS Manager" (page 75)

2. "Verifying and adjusting system-wide settings" (page

76)

3. "Configuring the NRS server settings (H.323

Gatekeeper or SIP)" (page 78)

4. "Configuring the service domain" (page 80)

5. "Configuring the L1 domain (UDP)" (page 81)

6. "Configuring the L0 domain (CDP)" (page 83)

7. "Configuring Gateway endpoints" (page 86)

8. "Configuring routing entries" (page 90)

9. "Configuring collaborative servers" (page 92)

10. "Updating the database" (page 94)

11. "Checking the status of registered endpoints" (page

95)

12. "Checking the status of virtual D-channels" (page 96)

Overview 15

13. "Checking the status of virtual trunks" (page 97)

Configure BCM BCM 200/400

1. "Configuring incoming VoIP trunks" (page 99)

2. "Verifying system license and keycodes" (page 100)

3. "Configuring VoIP trunk media parameters" (page

101)

4. "Configuring local Gateway parameters" (page 104)

5. "Configuring target lines" (page 109)

6. "Configuring VoIP lines" (page 112)

BCM50

1. "Configuring incoming VoIP trunks" (page 119)

2. "Verifying system license and keycodes" (page 120)

3. "Configuring VoIP trunk media parameters" (page

121)

4. "Configuring local Gateway parameters" (page 125)

5. "Configuring VoIP lines" (page 130)

6. "Configuring target lines" (page 134)

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

16 Overview

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

Prerequisites

Before you begin to integrate the Communication Server 1000 (CS 1000) and Business Communications Manager (BCM) systems, ensure that you complete the following prerequisites:

•

"Knowledge requirements" (page 17)

• "Capturing integration parameters" (page 18)

•

"Establishing the system baseline" (page 19)

Knowledge requirements

The following knowledge and skills are required to implement a CS 1000/BCM systems integration:

•

basic programming and provisioning skills for the CS 1000 system

•

basic programming and provisioning skills for Network Routing Service (NRS)

•

basic programming and provisioning skills for BCM systems

•

working knowledge of various operating systems, including VxWorks, Unix, Linux, and Windows

•

principles of Voice over IP (VoIP) protocols

•

networking principles

• knowledge of core data components

Training

Nortel recommends that you complete product-speciﬁc training before you begin integrating the CS 1000 and BCM systems. Training includes course 6034C, “CS 1000 BCM Multi-site Integration”, which deals speciﬁcally with the CS 1000/BCM integration and multi-site BCM integration processes. A complete list of courses is available at w

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

ww.nortel.com

18 Prerequisites

Capturing integration parameters

Table 2 "Integration parameters" (page 18) provides a list of parameters

required to successfully complete the integration. Record these parameters during the initial planning phase of the integration.

Table 2 Integration parameters

Parameter Value User IDs and passwords

SIP Gateway endpoint authentication password (must match the NRS password)

IP addresses and URLs

Gatekeeper IP address Alternate Gatekeeper IP address (optional) T-LAN IP address of the Signaling Server T-LAN IP address of the alternate Signaling

Server Primary SIP proxy address Alternate SIP proxy address Primary NCS IP address Alternate NCS IP address) Static endpoint IP address (same as the Node

IP address) Collaborative server IP address

Names

Service domain name in NRS SIP domain name (must be the same as the

service domain name) SIP Gateway endpoint name (must match the

NRS user ID) L0 domain name L1 domain name H.323 ID (preferable if it is the same as the one

in the Primary Signaling Server) H.323 Gatekeeper alias name (default is the

H.323 ID) Endpoint alias for BCM Read and write community names

Miscellaneous

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

Parameter Value

Coordinated Dialing Plan steering codes SIP access port to use (port 5060 is

recommended)

Establishing the system baseline

To successfully integrate voice services, you must ﬁrst establish the system baseline for the Call Server, Signaling Server, and Business Communications Manager (BCM) so that the systems are conﬁgured and working in a stand-alone environment.

Use Table 3 "Pre-integration checklist" (page 19) to complete system baselines prior to integration.

Table 3 Pre-integration checklist

Establishing the system baseline 19

Task Reference

The Enterprise software package is purchased and installed, with appropriate licenses for virtual trunks, lines, and IP Phones as required.

The Network Numbering Plan is implemented.

Dialing Plans: Description

(553- 3001-183)

CS 1000 software is Release

5.5.

Comments

Are you using a Uniform 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)?

To check the CS 1000 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.

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

20 Prerequisites

Task Reference

Signaling Server software is Release 5.5.

Basic installation, setup, and configuration of the Call Server components and the Signaling Server are complete.

Communication Server 1000M and Meridian 1: Small System Installation and Configuration (553-3011-210)

Communication Server 1000M and Meridian 1: Large System Installation and Configuration (553-3021-210)

Comments 3 The software release is

referred to as Release. The Signaling Server

software should be the most recent GA release compatible with your Call Server software version.

To check the software release of the Signaling Server:

1 Log on to Element Manager.

2 On the left navigation pane, select Home. The System Overview page appears.

3 Refer to the Signaling Server Details section for the Software Version.

Communication Server 1000S: Installation and Configuration (553-

3031-210)

Communication Server 1000E: Installation and Configuration (553-

3041-210)

Signaling Server: Installation and Configuration (553-

3001-212)

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

Establishing the system baseline 21

Task Reference

Primary, alternate, and fail-safe Network Routing Service (NRS) are configured

Signaling Server: Installation and Configuration (553-

3001-212) at installation and initial setup of the Signaling Server.

Digital Data Block configuration is complete in LD 73.

PTI or DTI trunks (DLOP) configuration is complete in LD 17.

IP Peer Networking

Installation and Configuration

Guide (553-3001-213)

IP Peer Networking

Installation and Configuration

Guide (553-3001-213)

Comments

The NRS requires IP telephony node configuration files. These files are installed and configured during the Signaling Server software installation as a basic configuration step.

To configure a Digital Data Block:

1 Connect to the Call Server. 2 Enter LD 73. 3 Enter NEW. 4 Enter DDB. 5 Press Enter to accept all

defaults. 6 Perform a data dump. To check PTI or DTI trunks: 1 Log on to Element

Manager.

A basic node is configured in Element Manager.

Voice Gateway Media Card configuration is complete if IP to PSTN translation is required.

IP Line Description,

Installation, and Maintenance

(553- 3001-365)

2 Select Routes and Trunks > Digital Trunk Interface.

3 Select Digital Trunk Interface Data Block (DDB).

4 Checkthattheconfiguration

is complete. This node information

is updated through the integration process.

To check that Media Gateway Cards are installed:

1 Log on to Element Manager.

2 On the left side navigation pane, expand the System tab.

3 Expand the Software tab. 4 Select Voice Gateway

Media Card.

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

22 Prerequisites

Task Reference

H.323 Virtual Trunk package 399 is installed.

Comments

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.

To check that the package is loaded:

1 Connect to the Call Server. 2 Log on to the Signaling

Server.

3 Enter LD 22. 4 Enter PRT. 5 Enter PKG 399. 6 The package is loaded if

youdonotreceivea“package is restricted” message.

IPT is Release 3.0 or newer if you are using IP Trunk cards.

BCM configuration is complete and passing data traffic.

To check that IPT Trunk cards are installed:

1 Log on to Element Manager.

2 On the left navigation pane, expand the IP Network tab.

3 Select Nodes: Servers, Media Cards.

4 Expand the appropriate

Node. Attention: The servers and

Media Cards installed and configured are listed under each node. Any installed IPT Trunk cards are listed under Type.

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

Establishing the system baseline 23

Task Reference

BCM networking hardware is installed for integration.

PEC III Media Service Cards (MSC) are later.

Comments

To check the installed hardware:

1 Log on to Element Manager.

2 Select the Administration tab.

3 Expand the General folder. 4 Select Hardware

Inventory. 5 Select the PCI cards tab.

The cards installed in BCM are listed.

PECIII MSCs are required for T.38 Fax and IP telephony.

To check the PEC hardware: 1 Log on to Element

Manager. 2 Select the Administration

tab.

BCM 200/400 is Release 4.0. BCM50 is Release 2.0.

3 Expand the General folder. 4 Select Hardware

Inventory. 5 Select the PCI cards tab. 6 Select the MSC PCI card

and scroll down to the Details for Card section.

To check the software version:

1 Log on to Element Manager.

2 Select the Configuration tab.

3 Expand the System folder. 4 Select Identification.

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

24 Prerequisites

Task Reference

VoIP Gateway Trunk licensing is purchased

Keycode Installation Guide

(NN40010-301) and loaded on BCM.

IP Client licensing is purchased and loaded

Keycode Installation Guide

(NN40010-30 on BCM.

MCDN feature licensing is purchased and loaded on

Keycode Installation Guide

(NN40010-30 BCM.

Comments

To check Feature Licenses: 1 Log on to Element

Manager. 2 Select the Configuration

tab.

3 Expand the System folder. 4 Select Keycodes.

To check Feature Licenses: 1 Log on to Element

Manager. 2 Select the Configuration

tab.

3 Expand the System folder. 4 Select Keycodes.

To check Feature Licenses: 1 Log on to Element

Manager. 2 Select the Configuration

tab.

3 Expand the System folder. 4 Select Keycodes.

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

CS 1000 setup and IP Peer Networking conﬁguration

Although you can conﬁgure the Communication Server 1000 and IP Peer Networking through overlays, the use of Element Manager and Network Routing Services (NRS) Manager are recommended. The Element Manager Web server resides on the Signaling Server and you can access it directly through a Web browser or by using Optivity Telephony Manager (OTM). You must conﬁgure NRS through Network Routing Service Manager (NRS Manager), which you can access only through the Element Manager.

Conﬁgure the Call Server through Element Manager in the following order:

• H.323 Call Server

•

H.323 Gate Keeper

•

Session Initiation Protocol (SIP) — SIP Protocol

— SIP Gateway — SIP Redirect Server and URI Map — SIP Call Server — Network Routing Service in the NRS Manager — SIP addressing — SIP virtual trunking

CS 1000/IP Peer Networking conﬁguration procedures

The sequence of CS 1000/IP Peer Networking conﬁguration procedures is as follows:

•

"Conﬁguration of H.323 Trunks in the Call Server" (page 26)

— "Deﬁning the customer to support ISDN" (page 27) — "Creating the virtual D-channel" (page 28) — "Conﬁguring zones (LD 117)" (page 31)

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

26 CS 1000 setup and IP Peer Networking conﬁguration

— "Creating the virtual route (LD 16)" (page 32) — "Creating the virtual trunks (LD 14)" (page 34) — "Creating the ESN data block for CDP" (page 36) — "Creating the Network Control Block (NCTL) for network access

(LD 87)" (page 38)

— "Creating the RLB for the virtual trunk route (LD 86)" (page 40) — "Creating the CDP steering codes (LD 87)" (page 41) — "Checking CODEC and QoS settings" (page 43)

•

"H.323 Gatekeeper conﬁguration" (page 46)

— "Conﬁguring Element Manager" (page 46)

•

"SIP protocol conﬁguration" (page 48)

— "Enabling the SIP Virtual Trunk application" (page 48) — "Conﬁguring the SIP Gateway" (page 50) — "Conﬁguring the SIP Redirect Server and URI map" (page 52) — "Deﬁning the customer to support ISDN" (page 27) — "Creating the virtual D-channel" (page 28) — "Conﬁguring zones (LD 117)" (page 31) — "Creating the virtual route (LD 16)" (page 32) — "Creating the virtual trunks (LD 14)" (page 34) — "Creating the ESN data block for CDP" (page 36) — "Creating the Network Control Block (NCTL) for network access

(LD 87)" (page 38)

— "Creating the RLB for the virtual trunk route (LD 86)" (page 40) — "Creating the CDP steering codes (LD 87)" (page 41) — "Checking CODEC and QoS settings" (page 43)

Conﬁguration of H.323 Trunks in the Call Server

The procedures in this section are as follows:

•

"Deﬁning the customer to support ISDN" (page 27)

•

"Creating the virtual D-channel" (page 28)

•

"Conﬁguring zones (LD 117)" (page 31)

•

"Creating the virtual route (LD 16)" (page 32)

•

"Creating the virtual trunks (LD 14)" (page 34)

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

Conﬁguration of H.323 Trunks in the Call Server 27

•

"Creating the ESN data block for CDP" (page 36)

•

"Conﬁguring the L0 domain (CDP)" (page 83)

•

"Creating the RLB for the virtual trunk route (LD 86)" (page 40)

•

"Creating the CDP steering codes (LD 87)" (page 41)

•

"Checking CODEC and QoS settings" (page 43)

Deﬁning the customer to support ISDN

Complete the following procedure to deﬁne the customer to support ISDN.

Step Action 1

2 3

Log on to Element Manager.

Select Customers.

Select the Customer Number you wish to edit.

The Customer Edit page appears. See Figure 3 "Customer Edit"

(page 27).

Figure 3

Customer Edit

Select the Feature Packages heading.

The Feature Packages page appears. See Figure 4 "Feature

Packages" (page 28).

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

28 CS 1000 setup and IP Peer Networking conﬁguration

Figure 4

Feature Packages

Expand the Integrated Services Digital Network Package 145

heading.

Ensure that the Integrated Services Digital Network check box

is selected.

Click Save.

—End—

Creating the virtual D-channel

Perform the following procedure to create the virtual D-channel.

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

Step Action

Conﬁguration of H.323 Trunks in the Call Server 29

1 2

Log on to Element Manager.

Select Routes and Trunks > D-Channels.

A message appears if a D-channel is not conﬁgured. Click OK.

The D-Channels page appears. See Figure 5 "D-Channels" (page

29).

Figure 5

D-Channels

From the Choose a D-Channel Number menu, select the

D-Channel number.

D-channels 0,1, and 2 are usually used or shared with other

applications. It is recommended that you begin conﬁguring virtual

D-channels on channel 3.

4 5

From the Type menu, select the D-Channel type.

Click to Add.

The D-Channels Property Conﬁguration page appears. See Figure

6 "D-Channels Property Conﬁguration" (page 30).

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

30 CS 1000 setup and IP Peer Networking conﬁguration

Figure 6

D-Channels Property Conﬁguration

For the D channel Card Type (CTYP), select D-Channel is over

IP (DCIP).

For the Designator (DES), type a meaningful name.

The Designator must not contain spaces; use underscores instead.

Make a note of the Designator in your records for future reference.

For User (USR), select Integrated Services Signaling Link

Dedicated (ISLD).

For Interface type for D-channel (IFC), select Meridian Meridian1

(SL1).

Leave all other parameters as is and click Submit.

The new channel appears.

—End—

Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager

Enterprise: Common

NN43001-326 02.01 Standard

Release 5.5 3 April 2009

+ 114 hidden pages