Business Communication Manager BCM 50 and BCM450 Release 6.0 Configuration Guide for MTS Allstream SIP Trunking Issue 1.0 Abstract This document provides guidelines for configuring a SIP Trunk between a BCM50 or BCM450 Release 6.
Table of Contents TABLE OF CONTENTS .......................................................................................................................................................... 2 1.0 INTRODUCTION ............................................................................................................................................................... 3 1.1 DOCUMENT CHANGE HISTORY ................................................................................................................
1.0 Introduction This document is intended to provide information to installers configuring a BCM50 or a BCM450 Release 6.0 for SIP trunk inter-working with MTS Allstream. The information provided is specific for the SIP trunk inter-working, unrelated configuration is not considered within this guide. This document assumes that the installer has undergone Avaya approved BCM training and has a working knowledge of BCM installations. 1.1 Document Change History Date Version September 3, 2010 0.
2.0 System Software / Loadware To achieve successful interoperability between the BCM and MTS Allstream SIP Trunking, the various network elements must be running the version of software as shown below: System BCM 50 BCM450 BCM Phones Platform All platforms All platforms All supported phones Firmware Release 6.0 GA build 1.02. Release 6.0 GA build 1.02. As provided by release 6.0 GA build 1.02. Table 1 Validated Equipment and Software NC; Reviewed: 11/11/2010 ©2010 Avaya Inc. All Rights Reserved.
3.0 Features 3.1 Features Supported • • • • • • • • • • The following are capabilities tested and validated: Basic calls (G711 u-law and G729 both with 20ms packetization) Calling line (number) identification presentation Calling line (number) presentation restriction DTMF (RFC 2833) Call hold Call transfer (attended and unattended) Conference calls Call forward Call waiting 3.2 Technical Caveats 1.
Overview Figure 0-1 shows a typical deployment of a SIP trunk between BCM R6 and MTS Allstream. In the deployment, a SIP unaware router with NAT and firewall is deployed between the BCM and MTS Allstream. SMB network protected by a NAT/FW with BCM on the LAN Local NAT Compensation A Data Network B NAT/FW TDM Phone BCM MTS Allstrea MTS Allstream SIP C Phone PSTN D Phone Figure 0-1 SIP Trunking between BCM and MTS Allstream NC; Reviewed: 11/11/2010 ©2010 Avaya Inc. All Rights Reserved.
4.0 System Configuration This section provides procedures for configuring a SIP trunk on BCM Rls. 6.0 to MTS Allstream. 4.1 BCM Configuration In order to configure a SIP trunk between BCM and MTS Allstream, do the following: 4.1.1 SIP Media Parameters Configuration 1. Navigate to Configuration Resources IP Trunks SIP Trunking 2. Select the Media Parameters tab. 3. In the Preferred Codecs section, configure G.729, G.711-uLaw as the first and second preferred codec respectively.
6. In the Choose Template dialog box, choose the MTS Allstream template (MTSAllstream.sipt) and click on the Select button. 7. In the Add Account dialog box that opens up a. Provide a unique name for this account in the Name field b. Provide a descriptive name for this account in the Description field c. Leave the rest of the parameters at their default values. 8. Click on the OK button 4.1.4 Customize the Account 1. Navigate to Configuration Resources IP Trunks SIP Trunking 2.
4.2 Dialing Plan 4.2.1 Line Pool Configuration 1. Under Configuration Telephony Dialing Plan; select Line Pools. 2. Select BlocA. 3. Click on the “Add” button to add DNs of sets that need to access the above line pool. 4.2.2 Dial Plan Configuration 1. Under Configuration Telephony Dialing Plan Public Network, define the Public Received number length. Check with MTS Allstream for the appropriate value. 2. Set the Public Network Dialing Plan to Public (Unknown) 3.
17. Under Normal Route column, double click and enter the route entered in Step 6. 18. Under the Absorbed Length column, specify the number of digits that will be absorbed before pre-pending the configured External number configured in Step 9 and sending the rest of the digits to the SIP trunking component. 19. While the row representing the Destination Code enter in Step 15 is selected, in the Alternate Routes table that shows up below, click on an unused schedule 20.
4.2.4 Configuring Incoming Calls from MTS ALLSTREAM to BCM This can be done in one of two ways; 1. The DID assigned to the BCM can be associated with a target line assigned to a group of set(s) and all calls to the DID will be routed those set(s). 2. All calls to the DID assigned to the BCM can be answered by the Auto Attendant (AA) and from there, a DN can be entered to reach a phone on the BCM 4.2.4.1 Assigning DID to BCM Phones for Incoming Call 1.
4.2.5 Giving Access to SIP Trunks To give access to BCM phones to make outgoing calls across the SIP trunk; 1. Navigate to ConfigurationTelephonySetsActive Sets 2. Click on the Line Access tab 3. Click on the DN of each the registered BCM phones in turn and click on the Line Pool Access tab 4. Click on the Add button 5. In the Add Line Pool dialog box, type bloca 6. Click OK 7. Repeat steps 3 to 6 for each of active sets on the BCM. NC; Reviewed: 11/11/2010 ©2010 Avaya Inc. All Rights Reserved.
©2010 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc. Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice.
