Avaya BCM 2.5 IP Telephony Configuration Guide

Return to Menu

Part No. P0937663 02

Business Communications Manager 2.5

IP Telephony Configuration Guide

The information in this document is subject to change without notice. The statements, configurations, technical data, and 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

NORTEL NETWORKS is a trademark of Nortel Networks.

Microsoft, MS, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation.

All other trademarks and registered trademarks are the property of their respective owners.

P0937663 02.0

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Symbols used in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

IP telephones and VoIP trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

IP telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

VoIP trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

The IP telephony network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Business Communications Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

M1-ITG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Public Switched Telephone Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Key IP Telephony Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Jitter Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

QoS routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Traditional telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

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

H.323 terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 2

Prerequisites checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Network diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Network devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Network assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Resource Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Keycodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Business Communications Manager System Configuration . . . . . . . . . . . . . . . . . . . . 29

IP Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

IP Telephony Configuration Guide

Chapter 3

Installing IP Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Preparing your Business Communications Manager for IP telephone registration . . . 31

Choosing a codec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Choosing a Jitter Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Installing and Configuring i2004 Internet Telephones . . . . . . . . . . . . . . . . . . . . . . . . . 34

Before Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Using a 3-port switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Connecting the i2004 Internet telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Configuring the i2004 telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Troubleshooting an IP telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Configuring DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Modifying settings for Nortel IP telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Download Firmware to an i200X telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Deregistering DNs for online IP telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Deregistering offline DNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Moving IP telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Configuring the i2050 Software Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

H.323 devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Adding H.323 devices to the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 4

VoIP Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Installing keycodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Setting the Published IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Determining the published IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Configuring media parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Setting Silence Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Setting Jitter Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Outgoing call configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Putting VoIP lines into a line pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Configuring the Access code for the Line Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Configuring DNs to access the VoIP line pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Configuring a remote gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Configuring PSTN fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Setting up a VoIP schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Configuring routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Creating a destination code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Configuring digits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Activating the VoIP schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

P0937663 02.0

Turning on QoS monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Enabling PSTN fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Incoming call configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Assign a target line to the DN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Example configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

On Business Communications Manager Ottawa . . . . . . . . . . . . . . . . . . . . . . . . . 72

On Business Communications Manager Santa Clara . . . . . . . . . . . . . . . . . . . . . . 73

Making calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Connecting an i200X telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Connecting an i200X telephone on the LAN . . . . . . . . . . . . . . . . . . . . . . . . . 75

Configuring NetMeeting clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Quality of Service Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Quality of Service Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Updating the QoS Monitor data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Port settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Using firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Port settings for legacy networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Using a gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

The call signalling method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Alias names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Modifying the call signalling method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Gatekeeper call scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 5

Typical applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

M1 to Business Communications Manager over IP trunks . . . . . . . . . . . . . . . . . . 85

MCDN functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Multiple Business Communications Manager systems

across VoIP trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

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

Business Communications Manager to IP Telephones . . . . . . . . . . . . . . . . . . . . . 89

Appendix A

Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Determining the bandwidth requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Determining WAN link resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Link utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Network Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Bandwidth Requirements on Half Duplex Links . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Bandwidth Requirements on Full Duplex Links . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

LAN Engineering Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

WAN engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

IP Telephony Configuration Guide

Additional feature configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Setting Non-linear processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

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

Other intranet resource considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Implementing the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

LAN engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Getting the best results from your system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Further network analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Components of delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Reduce link delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Reducing hop count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Routing issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Post-installation network measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Appendix B

Silence compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Silence compression on Half Duplex Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Silence compression on Full Duplex Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Comfort Noise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Appendix C

Network Performance Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Sniffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Appendix D

Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Speech Path Setup Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Media Path Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Asymmetrical Media Channel Negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

No feedback busy station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Symbol Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Appendix E

Quality of Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Setting QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Measuring Intranet QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

P0937663 02.0

