Avaya BCM50 Configuration Guide

Avaya BCM Solutions Test Lab

Business Communication Manager BCM 50 and BCM450

Release 5.0 Configuration Guide for Bell Canada SIP

Trunking Issue 1.0

Abstract

This document provides guidelines for configuring a SIP Trunk between a BCM50 or BCM450 Release 5.0 and Bell Canada SIP Trunking Service

Reviewed: 04/12/2010

2010-00000219

BCM Solution Test Lab 1 of 34

BCM50R5_BCM450_Configuration_Guide_For_Bell

TABLE OF CONTENTS.............................................................................................................................................2

1.0 INTRODUCTION..................................................................................................................................................4

1.1

PREREQUISITES..................................................................................................................................................4

1.1.1 Required Reading.....................................................................................................................................4

1.2

DOCUMENT CHANGE HISTORY ............................................................................................................................4

2.0 SIP TRUNKING SERVICE OVERVIEW ..............................................................................................................5

2.1

WHAT IS SIP TRUNKING?....................................................................................................................................5

3.0 REFERENCE TOPOLOGY..................................................................................................................................6

4.0 TESTED EQUIPMENT.........................................................................................................................................7

5.0 FEATURES ..........................................................................................................................................................8

5.1

FEATURES SUPPORTED ......................................................................................................................................8

5.2 TRUNK GROUP SELECTION FOR ORIGINATING CALLS............................................................................................8

5.3 FEATURES NOT SUPPORTED..............................................................................................................................10

6.0 DEPLOYMENT CONSIDERATIONS.................................................................................................................11

6.1

MEDIA CODEC’S FOR BELL SIP TRUNKING.........................................................................................................11

7.0 REQUIRED SERVICE CONFIGURATION INFORMATION..............................................................................12

8.0 SIP TRUNKING DIAL PLAN OVERVIEW.........................................................................................................13

9.0 CONFIGURE DNS (OPTIONAL) .......................................................................................................................14

9.1

BELL RESOLVES PBX DOMAIN ...........................................................................................................................14

PBX RESOLVES BELL SERVICE DOMAIN..............................................................................................................14

9.2

10.0 SYSTEM CONFIGURATION ...........................................................................................................................15

10.1

VOIP TRUNK SETTINGS...................................................................................................................................15

Select Resources Select Resources Select Resources Select Resources Select Resources Select Resources

11.0 IP SET SETINGS .............................................................................................................................................20

Select Resources Select Resources

Telephony Resources Æ Module IP Trunks Æ IP Trunks Settings..............................15

Telephony Resources Æ Module IP Trunks Æ SIP Settings........................................15

Telephony Resources Æ Module IP Trunks Æ SIP Proxy............................................16

Telephony Resources Æ Module IP Trunks Æ SIP Media Parameters.......................17

Telephony Resources Æ Module IP Trunks Æ SIP URI Map ......................................18

Telephony Resources Æ Module IP Sets Æ SIP Authentication..................................19

Telephony Resources Æ Module IP Sets Æ IP Terminal Global Settings ...................20

Telephony Resources Æ Module IP Sets Æ IP Terminal Details.................................21

Reviewed: 04/12/2010

Avaya BCM Solutions Test Lab

Application Notes

BCM50_BCM450_R5_Configuration_Bell

2 of 34

Reserved.

2010-00000219 Page 2 of 34

12.0 DIALING PLAN SETTINGS.............................................................................................................................22

Select Telephony Select Telephony Select Telephony Select Telephony Select Telephony

13.0 SET CONFIGURATION...................................................................................................................................25

Dialing Plan Æ Public Network.......................................................................................22

Dialing Plan Æ Routing Æ Routes .................................................................................23

Dialing Plan Æ Routing Æ Destination Codes...............................................................23

Dialing Plan ÆLine pools ...............................................................................................24

Sets Æ Active Sets Æ Line Access Æ Line Pool Access .............................................24

Select Telephony Select Telephony

14.0 ANALOG SETS................................................................................................................................................27

Select Telephony

15.0 QOS..................................................................................................................................................................28

DATA Services

16.0 FAQ & TROUBLESHOOTING.........................................................................................................................29

