Summary of the content on the page No. 1
AT&T IP Flexible Reach Service
Nortel BCM50 Release 3.0 SIP Configuration Guide
AT&T VOIP
Nortel BCM50 Release 3.0 SIP
Configuration Guide
For Use with AT&T
IP Flexible Reach Service
Issue 0.7
12/26/2007
© 2007 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T
logo and all other AT&T marks contained herein are trademarks of AT&T
Intellectual Property and/or AT&T affiliated companies. All other
marks contained herein are the property of their res
Summary of the content on the page No. 2
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide TABLE OF CONTENTS 1 Introduction................................................................................................................. 4 1.1 Pre-IP PBX Configuration Activity.................................................................... 4 1.2 Customer Questions............................................................................................ 4 1.3 Trouble Reporting..............
Summary of the content on the page No. 3
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide TABLE OF FIGURES Figure 1: AT&T IP Flexible Reach Network ..................................................................... 8 Figure 2: BCM50 Software Version Number................................................................... 11 Figure 3: BCM50 Lists of Applied Patches...................................................................... 12 Figure 4: Available VoIP Trunks..................
Summary of the content on the page No. 4
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide 1 Introduction This document provides a configuration guide to assist Nortel Networks BCM50 administrators in connecting to AT&T IP Flexible Reach service via SIP trunks. This document does not describe procedures to configure the BCM50 for advanced functionality. For more information and procedures, please refer to the Nortel technical documentation found on the Nortel website. 1.1 Pre-IP PBX C
Summary of the content on the page No. 5
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide Company location Administrator name and phone number IP PBX name and software version Customer Configuration Guide – Issue number and date 1.3 Trouble Reporting Nortel and AT&T will make every effort to quickly resolve reported troubles. The time required for trouble shooting can be reduced if the customer has the necessary detailed information available when reporting a problem. Prior to repo
Summary of the content on the page No. 6
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide Issue 0.6 December 12, 2007; Further explanation for software release in 4.1 and VoIP trunk licenses in 4.2 © 2007 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks contained herein are the property of their respective owners. Issue 0.7 Page
Summary of the content on the page No. 7
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide 2 Special Notes Emergency 911/E911 Services Limitations While AT&T IP Flexible Reach services support E911/911 calling capabilities in certain circumstances, there are significant limitations on how these capabilities are delivered. Please review the AT&T IP Flexible Reach Service Guide in detail to understand these limitations and restrictions. Calling Number Restricted / Private not supported Fo
Summary of the content on the page No. 8
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide 3 Overview This section provides a service overview of the Nortel Business Communication Manager 50 (BCM50) IP PBX integration with AT&T IP Flexible Reach service. For an overview of Nortel BCM 200/400 for IP Flexible Reach; please reference a separate document named “Nortel BCM 200/400 Configuration Guide.” PST Application Server Network Gateway Legacy Border AT&T Managed Circuit Call Contr
Summary of the content on the page No. 9
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide o 12 digital station ports supporting digital phones. o 4 Analog Loop Supervised Trunks (NA networking standards). o 4 Analog Station interfaces with message waiting and CLID support. o 3 port 10/100 Ethernet switch with auto sensing and auto polarity. Two of these ports also support connection of optional expansion units. o 1 10/100 Ethernet port reserved for direct access management of the system o
Summary of the content on the page No. 10
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide Fax was tested and is supported on the BCM50 using the T.38 or G.711 fax protocol through the AT&T IP Flexible Reach network to/from the following: • PSTN • Legacy PBX site with Cisco gateway • Another BCM50 IP PBX site © 2007 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affili
Summary of the content on the page No. 11
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide 4 Configuration Guide This configuration guide specifies the Nortel BCM50 screens that must be configured and updated to support the AT&T IP Flexible Reach service. 4.1 Nortel BCM50 Version and Feature Requirements The Nortel Networks BCM50 must be running at least software version 6.0.2.05.237. You can check the version of BCM50 by viewing the following screen under Administration Software Managem
Summary of the content on the page No. 12
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide The following BCM50 patches must be applied. To verify any installed patches on the system: under the BCM50 Element Manager’s “Administration” tab, click on “Software Management” and select “Software Update History.” Figure 3: BCM50 Lists of Applied Patches Patch Name Version Description BCM050.R300.FEPS 2-2 UPDATE to FEPS © 2007 AT&T Intellectual Property. All rights reserved. AT&T, the AT
Summary of the content on the page No. 13
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide 4.2 IP Trunks Voice over IP (VoIP) trunks, are signaling channels that simulate how CO lines work. However, VoIP trunks transmit data to the IP network over a LAN or IP network rather than over physical lines. Once the VoIP trunks are set up, you can assign them to line pools, and program their behavior in the same way you would PRI lines. VoIP trunks use line numbers 001 to 012. These line records
Summary of the content on the page No. 14
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide Figure 4: Available VoIP Trunks Note: If no active VoIP lines are present, check to see if either SIP or IP Trunks licenses are installed. If so, try restarting the “feps” service on the BCM50. This can be done by going to Administration General Service Manager, and restarting the “feps” service. Also, check under Configuration Resources Application Resources, and ensure that the SIP (or IP) T
Summary of the content on the page No. 15
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide Under Configuration Telephony Dialing Plan; select “Line Pools.” In this case we selected “BlocA” under the “Pool” tab. We will use this line pool to access the VoIP trunks. Additionally, all DN numbers that need to access the VoIP trunks must be added to this pool. Please see the following screen shots for an example configuration. Figure 6: Assigning Line Pool to IP Trunks Figure 7: Assi
Summary of the content on the page No. 16
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide © 2007 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks contained herein are the property of their respective owners. Issue 0.7 Page 16 of 37
Summary of the content on the page No. 17
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide Under Configuration Telephony Dialing Plan General, we define the DN length to 4 digits. Figure 8: Configuring General DN Length Under Configuration Telephony Dialing Plan Public Network, we define the Public Received number length to “4” digits and Public network dialing plan to “National.” Figure 9: Configuring Public Received Number Length and Dialing Plan © 2007 AT&T Intellectual Pr
Summary of the content on the page No. 18
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide Under Configuration Telephony Dialing Plan Private Network, we define the Private Received number length to “4” digits. Figure 10: Configuring Private Received Number Length © 2007 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks contained here
Summary of the content on the page No. 19
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide Under Configuration Telephony Dialing Plan Routing: Select the “Routes” tab and ensure there is an entry for “BlocA.” In this case “001” is the route number and the DN type is specified as “National.” See figure below. Figure 11: Assigning a Route for IP Trunks © 2007 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trade
Summary of the content on the page No. 20
AT&T IP Flexible Reach Service Nortel BCM50 Release 3.0 SIP Configuration Guide Under Configuration Telephony Dialing Plan Routing, select the “Destination Codes” tab to assign a destination code for the IP trunks. Configure a destination code “9” or to whatever code you want to access for outside (IP off-net) call that will be presented to the AT&T service for routing. In this case, when “9” is dialed we wish to push the dialed string to the IP trunk for routing. See figure b