Measuring end-to-end network delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Measuring end-to-end packet loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Recording routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Adjusting ping measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Measurement procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Other measurement considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Implementing QoS in IP networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Traffic mix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

TCP traffic behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Business Communications Manager Router QoS Support . . . . . . . . . . . . . . 121

Network Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Network Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Quality of Service parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Fallback to PSTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

IP Telephony Configuration Guide

P0937663 02.0

Figures

Figure 1 Network diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 2 Set registration properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Figure 3 Global options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Figure 4 DHCP summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Figure 5 DHCP range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Figure 6 IP Terminal status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Figure 7 Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Figure 8 Terminal status dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Figure 9 IP Terminal Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Figure 10 IP Terminal Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Figure 11 Deregister Offline DN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Figure 12 i2050 Communications server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Figure 13 i2050 Switch type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Figure 14 H.323 Terminal list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Figure 15 H.323 Terminal list dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Figure 16 Global IP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Figure 17 Setting the Published IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Figure 18 Media parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Figure 19 Media Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Figure 20 Media parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Figure 21 Trunk/Line data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Figure 22 Line pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Figure 23 Remote gateway list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Figure 24 Remote gateway dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Figure 25 PSTN fallback diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Figure 26 VoIP schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Figure 27 VoIP Routing Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Figure 28 Route list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Figure 29 Add route dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Figure 30 Add route dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Figure 31 Add destination code dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Figure 32 Normal schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Figure 33 VoIP schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Figure 34 Remote Gateway list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Figure 35 Remote Gateway dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Figure 36 Example PSTN fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Figure 37 NetMeeting options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Figure 38 NetMeeting advanced options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Figure 39 Port Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Figure 40 Port ranges dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

IP Telephony Configuration Guide

Figure 41 Local gateway IP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Figure 42 Business Communications Manager systems with a gatekeeper . . . . . . 82

Figure 43 M1 to Business Communications Manager network diagram . . . . . . . . . 85

Figure 44 Multiple Business Communications Manager systems network diagram 87

Figure 45 M1 to Business Communications Manager network diagram . . . . . . . . . 88

Figure 46 M1 to Business Communications Manager network diagram . . . . . . . . . 89

Figure 47 Calculating network load with IP telephony traffic . . . . . . . . . . . . . . . . . . 97

Figure 48 One Call on a Half Duplex Link Without Silence compression . . . . . . . . 104

Figure 49 One Call on a Half Duplex Link With Silence compression . . . . . . . . . . 104

Figure 50 Two Calls on a Half Duplex Link With Silence compression . . . . . . . . . 105

Figure 51 One Call on a Full Duplex Link Without Silence compression . . . . . . . . 106

Figure 52 One Call on a Full Duplex Link With Silence compression . . . . . . . . . . 107

Figure 53 Two Calls on a Full Duplex Link With Silence compression . . . . . . . . . . 108

Figure 54 Relationship between users and services . . . . . . . . . . . . . . . . . . . . . . . 115

P0937663 02.0

Tables

Table 1 Network diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Table 2 Network device checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Table 3 Network assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Table 4 Resource Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Table 5 Keycodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

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

Table 7 IP telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Table 8 Settings for IP telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Table 9 QoS status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Table 10 Voice over IP Transmission Characteristics for

Table 11 Bandwidth Requirements per BCM Gateway port for half-duplex links. . 94

Table 12 Bandwidth Requirements per BCM Gateway port for Full-duplex links. . 95

Table 13 Link capacity example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Table 14 Business Communications Manager 2.5 Product

Table 15 Engineering specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Table 16 Supported voice payload sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Table 17 Name comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Table 18 Quality of voice service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Table 19 Site pairs and routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Table 20 Computed load of voice traffic per link . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Table 21 Delay and error statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

unidirectional continuous media stream . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Interoperability Summary 111

IP Telephony Configuration Guide

P0937663 02.0

Preface

This guide describes IP Telephony functionality for the Business Communications Manager 2.5 system. This includes information on Nortel IP terminals such as the i2004 phone and the i2050 software phone, H.323 terminals and H.323 trunks.