16.1

SYSTEM MONIT ORI NG W ITH BCM MONITOR.....................................................................................................29

16.2 REAL-TIME DISPLAY OF BCM ALARMS .............................................................................................................31

17.0 ACRONYMS.....................................................................................................................................................33

Sets Æ Active Sets Æ Line Access Æ Line assignment...............................................25

Sets Æ Active Sets Æ Line Access Æ Line Pool Access .............................................26

Sets Æ Active Sets ÆActive SetsÆ Capabilities and PreferencesÆCapabilities........27

QOS...................................................................................................................................28

Reviewed: 04/12/2010

Avaya BCM Solutions Test Lab

Application Notes

BCM50_BCM450_R5_Configuration_Bell

3 of 34

Reserved.

2010-00000219 Page 3 of 34

1.0 Introduction

This document will cover the basic setup of the Nortel BCM50 R5.0 and BCM450 R5.0 for us e with the Bell Canada SIP Trunking service.

• Testing was performed in accordance to the Bell Canada test plan and all the core features of the SIP Trunking service were verified.

• The BCM450 configuration detailed in this document was verified in a lab environment with a minimal configuration used to ensure proper interoperability between Bell’s SIP network and the system under test.

DISCLAIMER: The configuration described in this document details only the minimum configuration required for interoperability to be successful; so care must be taken by the network administrator to ensure this configuration is valid for their deployment network, accounting for version differences, and possible feature conflicts with their CPE environment as well. Note all test cases where run BCM450 R5.0 hardware. Minimal testing was performed on the BCM50R5.0 system as the function of the BCM50 R5.0 and BCM450 R5.0 systems are identical this service.

1.1 Prerequisites

This document assumes the reader possesses administrator-level kno wled ge in regard to the deployment and configuration of the BCM line of products and there associated Management tools. Based on that assumption, this document will only cover what is necessary to connect the specified the BCM hardware to the Bell SIP Trunking service. The document does not cover any non-trunk-related configurations or any complex trunk-routing scenarios specific to a given customer deployment scenario.

1.1.1 Required Reading

The reader is urged to consult the Bell SIP Trunking Service Interface Document for more detailed coverage of the content in this guide. The Service Interface Document includes detailed coverage of the SIP –Trunking service parameters, including example SIP messages, full coverage of the production version of the dial-plan, and detailed coverage of codec support and policies for trans-coder invocation.

1.2 Document Change History

Date, Version Summary of Changes April 12th, 2010, Issue 1.0 original publication

Reviewed: 04/12/2010

Avaya BCM Solutions Test Lab

Application Notes

BCM50_BCM450_R5_Configuration_Bell

Reserved.

2010-00000219 Page 4 of 34

4 of 34

2.0 SIP Trunking Service Overview

2.1 What is SIP Trunking?

The SIP Trunking Service is a critical element for customers migrating to VoIP. The SIP Trunking Service provides customers with a voice gateway (typically an IP-based PBX) over their data network for calls to and from the PSTN.

An IP Trunk consists of a single virtual voice channel with local calling rights in the rate centre in which it is associated. The terminology used to describe the virtual voice channel is a “concurrent call” (“DS-0 equivalent” is also used sometimes). Customers can buy one or more concurrent calls to enable more than one call to be established simultaneously. Purchasing multiple trunks is referred to as a trunk group, so purchasing a trunkgroup with ten trunks would allow ten simultaneous calls to be carried on at once using that trunk group.

A rate centre represents the local calling area wherein customers can call each other without incurring toll charges. If a customer buys one trunk (one concurrent call) in the Toronto rate centre (416), they have purchased the capability for anyone on their corporate network to make one local call within that rate centre. If the customer places a trunk call to a location that is outside their local rate center, they would be charged for a long dista nce call. Callers in the Toronto 416 calling area must pay long distance to call the 514 rate centre in Montreal, for instance.

Reviewed: 04/12/2010

Avaya BCM Solutions Test Lab

Application Notes

BCM50_BCM450_R5_Configuration_Bell

5 of 34

Reserved.

2010-00000219 Page 5 of 34

3.0 Reference Topology

