Avaya BCM Solutions Test Lab Business Communication Manager BCM 50 and BCM450 Release 6.0 Configuration Guide for Skype SIP Connect Service 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 Skype. 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 July 23, 2010 0.1 October 1, 2010 1.
2.0 System Software / Loadware To achieve successful interoperability between the BCM and Skype 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.
3.0 Features 3.1 Features Supported • • • • • • • • • • The following are capabilities tested and validated: Basic calls (G711 a-law/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. FAX is not supported by Skype. 2. The Windows Skype client version 4.2.0.
4.0 Overview Figure 4-1 shows a typical deployment of a SIP trunk between BCM R6 and Skype. In the deployment, a SIP unaware layer 3 device with NAT and firewall is deployed between the BCM and Skype. The IP address assigned to the BCM and all IP phones is private and since Skype does not support remote NAT compensation, the BCM is configured to compensate for the presence of the local NAT.
5.0 System Configuration This section provides procedures for configuring a SIP trunk on BCM Rls. 6.0 to Skype. 5.1 BCM Configuration In order to configure a SIP trunk between BCM and Skype, do the following: 5.1.1 IP Trunks Settings Configuration 1. Navigate to Configuration Resources IP Trunks General 2. Click on the “IP Trunks Settings” tab 3. Ignore in-band DTMF in RTP: by clicking on the check box next to it. 5.1.2 SIP Media Parameters Configuration 1.
5.1.4 Create Public SIP Trunk Accounts 1. Navigate to Configuration Resources IP Trunks SIP Trunking 2. Select the Public tab. 3. Next select the Accounts tab. 4. Click on the Add button. 5. In the Add Account dialog box that pops up, click on Select Template. 6. In the Choose Template dialog box, choose one of the Skype templates 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.
o Set the CLID Override value to a Skype user id. o Set the PAI CLID Override to the same value as the CLID Override. o Click the OK button 10. Navigate to Configuration TelephonyGlobal SettingsFeature Settings 11. Provide a name in the Business Names section 12. Navigate to Configuration Telephony SetsActive Sets 13. For each active set in the Active sets table, change the Name column to name of user of that BCM phone. 14. For each active set in the Active sets table, cconfigure the Pub OLI.
If multiple SIP trunk User Accounts are associated with the same Skype SIP profile, SIP registration can only be turned on for one of the SIP trunk user accounts associated with the same Skype SIP Profile. SIP Trunk User Accounts are associated with Skype SIP profiles by way of using SIP User credentials of the Skype SIP Profile. BCM Outgoing Name and Number (ONN) Blocking feature (F819) is compatible with Skype Connect and can be used to block ONN on a call-by-call basis. 5.2 Dialing Plan 5.2.
15. Configure a destination code to route dialed digits by clicking on the Add button. Digits that begin with this destination code will be presented to the SIP trunking component on the BCM for routing towards the Service Provider. 16. In the Add Destination Code dialog box, enter a numeric number for the destination code and click on the OK button. 17. Select the row representing the Destination Code entered in the previous step 18.
• Set the Destination Digits to the value provide as the External Number in Step 10 of section 5.2.2 • In the ITSP Account drop down list, select the Skype account 9. Click OK 5.2.4 Configuring Incoming Calls from SKYPE 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.
4. Click on the Launch CallPilot Manager. 5. This launches a web browser to the BCM. Log in with the administrator credentials 6. On the left hand navigation menu, click on Auto Attendant 7. In the Line Administration web page, scroll down to the Target Line configured in Step 1. 8. Under the Command Column, click Change 9. In the Line Properties web page, select Auto-Attendant as the Answer Mode 10. Click the Submit button. 5.2.
©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.
