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 Copyright © 2009, Nortel Networks All Rights Reserved. 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.
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 Audience 9 Related information 9 9 Overview 11 Prerequisites 17 Knowledge requirements 17 Training 17 Capturing integration parameters 18 Establishing the system baseline 19 CS
Contents Configuring the SIP Gateway 50 Configuring the SIP Redirect Server and URI map 52 Configuring IP networking for SIP 54 NRS configuration NRS configuration procedures 75 Launching NRS Manager 75 Verifying and adjusting system-wide settings 76 Configuring the NRS server settings (H.
Contents 5 Cannot make calls between the CS 1000 and BCM 141 BCM fails to register to NRS 141 H.323 Gateway service is down 142 Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
Contents Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
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.
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.
About this document This document describes the planning, configuration, 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.
About this document • 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) • 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) • Keyc
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 10.10.11.1 CS1000 Endpoint IP address 10.12.12.3 BCM 400 Endpoint IP address 10.20.12.8 Signaling Server T-LAN IP Address 10.12.13.1 BCM Gateway Alias name BCM40 Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.
Overview Signaling Server E-LAN IP Address 10.12.13.2 Call Server E-LAN IP Address 10.12.12.3 NRS IP Address 10.10.12.2 NCS IP Address 10.10.12.3 BCM IP Address 10.26.12.9 NRS Host name CS1000E_PIV Figure 2 "CS 1000/BCM integration process" (page 13) shows the sequence of procedures you perform to integrate the CS 1000 and BCM systems. Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.
Overview 13 Figure 2 CS 1000/BCM integration process 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. Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
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.
Overview Task Reference Configure NRS 1. "Launching NRS Manager" (page 75) 15 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.
Overview Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
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 sy
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.
Establishing the system baseline 19 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 first establish the system baseline for the Call Server, Signaling Server, and Business Communications Manager (BCM) so that the systems are configured and working in a stand-alone environment.
Prerequisites Task Reference Comments 3 The software release is referred to as Release. Signaling Server software is Release 5.5. 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.
Establishing the system baseline 21 Task Reference Comments Primary, alternate, and fail-safe Network Routing Service (NRS) are configured at installation and initial setup of the Signaling Server. Signaling Server: Installation and Configuration (5533001-212) 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. Digital Data Block configuration is complete in LD 73.
Prerequisites Task Reference 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. H.323 Virtual Trunk package 399 is installed. 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.
Establishing the system baseline 23 Task BCM networking hardware is installed for integration. Reference 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. PEC III Media Service Cards (MSC) are later. PECIII MSCs are required for T.38 Fax and IP telephony. To check the PEC hardware: 1 Log on to Element Manager.
Prerequisites Task Reference Comments VoIP Gateway Trunk licensing is purchased and loaded on BCM. Keycode Installation Guide (NN40010-301) To check Feature Licenses: 1 Log on to Element Manager. 2 Select the Configuration tab. 3 Expand the System folder. 4 Select Keycodes. IP Client licensing is purchased and loaded on BCM. Keycode Installation Guide (NN40010-30 To check Feature Licenses: 1 Log on to Element Manager. 2 Select the Configuration tab. 3 Expand the System folder. 4 Select Keycodes.
CS 1000 setup and IP Peer Networking configuration Although you can configure 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).
CS 1000 setup and IP Peer Networking configuration — "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.
Configuration of H.323 Trunks in the Call Server • "Creating the ESN data block for CDP" (page 36) • "Configuring 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) 27 Defining the customer to support ISDN Complete the following procedure to define the customer to support ISDN. Step Action 1 Log on to Element Manager. 2 Select Customers.
CS 1000 setup and IP Peer Networking configuration Figure 4 Feature Packages 5 Expand the Integrated Services Digital Network Package 145 heading. 6 Ensure that the Integrated Services Digital Network check box is selected. 7 Click Save. —End— Creating the virtual D-channel Perform the following procedure to create the virtual D-channel. Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.
Configuration of H.323 Trunks in the Call Server 29 Step Action 1 Log on to Element Manager. 2 Select Routes and Trunks > D-Channels. A message appears if a D-channel is not configured. Click OK. The D-Channels page appears. See Figure 5 "D-Channels" (page 29). Figure 5 D-Channels 3 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.
CS 1000 setup and IP Peer Networking configuration Figure 6 D-Channels Property Configuration 6 For the D channel Card Type (CTYP), select D-Channel is over IP (DCIP). 7 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. 8 For User (USR), select Integrated Services Signaling Link Dedicated (ISLD).
Configuration of H.323 Trunks in the Call Server 31 Configuring zones (LD 117) Before you can configure the virtual routes and trunks, the following zones must be configured, in any order: • Zone 1 = IP Phones zone (ZBRN = MO) • Zone 2 = Voice Gateway Channels zone, which should be different from the IP Phones zone (ZBRN = VTRK) Ensure that enough bandwidth is allocated for the zones with the heaviest traffic. Never use or configure zone 0. Step Action 1 Log on to Element Manager.
CS 1000 setup and IP Peer Networking configuration 5 After you click to Add, a message may appear prompting you to use the Zone Basic Property and Bandwidth Management Spreadsheet. Click OK. 6 Leave the default values for bandwidth and resource type as is. 7 Set the Zone Intent (ZBRN) as follows: • Zone 1 is for the IP Phones at the Main Office. Set Zone Intent (ZBRN) for Zone 1 to MO (MO). • Zone 2 is for the Voice Gateway Channels. Set Zone Intent (ZBRN) for Zone 2 to VTRK (VTRK).
Configuration of H.323 Trunks in the Call Server 33 Step Action 1 Log on to Element Manager. 2 Select Routes and Trunks > Routes and Trunks. 3 Click the Add route button. The Route Property Configuration page appears. The trunk type (TKTP) you choose determines the parameters available on this page. SeeFigure 9 "Route Property Configuration" (page 33) for one possible view of the Route Property Configuration page. Figure 9 Route Property Configuration 4 Select the Route Number (ROUT).
CS 1000 setup and IP Peer Networking configuration 7 For Incoming and Outgoing trunk (ICOG), select Incoming and Outgoing (IAO). 8 Set the Access Code for the trunk route (ACOD). 9 Select the The route is for a virtual trunk route (VTRK) check box. 10 Type the Zone number of the zone with the ZBRN set to Vtrk for the new route. This value must match the values you configure in the Signaling Server. 11 Type the Node ID of signaling server of this route (NODE).
Configuration of H.323 Trunks in the Call Server 35 Step Action 1 Log on to Element Manager. 2 Select Routes and Trunks > Routes and Trunks. 3 Expand the Customer heading. 4 Click Add trunk next to the route to which you wish to add the trunk. The New Trunk Configuration page appears. See Figure 10 "New Trunk Configuration" (page 35). Your configuration determines the parameters available on this page.
CS 1000 setup and IP Peer Networking configuration 10 Set the values of Start arrangement Incoming (STRI) and Start arrangement Outgoing (STRO). Immediate (IMM) is recommended for both fields. 11 Type the Channel ID for this trunk (CHID). 12 You can add a Class of Service (CLS) for all features that you wish. In a basic configuration, you can leave the CLS as is. 13 Select Advanced Trunk Configurations to display a list of advanced features.
Configuration of H.323 Trunks in the Call Server 37 Figure 11 Electronic Switched Network 3 Select Customer > Network Control & Services > ESN Access Codes and Parameters (ESN). 4 A message appears if ESN data is not configured. Click OK. The ESN Access Codes and Basic Parameters page appears. See Figure 12 "ESN Access Codes and Basic Parameters" (page 38). If ESN data is configured on your switch, the fields on this page appear populated.
CS 1000 setup and IP Peer Networking configuration Figure 12 ESN Access Codes and Basic Parameters 5 Edit the main parameters (MXDM, MXRL, MXSD, MXIX, MXFC, MXFS and MXLC) if required, or leave the default values as is. 6 Select the Coordinated Dialing Plan feature for this customer (CDP) check box. 7 Set the value of the Maximum number of Steering Codes (MXSC). 8 Set the value of the Number of digits in CDP DN (DSC+DN or LSC+DN) (NCDP). 9 Click Submit.
Configuration of H.323 Trunks in the Call Server 39 2 Select Dialing and Numbering Plans > Electronic Switched Network. 3 Select Customer > Network Control & Services > Network Control Parameters (NCTL). See Figure 11 "Electronic Switched Network" (page 37). 4 A message appears if no network control data is configured. Click OK to configure new data. The Network Control Parameters page appears. See Figure 13 "Network Control Parameters" (page 39).
CS 1000 setup and IP Peer Networking configuration —End— Creating the RLB for the virtual trunk route (LD 86) Perform the following procedure to create the RLB for the virtual trunk route. Step Action 1 Log on to Element Manager. 2 Select Dialing and Numbering Plans > Electronic Switched Network. 3 Select Customer > Network Control & Services > Route List Block (RLB). If route list blocks are not configured, the error message “Route List does not exist” appears. Click OK.
Configuration of H.323 Trunks in the Call Server 41 Figure 15 Route List Block 6 Select the Route Number (ROUT) you previously defined. 7 For Strategy on Congestion (SBOC), select Reroute All (RRA). 8 Accept the other defaults and click Submit. The new Route List Block is generated. You can check the configuration by selecting Route List Block Index and Data Entry Index. —End— Creating the CDP steering codes (LD 87) Perform the following procedure to create the CDP steering codes.
CS 1000 setup and IP Peer Networking configuration Step Action 1 Log on to Element Manager. 2 Select Dialing and Numbering Plans > Electronic Switched Network. The Electronic Switched Network page appears. See Figure 11 "Electronic Switched Network" (page 37). 3 Select Customer > Coordinated Dialing Plan (CDP) > Distant Steering Code (DSC). The Distant Steering Code List page appears. See Figure 16 "Distant Steering Code List" (page 42).
Configuration of H.323 Trunks in the Call Server 43 Figure 17 Distant Steering Code 7 Check that the parameters are configured appropriately for your system. 8 Select a Route list to be accessed for trunk steering code (RLI). 9 Click Submit. 10 Repeat this procedure for all other DSCs on your network. —End— Checking CODEC and QoS settings At this point, the Call Server configuration is complete. It is recommended that you check the CODEC and QoS settings.
CS 1000 setup and IP Peer Networking configuration Figure 18 Node Configuration 3 Click Edit. 4 Expand the VGW and IP phone codec profile heading and edit the fields as necessary. See Figure 19 "VGW and IP phone codec profile" (page 45). Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
Configuration of H.323 Trunks in the Call Server 45 Figure 19 VGW and IP phone codec profile 5 Expand the QoS heading and edit the fields as necessary. See Figure 20 "QoS" (page 46). Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
CS 1000 setup and IP Peer Networking configuration Figure 20 QoS 6 If you make configuration changes, click Save and Transfer. When the successful transfer notification message appears, click OK. If you do not make configuration changes, click Cancel. —End— H.323 Gatekeeper configuration Configure the H.323 Gatekeeper in both Element Manager and the NRS. Configure the Element Manager before the NRS. The sequence of H.
H.323 Gatekeeper configuration 47 Figure 21 H323 Gateway and Signaling Server 5 Enter the Primary Gatekeeper (TLAN) IP address. This is the T-LAN IP address of the Signaling Server that runs the Gatekeeper application. This is not the same as the Node IP. 6 Enter the Alternate Gatekeeper (TLAN) IP address if you have an alternate on your system (optional). 7 Expand the Signaling Servers heading. 8 Expand the Signaling Server Properties heading at the bottom of the page. 9 Enter the H323 ID.
CS 1000 setup and IP Peer Networking configuration 10 Select the Enable Gatekeeper check box. 11 If you make configuration changes, click Save and Transfer. When the successful transfer notification message appears, click OK. If you do not make configuration changes, click Cancel.
SIP protocol configuration Step Action 1 Log on to Element Manager. 2 Select System > IP Network > Nodes: Servers, Media Cards. See Figure 18 "Node Configuration" (page 44). 3 Click Edit next to the node you are editing. 4 Expand the Signaling Servers heading. 5 Expand the Signaling Server Properties heading. See Figure 22 "Signaling Server Properties" (page 49). 49 Figure 22 Signaling Server Properties 6 For Enable IP Peer Gateway (Virtual Trunk TPS), select a SIP option (SIP only or H.
CS 1000 setup and IP Peer Networking configuration The SIP Domain Name must be less than 128 characters in length. Valid characters are a-z, 0-9, period, hyphen, comma, and underscore. This string builds all SIP messages and appears in the URI phone context. If you enable the SIP Gateway application, specify this field. This name must match the Service Domain name configured in NRS. 10 Enter the SIP Gateway Endpoint Name and SIP Gateway Authentication Password. These values must match the data in NRS.
SIP protocol configuration 51 Figure 23 SIP GW settings 5 In the Primary Proxy or Redirect Server section, type the Primary Proxy or Re-direct (TLAN) IP address. 6 In the Primary Proxy or Redirect Server section, type the Port number. The default port value is 5060. 7 Select the Supports Registration check box. 8 Select the Transport Protocol. Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.
CS 1000 setup and IP Peer Networking configuration 9 If you plan to configure a secondary or redundant proxy server, repeat steps 6 through 9 for the Secondary Proxy or Re-direct Server section. 10 If you make configuration changes, click Save and Transfer. When the successful transfer notification message appears, click OK. If you do not make configuration changes, click Cancel. —End— Configuring the SIP Redirect Server and URI map Use this procedure to configure your SIP numbering plan mapping.
SIP protocol configuration 53 Figure 24 Edit SIP URI Map 5 For Private/UDP domain name, type the L1 domain. 6 For Private/CDP domain name, type the L0 and L1 domains in the format . 7 Enter the values for your SIP numbering plan in the appropriate fields. 8 Click Save and Transfer. 9 Click OK when the system is done transferring data and the successful transfer message appears. —End— Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.
CS 1000 setup and IP Peer Networking configuration Configuring IP networking for SIP The IP Peer Networking configuration for SIP in the Call Server is similar to the H.323 configuration. For each Call Server in the IP Peer Network, perform the following tasks: 1. Define the customer to support ISDN (LD 15). 2. Create the virtual D-channel (LD 17). 3. Configure the zones (LD 117). 4. Create the virtual route (LD 16). Enter SIP in the VTRK page. 5. Create the virtual trunk. 6.
SIP protocol configuration 55 Figure 25 Customer Edit 4 Select the Feature Packages heading. The Feature Packages page appears. See Figure 26 "Feature Packages" (page 56). Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
CS 1000 setup and IP Peer Networking configuration Figure 26 Feature Packages 5 Expand the Integrated Services Digital Network Package 145 heading. 6 Ensure that the Integrated Services Digital Network check box is selected. 7 Click Save. —End— Creating the virtual D-channel Perform the following procedure to create the virtual D-channel. Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.
SIP protocol configuration 57 Step Action 1 Log on to Element Manager. 2 Select Routes and Trunks > D-Channels. The D-Channels page appears. See Figure 27 "D-Channels" (page 57). A message appears if a D-channel is not configured. Click OK. Figure 27 D-Channels 3 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 configuring virtual D-channels on channel 3.
CS 1000 setup and IP Peer Networking configuration Figure 28 D-Channels Property Configuration 6 For the D channel Card Type (CTYP), select D-channel is over IP (DCIP). 7 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. 8 For User (USR), select Integrated Services Signaling Link Dedicated (ISLD).
SIP protocol configuration 59 Configuring zones (LD 117) Before you can configure the virtual routes and trunks, the following zones must be configured, in any order: • Zone 1 = IP Phones zone (ZBRN = MO) • Zone 2 = Voice Gateway Channels zone, which should be different from the IP Phones zone (ZBRN = VTRK) Ensure that enough bandwidth is allocated for the zones with the heaviest traffic. Never use or configure zone 0. Step Action 1 Log on to Element Manager.
CS 1000 setup and IP Peer Networking configuration 5 After you click to Add, a message may appear prompting you to use the Zone Basic Property and Bandwidth Management Spreadsheet. Click OK. 6 Leave the default values for bandwidth and resource type as is. 7 Set the Zone Intent (ZBRN) as follows: • Zone 1 is for the IP Phones at the Main Office. Set Zone Intent (ZBRN) for Zone 1 to MO (MO). • Zone 2 is for the Voice Gateway Channels. Set Zone Intent (ZBRN) for Zone 2 to VTRK (VTRK).
SIP protocol configuration 61 Step Action 1 Log on to Element Manager. 2 Select Routes and Trunks > Routes and Trunks. 3 Click the Add route button. The Route Property Configuration page appears. The trunk type (TKTP) you choose determines the parameters available on this page. See Figure 31 "Route Property Configuration" (page 61) for one possible view of the Route Property Configuration page. Figure 31 Route Property Configuration 4 Select the Route Number (ROUT).
CS 1000 setup and IP Peer Networking configuration 7 For Incoming and Outgoing trunk (ICOG), select Incoming and Outgoing (IAO). 8 Set the Access Code for the trunk route (ACOD). 9 Select the The route is for a virtual trunk route (VTRK) check box. 10 Type the Zone number of the zone with the ZBRN set to Vtrk for the new route. This value must match the values you configure in the Signaling Server. 11 Type the Node ID of signaling server of this route (NODE).
SIP protocol configuration 63 Step Action 1 Log on to Element Manager. 2 Select Routes and Trunks > Routes and Trunks. 3 Expand the Customer heading. 4 Click Add trunk next to the route to which you wish to add the trunk. The New Trunk Configuration page appears. See Figure 32 "New Trunk Configuration" (page 63). Your configuration determines the parameters available on this page.
CS 1000 setup and IP Peer Networking configuration 10 Set the values of Start arrangement Incoming (STRI) and Start arrangement Outgoing (STRO). Immediate (IMM) is recommended for both fields. 11 Type the Channel ID for this trunk (CHID). 12 You can add a Class of Service (CLS) for all features that you wish. In a basic configuration, you can leave the CLS as is. 13 Select Advanced Trunk Configurations to display a list of advanced features.
SIP protocol configuration 65 Figure 33 Electronic Switched Network 3 Select Customer > Network Control & Services > ESN Access Codes and Parameters (ESN). 4 A message appears if ESN data is not configured. Click OK. The ESN Access Codes and Basic Parameters page appears. See Figure 34 "ESN Access Codes and Basic Parameters" (page 66). If ESN data is configured on your switch, the fields on this page appear populated.
CS 1000 setup and IP Peer Networking configuration Figure 34 ESN Access Codes and Basic Parameters 5 Edit the main parameters (MXDM, MXRL, MXSD, MXIX, MXFC, MXFS and MXLC) if required, or leave the default values as is. 6 Select the Coordinated Dialing Plan feature for this customer (CDP) check box. 7 Set the value of the Maximum number of Steering Codes (MXSC). 8 Set the value of the Number of digits in CDP DN (DSC+DN or LSC+DN) (NCDP). 9 Click Submit.
SIP protocol configuration 67 Step Action 1 Log onto Element Manager. 2 Select Dialing and Numbering Plans > Electronic Switched Network. 3 Select Customer > Network Control & Services > Network Control Parameters (NCTL). See Figure 33 "Electronic Switched Network" (page 65). 4 A message appears if no network control data is configured. Click OK to configure new data. The Network Control Parameters page appears. See Figure 35 "Network Control Parameters" (page 67).
CS 1000 setup and IP Peer Networking configuration 6 Choose the basic control parameters for your network. 7 Click Submit. —End— Creating the RLB for the virtual trunk route (LD 86) Perform the following procedure to create the RLB for the virtual trunk route. Step Action 1 Log on to Element Manager. 2 Select Dialing and Numbering Plans > Electronic Switched Network. 3 Select Customer > Network Control & Services > Route List Block (RLB).
SIP protocol configuration 69 Figure 37 Route List Block 6 Select the Route Number (ROUT) you previously defined. 7 For Strategy on Congestion (SBOC), select Reroute All (RRA). 8 Accept the other defaults and click Submit. The new Route List Block is generated. You can check the configuration by selecting Route List Block Index and Data Entry Index. —End— Creating the CDP steering codes (LD 87) Perform the following procedure to create the CDP steering codes.
CS 1000 setup and IP Peer Networking configuration Step Action 1 Log on to Element Manager. 2 Select Dialing and Numbering Plans > Electronic Switched Network. The Electronic Switched Network page appears. See Figure 33 "Electronic Switched Network" (page 65). 3 Select Customer > Coordinated Dialing Plan (CDP) > Distant Steering Code (DSC). The Distant Steering Code List page appears. See Figure 38 "Distant Steering Code List" (page 70).
SIP protocol configuration 71 Figure 39 Distant Steering Code 7 Check that the parameters are configured appropriately for your system. 8 Select a Route List to be accessed for trunk steering code (RLI). 9 Click Submit. 10 Repeat this procedure for all other DSCs on your network. —End— Checking CODEC and QoS settings At this point, the Call Server configuration is complete. It is recommended that you check the CODEC and QoS settings. Step Action 1 Log on to Element Manager.
CS 1000 setup and IP Peer Networking configuration Figure 40 Node Configuration 3 Click Edit. 4 Expand the VGW and IP phone codec profile heading and edit the fields as necessary. See Figure 41 "VGW and IP phone codec profile" (page 73). Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
SIP protocol configuration 73 Figure 41 VGW and IP phone codec profile 5 Expand the QoS heading and edit the fields as necessary. See Figure 42 "QoS" (page 74). Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
CS 1000 setup and IP Peer Networking configuration Figure 42 QoS 6 If you make configuration changes, click Save and Transfer. When the successful transfer notification message appears, click OK. If you do not make configuration changes, click Cancel. —End— Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
NRS configuration The Network Routing Service (NRS) uses a basic SIP structure for its configuration, which is applicable for SIP, H.323, and Network Connection Server (NCS) call completion. This structure is the basis of the single network dialing/numbering plan. Before you begin configuration of the NRS, gather the names of all domains and subdomains.
NRS configuration Step Action 1 Log on to Element Manager. 2 Select Dialing and Numbering Plans > Network Routing Service. 3 Click Next. The NRS logon page appears. 4 Click Login. 5 Enter the user ID and password. The NRS Overview page appears. See Figure 43 "NRS Overview" (page 76). Figure 43 NRS Overview —End— Verifying and adjusting system-wide settings You can check system-wide settings and make changes from NRS Manager.
Verifying and adjusting system-wide settings 77 Step Action 1 Log on to NRS Manager. 2 Select System Wide Settings. The System Wide Settings page appears. See Figure 44 "System Wide Settings" (page 77). Figure 44 System Wide Settings 3 Configure the information in the System Wide Settings page. Refer to Table 4 "System Wide Settings fields" (page 77). Table 4 System Wide Settings fields Field Description DB synch interval for alternate [Hours] 24 is the default.
NRS configuration Field Description SIP registration time to live timer [Seconds] 30 seconds is recommended. H.323 Gatekeeper registration time to live timer [Seconds] 30 seconds is recommended. H.323 alias name This is a mandatory field. The H.323 Alias Name must be alphanumeric and contain no spaces. The default value is the same as the H.323 ID and HostName value configured in the PRIMARY Signaling Server’s config.ini file.
Configuring the NRS server settings (H.323 Gatekeeper or SIP) 79 Figure 45 NRS Settings 3 Under NRS Settings, set the following values: • Host name • Primary IP (TLAN) • Alternate IP (TLAN) • Control priority 4 Under H.323 Gatekeeper Settings, select the Location request (LRQ) response timeout [Seconds].
NRS configuration 6 7 Under Network Connection Server (NCS) Settings, set the following values: • Primary NCS port • Alternate NCS port • Primary NCS timeout [Seconds] Click Save. —End— Configuring the service domain The NRS database information configured in this procedure is required by both the SIP Redirect Server and the H.323 Gatekeeper. Step Action 1 Log on to NRS Manager. 2 Select the Configuration tab.
Configuring the L1 domain (UDP) 81 5 Select Service Domains. 6 Click Add. 7 Enter your Domain name and a Domain description. These values must match that set for the Signaling Server. 8 Click Save. The Service Domains page appears again with the new domain added. When no description is entered, the service domain is shown with the message “Not available”. This means that the description is not entered, but the service domain is still active. This applies to all description fields in NRS Manager.
NRS configuration Figure 47 Add L1 Domain 6 Configure the L1 domain. Refer to Table 5 "L1 domain fields" (page 82) for configuration information. Table 5 L1 domain fields Field Value Description Domain name Mandatory. The name must be alphanumeric and can be up to 30 characters in length. Domain description Optional. The description can include any character except single quotes and be up to 120 characters in length.
Configuring the L0 domain (CDP) 83 Field Value Description E.164 country code Mandatory. The code must be numeric and up to 7 characters in length. E.164 area code Mandatory. The code must be numeric and up to 7 characters in length. E.164 international dialing access code Optional. The code must be numeric and up to 7 characters in length. E.164 national dialing access code Optional.
NRS configuration 3 Click set Standby DB view to switch from active to standby database view. 4 Select L0 Domains (CDP). 5 Click Add. The Add L0 Domain page appears. See Figure 48 "Add L0 Domain" (page 84). Figure 48 Add L0 Domain 6 Enter the appropriate values for your network. Refer to Table 6 "Add L0 Domain fields" (page 84)for configuration information. The country codes, area codes, public prefixes, and private prefixes must match those of your L1 domain.
Configuring the L0 domain (CDP) 85 Field Value Description Domain description Optional. The description can include any character except single quotes and can be up to 120 characters in length. Endpoint authentication enabled Authentication off If Authentication on is selected, then all endpoints require authentication. Authentication on Not configured Authentication password if Authentication on is selected, enter a password.
NRS configuration The View L0 Domain Property page appears. See Figure 48 "Add L0 Domain" (page 84). —End— Configuring Gateway endpoints Add an endpoint for both the Communication Server 1000 (CS 1000) and Business Communications Manager (BCM) systems. These are Gateway endpoints, which can be served by several users. You can add multiple endpoints, some SIP-only, some H.323-only, and Unistim. You can also configure a user endpoint, which can be only one of these three protocols.
Configuring Gateway endpoints 87 Figure 49 Add Gateway Endpoint 6 Enter the appropriate values for your network. Refer to Table 7 "Add Gateway Endpoint fields" (page 87) for configuration information. Table 7 Add Gateway Endpoint fields Field Value Description Endpoint name The name must be alphanumeric and up to 30 characters in length. Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.
NRS configuration Field Value Description Endpoint description The description must be alphanumeric and up to 120 characters in length. Tandem gateway endpoint name The tandem Gateway is optional. This indicates whether the endpoint is used to tandem calls from outside the network. The name must be alphanumeric and up to 30 characters in length. Note: Use the Look-up link to find configured Gateway endpoints.
Configuring Gateway endpoints 89 Field Value Description Static endpoint address This is the address of the BCM application server. If a third-party Gateway is used, it is the IP address of the Gateway. H.323 support H.323 not supported RAS H.323 Endpoint is recommended. RAS H.323 endpoint Not RAS H.323 endpoint If an H.323 Gateway Endpoint is configured with an H.323 Support type of RAS H.323 endpoint, NRS Manager displays Endpoint Dynamic Registration information after the H.
NRS configuration 9 Click Show. A list of configured Gateways appears. 10 Click the Gateway ID you wish to view. The Add Gateway Endpoint page appears. See Figure 49 "Add Gateway Endpoint" (page 87). —End— Configuring routing entries Perform the following procedure to configure routing entries. Step Action 1 Log on to NRS Manager. 2 Select the Configuration tab 3 Click set Standby DB view to switch from active to standby database view. 4 Click Routing Entries.
Configuring routing entries 91 Figure 50 Routing Entries 10 Click Add to add a new Routing Entry. The Add Routing Entry page appears. See Figure 51 "Add Routing Entry" (page 92). Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
NRS configuration Figure 51 Add Routing Entry 11 Enter the DN prefix. This is the CDP DSC steering code. 12 Enter the Route cost. The higher the number, the higher the cost. This is equivalent to Least Cost Routing. 13 Click Save. —End— Configuring collaborative servers A Collaborative Server is a server in another network zone that can resolve requests when your NRS cannot find a match in its numbering plan database.
Configuring collaborative servers 93 Figure 52 Add Collaborative Server 6 For Domain type for collaborative Server, select either L0 domain or L1 domain. 7 For the L1 or L0 domain name, select the L1 or L0 domain name. 8 Enter the Alias name of the collaborative server. The alias name must be alphanumeric and contain no spaces. 9 For Server address type, select IP version 4. 10 For Server address, type the server IP address.
NRS configuration 11 12 13 If the H.323 protocol is supported by the server, populate the following fields: • H.
Checking the status of registered endpoints 95 Figure 53 Database Actions 4 From the Select database action menu, select Cut over & Commit. 5 Click Submit. —End— Checking the status of registered endpoints Perform the following procedure to check the status of registered endpoints. Step Action 1 Log on to NRS Manager. 2 Click the Configuration tab. 3 Select Service Domains. See Figure 46 "Service Domains" (page 80).
NRS configuration 4 Ensure that Active DB View is selected. 5 Click the number in the # of gateway endpoints column. 6 Click Show. The Gateway Endpoints page appears. See Figure 54 "Gateway Endpoints" (page 96). Figure 54 Gateway Endpoints —End— Checking the status of virtual D-channels Perform the following procedure to check the status of virtual D-channels. Step Action 1 Log on to Element Manager. 2 Select Routes and Trunks > D-Channels. 3 Select D-Channel Diagnostics (LD 96).
Checking the status of virtual trunks 97 Figure 55 D-Channel Diagnostics 4 Under Diagnostic Commands, select Status for D-Channel (STAT DCH). 5 Click Submit. 6 Check that the D-Channel is operational, established, and active. —End— Checking the status of virtual trunks Perform the following procedure to check the status of virtual trunks. Step Action 1 Log on to Element Manager. 2 Select System > IP Network > Maintenance and Reports. 3 Expand the Node ID heading.
NRS configuration Figure 56 General Commands 5 For Group, select Vtrk. 6 For Command, select vtrkShow. 7 For Protocol, type H323. 8 Click Run. The Virtual Trunk status appears. 9 Check each IP Phone manually (that is, not through Element Manager). At the DEF GW option, verify that the IP address is the same as the T-LAN Gateway of that system. If the phones ring and have dial tone but there is no speech path, the Default Gateway is 0.0.0.0 and is not operational.
BCM 200/400 configuration This chapter describes configuration procedures for the Business Communications Manager (BCM) 200 and 400 systems. Element Manager as viewed on your system may differ slightly from the screens shown in this chapter because you can customize the column display in Element Manager.
BCM 200/400 configuration Figure 57 Keycodes 4 Load new Keycodes by loading a new keycode file or connecting to Nortel’s Keycode Retrieval System (KRS). For more information about keycodes and keycode retrieval, see Keycode Installation Guide (NN40010-301). —End— Verifying system license and keycodes Perform the following procedure to verify system license and keycodes. Step Action 1 Log on to Element Manager. 2 In the Task Navigation Panel, select the Configuration tab.
Configuring VoIP trunk media parameters 101 Configuring VoIP trunk media parameters Perform the following procedure to configure VoIP trunk media parameters. Step Action 1 Log on to Element Manager. 2 In the Task Navigation Panel, select the Configuration tab. 3 Select Resources > Telephony Resources. See Figure 58 "Telephony Resources" (page 101). Figure 58 Telephony Resources 4 In the Modules panel, select the line where the Module Type column is set to IP Trunks. 5 Select the H.
BCM 200/400 configuration Table 8 H.323 Media Parameters fields Field Value Description Preferred Codecs G.711 -uLaw Add codecs to the Selected list and order them in the order in which you want the system to attempt to use them. The system attempts to use the codecs in top-to-bottom sequence. G.711 -aLaw G.729 G.723 Performance note: Codecs on all networked BCMs must be consistent to ensure the proper functionality of interacting features such as Transfer and Conference.
Configuring VoIP trunk media parameters 103 Field Value Description Incremental payload size When enabled, the system advertises a variable payload size (40, 30, 20, 10 ms). Enable T.38 fax When enabled, the system supports T.38 fax over IP. Caution: Fax tones broadcast through a telephone speaker may disrupt calls at other telephones using VoIP trunks in the vicinity of the fax machine.
BCM 200/400 configuration Field Value Description Enable Voice Activity Detection Voice Activity Detection (VAD), also known as silence suppression, identifies periods of silence in a conversation and stops sending IP speech packets during those periods. In a typical telephone conversation, most of the conversation is half-duplex, meaning that one person is speaking while the other is listening. If VAD is enabled, no voice packets are sent from the listener end.
Configuring local Gateway parameters 105 Step Action 1 Log on to Element Manager. 2 In the Task Navigation Panel, select the Configuration tab. 3 Select Resources > Telephony Resources. 4 In the Modules panel, select the line in which the Module Type column is set to IP Trunks. See Figure 58 "Telephony Resources" (page 101). 5 Select the IP Trunk Settings tab and enter the information that supports your system. See Figure 59 "IP Trunk Settings" (page 105).
BCM 200/400 configuration Field Value Description Send name display If enabled, the telephone name is sent with outgoing calls to the network. Remote capability MWI This setting must coordinate with the functionality of the remote system hosting remote voice mail. 6 For H.323 VoIP trunks, select the H.323 Settings tab. See Figure 60 "H.323 Settings" (page 106). Figure 60 H.323 Settings 7 When implementing your dialing plan, in the H.
Configuring local Gateway parameters 107 Applying the changes made to the Call Signaling Settings causes all H.323 calls to be dropped. It is recommended that you make changes to the Call Signaling Settings during off-peak hours or a scheduled maintenance window. Refer to Table 11 "H.323 Call Signaling Settings fields" (page 107). Table 11 H.323 Call Signaling Settings fields Field Value Description Call Signaling Direct Call signaling information is passed directly between H.323 endpoints.
BCM 200/400 configuration Field Value Description Backup Gatekeeper (s) NetCentrex Gatekeeper does not support RAS. Any backup Gatekeepers must be entered in this field. Gatekeepers that use RAS can provide a list of backup Gatekeepers for the endpoint to use in the event of a primary Gatekeeper failure. Alias names NAME: Enter the alias names of the BCM required to direct call signals to your system. Note: The Alias name is case sensitive.
Configuring target lines 109 Table 12 SIP Settings fields Field Value Description Fallback to Circuit-Switched Disabled Defines how you want the system to handle calls that the system fails to send over the VoIP trunk. Enabled-TDM Enabled-All Domain Name Enabled-TDM enables fallback for calls originating on digital telephones. This is useful if your IP telephones are connected remotely, on the public side of the BCM network, because PSTN fallback is unlikely to result in better quality of service.
BCM 200/400 configuration Figure 62 Parameters Table 13 Parameters fields Field Value Description Line Type Public If the line is to be shared among telephones, select Public. If the line is only assigned to one telephone, select DN:*:. DN:* Pub. Received # Confirm the existing number or enter a public received number (PSTN DID or PRI trunks) that the system uses to identify calls from the public network to the target line.
Configuring target lines 111 Figure 63 Preferences Table 14 Preferences fields Field Value Description Aux. ringer If your system is equipped with an external ringer, you can enable this setting so that this line rings at the external ringer. If Busy Busy tone To automatically direct calls to the prime telephone, select To prime. Otherwise, select Busy tone. To Prime Distinct rings in use Read only Indicates which ring patterns are already configured on this system.
BCM 200/400 configuration Figure 64 Assigned DNs 8 Edit the listed DNs, or click Add to add a DN as required. 9 Enter the appropriate information for your network. Refer to Table 18 "Assigned DNs fields" (page 117) for configuration information. —End— Configuring VoIP lines Voice over IP (VoIP) lines simulate traditional Central Office (CO) lines. VoIP lines transmit data over an IP network rather than over physical lines. Step Action 1 Log on to Element Manager.
Configuring VoIP lines 113 Figure 65 VoIP lines 6 Configure the Parameters tab appropriately for your network. Refer to Table 15 "VoIP line descriptions" (page 113) for configuration information. Table 15 VoIP line descriptions Field Value Description Line 001-060 Unique line number. Trunk Type VoIP Ensure that the trunk type is set to VoIP when configuring VoIP lines. Control Set Identify a DN if you are using this line with scheduling. To change the DN, double-click the Control Set DN.
BCM 200/400 configuration Field Value Line Type Description Defines how the line is used in relation to other lines in the system. Distinct Ring 7 Public If the line is to be shared among telephones, set to Public. DN:* If the line is assigned to only one telephone, set to DN:*. Pool [A to O] If you are using routing, put the line into line pool (A to F). If you are using line pools, configure the target lines. If your system uses both H.323 and SIP trunks, assign H.
Configuring VoIP lines 115 Table 16 Preferences fields Field Value Description Auto privacy Defines whether one BCM user can select a line in use at another telephone to join an existing call. For more information, see BCM 4.0 Device Configuration Guide (N0060600). Full autohold Enables or disables Full autohold. When enabled, if a caller selects an idle line but does not dial any digits, that line is automatically placed on hold if the caller selects another line.
BCM 200/400 configuration Table 17 Restrictions fields Field Value Description Use remote package < package #> If the line is used to receive external calls or calls from other nodes on the private network, ensure that you indicate a remote package that provides only the availability that you want for external callers. This attribute is typically used for tandeming calls.
Configuring VoIP lines 117 Refer to Table 18 "Assigned DNs fields" (page 117) for configuration information. Table 18 Assigned DNs fields Field Value DN Appearance Type Description Unique number Ring only Appr&Ring Select Appr Only or Appr&Ring if the telephone has an available button. Otherwise select Ring Only. Appr only Appearances Target lines can have more than one appearance to accommodate multiple calls. For telephones that have these lines set to Ring Only, set to None.
BCM 200/400 configuration Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
BCM 50/450 configuration This chapter describes configuration procedures for the Business Communications Manager (BCM) 50 and 450 systems. Element Manager as viewed on your system may differ slightly from the screens shown in this chapter because you can customize the column display in Element Manager.
BCM 50/450 configuration Figure 69 Keycodes 4 Load new Keycodes by loading a new keycode file or connecting to Nortel’s Keycode Retrieval System (KRS). For more information about keycodes and keycode retrieval, see Keycode Installation Guide (NN40010-301). —End— Verifying system license and keycodes Perform the following procedure to verify system license and keycodes. Verifying system license and keycodes Step Action 1 Log on to Element Manager.
Configuring VoIP trunk media parameters 4 121 In the Name column, scroll down to VoIP GW Trunk. The number of license keys you have are listed in the Data column. —End— Configuring VoIP trunk media parameters Perform the following procedure to configure VoIP trunk media parameters. Configuring VoIP trunk media parameters Step Action 1 Log on to Element Manager. 2 In the Task Navigation Panel, select the Configuration tab. 3 Select Resources > Telephony Resources.
BCM 50/450 configuration 5 Select the H.323 Media Parameters or SIP Media Parameters tab. 6 Enter the information that supports your system. Ensure that these settings are consistent with the other systems on your network. Refer to Table 19 "H.323 Media Parameters fields" (page 122) and Table 20 "SIP Media Parameters fields" (page 123) for a description of the parameters. —End— Table 19 H.323 Media Parameters fields Field Value Description Preferred Codecs G.
Configuring VoIP trunk media parameters 123 Field Value Description Jitter Buffer Auto Select the size of jitter buffer for your system. None Note: Slower networks require larger Jitter Buffers to decrease voice break up, but increase end-to-end delay. Small Medium Large G.729 payload size (ms) 10,20,30,40,50,60 Set the maximum required payload size, per codec, for the VoIP calls sent over SIP trunks. G.723 payload size (ms) 30 G.
BCM 50/450 configuration Field Value Description G.723 Performance note: Codecs on all networked BCMs must be consistent to ensure the proper functionality of interacting features such as Transfer and Conference. Systems running BCM Release 3.5 or later allow codec negotiation and renegotiation to accommodate inconsistencies in codec settings over VoIP trunks.
Configuring local Gateway parameters Field Value 125 Description the fax machine. To minimize the possibility of your VoIP calls being dropped due to fax tone interference: • place the fax machine away from other telephones • turn the fax machine’s speaker volume to the lowest level, or off, if available Configuring local Gateway parameters Perform the following procedure to configure local Gateway parameters. Configuring local Gateway parameters Step Action 1 Log on to Element Manager.
BCM 50/450 configuration Figure 71 H.323 Settings 6 When implementing your dialing plan, in the H323 Settings tab, select a value for Fall back to circuit-switched. This determines how the system handles calls if the IP network cannot be used. 7 For Gateway protocol, select CSE. 8 Scroll down to Alias names and click Modify. The Modify Call Signaling Settings page appears. 9 Enter the information that supports your system. Applying the changes made to the Call Signaling Settings causes all H.
Configuring local Gateway parameters 127 Table 21 H.323 Call Signaling Settings fields Field Value Description Call signaling Direct Call signaling information is passed directly between H.323 endpoints. You must set up remote Gateways. Gatekeeper Resolved All call signaling occurs directly between H.323 endpoints. This means that the Gatekeeper resolves the phone numbers into IP addresses, but the Gatekeeper is not involved in call signaling.
BCM 50/450 configuration Field Value Description Alias names NAME: Enter the alias names of the BCM required to direct call signals to your system. Note: The Alias name is case sensitive. It must match the name configured in NRS. Registration TTL(s) 10 Specifies the keep-alive interval. For SIP trunks, select the SIP Settings tab. See Figure 72 "SIP Settings" (page 128). Figure 72 SIP Settings 11 Enter the information that supports your system.
Configuring local Gateway parameters 129 Table 22 SIP Settings fields Field Value Description Fallback to circuit-switched Disabled Defines how you want the system to handle calls that the system fails to send over the VoIP trunk. Enabled-TDM Enabled-All Local Domain Enabled-TDM enables fallback for calls originating on digital telephones.
BCM 50/450 configuration Field Value Description Keep Alive If ’none’ then the server will always be considered to be alive. If OPTIONS then a SIP OPTIONS ping is used to determine responsiveness. Figure 73 SIP Proxy Tab —End— Configuring VoIP lines Voice over IP (VoIP) lines simulate traditional Central Office (CO) lines. VoIP lines transmit data over an IP network rather than over physical lines. Configuring VoIP lines Step Action 1 Log on to Element Manager.
Configuring VoIP lines 3 Select Telephony > Lines > All Lines. 4 Highlight the individual line you wish to configure. 5 Select the Preferences tab. See Figure 74 "Preferences" (page 131). 131 Figure 74 Preferences 6 Configure the Preferences tab appropriately for your network. Refer to Table 24 "Preferences fields" (page 131) for configuration information. Table 24 Preferences fields Field Value Description Aux.
BCM 50/450 configuration Figure 75 Restrictions 8 Configure the Restrictions tab appropriately for your network. Refer to Table 25 "Restrictions fields" (page 132) for configuration information. Table 25 Restrictions fields Field Value Description Use remote package < package #> If the line is used to receive external calls or calls from other nodes on the private network, ensure that you indicate a remote package that provides only the availability that you want for external callers.
Configuring VoIP lines 9 In the Task Navigation Panel, in the Configuration tab, select Telephony > Sets > All DNs. 10 Highlight the individual line you wish to configure. 11 Select the Line Assignment tab. See Figure 76 "Line Assignment" (page 133). 133 Figure 76 Line Assignment 12 Edit the listed DNs, or click Add to add a DN as required. 13 Enter the appropriate information for your network. Refer to Table 26 "Assigned DNs fields" (page 133) for configuration information.
BCM 50/450 configuration Field Value Description Caller ID Set When enabled, displays caller ID for calls coming in over the target line. Vmsg Set When enabled, an indicator appears on the telephone when a message is waiting from a remote voice mail system. Check with your system administrator for the system voice mail setup before changing this parameter.
Configuring target lines 135 Figure 77 Preferences Table 27 Preferences fields Field Value Description Aux. ringer If your system is equipped with an external ringer, you can enable this setting so that this line rings at the external ringer. If Busy Busy tone To automatically direct calls to the prime telephone, select To prime. Otherwise, select Busy tone.
BCM 50/450 configuration Figure 78 Assigned DNs 7 Edit the listed DNs, or click Add to add a DN as required. 8 Enter the appropriate information for your network. Refer to Table 18 "Assigned DNs fields" (page 117) for configuration information. —End— Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
Testing and troubleshooting This chapter contains procedures to test and troubleshoot your Communication Server 1000/Business Communications Manager (BCM) integration.
Testing and troubleshooting Testing the integration from the BCM system Step Action 1 Log on to Element Manager on the BCM system. 2 Select Resources > Telephony Resources. See Figure 79 "Status" (page 139). Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
Testing 139 Figure 79 Status 3 In the Actual Type column, highlight IP Trunks. 4 In the bottom half of the page, select the H323 Settings tab. Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager NN43001-326 02.01 Standard Release 5.5 3 April 2009 Copyright © 2009, Nortel Networks .
Testing and troubleshooting 5 Scroll down to the Status bar to determine if the two systems are successfully registered. —End— Testing the integration from the CS 1000 system To determine if the two systems are registered from the CS 1000 side, check the status of the endpoints. Refer to the procedure "Checking the status of registered endpoints" (page 95). Troubleshooting Refer to these troubleshooting procedures to resolve common integration issues.
Troubleshooting 141 If not, ensure that the BCM and NRS can communicate with each other. 2 Check that the line is configured for outgoing calls. DNs need to have lines configured for both incoming and outgoing calls. Check your networks dialing plan or see Dialing Plans: Description (553-3001-183). 3 Verify that the dialing plan has been properly implemented on both the CS 1000 and BCM. For more information about dialing plans, see Dialing Plans: Description (553-3001-183).
Testing and troubleshooting If unsuccessful, check your network settings. Note that the NRS does not respond to pings. 2 In the H323 Settings tab for IP trunks under Resources > Telephony Resources, verify that the BCM includes its alias name as “NAME:aliasname”. 3 Verify that the Alias names match on the NRS and BCM. 4 In the H323 Settings tab for IP trunks under Resources > Telephony Resources, make sure the Gateway protocol is set to CSE. 5 Verify that the NRS has the proper routing entries.
Enterprise: Common Solution Integration Guide for Communication Server 1000 Release 5.5/Business Communications Manager Copyright © 2009, Nortel Networks All Rights Reserved. Publication: NN43001-326 Document status: Standard Document version: 02.01 Document date: 3 April 2009 To provide feedback or report a problem in this document, go to www.nortel.com/documentfeedback.