Before you begin

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

Before using this guide, you must install and configure a Business Communications Manager 2.5 system.

This guide assumes:

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

• The Business Communications Manager 2.5 is installed and initialized and the hardware is working. External lines and terminals and sets are connected to the appropriate media bay modules on the Business Communications Manager 2.5.

• Configuration of lines is complete.

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

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

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

IP Telephony Configuration Guide

14 Preface

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 equipment.

Danger: Electrical Shock Hazard Symbol Alerts you to conditions where you can get an electrical shock.

Warning: Warning Symbol Alerts you to conditions where you can cause the system to fail or work improperly.

Note:

Alerts you to important information.

Tip: Tip Symbol Alerts you to additional information that can help you perform a task.

Text conventions

This guide uses these following text conventions:

angle brackets (< >) Represent the text you enter based on the description

bold Courier text

inside the brackets. Do not type the brackets when entering the command.

Example: If the command syntax is

ping <ip_address> ping 192.32.10.12

Represent command names, options and text that you need to enter.

Example: Use the dinfo Example: Enter

, you enter

command.

show ip {alerts|routes}

P0937663 02.0

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 command syntax

show at <valid_route>, valid_route

is one variable and you substitute one

value for it.

Preface 15

plain Courier text

Acronyms

This guide uses the following acronyms:

ATM Asynchronous Transfer Mode

BCM Business Communications Manager

CIR Committed Information Rate

DID Direct Inward Dialing

DOD Direct Outward Dialing

DIBTS Digital In-Band Trunk Signalling

DSB DIBTS Signalling Buffer

ITU International Telecommunication Union

IXC IntereXchange Carrier

IP Internet Protocol

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

Example: Set Trap Monitor Filters

ISDN Integrated Services Digital Network

LAN Local Area Network

LATA Local Access and Transport Area

LEC Local Exchange Carrier

MOS Mean Opinion Score

PCM Pulse Code Modulation

PPP Point-to-Point Protocol

PRI Primary Rate Interface

PSTN Public Switched Telephone Network

QoS Quality of Service

RTP Real-time Transfer Protocol

SNMP Simple Network Management Protocol

TCP Transmission Control Protocol

IP Telephony Configuration Guide

16 Preface

UDP User Datagram Protocol

UTPS UNISTEM Terminal Proxy Server

VoIP Voice over Internet Protocol

WAN Wide Area Network

P0937663 02.0

Related publications

Documents referenced in the Business Communications Manager 2.5 IP Telephony Configuration Guide, include:

• Business Communications Manager 2.5 Installation and Maintenance Guide

• Business Communications Manager 2.5 Software Keycode Installation Guide

• Business Communications Manager 2.5 Telephone Features Guide

Preface 17

IP Telephony Configuration Guide

18 Preface

How to get help

Your local distributor can provide technical support for your Business Communications Manager system or have access to that information through a Technical Service Center (TSC).

If you require non-technical support, contact 1-800-4NORTEL (1-800-466-7835), choose option 3, Sales or Pre-Sales Support)

P0937663 02.0

Chapter 1 Introduction

IP Telephony provides the flexibility, affordability and expandability of the Internet to the world of voice communications. Business Communications Manager for VoIP gives you several critical advantages:

• Cost Savings. IP networks can be significantly less expensive to operate and maintain than traditional networks. The simplified network infrastructure of an Internet Telephony solution cuts costs by connecting IP telephones over the LAN wiring system and eliminates the need for dual cabling. Internet Telephony can also eliminate toll charges on site-to-site calls via global four-digit dialing. And, by using the extra bandwidth on your WAN for IP Telephony, you leverage the untapped capabilities of your data infrastructure to maximize the return on your current network investment.

• Portability and flexibility. Employees can be more productive because they are no longer confined by geographic location. IP telephones work anywhere on the network, even over a remote connection. With Nortel Networks wireless e-mobility solutions, your phone, laptop, or scanner can work anywhere on the network where a Nortel Networks Access Point is installed. Network deployments and reconfigurations are simplified, and service can be extended to remote sites and home offices over cost-effective IP links.