Primary Service Site

Nortel Device

Signallin

BCM

Media Path from IP

phone to

M e d i a

S g n a l l i g

Network

Media and Signaling from

customer

Media

Signalling

Medi

Sign lling

Redundant

Signaling and

Media Termination

poin

Backup redundant Service

IP Border

elemen

IP Border

element

SIP

Server

And GW

Device

Telephone

Network

SIP

Server

And GW

Device

Site

Reviewed: 04/12/2010

Avaya BCM Solutions Test Lab

Application Notes

BCM50_BCM450_R5_Configuration_Bell

6 of 34

Reserved.

2010-00000219 Page 6 of 34

4.0 Tested Equipment

Bell service is compatible with BCM50 and BCM450. The following list summarizes the version and patch levels of the hardware that has been validated as compatible in the Bell lab:

• BCM450 R5.0 System Software Version 9.0.1.22.542 patch 002.200912-1

Reviewed: 04/12/2010

2010-00000219 Page 7 of 34

Avaya BCM Solutions Test Lab

Application Notes

Reserved.

BCM50_BCM450_R5_Configuration_Bell

7 of 34

5.0 Features

5.1 Features Supported

The following list summarizes the base feature set for Bell SIP Trunking that has been verified on the tested equipment.

• Basic Call using G.729 or G.711ulaw

• Calling Party Number Presentation and Restriction

• Calling Name

• Intra- and Inter-site Call Transfer

• Intra- and Inter-site Conference.

• Call Hold and Resume

• Call Forward All, Busy and No Answer

• Fax using G.711 passthru

• TTY using G.711 passthru

• Outbound calls to IP and TDM networks

5.2 Trunk Group Selection for Originating Calls

The charging model for Bell SIP Trunking service is based upon Bell’s legacy PRI trunk model, and allows a trunk subscriber the ability to purchase trunks that provide local presence in one or more given toll rate centre’s. This implies the need for the subscriber to be able to originate outbound calls on the trunk of their choice so as to minimize the toll charges they would incur placing calls into any rate centre that they do not have a local presence (dedicated trunk) for. For instance, an Ottawa-based trunk subscriber can pla ce local calls to Toronto customers if they have purchased a trunk for the 416 rate centre.

The ability to select an outbound trunk on a per-call basis allows a customer with multiple trunks to originate their call from within a rate centre that is local to the called party. This selection is accomplished through one of the following mechanisms (listed in order of precedence):

* Note currently the BCM does not support trunk group selection within the IP trunk interfa ce via the additions of specific SIP headers as described above, so by default the “No Trunk Selected” mechanism is used.

•

TGRP (RFC 3904)

RFC 3904 describes a standardized mechanism for conveying trunk group selection parameters within ‘sip:’ and ‘tel:’ URLs..

Bell Canada SIP Trunking service expects a trunk group selection to be conveyed in the contact header for calls originating on the PBX and destined for the PSTN. The trunk group parameters detailed below are specific to the Bell Canada SIP Trunking service. These parameters are defined during the service setup process.

Example SIP Header:

Reviewed: 04/12/2010

Avaya BCM Solutions Test Lab

Application Notes

BCM50_BCM450_R5_Configuration_Bell

Reserved.

2010-00000219 Page 8 of 34

8 of 34

• OTG

Contact: <sip:6131112222;tgrp=rate_613;trunk- context=sipt.bell.ca@gw1.example.com;user=phone>

The example shows the trunk selection parameters are to be inserted between the user and domain parts of the contact address, and are semicolon-delimited. In this example, trunk group identified by the label ‘rate_613’ and trunk-context ‘sipt.bell.ca’ are used to route this particular outbound call.

Including an OTG parameter in the From:, P-Asserted-Identity:, or Diversion: SIP header fields will indicate to the SIP Trunking service that the customer wishes to use originate a call within the trunk group specified by the ‘otg=’ parameter. The value of this parameter is defined during the service setup process.

Example SIP Headers: From: <sip:6135604063@company.ca;user=phone;otg=rate_613> P-Asserted-Identity: <sip:6135604063@company.ca;otg=rate_613> Diversion: <sip:6135604063@company.ca;user=phone;otg=rate_613> Each of the header parameters above can be used to specify the trunk preference for this call to

