Page 1 Networking Configuration Guide BCM50 2.0 Business Communications Manager Document Status: Standard Document Number: NN40020-603 Document Version: 01.06 Date: December 2007...
Page 2 Nortel Networks. Trademarks Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks. Microsoft, MS, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation. All other trademarks and registered trademarks are the property of their respective owners.
Page 3: Table Of Contents
List of procedures List of procedures Getting started with BCM ........25 System telephony networking overview .
Page 4 List of procedures To configure BRI T-loop parameters ................197 To configure provisioned BRI line features..............198 Programming BRI S-loops, lines, and ISDN devices ....201 To set BRI properties for ISDN device connections ............202 Configuring CLID on your system .
Page 5 List of procedures To set Loop avoidance during hardware configuration..........335 Private networking: Using destination codes ..... 339 Private networking: PRI Call-by-Call services ..... 343 Configuring voice messaging .
Page 6 List of procedures Media Gateways panel ........413 Call security and remote access .
Page 7 List of procedures Firewall configuration resources ....... . 495 Dial Up overview ..........497 Dial Up Interfaces panel .
Page 8 List of procedures NN40020-603 NN40020-603...
Page 9 Getting Help from the Nortel Web site ....... . .
Page 10 Contents Naming convention ..........62 Application level differences .
Page 11 Contents Programming line access ..........98 Making lines available .
Page 12 Contents Chapter 13 Configuring lines: T1-E&M ........151 Configuring E&M line features .
Page 13 Contents Chapter 22 Configuring CLID on your system ....... 205 Programming incoming CLID .
Page 14 Contents Setting up VoIP trunks for fallback ........244 Chapter 25 Dialing plan: Routing configurations .
Page 15 Contents ETSI-specific network features ........286 Outgoing private calls routing .
Page 16 Contents Chapter 35 Private networking: PRI and VoIP tandem networks ....323 Routing for tandem networks ......... . . 323 Routing calls through a tandem network .
Page 17 Contents Chapter 42 VoIP overview..........363 IP telephones .
Page 18 Contents Deactivating the VoIP schedule ........396 Example: A private network configured for fallback .
Page 19 Contents Chapter 53 Call Security: Configuring Direct Inward System Access (DISA) ..427 Remote access overview ..........427 Setting up remote access on lines .
Page 20 Contents MTU option ........... . . 456 Main panel tabs: Internal subnets .
Page 21 Contents Chapter 66 DHCP Server Settings panel ........481 Main panel tabs: General Settings .
Page 22 Contents Creating an automatic dial-out interface ....... 521 Guidelines for using remote Dial-in ........522 Using a dial-up interface as a primary connection .
Page 23 Contents Codec rates..........549 Index .
Page 24 Contents NN40020-603 NN40020-603...
Page 25: Getting Started With Bcm
The Networking Configuration Guide is directed to installers who install, configure, and maintain BCM systems. To use this guide, you must: • be an authorized BCM installer or administrator within your organization • know basic Nortel BCM terminology • be knowledgeable about telephony and IP networking technology Networking Configuration Guide...
Page 26: Acronyms
Chapter 1 Getting started with BCM Acronyms The following is a list of acronyms used in this guide. Table 1 Acronyms Acronym Description Analog station module analog terminal adapter Basic Rate Interface Business Communications Manager Central Answering Position Contact Center CLID Calling Line Identification Class of Service...
Page 27 Chapter 1 Getting started with BCM BCM features BCM50 supports the complete range of IP telephony features offered by existing BCM products: Note: You enable the following features by entering the appropriate keycodes (no additional hardware is required). • VoIP Gateway (H.323 and SIP): Up to 12 VoIP trunks •...
Page 28: Symbols And Conventions Used In This Guide
Chapter 1 Getting started with BCM Symbols and conventions used in this guide These symbols are used to highlight critical information for the BCM system: Caution: Alerts you to conditions where you can damage the equipment. Danger: Alerts you to conditions where you can get an electrical shock. Warning: Alerts you to conditions where you can cause the system to fail or work improperly.
Page 29: Related Publications
This section provides a list of additional documents referred to in this guide. There are two types of publications: Technical Documents on page 29 and User Guides on page 30. Technical Documents System Installation BCM50 2.0 Installation and Maintenance Guide (NN40020-302) Keycode Installation Guide (NN40010-301) System Programming Administration Guide (NN40020-600) Networking Configuration Guide...
Page 30 Chapter 1 Getting started with BCM Device Configuration Guide (NN40020-300) Telset Administration Guide (NN40020-604) BCM50a Integrated Router Configuration — Basics (N0115790) BCM50a Integrated Router Configuration — Advanced (N0115791) BCM50e Integrated Router Configuration — Basics (N0115788) BCM50e Integrated Router Configuration — Advanced (N0115789) Telephones and Peripherals Telephony Device Installation Guide (NN40020-309) Digital Mobility...
Page 31: How To Get Help
Getting Help over the telephone from a Nortel Solutions Center If you have a Nortel support contract and cannot find the information you require on the Nortel Support Web site, you can get help over the telephone from a Nortel Solutions Center.
Page 32: Getting Help Through A Nortel Distributor Or Reseller
Getting Help through a Nortel distributor or reseller If you purchased 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. NN40020-603...
Page 33: System Telephony Networking Overview
Chapter 2 System telephony networking overview The system supports both public and private networking for telephony traffic. • The public network is created by PSTN trunk connections from a Central Office terminating on a telephone system such as the BCM. •...
Page 34 Chapter 2 System telephony networking overview Figure 1 PBX system Lines are assigned to a line pool CO line 1 CO line 2 All telephones CO line 3 are assigned CO line 4 access to the line pool for outgoing calls Receptionist Assigned all lines/...
Page 35 Chapter 2 System telephony networking overview Figure 2 DID system Target line mapped to DN (4005) CO DID line Target line mapped to i.e. 769 DN (4006) with range of call numbers (4005 to 4020) Target line mapped to Target line mapped to DN (4007) DN (4008) Incoming calls...
Page 36: Tandem Calling To A Remote Pstn
Chapter 2 System telephony networking overview Tandem calling to a remote PSTN A system connected to a private network that uses dedicated circuits or VoIP circuits can allow a user to dial directly to many other users, on different nodes, using a coordinating dialing plan. Using a private network saves on toll charges, and local charges, as fewer PSTN accesses are required for internal and external calling.
Page 37: Private Network Parameters
DNs. Private network parameters The following provides an overview of the system values that affect private networking. Private networking protocols The BCM supports the following protocols for private networking: • PRI: ETSI QSIG, Nortel Voice Networking (MCDN) Networking Configuration Guide...
Page 38 You must purchase and install these keycodes before you can create any of the networks described in this chapter. Consult with your Nortel distributor to ensure you order the correct keycodes for the type of network you want to create.
Page 39: Lines Used For Networking
External (trunk) lines provide the physical connection between BCM and other systems in a private or public network. The BCM50 numbers physical lines from 061 to 124. Default numbering depends on the type and connection to the BCM (EXP1 - EXP2).
Page 40: Routing-Based Networks Using T1 E&M Lines
Chapter 2 System telephony networking overview • “PRI networking using Call-by-Call services” on page 41 • “PRI SL-1/Q.Sig/DPNSS and VoIP trunk networking” on page 42 Routing-based networks using T1 E&M lines By properly planning and programming routing tables and destination codes, an installer can create a dialing plan where T1 E&M lines between BCM systems are available to other systems in the network Figure 4...
Page 41: Pri Networking Using Call-By-Call Services
Chapter 2 System telephony networking overview The call appears on the auto answer line on the BCM in Santa Clara as 6-221. Because 6 is programmed as a destination code for Toronto on the Santa Clara system, another call is placed using route 002 from Santa Clara to Toronto.
Page 42: Pri Sl-1/Q.sig/Dpnss And Voip Trunk Networking
Chapter 2 System telephony networking overview Figure 5 PRI networking using Call-by-Call Services New York office Toronto office Network # 2221 Network # 6221 Received # 2221 Received # 6221 Internal # 2221 Internal # 6221 DID # 763-2221 DID # 562-6221 TIE Connection Public Network Central...
Page 43: System Dialing Plans
PSTNs for all the nodes on the network. Note: A keycode is required to use the Nortel Voice Networking functionality which is referred to as SL-1 in the BCM Element Manager.
Page 44 Chapter 2 System telephony networking overview Routing for tandem networks In tandem networks, each node needs to know how to route calls that do not terminate locally. To do this, you set up routes for each connecting node by defining destination codes for each route. If the node is also connected to the public network, the usual routing is required for that connection.
Page 45 Chapter 2 System telephony networking overview Table 1 Node A destination code table, external termination Route Absorb length Destination code (public DNs) 4 (PSTN) 91604 3 (Node B) 91403762 (Node B) 3 (Node B) 91403765 (Node E) 4 (PSTN) 9140376* (not internal network) 4 (PSTN) 914037* (not internal network) 4 (PSTN)
Page 46: Understanding Nortel Voice Networking (Mcdn) Network Features
392 (Node B) 5 (Node A) 395 (Node E) Understanding Nortel Voice Networking (MCDN) network features When you connect your BCM systems through PRI-SL-1/ETSI QSIG/DPNSS or VoIP trunks, and activate the MCDN protocol, your network provides a number of network call features. You can use this protocol to network other BCM systems, such as the tandem system shown in “Creating...
Page 47: Isdn Call Connection Limitation
Chapter 2 System telephony networking overview Figure 6 Network call redirection path Meridian 1 with Meridian Mail SL-1 MCDN Telephone A Original call Telephone B Call forwarded to Meridian Mail ISDN Call Connection Limitation The ICCL (ISDN Call Connection Limitation) feature piggybacks on the call initiation request and acts as a check at transit PBX points to prevent misconfigured routes or calls with errors from blocking channels.
Page 48: Trunk Route Optimization
Chapter 2 System telephony networking overview Figure 7 Call loop on system without ICCL Meridian 1 Meridian 1 Telephone A Trunk Route Optimization Trunk Route Optimization (TRO) finds the most direct route through the network to send a call between nodes. This function occurs during the initial alerting phase of a call. To set BCM configurations: •...
Page 49: Trunk Anti-Tromboning
Chapter 2 System telephony networking overview Figure 8 Call paths with and without TRO Telephone B Meridian 1 Meridian 1 PRI SL-1 PRI SL-1 PRI SL-1 Original call (no TRO) Forwarded call (no TRO) Telephone A Telephone C Call path with TRO Trunk Anti-tromboning Trunk Anti-Tromboning (TAT) is a call-reroute feature that works to find better routes during a transfer of an active call.
Page 50: Networking With Etsi Qsig
Chapter 2 System telephony networking overview Figure 9 Call paths with and without TAT Telephone C Telephone A Telephone B Forwarded call (no TAT) Forwarded call (using TAT) Networking with ETSI QSIG (International systems only) ETSI QSIG is the European standard signaling protocol for multi-vendor peer-to-peer communications between PBX systems and/or central offices.
Page 51: Etsi Euro Network Services
Chapter 2 System telephony networking overview Figure 10 ETSI QSIG networking Network # 2221 Network # 6221 Received # 2221 Received # 6221 Internal # 2221 Internal # 6221 PRI/BRI PRI/BRI ETSI QSIG ETSI QSIG BCM West end branch BCM East end branch DN 4221 Central Office...
Page 52: Dpnss 1 Services
Chapter 2 System telephony networking overview When the features are activated, users can: • display a call charge • redirect calls over the ETSI ISDN BRI/PRI line to the outside network • tag malicious calls Advice of Charge-End of Call (AOCE) — AOCE is a supplementary service available from your service provider on ETSI ISDN BRI/PRI links.
Page 53: Dpnss 1 Capabilities
Chapter 2 System telephony networking overview DPNSS 1 capabilities A single BCM node, acting as a terminating node on the network, supports the following capabilities over DPNSS 1 lines: • Direct Dial Inward (DDI) for incoming calls. • Originating Line Identification (OLI) for incoming and outgoing calls: —...
Page 54 Chapter 2 System telephony networking overview • “Call Offer” on page 58 • “Route Optimization” on page 59 • “Loop avoidance” on page 59 • Message Waiting Indication The following parameters can be configured for DPNNS 1 lines: • Line type •...
Page 55: Making A Conference Call
Chapter 2 System telephony networking overview Making a conference call To initiate or disconnect from a conference call on a BCM system over DPNSS 1, use the procedure described in the Device Configuration Guide (NN40020-300) Note: Three Party Service is supported on model 7000 telephones, but in a receive-only fashion.
Page 56 Chapter 2 System telephony networking overview Follow-me diversion can be cancelled from the forwarded location. • Diversion on Busy and Diversion on No Reply cannot be cancelled from the forwarded telephone. These are programmable only by an installer and not by the user. •...
Page 57 When the ICL of the intruding telephone is higher than the IPLs of both telephones on the active call, EI occurs. Nortel recommends that you set the IPLs of most BCM telephones to the default of None, or Low or Medium.
Page 58 Chapter 2 System telephony networking overview Call Offer Call Offer over DPNSS 1 allows a calling party to indicate to the wanted party that there is an incoming call available, even though there is no answer button available to present the call on the telephone.
Page 59 Chapter 2 System telephony networking overview • Reject it. If the user activates Do Not Disturb on Busy (DND) when the Call Offer request is made, the request is removed from the telephone. The calling party is informed of the rejection.
Page 60: Private Networking With Dpnss
Chapter 2 System telephony networking overview Private networking with DPNSS (International only) DPNSS supports the Universal Dialing Plan (UDP), an international standard for sending and receiving private numbers over networks. The UDP requires that a dialing number include the following: •...
Page 61: Bri Euro Protocol
Chapter 2 System telephony networking overview Figure 11 DPNSS networking Private Network DPNSS DPNSS Terminating BCM Site C BCM Site A DN # 3333 DN # 111 LOC # 496 LOC # 244 DPNSS DPNSS Meridian M1 LOC # 563 BCM Site D BCM Site B DN # 2229...
Page 62: Naming Convention
Chapter 2 System telephony networking overview Naming convention Choose the protocol type for consistency with PRI trunk configuration. The PRI protocol type can be either User (Slave) or Network (Master). The BRI protocol type can be extended with T-T (Network). You can connect two BCMs through a BRI link. S-T refers to a far end which has an S interface (Line in M1 terminology).
Page 63: Telephony Programming: Configuring Call Traffic
Chapter 3 Telephony programming: Configuring call traffic Telephony call traffic has a number of configuration requirements. Some configuration is common to both incoming and outgoing traffic. Other settings are specific to the call direction. In the case of private networking, call configuration becomes more complex, as remote systems send calls over the private network to other nodes or to your system PSTN network and your local PSTN handles calls directed to remote nodes through your system.
Page 64 Chapter 3 Telephony programming: Configuring call traffic Figure 12 Telephony system and device programming Although many of the tasks involved in programming both areas can be performed in any order, work flow falls generally in the following order: • Module configuration/VoIP trunk gateways —...
Page 65 Chapter 3 Telephony programming: Configuring call traffic • Line configuration/target line configuration — “BRI ISDN: BRI loop properties” on page 187 — “BRI ISDN: BRI T-loops” on page 195 — “Programming BRI S-loops, lines, and ISDN devices” on page 201 —...
Page 66: Incoming Calls
Chapter 3 Telephony programming: Configuring call traffic Figure 13 Dialing plan configuration — “Dialing plan: System settings” on page 267 — “Dialing plan: Public network” on page 275 — “Dialing plan: Line pools and line pool codes” on page 357 —...
Page 67 Chapter 3 Telephony programming: Configuring call traffic Figure 14 Incoming call configuration - part A Networking Configuration Guide...
Page 68 Chapter 3 Telephony programming: Configuring call traffic Figure 1 Figure 1 Figure 15 Incoming call configuration - part B NN40020-603 NN40020-603...
Page 69 Chapter 3 Telephony programming: Configuring call traffic Figure 16 Configuring incoming call controls Networking Configuration Guide...
Page 70: Outgoing Calls
Chapter 3 Telephony programming: Configuring call traffic Outgoing calls For outgoing calls, you can assign one or more intercom keys to directly link to a line pool or prime line, or allow line pool access codes, destination codes, or internal system numbers to direct the call.
Page 71 Chapter 3 Telephony programming: Configuring call traffic Figure 17 Configuring outgoing call traffic (Sheet 1 of 2) Networking Configuration Guide...
Page 72 Chapter 3 Telephony programming: Configuring call traffic Figure 18 Configuring outgoing call traffic (Sheet 2 of 2) NN40020-603 NN40020-603...
Page 73: Application Resources Overview
Chapter 4 Application Resources overview Application Resources is a management tool for allocating system resources such as signalling channels, VDI channels, media channels, and DSP resources. While the BCM manages resources for different services by making resources available as they are needed, you can manage the resources by setting minimums and maximums for each service.
Page 74: Setting Values For Application Resources
Chapter 4 Application Resources overview Setting values for application resources For all applications, you can modify the minimum and maximum values. The minimum values reflect the number of resources that will always be reserved for a particular application, while the maximum reflects the maximum instances of an application the system will allow at once.
Page 75: Sip Trunks
Chapter 4 Application Resources overview Voice mail and CC resources These resources require DSP resources. Because there is often a slight delay in allocating DSP resources, you may want to set the minimum to 2 or more. This setting generally ensures that there is no delay occurs in setting up the application.
Page 76 Chapter 4 Application Resources overview NN40020-603 NN40020-603...
Page 77: Application Resources Panel
Chapter 5 Application Resources panel The application resources panel allows you to modify resources allocated to applications on the BCM. While the panel tracks four types of resources, DSP resources are generally the only type of resources that affect performance on the BCM. For more information on planning your application resources, see “Application Resources overview”...
Page 78 Chapter 5 Application Resources panel Figure 19 Application resources panel Table 8 Application Resources panel (Sheet 1 of 3) Attribute Value Description Total Resources Signalling channels <read-only> The total number of signalling channels on the system. VDI channels <read-only> The total number of VDI channels on the system. Media channels <read-only>...
Page 79 Chapter 5 Application Resources panel Table 8 Application Resources panel (Sheet 2 of 3) Attribute Value Description VDI channels <read-only> The number of VDI channels in use on the system. This number can change based on the values entered for applications, and on the those applications currently in use.
Page 80 Chapter 5 Application Resources panel Table 8 Application Resources panel (Sheet 3 of 3) Attribute Value Description Details for Application Current minimum <read-only> The current minimum assigned for an application. assigned limit Current maximum <read-only> The current maximum assigned for an application. assigned limit Note <read-only>...
Page 81: Module Configuration: Trunk Modules
Chapter 6 Module configuration: Trunk modules This following describes the Element Manager headings that define and control the settings for the trunk media bay modules installed on your system. The following paths indicate where to access the trunk modules in Element Manager and through Telset Administration: •...
Page 82 Chapter 6 Module configuration: Trunk modules Figure 20 Fitting the procedure into the overall picture NN40020-603 NN40020-603...
Page 83: To Define The Modules To The System
Chapter 6 Module configuration: Trunk modules Configuring the trunk module parameters Modules automatically configure to a free bus when they are connected to the system. • That bus determines what line numbers are supported by the module. • Module programming determines the type of line. •...
Page 84 Chapter 6 Module configuration: Trunk modules Warning: Changing the clock source may disconnect calls. If you change the clock source for your system, you may cause your system DTM interface(s) to reset, resulting in dropped calls. Choose a suitable time to change the clock source and use the Page feature to inform users of possible service disruptions.
Page 85 Chapter 6 Module configuration: Trunk modules • NSF Extension: None (DMS-100/250 switches); WATS (Siemens, ESWD, Lucent 5ESS switches); ALL (GTD5 and DMS-10 switches). • B-channel selection sequence: choose how B-channel resources are selected for call processing. • Clock Source: Determine how the module functions for timing on the network (Primary External, Secondary External, Internal) Warning: Changing the clock source may disconnect calls.
Page 86 Chapter 6 Module configuration: Trunk modules Configuring DASS2 module parameters • Clock Source: Determine how the module functions for timing on the network (Primary External, Secondary External, Internal) Warning: Changing the clock source may disconnect calls. If you change the clock source for your system, you may cause your system DTM interface(s) to reset, resulting in dropped calls.
Page 87: Managing Modules
Chapter 7 Managing modules When you need to find out information about a module, you can determine the status of any of the settings under the media bay module headings. To correct a problem or change a module setting, you may need to enable or disable a bus/module or select ports on the module. Refer to the following procedures: •...
Page 88: Trunk Module Metrics
Chapter 7 Managing modules Figure 21 Set Port Details Note: A trunk media bay module has no changeable settings on the Trunk Port Details record. Trunk module metrics To view the current status of the module trunks, you can use the Telephony Metrics – Trunk Modules Metrics panel.
Page 89: Lines Overview
“Line Job Aids” on page 94 Other line configuration options or requirements: • BRI loops require configuration and provisioning before the BRI lines can be configured. • The BCM50 does not support the DDIM (Digital Drop Insert MBM). Networking Configuration Guide...
Page 90: Understanding How The System Identifies Lines
Chapter 8 Lines overview Understanding how the system identifies lines On a new system, lines and loops are numbered and assigned defaults based on the type of media bay modules that have been connected to the system. The exception are the VoIP trunks, which require a keycode to activate.
Page 91 Chapter 8 Lines overview Target lines Target lines are internal communications paths that directly connect auto-answer trunks to system telephones. These lines are incoming only. Target lines allow you to make more efficient use of DID line resources.You can map a range of target lines for each DID line.
Page 92: Bri Loops Programming
Chapter 8 Lines overview Physical lines Physical lines are the central office (CO) trunks assigned to the trunk media bay modules. See the Installation and Maintenance Guide (NN40020-302) for information about which lines are enabled. You can change the line types to suit your system. For instance, BRI and DTM modules can be designated to a number of line types, depending on the type of line service provided through the central office (CO).
Page 93: Line Record
Chapter 8 Lines overview Line record The line record allows you to: • Identify the line and the features on the line. • Assign restrictions for outgoing calls. • Assign a voice message center, if the line connects to a remote voice-mail system, either on another node on the private network or at the central office.
Page 94: Remote Restrictions
Chapter 8 Lines overview Programming links The template has a set of default restrictions in Restriction 02 only. You must create your own restriction files if you want to use other settings. Remote restrictions Your system can accommodate users who call in from outside the system to access system features.
Page 95: Determining Line Numbers And Destination Codes
Chapter 8 Lines overview • “Using loss packages” on page 97 • “Turn Privacy on or off for a call” on page 98 Determining line numbers and destination codes Refer to Table 11 for a list of lines assigned per bus (DS30 bus and offset), based on the module type configured with that address.
Page 96: Line Pool Tips
Chapter 8 Lines overview Table 11 Line numbering for modules and VoIP DS30 Type of module Line/Loop numbers (default) Line Access codes pool and routes A-O/Bloc VoIP trunks (no module) 001-048 Integrated BRI loops (2) 061-064 05 /06 Expansion 1 DID4 65-68 DID8...
Page 97: Using Loss Packages
Chapter 8 Lines overview • Avoid putting unsupervised loop start lines in a line pool. These lines can become unusable, especially when a remote user uses the line pool to make an external call. • To assign line pool access to telephones, select Configuration > Telephony > Dialing Plan > Line Pools.
Page 98: Turn Privacy On Or Off For A Call
Chapter 8 Lines overview Turn Privacy on or off for a call You can configure lines in your system to have automatic privacy. With a line not programmed with privacy, anyone with the line assigned to their telephone can join your call by pressing the line button.
Page 99: Incoming Calls
Chapter 8 Lines overview • Voice over IP (VoIP) trunks use the data network to provide line service in and out of the system. VoIP trunk configuration is described in the. VoIP trunks use target lines for incoming calls, and require line pool codes or destination codes for outgoing calls. •...
Page 100 Chapter 8 Lines overview NN40020-603 NN40020-603...
Page 101: Configuring Telephony Resources
“Provisioning module lines/loops” on page 112 “IP telephones” on page 112 “IP Terminal Global Settings” on page 113 “Registering Nortel IP telephones” in the Telephony Device Installation Guide (NN40020-309) “IP telephone set details” on page 114 “Voice over IP trunks” on page 115 “Configuring VoIP trunk gateways”...
Page 102: Telephony Resources Table
Chapter 9 Configuring telephony resources The top frame of this panel displays a table showing each type of module and the VoIP trunks that are assigned to the system, either through connections to a media bay module or by applying the required keycodes (VoIP trunks).
Page 103 Chapter 9 Configuring telephony resources The Telephony Resources table fields are described in Table Table 13 Telephony Resources table fields (Sheet 1 of 2) Attribute Value Description Location <read-only> Module type <read-only> This field indicates the type of module assigned to each location.
Page 104: Media Bay Module Panels
Chapter 9 Configuring telephony resources Table 13 Telephony Resources table fields (Sheet 2 of 2) Attribute Value Description Busy This field indicates the current activity for the devices or lines attached to the module. Media bay module panels The following panel tabs appear when you select a module table entry on the Telephony Resources panel.
Page 105 Chapter 9 Configuring telephony resources Table 14 Module parameters values (Sheet 2 of 4) Attribute Value Module/line type • DS/CLID: displays for old North American LS/DS or CLID analog trunk modules, the old analog MBM, or the GATM with North American DIP switch settings. •...
Page 106 Chapter 9 Configuring telephony resources Table 14 Module parameters values (Sheet 3 of 4) Attribute Value Module/line type Disconnect 60, 100, 260, 460, or Loop timer 600 milliseconds Specify the duration of an Open Switch Interval (OSI) before a call on a supervised external line is considered disconnected.
Page 107 Chapter 9 Configuring telephony resources Table 14 Module parameters values (Sheet 4 of 4) Attribute Value Module/line type T1 parameters CO fail Specify a carrier failure standard (T1A-5474, TR62411) Interface levels ISDN, PSTN Define a loss plan setting. For more information, see “Interface levels”...
Page 108: Call-By-Call Service Selection
Chapter 9 Configuring telephony resources The ISDN setting requires digital access lines (DAL) that have digital network loss treatment. On a DAL network, the PBX system administers the dB loss, not the CO. DALs may have ISDN signaling or digital signaling (for example, T1). The loss plan follows the Draft TIA-464-C loss plan, which uses a send loudness rating (SLR) of 8 dB.
Page 109 Chapter 9 Configuring telephony resources Figure 24 Call-by-Call Service Selection subpanel Table 15 describes the fields shown on the Call-by-Call Service Selection tab panel. Table 15 Call-by-Call Service selection panel fields Attribute Value Description Service Type Foreign Exchange Refer to “CbC services available by switch protocol”...
Page 110: Port Details
Chapter 9 Configuring telephony resources CbC services available by switch protocol Table 16 lists the applicable services for the protocol defined on the Module record. Table 16 Services available for each PRI protocol Services Available Foreign Switched Nine Hundred Protocol Exchg Inwats (800) Intl-800...
Page 111 Chapter 9 Configuring telephony resources Figure 26 Trunk module Port Details panel. Table 17 describes the fields shown on the Port Values tab panel. Table 17 Port Values tab Attribute Value Module type Port # Read-only All modules • These are the port numbers of the physical device. Device type Read-only All modules...
Page 112: Provisioning Module Lines/Loops
Chapter 9 Configuring telephony resources Provisioning module lines/loops You can access three provisioning subpanels in Element Manager at by clicking Configuration > Resources > Telephony Resources. The tabbed provisioning panel that appears depends on the type of module that is selected on the Telephony Resources table. The provisioning subpanels are as follows: •...
Page 113: Ip Terminal Global Settings
Chapter 9 Configuring telephony resources IP Terminal Global Settings The parameters on the IP Terminal Global Settings subpanel affect all Nortel 1120/1140/20XX IP telephones. This is also the panel you use to allow these telephones to register to the system, and to turn off registration once you have registered all the telephones.
Page 114: Ip Telephone Set Details
Default: 20 IP telephone set details After a Nortel 1120/1140 or 20XX IP telephone registers with the system, this panel displays the terminal parameters. The telephone is identified to the system by its IP address, so this cannot be changed. If you need to change the IP address of a telephone, you need to deregister the telephone and then register it again with the new IP address.
Page 115: Voice Over Ip Trunks
Chapter 9 Configuring telephony resources Figure 28 IP Terminal Details (Telephony Resources) subpanel Table 20 describes the fields on this panel. Table 20 IP terminal fields Field Value Description IP Address <read-only> If the telephone is using DHCP or partial DHCP, this may vary. <DN>...
Page 116: Routing Table
Chapter 9 Configuring telephony resources • “SIP Settings” on page 125 • “SIP Media Parameters” on page 126 • “SIP URI Map” on page 127 Routing table Both H.323 and SIP trunks are automatically assigned to line pool BlocA. The decision about whether a given call is through SIP or H.323 is made from the information in the Routing Table.
Page 117 Chapter 9 Configuring telephony resources Table 21 Routing Table fields (Sheet 2 of 2) Attribute Value Description GW Type Choose the type of system that is accessed through the BCM35 remote gateway: BCM: BCMs running 3.6 or later software and CallPilot with Other compatible versions of H.323.
Page 118: H323 Settings
Chapter 9 Configuring telephony resources H323 Settings Figure 30 H323 Settings Table 22 describes the fields on the H323 Settings tab. Table 22 H323 Settings fields (Sheet 1 of 5) Field Value Description Telephony Settings Fallback to Enabled-All Your choice determines how the system will handle calls if circuit-switched the IP network cannot be used.
Page 119 Chapter 9 Configuring telephony resources Table 22 H323 Settings fields (Sheet 2 of 5) Field Value Description Forward redirected OLI <check box> If the check box is selected, the OLI of an internal telephone is forwarded over the VoIP trunk when a call is transferred to an external number over the private VoIP network.
Page 120 Gatekeeper Routed system to direct the calls for that system to route. In each Gatekeeper Routed no RAS system, the Nortel IP Terminals and H.323 Terminals records map IP addresses to specific telephones. Gatekeeper Resolved: all call signaling occurs directly between H.323 endpoints.
Page 121 TEL: Example: the BCM is assigned an E.164 and an H323 Identifier: Alias Names: TEL:76, NAME:bcm10.nortel.com • NPI-TON — also referred to as a PartyNumber alias. Similar to E164 except that the keyword indicates the NPI (numbering plan identification), as well as the TON (type of number).
Page 122: H323 Media Parameters
Chapter 9 Configuring telephony resources Table 22 H323 Settings fields (Sheet 5 of 5) Field Value Description Gatekeeper TTL (s) The actual time used by the gatekeeper for the registration process. Status <read-only> Indicates if the device is online. Modify <button>...
Page 123 Chapter 9 Configuring telephony resources Figure 31 H323 Media Parameters panel Table 23 describes the fields on this panel. Table 23 H323 Media parameters record (Sheet 1 of 2) Field Value Description Preferred Codecs Preferred Codecs None Select the Codecs in the order in which you want the system to attempt to use them.
Page 124 Set the maximum required payload size, per codec, for the VoIP (ms) calls sent over H.323 trunks. Default: 30 Note: Payload size can also be set for Nortel IP telephones. See G.723 payload size the BCM 4.0 Telephony Device Installation Guide (N0027269). (ms) G.711 payload size...
Page 125: Sip Settings
Chapter 9 Configuring telephony resources SIP Settings Figure 32 SIP Settings tab Table 24 SIP Settings fields Field Value Description Telephony Settings Fallback to circuit-switched Enabled-All Your choice determines how the system will handle calls if the IP network cannot be used. Enabled-TDM •...
Page 126: Sip Media Parameters
Chapter 9 Configuring telephony resources SIP Media Parameters SIP trunks are administered separately from H.323 trunks. Both H.323 and SIP trunks commonly h exist on the same system; however, each has different network settings. Figure 33 SIP Media Parameters tab Table 25 SIP Media parameters tab (Sheet 1 of 2) Field Value...
Page 127: Sip Uri Map
Set the desired payload size, per codec, for VoIP calls sent over (ms) SIP trunks. Default: 30 Note: Payload size can also be set for Nortel IP telephones. G.723 Payload Size Refer to the Device Configuration Guide (NN40020-300).Refer to (ms) the Telephony Device Installation Guide (NN40020-309).
Page 128 Chapter 9 Configuring telephony resources Figure 34 SIP URI Map tab Table 26 SIP URI Map Fields Field Value Description SIP Domain Names e.164 / National national.e164 String to use in phone context to identify numbering plan type e.164 / Subscriber subscriber.e164 String to use in phone context to identify numbering plan type e.164 / Special...
Page 129: Configuring Lines
Chapter 10 Configuring lines All the Lines panels show the same type of tabbed panels. The information on the tabbed panels may vary, however, depending on the type of line. The following paths indicate where to access the lines information in Element Manager and through Telset Administration: •...
Page 130: Trunk/Line Data, Main Panel
Chapter 10 Configuring lines Trunk/Line data, main panel The top-level Table View panel shows line records for all lines active on the system, and the common assigned parameters. Figure 35 shows the Trunk/Line Data lines panel. Figure 35 Trunk/Line Data lines panel NN40020-603 NN40020-603...
Page 131 Tips: External lines and telephones must be programmed to use one of the Scheduled Services: Ringing, Restriction, and Routing Services. For maximum flexibility, Nortel recommends that you create two different control telephones, one for the lines and one for the telephones.
Page 132: Properties
Chapter 10 Configuring lines Table 27 Trunk/Line Data main panel (Sheet 2 of 2) Attribute Value Description Prime set Assign a telephone to provide backup answering for calls on the line. For an Auto Answer line, calls are redirected if None the received number is invalid or the target line is busy, and if the...
Page 133 Chapter 10 Configuring lines Figure 36 Properties details panel Table 28 defines the fields on this panel and indicates the lines. Table 28 Properties line settings (Sheet 1 of 2) Attribute Value Description Legend: Loop = analog/digital loop; GS = ground start; DID = DID; E&M = E&M; BRI = BRI; DPNSS = DPNSS;...
Page 134: Preferences (Lines)
Chapter 10 Configuring lines Table 28 Properties line settings (Sheet 2 of 2) Attribute Value Description Legend: Loop = analog/digital loop; GS = ground start; DID = DID; E&M = E&M; BRI = BRI; DPNSS = DPNSS; VoIP = VoIP; TL = Target. Note: PRI fields are all included under the main table. Signaling E&M WinkStart...
Page 135 Chapter 10 Configuring lines Table 29 defines the fields on this panel and indicates the lines. Table 29 Preferences details fields for lines (Sheet 1 of 3) Attribute Value Description Legend: Loop = analog/digital loop; GS = ground start; DID = DID; E&M = E&M; BRI = BRI; DPNSS = DPNSS;...
Page 136 Chapter 10 Configuring lines Table 29 Preferences details fields for lines (Sheet 2 of 3) Attribute Value Description Legend: Loop = analog/digital loop; GS = ground start; DID = DID; E&M = E&M; BRI = BRI; DPNSS = DPNSS; VoIP = VoIP; TL = Target and DASS2. Note: PRI fields are all included under the main panel.
Page 137: Restrictions (Line And Remote)
Chapter 10 Configuring lines Table 29 Preferences details fields for lines (Sheet 3 of 3) Attribute Value Description Legend: Loop = analog/digital loop; GS = ground start; DID = DID; E&M = E&M; BRI = BRI; DPNSS = DPNSS; VoIP = VoIP; TL = Target and DASS2. Note: PRI fields are all included under the main panel.
Page 138: Assigned Dns
Chapter 10 Configuring lines Figure 38 Restrictions tables for a line Table 30 describes the fields on this panel. Table 30 Restrictions Attribute Values Description Use remote package <remote package #> If the line is being 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 external callers to have.
Page 139: To Add A Dn Record To A Line Record
Chapter 10 Configuring lines Figure 39 Add a DN record To add a DN record to a line record In the top panel, click the line where you want to add a DN record. In the bottom frame, click Add. Enter the DN record number and line settings: •...
Page 140 Chapter 10 Configuring lines NN40020-603 NN40020-603...
Page 141: Configuring Lines: Target Lines
Chapter 11 Configuring lines: Target lines Target lines are virtual lines that allow the mapping of received digits to a line number over PRI channel. The following paths indicate where to access target lines in Element Manager and through Telset Administration: •...
Page 142 Chapter 11 Configuring lines: Target lines Figure 40 Configuring target lines — main screen NN40020-603 NN40020-603...
Page 143 Chapter 11 Configuring lines: Target lines Figure 41 Configuring target lines — subscreens Networking Configuration Guide...
Page 144: Configuring Target Line Settings
Chapter 11 Configuring lines: Target lines Configuring Target line settings The following procedure describes the fields that need to be confirmed or set for these lines. For detailed field descriptions, refer to “Configuring lines” on page 129. Confirm or change the settings on the Trunk/Line Data main panel: •...
Page 145: Configuring Lines: Pri
Chapter 12 Configuring lines: PRI PRI are auto-answer lines. These lines cannot be individually assigned to telephones. They must be configured into line pools. PRI line pools then are assigned routes and these routes are used to create destination codes. The following paths indicate where to access PRI line pools in Element Manager and through Telset Administration: •...
Page 146 Chapter 12 Configuring lines: PRI Figure 42 PRI line feature configuration process — Part A NN40020-603 NN40020-603...
Page 147: Configuring Pri Line Features
Chapter 12 Configuring lines: PRI Figure 43 PRI line feature configuration process — Part B Configuring PRI line features The following procedure describes the fields that need to be confirmed or set for these lines. For detailed field descriptions, refer to “Configuring lines”...
Page 148: Configuring Pri Call-By-Call Services
Chapter 12 Configuring lines: PRI • Pub. Received #: Not applicable. • Priv. Received #: Not applicable. • Distinct Ring: If you want this line to have a special ring, indicate a pattern (2, 3, 4, or None). Subpanel under Restrictions tab: •...
Page 149: To Configure Call-By-Call Services And The Pri Lines
Chapter 12 Configuring lines: PRI To configure Call-by-Call services and the PRI lines Set up the DTM module to support PRI. Set up the Call-by-Call services selection for the module. Refer to “Call-by-Call Service Selection” on page 108. Provision the PRI lines. Refer to “Provisioning module lines/loops”...
Page 150 Chapter 12 Configuring lines: PRI NN40020-603 NN40020-603...
Page 151: Configuring Lines: T1-E&M
Chapter 13 Configuring lines: T1-E&M E&M lines must be digital (T1). The following paths indicate where to access the E&M lines in Element Manager and through Telset Administration: • Element Manager: Configuration > Telephony > Lines • Telset interface: **CONFIG > Lines Task: Configure T1 E&M lines connected to the system •...
Page 152 Chapter 13 Configuring lines: T1-E&M Figure 44 T1-E&M line configuration process — Part A NN40020-603 NN40020-603...
Page 153 Chapter 13 Configuring lines: T1-E&M Figure 45 T1-E&M line configuration process — Part B Networking Configuration Guide...
Page 154 Chapter 13 Configuring lines: T1-E&M Figure 46 T1-E&M line configuration process — Part C NN40020-603 NN40020-603...
Page 155: Configuring E&M Line Features
Chapter 13 Configuring lines: T1-E&M Configuring E&M line features The following procedure describes the fields that need to be confirmed or set for these lines. For detailed field descriptions, refer to “Configuring lines” on page 129. Confirm or change the settings on the Trunk/Line Data main panel: •...
Page 156 Chapter 13 Configuring lines: T1-E&M • Redirect to: If you want to automatically direct calls out of the system to a specific telephone, such as a headoffice answer attendant, enter that remote number here. Ensure that you include the proper routing information. Set the restriction and remote package scheduling (Restrictions tab): •...
Page 157: Configuring Lines: T1-Loop Start
Chapter 14 Configuring lines: T1-Loop start Loop start trunks provide remote access to the BCM from the public network. They must be configured to auto-answer to provide remote system access. A loop start trunk must have disconnect supervision if it is to operate in the auto-answer mode. The following paths indicate where to access the loop start trunks information through Element Manager and through Telset Administration: •...
Page 158 Chapter 14 Configuring lines: T1-Loop start Figure 47 T1-Loop start line configuration process — Part A NN40020-603 NN40020-603...
Page 159 Chapter 14 Configuring lines: T1-Loop start Figure 48 T1-Loop start line configuration process — Part B Networking Configuration Guide...
Page 160 Chapter 14 Configuring lines: T1-Loop start Figure 49 T1-Loop start line configuration process — Part C NN40020-603 NN40020-603...
Page 161: To Configure Digital Loop Start Lines
Chapter 14 Configuring lines: T1-Loop start Configuring digital (T1/E1) loop start lines The following procedure describes the fields that need to be confirmed or set for these lines. For detailed field descriptions, refer to “Configuring lines” on page 129. To configure digital loop start lines Confirm or change the settings on the Trunk/Line Data main panel: •...
Page 162 Chapter 14 Configuring lines: T1-Loop start Under the Restrictions tab: • Use remote package: If this line allows remote call-ins, ensure that you define a remote package. • Line Restrictions: Enter a valid restriction filter for the Normal schedule, and any other schedules that you want this line to be part of.
Page 163: Configuring Lines: T1-Digital Ground Start
Chapter 15 Configuring lines: T1-Digital Ground Start The following describes how to configure digital Ground Start lines. The following paths indicate where to access the Ground Start lines through Element Manager and through Telset Administration: • Element Manager: Configuration > Telephony > Lines •...
Page 164 Chapter 15 Configuring lines: T1-Digital Ground Start Figure 50 T1-Digital Ground Start lines configuration process — Part A NN40020-603 NN40020-603...
Page 165 Chapter 15 Configuring lines: T1-Digital Ground Start Figure 51 T1-Digital Ground Start lines configuration process — Part B Networking Configuration Guide...
Page 166: To Configure Digital Ground Start Line Features
Chapter 15 Configuring lines: T1-Digital Ground Start Configuring digital ground start line features The following procedure describes the fields that need to be confirmed or set for these lines. For detailed field descriptions, refer to “Configuring lines” on page 129. To configure digital Ground Start line features Confirm or change the settings on the Trunk/Line Data main panel: •...
Page 167 Chapter 15 Configuring lines: T1-Digital Ground Start • Remote Packages: Enter a valid remote access package for the Normal schedule, and any other schedules that you want this line to be part of (incoming calls from remote users or private networks) Assign the lines to DNs (Assigned DNs tab) If you have configured the DNs and know to which telephones the line needs to be assigned, you can enter those DNs here.
Page 168 Chapter 15 Configuring lines: T1-Digital Ground Start NN40020-603 NN40020-603...
Page 169: Configuring Lines: T1-Did
Chapter 16 Configuring lines: T1-DID DID (Direct Inward Dial) are lines on a digital trunk module on a T1. Inbound DID lines are mapped through target lines. The following paths indicate where to access the DID lines in Element Manager and through Telset Administration: •...
Page 170 Chapter 16 Configuring lines: T1-DID Figure 52 DID line feature configuration process — Part A NN40020-603 NN40020-603...
Page 171 Chapter 16 Configuring lines: T1-DID Figure 53 DID line feature configuration process — Part B Networking Configuration Guide...
Page 172: To Configure Did Line Features
Chapter 16 Configuring lines: T1-DID Configuring DID line features The following procedure describes the fields that need to be confirmed or set for these lines. For detailed field descriptions, refer to “Configuring lines” on page 129. To configure DID line features Confirm or change the settings on the Trunk/Line Data main panel: •...
Page 173 Chapter 16 Configuring lines: T1-DID Set the restriction and remote package scheduling (Restrictions tab): • Line restrictions: Enter a valid restriction filter for the Normal schedule, and any other schedules that you want this line to be part of. (outgoing calls) •...
Page 174 Chapter 16 Configuring lines: T1-DID NN40020-603 NN40020-603...
Page 175: Configuring Lines: Dass2 Lines
Chapter 17 Configuring lines: DASS2 lines DASS2 trunks are specific to the UK protocol. The following paths indicate where to access the DASS2 trunks in Element Manager and through Telset Administration: • Element Manager: Configuration > Telephony > Lines • Telset Interface: **CONFIG >...
Page 176 Chapter 17 Configuring lines: DASS2 lines Figure 54 DASS2 line feature configuration process — Part A NN40020-603 NN40020-603...
Page 177: Configuring Dass2 Line Features
Chapter 17 Configuring lines: DASS2 lines Figure 55 DASS2 line feature configuration process — Part B Configuring DASS2 line features The following procedure describes the fields that need to be confirmed or set for these lines. For detailed field descriptions, refer to “Configuring lines”...
Page 178 Chapter 17 Configuring lines: DASS2 lines • Line type: Define how the line will be used. If you are using routing, ensure it is put into line pool (A to O). • Prime Set: If you want the line to be answered at another telephone if the line is not answered at the target telephone, otherwise, choose None.
Page 179 Chapter 17 Configuring lines: DASS2 lines • Networking “Public networking: Tandem calls from private node” on page 293 “Private networking: Using destination codes” on page 339 “Private networking: DPNSS network services (UK only)” on page 331 “Private networking: MCDN over PRI and VoIP” on page 297 Networking Configuration Guide...
Page 180 Chapter 17 Configuring lines: DASS2 lines NN40020-603 NN40020-603...
Page 181: Configuring Lines: Dpnss Lines
Chapter 18 Configuring lines: DPNSS lines DPNSS trunks are specific to the UK protocol. The following paths indicate where to access the DPNSS trunks in Element Manager and through Telset Administration: • Element Manager: Configuration > Telephony > Lines • Telset interface: **CONFIG >...
Page 182 Chapter 18 Configuring lines: DPNSS lines Figure 56 DPNSS line feature configuration process — Part A NN40020-603 NN40020-603...
Page 183: Configuring Dpnss Line Features
Chapter 18 Configuring lines: DPNSS lines Figure 57 DPNSS line feature configuration process — Part B Configuring DPNSS line features The following procedure describes the fields that need to be confirmed or set for these lines. For detailed field descriptions, refer to “Configuring lines”...
Page 184 Chapter 18 Configuring lines: DPNSS lines • Prime Set: If you want the line to be answered at another telephone if the line is not answered at the target telephone, otherwise, choose None. • Pub. Received #: Not applicable. • Priv.
Page 185 Chapter 18 Configuring lines: DPNSS lines • Networking “Public networking: Tandem calls from private node” on page 293 “Private networking: Using destination codes” on page 339 “Private networking: DPNSS network services (UK only)” on page 331 “Private networking: MCDN over PRI and VoIP” on page 297 Networking Configuration Guide...
Page 186 Chapter 18 Configuring lines: DPNSS lines NN40020-603 NN40020-603...
Page 187: Bri Isdn: Bri Loop Properties
The default loops are 301 and 302. Physical lines 061-064 are always assigned to the BRI cNIC. Refer to the BCM50 2.0 Installation and Maintenance Guide (NN40020-302) for more information on the BCM50 integrated BRI models. The following paths indicate where to access the loops table for BRI modules in Element Manager and through Telset Administration: •...
Page 188: Configure Loop Type And General Parameters
Chapter 19 BRI ISDN: BRI loop properties Configure loop type and general parameters The Loops table displays the BRI loops for an installed module and the settings that are common to both T-loops and S-loops. Figure 58 illustrates the Loops table. Figure 58 Loops table Table 31 describes the fields found on the Loop main panel.
Page 189: T-Loop General Settings
Chapter 19 BRI ISDN: BRI loop properties Table 31 Loops main panel (Sheet 2 of 2) Attribute Value Description ONN blocking Suppression bit: the system flags the call to the Central Office (CO) so that the name and number is not sent to the person you call.
Page 190: T-Loop Spids And Network Dns
Chapter 19 BRI ISDN: BRI loop properties Table 32 Details for Loop (Sheet 2 of 2) Note: This parameter appears only when Overlap receiving is enabled. Example: Public received number = 4502303 Target line received numbers = 303 Local number length = 7 Public received number length = 3 Thus the first four digits are deleted by the system.
Page 191 Chapter 19 BRI ISDN: BRI loop properties Table 33 Loop settings (Sheet 1 of 2) Attribute Value Description SPIDS table SPID Digits <digits> Supplied by your service provider. System running with North American country profiles support additional BRI services offered by ISDN service providers and defined by network service profile identifiers (SPID).
Page 192: T-Loops D-Packet Service
Chapter 19 BRI ISDN: BRI loop properties Table 33 Loop settings (Sheet 2 of 2) Attribute Value Description Actions 1. Select the appropriate SPID (1 or 2) 2. Under the Details for SPID table, click Add. 3. Enter a network DN. 4.
Page 193: S-Loops Assigned Dns
Chapter 19 BRI ISDN: BRI loop properties Table 34 describes each section on the D-Packet Service panel. Table 34 D-packet settings Attribute Value Description Associated loop X01-X04 T-loop: This is the loop on the BRI module that is configured as the T-loop and is connected to the external trunk.
Page 194 Chapter 19 BRI ISDN: BRI loop properties Figure 62 Assigned DNs (S-loops) Table 35 defines the fields on the Details for Loop panel. Table 35 Loop settings Attribute Value Description Loop DN <system DN> Control DN for the loop. This DN must be on the Assigned DNs list. Assigned DNs table <system DN>...
Page 195: Bri Isdn: Bri T-Loops
Chapter 20 BRI ISDN: BRI T-loops BRI modules support both trunk and station (telephone) services. The following describes the process for configuring trunk (T) loops. Task: Configure BRI T-loops Configuring BRI T-loop parameters on page 197 Prerequisites Complete the following prerequisites checklist before configuring the modules. Ensure that system hardware is installed and operating correctly.
Page 196 Chapter 20 BRI ISDN: BRI T-loops Figure 63 BRI loops configuration process NN40020-603 NN40020-603...
Page 197: To Configure Bri T-Loop Parameters
Chapter 20 BRI ISDN: BRI T-loops Configuring BRI T-loop parameters To configure BRI T-loop parameters Identify the loop as a T-loop (refer to “Configure loop type and general parameters” on page 188). • Protocol (ETSI and ETSI-QSIG loops, only) • ONN block state •...
Page 198: To Configure Provisioned Bri Line Features
Chapter 20 BRI ISDN: BRI T-loops Prior programming: BRI module: Installed and configured. Refer to “Trunk Module Parameters” on page 104. BRI loops are configured as T loops. Refer to “Configuring BRI T-loop parameters” on page 197. BRI loop lines are provisioned. Refer to “Provisioning module lines/ loops”...
Page 199 Chapter 20 BRI ISDN: BRI T-loops Set the restriction and remote package scheduling (Restrictions tab): • Line restrictions: Enter a valid restriction filter for the Normal schedule, and any other schedules that you want this line to be part of. (outgoing calls) •...
Page 200 Chapter 20 BRI ISDN: BRI T-loops NN40020-603 NN40020-603...
Page 201: Programming Bri S-Loops, Lines, And Isdn Devices
Chapter 21 BRI S-loops, lines, and ISDN devices Programming BRI modules support both trunk and station (telephone) services. The following describes the process for configuring station/device (S) loops, which support devices that use an ISDN interface. You can assign a single device to a loop, or multiple devices connected through an NT-1 interface. The following paths indicate where to configure loops through Element Manager and through Telset Administration: •...
Page 202: To Set Bri Properties For Isdn Device Connections
Chapter 21 Programming BRI S-loops, lines, and ISDN devices To set BRI properties for ISDN device connections On the top panel, identify the loop as an S-loop. Refer to “Configure loop type and general parameters” on page 188. • Sampling •...
Page 203 Chapter 21 Programming BRI S-loops, lines, and ISDN devices Figure 64 ISDN DN record overview Prerequisites Ensure that the following prerequisites checklist is complete before configuring the devices. BRI module installation and configuration is complete. Refer to “Trunk Module Parameters” on page 104.
Page 204: Configuring An Isdn Telephone Dn Record
Chapter 21 Programming BRI S-loops, lines, and ISDN devices Configuring an ISDN telephone DN record On each panel on the DNs list, add or modify settings to customize the telephone operations. The following headings correspond to each panel. Refer to the Programming notes in each section for configurations that are unique or specific for ISDN telephones.
Page 205: Configuring Clid On Your System
Chapter 22 Configuring CLID on your system The following describes the various areas in the system that need configuration to allow incoming or outgoing Calling Line Identification Display (CLID) information to display (incoming calls) or transmit over the trunks (outgoing calls). The following describes programming and setting up this feature.
Page 206 Chapter 22 Configuring CLID on your system Figure 65 CLID configuration process NN40020-603 NN40020-603...
Page 207: To Set Up Alpha Tagging On Your System
Chapter 22 Configuring CLID on your system Programming incoming CLID Telephones can receive Name, Number, and Line display for incoming calls over trunks that support CLID or between telephones within the system. The following describes the different areas where these capabilities are configured. Note: If no configuration is done, CLID will show up after answering a call unless Feature 811 is used.
Page 208: To Program The Business Name
Programming Business name display (outgoing) Nortel recommends that you use a blank space for the last character of the Business name to act as a separator between the Business name and telephone name. Note that if you leave this field blank, no name appears.
Page 209 Chapter 22 Configuring CLID on your system • The OLI number. Refer to “Line Access tab” in the Device Configuration Guide (NN40020-300). • The Auto Called ID must be selected. Refer to “Capabilities tab” in the Device Configuration Guide (NN40020-300). Internal name and extension display If you want to be able to see the CLID of internal telephones you call, ensure that Auto caller ID is enabled under Configuration >...
Page 210 Chapter 22 Configuring CLID on your system Blocking outgoing name display at the trunks To block outgoing name display at the media bay module level, you can configure module records to disable the Send Name display check box, select Configuration > Resources > Telephony Resources >...
Page 211: Clid: Name Display
Chapter 23 CLID: Name display BCM displays the name of the calling party at the answering telephone when this information is available on Private or Public PRI trunks, VoIP trunks, and analog trunks that support Calling Line Identification (CLID). The displayed name can include the Receiving Calling Name, Receiving Redirected Name, and/or Receiving Connected Name.
Page 212: Business Name Display
Use this for trunks where the connecting switch does not support outgoing line display. Default is enabled. Business name display Nortel recommends that you use a blank space for the last character of the Business name to act as a separator between the Business name and telephone name. A maximum of eight characters is supported.
Page 213: Name Display
Chapter 23 CLID: Name display Limitations: • Due to system resource limitations, only 30 telephones can be assigned to provide alpha tagging CLID per line. • If the incoming number only partially matches the CLID match length, no name displays. •...
Page 214: Incoming And Outgoing Call Display
Chapter 23 CLID: Name display Figure 66 Naming components in the system K9 Unit 5553465 K9 Unit Public or Private Target line network Trunks K9help Hunt group Incoming and outgoing call display If you subscribe to Call Display services from your local telephone company, one line of information about an external caller appears on the display after you answer a call.
Page 215 Chapter 23 CLID: Name display Figure 67 Sending and receiving call display DogFood 5556897 Business name Line: 026 *Public or display: RCMP Private network K9 Unit *Trunks 5552354 RCMP K9 Unit 5552354 Incoming Name, Number, Line display DogFood Outgoing Name display 5556897 Networking Configuration Guide...
Page 216 Chapter 23 CLID: Name display NN40020-603 NN40020-603...
Page 217: Dialing Plans
Chapter 24 Dialing plans The BCM allows for flexible dialing plans using access codes, destination codes, PSTN trunks and private network trunks that provide multiple options for customizing the dialing options to meet each customers unique requirements. Refer to “Outgoing call routing” on page 222.
Page 218: Creating Dialing Plans
Chapter 24 Dialing plans Also refer to “Call security: Restriction filters” on page 433. This section also discusses Class of Service (CoS) passwords, which you can use so that users can access the system features over public connections. Refer to “Call security and remote access”...
Page 219 Chapter 24 Dialing plans Public Auto DN Private DISA DN Public DISA DN Incoming calls: The Private Dialing Plan provides the special codes that identify the system to calls coming over private PSTN or VoIP trunks. Calls that do not match the private dialing plan information, are not accepted by the system.
Page 220 Chapter 24 Dialing plans MCDN special call types: If your system is networked to other types of systems, such as Meridian 1, which sends calls through one or more BCM systems to the public network, you need to specify specific call-type codes. These codes append to the incoming dial string, so that the call-type remains intact as it passes through the BCM call processing: Variable Example or default...
Page 221: Public And Private Received Numbers
Chapter 24 Dialing plans Public and Private Received numbers If the received number is different than the regular DN number, in the target line configuration programming, enter the number in the Private number and/or Public number field. Programming note: Auto-answer trunks such as PRI, T1, BRI, and VoIP trunks, use these settings to route calls: •...
Page 222: Outgoing Call Routing
Chapter 24 Dialing plans A set of default Public DN lengths is included with the default template. In most cases it is not necessary to change the default values. About the Public DN lengths table In the public DN lengths table: •...
Page 223 Chapter 24 Dialing plans • If the outgoing call is designated as public, the system checks the beginning of the string for a destination code that routes to a PSTN or an MCDN trunk. If the call routes to a public route, the system checks the public dialing table to ensure that the dialout string has legitimate leading digits and is the correct length.
Page 224: Incoming Call Routing
Chapter 24 Dialing plans MCDN trunks also allow public call types when tandeming calls from another system on the private network. Some of these systems use specific call types that the BCM needs to recognize to pass on correctly. Also refer to “Using the MCDN access codes (tandem calls)”...
Page 225: Processing Incoming Calls
Chapter 24 Dialing plans Warning: If your system is running with a PBX telephony template, the Public and Private received # length are by default 3 (digits) at startup. Increasing the DN length after system startup does not change these digits, so you will need to manually change the Public and Private Receive Number length.
Page 226 Chapter 24 Dialing plans • If the call is from ETSI-QSIG, MCDN, NI, DMS-100, or DMS-250 and tagged as Private/Subscriber, the system prepends the Private access code, if the dialing plan is UDP. • If the call is tagged as Unknown/Unknown or Private/Unknown (ETSI-QSIG, MCDN, N1, DMS-100, or DMS-250 trunks), no access code is added.
Page 227 Chapter 24 Dialing plans Figure 68 Incoming public and private call coding Networking Configuration Guide...
Page 228: Determining Line Access Dialing
Chapter 24 Dialing plans Determining line access dialing “Understanding access codes” on page 229 “Configuring call routing” on page 234 describe what you do with the lines and loops you previously set up into line pools. By using access codes or call routing, which uses destination codes, you can determine which lines (routes) outgoing calls use.
Page 229: Understanding Access Codes
Chapter 24 Dialing plans Understanding access codes The system uses access codes to direct calls to the correct lines and destinations. Refer to “Creating dialing plans” on page 218 for a general overview about using access codes within the system dialing plan. Task: Set up access codes for internal features: •...
Page 230: Call Park Codes
Chapter 24 Dialing plans The default settings shown in Table 38 can help you plan your access codes so there are no conflicts. Table 38 Default codes table Digit System panel direct dial digit Access codes park prefix Access codes first digit of DNs/DN lengths Set through Quick Start Wizard...
Page 231: Creating Direct Dial Sets
Chapter 24 Dialing plans The system assigns Call Park codes to calls in sequence, from the lowest to the highest, until all the codes are used. The use of different of codes ensures a call reaches the right person, especially when more than one incoming call is parked.
Page 232: Tips About Access Codes
Chapter 24 Dialing plans Tips about access codes Here are some pointers to assist you in planning the access codes for your system. Note: The following codes/digits must not conflict: • park prefix • external code • direct dial digit •...
Page 233 Chapter 24 Dialing plans Calls tandeming to the public network through the private network need to retain their dialing protocol throughout the private network. This means that BCM node receives a call from an M1 node tagged as a local call and recognizes the call intended for the public network, but also recognizes the call that needs to maintain the local call tag until it gets to the BCM node that is directly connected to the PSTN.
Page 234: Line Pool Access Codes
Chapter 24 Dialing plans Line pool access codes Line pool access codes allow you to assign an access code for each of the basic line pools (A to O). These codes specify the line pool for making an outgoing external call. Up to three digits in length, these codes do not allow any other routing programming.
Page 235: Configuring Call-By-Call Services
Chapter 24 Dialing plans • dialing an access code for a long-distance carrier • deciding which line pool to use according to the time and day You can set up routing to take advantage of any leased or discounted routes using information supplied by the customer.
Page 236: Call-By-Call Services
Chapter 24 Dialing plans Supporting protocols The following protocols support Call-by-call limits: • National ISDN 2 (NI-2) • DMS-100 custom • DMS-250 • AT&T 4ESS custom Call-by-Call services BCM supports the Call-by-Call Services listed in Table Table 39 Call-by-Call Services available on the system Service Description Public...
Page 237: Switches Supporting Call-By-Call Limits
Chapter 24 Dialing plans Switches supporting Call-by-call limits Table 40 lists the service types and cross-references them with four common switches. Table 40 Switches and service types chart Switches Service types NI-2 DMS-100 DMS-250 AT&T 4ESS (custom) SDN (software defined network) INWATS INWATS...
Page 238: Provisioning For Call-By-Call Limits With Pri
Chapter 24 Dialing plans Provisioning for Call-by-Call limits with PRI To program the system for Call-by-Call Limits with a PRI interface, you must: • provision a DTM as PRI, if one is not already configured as part of the system •...
Page 239: Pri Routing Protocols
Chapter 24 Dialing plans The service identifier (SID) depends on the selected service type (for example, with NI-2 protocol). Service Type Service Identifier description Public None Facility Number 1-5 digits Facility Number 1-5 digits OUTWATS Optional Band Number 1-3 digits Private None Switched Digital...
Page 240: Why Use Destination Codes
Chapter 24 Dialing plans Note: Destination codes must not conflict with the following: • park prefix • external code • direct dial digit • Auto DN • DISA DN • Private access code • line pool codes • telephone DN •...
Page 241: Deciding On A Code
Chapter 24 Dialing plans Figure 71 Using destination codes to access another system Deciding on a code Note: When configuring a private network, ensure the numbering plan does not conflict with the public telephone network. For example, in North America, using “1” as an access code in a private network, conflicts with the PSTN numbering plan for long-distance calls When deciding on which digits to use to start your destination codes, consider the following: •...
Page 242: Adding Carrier Access Codes To Destination Codes
Chapter 24 Dialing plans Example: If users are used to dialing 9-1-555-1234-<DN number> to reach another system (whose DN codes start with 6), you create a destination code of 915551236A, using the VoIP line pools (users dial the destination code plus the DN of the telephone they want to reach on the other system).
Page 243: Routing Schedules And Alternate Routes
Chapter 24 Dialing plans Figure 72 Carrier code call numbering sequence Tips: The destination codes 9 and 91 used in the examples cannot be used together. If you need the destination code 91 to direct long-distance calls, you must create a separate set of codes that use local calling routes. These codes would be, for example, 90, 92, 93, 94, 95, 96, 97, 98 and 99.
Page 244: Setting Up Voip Trunks For Fallback
Chapter 24 Dialing plans When a user dials, and the telephone cannot capture the preferred line (First Route), the system tries each successive defined route (Second Route, then Third Route). If none of these routes have available lines, the call reverts to the Normal mode. When the call switches from the preferred routing mode (First Route, Second Route, Third Route) to Normal mode, the telephone display flashes an “expensive route”...
Page 245 Chapter 24 Dialing plans Figure 73 PSTN fallback diagram IP network BCM50 B BCM50 A PSTN Public or Private Public or Private PSTN line PSTN line In a network configured for PSTN fallback, there are two connections between a BCM and a remote system.
Page 246 Chapter 24 Dialing plans NN40020-603 NN40020-603...
Page 247: Dialing Plan: Routing Configurations
Chapter 25 Dialing plan: Routing configurations This following describes how you can configure the lines and loops to allow system users to dial out of the system over a public or private network. The following paths indicate where to access the route lines and loops in Element Manager and through Telset Administration: •...
Page 248 Chapter 25 Dialing plan: Routing configurations Figure 74 Routing workflow NN40020-603 NN40020-603...
Page 249: To Build A Route To Allow Local Calls
Chapter 25 Dialing plan: Routing configurations Destination code numbering in a network Because the system checks the initial digits of a call against the routing tables, each type of internal or external call must begin with a unique pattern of digits. Table 43 gives a sample plan for how initial digits are assigned in a network of systems with three-digit intercom numbers.
Page 250: To Set Up A Route Through A Dedicated Trunk
Chapter 25 Dialing plan: Routing configurations Set up the Normal schedule with the route number you defined in step 1. Figure 75 Routing Service programming example Routing Service ( Services: Routing Service Route # Dial out (if required) Use Pool (000-999) (max.
Page 251: Grouping Destination Codes Using A Wild Card
Chapter 25 Dialing plan: Routing configurations Grouping destination codes using a wild card If you have a number of destinations that have the same route and digit absorb length, you can group these codes under one destination code to maximize your destination code table. In this case, the start digits will be the same, but the last character will be the wild card, and indicates any digit between 0 and 9.
Page 252: To Build A Route For A Secondary Carrier
Chapter 25 Dialing plan: Routing configurations Tips: To minimize the effort involved in preparing destination codes, set the digit absorption to 0. When digital absorption is set to 0, the actual digits dialed by a caller are preserved in the dial-out sequence. The need to program a dial out sequence as part of the route depends on the required dialout.
Page 253: To Set Up The Multiple Routing Overflow Feature
Chapter 25 Dialing plan: Routing configurations To set up the multiple routing overflow feature You assign the preferred routes in a destination code schedule. Refer to “Alternate routes for routing schedules” on page 264. Pick a schedule when you want these routes to be in effect. b In the First Route field enter the route number for the preferred route for the call.
Page 254: Dialing Plan Using Public Lines
Chapter 25 Dialing plan: Routing configurations Dialing plan using public lines Figure 77 Figure 78 provide examples of how you can record dialing plan information in a spreadsheet. The example shows dialing plan information for a Toronto system in a network of three offices: Toronto, Halifax, and Vancouver.
Page 255: To Program The Pri Routing Table
Chapter 25 Dialing plan: Routing configurations Figure 78 Routing service record: Destination code Routing service (continued) Dest code (Services: Routing Services: Dest Codes) Service Normal Schedule Schedule DestCode Use route Absorb 1st route Absorb 2nd route Absorb 3rd route Absorb Length Length Length...
Page 256: To Program A Long Distance Carrier Access Code Into A Destination Code
Chapter 25 Dialing plan: Routing configurations Adding Carrier access codes to destination codes In some cases, long distance service uses the same lines as local service but is switched to a specific carrier using an access number, which is sometimes referred to as an carrier access code (CAC).
Page 257: Using The Mcdn Access Codes To Tandem Calls
Chapter 25 Dialing plan: Routing configurations Set Absorbed Length to 1. The digit 9 is only used internally and should be dropped. The 1 is needed to direct the call to the public carrier network. Tips: The destination codes 9 and 91 used in the examples cannot be used together.
Page 258 Chapter 25 Dialing plan: Routing configurations Figure 80 Local call tandemed through private network nodes IP Phone Dialout: 9-823-2222 The BCM receives the call. The system recog- nizes 9823 as the destination code for the local PSTN route. Route drops the leading digit and dials out over the PSTN trunk.
Page 259: Dialing Plan: Routing And Destination Codes
Chapter 26 Dialing plan: Routing and destination codes A large system usually requires a number of destination codes to ensure that calls are directed to the correct trunks, either on the private or public network. The following paths indicate where to access destination codes in Element Manager and through Telset Administration: •...
Page 260: Routes
Chapter 26 Dialing plan: Routing and destination codes Panels Tasks Feature notes See also: • “Setting up VoIP trunks for fallback” on page 391 • “Configuring lines” on page 129 • “BRI ISDN: BRI T-loops” on page 195 • “Dialing plan: System settings” on page 267 •...
Page 261 Chapter 26 Dialing plan: Routing and destination codes Table 47 describes the fields on the top panel. Table 47 Route settings (Sheet 1 of 2) Attribute Value Description Route <001-999> This number is unique to each route. External <a maximum of 24 Enter the external or dial-out number for the route you want the Number digits>...
Page 262: Destination Codes
Chapter 26 Dialing plan: Routing and destination codes Table 47 Route settings (Sheet 2 of 2) Attribute Value Description Actions: 1. Under the routes table, click Add. 2. Enter a route number in the dialog box. 3. Click OK to save the new route. Delete 1.
Page 263 Chapter 26 Dialing plan: Routing and destination codes Figure 82 Destination codes table panel Table 49 describes the fields on the destination codes frame. Table 49 Destination codes table Attribute Value Description Destination Code <max. 12 digits> This number precedes a telephone number to tell the system where the call needs to be routed.
Page 264: Alternate Routes For Routing Schedules
Chapter 26 Dialing plan: Routing and destination codes Note: The destination codes must not conflict with the following: • park prefix • external code • direct dial digit • Auto DN • DISA DN • Private access code • line pool codes •...
Page 265: Second Dial Tone
Chapter 26 Dialing plan: Routing and destination codes Table 50 Destination codes schedules Attribute Value Description Schedule Defaults: Night, If you use a different carrier at different times of the day or Evening, Lunch, week, you can set the destination code to use that route Weekend, Sched.
Page 266 Chapter 26 Dialing plan: Routing and destination codes • Element Manager: Configuration > Telephony > Dialing Plan > Routing > Second Dial Tone • Telset interface: **CONFIG > Services > Routing Service > 2nd Dial Tone Figure 84 Second Dial Tone Table 2 Second Dial Tone Attribute Value...
Page 267: Dialing Plan: System Settings
Chapter 27 Dialing plan: System settings The panels described in the following information define various common system settings that affect, or that are affected by, number planning. The following paths indicate where to access system settings for dialing plans in Element Manager and through Telset Administration: •...
Page 268 Chapter 27 Dialing plan: System settings Figure 85 Dialing Plan - General settings and Direct Dial devices Table 51 describes each field on this panel. Table 51 Private and Public received numbers (Sheet 1 of 3) Attribute Value Description Global Settings DN length (3 to 7) This is the length of the locally dialed telephones.
Page 269 Chapter 27 Dialing plan: System settings Table 51 Private and Public received numbers (Sheet 2 of 3) Attribute Value Description Dialing timeout Default: 4 This is the maximum period allowed between user dialpad seconds presses before the system decides that the dial string is complete.
Page 270: Dn Length Constraints
Chapter 27 Dialing plan: System settings Table 51 Private and Public received numbers (Sheet 3 of 3) Attribute Value Description Facility Line The facility to be used to route the call to a direct dial set that you Pool (A-O) define with an external number.
Page 271: Received Number Notes
Chapter 27 Dialing plan: System settings Warning: Increasing the DN length affects other areas of the system: If the DN length change creates a conflict with the Park prefix, external line access code, direct-dial digit, or any line pool access code, the setting for the prefix or code changes to None, and the corresponding feature is disabled.
Page 272: Tips About Access Codes
Chapter 27 Dialing plan: System settings Tips about access codes Here are some pointers to assist you in planning the access codes for your system. Note: The following values must not conflict: • Park prefix • external code • direct dial digit •...
Page 273: Call Park Codes
Chapter 27 Dialing plan: System settings • Public/Private DISA DN: The length of the DISA DNs are the same as the Public or Private Received number length specified under Configuration > Telephony > Dialing Plan > Public or Private. The public/private DISA DN is cleared if the corresponding Received number length is changed.
Page 274 Chapter 27 Dialing plan: System settings Calls are retrieved by pressing the intercom button and dialing the retrieval code. On model 7000 and analog telephones, pick up the receiver, and then dial <parkcode>25. You also need to program the delay timer that determines when external parked calls that are not answered return to the originating telephone.
Page 275: Dialing Plan: Public Network
Chapter 28 Dialing plan: Public network The panel described in the following information defines the number planning required for calls exiting the system to the public telephone network. The following paths indicate where to access the dialing plan for public network in Element Manager and through Telset Administration: •...
Page 276: Public Network Settings
Chapter 28 Dialing plan: Public network This panel includes information about: • “Public Network Settings” on page 276 • “Public network DN lengths” on page 277 • “Carrier Codes” on page 279 Public Network Settings This following describes system settings that allow the system to determine if an incoming call is meant for the local system.
Page 277: Public Network Dn Lengths
Chapter 28 Dialing plan: Public network Table 52 Private and Public received numbers (Sheet 2 of 2) Attribute Value Description Public network National Local dialing plan defines a seven-digit numbering scheme. dialing plan Local National dialing plans define an extended number scheme. North (Subscriber) America is set to 10 digits.
Page 278 Chapter 28 Dialing plan: Public network Table 53 describes each field on this panel. Table 53 Public network DN values Attribute Values Description DN Prefix <XXXX> This is the number that must precede a dial string exiting the system to the public network. Each prefix defines a specific destination or type of call.
Page 279: Carrier Codes
Chapter 28 Dialing plan: Public network Deleting a DN prefix Note: Dialing prefixes are used system-wide for users to make calls. Delete prefixes with caution. On the Public Network DN Lengths panel, click the DN prefix you want to delete. Click Delete.
Page 280 Chapter 28 Dialing plan: Public network Table 54 describes each field on this panel. Table 54 Carrier Code values Attribute Values Description Code Prefix <one to six digits> This value defines the prefix that will be used to access the (Read-only) carrier code.
Page 281: Dialing Plan: Private Network Settings
Chapter 29 Dialing plan: Private network settings The panels described in the following information define various system settings that affect or that are affected by number planning for private networks. The following paths indicate where to access the dialing plan for private networks in Element Manager and through Telset Administration: •...
Page 282: Private Network Settings
Chapter 29 Dialing plan: Private network settings • “Private Network - MCDN network (PRI SL-1, PRI ETSI, VoIP)” on page 283 • “ETSI-specific network features” on page 286 Private Network Settings The settings on the Private Network Settings panel describe the numbering that the system uses to assess an incoming call to determine if the call is destined for your system or needs to be routed elsewhere on the private or public network.
Page 283: Private Network - Mcdn Network (Pri Sl-1, Pri Etsi, Voip)
Chapter 29 Dialing plan: Private network settings Table 55 Private Network Settings (Sheet 2 of 2) Attribute Value Description * Private DISA DN <DISA DN digits For private network calls answered with DISA, the system to be received presents a stuttered dial tone to prompt a caller to enter a valid from the password.
Page 284 Chapter 29 Dialing plan: Private network settings Figure 89 MCDN network values Table 56 describes the values for these fields. Table 56 Private network values (Sheet 1 of 2) Attribute Values Description Private networking also provides access to tandem calling and toll bypass functionality to users calling into the system.
Page 285: Voip-Specific Private Network Dialing
Chapter 29 Dialing plan: Private network settings Table 56 Private network values (Sheet 2 of 2) <check box> Trunk Route Optimization occurs during the call setup. This feature finds the most direct route through the network to send a call between nodes. <check box>...
Page 286: Etsi-Specific Network Features
Chapter 29 Dialing plan: Private network settings ETSI-specific network features The features contained in the ETSI subpanel are service provider-based network services available for some PRI-ETSI lines. This subpanel is illustrated in Figure Figure 91 ETSI private network settings Table 58 to determine the settings you want to define network services feature availability.
Page 287 Chapter 29 Dialing plan: Private network settings Dialing plan setting NPI/TON Private called number length based on Private/UDP private access code + home location code (LOC) + private received digits Private/CDP private received digit DMS-100/DMS-250/ETSI-QSIG trunks send private calls in this way: None Private/Subscriber Private DN length (set on Private Network...
Page 288 Chapter 29 Dialing plan: Private network settings NN40020-603 NN40020-603...
Page 289: Public Networking: Setting Up Basic Systems
Chapter 30 Public networking: Setting up basic systems Public networks are the connection between the BCM and the public network (PSTN network). This following provides examples of two basic types of systems. • “Public networks: PBX system setup” on page 289 •...
Page 290: Public Network: Did System
Chapter 30 Public networking: Setting up basic systems Programming: Lines • Set lines to manual answer. • Configure into a line pool. Telephones • Line pools are assigned to general office telephones. • The Prime line is set to the line pool. •...
Page 291 Chapter 30 Public networking: Setting up basic systems Figure 93 DID system Target line mapped to DN (4005) CO DID line 769 Target line mapped to with range of call a DN (4006) numbers (4005 to 4020) Target line mapped to Target line mapped to DN (4007) DN (4008)
Page 292 Chapter 30 Public networking: Setting up basic systems NN40020-603 NN40020-603...
Page 293: Public Networking: Tandem Calls From Private Node
Chapter 31 Public networking: Tandem calls from private node If your system is connected by a private network to another system that does not have PSTN line access, or which is not located within the local dialing range, you can set up a routing plan that allows the users of the private network to dial into your system, and through your system to the PSTN network.
Page 294: Caller Access On A Tandem Network
Chapter 31 Public networking: Tandem calls from private node Dialing plan/Routing: • Coordinate Dialing plan with private network node. • Assign each line pool to a route • Create destination codes for the private network node, and the public network, using the appropriate routes.
Page 295 Chapter 31 Public networking: Tandem calls from private node • call directly to one or more BCM telephones • call into BCM and select an outgoing TIE line to access other nodes in a private network • call into BCM and select an outgoing central office line to access the public network •...
Page 296 Chapter 31 Public networking: Tandem calls from private node NN40020-603 NN40020-603...
Page 297: Private Networking: Mcdn Over Pri And Voip
Chapter 32 Private networking: MCDN over PRI and VoIP The following describes how to network BCMs together in a private network using PRI lines with MCDN protocol. When BCMs are networked with other call services, such as Meridian 1, using the MCDN protocol, the network can also support centralized voice mail.
Page 298: Software Requirements
Chapter 32 Private networking: MCDN over PRI and VoIP The Meridian must provide the following: — end-to-end signaling (option 10) — message center (option 46) and an IVMS link (option 35) — Meridian Mail link (options 77 and 85) — basic Attendant Console Directory features (options 40, 45, and 83) —...
Page 299: Message Waiting Indication
BCM of a call waiting using the native MCDN MWI or MIK/MCK message indicators on the Meridian telephones. This feature works for both Nortel and third-party voice mail systems. Messages are received at a centralized location, to a predetermined telephone, where they are processed and forwarded to the target telephone.
Page 300 Chapter 32 Private networking: MCDN over PRI and VoIP Figure 95 Message waiting indication message Meridian 1 with CallPilot MCDN Telephone A Message Telephone B Original call Call forwarded to CallPilot MWI message signal (over target line) Programming notes BCM programming M1 programming To select Remote Capability for MWI on a per-loop basis 1.
Page 301 Chapter 32 Private networking: MCDN over PRI and VoIP Camp-on A call received by the Meridian attendant can be assigned to a telephone anywhere in the MCDN network, when the following situations are valid: • the target telephone rings busy when the attendant calls •...
Page 302 Chapter 32 Private networking: MCDN over PRI and VoIP Figure 97 Breaking into a local system call path Telephone B Incoming call for Telephone A Meridian 1 Telephone A (rings busy) Attendant Break-in path Break-in can occur when these situations are valid: •...
Page 303: Mcdn Networking Checklist
Chapter 32 Private networking: MCDN over PRI and VoIP MCDN networking checklist The following points provide a quick check for the system prerequisite settings for MCDN networking. Select the dialing plan to be used: • UDP (Universal Dialing Plan) — DNs on the same node are dialed directly. —...
Page 304: Udp-Specific Programming
Chapter 32 Private networking: MCDN over PRI and VoIP UDP-specific programming BCM UDP programming • Private Dialing Plan: Type=UDP, HomeLoc=<three-digit prefix> • Private Access Code <unique code> • Private DN length <total of Private Access Code + Location Code + DN length> Example: if dialing string is 6 393 2222, then set private DN to 8 •...
Page 305: Cdp-Specific Programming
Chapter 32 Private networking: MCDN over PRI and VoIP CDP-specific programming BCM CDP programming • Private Dialing Plan: Private Type=CDP Access Code <unique code>. • Private DN length <system DN length> • <number assigned from M1 (1-127)> • Program the DestCodes for use Steering code as part of dial string the other nodes M1 CDP programming...
Page 306: Vm Programming With Meridian 1
Chapter 32 Private networking: MCDN over PRI and VoIP VM programming with Meridian 1 If you are using the centralized voice message system from a Meridian 1 system, you require the following programming on the M1: M1 programming in LD 17 •...
Page 307: Meridian Tro Programming
Chapter 32 Private networking: MCDN over PRI and VoIP Meridian TRO programming If you are using a Meridian 1 system as part of the network, you need the following programming for each system: M1 TRO set to yes for BCM route: LD 16 TYPE: RDB Cust: xx...
Page 308 Chapter 32 Private networking: MCDN over PRI and VoIP Figure 98 MCDN networking, with a common public network connection Network # 2221 Network # 6221 Received # 2221 Received # 6221 Internal # 2221 Internal # 6221 PRI (SL-1) PRI (SL-1) Meridian M1 East-End branch West-End branch...
Page 309 Chapter 32 Private networking: MCDN over PRI and VoIP BCM module settings: Table 60 lists the module settings that are required to set up the network described in Figure Table 60 Module settings for MCDN network West End office: Module programming DTM Protocol SL-1 BchanSeq...
Page 310 Chapter 32 Private networking: MCDN over PRI and VoIP BCM dialing plan settings: Table 61 lists the dialing plan settings that are required to set up the network described in the figure in the previous section. Table 61 MCDN dialing plan settings West End office: Dialing Plan Type...
Page 311: Configuring Fallback Over A Voip Mcdn Network
Chapter 32 Private networking: MCDN over PRI and VoIP Table 62 Network routing information (Sheet 2 of 2) East End office: Trunk/Line Data Line 125 Target line Private Received # 6221 Line Access DN 6221 L125:Ring only Line pool access Line pool BlocA Routing Services Private Network...
Page 312: To Set Up The M1 In A Bcm Network
Chapter 32 Private networking: MCDN over PRI and VoIP Figure 99 M1 to BCM network diagram Head Office Warehouse M1 + IPT Meridian BCM50 telephone PSTN (fallback route) System telephone Intranet Router VoIP trunk Router Company server 2004 IP telephone...
Page 313: Networking With Etsi Qsig
Chapter 32 Private networking: MCDN over PRI and VoIP For a detailed description of setting up fallback, refer to “Setting up VoIP trunks for fallback” on page 391. Networking with ETSI QSIG (International systems only) ETSI QSIG is the European standard signaling protocol for multi-vendor peer-to-peer communications between PBX systems and/or central offices.
Page 314 Chapter 32 Private networking: MCDN over PRI and VoIP Settings for some of the hardware parameters for the ETSI QSIG networking example shown above are as follows. West End office: East End office: Hardware DTM/BRIM PRI/BRI Hardware DTM/BRIM PRI/BRI programming programming Protocol ETSI QSIG...
Page 315: Private Networking: Basic Parameters
Chapter 33 Private networking: Basic parameters The following provides an overview of the values in the system that affect private networking, including: • “Private networking protocols” on page 315 • “Keycode requirements” on page 315 • “Remote access to the network” on page 316 •...
Page 316: Remote Access To The Network
You must purchase and install these keycodes before you can create any of the networks described in this chapter. Consult with your Nortel distributor to ensure you order the correct keycodes for the type of network you want to create.
Page 317 Chapter 33 Private networking: Basic parameters The services provided within networks is based on the type of trunks and the protocols assigned to the trunks. All trunks within the network should be running the same protocols, to provide a consistent look and feel to the users. These are the main types of private networking, listed from the simplest to the more complex PRI/ ETSI and VoIP routing using MCDN protocols: •...
Page 318 Chapter 33 Private networking: Basic parameters NN40020-603 NN40020-603...
Page 319: Private Networking: Mcdn And Etsi Network Features
Chapter 34 Private networking: MCDN and ETSI network features If the MCDN protocol is added to a PRI SL-1 or VoIP private network, the network provides additional network-management features and provides available centralized voice mail features to all nodes on the network. ETSI lines (UK profile) also have network features available from the central office that can be enabled or disabled.
Page 320: To Configure Iccl
Chapter 34 Private networking: MCDN and ETSI network features ISDN Call Connection Limitation The ICCL feature piggybacks on the call initiation request and acts as a check at transit PBX points to prevent misconfigured routes or calls with errors from blocking channels. To configure ICCL Click Configuration >...
Page 321: To Enable Mcid And Network Diversion
Chapter 34 Private networking: MCDN and ETSI network features Select the TAT check box. Configuring ETSI Euro network services If your system has ETSI ISDN BRI/PRI lines, you can activate the malicious call identification (MCID) and Network Diversion features. Advice of Charge-End of Call (AOCE) is active if your service provider has activated that service on the line.
Page 322 Chapter 34 Private networking: MCDN and ETSI network features Table 64 ETSI network values Attribute Values Description Netwrk Diversion <check box> Allows calls to be redirected to an outside network. MCID <check box> Malicious Call Identification When selected, the called party can use FEATURE 897 to request the network to record the identity of an incoming call.
Page 323: Private Networking: Pri And Voip Tandem Networks
Chapter 35 Private networking: PRI and VoIP tandem networks You can use PRI trunks and VoIP trunks to create a private network between other BCMs. This tandem network provides you with the benefits of end-to-end name display and toll-free calling over the PRI or VoIP private link.
Page 324: Routing Calls Through A Tandem Network
Chapter 35 Private networking: PRI and VoIP tandem networks The following tables show the routing tables for Node A and Node C for external and internal terminating calls. Table 65 Node A destination code table, external termination Route Absorb length Destination code (public DNs) 4 (PSTN) 91604...
Page 325: Calls Originating From The Public Network
Chapter 35 Private networking: PRI and VoIP tandem networks • “Calls originating from the public network” on page 325 • “Calls originating in the private network” on page 326 Calls originating from the public network Table 69 describes how each node handles calls originating from the public network into the system.
Page 326: Calls Originating In The Private Network
Chapter 35 Private networking: PRI and VoIP tandem networks Table 69 Call originating from the public network to a tandem network (Sheet 2 of 2) Received Destination Description Node A Ottawa An external user in Calgary dials a 761-xxxx number which is answered with DISA. User PSTN enters a CoS password and an Ottawa public network number.
Page 327: Using Voip To Tandem Systems
Full toll bypass occurs through the tandem setup, meaning that any user can call any DN without long distance charges being applied. Users have full access to system users, PSTN connections. Figure 102 demonstrates a multiple-BCM50 network. The network diagram shows two BCMs, but additional base units can be added. Networking Configuration Guide...
Page 328: To Set Up A Network Of Bcms
Chapter 35 Private networking: PRI and VoIP tandem networks Figure 102 Multiple BCMs network diagram Head Office Warehouse System System telephone telephone BCM50 BCM50 PSTN (fallback route) router router Intranet VoIP trunk 2050 IP phone 2004 router Company IP phone...
Page 329 Chapter 35 Private networking: PRI and VoIP tandem networks Figure 103 demonstrates an example of routing all public calls through one BCM50. Figure 103 Routing all public calls through one BCM Head Office Warehouse System System PSTN telephone telephone BCM50...
Page 330 Chapter 35 Private networking: PRI and VoIP tandem networks NN40020-603 NN40020-603...
Page 331: Private Networking: Dpnss Network Services (Uk Only)
Chapter 36 Private networking: DPNSS network services (UK only) Programming note: software keys are required to enable DPNSS 1. DPNSS 1 is not available on all profiles. The following features are available and can be programmed over DPNSS lines: • Diversion (“Using the diversion feature”...
Page 332 Chapter 36 Private networking: DPNSS network services (UK only) • Follow-me Diversion is also a receive-only feature. It allows the call forwarded destination to remotely change the BCM call-forwarding programming (Call Forward All Calls (CFAC) feature) to a different telephone. Note: BCM CFAC must be active, and the destination set/PBX system must support the feature.
Page 333: Using The Redirection Feature
Chapter 36 Private networking: DPNSS network services (UK only) Also, during programming for Call Forward No Answer and Call Forward on Busy, when you enter the Forward to: digits, the system does a validation check with the switch on the number. (Configuration >...
Page 334: To Program Ipl
Chapter 36 Private networking: DPNSS network services (UK only) Programming IPL on a telephone To program IPL Click Configuration > Telephony > Sets. On the panel, locate and click the Capabilities and Preferences tab. Select the DN of the telephone set being programmed. The Details subpanel for that DN appears in the lower portion of the panel.
Page 335: To Set Loop Avoidance During Hardware Configuration
Chapter 36 Private networking: DPNSS network services (UK only) Route Optimization Route Optimization is a DPNSS 1 feature for BCM that allows calls to follow the optimum route between two end PBXs. This allows efficient use of network resources. No system programming is required for the feature when BCM is working as a terminating PBX system.
Page 336 Chapter 36 Private networking: DPNSS network services (UK only) A typical Private Number, using a private access code and dialed from another site on the network, appears below. Private Access + Home Location + Directory = Calling Party Code Code Number Number + 848...
Page 337 Chapter 36 Private networking: DPNSS network services (UK only) Figure 104 DPNSS networking Private Network DPNSS DPNSS Terminating BCM 50 Site C BCM 50 Site A DN # 3333 DN # 111 LOC #496 LOC # 244 DPNSS DPNSS Meridian M1 LOC # 563 BCM 50 Site B BCM 50 Site D...
Page 338 Chapter 36 Private networking: DPNSS network services (UK only) • When creating HLCs for the nodes in your system, avoid numbering conflicts between network nodes and internal DNs, Hunt group DNs. • Program a Private Access Code into your destination routing tables to avoid conflicts with your internal HLC and dest code dialing plan.
Page 339: Private Networking: Using Destination Codes
Chapter 37 Private networking: Using destination codes By properly planning and programming routing tables and destination codes, an installer can create a dialing plan where VoIP lines between BCM are available to other systems in the network. Figure 106 shows a network of three BCMs. Two remote systems connect to a central system. Figure 106 Dialing plan for VoIP routing network New York Toronto...
Page 340 Chapter 37 Private networking: Using destination codes Table 72 VoIP routing for a BCM network (Sheet 2 of 3) Private Received # 2221 Line Access (set) Set 2221 L125: Ring only Line pool access Line BlocA Routing service Route BlocA External # None Routing Destinations...
Page 341 Chapter 37 Private networking: Using destination codes Table 72 VoIP routing for a BCM network (Sheet 3 of 3) Toronto office: Parameter Setting Trunk/Line Data (external) Line 001-004 VoIP Line type BlocA Target line (internal) Line 125 Target line Private Received # 6221 Line Access DN 6221...
Page 342 Chapter 37 Private networking: Using destination codes The call appears on the routing table on the BCM in Santa Clara as 6-221. Because 6 is programmed as a destination code for Toronto on the Santa Clara system, another call is placed using route 001 from Santa Clara to Toronto.
Page 343: Private Networking: Pri Call-By-Call Services
Chapter 38 Private networking: PRI Call-by-Call services The example shown in Figure 107 highlights the use of PRI Call-by-Call services. It shows two offices of a company, one in New York and one in Toronto. Each office is equipped with a BCM and a PRI line.
Page 344 For example, if a public network user dials an employee in the Toronto office, the network delivers digits 4167632221. The BCM routes the call using the last four digits, 2221, to the BCM50. Refer to Table 73 for a description of the settings required for this type of routing service.
Page 345 Chapter 38 Private networking: PRI Call-by-Call services Table 73 PRI Call-by-Call services routing information (Sheet 2 of 2) ServiceID DN type Private Destination Code Normal route Absorb New York office: Parameter Home System Settings Hardware Protocol NI-2 Trunk/Line Data Line 125 Target line Private/Public Received # 6221 Line Access...
Page 346 Chapter 38 Private networking: PRI Call-by-Call services NN40020-603 NN40020-603...
Page 347: Configuring Voice Messaging
Chapter 39 Configuring voice messaging You can have either an internal voice message service, or you can connect your system to an external voice message service, either over the PSTN network to a message center at the central office or through a private network to another system. This panel allows you to choose the type of voice messaging service you want to use.
Page 348: Programming Mwi And Mwc Strings
Chapter 39 Configuring voice messaging Table 74 describes each field on this panel. Table 74 Voice Message Centers Table Attribute Values Description Center <read-only> You can define a maximum of five external voice message centers. Note that any one user can only be connected to one center.
Page 349: Local Voice Messaging Access (Callpilot Manager)
Chapter 39 Configuring voice messaging • No spaces are allowed, including spaces at the end of the string. • A # must be present at the end. • A # or a * cannot be present in the first character. Local voice messaging access (CallPilot Manager) Local voice messaging is configured using a client application.
Page 350 Chapter 39 Configuring voice messaging NN40020-603 NN40020-603...
Page 351: Configuring Centralized Voice Mail
The BCM supports voice-mail configuration either from the local source or by accessing a remote voice mail system located on another BCM, located on a BCM50, or attached to a Meridian 1 system. The system can be configured to more than one voice mail system. However, each telephone can only be configured to one system.
Page 352: Meridian System As Host
Chapter 40 Configuring centralized voice mail For details about setting up the CallPilot parameters and features, refer to the CallPilot Manager Set Up and Operations Guide and the other CallPilot supporting documentation. Meridian system as host If you are using a voice mail system connected to a Meridian 1 as a host system, ensure that the systems are set up to be compatible with each other.
Page 353: To Configure The Host System
Chapter 40 Configuring centralized voice mail • CallPilot or auto attendant is set up and is running for the local system. • You have obtained a list of DNs from the remote systems that require mailboxes. To configure the host system Obtain the voice mail DN by pressing FEATURE 985 on a system telephone.
Page 354: To Set Up A Satellite System For Voice Mail
Chapter 40 Configuring centralized voice mail • Private network has been set up, with MCDN, between the satellite and host system. • The correct routing to the host system is set up and working. • You have supplied a list of DNs to the host system administrator that require mailboxes. To set up a satellite system for voice mail To access the Centralized Voice Messaging panel, select Configuration >...
Page 355: Configuring The System For Centralized Voice Mail
Chapter 40 Configuring centralized voice mail 10 In the Details for DN subpanel, click the Line Assignment tab. 11 Add the line number of the target line programmed for the telephone. 12 Select the Vmsg check box. Configuring Call forward to go to voice mail: 13 For the same DN: Click the Capabilities and Preferences tab.
Page 356: To Set Up A Pri Connection On The System
Chapter 40 Configuring centralized voice mail Apart from line configuration, MCDN over VoIP has the same system configuration. To set up a PRI connection on the system Ensure that the remote voice mail system is set up to accommodate your system on the network.
Page 357: Dialing Plan: Line Pools And Line Pool Codes
Chapter 41 Dialing plan: Line pools and line pool codes The Line Pools panels allow you to: • assign access codes to line pools • add lines to line pools • assign lines pools to telephones (and view which telephones have line pool assigned) •...
Page 358 Chapter 41 Dialing plan: Line pools and line pool codes Figure 109 Dialing Plan - Line Pools table Table 76 describes the fields on the top frame. Table 76 Line Pools table fields Attribute Value Description Pool <read-only> These are the available line pools. Program only the ones for which you have actually assigned lines.
Page 359: Line Pools: Dns Tab
Chapter 41 Dialing plan: Line pools and line pool codes Note: The line pool number must not conflict with the following: • park prefix • external code • direct dial digits • private access code • Public/Private Auto DN • Public/Private DISA DN •...
Page 360: Line Pools: Call-By-Call Limits Tab (Pri Only)
Chapter 41 Dialing plan: Line pools and line pool codes Table 77 Line Pools: DN access to line pools fields (Sheet 2 of 2) Attribute Value Description Delete 1. On the Line Pools table, select the line pool you want to modify. 2.
Page 361 Chapter 41 Dialing plan: Line pools and line pool codes Table 78 describes the fields on the Lines tab. Table 78 Line Pools: Call-by-Call limits fields Attribute Value Description Service Type <read-only> This is the type of CbC service provided on the PRI trunks in the line pool.
Page 362 Chapter 41 Dialing plan: Line pools and line pool codes NN40020-603 NN40020-603...
Page 363: Voip Overview
Public Switched Telephone Network (PSTN). Nortel has several types of IP telephones that connect to the BCM through Ethernet. The IP softphone 2050, which runs as a client application on a PC or PDA, also connects to the BCM through the Ethernet.
Page 364: Telephones
7316, 7316E, 7316E+KIMs, and 7310), cordless telephones (7406), and IP telephones and applications (Nortel IP Phone 2001, IP Phone 2002, IP Phone 2004, and Nortel IP softphone 2050). With this much flexibility, the BCM can provide the type of service you require to be most productive in your business.
Page 365: Key Voip Concepts
Chapter 42 VoIP overview A Local Area Network (LAN) is a communications network that serves users within a confined geographical area. For BCM, a LAN is any IP network connected on the BCM system. Often, the LAN can include a router that forms a connection to the Internet. A BCM can have up to two LAN connections.
Page 366 Chapter 42 VoIP overview Codecs with Silence Suppression, also referred to as VAD (Voice Activity Detection), make VAD active on the system, which performs the same function as having silence suppression active. Also refer to “Silence suppression” on page 529. Note: You can only change the codec on a configured IP telephone if it is online to the BCM, or if Keep DN Alive is enabled for an offline telephone.
Page 367: Voip Trunk Gateways
Chapter 43 VoIP trunk gateways You can use a VoIP trunk to establish communications between a BCM and a remote system across an IP network. Each trunk is associated with a line record (lines 001-012), and are configured in the same way that other lines are configured. However, VoIP trunks have additional programming to support the IP network connection.
Page 368: How Voip Trunks Make A Network
Chapter 43 VoIP trunk gateways Keycodes Before you can use VoIP, you must obtain and install the necessary keycodes. See the Keycode Installation Guide (NN40010-301) for more information about installing the keycodes. Talk to your BCM sales agent if you need to purchase VoIP keycodes. Each keycode adds a specific number of VoIP trunks.
Page 369: Local Gateway Programming
Chapter 43 VoIP trunk gateways Figure 112 Internal call from Meridian 1 tandems to remote PSTN line Node B Node C Calgary Ottawa VoIP trunk (with MCDN, optional) Head office Since the VoIP trunks are configured into line pools, you can assign line pool codes to users who have been assigned access to the VoIP trunks.
Page 370: Routing Table
NPI-TON aliases store dialed number prefixes as well as information about the type of number. A dialed number can be qualified according to its TON (type of number), as well as its NPI (numbering plan identification). Nortel recommends this format over the E.164 format, for encoding dialed numbers and aliases registered with a gatekeeper.
Page 371: Pstn Call To Remote Node
Chapter 43 VoIP trunk gateways • the IP address of the destination system • whether QoS monitor is enabled (this is required if you plan to use PSTN fallback) • transmit threshold so that the system knows when to activate the fallback feature •...
Page 372 Chapter 43 VoIP trunk gateways Figure 113 Calling into a remote node from a public location Santa Clara Ottawa Target line XXX recognizes 2244 PSTN DN 2244 assigned with target line XXX DN 3322 DN 2244 System B System A Dial in: XXX-2244 Gateway: 3...
Page 373: Fallback To Pstn From Voip Trunks
Chapter 43 VoIP trunk gateways Dialout: Ottawa 2244 Gateway: 3 dedicated VoIP trunk private network System B recognizes the code as its own, and uses a local target line to route the call to the correct telephone. Target line XXX recognizes 2244 DN 2244 DN 2244 assigned with target line XXX Fallback to PSTN from VoIP trunks...
Page 374: Describing A Fallback Network
Table panel. Describing a fallback network Figure 114 shows how a fallback network would be set up between two sites. Figure 114 PSTN fallback diagram IP network BCM50 B BCM50 A PSTN Public or Private Public or Private PSTN line...
Page 375: How Fallback Routing Works
Chapter 43 VoIP trunk gateways How fallback routing works CDP network: User dials 2233 (remote system DN: 2233; remote identifier/destination digit: 2). The system absorbs the 8, no other digits are absorbed and the system dials out 2233. If the call falls back to PSTN line, the system still only absorbs the 8. If the PSTN line is on a private network, the system dials out 2233.
Page 376 Chapter 43 VoIP trunk gateways Figure 115 Setting up routes and fallback for call to remote system (CDP dialing code) UDP network: The user dials 2233 (remote system DN: 2233; destination digits/private access code: 555). The system then adds the private access code to the dialout digits. If the call falls back to PSTN line, the system then dials out the private access code (private network PSTN line) or public access number (public PSTN) to the remote system in front of the 2233.
Page 377: Optional Voip Trunk Configurations
VoIP are allowed. A Nortel IP telephone uses ports between 51000 and 51200 to communicate with the system. The system, by default, uses ports 28000 to 28255 to transmit VoIP packets.
Page 378: Gatekeeper Call Scenarios
BCMs and a gatekeeper. Figure 116 BCM systems with a gatekeeper gatekeeper IP:10.10.10.17 BCM50 Ottawa DN 321 IP:10:10:10:18 BCM50 Santa Clara DN 421 IP:10:10:10:19 IP network BCM50 Calgary DN 521 IP:10:10:10:20 This example explains how a call from DN 321 in Ottawa would be made to DN 421 in Santa Clara.
Page 379: Operational Notes And Restrictions
Chapter 43 VoIP trunk gateways BCM Ottawa sends the call Setup message for DN 421 to the gateway at 10.10.10.19, and the call is established. If call signaling is set to Gatekeeper Routed and no pre-granted ARQ has been issued: BCM Ottawa sends an ARQ to the gatekeeper for DN 421.
Page 380 Chapter 43 VoIP trunk gateways • Avoid the use of manual dial on the originating fax machine. In some fax machines, manually dialing introduces a much shorter call time-out. • If manual dial must be used, then the user should wait until the call is answered before starting the fax session.
Page 381: Configuring Voip Trunk Gateways
Chapter 44 Configuring VoIP trunk gateways The following explains how to configure voice over IP (VoIP) trunks on a BCM system for incoming traffic. A VoIP trunk allows you to establish communications between a BCM and a remote system across an IP network. The following path indicates where to where to configure VoIP trunks in Element Manager: •...
Page 382: Configuring Voip Trunk Media Parameters
Chapter 44 Configuring VoIP trunk gateways — If your network uses a gatekeeper (H.323 trunks only), there are also specific settings that must be set on the your system to recognize the gatekeeper, and also within the gatekeeper application, so that VoIP lines are recognized. Refer to “VoIP interoperability: Gatekeeper configuration”...
Page 383: Setting Up The Local Gateway
Chapter 44 Configuring VoIP trunk gateways • Force G.711 for 3.1k audio - When enabled, the system forces the VoIP trunk to use the G.711 codec for 3.1k audio signals such as modem or TTY machines. Set up the local gateway parameters. (“Setting up the local gateway”...
Page 384 Chapter 44 Configuring VoIP trunk gateways — Gatekeeper Routed: uses a gatekeeper for call setup and control. In this method, call signaling is directed through the gatekeeper. — Gatekeeper Routed no RAS: Use this setting for a NetCentrex gatekeeper. With this setting, the system routes all calls through the gatekeeper but does not use any of the gatekeeper Registration and Admission Services (RAS).
Page 385: Setting Up Remote Gateways
Chapter 44 Configuring VoIP trunk gateways Setting up remote gateways The following explains how to set up your system to place calls through VoIP trunks. The system at the other end of the call must be set up to receive VoIP calls. For information about this, refer to “Configuring a remote gateway (H.323 trunks)”...
Page 386: Configuring Voip Line Features
Chapter 44 Configuring VoIP trunk gateways You must also set up target lines when you use these trunks. The following path indicates where to set up target lines in Element Manager: • Element Manager: Configuration > Telephony > Lines > Target Lines Prerequisites Complete the following prerequisites checklist before configuring the modules.
Page 387 Chapter 44 Configuring VoIP trunk gateways Set the restriction and remote restrictions scheduling (Restrictions tab): • Line Restrictions: Enter a valid restriction filter for the Normal schedule, and any other schedules that you want this line to be part of. (outgoing calls) •...
Page 388 Chapter 44 Configuring VoIP trunk gateways NN40020-603 NN40020-603...
Page 389: Voip Interoperability: Gatekeeper Configuration
Refer to the gatekeeper software documentation for information about changing IP addresses. Gatekeeper notes: • The BCM has been tested by Nortel to be compliant with CS 1000 gatekeeper applications. • A gatekeeper may help to simplify IP configuration or the BCM dialing plan; however, it does not simplify the network dialing plan.
Page 390: Cs 1000 Configuration
Chapter 45 VoIP interoperability: Gatekeeper configuration Similarly, to make a CS 1000 system-to-BCM 3.01 (or later) call, ensure that the numbering plan entry assigned to the BCM (through NRS Manager) matches the dialing plan information configured on the CS 1000 systems. CS 1000 configuration You must use NRS Manager to configure the CS 1000.
Page 391: Setting Up Voip Trunks For Fallback
Chapter 46 Setting up VoIP trunks for fallback The following path indicates where to access setting VoIP trunks for fallback in the Element Manager: • Element Manager: Configuration > Resources > Telephony Resources > IP Trunks > H323 Settings tab Task: Configure VoIP trunks to allow fallback to PSTN lines •...
Page 392: To Add The Pstn Route To Other System
Chapter 46 Setting up VoIP trunks for fallback • Ensure the PSTN and VoIP line pools have been configured before you continue with this section. For information about creating a VoIP line pool, see “Configuring VoIP trunk gateways” on page 381.
Page 393: To Assign Pstn Line Pool To Local Pstn Lines
Chapter 46 Setting up VoIP trunks for fallback In the DN Type box, choose Public. To assign PSTN line pool to local PSTN lines Click the route you created for your local PSTN line. In the Use Pool box, type the letter of the line pool for the PSTN line. In the External Number field: leave this field blank.
Page 394: To Configure The Voip Schedule For All Fallback Destination Codes
Chapter 46 Setting up VoIP trunks for fallback Example: Destination code digit: If it is available, you might want to use the same number that you used for the destination code of the gateway. If you have multiple gateways, you could use a unique first number followed by the destination digits, to provide some consistency, such as 82, 83, 84, 85 to reach gateways with destinations digits of 2, 3, 4 and 5.
Page 395: To Set Up The Voip Schedule For Routing Services
Chapter 46 Setting up VoIP trunks for fallback Absorbed length, Normal schedule: If this is a private network PSTN line, and the network uses a CDP dialing plan, and the remote system identifier is 2, which is part of the remote system DN structure, and you specified destination digit of 2 for the remote gateway, then configured a destination code of 82, set this field to 1, so that the 2 is still part of the dialout.
Page 396: To Activate The Voip Line From The Control Set
Chapter 46 Setting up VoIP trunks for fallback To activate the VoIP line from the control set Dial FEATURE 873 from the control set for the VoIP trunk. The phone prompts you for a password. Type the password (default - admin: 23646). Press OK.
Page 397 Chapter 46 Setting up VoIP trunks for fallback Figure 117 Example PSTN fallback DN 2244 DN 3322 Dialout: Dialout: IP network 2244 3322 (Packet Data Network) Ottawa Gateway: 3 Gateway: 2 Santa Clara Gateway destination Gateway destination digit digit (Ottawa): 2 (Santa Clara): 3 Route 867 (VoIP) Route 867 (VoIP)
Page 398 Chapter 46 Setting up VoIP trunks for fallback The systems already communicate through a PRI line, which will be configured to be used for fallback. Both systems already have all keycodes installed for eight VoIP lines, and resources properly allocated for VoIP trunking. For information about keycodes, see the Keycode Installation Guide (NN40010-301).
Page 399 Chapter 46 Setting up VoIP trunks for fallback Table 81 Fallback configuration to create fallback between two systems (Sheet 2 of 2) Task Settings for Settings for Location in Element Manager Santa Clara Ottawa Set up Scheduling to allow Service setting: Manual Configuration >...
Page 400 Chapter 46 Setting up VoIP trunks for fallback If a user in Santa Clara wanted to make a local call in Ottawa, they would dial 29, followed by the local Ottawa number. The digit 2 accesses the remote gateway for the VoIP line. The digit 9 accesses an Ottawa outside line.
Page 401: T.38 Fax
Chapter 47 T.38 fax If you are using the T.38 fax protocol, it is assumed that you have already configured IP trunks and gateways, and that they are functional. For more information on configuring VoIP trunks see “Configuring lines” on page 129.
Page 402: To Enable A T.38 Fax
Chapter 47 T.38 fax Verify that the codecs are set at the default before performing T.38 sessions. To enable a T.38 fax Click Configuration > Telephony Resources. In the Telephony Resources panel, select the row for IP Trunks. The details panel appears. Click the H323 Media Parameters tab or the SIP Media Parameters tab.
Page 403: T.38 Fax Restrictions
Chapter 47 T.38 fax Figure 119 Media Gateways panel Note: For more details and instructions on how to configure media gateways, see “Media Gateways panel” on page 413. T.38 Fax restrictions Note: Fax tones that broadcast through a telephone speaker can disrupt calls on other telephones using VoIP trunks near the fax machine.
Page 404 Chapter 47 T.38 fax • If you must dial manually, wait until the call is answered before you start the fax session. • For Mailbox Call Answering only, if you must dial manually, enter the digit 8 as soon as you hear the mailbox greeting.
Page 405: Port Ranges Overview
Chapter 48 Port ranges overview The Port Ranges panel provides a list of which Ports are currently being used for RTP/UDP, UDP, and Signaling. In the case of RTP over UDP and UDP, it allows changes to the ports being used. For information on configuring port ranges, see “Port Ranges panel”...
Page 406 Chapter 48 Port ranges overview NN40020-603 NN40020-603...
Page 407: Port Ranges Panel
Chapter 49 Port Ranges panel The Port Ranges panel allows you to reserve ports for use by UDP (User Datagram Protocol). The Port Ranges panel consists of three tables: RDP over UDP, UDP, and Signaling. Panel tabs Tasks Features “RTP over UDP Port Ranges” on “Adding new RTP over UDP Port page 407 Ranges”...
Page 408: To Add New Port Ranges In The Rtp Over Udp Table
Chapter 49 Port Ranges panel Figure 120 Port Ranges panel Table 82 RTP over UDP Attribute Value Description Begin <numeric string> The first port in the port range. <numeric string> The last port in the port range. Adding new RTP over UDP Port Ranges You can add up to ten port ranges.
Page 409: To Modify An Entry On The Rtp Over Udp Table
Chapter 49 Port Ranges panel Modifying RTP over UDP Port Ranges To modify an entry on the RTP over UDP table On the RTP over UDP table, select the entry to modify. Type the new value. UDP Port Ranges UDP (User Datagram Protocol) ports are necessary for certain types of network communications. The UDP table has two settings, as shown in Table Table 83 UDP...
Page 410: To Modify An Entry On The Udp Table
Chapter 49 Port Ranges panel Modifying UDP Port Ranges To modify an entry on the UDP table On the UDP table, select the entry to modify. Type the new value. Signaling Port Ranges Table 84 displays port ranges used for signaling. These port ranges cannot be modified. The Signaling Port Ranges table consists of two fields: Table 84 Signaling Attribute...
Page 411: Media Gateways Overview
Chapter 50 Media gateways overview Certain types of IP communications pass through Media Gateways on the BCM. You can control the performance of these communications by adjusting the parameters for echo-cancellation and UDP Redundancy. For detailed information on configuring the Media Gateways, see “Media Gateways panel”...
Page 412 Chapter 50 Media gateways overview NN40020-603 NN40020-603...
Page 413: Media Gateways Panel
Chapter 51 Media Gateways panel The Media Gateways panel allows you to set basic parameters that control IP telephony. The Media Gateways panel contains only two fields: Figure 121 Media Gateways panel Table 85 General Settings Attribute Value Description Echo <drop-down menu>...
Page 414 Chapter 51 Media Gateways panel NN40020-603 NN40020-603...
Page 415: Call Security And Remote Access
Chapter 52 Call security and remote access System restrictions are required to ensure that your system is used appropriately and not vulnerable to unauthorized use. Call security includes: • restriction filters, which limit outbound call access • remote access packages, which limit system call feature access for users calling in over the Private or Public network •...
Page 416: Notes About Restriction Filters
Chapter 52 Call security and remote access Notes about restriction filters A restriction filter is a group of restrictions and overrides that specify the external numbers or feature codes that cannot be dialed from a telephone or on a line. The restriction filters setting allows you to assign restrictions in one step as a single package of dialing sequences that are not permitted.
Page 417: Default Filters (North America)
Chapter 52 Call security and remote access • Removing a restriction from a filter has no effect on the contents of other filters, even if the restriction was copied to them. • You cannot delete a filter. Removing the restrictions programmed on a filter makes it an unrestricted filter but the filter itself is not removed.
Page 418: Default Filters (Other)
Chapter 52 Call security and remote access Table 87 Default filters for program headings Filter Heading Sub-heading System DNs Set restrictions Lines Line restriction Lines Remote restriction Default filters (other) Two profiles have global overrides which do not appear in Element Manager restriction programming and cannot be changed.
Page 419: Remote Call-In Programming
Chapter 52 Call security and remote access Figure 122 Line restriction example Line restriction no long Line 1 distance except Set restriction area code 212, Line 1 718, 214, 713 no long distance except Line 3 area codes 212, Line 3 no long distance Line/Set...
Page 420: Creating Direct Inward System Access (Disa)
Chapter 52 Call security and remote access • Setting up lines to allow users access to the system (“Creating Direct Inward System Access (DISA)” on page 420. • Setting up Remote Access Packages that determine what services the remote users can access. •...
Page 421 Chapter 52 Call security and remote access The system resources, such as dialing capabilities, line pool access and feature access, that a remote user may access depends on the CoS password assigned to them. See “Defining CoS passwords” on page 423.
Page 422: Defining Remote Access Packages
If Answer mode is set to Auto, BCM automatically answers the incoming call. Because most other DPNSS features are extension-specific, Nortel recommends that all DPNSS lines are configured as auto-answer lines.
Page 423: Defining Cos Passwords
Chapter 52 Call security and remote access Create a remote access package by defining the system line pools remote users can access. You then assign the package to individual lines, and to a particular Class of Service password (see “Defining CoS passwords” on page 423).
Page 424 Chapter 52 Call security and remote access Remote users can access system lines, line pools, the Page feature, and remote administration. The exact facilities available to you through remote access vary depending on how your installer set up your system. Note: If the loop start line used for remote access is not supervised, auto-answer does not function and the caller hears ringing instead of a stuttered tone or the system dial tone.
Page 425: External Access Tones
Chapter 52 Call security and remote access External access tones You can hear some of the following tones when accessing BCM from remote location. Table 88 shows the different types of tones and what they mean. Table 88 External access tones Tone What it means System dial tone...
Page 426 Chapter 52 Call security and remote access NN40020-603 NN40020-603...
Page 427: Call Security: Configuring Direct Inward System Access (Disa)
Chapter 53 Call Security: Configuring Direct Inward System Access (DISA) This following describes the telephony configuration that allows users to call from a remote site into the system to access system features. The following paths indicate where to access DISA settings in Element Manager and through Telset Administration: •...
Page 428 Chapter 53 Call Security: Configuring Direct Inward System Access (DISA) • You cannot program a DISA DN or Auto DN to VoIP trunks, because they act as auto-answer lines for private networks. However, you still need to assign remote access packages to the VoIP trunks, to ensure that remote access restrictions are properly applied to incoming calls trying to access the system or the system network.
Page 429 Chapter 53 Call Security: Configuring Direct Inward System Access (DISA) Figure 124 Remote access task overview Networking Configuration Guide...
Page 430: Setting Up Remote Access On Lines
Chapter 53 Call Security: Configuring Direct Inward System Access (DISA) Setting up remote access on lines Setting up remote access on different types of trunks requires you to understand the trunk properties and how you want the system to answer the dial-in calls. Refer to the following information: •...
Page 431 If Answer mode is set to Auto, BCM automatically answers the incoming call. Because most other DPNSS features are extension-specific, Nortel recommends that you configure all DPNSS lines as auto-answer lines.
Page 432 Chapter 53 Call Security: Configuring Direct Inward System Access (DISA) • The line redirection feature allows the originating party to redirect a call that is waiting a connection or re-connection to an alternate destination after a time-out period. Failed calls can be redirected.
Page 433: Call Security: Restriction Filters
Chapter 54 Call security: Restriction filters The following describes the panels that are used to enter restriction filters and restriction overrides. You can have a maximum of 100 restriction filters on the system. The following paths indicate where to access restriction filter settings in Element Manager and through Telset Administration: •...
Page 434 Chapter 54 Call security: Restriction filters Figure 125 Restriction Filters panels 4. Add exceptions. 3. If restricted digits have 1.Select a restriction filter. exceptions, select the digit. 2. Add restricted digits to the Restriction filter. Table 89 provides a description of the fields on the Restriction filters panel. Table 89 Restriction filters and exceptions fields (Sheet 1 of 2) Attribute Value...
Page 435: To Add A Restriction Filter
Chapter 54 Call security: Restriction filters Table 89 Restriction filters and exceptions fields (Sheet 2 of 2) Attribute Value Description Delete 1. On the Filters table, select the filter where you want to delete information. 2. On the Restrictions table, select one or more restrictions to delete. 3.
Page 436: Default Filters
Chapter 54 Call security: Restriction filters 11 Click OK. 12 Next steps: Assign filters to lines, DN records and class of service (CoS) passwords for remote access. Default filters The following provides a list of the default restriction filters for North America and other common profiles: •...
Page 437 Chapter 54 Call security: Restriction filters Note: Default filters are loaded when the system is initialized. A cold start restores the default filters. Filters 02, 03, and 04, although not preset with restrictions and overrides, are the default filters in these programming headings: Filter Heading...
Page 438 Chapter 54 Call security: Restriction filters NN40020-603 NN40020-603...
Page 439: Call Security: Remote Access Packages
Chapter 55 Call security: Remote access packages This panel describes the telephony configuration that is used to control access to system lines by calls coming in from outside the system.The remote access package also allows remote paging capabilities. Note: Callers dialing into the system over private network lines are also considered remote callers.
Page 440 Chapter 55 Call security: Remote access packages Figure 126 Remote Access Packages tables Table 91 describes each field on this panel. Table 91 Remote Access Packages (Sheet 1 of 2) Attribute Values Description Packages table Package <00-99> This designates the package number. This is what is entered in the fields for lines programming for remote access.
Page 441 Chapter 55 Call security: Remote access packages Table 91 Remote Access Packages (Sheet 2 of 2) Delete (line pool) 1. On the Packages table, select the remote package number where you want to delete line pools. 2. On the Line Pool Access table select one or more line pools to delete. 3.
Page 442 Chapter 55 Call security: Remote access packages NN40020-603 NN40020-603...
Page 443: Configuring Cos Passwords For Remote Access
Chapter 56 Configuring CoS passwords for remote access The Class of Service panel allows you to configure passwords for system users who will be dialing into the system over a PSTN/private network to use system features, or for users who must bypass local restrictions on telephones.
Page 444: Adding Or Modifying A Cos Password Values
Chapter 56 Configuring CoS passwords for remote access Figure 127 Class of Service table panel Table 92 describes the fields on this panel. Table 92 CoS password values Attribute Values Description <CoS 00- CoS 99> These numbers identify the password position to the system. Read-only Password <six digits>...
Page 445: To Add Or Modify A Cos Password
Chapter 56 Configuring CoS passwords for remote access • “External access tones” on page 447 Note: You can add a maximum of 99 CoS Passwords. To add or modify a CoS password On the Class of Service table, click the CoS line to which you want to add or modify a password.
Page 446 Chapter 56 Configuring CoS passwords for remote access Remote users can access system lines, line pools, the Page feature, and remote administration. The exact facilities available to you through remote access vary depending on how your installer set up your system. Note: Remote paging is not available on IP trunks.
Page 447: To Access The System Over A Public Network
Chapter 56 Configuring CoS passwords for remote access A sales representative out of the office needs to make long distance calls to the European office. Your system has a leased line to Europe with reduced transatlantic charges. You provide the sales representative with a Class of Service password that gives access to the transatlantic line.
Page 448 Chapter 56 Configuring CoS passwords for remote access Table 93 External access tones (Sheet 2 of 2) Fast busy tone You have done one of the following: • Entered an incorrect CoS password. Your call disconnects after five seconds. • Taken too long while entering a CoS password.
Page 449: Lan Overview
Chapter 57 LAN overview On the BCM main unit, the LAN configuration determines how the Core Module of the BCM communicates with other devices on the LAN. For the BCM with Router, the LAN configuration also includes Router LAN configuration, which determines how the router communicates with devices on the LAN.
Page 450 Chapter 57 LAN overview NN40020-603 NN40020-603...
Page 451: Configuring The Bcm With A Dhcp Address
Chapter 58 Configuring the BCM with a DHCP address To configure the BCM with a DHCP address Set up your DHCP server if it is not already configured on your network. If you are using a BCM50a or BCM50e, consult the router documentation for information on configuring the DHCP network.
Page 452 Chapter 58 Configuring the BCM with a DHCP address NN40020-603 NN40020-603...
Page 453: Data Networking Overview
Chapter 59 Data networking overview The BCM is a converged voice product, and can be connected to virtually any data network, to provide Voice over Internet Protocol (VoIP) support in either a Local Area Network (LAN) or Wide Area Network (WAN) environment. The BCM is also available with an integrated Broadband Ethernet or ADSL Router, which is intended to provide basic data networking and services, as well as Virtual Private Network (VPN) connectivity for small sites.
Page 454 Chapter 59 Data networking overview • Complete the pre-installation checklist. This will make sure that you’ve made all necessary preparations for connecting the BCM. For information on completing the pre-installation checklist, “Data network prerequisites checklist” on page 465. • Configure your router. If you already have a router on your system, you must make some modifications to its configuration for use with the BCM.
Page 455: Ip Subsystem
Chapter 60 IP Subsystem The IP Settings define the basic and advanced IP address and DNS configuration for the BCM main unit. The panel tabs links provide a general description of each panel and definitions of each panel field. Click one of the following links: Panel tabs “Main panel tabs: General settings”...
Page 456: To Modify An Ip Address
Chapter 60 IP Subsystem To modify an IP address Click Configuration > System > IP Subsystem > General Settings tab. Click Modify. The Modify IP Settings dialog box appears. Enter the appropriate values. See Table 94 for a description of these fields. Click OK.
Page 457 Chapter 60 IP Subsystem Figure 128 General Settings panel Table 94 General Settings (Sheet 1 of 2) Attribute Value Description System name <alphanumeric Enter a name to identify the BCM. characters> MAC address <read-only> This is the physical address of the BCM core (not the integrated router).
Page 458: Main Panel Tabs: Internal Subnets
Chapter 60 IP Subsystem Table 94 General Settings (Sheet 2 of 2) Attribute Value Description Default gateway <read-only> The gateway used by the BCM. Note: The gateway must be in the same domain, and reachable, from this IP address. Modify button Click Modify to change IP settings.
Page 459: To Modify A Subnet
Chapter 60 IP Subsystem The Internal LAN is an interface that is used internally by the BCM for digital signal processing. Warning: Only modify a subnet if the address the subnets are currently set to are in-use elsewhere on the network. Modifying a Subnet Warning: You should modify a subnet only if the address the subnet is currently set to are in use elsewhere on the network.
Page 460 Chapter 60 IP Subsystem Figure 129 Internal Subnets tab Table 95 Internal Subnets panel (Sheet 1 of 2) Attribute Value Description Name <alphanumeric> The subnet name. IP Address <IP address> The IP address for the subnet. Subnet Mask <IP address> The mask for the subnet.
Page 461: Main Panel Tabs: Dial-Out Static Routes
Chapter 60 IP Subsystem Table 95 Internal Subnets panel (Sheet 2 of 2) Attribute Value Description Client Name <read-only> Displayed if client has name in Reserved Addresses table, otherwise blank. Lease Start <read-only> When IP lease began. Lease Expiration <read-only> When IP lease expires.
Page 462 Chapter 60 IP Subsystem Figure 130 Main panel tabs: Dial-out Static Routes Table 96 Main panel tabs: Dial-out Static Routes Attribute Value Description Destination Address <IP Address> IP address in Ipv4 format. Specify the IP address of the destination network or host. Default: None.
Page 463: To Add A New Ip Static Route
Chapter 60 IP Subsystem Configuring static routes To add a new IP Static Route Click Configuration > System > IP Subsystem > Dial-out Static Routes tab. Click Add. The Add Dial out Static Route dialog box appears. Enter the Destination, Destination mask, Interface name and Metric fields. Click OK.
Page 464 Chapter 60 IP Subsystem NN40020-603 NN40020-603...
Page 465: Data Network Prerequisites Checklist
Chapter 61 Data network prerequisites checklist Before you set up voice over IP (VoIP) trunks or IP telephones on a BCM, complete the following checklists to ensure the system is correctly set up for IP telephony. Some items in the checklist do not apply to all installations.
Page 466: Network Devices
Chapter 61 Data network prerequisites checklist Network devices Table 98 contains questions about devices on the network such as firewalls, NAT devices, and DHCP servers. • If the network uses public IP addresses, complete 2.d. • If the network uses private IP addresses, complete 2.e. to 2.f. Table 98 Network device checklist Prerequisites 2.a Is the network using DHCP?
Page 467: Keycodes
Chapter 61 Data network prerequisites checklist Keycodes All elements of VoIP trunks and IP telephony are locked by the BCM keycode system. Answer the questions in Table 100 to ensure you have the appropriate keycodes. You can purchase keycodes for the amount of access you want for your system. Additional keycodes can be added later, provided there are adequate resources to handle them.
Page 468: Voip Trunks
7.d Have telephone power and connectors been provisioned? 7.e Do computers that will be using the Nortel Software Phone IP softphone 2050 meet the minimum system requirements, including headset? Note: Additional details available on client page for BCM 7.f Have DN records been programmed for the corresponding IP clients? (Use when manually...
Page 469: Router Overview
Chapter 62 Router overview The following introduces the router, available with the BCM, and explains the two different types of routers available. As well, it introduces the key features you must configure on your router. For more information on the router, see your router documentation. The router is a fully functional and powerful device that connects your LAN to an external data network.
Page 470 Chapter 62 Router overview NN40020-603 NN40020-603...
Page 471: Router Panel
Chapter 63 Router panel Use the router panel to launch the router on your BCM50a/BCM50e. For information about configuring the router, consult the router documentation. Note: The Launch Router button will appear only if you have a BCM50a/BCM50e. Figure 131 Router panel display Accessing your router To access your router Click Launch Router WebGUI Tool.
Page 472 Chapter 63 Router panel NN40020-603 NN40020-603...
Page 473: Vlan Overview
Chapter 64 VLAN overview A virtual LAN (VLAN) is a logical grouping of ports, controlled by a switch, and end-stations, such as IP telephones, configured so that all ports and end-stations in the VLAN appear to be on the same physical (or extended) LAN segment even though they may be geographically separated. VLAN IDs are determined by how the VLAN switch is configured.
Page 474: Specifying The Site-Specific Options For Vlan
IP phones. The DHCP server supplies site-specific options in the DHCP offer message. The following definition describes the Nortel IP Phone 2004-specific, site-specific option. This option uses the reserved for site specific use DHCP options (DHCP option values 128 to 254) and must be returned by the DHCP server as part of each DHCP OFFER and ACK message for the IP Phone 2004 to accept these messages as valid.
Page 475: Dhcp Overview
Chapter 65 DHCP overview On the BCM, DHCP can be set up in a variety of configurations, based on your needs, your existing network, and the version of the BCM that you have. The following explains the various ways that you can configure DHCP on the BCM (including router and main configuration).
Page 476: Main Module Dhcp Client
Chapter 65 DHCP overview If you intend to use the BCM50a or BCM50e as a DHCP server, configure the router to be the DHCP server, as described in the BCM 4.0a Integrated Router Configuration Guide (NN40020-500) or the BCM 4.0e Integrated Router Configuration Guide (NN40020-501). The main module disables its own DHCP server if the route-embedded DHCP server is active.
Page 477 Nortel IP Phones requesting DHCP information. It does not service PCs. This is equivalent to setting the DHCP Status to Enabled (IP Phones Only). The VoIP settings allow any Nortel IP telephone using DHCP to get the BCM address and connect to the system: 47.166.50.108...
Page 478: Default Configurations
Chapter 65 DHCP overview For example, the BCM LAN IP address, S1 and S2 IP address were all set to 47.166.50.80. When the BCM LAN IP address is changed to a static IP address 47.166.50.114, the S1 and S2 IP addresses also change to 46.166.50.114.
Page 479 Chapter 65 DHCP overview Additional settings to configure In addition to these default settings, you must also configure several other settings, including DNS and WINS server settings, and IP set information. Networking Configuration Guide...
Page 480 Chapter 65 DHCP overview NN40020-603 NN40020-603...
Page 481: Dhcp Server Settings Panel
Chapter 66 DHCP Server Settings panel The DHCP Server Settings contains fields for configuring the BCM core as a DHCP server. Note: The DHCP settings panel is unavailable for the BCM50a or BCM50e if DHCP is enabled on the embedded router. In that case, the DHCP Server Settings panel is replaced by a single button that opens the GUI for the embedded router.
Page 482 Chapter 66 DHCP Server Settings panel Figure 132 General Settings tab Warning: Whenever you make changes to the default gateway, the DHCP server may become unavailable to clients for a brief period of time. When making changes, consider doing so at a time that will minimize the effect on users. Table 104 General Settings (Sheet 1 of 2) Attribute Value...
Page 483: Main Panel Tabs: Ip Terminal Dhcp Options
Chapter 66 DHCP Server Settings panel Table 104 General Settings (Sheet 2 of 2) Attribute Value Description The type of WINS node: WINS node <drop-down menu> type • B-node: The BCM first checks the HMHOSTS cache, then uses broadcast for name registration and resolution. •...
Page 484 Chapter 66 DHCP Server Settings panel Figure 133 IP Terminal DHCP Options Table 105 IP Terminal DHCP Options (Sheet 1 of 2) Attribute Value Description Primary Terminal Proxy Server (S1) IP Address <IP address> The IP address of the Proxy Server for IP phones. 10.10.10.10 Port <drop-down list>...
Page 485 If you do not want DHCP to automatically assign VLAN IDs to the telephones, enter VLAN-A:none, in this text box. Note1: The NORTEL IP Terminal VLAN ID string, must be terminated with a period (.). Note2: If you do not know the VLAN ID, contact your network administrator.
Page 486: Main Panel Tabs: Address Ranges
Chapter 66 DHCP Server Settings panel Main panel tabs: Address Ranges Warning: Whenever you make changes to the address range, the DHCP server may become unavailable to clients for a brief period of time. When making changes, consider doing so at a time that will minimize the effect on users. The Address Ranges tab specifies IP addresses to be provided to DHCP clients.
Page 487 Chapter 66 DHCP Server Settings panel Figure 134 Address Ranges tab Table 106 Address Ranges Attribute Value Description Included Address Ranges From IP Address <IP Address, format An IP address specifying the lowest IP address in a 10.10.10.10> range. To IP Address <IP Address, format An IP address specifying the highest IP address in a 10.10.10.10>...
Page 488: To Add A New Included Address Range
Chapter 66 DHCP Server Settings panel To add a new Included Address Range Click Configuration > Data Services >DHCP Server > Address Ranges. Click Add beneath the Included Address Ranges table. The Add Included Address Range dialog box appears. Enter the appropriate From IP address and To IP address ranges. Click OK.
Page 489: Main Panel Tabs: Lease Info
Chapter 66 DHCP Server Settings panel Main panel tabs: Lease Info The lease info panel is a read-only panel describing the current state of DHCP clients currently using the service. The Lease Info panel contains the Customer LAN Lease Info. Figure 135 Lease Info Table 107 Lease Info Attribute...
Page 490 Chapter 66 DHCP Server Settings panel NN40020-603 NN40020-603...
Page 491: Dhcp Configuration With Router
IP address of the BCM LAN also changes. Changing the default router DHCP configuration The DHCP Server also supplies the Nortel specific information that are required by IP sets. This information includes TPS server information and VLAN ids. If the S1 and S2 IP addresses are left as their default, they will automatically be updated when the router’s IP address is changed.
Page 492: Determining The Status For The Dhcp Server
• The network is already using DHCP from another server, but the network contains devices that require the BCM DHCP server, such as Nortel IP Phones. • The network is already using DHCP from another server, and the network does not contain any devices that require the BCM DHCP server.
Page 493: To Disable The Dhcp Server
Chapter 67 DHCP configuration with router Disabling the DHCP server To disable the DHCP server Click Configuration > Telephony > Data Services > DHCP Server > General Settings tab. Select Disabled from the DHCP server is list. Networking Configuration Guide...
Page 494 Chapter 67 DHCP configuration with router NN40020-603 NN40020-603...
Page 495: Firewall Configuration Resources
Chapter 68 Firewall configuration resources Table 108 shows the port configurations that must be allowed on a firewall for the BCM to function properly. Table 108 Firewall configuration Port Type Description 5989 Required for running Element Manager across a firewall SMTP used for Unified Messaging IMAP used for Unified Messaging SNMP management...
Page 496 Chapter 68 Firewall configuration resources NN40020-603 NN40020-603...
Page 497: Dial Up Overview
Chapter 69 Dial Up overview The dial-out interfaces on the BCM offer three key services: • Remote Access allows users at a client station to connect to the BCM across a phone line using Point to Point Protocol (PPP). This allows a person working from home or from a remote location to connect to the BCM LAN through a modem and a phone line.
Page 498: Remote Access Service
Chapter 69 Dial Up overview Remote Access Service Remote Access Service (RAS) allows a client system to dial a telephone number and establish an IP link with a BCM. This link is a connection across a telephone network over an ISDN line, or between a modem on the client system and a modem on the BCM.
Page 499: Automatic Data Dial-Out Service
Chapter 69 Dial Up overview Modem Remote Access Service Specifics For Modem dial in, the Auto-disable feature will automatically disable the modem if no connections are established for a configurable period of time. The Auto-disable feature is turned off by default. The modem can be enabled through Element Manager, using Feature 9*8 or the Startup Profile.
Page 500: Wan Failover Service
Chapter 69 Dial Up overview The BCM will use the user name and password associated with the configured account to authenticate itself with the remote server. The IP addresses assigned to the BCM and the remote server are configurable. Both must be resolvable with the routes programmed for dialing out and the remote server address must match the address supplied when programming the service that will attempt to deliver the packets.
Page 501: Dial Up Interfaces Panel
Chapter 70 Dial Up Interfaces panel The Dial Up Interfaces panel contains four sub-panels: Panel Task Dial-out Interfaces panel Add and configure the dial-out interfaces Global Settings panel Set the WAN Failover interface Modem Dial-In Parameters panel Configure and check the status of the modem dial-in interface ISDN Dial-In Parameters panel Configure and check the status of the ISDN dial-in interfaces Dial-out Interfaces panel...
Page 502: Isdn Interfaces
Subnet mask assigned to the connected interface. ISDN interfaces ISDN interfaces can only be configured on a BCM50 with an integrated BRI module, or on a BCM with a BRI MBM installed in the expansion unit. A maximum of two BRI-ISDN interfaces are supported on each BCM.
Page 503: To Add An Isdn Interface
On the Dial-out Interfaces tab, select the Enable check box next to the ISDN interface to enable. Note: BCM50 R2 will only allow the configuration of two ISDN auto-dialout interfaces. When both of these interfaces are enabled ISDN dial-in will be disabled.
Page 504: To Manually Connect An Isdn Interface
Chapter 70 Dial Up Interfaces panel To manually connect an ISDN interface Click Configuration > Resources > Dial Up Interfaces. On the Dial-out Interfaces tab, select the interface to connect. Select the Enable check box. In the IP Address Specification tab, specify the remote IP address to which to connect. In the top panel, click Connect.
Page 505: Isdn Dial-Out Channel Characteristics
Chapter 70 Dial Up Interfaces panel ISDN Dial-out Channel Characteristics Figure 137 ISDN Dial-out Interface Channel Characteristics tab Table 110 ISDN Dial-out Interface Channel Characteristics fields Attribute Value Description Channel <read-only> There are two ISDN channels available for dial out, ISDN1 and ISDN2.
Page 506: To Modify The Characteristics Of An Existing Isdn Channel
Chapter 70 Dial Up Interfaces panel To modify the characteristics of an existing ISDN channel Click Configuration > Resources > Dial Up Interfaces. Click the ISDN interface to configure. Select the Channel Characteristics tab. Double-click the field to modify. Make the necessary changes. ISDN Dial-out Link Parameters Figure 138 ISDN Dial-out Interface Link Parameters tab Table 111 ISDN Dial-out Interface Link Parameters fields (Sheet 1 of 2)
Page 507: To Configure The Isdn Link Parameters
Chapter 70 Dial Up Interfaces panel Table 111 ISDN Dial-out Interface Link Parameters fields (Sheet 2 of 2) Attribute Value Description IP Header <check box> Enable or disable IP header compression. Compression Note: The feature must be enabled at both ends of the connection.
Page 508: To Add The Modem Interface
<IP Address> The local IP address used on the BCM for the dial-out connection. Default: 10.11.16.1 Modem interface BCM supports one V.34 modem connection to, and from, the BCM50. Caution: Do not modify any of the advanced modem settings on the integrated router. To add the modem interface Click Configuration >...
Page 509: To Enable The Modem Interface
Chapter 70 Dial Up Interfaces panel Enter a logical name in the Interface name field. Select the Automatic dialout check box to use this interface for scheduled service. Refer to “Creating an automatic dial-out interface” on page 521. Click OK. The interface appears in the Dial-out Interfaces table.
Page 510: To Disconnect A Modem Interface
Chapter 70 Dial Up Interfaces panel To disconnect a modem interface Click Configuration > Resources > Dial Up Interfaces. On the Dial-out Interfaces tab, select the interface to disconnect. Click Disconnect. A confirmation dialog box will appear. Click Yes. To delete a modem interface Click Configuration >...
Page 511: To Configure The Modem Link Parameters
Chapter 70 Dial Up Interfaces panel Table 113 Modem Dial-out Interface Link Parameters fields Attribute Value Description Dial-Out Parameters Dial-out number <numeric string> Telephone number to use to connect using the modem interface. If needed, area codes and all necessary digits to dial an external number are included.
Page 512: To Configure The Modem Ip Address Specification
Chapter 70 Dial Up Interfaces panel Modem Dial-out IP Address Figure 141 Modem Dial-out Interface IP Address Specification tab Table 114 Modem Dial-out Interface IP Address Specification fields Attribute Value Description Local IP Address Specification Remote Assigned <check box> When selected, the BCM obtains it’s IP address from the remote end.
Page 513: Wan Failover
Chapter 70 Dial Up Interfaces panel Figure 142 Global Settings panel Table 115 Global Settings field Attribute Value Description Automatic WAN Failover Failover interface <drop-down list> Select one of the existing dial-out interfaces that is not selected for “Automatic dialout”. Dial-out interfaces are provisioned from the Dial-out Interfaces tab in this same section.
Page 514: To Assign A Modem Interface For Wan Failover
Dial-in. It also displays the connection status of the modem if one is in progress. The Modem Dial-in Parameters panel is shown in Figure 143. If the BCM50 has an integrated router (BCM50a or BCM50e), see “Additional configuration to allow network access functionality”...
Page 515 Chapter 70 Dial Up Interfaces panel Figure 143 Modem Dial-In Parameters panel Table 116 Modem Dial-In Parameters fields (Sheet 1 of 3) Attribute Value Description Enable Modem Dial-In <check box> Enable or disable modem dial-in. Default: disabled Allow network access <check box>...
Page 516 Chapter 70 Dial Up Interfaces panel Table 116 Modem Dial-In Parameters fields (Sheet 2 of 3) Attribute Value Description User <read-only> Displays the user that is currently dialed in. Local IP Address <read-only> The local IP address assigned to the dial-in connection. Remote IP Address <read-only>...
Page 517: Additional Configuration To Allow Network Access Functionality
IP address specified in this field. Default: 10.10.14.2 Additional configuration to allow network access functionality If the BCM50 has an integrated router (BCM50a or BCM50e), then you must: • Configure a static route on the integrated router. •...
Page 518: Isdn Dial-In Parameters Panel
If you want DIALIN_PC to access PC1 (192.168.1.50) on the customer LAN, then you must configure a static route on the integrated router to route all traffic for the dial-in IP address to the CSC card on the BCM50 (192.168.1.2). The static route is configured as shown in Table...
Page 519 Chapter 70 Dial Up Interfaces panel Figure 145 ISDN Dial-in parameters fields Table 118 ISDN Dial-In Parameters fields (Sheet 1 of 3) Attribute Value Description Enable ISDN dial-in <check box> Enable or disable ISDN dial-in. Default: disabled Allow network access <check box>...
Page 520 Chapter 70 Dial Up Interfaces panel Table 118 ISDN Dial-In Parameters fields (Sheet 2 of 3) Attribute Value Description Connection State: This is a table that shows the current dial-in state if connected. Note: There is a maximum of two entries in this table (as there are two ISDN channels). This table will display the ISDN channels that are available for ISDN dial in.
Page 521: Creating An Automatic Dial-Out Interface
Chapter 70 Dial Up Interfaces panel Table 118 ISDN Dial-In Parameters fields (Sheet 3 of 3) Attribute Value Description Second dial-in IP <IP Address> The IP address that will be assigned to the BCM side of the Address second dial-in connection. This is only assigned if Remote Assigned is disabled.
Page 522: To Add An Automatic Dial-Out Interface
Chapter 70 Dial Up Interfaces panel To add an automatic dial-out interface Create a Modem or ISDN interface. See “To add an ISDN interface” on page 503 “To add the modem interface” on page 508. Note: If an interface is enabled and configured for manual dial-out, the interface must be disabled before it can be configured for automatic dial-out.
Page 523 Chapter 70 Dial Up Interfaces panel The following tasks can be configured to use dial-up as a primary connection: • SNMP auto trap dial-out • modem user secure callback • CDR records retrieval • backup to a remote destination • log collection to a remote destination •...
Page 524: Static Routes For Automatic Dial-Out Interfaces
Chapter 70 Dial Up Interfaces panel Create a dial-up interface Click Configuration > Resources > Dial Up Interfaces. Click Add. The Add Interface dialog box appears. Select Modem from the drop-down menu. Enter a logical name for the interface in the interface name field. Click OK.
Page 525: Vpn Overview
Typically, the edge devices connecting the branches of a corporation to the ISP use VPN in this mode. BCM is compatible with the Nortel Services Edge Router (formerly known as Shasta 5000) and the following versions of the Contivity VPN Client: •...
Page 526 Appendix A VPN overview IPsec offers the following features: • Branch Office support that allows you to configure an IPSec tunnel connection between two private networks. • Support for IP address translation over encapsulation, packet-by-packet authentication. • Strong encryption and token codes. NN40020-603 NN40020-603...
Page 527: Ipsec
Appendix A VPN overview IPSec Nortel and other third-party vendors support the IPsec tunneling protocol. IPsec is an emerging standard that offers a strong level of encryption (DES and Triple DES), integrity protection (MD5 and SHA), and the IETF-commended Internet Security Association & Key Management Protocol (ISAKMP) and Oakley Key Determination Protocols.
Page 528 Appendix A VPN overview The encryption level you choose is made of three components: • the protocol • the encryption method • the authentication method Protocol The protocol can be ESP or AH. • Encapsulating Security Payload (ESP) provides data integrity, source authentication and confidentiality for IP datagrams by encrypting the payload data to be protected.
Page 529: Silence Suppression
Appendix B Silence suppression The following describes using silence suppression on half-duplex and full-duplex links: Silence suppression, also known as voice activity detection, reduces bandwidth requirements by as much as 50 percent. The following explains how silence suppression functions on a Business Communications Manager network.
Page 530 Appendix B Silence suppression Figure 146 One call on a half-duplex link without silence suppression Conversation Hello Fred. this is Susan Do you have a minute? Fred Here. Sure! Conversation Bandwidth used Channel/Link max Time Voice frames sent even when speaker is silent When silence suppression is enabled, voice packets are only sent when a speaker is talking.
Page 531: Silence Suppression On Full-Duplex Links
Appendix B Silence suppression The effect of silence suppression on half-duplex links is, therefore, to reduce the peak and average bandwidth requirements by approximately 50% of the full transmission rate. Because the sender and receiver are sharing the same bandwidth, this effect can be aggregated for a number of calls. The following figure shows the peak bandwidth requirements for two calls on a half-duplex link with silence suppression enabled.
Page 532 Appendix B Silence suppression Figure 149 One call on a full-duplex link without silence suppression Conversation Hello Fred. This is Susan. Do you have a minute? Fred here. Sure! Conversation Bandwidth used Channel/Link max Time Channel/Link max Time Voice frames sent even when speaker is silent When silence suppression is enabled, voice packets are only sent when a speaker is talking.
Page 533: Comfort Noise
Appendix B Silence suppression When several calls are made over a full-duplex link, all calls share the same transmit path and they share the same receive path. Since the calls are independent, the peak bandwidth must account for the possibility that all speakers at one end of the link may talk at the same time. Therefore, the peak bandwidth for n calls is n * the full transmission rate.
Page 534 Appendix B Silence suppression NN40020-603 NN40020-603...
Page 535: Isdn Overview
Appendix C ISDN overview The following provides some general information about using ISDN lines on your BCM system. Detailed information about ISDN is widely available through the internet. Your service provider can also provide you with specific information to help you understand what suits your requirements.
Page 536 Appendix C ISDN overview Analog versus ISDN ISDN offers significantly higher bandwidth and speed than analog transmission because of its end-to-end digital connectivity on all transmission circuits. Being digital allows ISDN lines to provide better quality signaling than analog POTS lines, and ISDN out-of band data channel signaling offers faster call set up and tear down.
Page 537: Services And Features For Isdn Bri And Pri
Appendix C ISDN overview • Layer 1: A physical connection that supports fundamental signaling passed between the ISDN network (your service provider) and the BCM system. When the LED on a BRI S/T Media Bay Module configured as BRI is lit, your layer 1 is functioning. •...
Page 538: Pri Services And Features
Appendix C ISDN overview Refer to the following features and services: • “Network name display” on page 539 • “Name and number blocking (ONN)” on page 540 • “Call-by-Call Service Selection for PRI” on page 540 • “Emergency 911 dialing” on page 541 •...
Page 539: Service Provider Features
Appendix C ISDN overview Your service provider supplies a Terminal Endpoint Identifier (TEI) and DN to support D-packet service. The TEI is a number between 00 and 63 (in Canada, the default range is 21-63). Your service provider may also supply you with a DN to program your D-packet device. The DN for D-packet service becomes part of the dialing string used by the D-packet to call the packet handler.
Page 540: Name And Number Blocking (Onn)
Appendix C ISDN overview • Receiving Redirected Name • Sending Connected Name • Sending Calling Party Name Consult your customer service representative to determine which of these features is compatible with your service provider. Name and number blocking (ONN) (North America only) When activated, FEATURE 819 allows you to block the outgoing name and/or number on a per-call basis.
Page 541: Emergency 911 Dialing
The actual digit string 911 is not hard-coded into the system. More than one emergency number can be supported. If transmission of internal extension numbers is not required or desired, Nortel recommends that the person in charge of the system maintain a site map or location directory so that emergency personnel can rapidly locate a BCM set given its DID number.
Page 542: Isdn Hardware
Appendix C ISDN overview • allows incoming calls to be routed to sets based on service type and digits received • provides the ability to map user-dialed digits to a service type on a Call-by-Call basis • allows long distance carrier selection through user-dialed Carrier Access Codes Consult your customer service representative to determine how your dialing plan is configured.
Page 543 Appendix C ISDN overview S Reference Point The S reference-point connection provides either a point-to-point or point-to-multipoint digital connection between BCM and ISDN terminal equipment (TE) that uses an S interface. Refer to Figure 152. S loops support up to seven ISDN DNs, which identify TE to the BCM system. Figure 152 S reference point ISDN TE (with terminating resistors)
Page 544: Clock Source For Isdn
Appendix C ISDN overview Figure 153 T reference point ISDN network connection A T loop can be used in combination with an S loop to provide D-packet service for a point-of-sale terminal adapter (POSTA) or other D-packet device. D-packet service is a 16 kbps data transmission service that uses the D-channel of an ISDN line.
Page 545: Isdn Standards Compatibility
NT1, and between the NT1 and the BCM system. The NT1 from Nortel is packaged two ways: • a stand alone package which contains one NT1 card (NTBX80XX) and a power supply (NTBX81XX) •...
Page 546: Ordering Isdn Bri
EKTS (Electronic Key Telephone System) turned off. Use the following packages as a guideline for ordering your National ISDN BRI-NI-1. However, Nortel recommends using packages M or P with the BCM system. Contact your service provider for more information about the capability packages it offers.
Page 547: Supported Isdn Protocols
Appendix C ISDN overview Supported ISDN protocols The switch used by your service provider must be running the appropriate protocol software and the correct version of that software to support ISDN PRI and BRI. Each protocol is different and supports different services. Contact your service provider to make sure that your ISDN connection has the protocol you require.
Page 548 Appendix C ISDN overview NN40020-603 NN40020-603...
Page 549: Codec Rates
Appendix D Codec rates The information in the table below enables the administrator to determine the number of resources that can be maintained on the available system bandwidth. The packet transfer rate must also include the overhead. Note: Using Silence Suppression on G.723 and G.729 can reduce the overall bandwidth consumption by 40%.
Page 550 Appendix D Codec rates RTP over IP Table 120 (Sheet 2 of 2) Payload Overhead Latency (bytes) Packets/frame (bytes) Total (bytes) bytes/s Overhead (%) (msec) 68640 7.25 G.723 21867 173.33 20800 160.00 Note: *These are the default values. NN40020-603 NN40020-603...
Page 551: Index
Index ANY character 251 ARS (automatic route selection). See also call routing ASM (analog station module) Numerics Call Park prefix 231, 273 2-way DID, PRI 541 ATA2 (analog terminal adapter 2) 4ESS Call Park prefix 231, 273 available services 110 external code 269 call-by-call services support 237 authentication header.
Page 552 Index port settings 377 analog telephones 231, 273 signaling method 383 initiating (74) 230, 273 system prefix 230, 273 configuration prerequisites 467 call routing networking 294 tandem networks 44 tandem networking 36 call routing. See also ARS (automatic route selection) using a gatekeeper 378 call signaling, local gateway 120...
Page 553 MCDN 312 auto DN 282 calls answered with DISA 276, 283 CDR (call detail recording) password, with DISA 420, 427 records push passwords 423, 443 automatic 499 programming 444 central administrator direct dial 269 CSU (Channel Service Unit) 108 channel characteristics ISDN 505 Channel Service Unit.
Page 554 Index remote gateway 385 network ID 283 types 221 destination gateway 533 PSTN fallback 245, 374 destination IP public network example 398 DN lengths 221 remote gateway 385 lines 254 DHCP (dynamic host configuration protocol) network 221 IP telephone prerequisites 468 network code 277 network prerequisites 466 public network...
Page 555 programming 269 call-by-call services support 237 type 269 PRI protocol 239, 262 digit facility 270 DMS-250 prime line 270 available services 110 direct dial telephones 231 call-by-call services support 237 PRI protocol 239, 262 Direct Inward System Access. See DISA 283, 420, 427 DISA (direct inward system access) auto assign 467 DID, trunk 421, 430...
Page 556 Index host node 106 ETSI name and number blocking 210 DSX1 build 107 ETSI Euro DTI trunk. See also DTM 39 PRI protocol 239, 262 DTM (digital trunk module) ETSI QSIG clock source 544 advice of charge- end of call (AOCE) 52, 321 ISDN hardware 542 malicious call identification (MCID) 322 DTMF (dual tone multi-frequency)
Page 557 feature GATM (global analog trunk module) 68 - Class of Service (CoS) 447 module mode 104 74 - call park 230, 273 global analog trunk module. See GATM 104 78 - 1.5-second pause 261 ground start 811 - call display 214 answer with DISA 136 811 - call information 214 auto privacy 135...
Page 558 Index target line calls 91 clock source 544 clocking 544 Internal/External #, direct dial programming 269 compared to analog 536 international (special) access code 284 configure link parameters 507 International INWATS, call-by-call services 236 connect interface 504 Internet Security Association and Key Management data transmission speed 538 Protocol (ISAKMP), IPSec 527 deleting an interface 504...
Page 559 lines changing the name 213 identifying 90 Business Communications Manager function 467 numbering 39 least cost routing 243, 252 programming overview 98 voice message center 136 line access call diagram 228 link call-by-call services network 344 at CO, loop start analog lines 134 MCDN network 310 code (F71) 261 signal 134...
Page 560 Index analog camp-on feature 301 auto privacy 135 CDP programming specifics 303 digital creating SL-1 or VoIP networks 356 auto privacy 135 DN types, routing 261 gateway type 311 loop start analog ISDN call connection limitation (ICCL) 47, 320 answer with DISA 136 local access code 284 dial mode 133 M1-IPT requirements 312...
Page 561 M1-IPT 368 IPSec restriction 528 MCDN NAT, network prerequisites 466 special calls 232, 257 national MCDN networking 311 e.164 outgoing calls 223, 279 message waiting indication national access code 284 MCDN 299 MCDN 284 messages National ISDN standards 545 network features 299 Netmask modem network prerequisites 465...
Page 562 Index private networking 297 NT1 (network termination type 1) 544 MCDN check list 303 numbering plans, overview 218 MCDN features 299 MCDN network example 308 MCDN over VoIP 311 Oakley Key Determination Protocols 527 MCDN routing 310 MCDN Zone ID for SRG 285 changing DN length 225, 271 MCDN, break-in 301 ONN (outgoing name and number) blocking...
Page 563 DPNSS 1 networking 52 private auto DN 282 system diagram 33, 289 DN received number lengths 232, 272 port private DISA DN disable-enable 87 received number lengths 232, 272 port settings 377 Private DN length numbering overview 219 ports firewalls 377 private DN length, UDP dialing plan 283 legacy networks 377 private DN, route programming 261...
Page 564 Index MCDN (Meridian Customer Defined Networking) public network code 277 special calls 232 public network plan 277 MCDN special route codes 261 to tandem network 325 outgoing calls 286 public network dialing plan 277 private services call 540 public networking private, call-by-call services 236 outgoing calls 223, 279 process map...
Page 565 ISDN 498 private DN 261 loop start trunks 421, 430 public DN 261 modem 498, 499 Use pool 261 numbering overview 218 router package, CoS programming 444 port settings 377 PRI 422, 432 routing 242, 256 PRI trunk 431 call-by-call routing table 238 private auto DN 282 call-by-call services network 344 private DISA DN 283...
Page 566 Index Selective LIne Redirection, see SLR 212 system codes 347 service code square system 33 North American ONN blocking 210 service code, ONN blocking 188 MCDN Zone ID 285 Virtual Private Network ID 285 service selection 108 Start DN service setting, manual 395 overview 218 service type static routes...
Page 567 E&M network diagram 40 IP trunks, remote access 425, 448 E&M private networking 37, 315 remote access tones 425, 447 full autohold, E&M 135 trademarks 2 parameters Transmit Threshold 385, 398 DSX1 build 107 transport mode, IPSec 525 framing 107 internal CSU 107, 108 trunk line coding 107...
Page 568 Index Virtual Private Network ID 285 virtual private networks, see VPN 525 Wait for dial tone (804) 261 VLAN i-series telephones 468 Business Communications Manager function 467 Voice Activity Detection See VAD 529 failover 500, 513 dial-out interface 497 Voice Activity Detection. See VAD 529 ISDN 514 voice jitter buffer 124, 127 modem 514...

Nortel BCM50 Configuration Manual

Chapter 1 Getting Started with BCM

Chapter 2 System Telephony Networking Overview

Chapter 3 Telephony Programming: Configuring Call Traffic

Chapter 4 Application Resources Overview

Chapter 5

Application Resources Panel

Chapter 6 Module Configuration: Trunk Modules

Chapter 7 Managing Modules

Chapter 8 Lines Overview

Chapter 9 Configuring Telephony Resources

Chapter 10 Configuring Lines

Chapter 11 Configuring Lines: Target Lines

Chapter 12 Configuring Lines: PRI

Chapter 13 Configuring Lines: T1-E&M

Chapter 14 Configuring Lines: T1-Loop Start

Chapter 15 Configuring Lines: T1-Digital Ground Start

Chapter 16 Configuring Lines: T1-DID

Chapter 17 Configuring Lines: DASS2 Lines

Chapter 18 Configuring Lines: DPNSS Lines

Chapter 19 BRI ISDN: BRI Loop Properties

Chapter 20 BRI ISDN: BRI T-Loops

Chapter 21 Programming BRI S-Loops, Lines, and ISDN Devices

Chapter 22 Configuring CLID on Your System

Chapter 23 CLID: Name Display

Chapter 24 Dialing Plans

Chapter 25 Dialing Plan: Routing Configurations

Chapter 26 Dialing Plan: Routing and Destination Codes

Chapter 27 Dialing Plan: System Settings

Chapter 28 Dialing Plan: Public Network

Chapter 29 Dialing Plan: Private Network Settings

Chapter 30 Public Networking: Setting up Basic Systems

Chapter 31 Public Networking: Tandem Calls from Private Node

Chapter 32 Private Networking: MCDN over PRI and Voip

Chapter 33 Private Networking: Basic Parameters

Chapter 34 Private Networking: MCDN and ETSI Network Features

Chapter 35 Private Networking: PRI and Voip Tandem Networks

Chapter 36 Private Networking: DPNSS Network Services (UK Only)

Chapter 37

Private Networking: Using Destination Codes

Chapter 38

Private Networking: PRI Call-By-Call Services

Chapter 39 Configuring Voice Messaging

Chapter 40 Configuring Centralized Voice Mail

Chapter 41 Dialing Plan: Line Pools and Line Pool Codes

Chapter 42 Voip Overview

Quick Links

Related Manuals for Nortel BCM50

Summary of Contents for Nortel BCM50