• Simplicity and consistency. 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 from a central point 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, making 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, a LAN, frame relay, asynchronous transfer mode, SONET or wireless connection.

• Scalability. A future-proof, flexible, and safe solution combined with high reliability lets your company focus on customer needs, not network problems. Nortel Networks Internet Telephony solutions offer hybrid environments that leverage existing investments in Meridian and Norstar systems.

• Increased customer satisfaction. Breakthrough e-business applications help deliver the top-flight customer service that leads to success. By providing your customers rapid access to sales and support personnel via phone, the Web, and e-mail, your business can provide better customer service than ever before.

IP telephones and VoIP trunks

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

IP Telephony Configuration Guide

20 Chapter 1 Introduction

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 plugged into an IP network which is connected to the LAN or WAN card on the Business Communications Manager. Calls made from IP telephones can pass over VoIP trunks or across a Public Switched Telephone Network (PSTN).

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 transmitted through the IP network. The device at the other end reassembles the packets into a voice signal.

The IP telephony network

This section explains the components of the Business Communications Manager system and the devices it interoperates with to create a network. Figure 1: Network diagram on page 21 shows components of the Business Communications Manager system.

P0937663 02.0

Inspect FORWARD Callers

MXP

Inspect FORWARD Callers

MXP

Figure 1 Network diagram

Chapter 1 Introduction 21

Router

Internet

Inspect FO

ARD Ca

llers

H.323 Device A

Gatekeeper

LAN A

IP set A

WAN

BCM A

Router

PSTN

Norstar set A

I2050 set A

Router

LAN B

BCM B

In spect FO

RWA

RD Callers

MXP

M1-ITG

Meridian set A

H 323 Device B

IP set B

Business Communications Manager

The Business Communications Manager is a key building block in creating your network. It interoperates with many devices including the M1 and any H.323 device. In this network diagram, the Business Communications Manager system is connected to devices through multiple IP networks as well as the PSTN. Multiple Business Communications Manager systems can be linked together on a network.

In Figure 1: Network diagram on page 21, BCM A is connected to a LAN (via a LAN card), a WAN (via a WAN card), and a PSTN (via Media Bay Modules). Through these networks, the system accesses other systems and network equipment connected to the network.

IP Telephony Configuration Guide

22 Chapter 1 Introduction

M1-ITG

The Meridian 1 Internet Telephony Gateway lets the M1 communicate with H.323 devices including the Business Communications Manager. In Figure 1: Network diagram on page 21, telephones on the M1 such as Meridian set A can initiate and receive calls with the other telephones on the system across IP networks.

Telephones

The Business Communications Manager system can communicate using several different types of telephones, ranging from traditional analog and digital telephones to IP telephones and H.323 terminals.

Traditional telephones

While traditional telephones cannot be connected to the Business Communications Manager system with an IP connection, they can use VoIP trunks to make calls to other locations on a network.

IP telephones

Nortel IP telephones include the i2004, i2002 and i2050. These devices connect to the Business Communications Manager across an IP network through either a LAN or a WAN.

H.323 terminals

H.323 terminals include computers that have Microsoft NetMeeting installed, or other third-party devices. These terminals connect through the network to either the LAN or WAN card on the Business Communications Manager.

Gatekeeper

A gatekeeper tracks IP addresses of specified devices, and provides authorization for making and accepting calls for these devices. A gatekeeper is not required for the Business Communications Manager system, but can be useful on networks with a large number of devices. In Figure 1:

Network diagram on page 21, for example, when Norstar set A wants to call an H.323 device, and

Norstar set B is under the control of the gatekeeper, Norstar set A sends a request to the gatekeeper. The gatekeeper, depending on how it is programmed, provides Norstar set A with the information it needs to contact Norstar set B.

IP Network

In the network shown in Figure 1: Network diagram on page 21 several LANs and a WAN are shown. When planning your network, be sure to consider your other needs for a data network.