the SIP trunking service. In this example the customer wants the call to be placed using the settings for trunk group 613 (including billing and capacity management).

•

No Trunk Selected

If none of the preceding trunk selection mechanisms are used for a given outbound call, the SIP Trunking service will use the calling party’s default trunk for that call. The default trunk is selected using the identity of the call originator, which is typically specified by the contents of the SIP From: header. If the From: header is encrypted or set to ‘anonymous’, then the service will use the contents of the P-Asserted-Identity: header instead.

Reviewed: 04/12/2010

Avaya BCM Solutions Test Lab

Application Notes

BCM50_BCM450_R5_Configuration_Bell

9 of 34

Reserved.

2010-00000219 Page 9 of 34

5.3 Features not supported

• SIP REFER

o The REFER method is not supported under Bell’s SIP Trunking service.

•

T.38 Fax Protocol

o T.38 Fax transmissions are not supported by Bell SIP Trunking service. In-band Fax

transmissions using G.711 transport have been verified in Bell’s SIP Trunking verification tests.

•

Modem transmissions not supported

o Modem connections are not supported over the Bell SIP Trunking at this time; although these

connections may work.

•

Call Connected Network Name Display

o This feature is not supported by the SIP Trunking service. Name and Number display is

presented as provisioned in the SIP Trunking core elements.

Reviewed: 04/12/2010

Avaya BCM Solutions Test Lab

Application Notes

BCM50_BCM450_R5_Configuration_Bell

10 of 34

Reserved.

2010-00000219 Page 10 of 34

6.0 Deployment considerations

• A clear media path from IP sets to the sip trunk interface is required. The IP set determines the available codec used for media exchange.

• Trunk selection for the service is based on the From and PAI headers of the sip message. The headers are configured at a set level. Explicit trunk group selection is not supported on the BCM devices.

• If the call contains both G.711 and G.729 G711 will be used independent of the codec prefe re nce in the SDP to the PSTN.

• Call forwards do not include the original caller display information; instead these calls will appear as if they originated from the set doing the forwarding. When “Forward redirection OLI” is turned off. This feature must be turned on for original call display information to be used.

• Additional licensing maybe required on the BCM to support deployment requirements. To connect the Bell SIP trunks you will need at a minimum the IP Trunk module Auth codes

6.1 Media Codec’s for Bell SIP Trunking

Bell SIP Trunking service provides support for G.711, and G.729 codecs. The G.711 codec is the default for SIP Trunking customers, but they may choose to sign up for SIP Trunking as G.729 subscribers in orde r to take advantage of the bandwidth saving a compressed codec offers them.

The SIP Trunking service infrastructure provides transcoding services to manage and alter the media path for calls where G.729 can’t be supported end-to-end. The transcoder’s intervention allows G.729 customers to view their service as a G.729-only service, and they need not consider the media capabilities of the called party’s device or network, as the transcoder mediates the negotiation if required, and encapsulates any discre pancies between the customer’s codec choice and that of the parties they place calls to, or receive calls from.

NOTE: The only valid ptime value for media codecs on the SIP Trunking service is 20 ms. All supported codecs must abide by this restriction. The ‘ptime is specified in the SDP part of the SIP signaling, which is used to negotiate the media path for each session.

Reviewed: 04/12/2010

Avaya BCM Solutions Test Lab

Application Notes

BCM50_BCM450_R5_Configuration_Bell

11 of 34

Reserved.

2010-00000219 Page 11 of 34

+ 23 hidden pages

Avaya BCM50 Configuration Guide

Table of Contents

1.0 Introduction

1.1 Prerequisites

1.1.1 Required Reading

1.2 Document Change History

2.0 SIP Trunking Service Overview

2.1 What is SIP Trunking?

3.0 Reference Topology

4.0 Tested Equipment

5.0 Features

5.1 Features Supported

5.2 Trunk Group Selection for Originating Calls

TGRP (RFC 3904)

5.3 Features not supported

6.0 Deployment considerations

6.1 Media Codec’s for Bell SIP Trunking