Avaya IP Telephony Configuration Guide

Part No. P0609327 02 March 17, 2004

Business Communications Manager 3.6

IP Telephony Configuration Guide

recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks NA Inc.

Trademarks

NORT EL NETWORKS is a trademark of Nortel Networks. Microsoft, MS, MS-DOS, Windows, and W indows NT are re gistered trademarks of Microsoft Co rporation. Symbol, Spe ctrum24, and NetVision are re gistered trademarks of Sym bol Technologies, Inc. All other trademarks and registered trademarks are the prop erty of their respective owners.

P0609327 02

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Symbols used in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

IP telephones and VoIP trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

IP telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

VoIP trunks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Creating the IP telephony network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Networking with Business Communications Manager . . . . . . . . . . . . . . . . . . . . . . 24

M1-IPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Gatekeepers on the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

IP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Public Switched Telephone Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Key IP telephony concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Jitter Buffer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

QoS routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 2

Prerequisites checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Network diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Network devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Network assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Resource assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Keycodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

System configuration for IP functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Finding the published IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Setting the Global IP (published IP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Determining the published IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Media gateway parameters for IP service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

VoIP trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

IP telephone records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

IP Telephony Configuration Guide

4 Contents

Chapter 3

Installing IP telephones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

IP telephony on the Business Communications Manager . . . . . . . . . . . . . . . . . . . . . . 42

Configuring Nortel Networks i-series telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Configuring DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Checking IP server status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Modifying IP telephone status settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Working with the features list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Resetting the Hot Desking password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Customizing feature labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Download firmware to a Nortel IP telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Deregistering DNs for IP telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Moving IP telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Configuring a new time zone on a remote telephone . . . . . . . . . . . . . . . . . . . . . . . . . 70

Nortel Networks i2050 Software Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Preparing your system for IP telephone registration . . . . . . . . . . . . . . . . . . . . . . . 43

Setting IP terminal general settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Choosing a codec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Choosing a Jitter Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Installing i-series telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Before installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Using a 3-port switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Connecting the i200X telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuring the i20XX telephones to the system . . . . . . . . . . . . . . . . . . . . . . . . . 47

Registering the telephone to the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Configuring telephone settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Troubleshooting IP telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Operation issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Setting up DHCP to work with IP terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

IP telephony DHCP notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Using the Services button to access features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Notes about Hot Desking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Changing features or labels on the memory buttons . . . . . . . . . . . . . . . . . . . . . . 64

Forcing a firmware download to an IP telephone. . . . . . . . . . . . . . . . . . . . . . . . . . 65

Deregistering a telephone using the IP record. . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Deregistering a telephone using a DN registration heading. . . . . . . . . . . . . . . . . . 67

Moving IP telephones and retaining the DN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Moving telephones and changing the DN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Configuring the i2050 Software Phone for the local system . . . . . . . . . . . . . . . . . 71

Chapter 4

Installing NetVision telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

NetVision connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

P0609327 02

Contents 5

Access points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Keycodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Handset and call functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Configuring NetVision records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Gathering system information before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Assigning general settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Monitoring H.323 service status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Assigning H.323 Terminals records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Pre-configuration notes for NetVision handsets . . . . . . . . . . . . . . . . . . . . . . . 78

Adding a NetVision record in the Unified Manager . . . . . . . . . . . . . . . . . . . . . 79

Modifying H.323 terminal records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Updating the H.323 terminals record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Changing a handset Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Changing the DN record of a handset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Deleting a NetVision telephone from the system . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Deregistering a telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Chapter 5

Configuring local VoIP trunks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Pre-installation system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Keycodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Published IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

SIP network data considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

H.323 network applications considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Counting IP trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Determining the IP trunk count. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Configuring media parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Setting up the local gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Modifying local gateway settings for H.323 and SIP trunks . . . . . . . . . . . . . . . . . 92

Notes about NPI-TON aliases for H.323 trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Setting up SIP trunk subdomain names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Viewing SIP summary and status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Incoming calls: Assigning target lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

How to use target lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Configuring target lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Chapter 6

Setting up VoIP trunks for outgoing calls . . . . . . . . . . . . . . . . . . . . . . . . . 101

Setting up remote gateways and end points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Configuring a remote gateway (H.323 trunks) . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Creating a remote gateway record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Configuring remote endpoints (SIP trunks) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Setting up the SIP address book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Outgoing call configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

IP Telephony Configuration Guide

6 Contents

Setting up VoIP trunks for fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Quality of Service Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Managing H.323 and SIP trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Configuring lines and creating line pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Configuring telephones to access the VoIP lines. . . . . . . . . . . . . . . . . . . . . . . . . 109

PSTN call to remote node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Call process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Describing a fallback network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Configuring routes for fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Pre-configuration requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Adding routes for fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Assigning the line pools to routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Adding the destination code for the fallback route . . . . . . . . . . . . . . . . . . . . 116

Configuring the schedules for the destination codes . . . . . . . . . . . . . . . . . . 117

Setting up the VoIP schedule to overflow . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Activating the VoIP schedule for fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Deactivating the VoIP schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

How fallback routing works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Example: A private network configured for fallback . . . . . . . . . . . . . . . . . . . . . . 122

System programming for networking and fallback routes . . . . . . . . . . . . . . . 123

Making calls through a private VoIP network gateway . . . . . . . . . . . . . . . . . 125

Connecting an i200X telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

PSTN fallback metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Resetting the log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Quality of Service Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Updating the QoS monitor data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Viewing QoS monitoring logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Chapter 7

Optional VoIP trunk configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Port settings (firewall) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Using firewalls: adding PortRanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Modifying PortRanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Port settings for legacy networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Using a gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Using Radvision ECS 3.2 GK as the gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Configuring Radvision for Business Communications Manager . . . . . . . . . . . . . 134

Using CSE 1000 as a gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Business Communications Manager requirements . . . . . . . . . . . . . . . . . . . . . . . 136

CSE 1000 configuration, adding an H.323 endpoint . . . . . . . . . . . . . . . . . . . . . . 137

Setting the H.323 Endpoint Dialing Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Committing Gatekeeper Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . 138

Configuring Codec Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

P0609327 02

Contents 7

Setting Codecs on the CSE 1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Gatekeeper call scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Faxing over VoIP lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Operational notes and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

IP trunking interoperability settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Configuring NetMeeting clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Chapter 8

Typical network applications using MCDN . . . . . . . . . . . . . . . . . . . . . . . . 147

Setting up MCDN over VoIP with fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

MCDN functionality on fallback PRI lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Networking multiple Business Communications Managers . . . . . . . . . . . . . . . . . . . . 149

Multi-location chain with call center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Business Communications Manager to remote IP telephones . . . . . . . . . . . . . . . . . 152

Appendix A

Efficient Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Determining the bandwidth requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Determining WAN link resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Link utilization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Network engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Bandwidth requirements on half duplex links . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Bandwidth requirements on full duplex links . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

LAN engineering examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

WAN engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

QoS Monitoring Bandwidth Requirement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Additional feature configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Setting Non-linear processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Determining network loading caused by IP telephony traffic . . . . . . . . . . . . . . . 160

Enough link capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Not enough link capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Other intranet resource considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Implementing the network, LAN engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Further network analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Components of delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Reduce link delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Reducing hop count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Adjust the jitter buffer size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Reduce packet errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Routing issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Post-installation network measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

IP Telephony Configuration Guide

8 Contents

Appendix B

Silence compression. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Silence compression on half-duplex links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Silence compression on full-duplex links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Comfort noise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Appendix C

Network performance utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Appendix D

Interoperability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Speech path setup methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Media path redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Asymmetrical media channel negotiation, Net Meeting . . . . . . . . . . . . . . . . . . . . . . . 178

Setting up Remote Routers for IP Telephony Prioritization . . . . . . . . . . . . . . . . . . . . 179

Using VLAN on the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Symbol NetVision telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Software interoperability compatibility and constraints . . . . . . . . . . . . . . . . . . . . . . . 183

No feedback busy station. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Creating an outbound traffic filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Sample criteria, ranges, and actions for UDP filtering . . . . . . . . . . . . . . . . . . . . . 180

Choosing DHCP for VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Specifying the site-specific options for VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

H.323 trunk compatibility by software version . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

H.323 trunk compatibility issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

SIP trunk interoperability issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

T.38 fax restrictions and requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Appendix E

Quality of Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Setting QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Measuring Intranet QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Measuring end-to-end network delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Measuring end-to-end packet loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Recording routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Adjusting Ping measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Adjustment for processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Late packets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Measurement procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Other measurement considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Decision: does the intranet meet IP telephony QoS needs? . . . . . . . . . . . . . . . . 197

Implementing QoS in IP networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Traffic mix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

P0609327 02

Contents 9

TCP traffic behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Business Communications Manager router QoS support . . . . . . . . . . . . . . . . . . 199

Network Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Network monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Quality of Service parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Fallback to PSTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 11

IP Telephony Configuration Guide

10 Contents

P0609327 02

Figures

Figure 1 Network diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Figure 2 Global IP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Figure 3 Selecting the Published IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Figure 4 System Configuration, Parameters screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Figure 5 Set registration properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Figure 6 IP terminal registration server status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Figure 7 IP Terminal status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Figure 8 IP Terminal status dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Figure 9 IP Telephony Features List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Figure 10 Add/Modify Telephony Features List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Figure 11 IP Terminal Status tab list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Figure 12 Label set defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Figure 13 Deregister DN from Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Figure 14 Deregister DN from Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Figure 15 i2050 Communications server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Figure 16 i2050 Switch type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Figure 17 Defining Codec and Jitter Buffer for all terminals . . . . . . . . . . . . . . . . . . . . . . . . 76

Figure 18 Viewing the Summary tab for H.323 terminals . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Figure 19 H.323 Terminal list dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Figure 20 H.323 Terminal list with terminal information . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Figure 21 Deregister DN from Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Figure 22 IP Trunks Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Figure 23 H.323 Media Parameters dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Figure 24 SIP Media Parameters dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Figure 25 Local gateway IP interface, H.323 Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Figure 26 Local gateway IP interface, SIP trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Figure 27 SIP Dialing Sub-Domain settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Figure 28 SIP Summary dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Figure 29 Internal call from Meridian 1 tandems to remote PSTN line . . . . . . . . . . . . . . 102

Figure 30 Remote gateway dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Figure 31 Add an entry to the SIP address book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Figure 32 Calling into a remote node from a public location . . . . . . . . . . . . . . . . . . . . . . 110

Figure 33 PSTN fallback diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Figure 34 Add route dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Figure 35 Route XXX screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Figure 36 VoIP schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Figure 37 Normal schedule routing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Figure 38 Setting up routes and fallback for call to remote system (CDP dialing code) . . 120

Figure 39 Setting up routes and fallback for remote external call (CDP dialing code) . . . 121

Figure 40 Example PSTN fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

IP Telephony Configuration Guide

Figure 41 Fallback Metrics fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Figure 42 Port ranges dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Figure 43 Port Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Figure 44 Port Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Figure 45 Port ranges dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Figure 46 Business Communications Manager systems with a gatekeeper . . . . . . . . . . 141

Figure 47 IP trunking interoperability fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Figure 48 NetMeeting options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Figure 49 NetMeeting Advanced Calling Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Figure 50 M1 to Business Communications Manager network diagram . . . . . . . . . . . . . 148

Figure 51 Multiple Business Communications Manager systems network diagram . . . . . 149

Figure 52 Routing all public calls through one Business Communications Manager . . . . 150

Figure 53 M1 to Business Communications Manager network diagram . . . . . . . . . . . . . 151

Figure 54 Connecting to IP telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Figure 54 LAN engineering peak transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Figure 55 Peak traffic, WAN link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Figure 56 Calculating network load with IP telephony traffic . . . . . . . . . . . . . . . . . . . . . . 160

Figure 57 Network loading bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Figure 58 One call on a half duplex link without silence compression . . . . . . . . . . . . . . . 168

Figure 59 One call on a half duplex link with silence compression . . . . . . . . . . . . . . . . . 168

Figure 60 Two calls on a half duplex link with silence compression . . . . . . . . . . . . . . . . . 169

Figure 61 One call on a full duplex link without silence compression . . . . . . . . . . . . . . . . 170

Figure 62 One call on a full duplex link with silence compression . . . . . . . . . . . . . . . . . . 171

Figure 63 Two calls on a full duplex link with silence compression . . . . . . . . . . . . . . . . . 172

Figure 64 Relationship between users and services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

P0609327 02

Tables

Table 1 Network diagram prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Table 2 Network device checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Table 3 Network assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Table 4 Resource assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Table 5 Keycodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Table 6 Business Communications Manager system configuration . . . . . . . . . . . . . . . . 34

Table 7 Published IP Address options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Table 8 IP terminals general record fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Table 9 VoIP trunk provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Table 10 IP telephone provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Table 11 IP terminals general record fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Table 12 IP telephone server configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Table 13 IP telephony display messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Table 14 IP telephone troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Table 15 IP terminal Summary fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Table 16 IP Terminal Status fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Table 17 Relabelling examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Table 18 H.323 Terminal list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Table 19 H.323 terminals Summary fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Table 20 H.323 Terminal list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Table 21 Media parameters record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Table 22 Media parameters record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Table 23 Local Gateway IP interface fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Table 24 Route and Dialing Plan configurations for NPI-TON . . . . . . . . . . . . . . . . . . . . . 96

Table 25 Remote gateway record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Table 26 Adding SIP Address Book records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Table 27 Fallback configuration for to create fallback between two systems . . . . . . . . . 123

Table 28 QoS status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Table 29 Media parameters record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Table 30 Media parameters record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Table 31 Radvision Calls screen required settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Table 32 Radvision Advanced screen required settings . . . . . . . . . . . . . . . . . . . . . . . . . 134

Table 33 Radvision Predefined Endpoints Properties settings . . . . . . . . . . . . . . . . . . . . 135

Table 34 CSE 1000 H.323 endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Table 35 CSE 1000 H.323 dialing plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Table 36 CSE1000 codec compatibility with endpoints . . . . . . . . . . . . . . . . . . . . . . . . . 139

Table 37 CSE 1000 codec configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Table 38 IP trunking interoperability fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Table 38 VoIP Transmission Characteristics for unidirectional continuous media stream 154

Table 39 Bandwidth Requirements per Gateway port for half-duplex links . . . . . . . . . . . 155

IP Telephony Configuration Guide

Table 40 Bandwidth Requirements per Gateway port for Full-duplex links . . . . . . . . . . . 156

Table 41 Link capacity example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Table 42 Business Communications Manager 3.6 IP Interoperability Summary . . . . . . 175

Table 43 Engineering specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Table 44 Supported voice payload sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Table 45 Name comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Table 46 Supported voice payload sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Table 47 Software interoperability restrictions and limitations for IP trunking . . . . . . . . . 184

Table 48 Software network communications application compatibility . . . . . . . . . . . . . . 188

Table 49 T.38 restrictions and requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Table 50 Quality of voice service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Table 51 Site pairs and routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Table 52 Computed load of voice traffic per link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Table 53 Delay and error statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Table 54 Expected QoS level per site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

P0609327 02

Preface

This guide describes IP Telephony functionality for the Business Communications Manager system that is running BCM 3.6 software. This in formation includes c onfiguration instructions for Nortel IP telephones (i-se ries 200X), the i2050 Software Phone, the Symbol NetVision and NetVision data telephone s (H. 323-protocol devices) , and VoIP trunks (H.323 and SIP), as well as some general information about IP networking data controls and IP private telephony networking.

Before you begi n

This guide is intended for installers and managers of a Business Communications Manager system. Prior knowledge of IP networks is required.

Before using this guide, the Business Communications Manager system must be config ured an d tested for basic connectivity and basic telephony operations.

This guide ass umes:

• You have planned the telephony and data requirements for your Business Communications Manager system.

• Operators have a working knowledge of the Windows operating system and of graphical user interfaces.

• Operators who manage the data portion of the system are familiar with network management and applications.

• The Business Communications Manager hardware is installed and initialized, and the hardware is working. Externa l lines and internal telephones and tele phony equipment are connected to the appropri at e media bay modules on the Business Communications Manager.

• Keycodes for the required number of VoIP trunks, IP telephones have been installed.

• If you are using VoIP trunks, the keycode for MCDN has been installed.

• Configuration of lines is complete.

Refer to Chapter 2, “Prerequisites checklist,” on page 35 for more information.

Symbols used in this guide

This guide uses these symbols to draw your attention to important information:

Caution: Caution Symbol Alerts you to conditions where you can damage the equipm ent.

Danger: Electrical Shock Hazar d Symbol Alerts you to conditions where you can get an elect rical shock.

IP Telephony Configuration Guide

16 Preface

Warning: W arning Symbol

Alerts you to conditions where you can cause the syste m to fail or work improperly.

Note: Note/Tip symbol Alerts you to important info rmation.

Tip: Note/Tip s ymbol Alerts you to additional information that can help you perform a task.

Security N o te: This symbol indicates a point of system security where a default shoul d be changed, or where the administrator needs to make a decision about the level of

security required for the system.

Text conventions

This guide uses these following text conventions:

angle brackets (< >) Represent the text you enter base d on the description inside the

brackets. Do not type the brackets when entering the command. Example: If the command syntax is

ping <ip_address>, you enter: ping 192.32.10.12

bold Courier text

Represent command names, options and text tha t you need to enter. Example: Use the

dinfo command.

Example: Enter show ip {alerts|routes}.

italic text Represents terms, book titles and variables in command syntax

descriptions. If a variable is two or more words, the words are connected by an underscore.

Example : The co mm an d synt ax

show at <valid_route>, valid_route

is one variable and you substitute one value for it.

bold t ext Represents fields names , fi el d entries, and screen names in the Unified

Manager application.

plain Courier text

Represents command syntax and syste m output, such as prompts and system messages.

Example:

Set Trap Monitor Filters

P0609327 02

Acronyms

This guide uses the following acronyms:

API Application Progra mming Interface ATM Asynchronous T ransfer Mode BCM Business Communications Manager CIR C ommitted Information Rate DID Direct Inward Dialing DOD Direct Outward Dialing DIBTS Digital In-Band Trunk Signaling DSB DIBTS Signaling Buffer DSL Digital Subscriber Line DSP Digital Signal Process or FEPS Functional Endpoint Proxy Server FoIP Fax over IP

Preface 17

FUMP Functional Messaging Protocol ICMP Internet Contro l Message Protocol IEEE802 ESS Institute of Electr ical and Electronics Enginee rs, Inc., standard 802

Electronic Switc hing System Identification code IP Internet protoc ol IPT Internet Protocol for Telephony (for Meridian) (supported by BCM

version 3.5 and newer software) ISP Internet Ser vice Provider ITG I nterne t Tele phony Gatewa y (for Meridia n) ( supported by B CM versio n

3.0.1 and earlier sof tware, providing th e systems do not share a networ k

with a BCM version 3.5 or newer software) ITU International Telecommunication Union IXC IntereXchange Carrier IP Internet Protocol ISDN Integrated Services Digital Network Kb kilobit KB kilo Byte LAN Local Area Network LATA Local Access and Transport Area LEC Local Exchange Car rier Mb Mega bit

IP Telephony Configuration Guide

18 Preface

MB Mega Byte MOS Mean Opinion Score NAT Networ k Address Transla tion NVPA NetVision Phone Administra tor PCM Pulse Code Modulation PING Packet InterNet Groper PiPP Power inline patch panel PPP Point-to-Point Protoc ol PRI Primary Rate Interface PSTN Public Switched Telephone Network QoS Quality of Service RAS Registratio n, Admi ssions and Status RTP Real-time Transfer Protocol SIP Session Initiation Protocol SNMP Simple Network Management Protocol TCP Transmi ssion Control Protocol UDP User Datagram Protocol or Universal Dialing Plan UTPS UNISTIM Terminal Proxy Server VoIP Voice over Internet Protocol VAD Voice Activity Detect ion VLAN Virtual LAN WAN Wide Area Network

Related publications

Documents referenced in the IP Telephony Configuration Guide, include:

• Installation and Mainte nance Guide

• Software Keycode Instal lation Guide

• Programming Operations Guide

• Telephony Feature Handbook

• i200X and i2050 Software Phone user cards

P0609327 02

How to ge t h e lp

If you do not see an appropriate number in this list, go to www.Nortelnetworks.com/support.

USA and Canada

Authorized Distributors - ITAS Technical Support

Telephone: 1-800-4NORTEL (1-800-466-7835) If you already have a PIN Code, you can enter Express Routing Code (ERC) 196#. If you do not yet have a PIN Code, or for general questions and fir st line support, you can enter ERC 338#.

Website: http://www.nortelnetworks.com/support

Presales Support (CSAN)

Telephone: 1-800-4NORTEL (1-800-466-7835) Use Express Routing Code (ERC) 1063#

EMEA (Europe, Middle East, Africa)

Technical Support - CTAS

Preface 19

Telephone:

*European Freephone 00800 800 89009

European A lter n ative / United Kingdom +44 (0)870-907-9009 Africa +27-11-808-4000 Israel 800-945-9779

*Not e: Calls are not free from all countries in Europe , Middl e East or Africa

Fax: 44-191-555-7980 email: emeahelp@nortelnetworks.com

CALA (Caribbean & Latin America)

Technical Support - CTAS

Telephone: 1-954-858-7777 email: csrmgmt@nortelnetworks.com

APAC (Asia Pacific)

Technical Support - CTAS

Telephone: +61-2-870-8800 Fax: +61 388664644 email: asia_support@nortelnetworks.com

In-country toll free numbers

Australia 1800NORTEL (1800-66 7-835) China 010-6510-7770

IP Telephony Configuration Guide

20 Preface

India 011-5154-2210 Indonesia 0018-036-1004 Japan 0120-332-533 Malaysia 1800-805-380 New Zealand 0800-449-716 Philippines 1800-1611- 0063 Singapore 800-616-2004 South Korea 0079-8611-2001 Taiwan 0800-810-500 Thailand 001-800-611 -3007 Service Business Centre & Pre-Sales Help Desk +61-2-8870-5511

P0609327 02

Chapter 1 Introduction

IP telephony provides t he flexibil ity, af fordabil ity, a nd expanda bil ity of the I nterne t to the world of voice communications.

This section includes an overview of the components that make up the Business Communications Manager version 3.6 IP telephony and Voice over IP (VoIP) features:

• “IP telephones and VoIP trunks” on page 22

• “Creating the IP telephony network” on page 23

• “Key IP telephony concepts” on page 27

Business Communications Manag er with voice over IP (VoIP) provides several critical advantages:

• Cost Savings. IP networks can be significantly less expensive to operate and maintai n than

traditional net works. The simplified network infr astructure of an Internet Telepho ny solution cuts costs by connecting IP tel ephones over your LAN and eliminates the need for dual cabling. Internet Telephony can also eliminate toll charge s on site -to-site calls by using your existing WAN. By using the extra bandwidth on your WAN for IP Telephony, you le verage the untapped capabili ties of your data infrastructur e to maximiz e the return on your current network investment.

• Cost flexibility: The three models of IP telephones offer three levels of functionality, that allow you to choose an IP telephone that fits your budget and/or your service requirem ents.

• Portability and flexibil ity. Employees can be more productive because they are no longer confined by geographic loc ation. IP telephones work anywhere on the network, even over a remote connection. With Nortel Networks wireless e-mobilit y solutions, your phone, laptop, or scanner can work anywhere on the network where a an 802.11b acc ess point is installed. Network deployments and reconf igurations are simplified, and service can be extended to remote sites and home office s ove r cost-effective IP links. As well, IP telephone functiona lity can be transferred betwe en IP tele phones using the Hot desking feature. All your telephone features and setup can trave l with you between offices.

• Simplici ty a nd co n sis ten cy . A common approach to service deployment allows further cost-savings from the use of common management tools, resource directories, flow-through provisioning, and a consistent approach to network security. As well, customers can centrally manage a host of multimedia services and business-building applications via a Web-based browser. The ability to network existing PBXs using IP can bring new benefits to your business. For example, the ability to consolidate voice mail onto a single system, or to fewer systems, makes it easier for voice mail users to network.

• Compatibility. Internet telephony is supported over a wide variety of transport technologies. A user can gain access to just about any business system through an analog line, Digital Subscriber Line (DSL), a LAN, fr ame relay, async hronous tr ansfe r mode, SONET, or wirele ss connection.

IP Telephony Configuration Guide

22 Chapter 1 Introduction

• Scalability. A future-proof, flexible, and safe solution, combined with high reliability, allows your company to focus on customer needs, not network pr oblems. Nortel Networks interne t telephony solutions offer hybrid environments that leverage existing investments in Meridian and Norstar systems.

• Increas ed cu s tom er s ati sf acti on. Breakthrough e-business applications help deliver the top-flight custom er service that leads to success. By providing your customers with rapid access to sales and support personnel via telephone, the Web, and e-mail, your business can provide better cust omer service than ever before.

IP telephones and VoIP trunks

This section describes two similar applications for IP telephony on the Business Communications Manager system: IP telephone s and VoIP trunks. These applications can be used separate ly or together as a network voice/data solution.

Refer to the information under the following headings:

• IP telephones

• VoIP trunks

IP telephones

IP telephones offer the functionality of regular telephones, but do not require a hardwire connection to the Business Communications Manager. Instead, they must be plugg ed into an IP network which is connected to the LAN or WAN card on the Business Communications Manager.

Calls made from IP telephones through the Business Communications Manager can pass over VoIP trunks or across Public Switched Telephone Network (PSTN) lines.

Nortel Networks provides two types of IP telephones. The IP telephones are wired to the IP network using Ethernet, in the case of the i-series 200X IP telephones, or are acce ssed through your desktop or laptop computer , as in the case of the Nort el Networks i2050 Software Phone.

Emobility voice c an be provided using Symbol connect through an access point wir ed to an IP network configured on the LAN. NetVision telephones use an extended version of the H.323 protocol to connect to the system.

Note: For this release, NetVision telephones are not able to use SIP trunks.

VoIP trunks

VoIP trunks allow voice signals to travel across IP networks. A gateway within the Business Communications Manager converts the voice signal into IP packets, which are then tr ansmitted through the IP network to a gateway on the remote syste m. The devic e at the other end reassembles the pa ckets into a voice signa l. Both H. 323 and SIP trunk s support pr ivate ne tworking

P0609327 02

between Business Communications Managers. H.323 trunks can support connections to a number of different types of equipm ent, including the Meridian 1 (running IPT), Success ion 1000/M, DMS100 switches, and SL100 switch es, and tru nk applic ations such a s NetMeeti ng. SIP trunks do not currently support the MCDN network protocol or interconnection with a Meridia n system.

Creating the IP telephony network

This section explains the components of the Business Co mmunications Manager system and the devices it interope rates to create a network.

The information under the head ings in this section describe the vari ous compone nts of the system:

• “Networking with Business Communications Manager” on page 24

• “M1-IPT” on page 25

• “Telephones” on page 25

• “Gatekeepers on the network” on page 25

• “IP network” on page 26

• “Public Switched Telephone Networ k” on page 27

Chapter 1 Introduction 23

The following figure shows components of a Business Communications Manager network configuration.

In this example, two Business Communications Manager systems are connected both through a PSTN connection and through a WAN connection. The WAN connection uses VoIP trunks. If the PSTN connections use dedicate d ISDN lines, the two systems have backup private networks to each other. Both Business Communications Manager systems use VoIP trunks through a common WAN to conn ect to the M eri d ian (M1 -IP T ) syst em .

IP Telephony Configuration Guide

24 Chapter 1 Introduction

Inspect FORWARD Callers

MXP

Figure 1 Network diagram

Router

Access Point

Business Communications Manager A

LAN A

PSTN

SND

FCTMENU

END

NAMERCL

ABC3DEF

1 2

JKL4GHI6MNO

TUV7PQRS9WXYZ

OPR

<#>

(H 323 device A)

STOCLR

HOLD

NetVision

Gatekeeper

IP telephone A

WAN

M1+IPT

Digital telephone A

Router

Business Communications

Manager B

I n s

p e

c t

F O R

A R

D C

a ll

e r s

M X

H 323 Device B

I2050 telephone A

LAN B

IP telephone B

Meridian set A

Networking with Business Communications Manager

The Business Communications Manager is a key building block in creating your communications network. It interoperates with many devices, including the Meridian 1 system and H.323 devices. The Business Communications Manager system can be connected to devices through multiple IP networks, as well a s throug h the PSTN. Multiple Busine ss Communicat ions Manage r syst ems also can be linked together on a network of VoIP trunks and/o r dedicated physical lines. Refer to

Chapter 8, “Typical network applications using MCDN,” on page 147.

The Business Communications Manager can be connected to a LAN through a LAN card, to a WAN through a WAN card, and to a PSTN through trunk media bay modules, as shown for Business Communications Manag er A in the above diagram. Through these networks, the syste m accesses other syste ms and network eq uipment connected to the network.

P0609327 02

Chapter 1 Introduction 25

M1-IPT

The Meridian 1 Internet Telephony Path (M1-IPT) allows Meridian 1 systems to communicate with the Business Communications Manager via H.323 trunks. Telephones on the M1, such as Meridian telephone A, can init iate and recei ve calls with the other telephon es on the system across IP networks.

To provide fallbac k at times when IP traffic cannot pass, you can also connect the Meridi an to the Business Communications Manag ers through ISDN PRI SL-1 lines, which provide the same MCDN capability that you can achieve through the H.323 VoIP trunks with MCDN active.

Refer to the Programming Operations Guide for a description of MCDN features and networking with PRI SL-1 lines. “Typical network applications using MCDN” on page 147 describes how to provide the same network over VoIP lines.

A Business Communications Manager connected to an M1-IPT using the MCDN protocol can provide access to a central voice mail and call attendant systems, which can streamline multi-office telephony administration.

Telephones

The Business Communications Manager can communic ate using digital telephones (Model 7000, 7100, 7208, T7316, T7316E/T73 16E+KIMs, M7310(N) , M7324(N)), T7406 (cordle ss tele phone), wireless telephone s (Companion, DECT), IP telephones and appli cations (i-series 200X and the Nortel Networks i2050 Softwar e Phone), and IP wireless telephones (NetVision and NetVision Data telephones). With this much flexibility, the Business Communications Manager can provide the type of service you require to be most prod uct ive in your business.

While analog and digital tel ephones cannot be connected to the Business Communica tions Manager system with an IP conne ction, they can make and receive calls to a nd from other systems through VoIP trunks. Calls received through the VoIP trunks to system telephone s are received through the LAN or WAN card and are translated within the Business Communications Manager to voice channels.

The IP telephones connect to the Business Communications Manager across an IP network through either a LAN or a WAN. From the Business Communications Manager connection, they can then use standard lines or VoIP trunks to communicate to other telephones on other public or private networks. The Business Communications Manager also supports H.323 (version 4) and H.323 third-party devices through this type of connection.

Gatekeepers on the network

A gatekeeper tracks IP addresses of specified devices, and provides routing and (optionally) authorizatio n for making and acce pting calls f or thes e devices. A gate keeper is not required a s part of the network to which your Business Communications Manager system is attached, but Gatekeepers can be useful on networks with a large number of devices. Referring to Figure 1 on

page 24, for example: Digital tele phone A wants to call IP telephone B, which is attached to

Business Communications Manag er B, over a network that is under the control of a gatekeeper.

IP Telephony Configuration Guide

26 Chapter 1 Introduction

Digital telephone A sends a request to the gatekeeper. The gatekeeper, depending on how it is programmed, provides Digital telephone A with the information it need s to contac t BC M B over the network. Business Communications Manager B then passes the call to IP telephone B. SIP trunks do not use gatekeepers.

The Business Communicati ons Manager does not contain a gatekeeper application. If you want to put a gatekeeper on your network, it must be put on a separate gatekeeper server. The Business Communications Manager is compatible with RadV ision, CSE 1000 (CSE1K), and NetCentrex gatekeepers. Refer to “Using a gatekeeper” on page 133 and Appendix D, “Interoperability,” on

page 175.

Warning: Meridian 1 IP T does not support the RadVision gatekeeper.

IP network

In the network shown in Figure 1 on page 24, several LANs and a WAN are shown. When planning your network, be sure to consider all requirements for a data network. Your network administrator should be able to advise you about the network setup and how the Business Communications Manager fits into the network.

WAN

A Wide Area Network (WAN) is a communications network that covers a wide geographic area, such as state or country. For Business Communications Manager, a WAN is any IP network connected to a WAN card on the Business Communications Manager system. This may also be a direct connection to another Business Communications Manager system.

If you want to deploy IP telephones or NetVision te lephones that will be connected to a LAN outside of the LAN that the Business Communica tions Mana ger is installed on, you must ensure the Business Communication s Manager has a WAN connection. This includes ensuring that you obtain IP ad dresses and routin g information that allows the remote telephones to find the Busi ness Communications Manager, and vice versa.

The Programming Operations Guide has a data section that describes the internet protocols and data settings that the Business Communications Manager requires or is compatible with. Ensure that this connectio n is correctly set up and working before you attempt to deploy any remote IP devices.

LAN

A Local Area Network (LAN) is a communications network that serves users within a confined geographical are a. For Business Communi cati ons Manager, a LAN is any I P network conne cte d to a LAN card on the Business Communications Manager system. Often, the LAN can include a router that forms a connection to the Internet. A Business Communications Manager can have up to two LAN connections.

P0609327 02

Public Switched Telephone Network

The Public Switched Telephone Network (PSTN) can play an important role in IP telephony communications. In many installations, the PSTN forms a fallback route. If a call across a VoIP trunk does not have adequate voic e qualit y, th e call c an be rout ed across PSTN li nes instead, eit her on public lines or on a dedicated ISDN connection between the two systems (private network). The Business Communicat ions Manager also serves as a gate way to the PSTN for all voice tra ffic on the system.

Key IP telephony c onc e pts

In traditional tele phony, the voice path between two telephones is cir cuit switched. This means that the analog or digital connection betwe en the two telephones is dedic ated to the call. The voice quality is usually excellent, since there is no other signal to inte rfere.

In IP telephony, each IP telephone encodes the speech at the handset microphone into small data packets called frames. The system sends the frames across the IP network to the other tele phone , where the frames are decoded and played at the handset receiver. If some of the frames get lost while in transit, or are delayed too long, the receiving telephone experiences poor voice quality. On a properly-configured network, voice quality should be consistent for all IP calls.

Chapter 1 Introduction 27

The information under the following headings describe some of the components that determine voice quality for IP telephone s an d trunks:

• “Codecs” on page 27

• “Jitter Buffer” on page 28

• “QoS routing” on page 29

Codecs

The algorithm used to compress and decompr ess voice is embedded in a software entity called a codec (COde-DECode).

Two popular Codecs are G.711 and G.729. The G.711 Codec samples voice at 64 kilobits per second (kbps) while G.729 samples at a far lower rate of 8 kbps. For actual bandwidth requiremen ts , refe r to “Determining the bandwidth requirements” on page 153, where you will note that the actual kbps requi rements are slightly higher than lab el sugg ests.

Voice quality is better when using a G.711 CODEC, but more network bandwidth is used to exchange the voice frames between the telephones.

If you experience poor voice quality, and suspect it is due to heavy network traffic, you can get better voice qualit y by configuring the IP telephone to use a G.729 CODEC.

Note: You can only change the codec on a configured IP telephone if it is online to the Business Communications Manager, or if Keep DN Alive is enabled for an offline telephone.

IP Telephony Configuration Guide

28 Chapter 1 Introduction

The Business Communications Manager supports these codecs:

• G.729

• G.723

• G.729 with VAD (Voice Activity Detection)

• G.723 with VAD

• G.711-uLaw

• G.711-aLaw

Jitter Buffer

Voice frames are transmitted at a fixed rate, because the time interval between frames is constant. If the frames arrive at the other end at the same rate , voic e quality is perceived as good. In many cases, however, some frame s can arrive slightl y faster or slower than the o the r fram es . Th is is called jitte r, and degrades the perceive d voice quality. To minimize this problem, config ure the IP telephone with a jitter buffer for arriving frames.

Note: You can only change the jitter buffer on a configured IP tel ephone if it is online to the Business Communications Manag er, or if Keep DN Alive is enabled for an offline telephone.

This is how the jitter buffer works: Assume a jitter buffer sett ing of five frames.

• The IP telephone firmware places the first five arriving frames in the jitter buffer.

• When frame six arrives, the IP telephone firmware places it in the buffer, and sends frame one to the handset speaker.

• When frame seven arrives, the IP tele phone buffers it, and sends frame two to the handset speaker.

The net effect of using a jitter buf fer is that the arriving packets are delayed slightly in order to ensure a constant rate of arriving frames at the handset speaker.

This delaying of packets can provide somewhat of a communications challenge, as speech is delayed by the number of frames in the buffer. For one -sided conversations, there are no issues. However, for two-sided conversations, where one party tries to interrupt the other speaking party, it can be annoying. In this second situation, by the time the voice of the interrupter reaches the interruptee, the inte rrupte e has spoke n (2*jitt er si ze) frames pa st t he intende d poin t of inter ruption . In cases where very large jitter sizes are used, some users revert to saying OVER when they wish the other party to speak.

Possible jitter buffer settings, and corresponding voice packet latency (delay) for the Business Communications Manager syst em IP telephones are:

• None

• Small (G.723: .06 seconds; G.711/G.729: .05 seconds)

• Medium (G.723: .12 seconds; G711/G.729: .09 seconds)

P0609327 02

Chapter 1 Introduction 29

• Large (G.723: .18 seconds; G711/G.729: .15 seconds)

QoS routing

To minimize voice jitt er over low bandwi dth connecti ons, the Business Communic ations Mana ger programming assigns spec ific DiffServ Marking in the IPv4 header of the data packets sent from IP telephones.

Warning: BCM version 3.5 and newer software only supports H.323 ve rs ion 4. To support this, all Business Communications Managers running BCM version 3.0. 1 or earlier software, which are on a network with a Business Communications Manager running BCM version 3.5 or newer software, must either be upgra ded to BCM version 3.5 or newer software or apply a QoS patch (3.0.0.25 or late r) to support thi s versio n of H.323.

The DiffServ Code point (DSCP) is c ontained in th e sec ond byte of the IPv 4 header. DSCP is used by the router to determine how the packets will be separated for Per Hop Behavior (PHB). The DSCP is contained within the Dif fServ field, which was known as the ToS field in older versions. The Business Communicati ons Manager assig ns Expe dited Forwar ding (EF) PHB for voice medi a packets and the Class Selector 5 (CS5) PHB for voice signal ing (control ) packets. On the Business Communications Manager, these assignments cannot be adjusted.

The Business Communi cations Manager system performs QOS routing, but if one or more routers along the network route do not support QOS routing, this can impact voice quality. Business Communications Manager system QoS can also be configured so that the system reverts to a circuit-swit ched line if a suitable QoS cannot be guaranteed.

IP Telephony Configuration Guide

30 Chapter 1 Introduction

P0609327 02

+ 192 hidden pages