P0937663 02.0

Chapter 1 Introduction 23

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.

LAN

A Local Area Network (LAN) is a communications network that serves users within a confined geographical area. For Business Communications Manager, a LAN is any IP network connected to a LAN card on the Business Communications Manager system. Often, the LAN can include a router that forms a connection to the Internet.

Public Switched Telephone Network

The Public Switched Telephone Network (PSTN) can play an import role in IP Telephony communications. In many installations, the PSTN forms a fallback route, so that if a call across a VoIP trunk does not have adequate voice quality, the call is routed across the PSTN instead. The Business Communications Manager also serves as a gateway to the PSTN for users on the system.

Key IP Telephony Concepts

In traditional telephony, the voice path between two telephones is circuit switched. This means that the analog or digital connection between the two telephones is dedicated to the call. The voice quality is usually excellent, since there is no other signal to interfere.

In IP telephony, voice quality between IP telephones can vary significantly from call to call and time of day. When two IP telephones are on a call, each IP telephone encodes the speech at the handset microphone into small data packets called frames, and sends the frames across the IP network to the other telephone 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.

Codecs

The algorithm used to compress and decompress 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.

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 quality by configuring the IP telephone to use a G.729 CODEC.

IP Telephony Configuration Guide

24 Chapter 1 Introduction

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, voice quality is perceived as good. In many cases, however, some frames can arrive slightly faster or slower than the other frames. This is called jitter, and degrades the perceived voice quality. To minimize this problem, configure the IP telephone with a jitter buffer for arriving frames. This is how the jitter buffer works:

Assume a jitter buffer setting of five frames.

• The IP telephone firmware places 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 telephone buffers it and send frame two to the handset speaker.

The net effect of using a jitter buffer is that the arriving packets are delayed slightly in order to ensure a constant rate of arriving frames at the handset speaker. The disadvantage of using a jitter buffer is that the speech arrives delayed by the number of frames in the buffer. For one-sided conversations, this is not an issue. For conversations where one party tries to interrupt the other speaking party, it is annoying because by the time the voice of the interrupter reaches the interruptee, the interruptee has spoken (2*jitter size) frames past the intended point of interruption. 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 system IP telephones are:

• None

• Small (.06 seconds)

• Medium (.12 seconds)

• Large (.18 seconds)

QoS routing

When it sends a voice frame onto the network, the IP telephone firmware places some header information on the frame.

The header contains the network address of the sending and receiving IP telephones, and a TOS (Type Of Service) byte, which contains a routing priority.

The IP telephone firmware establishes the TOS byte to the highest possible priority so that as the voice frame travels through the network, the routers it encounters give it higher routing priority than competing data frames resulting from file transfers, WEB downloads, e-mails, etc. This process of prioritizing data frames is Quality of Service (QoS) routing.

P0937663 02.0

Chapter 1 Introduction 25

The Business Communications Manager system does 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-switched line if a suitable QoS cannot be guaranteed.

IP Telephony Configuration Guide

26 Chapter 1 Introduction

P0937663 02.0

Chapter 2 Prerequisites checklist

Before you set up VoIP trunks or IP telephones on a Business Communications Manager, complete the following checklist to ensure that the system is set up properly. Some questions do not apply to all installations.

Network diagram

To aid in installation a Network Diagram is needed to provide a basic understanding of how the network is configured. Before you install VoIP functionality, you must have a network diagram that captures all of the information described below. If you are configuring IP telephones but not IP trunks, you do not need to answer 1.d and 1.e.

Tabl e 1 Network diagram

Prerequisites Yes No

1.a Has a network diagram been developed?

1.b Does the network diagram contain any routers, switches or bridges with corresponding IP addresses and bandwidth values for WAN or LAN links?

1.c Does the network diagram contain IP Addresses and network locations of all BCMs?

1.d Answer this if your system will use IP trunks, otherwise, leave it blank: Does the network diagram contain IP Addresses of any other Voice over IP gateways desired to connect to?

1.e Answer this only if your system will use a gatekeeper, otherwise, leave it blank: Does the network diagram contain alias for any Gatekeeper that may be used?

Network devices

This section of the checklist contains questions about devices on the network such as firewalls, NAT devices, and DHCP servers.

IP Telephony Configuration Guide

28 Chapter 2 Prerequisites checklist

Tabl e 2 Network device checklist

Prerequisites Yes No

2.a This section of the checklist contains questions about devices on the network such as

firewalls, NAT devices, and DHCP servers.

2.b Is the network using private IP addresses? If the network uses public IP addresses, complete 2.c. If the network uses private IP addresses, complete 2.d to 2.e.

2.c Are there enough public IP addresses to accommodate all IP telephones and the Business Communications Manager?

2.d Does the system have a firewall/NAT device, or will the BCM be used as a firewall/ NAT device?

2.e The Business Communication Manager has limited space fore firewall rules. If the Business Communications Manager is to be used as a firewall/NAT device, do the firewall rules fit within 32 input rules and 32 output rules?

2.f A hub-based core will not have suitable performance for IP Telephony. Does the network use a non-hub solution at its core?

Network assessment

This section ensures that the network is capable of handling IP Telephony and that existing network services are not adversely affected.

Tabl e 3 Network assessment

Prerequisites Yes No

3.a Has a network assessment been completed?

3.b Has the number of switch/hub ports available and used in the LAN infrastructure been calculated?

3.c Have the used and available IP addresses for each LAN segment been calculated?

3.d Has DHCP usage and location been recorded?

3.e Has the speed and configuration of the LAN been calculated?

3.f Has the estimated latency values between network locations been calculated?

3.g Bandwidth/CIR utilization values for all WAN links.

3.h Has the quality of service availability on the network been calculated?

Resource Assessment

You must allocate sufficient resources on the Business Communications Manager for IP telephony.

P0937663 02.0

Chapter 2 Prerequisites checklis t29

Tabl e 4 Resource Assessment

Prerequisites Yes No

4.a Has a Business Communications Manager Resource Assessment been performed

using the resource questionnaire in the Programming Operations Guide?

4.b Has an analysis been done to determine which DS-30 split is appropriate for the system, and has the DS-30 split been changed to 5/3 if necessary?

4.c Have all necessary media resources for IP trunks, clients, vmail or WAN dialup been assigned or dedicated?

Keycodes

All elements of VoIP trunks and IP telephony are locked by the Business Communications Manager keycode system.

Tabl e 5 Keycodes

Prerequisites Yes No

5.a Complete this question only if you are using VoIP trunks: Do you have enough VoIP

keycodes?

5.b Complete this question only if you are using IP telephones: Do you have enough IP client keycode?

Business Communications Manager System Configuration

Several sections of the the Business Communications Manager must be properly configured prior to activatio n o f I P telephony.

IP Telephony Configuration Guide

30 Chapter 2 Prerequisites checklist

Tabl e 6 Business Communications Manager system configuration

Prerequisites Yes No

6.a Is the LAN functioning properly with the Business Communications Manager?

6.b Is the WAN functioning properly with the Business Communications Manager?

6.c Has a dialing plan been created, taking into account special considerations for IP telephony?

6.d Has a preference been established between pre-configured DNs and auto-assigned DNs? If the preference is for auto-assigned DNs, complete 6.e.

6.e Complete this question only if you are not using Auto-assign DNs. Have set DNs been programmed for the corresponding IP clients?

IP Telephones

Complete this section only if you have IP telephones.

Tabl e 7 IP telephones

Prerequisites Yes No

7.a Are IP connections and IP addresses available for all IP telephones?

7.b If DHCP is not being used, has all telephone configuration been documented and made available for telephone installers?

7.c Has telephone powering been provisioned?

7.d Do computers that will be using the i2050 soft phone meet the minimum system requirements, including headset?

7.e Are IP connections and IP addresses available for all IP telephones?

P0937663 02.0

+ 98 hidden pages