AT&T Definity Enterprise R 8-2 Admin for Network - Connectivity

Download

DEFINITY

Enterprise Communications Server

Release 8.2 Administration for Network Connectivity

555-233-504 Comcode 1086787 49 Issue 1 April 2000

Notice

Every effort was made to ensure that the information in this book was complete and accurate at the time of printing. However, information is subject to change.

Your Responsibility for Your System’s Security

Toll fraud is the unautho r ized use of your teleco mmu ni cations system by an unauthorized party, for example, persons other than your com -

pany’s employees, agents, subcontractors, or persons working on your company’s behalf. Note that there may be a risk of toll fraud associated with your telecommuni cations system and, if toll frau d occur s , it can result in substantial additional charges for your telecommunications services.

You and your system manager are responsible for the security of your system, such as programming and configuring your equipment to pr event unauthorized use. The system manager is also responsible for reading all installation, instru ct io n, and syst em administration documents provided with this product in ord er t o ful ly un derstand the features that can introduce risk of toll fraud and the steps that can be taken to reduce that risk. Lucent Technologies does not warrant that this product is immune from or will pre v e nt un authorized use of common-carrier tele commu nica ti on serv ices o r faci li ties a cce ssed thr ough or connected to it. Lucent Technologies will not be responsible for any charges that result from such unauthorized use.

Lucent Technologies Fraud Intervention

If you suspect that yo u a r e be ing vict imiz ed by toll fraud and you need technical support or assistance, cal l Technical Service Center Toll Fraud Intervention Hotl ine at 1 800 643-2353 or contact you Luce nt representative.

Federal Communications Commission Statement Part 15: Class A Statement. This equipm ent has been tested and

found to comply with the lim it s f or a Class A digital device, pursua nt to Part 15 of the FCC Rules. These limi ts are de signed to provide reasonable protection against harmful interference when the equipment is operated in a commerci al environment. This equipment generates, uses, and can radiate rad io -frequency energy and, if not inst alled and used in accordance with the instructions, may cause harmful interference to radio commu nications. Ope r ation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be re q uired to corr ect the interfe rence at his own expense.

Part 68: Network Registratio n N umber. This equipment is registered with the FCC in acco r dance with Pa r t 68 of the FCC Ru les. It is identified by FCC registration numbe r A S 59 3M-13283-MF-E.

Part 68: Answer-Supervision Signaling. Allowing this equipment to be operated in a manner that does not provide proper answer-supervision signaling is in violation of Part 68 Rules. This equipment returns answer-supervision signals to the public switched network when:

• Answered by the called station

• Answered by the attendant

• Routed to a recorde d an nouncement that can be administered by the CPE user

This equipment returns answe r-superv isi on sig nals on all DID calls forwarded back to the public switched telephone network. Permissible exceptions are:

• A call is unanswere d

• A busy tone is received

• A reorder tone is rece iv ed

Canadian Department of Communications (DOC) Interference Information

This digital apparatus does not exceed the Class A limits for radio noise emissions set out in the radio in te rfe rence regulations of the Canadian Department of C ommunications.

Le Présent Appareil Nomérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la class A préscrites dans le reglement sur le br ouillage rad ioélectriqu e édicté par le ministére des Comm unications du Canada.

Trademarks

See the preface of this document.

Ordering Information Call: Lucent Technologies BCS Publications Center

US V oice 1 888 582 3688 US Fax 1 800 566 9568 Canada Voice +317 322 6619 Europe, Middle East, Africa Voice +317 322 6416 Asia, China, Pacifi c Region, Caribbean, Lati n A m erica Voice +317 322 6411 Non-US Fax 1 317 322 6699

Write: Lucent Technologies BCS Publications Center

2855 N. Franklin Road, Indianapolis, IN 46219

Order: Document No. 555-233-504

Comcode 108678749 Issue 1, April 2000

For additional documents, refer to the appedix , “ Re ferences.”

You can be placed on a standing orde r li st for thi s and ot her documents you may need. Standing ord er wi ll ena bl e yo u to a uto m at ic ally receive updated versions of indi vid ua l do cuments or document sets, billed to account information that you provide. For more information on standing orders, or to be put on a list to receive future issues of this document, contact the Lucent Technologies Publications Center.

European Union Declaration of Conformity

The “CE” mark affixed to the DEFINITY® equipment described in this book indicates that the eq ui pm en t co nf o r ms to th e following European Union (EU ) D ire c ti ves:

• Electromagnetic Comp atibility (89/336/EEC)

• Low Voltage (73/23/EEC)

• Telecommunications Terminal Equipment (T TE) i-CTR3 BRI and i-CTR4 PRI

For more informati on on stan dar ds compli ance , cont ac t you r loca l di stributor.

Comments

To c omment o n th is doc ument, r etu rn t he c ommen t car d at the fro nt of the document.

Acknowledgment

This document was prepared by Product Docume nt ation Development, Lucent Technologies, Denver, CO.

CID: 77730

Preface ix

Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Issue Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

How to access this book from the web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

How to order more copies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Tell us what you think . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii

How to Order Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii

How to Comment on This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii

Where to Call for Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

1 Networking Overview 1

DEFINITY Switch Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Connectivity Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Release 8 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Hardware Requirements for Upgrades from Pre-R7 Switches . . . . . . . . . . . . . . . . 7

DEFINITY Connection types and capacities . . . . . . . . . . . . . . . . . . . . . . . . . 9

IP Softphones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Physical Addressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Logical Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Subnetting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Default Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

When to use IP routes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2 H.323 Trunks 31

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

IP Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

IP-Connected Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

IP Softphones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

H.323 Trunk Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Enabling Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

H.323 Trunk Administration — Task Summary . . . . . . . . . . . . . . . . . . . . . . . 36

H.323 Trunk Administration — Task Detail . . . . . . . . . . . . . . . . . . . . . . . . . 38

Troubleshooting IP Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

H.323 Trunk Problem Solving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

IP Softphone Problem Solving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Administration for Network Connectivity

555-233-504 — Issue 1 — April 2000 CID: 77730

iii

Contents

3 C-LAN Administration 53

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Intuity AUDIX LAN Setup Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

CMS LAN Setup Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Configuration 1: R8r <—ppp—> R8si . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Configuration 2: R7r (+CMS) <—ethernet—> R7csi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Intuity System Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Administer Subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

Worksheet A: Names and IP Addresses for Lucent Intuity System. . . . . . . . . . . . . .96

Worksheet B: LAN Data for the Lucent Intuity System . . . . . . . . . . . . . . . . . . . .97

Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si . . . . . . . . . . . . . . . . . . .99

Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi . . . . . . . . . . . . . . . . . .124

Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si . . . . . . . . . . . . . .146

Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si. . . . . . . . . . . . . . .171

4 Networking Example 203

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203

Network Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Task Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Link/Channel/TSC Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206

Network Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207

Switch-Node 1 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208

DS1 Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Signaling Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Synchronization Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Trunk Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Uniform Dialing Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

AAR Digit Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 6

ISDN TSC Gateway Channel Assignment . . . . . . . . . . . . . . . . . . . . . . . . . 217

Routing Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Node Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Data Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Processor Channel Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Switch-Node 2 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222

DS1 Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Synchronization Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Trunk Goups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Uniform Dialing Paln . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

AAR Digit Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5

Routing Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Data Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Processor Channel Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Hunt Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

CID: 77730 555-233-504 — Issue 1 — April 2000

Administration for Network Connectivity

Contents

Switch-Node 3 Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

DS1 Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Synchronization Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Signaling Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Trunk Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Uniform Dialing Paln . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

AAR Digit Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Routing Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Hunt Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Switch-Node 4 Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Bus Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

DS1 Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Synchronization Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Trunk Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Uniform Dialing Paln . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

AAR Digit Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Routing Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Node Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Data Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Processor Channel Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

IP Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Hunt Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Intuity Translations for DCS AUDIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

CMS Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Appendix A: Screens Reference 243

Networking Screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Other Network-Related DEFINITY Screens . . . . . . . . . . . . . . . . . . . . . . . . 244

Networking Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Node Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

page 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Pages 2 – 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

IP Media Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Data Module Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Common Data Module Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Data Module — Type ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Data Module — Type ppp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Data Module — Type procr-intf (used for BX.25 connections with the si model) . . . . . . 266

Data Module - type X.25 (used for BX.25 connections with the r model) . . . . . . . . . . 269

Data Module - type pdm (used for BX.25 connections with the r model) . . . . . . . . . . 272

Communication-Interface Processor Channel . . . . . . . . . . . . . . . . . . . . . . . 273

Administration for Network Connectivity

555-233-504 — I ss ue 1 — April 2000 CID: 77730

Contents

Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Signaling Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

ISDN TSC Gateway Channel Assignments . . . . . . . . . . . . . . . . . . . . . . . . 291

Other Networking-Related DEFINITY Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293

Communication Interface Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Data Module - type netcon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Data Module - type analog-dm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Extended Trunk Access Call Screening . . . . . . . . . . . . . . . . . . . . . . . . . . 298

Extension Number Portability Numbering Plan . . . . . . . . . . . . . . . . . . . . . . . 299

Hop Channel Assignments Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Implementation notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Node Number Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Message Waiting Indication Subscriber Number Prefixes . . . . . . . . . . . . . . . . . 303

Synchronization Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Pages 1–X of the screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Uniform Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Appendix B: Private Networking 311

Contents of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311

Distributed Communications System (page 312) . . . . . . . . . . . . . . . . . . . . . 311

ISDN Feature Plus (page 355). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

QSIG (page 360). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

Centralized Voice Mail Via Mode Code (page 395) . . . . . . . . . . . . . . . . . . . . 311

Japan TTC Q931-a Private Networking Protocols (page 400). . . . . . . . . . . . . . . 311

Distributed Communications System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312

Description of DCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

DCS Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Italian DCS Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

ISDN/X.25 gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

DCS Over ISDN-PRI D-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

DCS feature considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

DCS Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Example DCS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Centralized Attendant Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Extended Trunk Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Extension Number Portability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Inter-PBX Attendant Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Private Network Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

Uniform Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

ISDN Feature Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355

How to administer ISDN Feature Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

Differences in Inserted Digits field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

Interrogation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

CID: 77730 555-233-504 — Issue 1 — April 2000

Administration for Network Connectivity

Contents

QSIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

QSIG Basic Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

QSIG Basic Supplementary Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

QSIG Centralized Attendant Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

QSIG Supplementary Services with Rerouting . . . . . . . . . . . . . . . . . . . . . . . 367

QSIG Transfer into Lucent QSIG Voice Mail . . . . . . . . . . . . . . . . . . . . . . . . 368

QSIG Value-Added Lucent (VALU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

QSIG Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Temporary Signaling Connection (TSCs) . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Setting Up QSIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

QSIG Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Centralized Voice Mail Via Mode Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

Configuration requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

Feature Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

Setting Up Centralized Voice Mail Via Mode Code . . . . . . . . . . . . . . . . . . . . . 397

Japan TTC Q931-a Private Networking Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400

TTC Basic Call Setup with Number Identification Supplementary Service . . . . . . . . . 400

TTC Q931-a Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

Setting Up TTC Q931-a. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

Appendix C: Security Issues 403

Network Security Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

Appendix D: Capacities and Performance 407

Capacities and Resource Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 407

Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

Appendix E: C-LAN Installation 413

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

Install the C-LAN Circuit Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

Other Hardware Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

Appendix F: IP Trunk Installation and Administration 417

IP Trunk Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

IP Trunk Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

Administration overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

Plan call routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

DEFINITY administration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . 421

Backing up configuration manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

Restoring IP trunk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

Confirming the number of available ports. . . . . . . . . . . . . . . . . . . . . . . . . . 426

NT administration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

Procedures for Extension Dialing Between Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433

Non-DCS Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433

Administration for Network Connectivity

555-233-504 — I ss ue 1 — April 2000 CID: 77730

vii

Contents

DCS over IP Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .435

DCS or Dedicated Trunks to Specific Locations Configurations . . . . . . . . . . . . . . 436

Rerouting calls when IP transmission quality is poor . . . . . . . . . . . . . . . . . . . . 439

Placing a test telephone call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440

Setting up alerts on IP trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440

Alert types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442

Viewing error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442

Troubleshooting IP trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443

Maintaining the performance of the IP trunk server . . . . . . . . . . . . . . . . . . . . 444

Configuring Microsoft NetMeeting™ on a PC . . . . . . . . . . . . . . . . . . . . . . . 445

IP Trunk Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .449

Appendix G: References 459

Basic DEFINITY ECS documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459

Call center documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462

Application-specific documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463

Glossary 465 Index 491

viii

CID: 77730 555-233-504 — Issue 1 — April 2000

Administration for Network Connectivity

Preface

This book describes how to administer connections between DEFINITY® ECS switches (csi, si, and r models). The main focus is on TCP/IP for DCS signaling, introduced with DEFINITY Release 7, and H.323 trunks, introduced with DEFINITY Releases 8.

Purpose

This document provides the information needed to understand and administer the connections between DEFINITY ECS systems in a network using IP connections. It does not cover the installation or upgrade procedures for establishing physical connectivity between DEFINITY switches or for connecting the CMS and

Intuity AUDIX adjuncts to a DEFINITY switch — that information is contained in the upgrades and installation documents listed in the References section.

Audience

This document is intended for anyone involved in planning, designing, or administering DEFINITY ECS systems as part of networks using IP connectivity.

Issue Status

First issued for DEFINITY ECS Release 7, this update includes Release 8 new hardware and administration, as described below.

IP Interface assembly The Release 8 IP Interface assembly is a 3-slot wide TN802B circuit pack. It enables

the transmission of voice and signaling data over IP connections. It can be used in one of two operating modes:

• MedPro mode — enables H.323 tie trunks over IP connections

• IP trunk mode (as in Release 7) — enables emulation of DS1 trunks over IP

connections.

Each IP Interface assembly operates in either Medpro mode or IP trunk mode for all trunks assigned to it — it cannot mix modes. The MedPro mode is the normal operating mode for R8 systems. The IP Trunk mode is used only for compatibility with existing R7 systems that cannot be upgraded to R8.

The C-LAN (TN799B) circuit pack is required to handle signaling for the Medpro mode. C-LAN can be used, but is not required, for signaling in the IP Trunk mode.

Administration for the MedPro mode includes the H.323 trunking introduced with Release 8 and is documented in Chapter 2. Administration for the IP trunk mode is documented in Appendix F and is unchanged from Release 7.

Administration for Network Connectivity

555-233-504 — Issue 1 — April 2000 CID: 77730

Issue Status Preface

Screen Changes In Release 8, the following changes have been made to screens related to IP networks.

Ethernet Data Module screen

The ethernet Data Module screen is changed in Release 8.

add data-module next Page 1 of X

Data Extension: 2377 Name: __________________

Type: ethernet Port: ________ Link: 2

Network uses 1’s for broadcast addresses?: y

1 The following fields have been removed from the ethernet Data Module screen:

• Broadcast Address

• Automatic Subnet Routing

DATA MODULE

The Broadcast Address field previously enabled you to specify that broadcast

messages are to be sent to a subset of the host’s subnet. Now, broadcast messages are always sent to the host’s full subnet.

The Automatic Subnet Routing field previously enabled you to disable automatic subnet routing. Now, automatic subnet routing is always enabled.

2 The following fields have been moved from the ethernet Data Module screen to

the new IP Interfaces screen:

• Enable Link?

• Node Name

• Subnet Mask

3 The following field is added to the ethernet Data Module screen:

• Network uses 1’s for broadcast addresses?

This field enables you to accommodate systems on your network that use the older method of putting 0’s instead of 1’s in the host portion of a broadcast address.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Issue Status

ppp Data Module screen

The ppp Data Module screen is changed in Release 8.

add data-module 1994 Page 1 of x DATA MODULE

Data Extension: 1994 Name: _ppp on link 4 to node 4___ BCC: 2 Type: ppp COS: 1 Port: 01c1502 Link: 4 Enable Link? n

Node Name: ppp14_____

Subnet Mask: 255.255.255.0

Establish Connection: y

_ TN: 1

COR: 1

Preface

DESTINATION Digits: 7241991

Node Name: ppp41___________

CHAP? n

_________

The following fields have been added to the ppp Data Module screen:

• Subnet Mask

The Mask field enables you to specify a subnetwork for the IP address of this node.

iP routing and the IP Route screen

add ip-route next Page 1 of 1 IP ROUTING

Route Number: 3 Destination Node: Gateway: C-LAN Board: Metric:

The following fields have been added to the IP Routing screen:

• Route Type — display onl y

For the display, change, and list IP Route commands, a display-only field, Route Type, indicates whether this IP route is a “host” or “network” route. Whether an IP route is a host or network route is determined by the Destination Node IP address and the subnet mask associated with that address.

Administration for Network Connectivity

555-233-504 — I ss ue 1 — April 2000 CID: 77730

Issue Status Preface

New Fields

In addition to the R8 screen changes described above, the following screens have new fields that specify IP trunk or IP Softphone parameters:

• Optional Parameter (System-Parameters Customer Options)

• Trunk Groups

• Signaling Group

• Station

• Several Status and Measurement screens

New Screens In Release 8, the following IP-related screens are new.

IP Interfaces screen

The IP Interfaces screen is new for Release 8.

change ip-interfaces Page 1 of 2

IP Interfaces

Inter-region IP connectivity allowed? n Enable Net Eth Pt Type Slot Code Sfx Node Name Subnet Mask Gateway Addr Rgn

n 255.255.255.0 . . . n 255.255.255.0 . . .

n 255.255.255.0 . . .

The fields for this screen are described in Appendix A, “Screens Reference.”

IP Media Parameters

The IP Media Parameters screen specifies the type of codecs available for voice processing. The order in which you list the codecs is the order in which the system will use them. This screen also specifies the range of audio port numbers available.

change ip-parameters Page 1 of 1 IP Media Parameters Audio Codec Preferences 1: G.711MU

2: G.723-6.3K

3: G.729A

UDP Port Range Min: 2048

Max: 65535

Administration for Network Connectivity

xii

CID: 77730 555-233-504 — Issue 1 — April 2000

Issue Status

Reorganization The following chapter reorganization has been made for Release 8.

• New Chapter 2 covers H.323 trunk administration.

• The previous Chapter 2 has been renamed Chapter 3. This chapter now

describes how to connect switches and adjuncts using the C-LAN signaling

connectivity — without the H.323 functionality — if you are running Release 8 software. This would be the case if you use R8 as a bugfix for R7 or if you are using the IP Interface board in IP Trunk mode.

• Chapter 3 has been renamed Chapter 4. The example network is the same as

for R7 with the Data Module and IP Interfaces screens updated. A subsequent issue of this book will add MedPro functionality in the example network.

• The appendix sections are organized as in R7 and updated for R8 changes.

Preface

Administration for Network Connectivity

555-233-504 — I ss ue 1 — April 2000 CID: 77730

xiii

Organization Preface

Organization

This document is organized into four chapters and seven appendixes. Chapter 2 gives the essential infor mat ion needed to administer H.323 trunk connections.

Chapter 1 – Overview

An overview of DEFINITY Connectivity and IP Addressing

Chapter 2 – H.323 Trunk

Gives detailed procedures for initial administration of IP trunks using H.323 IP connections.

Administration

Chapter 3 – C-LAN Administration

Gives detailed procedures for six basic network configurations using C-LAN IP connections.

Chapter 4 – Network Example

Shows administration screens for setting up a complex network.

Appendix C Security

A brief discussion of security issues as related to networking.

Appendix A – Screens Reference

Field descriptions for network-related administration screens.

Appendix B – Private Networking

DCS features and QSIG.

Appendix D – Capacity and Performance

A brief discussion of network capacities and how to estimate C-LAN and voice-processing resources.

Appendix E – C-LAN Installation

Installation procedures for the C-LAN circuit pack.

Appendix F– IP Trunk Installation & Admin

Installation and initial administration for IP Trunk.

Appendix G– Document Reference

The DEFINITY documentation library.

Glossary Index

xiv

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Terminology

Preface

Terminology

The terms form, screen and node are used in this book with somewhat different meanings than in previous documents. The usage of the terms MedPro and IP Interface in this book deserve an explanation.

Screen The term “screen” is used in this book to mean what used to be called “form” — the

set of switch-administration interface pictures that contain the fields that hold the switch-translations values. For example, the “Data Module screen.” Each screen can have one or more pages.

In some parts of this book, he terms “screen” and “form” are used interchangeably.

Node The term “node” has two meanings for DEFINITY ECS switches connected in a

network. In a DCS network, node means a switch or adjunct. This is how the term is used on the Dial Plan screen for the field name, “Local Node Number.”

With TCP/IP connectivity, node has a different meaning — it refers to an interface to a network. For example, each of the 17 ports on the C-LAN board is a node in this sense. This is how the term is used on the Node Names, Data Module, Processor Channel, and IP Routing screens. This is also th e common usag e in a data networ king environment. With these definitions, a “DCS node” (a switch) can have many “IP nodes,” (network interfaces).

In this book, node is used in the second sense, as a network interface. A “DCS node” is referred to as a switch or, in Chapter 4, as a swit ch node.

IP Interface and Med Pro The official name for the TN802B circuit pack is IP Interface assembl y. It is a media

processing circuit pack in a 3-slot wide assembly. It can be administered to operate in one of two modes — IP Trunk mode or MedPro mode.

MedPro is a contraction of the words, media processor. Since the TN802B IP Interface assembly does media processing, it is also referred to as the MedPr o boa rd.

The TN802B IP Interface assembly is an IP interface for DEFINITY ECS — it connects directly to a 10/100BaseT LAN or WAN, which uses the TCP/IP protocols. The C-LAN (TN799B) circuit pack is also an IP interface for DEFINITY ECS.

In this book, the terms TN802B circuit pack, TN802B IP Interface, IP Interface assembly, and MedPro board are used interchangeably.

Administration for Network Connectivity

555-233-504 — I ss ue 1 — April 2000 CID: 77730

How to access this book from the web Preface

How to access this book from the web

If you have internet access, you can view and download the latest version of DEFINITY ECS Release 8.2 Administration for Network Connectivity. To view the book, you must have a copy of Adobe Acrobat Reader (www.adobe.com).

To access the latest version:

1 Access the Customer Self-Service Center web site at

http://www.lucent.com/enterprise/selfservice

2 Click Information Resources. 3 Click ELMO 4 Enter your IL to access the library. 5 Enter 555-233-504 (the document number) to view the latest version of the

book.

To access this book from within the Lucent intranet, go to www.prodpubs.lucent.com.

How to order more copies

Call: Lucent Technologies Publications Center

Voice 1-800-457-1235 Fax 1-800-457-1764 International Voice 317-322-6416 International Fax 317-322-6699

Write: Lucent Technologies Publications Center

2855 N. Franklin Road, Indianapolis, IN 46219

Order: Document No. 555-233-504

Comcode 108678749, Issue 1, Apri l 2000

We can place you on a standing order list so that you will automatically receive updated versions of this book. For more information on standing orders, or to be put on a list to receive future issues of this book, please contact the Lucent Technologies Publications Center.

xvi

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Tell us what you think

Let us know what you like or don’t like about this book. Although we can’t respond personally to all your feedback, we promise we will read each response we receive. You can use the comment card at the back of the book or send us your feedback in your own format.

Write to us at: Lucent Technologies

Fax to: 303-538-1741 Send email to: document@drmail.lucent.com

How to Order Books

In addition to this book, other description, installatio n and test, maintenance, and administration books are available. A complete list of DEFINITY books can be found in the Business Commu nications System Publications Catalog, 555-000-01 0.

Preface

Product Documentation Group Room 22-2H15 11900 North Pecos Street Denver, CO 80234 USA

This book and any other DEFINITY books can be ordered directly from the Lucent Technologies Business Communications Sy stem Publications Fulfillment Center at 1-317-322-6791 or toll free at 1-800-457-1235.

How to Comment on This Book

Lucent Technologies welcomes your feedback. Please fill out the reader comment card found at the front of this manual an d return it. Your comments are of g reat value and help improve our documentation.

If the reader comment card is missing, FAX your comments to 1-303-538-1741 or to your Lucent Technologies representative, and mention this book’s name and number, DEFINITY ECS Release 8.2 Administration for Network Connectivity, 555-233-501.

Administration for Network Connectivity

555-233-504 — I ss ue 1 — April 2000 CID: 77730

xvii

Where to Call for Technical Support Preface

Where to Call for Technical Support

Use the telephone numbers in the following table for technical support.

Telephone Number

Streamlined Implementation (for missing equipment) 1-800-772-5409 USA/Canada Technical Service Center 1-800-248-1234 Technical Service Center (INADS Database

Administration) Asia/Pacific Regional Support Center 65-872-8686 Western Europe/South Africa/Middle East 441-252-774-800 Business Communications Europe 441-252-391-789 Eastern/Central Europe 361-345-4334 International Technical Assistance Center (ITAC) 1-303-804-3777 Latin/Central America & Caribbean 1-303-804-3778 DEFINITY Helpline 1-800-225-7585 Lucent Technologies Toll Fraud Intervention 1-800-643-2353 Lucent Technologies Technical Service Center 1-800-242-2121 Lucent Technologies Corporate Security 1-800-822-9009

1-800-248-1111

xviii

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Trademarks

Preface

The following are trademarks or registered trademarks of Lucent Technologies:

• 5ESS™, 4ESS™

• AUDIX

• Callvisor

• Callmaster

• CentreVu™

• CONVERSANT

• DEFINITY

• DIMENSION

• INTUITY™

• MERLIN

• VOICE POWER

The following are trademarks or registered trademarks of AT&T:

• ACCUNET

• DATAPHONE

• MEGACOM

• MULTIQUEST

• TELESEER

The following are trademarks or registered trademarks of other companies:

• Acrobat

• MS-DOS

• MULTIQUEST

• ProShare

• UNIX

Administration for Network Connectivity

555-233-504 — I ss ue 1 — April 2000 CID: 77730

is a registered trademark of Adobe Systems Incorporated

(registered trademark of the Microsoft Corporation)

(registered trademark of Telecommunications Service)

(registered trademark of Intel Corporation)

(trademark of the Novell Corporation)

xix

Trademarks Preface

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

1 Networking Overview

This chapter provides background information that will help you understand and use the information in the remainder of the book. There are two major sections in this chapter. The first section describes how DEFINITY ECS switches can be connected, with a focus on IP connectivity. The second section describes IP addressing and subnetting.

DEFINITY Switch Connectivity

This section describes the basic components of a network of DEFINITY switches and how voice and signaling data are transmitted between switches for the different types of switch connections. It also provides a summa r y of the administration procedures for connecting switches via an IP network (using the C-LAN and TN802B-MedPro circuit packs).

Connectivity Overview

Why connect switches? DEFINITY switches can be connected in various ways for vario us reas ons . T he main

motivation for connecting switches is to enable people within an enterprise to easily communicate with one another, regardless of their physical location or the particular communications server they are assigned to. Inter-switch connections also enable the sharing of communications resources such as messaging and Call Center services.

What kinds of connections are possible?

Trunks

Switches communicate with each other over trunk connections. There are several

kinds of trunks — each kind provides a different set of services for the connection. Commonly used trunk types are (Central Office) CO trunks, which provide connections to the public telephone network through a central office, and tie trunks, which provide connections between switches in a private network.

These and other common trunk types are described in DEFINITY ECS

Administrator’s Guide, 555-233-506. DEFINITY ECS Release 8 introduces the H.323 trunk, which allows voice and fax

data to be transmitted over the Internet to another DEFINITY system with H.323 Trunk capability. The H.323 trunk supports Q.931 services such as DCS+ and QSIG.

Administration for Network Connectivity

555-233-504 — Issue 1 — April 2000 CID: 77730

DEFINITY Switch Connectivity 1 Networking Overview

Networks

When two or more switches are conn ected via tie tr unks, they form a private networ k. There are two basic types of networks for Lucent switches:

• Main-satellite/tributary (MS/T) — A network of switches in which a main switch

is fully functional and provides attendants and CO trunks for connected satellite switches. Tributary switches are connected to the main and may have their own attendant and CO trunks. The main switch may be connected to one or more Electronic tandem networks (ETNs).

• Electronic tandem network (ETN) — A wide-area network of switches in which a

call can tandem through one or more switches on its way from the originating switch to the destination switch. ETNs have a uniform dial plan (UDP), automatic alternate routing (AAR), and automatic route selection (ARS).

AT&T provides a service called software-defined network (SDN) that allows you to build a private network through the AT&T public network facilities. An ETN can be combined with an SDN to form a hybrid (ETN/SDN) network.

The switches in MS/T or ETN networks need to be provisioned with special DEFINITY networking software packages.

DCS

Distributed Communications System (DCS) is a messaging overlay for ETN or MS/T networks. The overlay provides signaling connections between network nodes th at enable certain key call features to operate transparently across the DCS network. That is, the transparent features appear to operate as if the switches in the DCS network were a single switch. For example, the DCS Call Coverage feature enables calls to an extension on one switch to be covered by extensions on a remote switch in the network.

DCS consists of two components — routing and message sig naling. Routing the message requires one of several networking software packages. Typically, UDP is used singe it is included with DCS at no additional charge.

Although DCS is actually a messaging overlay for an existing networ k, it is commonly thought of as a type of network itself. In this document, we will refer to DCS in thi s way — DCS network will refer to a cluster of switches that are part of an existing ETN or MS/T network and are also administered for DCS.

In addition to the normal tie-trunk connections for the transmissio n of vo ice and call-control data, DCS requires a special signaling connection to carry the information needed to make the DCS features work. This signaling connection, or link, between two switches in a DCS network can be implemented in one of three ways:

• over a processor interface (PI) channel (on the si model) or a packet gateway

(PGATE) channel (r mode l) using the X.25 protocol

• over an ISDN-PRI D-channel (csi, si, or r models)

• over a TCP/IP (either PPP or 10Base-T Ethernet) connection (csi, si, or r models)

Note: The csi model does not support X.25 connections.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

DEFINITY Switch Connectivity

TCP/IP signaling connections were introduced with DEFINITY Release 7. Starting with R7, X.25 was no longer sold with new systems. R7 and later new systems ship with only TCP/IP connections or ISDN-PRI for DCS signaling. However, existing systems with X.25 and/or ISDN-PRI DCS signaling can be upgraded to the latest version and keep those signaling links, or a new system can be added to an existing DCS network. Connections to the CMS Call Center and Intuity AU DIX adjuncts can use either X.25 or 10Base-T DCS signaling.

When a DCS network uses a mixture of two or three of the different DCS signaling types, one or more switches in the network must act as a gateway. A gateway switch is connected between two switches using different signaling protocols and the gateway enables the two end switches to communicate by converting the signalin g messages between the two protocols. A gateway switch can provide conversion between two or all three of the signali n g pro t ocols , bu t o nly on e pro t ocol can b e used for DCS signaling between any two switches.

1 Networking Overview

What is transmitted between connected switches?

How does the data move between switches?

A telephone call consists of voice (bearer) data and call-signaling data. If the call is over a DCS network, DCS signaling data is also required. The DCS signaling data is sent over a separate path from the voice and call-signaling data.

Call-signaling data

The call-signaling data includes messages necessary to set up the call connection, maintain the connection during the call, and remove the connection when the call is finished.

DCS-signaling data

The DCS-signaling data is separate from the call-signaling data. How it gets transmitted depends on the connection type, which determines the type of signaling protocol used.

Figure 1 shows some of the major components of switch connections. Before R7, a

call from switch 1 to switch 2, which consists of voice and signaling data, is sent through a trunk circuit pack across a TDM transmission facility to a trunk circuit pack in switch 2. Releases 7 and later add alternate pathways for the call data. In R8 and later releases, Q.931 signaling is used, which enables support for DCS+ and QSIG. The C-LAN circuit pack enables signaling data to be packetized and sent over a LAN, WAN, or the Internet. The IP Interface (TN802B) circuit pack enables voice data and non-DCS signaling data to be sent over IP facilities.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

DEFINITY Switch Connectivity 1 Networking Overview

Figure 1. Components of Switch Connectivity

Processor

DEFINITY Switch 1

PGate (r)

NetPkt (si)

PI (si)

Interface to Transmission

Facilities

Tie-Trunk Circuit Packs

DS1, ISDN-PRI, Analog

PPP

C-LAN

Interface

MedPro

mode

IP trunk

mode

10BaseT

10/100BaseT

Voice Data

Signaling Data

LAN

WAN

DEFINITY Switch 2

Tie Trunk

C-LAN

Interface

MedPro

mode

IP trunk

mode

What do the components do?

The function of each circuit pack shown in Figure 1 is described below.

Processor

The processor board is the main control element in handling the call. This is the UN332B for the r model, the TN 790B for the si model, and the TN798B for the csi model.

PGATE (r only)

On the r model, the PGATE board (TN577) connects the processor to the packet bus and terminates X.25 signaling.

NetPkt (si only)

The Network control/Packet Interface (NetPkt) board (TN794) replaces the NETCON (TN777B) and the PACCON (TN778) circuit packs in the R7si model. It also replaces the LAPD portion of the PI (TN765) circuit pack.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

DEFINITY Switch Connectivity

C-LAN

The C-LAN circuit pack (TN799B) enables signaling data to be transmitted via the TCP/IP protocols across a LAN or WAN. Signaling types include call setup and teardown, registration of IP softphones, TSCs, QSIG and DCS signaling.

The C-LAN circuit pack provides the data link inter face between the switch processor and the transmission facilities. C-LAN prepares the signaling information for TCP/IP

transmission over one of two pathways — either via an Ethernet LAN or a point to point protocol (PPP) conn ection — dependi ng on how the d ata link is ad ministered. I f the link is administered for an ethernet connection, the signaling data is sent out on a 10Base-T network, which is connected directly to the C-LAN ethernet port. If the link is administered for a PPP connection, C-LAN inserts the signaling data on the TDM bus for subsequent inclusion (via the switching fabric) in the sam e D S1 bit s tream as the voice transmissions.

The C-LAN board can be inserted in any available port slot. Up to 10 C-LAN boards can be used in the DEFINITY ECS R8r and R8si models — up to 2 C-LAN boards can be used in the R8csi model. Each C-LAN board has 17 ports; port 17 is used for the LAN interface and the other 16 can be used for PPP connections. Up to 508 sockets are available on each C-LAN circuit pack.

IP-Interface

The IP Interface circuit pack (TN802B) enables two switches to transmit voice data between them over an IP network. The TN802B normally operates in the MedPro mode, which enables support of applications that comply with the H.323-v2 protocols. It can also operate in the IP Trunk mode to support R7 IP trunks that emulate DS1 connections.

1 Networking Overview

Tie-Trunk Circuit Packs

The tie-trunk circuit packs provide an interface between the switch and the transmission facilities for voice data, call-signaling data and data. See System Description, 555-230-211 for descriptions of tie-trunk (and other) circuit packs.

Pre-R7 circuit packs PI (si only)

The PRI functionality of the Processor Interface (PI) board (TN765) is replaced by the NetPkt board (TN794) in R7. The PI board will no longer be shipped with new systems starting with R7. The PI board is needed in switches upgraded to R7 and later releases only if existing X.25 connections are retained. The PI board has 4 data links that can connect to DS1 tie trunks over the TDM bus for interface to DCS or ISDN applications. The PI board terminates BX.25 an d ISDN-PRI link access procedure on the D-Channel (LAPD).

NETCON (si only)

The network controller (NETCON) board (TN77B) is replaced by the NetPkt board (TN794) starting in R7. For pre-R7 systems, NETCON provides an interface to the processor for the port circuit packs on the TDM bus.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

DEFINITY Switch Connectivity 1 Networking Overview

PACCON (si only)

The Packet Controller (PACCON) board (TN778) is replaced by the NetPkt board (TN794) starting in R7. For pre-R7 systems, PACCON provides an interface to the processor for D-Channel signaling over the packet bus.

The following table gives a summary of the different types of call connections and how the voice and signaling data are transmitted between switches.

Tie Trunk LAN or WAN

Connection

Type

Voice & Call-

Signaling

DCS

Signaling Voice

Call & DCS

Signaling

ISDN

(DCS+)

& QSIG

X.25

C-LAN

PPP

C-LAN

Ethernet

Interface

R7—DS1

emulation

(IP Trunk

mode)

T1/E1 facilities using ISDN-PRI or DS1 B-Channel

T1/E1 facilities using ISDN-PRI or DS1 B-Channel OR Analog trunk

TSCs on the ISDN-PRI

D-Channel

Packet PVC

Packet PVC (X.25)

RTP Packet (IP Interface in ip trunk mode)

TSCs on the ISDN-PRI

D-Channel

TCP Packet (DCS signaling only)

TCP Packet (C-LAN)

Interface

R8 — H.323

trunk

(MedPro

mode)

RTP Packet (IP Interface in medpro mode)

TCP Packet (C-LAN)

For DCS+, X.25, and ppp connection types, the signaling and voice data are sent together over tie-trunk facilities as TDM-multiplexed frames. The DCS signaling data is sent as packets over a permanent virtual circuit (PVC) on tie-trunk facilities.

For C-LAN Ethernet connections, the signaling and voice data are sent together over tie-trunk facilities as TDM-multiplexed frames. The DCS signalin g da ta is sent as TCP datagrams over an IP network through the C-LAN.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

DEFINITY Switch Connectivity

1 Networking Overview

For IP Trunk connections, the voice data is sent over IP facilities as RTP datagrams

using the IP Interface assembly (TN802 or TN802B) — each packet can potentially take a different route through the network. The call and DCS signaling data are sent as datagram packets over an IP network using the C-LAN interface. The R7 type of IP trunk (IP Interface operating in ip trunk mode) can also use tie-trunk PVC facilities for the DCS signaling.

Release 8 Hardware Requirements

For the three DEFINITY ECS switch models — csi, si, and r — Release 8 IP trunking (H.323) and IP Softph one connections require at least one IP Interface (TN802B) circuit pack and at least one C-LAN (TN799B) circuit pack. DEFINITY One requires only the IP Interface circuit pack.

IP Interface The IP Interface assembly (J58890MA-1 L30) is a 3-slot wide TN802B circuit pack

that provides voice processing over IP connections. The IP Interface assembly contains an NT processor, which is automatically administered by the DEFINITY software. The TN802B can be administered to operate in medpro mode for H.323 trunks and IP softphones, or in ip trunk mode for R7-type IP Trunk connections.

C-LAN The C-LAN circuit pack, TN799B, provides call setup, TSCs, QSIG, and DCS

signaling over IP connections. Note: The TN799B must be used to handle call signaling for the TN802B in

MedPro mode. However , the previous vers ion of C-LAN (TN799) can be used for call signaling with the TN802 or the TN802B operating in IP Trunk mode. The TN7 99 can also be u sed for DCS si gnaling con nections on a switch that is using the TN802B in MedPro mode, as long as there are TN799Bs to handle the call signaling for the TN802B.

Hardware Requirements for Upgrades from Pre-R7 Switches

DEFINITY release 7 introduced several hardware changes that are also required for release 8. This section summarizes the hardware changes needed for pre-R7 switches upgrading to R8 for each switch model and each type of non-H.323 connectivity.

R8r model The following table shows the hardware required for an upgrade to an R8r.

Connection Type Hardware Required

BX.25 (Existing systems only)

TCP/IP (ethernet and ppp)

ISDN-PRI No hardware changes required

PGATE (TN577)

C-LAN (TN799B)

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

DEFINITY Switch Connectivity 1 Networking Overview

R8si model The following table shows the hardware required for an upgrade to an R8si.

Connection Type Hardware Required

BX.25 (Existing systems only)

TCP/IP (ethernet and ppp)

ISDN-PRI

• PI (TN765)

• NetPkt (TN794) — replac es the NetCon (TN777B) and the

PACCON (TN778) circuit packs

•

Upgraded processor (TN790B)

• In duplicated systems, a second NetPkt Control

Assembly and a new DUPINT (TN792)

• C-LAN (TN799B)

• NetPkt (TN794) — replac es the NetCon (TN777B) and the

PACCON (TN778) circuit packs

•

Upgraded processor (TN790B)

• In duplicated systems, a second NetPkt Control

Assembly and a new DUPINT (TN792)

• Expansion Interface (TN570) if there is an EPN and

there are packet-based applications (such as TCP/IP over the C-LAN or ISDN-PRI over the TN464). The TN776 EI can be used only when the switch has no packet-based applications.

• NetPkt (TN794) — replac es the NetCon (TN777B) and the

PACCON (TN778) circuit packs

•

Upgraded processor (TN790B)

• In duplicated systems, a second NetPkt Control

Assembly and a new DUPINT (TN792)

• Expansion Interface (TN570) if there is an EPN.

ISDN-PRI capabilities formerly provided by the PI and PACCON circuit packs are now provided by the NetPkt. Note that you do not need to replace the TN767 with the TN464 since NetPkt supports D-channel signaling over the TDM bus.

R8csi model The following table shows the hardware required for an upgrade to an R8csi.

Connection Ty pe Hardware Required

BX.25 (Existing systems

The csi model does not support BX.25 connectivity.

only) TCP/IP

(ethernet and ppp)

ISDN-PRI

• C-LAN (TN799B)

• Upgraded processor (TN798B)

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

DEFINITY Switch Connectivity

1 Networking Overview

DEFINITY Connection types and capacities

This subsection gives an overview of the types of connections that can be set up with DEFINITY switch es and adjuncts and capacities for some connectivity parameters.

T ype s of connecti ons This table lists the types of connections possible with each DEFINITY model and

adjunct.

DEFINITY ECS R8 Model Connection Type Endpoint

Ethernet DCS, CMS, Intuity

AUDIX

Synchronous PPP DCS

R8csi

ISDN-PRI DCS+ H.323 Trunk DCS+ Ethernet DCS, CMS, Intuity

AUDIX

Synchronous PPP DCS

R8si

ISDN-PRI DCS+ BX.25 DCS, CMS, Intuity

DEFINITY AUDIX

AUDIX,

H.323 Trunk DCS+ Ethernet DCS, CMS, Intuity

AUDIX

Synchronous PPP DCS

R8r

ISDN-PRI DCS+ BX.25 DCS, CMS, Intuity

DEFINITY AUDIX

AUDIX,

H.323 Trunk DCS+

If an R8 switch is connected to two endpoints by diffe rent co nnection types , it acts as a gateway (protocol converter) between the endpoints.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

DEFINITY Switch Connectivity 1 Networking Overview

DEFINITY Capacities The following table shows maxi mum allowable values and ranges for several

connectivity parameters for DEFINITY ECS Release 8. Note that some or all maxima may not be achievable, depending on specific switch/traffic configurations.

csi si r

Circuit Packs

2 C-LAN X IP-Interface (medpro)

10 C-LAN 1 NetPkt 2 PI 14 IP-Interface (medpro)

10 C-LAN 4 PGATE 46 IP-Interface (medpro)

Audio Streams per IP-Interface

†

board H.323 IP Trunks

31 for G711 codec 22 for compression codecs

300 300 1000

+ IP Stations Processor

Channels:

X.25

1–128

1–64 1–256

1–128 1–384

ethernet/ppp

Interface Channels (listen ports):

X.25

ethernet/pppna5000–64,500

ISDN-TSC

na 128 256

1–64 5000–64,500

Gateway Channels Links per System 25 25 33 Links per Circuit

Pack:

PGATE

C-LAN

na na 1 ethernet, 16 ppp

4 na 1 ethernet, 16 ppp

na 4 1 ethernet , 16 ppp

IP Routes 270 400 650 Hop Channels

na 128 256

(X.25 only)

* Circuit pack abbreviations:

C-LAN: Control LAN (TN799B) NetPkt: Network Control/Packet Interface (TN794) PI: Processor Interface (TN765; used only for X.25 connections retained from pre-R7 systems) PGATE: Packet Gateway (TN577) IP-Interface: Used in the Medpro mode (TN802B)

† The n umber of aud io streams pe r bo ard i s 2 2 i f o nly on e c all us es a co mp ression c odec, ev en i f a ll

other calls use the G711.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

IP Softphones

1 Networking Overview

IP Softphones

This book focuses on administration for the trunk side of the DEFINITY IP Solutions offer. The administration of the line side (IP Softphones) is covered in DEFIN IT Y ECS R8 Administrator’s Guide, 555-233-506. For completeness, a brief checklist of IP Softphone administration is presented here.

For R8, there are two main types of DEFINITY IP Softphone applications — the telecommuter application and the road-warrior application. The CentreVu IP Agent is a variation of the telecommuter application.

Telecommuter application

Road-warrior application

The telecommuter application uses two connections to the DEFINITY system: a connection to the PC over the IP network and a connection to the telephone over the PSTN. The user places and receives calls with the DEFINITY IP Softphone interface running on a PC and uses the telephone handset to speak and listen.

To administer a telecommuter application, you must complete these steps:

1 Ve rify that the DEFINITY system is enabled for IP Softphone use. On the System

Parameters Customer Options screen, verify that:

~ Maximum H.323 Stations is > 0 ~ Maximum IP Softphones is > 0 ~ IP Stations is y

2 Add a DCP station (or change an existing DCP station) using the Station screen:

~ Type [enter the phone model you wish to use, such as 6408D] ~ Port: x if virtual, or the port number of an existing phone ~ Security Code: [enter the user’s password] ~ IP Softphone: y ~ Go to page 2; Service L ink Mode: as-needed

3 Install the IP Softphone software on the user’s PC

The road-warrior application uses two separate software applications run ning on a PC that is connected to a DEFINITY system over an IP network. The single network connection carries two channels: one for call control signaling and one for voice. DEFINITY IP Softphone software handles the call signaling and an H.323 V2-compliant audio app lication (s uch as Microsof t



NetMeeting) handles the voice

communications. To administer a road-warrior application, you must complete these steps:

1 Ve rify that the DEFINITY system is enabled for IP Softphone use. On the System

Parameters Customer Options screen, verify that:

~ Maximum H.323 Stations is > 0 ~ Maximum IP Softphones is > 0 ~ IP Stations is y

2 On the DEFINITY system, add an H.323 station using the Station screen:

~ Type H.322 ~ Port: x

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

IP Softphones 1 Networking Overv iew

3 Add a DCP station (or change an existing DCP station) using the Station screen:

~ Type [enter the phone model you wish to use, such as 6408D] ~ Port: x if virtual, or the port number of an existing phone ~ Security Code: [enter the user’s password] ~ Media Complex Ext: [enter the extension of the H.323 station from the

previous step]

~ IP Softphone: y ~ Go to page 2; Service L ink Mode: as-needed

4 Install the IP Softphone software on the user’s PC 5 Install an H.323 V2-compliant audio application (such as Microsoft NetMeeting)

on the user’s PC

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

IP Addressing

This section describes IP addressing, subnetting, and routing.

Physical Addressing

The Address Resolution Protocol (ARP) softw are o n the C-LAN circuit pack relates the 32-bit logical IP address, which is configured in software, with the 48-bit physical address of the C-LAN circuit pack, which is burned into the board at the factory. The C-LAN board has an ARP table that associates the IP addresses with the hardware addresses, which are used to route messages across the network. Each C-LAN board has one physical address and up to 17 assigned IP addresses (one for each port).

Logical Addressing

An IP address is a software-defined 32-bit binary number that identifies a network

node. The IP address has two main parts -- the first n bits specify a “network ID” and the remaining 32 – n bits specify a “host ID.”

1 Networking Overview

Format

Dotted Decimal notation

Class

Type

The 32-bit binary IP address is what the computer understands. For human use, the address is typically expressed in dotted decimal notation — the 32 bits are grouped into four 8-bit octets (bytes) and converted to decimal numbers separated by decimal points, as in the example below.

Octet 1

11000010

Network ID Host ID

Octet 2

00001101

Octet 3

11011011

32 – n

Octet 4

00000111

194 . 13 . 219 . 7

The eight binary bits in each octet can be combined to represent decimal numbers ranging from 0 to 255.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

IP Addressing 1 Networki ng Overv iew

Conversion between binary and decimal

Conversion from binary to decimal notation is accom plished b y adding the po wers of

2 corresponding to the 1’s positions in each byte:

26 = 6425 = 3224 = 1623 =822 =421 =220 =

128

194 =11000010 13 =00001101 219 =11011011

7 =00000111

IP Address Classes The IP address space (2

groups, Classes A–E, to accommodate the need for different network sizes. Each class has a different allocation of bits between the network and host IDs. The classes are identified by a fixed pattern of leading bits.

In Class A addresses, the first (leftmost) bit is always 0. So Clas s A IP addresses have 7 bits to define network IDs; 7 bits can define a total of 128 (0-->127) Class A networks. The remaining 24 bits of a Class A IP address are used to define host IDs. So for each of the 126 networks, there are 2

The following table shows how IP addresses are the allocated among the five classes.

Octet 1 Octet 2

or about 4.3 billion addresses) has been divided into five

or 16,777,216 possible hosts.

Octet 3

Octet 4

Class A

50%

Class B

25%

Class C

12.5%

Class D

6.5%

Class E

6.5%

Network ID Host ID

1 0

1 1 0

1 1 1 0

1 1 1 1

Network ID Host ID

Reserved for Multicast addresses

Reserved for future use

Address classes A, B, and C cover 87.5% of the address space. These addresses are assigned by the ISP or the Internet Assigned Number Authority (IANA) to organizations for their exclusive use. The remaining 12.5% of addresses, designated classes D and E, are reserved for special purposes.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

IP Addressing

1 Networking Overview

The IANA assigns a network address to an organization and a network administrator in the organization assigns the Host IDs associated with that Network ID to nodes

within the organization’s network. The following table shows the ranges of network and host IDs, and the total number

of IP addresses (# network IDs times # host IDs), for each class.

Network ID Range Host ID Range Total IP

Addresses

Class A 7 bits

126 Networks:

1 to 126

24 bits

16.8 Million Hosts per network:

2.1 Billion 50%

0.0.1 to 255.255.254

Class B 14 bits,

16,382 Networks:

128.0 to 191.255

Class C 21 bits,

2.1 Million Networks:

192.0.0 to 233.255.255

Classes D&E

16 bits 65,534 Hosts per network

0.1 to 255.254

8 bits 254 Hosts per network:

1 to 254

1.1 Billion 25%

0.5 Billion

12.5%

0.5 Billion

12.5%

You can tell the class of an IP address by the first octet. For example, 191.221.30.101 is a Class B address and 192.221.30.101 is a Class C address.

Private IP Address Addresses on the Internet need to be unique to avoid ambiguity in message routing

over the Internet. To insure uniqueness, the Internet Assigned Number Authority (IANA) controls the use of IP addresses. Organizations that maintain private networks that never communicate with the Internet can use arbitrary IP addresses as long as they are unique within the private network. To help prevent the duplication of IP addresses on the Internet, the IANA has reserved the following ranges of IP addresses for private networks:

1 Class A networks: 16.6 Million addresses: 10.0.0.0 --> 10.255.255.255 16 Class B networks: 1 Million addresses: 172.16.0.0 --> 172.31.255.255 256 Class C networks: 65,000 addresses:192.168.0.0 --> 192.168.255.255 These IP addresses can be used repeatedly in separate private networks, which are not

connected to the Internet. Routing tables prohibit the propagation of these addresses over the Internet. (See RFC 1918). All other IP addresses are unique and must be assigned by the IANA or ISP.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

IP Addressing 1 Networki ng Overv iew

Subnetting

Subnetting is the grouping of IP addresses associated with a netwo r k ID into two or more subnetworks. The subnets of a network ID are visible only within the organization that owns the network ID; Internet routers route messages based on the network ID and the routers within the private organization differentiate between the individua l subnets.

Reasons for subnetting Subnetting is desirable because it enables a more efficient allocation and management

of IP addresses. The three-class hierarchy of IP addresses results in an inefficient allocation of

addresses in many cases because addresses are assigned and managed in blocks by network ID. For example, a company that needs 10,000 IP addresses in each of two locations might be assigned two Class B network IDs, each of which provides 65,534 IP addresses. Even though one Class B network ID would provide more than enough addresses for both locations, having a separate network ID for each location is easier to manage. If the company uses only 20,000 of these addresses, about 100,000 go unused.

In this case, subnetting would enable the company to use one Clas s B network ID and subdivide the addresses into two subnets, one for each location. Each subnet would

have a unique “extended network ID” that would enable them to be managed as if they had unique network IDs.

How subnets are created

Typically, organizations need to manage IP addresses in separate groups based on several criteria in addition to location:

• different types of LANs

• different server applications

• different work projects

• security

The grouping of IP addresses provided by the three-Class structure does not allow nearly enough flexibility to meet the needs of most organizations. Subnetting allows the N IP addresses associated with a network ID to be divided into as few as 2 groups, each with N/2 addresses, or into as many as N/2 groups, each with 2 addresses, if desired.

RFC 950 defines a standard procedure to divide a Class A, B, or C network ID into subnets. The subnetting adds a third level of hierarchy to the two-level hierarchy of

the Class A, B, and C network ID number. An “extended network prefix” is formed by using two or more bits of the Host ID as a subnet number, and appending this subnet number to the network ID.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

IP Addressing

1 Networking Overview

Two-level classful hierarchy

Class

Type

Network ID Host ID

Three-level subnet hierarchy

Class

Type

Network ID Subnet ID Host ID

Extended Network Prefix

Subnet mask

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 . . . 1 0 0 0 0 0 . . . 0

The extended network prefix is then treated as a normal network ID. The remaining host ID bits define the host IDs within each subnet. For example, a block of IP

addresses could be subdivided into four subnets by using 2 host bits to “extend” the network ID. Now there are 4 times as many (extended) networks and 1/4 as many hosts per network.

Note: In adding up the number of network and host IDs, certain addresses

cannot be counted. In general, addresses with all ones or all zeros in either the network portion or the host portion of the address are not usable. These are reserved for special uses, such as broadcasting or loopback.

Subnet Masks Routing protocols use a subnet mask to determine the boundary between the extended

network ID and the host ID in an IP address. The subnet mask is a 32-bit binary number consisting of a string of contiguous 1’s followed by a string of contiguous 0’s. The 1’s part corresponds to the extended network prefix and the 0’s part corresponds to the host ID of the address.

Each of the three classes of addresses has a defau lt subnet m ask that s pecifies the end of the 1st, 2nd, and 3rd octet as the boundary between the extended network prefix and the host ID. The default subnet mask in each case means “no subnetting.”

Default Subnet Mask

Class A 11111111.00000000.00000000.00000000

255.0.0.0

Class B 11111111.11111111.00000000.00000000

255.255.0.0

Class C 11111111.11111111.11111111.00000000

255.255.255.0

In addition to the default subnet masks, which divide the network and host IDs at the octet boundaries in the IP address, subnets can be formed by using 2 or more bits from the host octets to define the subnet ID.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

IP Addressing 1 Networki ng Overv iew

Class-C subnets The following table shows that Class-C IP addresses can have 5 s ubnetting schemes,

each with a different number of subnets per network. The first and last subnet, form ed by using 1 and 7 bits respectively, are unusable because they result in either the subnet ID or the host ID having all zeros or all ones.

No. Subnet bits

No. of Usable Subnets per NW

No. of Hosts per Subnet

No. of Usable IP Addresses

Binary Subnet ID

(4th Octet)

Decimal Subnet ID

Class C Subnet Masks

1 0 126 0 10000000 128 255.255.255.128 2 2 62 124 11000000 192 255.255.255.192 3 6 30 180 11100000 224 255.255.255.224 4 14 14 196 11110000 240 225.225.225.240 5 30 6 180 11111000 248 255.255.255.248 6 62 2 124 11111100 252 255.255.255.252 7 126 0 0 11111110 254 255.255.255.254

3-bit subnets

As an example, the third row of the table shows the results of using 3 bits for the

subnet ID. Three bits are “borrowed” from the host ID leaving 5 bits for the host IDs.

The number of subnets that can be defined with three bits is 2 011, 100, 101, 110, 111

). Of these, only 6 are usable (all ones and all zeros are not

usable). The remaining 5 bits are used for the host IDs. Of these, 2

= 8 (000, 001, 010,

– 2 = 30 are usable. As shown in columns 2–4 (row 3), by using 3 bits for subnetting, a Class C network can be divided into 6 subnets with 30 host IDs in each subnet for a total of 6 X 30 = 180 usable IP addresses.

Subnet mask

The subnet mask is defined as follows. The subnet bits “borrowed” from the host ID are the highest-order bits in the octet of the host ID. The 5th and 6th columns of the table show the binary and decimal subnet IDs, formed by using the subnet bits as the highest-order bits in an octet. For example, in the third row of the table, the binary bit pattern is 11100000, which is decimal 224. This is the highest number that can be formed with the 3 high-order bits in the octet. The subnet mask is formed by putting this number in the 4th octet of the default subnet mask (shown in the last column of the table).

The mask, 255.255.255.224, corresponds to a bit pattern of 27 ones followed by 5 zeros. This mask would be used to check that two IP addresses are on the same or different subnets by comparing the first 27 binary digits of the two addresses. If the first 27 binary digits are the same, the two addresses are on the same subnet.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

IP Addressing

1 Networking Overview

Example

To continue the example using a 3-bit subnet ID, assume a Class C network ID of

192.168.50.xxx. This network ID can provide 254 usable IP addresses, all on the

same network — from 192.168.50.1 to 192.168.50.254. If we divide this network into 3-bit subnets, we will have 6 usable subnets with 30 usable IP addresses in each subnet. Note that we have lost 74 usable IP addresses in the process because we had to discard the all-ones and all-zeros subnet IDs (62 addresses) and host IDs (12 addresses). There is always a loss of usable IP addresses with subnetting.

The following table shows the subnet boundaries for the six subnets formed with 3 bits. The boundaries are the numbers formed by using all combinations of 3 bits as the highest-order bits in an octet (Columns 1 and 2) and then using these numbers in the 4th octet for the host IDs.

Binary Subnet Boundaries

Decimal Subnet Boundaries

Range of usable IP Addresses in the Subnet

(for 3 bits)

00000000 0 not usable 00100000 32 192.168.50.33 to

192.168.50.62

01000000 64 192.168.50.65 to

192.168.50.94

01100000 96 192.168.50.97 to

192.168.50.126

10000000 128 192.168.50.129 to

192.168.50.158

10100000 160 192.168.50.161 to

192.168.50.190

11000000 192 192.168.50.193 to

192.168.50.222

11100000 224 not usable

For example, the IP addresses 192.168.50.75 and 192.168.50.91 are on the same subnet but 192.168.50.100 is on a different subnet. This is illustrated in the following diagram where the subnet mask, 255.255.255.244 is used to compare the first 27 binary digits or each address.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

IP Addressing 1 Networki ng Overv iew

192 168 50 75

11000000 10101000 00110010 0100101 1

192 168 50 91

11000000 10101000 00110010 0101 1011

192 168 50 100

11000000 10101000 00110010 01100100

Class-A and Class-B subnets

Subnet mask

255 255 255 224

11111111 11111111 11111111 11100000

27 digits

The other four possible subnetting schemes for Class C addresses, using 2, 4, 5, and 6 subnet bits, are formed in the same way. Which of the 5 subnetting schemes to use depends on the requirements for the number of subnets and the number of hosts per subnet.

For Class A and Class B IP addresses, subnets can be formed in the same way as for Class C addresses. The only difference is that many more subnets per network can be formed. For Class B networks, subnets can be formed using fr om 2 to 14 bits from the 3rd and 4th octets. For Class A networks, subnets can be formed using from 2 to 22 bits from the 2nd, 3rd and 4th octets.

The Subnet Mask field on the ppp Data Module screen (used for p pp connections) and on the IP Interfaces screen (used for ethernet co nnections) enables the s pecification of a subnet for the IP address.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

IP Addressing

Valid subnet masks The valid subnets for each Class of address are:

1 Networking Overview

Class A (default 255.0.0.0)

Class B: (default 255.255.0.0)

Class C (default 255.255.255.0)

255.192.0.0 255.255.192.0 255.255.255.192

255.224.0.0 255.255.224.0 255.255.255.224

255.240.0.0 255.255.240.0 255.255.255.240

255.248.0.0 255.255.248.0 255.255.255.248

255.252.0.0 255.255.252.0 255.255.255.252

255.254.0.0 255.255.254.0

255.255.0.0 255.255.255.0

255.255.128.0 255.255.255.128

255.255.192.0 255.255.255.192

255.255.224.0 255.255.255.224

255.255.240.0 255.255.255.240

255.255.248.0 255.255.255.248

255.255.252.0 255.255.255.252

255.255.254.0

255.255.255.0

255.255.255.128

255.255.255.192

255.255.255.224

255.255.255.240

255.255.255.248

255.255.255.252

Notice that all 5 valid Class C subnet masks can also be valid Class B or Class A subnet masks, and all 13 valid Class B subn et mas ks can also be valid Class A subnet masks.

For example, classes. It allows 6 (2

255.255.255.224

2) subnetworks for Class C addresses, 2046 (2

−

subnetworks for Class B addresses and 524,286 (2 addresses. Each of these subnetworks can have 30 (2

is a valid subnet mask for all three address

2)subnetworks for Class A

−

2) hosts.

−

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

IP Addressing 1 Networki ng Overv iew

Default Gateway

On LANs that connect to other networks or subnetworks, it is convenient to define a default gateway node. The default gateway node is usually a router that is connected to 2 or more different (sub)networks. It could also be a C-LAN ethernet port that is connected to other C-LANs on the same switch. Any packets addressed to a different (sub)network, and for which no explicit IP route is defined, are sent to the default gateway node. The default gateway node is either directly conn ected to the addressed node or knows of another router that knows how to get to the packet address.

A default gateway can be assigned to a node (C-LAN port or IP In terface por t) on the IP Interfaces screen. If you do not assi gn a defau lt gatewa y to a n ode, an ex plicit hos t IP route must be defined to enable communications to any node on a different (sub)network.

You can also assign a default gateway by setting up an IP route with the default node as the destination and the router (or C-LAN) as the gateway. The default node is a display-only entry on the Node Names screen with IP address 0.0.0.0. It acts as a

variable that takes on unknown addresses as values. When the “default” IP route is set up, any address not know by C-LAN is substituted for the default address in the default IP route, which uses the router as the “default” gateway.

SECURITY ALERT:

A default gateway could allow unauthorized access to your network if it is not properly administered and maintained.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

IP Addressing

When to use IP routes

You need to define IP routes only in special cases when default gateways are not defined or when you want to limit communication between nodes. This section describes the network configurations that require explicit IP routes.

The following table summarizes when you would use IP routes:

1 Networking Overview

Connection

When IP Routes are Needed:

Type

The endpoints are on different subnets and no default gateway is defined on the IP Interfaces screen for the local node, and

• You want the local node to co mmunicate with only

Ethernet

the specified node on a remote subnet (this is a host route type), or

• You want the local node to comm unicate with any

node a remote network but not wi th nodes on other networks (this is a network route type)

PPP

There are one or more intermediate nodes between endpoints.

The host and network route types are not specified directly. The system implies the type from the specified destination IP address and its associated subnet mask. The route type is displayed on the IP Routing screen for the display, list, and modify commands.

The endpoint nodes are on the same subnet if the following three conditions are met:

• the endpoints are on the same physical subnetwork

• the Subnet Mask field is assigned the same value on the IP Interface

screens for the two endpoint nodes

• the network + subnet portions of the IP addresses (as determined by the

subnet mask) are the same

See Subnetting (page 16) for more information about subnet masks.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

IP Addressing 1 Networki ng Overv iew

IP Routing Screen The following diagram shows the IP Routing screen.

display ip-route 1 Page 1 of 1

Route Number: 1 Destination Node: clan-a2_ ___ Gateway: router-1 C-LAN Board: 1b01

Metric: 0

Route Type: host

IP ROUTING

To set up an IP route, enter the node names for the destination and the gateway, and enter the slot location of the C-LAN on the local switch. The destination and gateway node names and their associated IP addresses must be specified on the Node Names screen.

The Route Type is a display-only field that appears on the screen for the display, list, and change ip-route commands. This field indicates whether the route is a host or network route. It is a host route if the destination address (associated with the Destination Node on the Node Names sc reen) is th e addre ss of a sing l e hos t, or nod e . It is a network route if the destination address is the address of a network, not a single node.

An IP address for a network has the network ID in the network portion and 0 in the host portion. For example, 192.168.1.0 is the network addr ess for the 192.168.1 network.

When a network is subnetted, and you want to set up a network IP route to a subnetwork, the IP address of the subnetwork is the first address in that subnetwork,

which has all 0’s for the host portion of the address. For example, the subnet mask formed by using 2 bits of the host portion of a Class C address is 255.255.255.192 (1100000 = 192). For the 192.168.1 network, this subnet mask creates 2 usable subnetworks whose IP addres ses ar e 192 .168.1 .64 (01 00000 = 64) and 192.16 8.1. 128 (1000000 = 128), with 62 usable host addresses in each subnetwork.

If you wanted the local C-LAN node to be able to communicate with the nodes on the

192.168.1.64 subnetwork and not with others, you could do the following:

1 Leave blank the Gateway Address field on the IP Interfaces screen. 2 Enter a node name — for example, “subnet-1” — and the IP address,

192.168.1.64, on the Node Names screen.

3 Set up an IP route with “subnet-1” in the Destination Node field.

See the description of the subnet mask in Subnetting (page 16) for more information on subnet addresses. See IP Routing (page 251) in Appendix A for a description of the Metric field.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

IP Addressing

IP Route Examples PPP Connections

The diagram below shows three switches in a DCS network with PPP signaling connections between switches A & B and between switches A & C. All nodes in this diagram are C-LAN ports. PPP data modules are administered between nodes 1 & 2 on switches A & B, and between nodes 3 & 4 on switches A & C. With these connections, switch A can communicate with switches B and C without using the IP Routing screen to administer explicit host IP routes. However, s witches B and C need host IP routes to communicate with each other because they are not directly connected.

1 Networking Overview

SW B

DS1

DCS Signaling over PPP

C-LAN

SW C

DS1

C-LAN

SW A

DS1

C-LAN

ppp

2 3

The IP routes needed between nodes fo r this example ar e listed in the following table. The Destination Node and Gateway Node columns in the table show the nodes that you would enter on the IP Routing screen to administer a host IP route. On the IP Routing screen, you would enter the node names assigned on the Node Names screen for these nodes.

Gateway

Node

Route

Type

Comments

Switch

Node

Connections

Destination

Node

host IP route needed

B 1 —> 4 4 2

because there is an intermediate node between nodes 1 & 4.

host IP route needed

C 4 —> 1 1 3

because there is an intermediate node between nodes 4 & 1.

Note: (1) The PPP data modules on switches B and C for the connections to A

must be enabled before the IP routes can be administered.

Note: (2) Nodes 2 and 3 in this example are two ports on the same C-LAN

board. Messages from node 1 destined for node 4 arrive at node 2; the C-LAN ARP software routes the messages to node 4 through node 3.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

IP Addressing 1 Networki ng Overv iew

PPP with Ethernet Connections

The diagram below shows two interconnected (sub)networks. There are three switches in a DCS network with a ppp signaling connection between switches A & B and an ethernet signaling connection between switch A and the adjunct. Switches A & B and the adjunct are on one (sub)network and switch C is on another (sub)network.

Switch A acts as a gateway to convert between the two signaling protocols. PPP data modules are administered between nodes 1 & 3 on switches A & B and ethernet data modules are administered on switches A & C for the C-LAN ethernet port interfaces to their LANs. With these connections, switch A can communicate with switch B and with the adjunct without using the IP Routing screen to administer explicit IP routes.

Normally, node 5 would be defined as the default gateway for node 2 on the IP Interfaces screen, which would enable switch A to communicate with switch C without an explicit IP route defined. However, if node 5 is not assigned as the default gateway for node 2, switch A needs an IP route to communicate with switch C because these switches are on different (sub)networks. Similarly, node 6 would normally be defined as the default gateway for node 7; if not, switch C needs an IP route to communicate with switch A.

Also, switch B needs an IP route to communicate with switch C because B is connected to A via ppp and there are intermediate nodes between B & C.

SW A

DS1

C-LAN

SW B

DS1

DCS Signaling over PPP

DCS Signaling over Ethernet/ Internet

C-LAN

SW C

DS1 C-LAN

PPP

Ethernet

LAN

Network 1

Wan or Intranet

Network 2

LAN

Ethernet

Adjunct

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

IP Addressing

1 Networking Overview

The following table shows the IP routes needed if nodes 5 and 6 are not defined as default gateways for nodes 2 and 7, respectively.

IP Route

Destination

Node

Switch

Node

Connections

A 2 —> 7 7 5

3 —> 4 4 1

3 —> 7 7 1

7 —> 4 4 6

IP Route Gateway

Node

Comments

IP route needed because nodes 2 & 7 are on different subnets and the Gateway Address field for the node-2 C-LAN is blank on the IP Interfaces screen.

IP route needed because 3 is connected to 1 via ppp and there are intermediate nodes between 3 & 4. The data module for the ppp connection between nodes 3 and 1 must be enabled before administering this route.

IP route needed to because 3 is connected to 1 via ppp and there are intermediate nodes between 3 & 7. The data module for the ppp connection between nodes 3 and 1 must be enabled before administering this route.

IP route needed because nodes 4 & 7 are on different subnets and the Gateway Address field for the node-7 C-LAN is blank on the IP Interfaces screen.

7 —> 2 2 6

7 —> 3 3 2

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

IP route needed because nodes 2 & 7 are on different subnets and the Gateway Address field for the node-7 C-LAN is blank on the IP Interfaces screen.

IP route needed because nodes 3 & 7 are on different subnets. This route depends on route 7—>2.

Note: this route would not be needed if node 6 is administered for proxy ARP to act as a proxy agent for node 3.

IP Addressing 1 Networki ng Overv iew

Ethernet-only Connections

The diagram below shows three interconnected (sub)networks. There are three switches in a DCS network with ethernet signaling connections between them. Switches A & B and the adjunct are on one (sub)network and switch C is on another (sub)network. Nodes 1, 2, and 6 are C-LAN ports. Node 3 is the adjunct interface port to the LAN. Nodes 4, 5, and 7 are interfaces to the WAN/Internet cloud and have IP addresses that are on different (sub)networks. An ethernet data module and IP Interface is administered for the C-LAN ethernet port on each switch.

Switches A and B can communicate with each other and with the adjunct without using the IP Routing screen to explicitly administer host IP routes. Normally, node 4 would be defined as the Gateway Address for node 1 on the IP Interfaces screen, which would enable switch A to communicate with switch C without an explicit host IP route defined. However, if node 4 is not assigned as the Gateway Addres s for node 1, switch A needs an IP route to communicate with switch C because these switches are on different (sub)networks. Similarly, node 5 would normally be defined as the default gateway for node 6; if not, switch C needs an IP route to communicate with switch A.

In this configuration, network IP routes could be used alone, or in combination with host IP routes, to tailor access among n odes. Fo r example, if you wanted node 1 to be able to communicate with any node on ( sub)networks 2 and 3, you would d efine node 4 as the Gateway Address for node 1. Then you would no t need any IP routes defined for node 1. If you wanted node 1 to be able to communicate with all nodes on (sub)network 3 but none on (sub)network 2, y o u would define a network IP route to (sub)network 3 (and not assign node 4 as the Gateway Address for node 1). Then node 1 could communicate with any no de on (su b)net work 3 witho ut defin ing ho st IP routes to them.

SW A

DS1 C-LAN

SW B

DS1

C-LAN

DCS Signaling over Ethernet/ Internet

SW C

DS1

Network 2

192.168.2.0

LAN

C-LAN

Network 1

192.168.1.0

LAN

Router(s)

WAN

Adjunct

CID: 77730 555-233-504 — Issue 1 — April 2000

Network 3

192.168.3.0

Administration for Network Connectivity

LAN

IP Addressing

1 Networking Overview

The following table shows the IP routes needed if node 4 is not defined as the Gateway Address (on the IP Interfaces screen) for nodes 1, 2, and 3 but node 5 is defined as the Gateway Address for node 6.

Switch

Node

Connec-

tions

IP Route

Destination

Node

IP Route Gateway

Node

Route

Type

1 —> 6 6 4 host

1—>

network 3

network-3 4 network

B2 —> 6 6 4host

Comments

IP route needed because nodes 1 & 6 are on different subnets and no Gateway Address is specified for the node-1 C-LAN on the IP Interfaces screen.

This route enables node 1 to communicate with any node on Network 3. The node name network-3 must be associated with the IP address 192.168.3.0 on the Node Names screen.

IP route needed because nodes 2 & 6 are on different subnets and no Gateway Address is specified for the node-1 C-LAN on the IP Interfaces screen.

No IP routes are needed on Switch C because node 5 is defined as the Gateway Address for node 6.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

IP Addressing 1 Networki ng Overv iew

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

2 H.323 Trunks

This chapter describes how to set up and perform initial administration of IP Trunks between DEFINITY ECS switches and between DEFINITY and non-DEFINITY switches that support the H.323 V2 signaling protocols. The IP trunk connections described in this chapter use the TN802B circuit pack in the MEDPRO mode. See Appendix F for administration of trunk connections that use the TN802 or TN802B in the IP Trunk mode.

Overview

This section provides a summary of DEFINIY IP Solutions for DEFINITY ECS Release 8.2.

IP Solutions

DEFINITY ECS IP Solutions provide TCP/IP connectivity for two types of trunks and three types of IP

Softphones. On DEFINITY ECS,

TN799B C-LAN for signaling. The TN802B IP Interface includes a Windows NT server that resides on the TN802B circuit pack inside the DEFINITY ECS.

IP Solutions use the TN802B IP Interface assembly f or voice processing and the

The TN802B IP Interface, introduced in Release 8, can be administered to operates in either the MedPro mode (for H.323-compliant ISDN PRI-equivalent trunk connections) or IP Trunk mode (for DS1-emulation connections). It will typically be used in the MedPro mode. The IP Trunk mode is provided for compatibility with existing R7 IP Trunk connections.

The TN802 IP-Interface introduced in Release 7, which operates only in the IP Trunk mode, can be upgraded via firmware download to the TN802B.

The following table lists the IP Solutions configurations and the circuit packs and software used with each.

Circuit Pack Requirements Software

IP Solutions

R7 R8

H.323 Trunk –

Trunks

IP Trunk TN802

Road-warrior

application IP Softphones

* The IP Softphones should work with other audio applications that are fully H.323 v2-compliant.

DEFINITY IP Solutions was developed and tested with Microsoft NetMeeting.

Telecommuter

application

CentreVu IP Agent – TN799B DEFINITY IP Softphone

–

– TN799B DEFINITY IP Softphone

TN802B in medpro mod e with TN799B

TN802B in ip trunk mode with TN799B

TN802B in medpro mod e with TN799B

Requirements

–

DEFINITY IP Softphone, Microsoft NetMeeting

Administration for Network Connectivity

555-233-504 — Issue 1 — April 2000 CID: 77730

Overview 2 H.323 Trunks

IP-Connected Trunks

IP-connected trunks allow trunk groups to be defined as ISDN-PRI-equivalent tie lines between switches over an IP network.

Trunks usi ng IP connec t ivity provide cost-reduction and simplified management. Benefits include a reduction in long distance voice and fax expenses, facilitation of global communications, full-function network s with d ata an d v oice conv ergen ce, and network optimization by using the existing network resources.

H.323 Trunk The TN802B IP Interface in Medpro mode enables H.323 trunk service using IP

connectivity between two DEFINITY ECS systems. H.323 trunk groups can be configured as DEFINITY-specific tie trunks supporting ISDN trunk features such as DCS+ and QSIG, or as generic tie trunks permitting interconnection with other

vendors’ H.323 v2-compliant switches, or as direct-inward-dial (DID) type of “public” trunk providing access to the switch for unregistered users. A variety of signaling options can be chosen by the system administrator.

IP Trunk The IP Trunk mode (of the TN802B IP Interface) will typically be chosen for

interoperability with existing TN802 (as opposed to the TN802B) IP Interface circuit packs. IP Trunk mode can be used only between two DEFINITY switches. Each IP Interface circuit pack in IP Trunk mode provides a basic twelve-po rt package that can be expanded up to a total of 30 ports.

IP Softphones

DEFINITY IP Softphones operate on a PC equipped with Microsoft Windows 95/98/NT and with TCP/IP connectivity to DEFINITY ECS. DEFINITY IP Solutions supports three IP Softphone configurations:

• R o ad-warrior application of IP Softphone — a PC running the DEFINITY IP

Softphone application and an H.323v2 -com pliant audio application, with a single IP connection to a DEFINITY server.

• Telecommuter application of IP Softphone — a PC running the DEFINITY IP

Softphone application with an IP connection to the DEFINITY server, and a standard telephone with a separate PSTN connection to the DEFINITY server.

• CentreVu IP Agent — same as the Dual-Connection IP Softphone with the

addition of call-center agent features that enable agents to work at home.

The DEFINITY IP Softphone can also operate in a “native H.323” mode, which is a PC-based single phone with limited features.

Documentation on how to set up and use the IP Softphones is included on the CD-ROM containing the IP Softphone software. The documentation includes a Getting Started quick reference, an overview and troubleshooting document, and context-sensitive help integrated with the softphone software.

Procedures for administering the DEFINITY ECS server to support IP Softpho nes are given in DEFINITY ECS R8.2 Administrator’s Guide, 555-233-506.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

H.323 Trunk Administration

2 H.323 Trunks

H.323 Trunk Administration

This section describes the administration steps needed to setup H.323 trunks. The first subs ection covers the enabling administration that needs to be in place before the trunk administration can be done. The second subsection gives a summary of the H.323 trunk administration and the last subsection gives the detailed steps. The screens used for this administration are described in detail in Appendix A, Screens Reference.

Screen fields not mentioned here are administered as in previous releases.

Enabling Administration

Before you can administer an H.323 trunk, a few customer options and circuit pack parameters need to be properly set. In addition, there are some optional maintenance and IP parameters that can be administered. These enabling settings are summarized here.

Optional Features (System Parameters Customer Options)

Circuit Pack The C-LAN and IP Interface assembly circuit packs must be administered on the

The Optional Features screen must be administered by the init login. Open the screen with the change command (ch sys cu) and set the following fields:

page 1

•

G3 Version

•

Maximum H.323 Trunks

page 3

•

H.323 Trunk

•

ISDN-PRI?

= V8

= number purchased; must be greater than 0.

s? = y

= y

Circuit Pack screen. Open the Circuit Pack screen with the change command (ch ci) and enter the board codes in available port slots:

C-LAN

•

Code = TN799

• Sfx = B

• Name = C-LAN

IP Interface assembly — enter in a slot with at least two empty slot before it

•

Code = TN802

• Sfx = B

• Name = MAPD Board {entered automatically by system}

The two slots immediately before this slot are automatically populated as follows:

• Code = DSMAPD {displays automatically}

Change DSMAPD to MEDPRO {the IP Interface board defaults to the IP Trunk mode, which is specified by the DSMAPD in this field. Changing this field to

MEDPRO changes the board’s mode to MEDPRO}

• Sfx = {blank}

• Name = Reserved - IP {displays automatically}

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

H.323 Trunk Administration 2 H.323 Trunks

Maintenance-Related System Parameters

Four parameters on the Maintenance-Related System Parameters screen set threshold values for network performance:

page 4

• Roundtrip Propagation Delay (sec) High: 800_ Low: 400_

• Packet Loss (%) High: 40__ Low: 15__

• Ping Test Interval (sec): 20

• Pings per Measurement Interval: 10

These parameters have no effect unless the bypass function is activated on the Signaling Group screen. If the bypass function is activated for a signaling grou p, ongoing measurements of network activity co llected by the system ar e compared with these values. If the values of these parameters are exceeded by the current measurements, the bypass function terminates further use of the network path associated with the signaling group. The following actions are taken when thresholds are exceeded:

• existing calls are maintained

• incoming calls are allowed

• outgoing calls are blocked on this signaling group; if so administered, blocked

calls are diverted to alternate routes (either IP or circuits) as determined by the administered routing patterns

You can use the default values set for these p arameters , o r you ca n chan ge th em to fit the needs of your network. The Maintenance-Related System Parameters screen can be administered by the init, inads, or craft logins. Open the screen with the change command (ch sys ma).

IP Parameters The IP Media Parameters screen allows you to specify the type of codec used for

voice encoding and companding (compression/decompression). The main difference between codecs is in the compression algorithm used: some codecs compress the voice data more than others. A greater degree of compression results in lower bandwidth requirements on the network, but may also introduce transmission delays and lower voice quality.

The default codec is set for G711. The G711 provides the highest voice quality because it does the least amount of compression, but it uses the most bandwidth. The G711 default setting can be changed to one of four other codecs if the G711 does not meet your desired voice-quality/bandwidth tradeoff s pecification. Also, if the far -end switch is a not a DEFINTIY ECS, you may need to change the codec to match one that is supported by that switch.

The order in which the codecs are listed on this screen is the order of preference of usage. A trunk call between two DEFINITY switches will be set up to use the first common codec listed on the two IP Parameters screens.

NOTE: The codec ordering

must be the same

both ends of an H.323 trunk connection. The

order

not be the same, but the

of the listed codecs must be the same.

CID: 77730 555-233-504 — Issue 1 — April 2000

on DEFINITY switches at

set

of codecs listed need

Administration for Network Connectivity

H.323 Trunk Administration

You can also use the Audio IP port number range field to specify a block of port numbers to be used for audio connections. Then, if yo ur network is equipped with the appropriate data filtering devices, audio data can be segregated fr om other d ata traffic to improve quality of service.

Open the screen with the change command (ch ip-p) and set the following fields:

• Codec type = {enter as many of the following types as supported by this switch, in

the prefe rred order of usage — G711A, G 711Mu, G723-6.3k, G723- 5.3k, G.729A}. Refer to the following table of bandwidth requirements to decide which codecs to administer:

Codec Bandwidth Requirement

G711 A-law @ 64Kbps 117.6 Kbps G711 Mu-law @ 64Kbps 117.6 Kbps G723 @ 6.3Kbps 31.1 Kbps G723 @ 5.3Kbps 29.6 Kbps G729A @ 8Kbps 33.6 Kbps

• Audio IP port number range =

2 H.323 Trunks

UDP Port Range Min: 2048 Max: 65535

The G711 codecs use either an A-law or Mu-law companding algorithm. The Mu-law algorithm is used in the U.S. and Japan; the A-law is typically used in other countries.

Best Service Routing The call center Best Service Routing (BSR) feature can be implemented using H.323

trunks. You can use H.323 trunks for just the polling function or for both the polling and interflow functions. Since polling requires only a small amou nt of data exch ange, the additional network traffic is insignificant. However, the in terflo w f unc tion requires a significant amount of bandwidth to carry the voice data. Depending on the other uses of the LAN/WAN and its overall utilization rate, the voic e quality cou ld be degraded to unacceptable levels.

Lucent recommends that if H.323 trunks are used for BSR interflow, this traffic should be routed to a low-occupan cy or unshar ed LAN/WAN segment. Alternatively, you might want to route internal interflow traffic (which may have lower quality-of-service requirements) over H.323 trunks and route customer interflow traffic over circuit-switched tie trunks.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

H.323 Trunk Administration 2 H.323 Trunks

H.323 Trunk Administration — Task Summary

After the enabling administration is complete, you can administer the H.323 IP trunks. The screens and fields that need to be administered are listed below.

NOTE: This is only a list of screens and the fields that need to be administered. The values that need to be entered in these fields are described in the next section.

Node names A node name and IP address must be entered on the Node Names screen for each

C-LAN and IP Interface board on the local switch. For each far-end node that the H.323 trunks on the local switch will connect to, a node name and IP address must be entered for the far-end gatekeeper, which is a C-LAN board if the far-end is a DEFINITY switch. Enter values in these fields:

~ Node Name ~ IP Address

IP Interfaces Each DEFINITY switch in an IP network has one IP Interfaces screen. One line on

this screen must be administered for each C-LAN and each IP Interface board. Enter values in these fields:

~ Network regions are interconnected? ~ Enable ~ Type ~ Slot ~ Code ~ Sfx ~ Node Name ~ Subnet Mask ~ Default Gateway Address ~ Region

Ethernet Data Module A data module screen, type ethernet, must be administered for each C-LAN board on

the switch. Enter values in these fields:

~ Type ~ Port ~ Link ~ Name ~ Network uses 1’s for broadcast address?

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

H.323 Trunk Administration

Signaling Group Each H.323 trunk must be assigned to a signaling group. Enter values in these fields:

page 1

~ Group Type ~ Trunk Group for Channel Selection ~ Near-end Node Name ~ Near-end Listen Port ~ Far-end Node Name (Optional) ~ Far-end Listen Port (Optional ~ LRQ Required? ~ Calls Share IP Signaling Connection? ~ Bypass If IP Threshold Exceeded?

Page 2 — Administered NCA TSC Assignment

2 H.323 Trunks

NCA TSCs need to be administered only if this signaling group is to be used for DCS, AUDIX, MASI, or as Gateway. Administration of TSCs is the same as in previous releases.

Trunk Group Each H.323 trunk must be assigned to a trunk group, which is assigned to a signaling

group. Enter values in these fields:

page 1

~ Group Type ~ Carrier Medium ~ Service Type ~ Codeset to Send Display ~ TestCall ITC ~ TestCall BCC

page 2

~ Used for DCS? ~ PBX ID ~ DCS Signaling

page 4—trunk group members assignment

Port

~ Code ~ Name ~ Night ~ Sig Grp

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

H.323 Trunk Administration 2 H.323 Trunks

IP Media Parameters Each DEFINITY switch in an IP network has one IP Media Parameters screen. Use

this screen to enter:

~ the types of codecs (for audio processing) available on this switch ~ the preferred order of use of the codec types ~ the range of port numbers available for audio connections

Network Regions The Region field on the IP Interfaces screen allows you to set up segregated groups of

C-LAN and IP Interface (Medpro) resources. This feature can be used in a variety of ways. For example, you could u se regions to allocate s pecific C-LAN and IP I nterface boards to H.323 trunks and others to stations; or you could use regions to avoid multimedia traffic over low bandwidth or high-latency network links.

H.323 Trunk Administration — Task Detail

This section describes the tasks that need to be completed to administer an H.323 trunk. Sample values are used to populate the fields to show the relationships between the screens and fields.

Task 1 — Assign Node Names

This task assigns node names and IP addresses to each node in the network that this switch communicates with via IP connections. A Node Names screen must be administered on each DEFINITY switch in an IP network.

A node is defined as any of the following — a C-LAN ethernet or ppp port, a bridge

or router, a CMS ethernet port, or an Intuity AUDIX or other MSA network interface card. The AUDIX and MSA node name and IP address must be entered on page 1 of the screen. The data for all other node types must be entered on pages 2–6.

For H.323 connections, each MedPro ethernet port (IP interface) on the local switch only must also be assigned a node name and IP address on this form.

The node names and IP addresses in any network should be assigned in a logical and consistent manner from the point of view of the whole network. These names and addresses should be assigned in the planning stages of the network and should be available from the customer system administrator or from a Lucent representative.

Note: Enter node names for Intuity AUDIX and MSA adjuncts on page 1. Enter

node names for switches, routers, and CMS starting on page 2.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

H.323 Trunk Administration

Task 1 Steps

Begin

> Open Node Names screen — enter ch node-n > Go to page 2 of the screen

2 H.323 Trunks

change node-names Page 2 of 6

Name IP Address Name IP Address clan-a1 clan-a2______ 192.168.20_.31_ ___________ ___.___.___.___ default 0 .0 .0 .0 ___________ ___.___.___.___ medpro-a1 medpro-a2___ 192.168.20_.81_ ___________ ___.___.___.___ medpro-a3 medpro-b1

______ 192.168.10_.31_ ___________ ___.___.___.___

___ 192.168.10_.81_ ___________ ___.___.___.___

___ 192.168.10_.82_ ___________ ___.___.___.___ ___ 192.168.10_.83_ ___________ ___.___.___.___ ___ ___.___.___.___ ___________ ___.___.___.___

NODE NAMES

> Enter values.

Field Conditions/Comments

Name Enter unique node names for:

• Each C-LAN ethernet port on the network

• Each IP-Interface (Medpro) board on the local switch.

The default node name and IP address is used to set up a default gateway, if desired. This entry is automatically present on the Node Names screen and cannot be removed.

When the Node Names screen is saved, the system automatically alphabetizes the entries by node name.

IP Address Enter a unique IP addresses for each node named in the previous

field.

> Submit the screen

End

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

H.323 Trunk Administration 2 H.323 Trunks

Task 2 — Define IP Interfaces

The IP interface for each C-LAN and MedPro board on the switch must be defined on the IP Interfaces form. Each DEFINITY switch in an IP network has one IP Interfaces form.

Task 2 Steps

Begin

> Open IP Interfaces form — enter ch ip-i

change ip-interfaces Page 1 of 2

IP Interfaces

Inter-region IP connectivity allowed? n Enable Net Eth Pt Type Slot Code Sfx Node Name Subnet Mask Gateway Addr Rgn

y C-LAN 01A10 TN799 B clan-a1 255.255.255.0 192.168.10 .100 1

y MEDPRO 01A13 TN802 B medpro-a1 255.255.255.0 192.168.10 .100 1

y MEDPRO 01A16 TN802 B medpro-a2 255.255.255.0 192.168.20 .100 1 y C-LAN 01A09 TN799 B clan-a2 255.255.255.0 192.168.20 .100 2

y MEDPRO 01B13 TN802 B medpro-a3 255.255.255.0 192.168.10 .100 2

y MEDPRO 01B09 TN802 B medpro-b1 255.255.255.0 192.168.10 .100 2

n 255.255.255.0 . . .

> Enter values

Field Conditions/Comments

Inter-region IP connectivity allowed?

Enter y to allow IP endpoints (phones and trunks) to use MedPro resources administered in regions that are different from the endpoints’ regions.

Enable Eth Pt The Ethernet port must be enabled (y) before it can be

used. The port must be disabled (n) before changes can be made to its attributes on this screen.

Type Enter c-lan or medpro. Slot Enter the slot location for the circuit pack. Code Display only. This field is automatically populated with

TN799 for C-LAN or TN802 for MedPro.

Sfx Display only. This field is automatically populated with B

for the TN802 and TN799.

Node name Enter the unique node name for the IP interface. The node

name entered here must already be administered on the Node Names screen

1 of 2

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

H.323 Trunk Administration

Field Conditions/Comments

Subnet Mask Enter the subnet mask associated with the IP address for

Gateway Addr Enter the address of a network node that will serve as the

Net Rgn Enter the region number for this IP interface.

> Submit the screen

End

2 H.323 Trunks

this IP interface. (The IP address is associated with the node name on the Node Names screen).

default gateway for the IP interface.

2 of 2

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

H.323 Trunk Administration 2 H.323 Trunks

Task 3 — Assign Link via ethernet Data Module to the LAN

This task administers an ethernet data module for the connection between the C-LAN

board’s ethernet port (port 17) and the LAN. The data module associates a link number and extension number with the C-LAN ethernet port location. This association is used by the DEFINITY processor to set up and maintain signaling connections for multimedia call handling.

The C-LAN ethernet port is indirectly associated with the C-LAN IP address via the slot location (which is part of the port location) on the IP Interfaces screen and the node name, which is on both the IP Interfaces and Node Names screens.

Task 3 Steps

Begin

> Open Data Module form — enter a da n

add data-module next Page 1 of X

Data Extension: 2377 Name: ethernet on link 2

Type: ethernet Port: 01c0817_ Link: 2

Network uses 1’s for broadcast addresses?: y

DATA MODULE

> Enter values

Field Conditions/Comments

Type: This indicates the data-module type (ethernet) for this link . Port: Ethernet connections must be assigned to port 17 on the C-LAN

circuit pack.

Link: The link number must be in the range 1 – 33 for G3r, or 1 – 25 for

G3si and G3csi, and not previously assigned on this switch.

Name: This field is information-only; it appears in lists generated by the

“list data module” command.

Network uses 1’s for broadcast addresses?

Leave the default (y) if the private network contains only DEFINITY switches and adjuncts. Set to n only if the network includes non-DEFINITY switches that use the 0’s method of forming broadcast addresses. See Appendix A, “Data Module type ethernet” for more information about this field.

> Submit the screen

End

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

H.323 Trunk Administration

2 H.323 Trunks

Task 4 — Create a signaling group

This task creates a signaling group that will be associated with H.323 trunks that connect this switch to a far-end switch. One or more unique signaling groups must be established for each far-end node that this switch is connected to via H.323 trunks.

Note: The following steps address only those fields that are specifically related

to H.323 trunks. The other fields are administered as for previou s releases

and are described in the Administrator’s Guide.

Task 4 Steps

Begin

> Open new Signaling Group form — enter a sig n

add signaling-group n Page 1 of 5 SIGNALING GROUP

Group Number: 3 Group Type: h.323 Max number of NCA TSC: 0 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: Supplementary Service Protocol: a

Near-end Node Name: clan-a1 Far-end Node Name: clan-b1 Near-end Listen Port: 1720 Far-end Listen Port: 1720

LRQ Required? n Calls Share IP Signaling Connection? n Bypass If IP Threshold Exceeded? n

Internetworking Message: PROGress

> Enter values

Field Conditions/Comments

Group Type: Enter h.323 Trunk Group for

Channel Selection:

Leave blank until you create a trunk group in the following task; then use the change command and enter the trunk group number in this field.

Near-end Node Name: Enter the node name for the C-LAN IP interface on this

switch. The node name must be administered on the Node Names screen and the IP Interfaces screen.

Near-end Listen Port: Enter an unused port number from the range 17 19, 1720

or 5000–9999. The number 1720 is recommended. Note: If the LRQ field is set to y, the near-end

Listen Port must be 1719.

1 of 2

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

H.323 Trunk Administration 2 H.323 Trunks

Field Conditions/Comments

Far-end Node Name: This is the node name for the far-end C-LAN IP

Interface used for trunks assigned to this signaling group. The node name must be administered on the Node Names form on this switch.

This field can be left blank if the signaling group is associated with an unspecified destination.

Far-end Listen Port: The same number as entered in the Near-end Listen

Port field is recommended; this number must match the number entered in the Near-end Listen Por t field o n the signaling group form for the far-end switch.

This field can be left blank if the signaling group is associated with an unspecified destination.

LRQ Required? Leave the default (n) if the far-end switch is a

DEFINITY ECS. Set to y only if the far-end switch is a non-DEFINITY switch and requires a location request (to obtain a signaling address) in its signaling protocol.

Calls Share IP Signaling Connection?

Always e nt er y for inter-DEFINITY connections. If the local and/or remote switch is a non-DEFINITY switch, leave the default (n).

Bypass if IP Threshold Exceeded?

Set to y to automatically remove from service trunks assigned to this signaling group when IP transport performance falls below limits administered on the Maintenance-Related System Parameters (sys par maint) screen.

>Go to page 2

add signaling-group next Page 2 of 5

ADMINISTERED NCA TSC ASSIGNMENT

Service/Feature: As-needed Inactivity Time-out (min): TSC Local Mach. Index Ext. Enabled Established Dest. Digits Appl. ID 1: n 2: n 3: n 4: n 5: n 6: n 7: n 8: n

2 of 2

If this signaling group will be used for DCS, enter NCA TSC information here. See Chapter 3, Configuration 4, for instructions.

> Submit the screen

End

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

H.323 Trunk Administration

2 H.323 Trunks

Task 5 — Create a trunk group

This task creates a new trunk group for H.323 trunks. Each H.323 trunk must be a member of an ISDN trunk group and must be associated with an H.323 signaling group.

Note: The following steps address only those fields that are specifically related

to H.323 trunks. The other fields are administered as for previou s releases

and are described in the Administrator’s Guide.

Task 5 Steps

Begin

> Open new Trunk Group form — enter a tr n

add trunk-group n Page 1 of 10 TRUNK GROUP Group Number: 3 Group Type: isdn CDR Reports: y

Group Name: TG 3 for H.323 trunks COR: 1 TN: 1 TAC: 103 Direction: two-way Outgoing Display? n Carrier Medium: IP Dial Access? n Busy Threshold: 99 Night Service: Queue Length: 0 Service Type: tie Auth Code? n TestCall ITC: rest Far End Test Line No: TestCall BCC: 0 TRUNK PARAMETERS Codeset to Send Display: 0 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Charge Advice: none Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc

Trunk Hunt: cyclical QSIG Value-Added Lucent? n Digital Loss Group: 13 Calling Number - Delete: Insert: Numbering Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0

> Enter values

Field Conditions/Comments

Group Type Enter isdn. Carrier Medium Enter ip. Service Type Enter tie. TestCall ITC: Enter unre (unrestricted). TestCall BCC: Enter 0. Codeset to Send Display Enter 0.

Note: Outgoing Display This field may need to be changed if the

far-end is a non-DEFINITY switch.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

H.323 Trunk Administration 2 H.323 Trunks

> If using DCS, go to screen page 2

add trunk-group n Page 2 of 10 ACA Assignment? n Measured: none Wideband Support? n

Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: Send Name: n Send Calling Number: n Used for DCS? y PBX ID: 4 Suppress # Outpulsing? n DCS Signaling: d-chan Outgoing Channel ID Encoding: exclusive UUI IE Treatment: service-provider

Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: n

Send UCID? n Send Codeset 6/7 LAI IE? y

TRUNK FEATURES

> Enter values

Field Conditions/Comments

Used for DCS? Enter y. PBX ID: Enter the switch ID. This is the value in the

Destination Node Number field on the Dial Plan Record screen of the remote sw it c h .

DCS Signaling: Enter d-chan.

Note:

• Send Name

• Send Calling Number

• Send Connected Number

These fields may need to be changed if the far-end is a non-DEFINITY switch.

> Go to page 4

add trunk-group 3 Page 4 of 10 TRUNK GROUP Administered Members (min/max): 0/0 GROUP MEMBER ASSIGNMENTS Total Administered Members: 0

Port Code Sfx Name Night Sig Grp 1: ip H.323 Tr 1 3 2: ip H.323 Tr 2 3 3: ip H.323 Tr 3 3 4: 5:

Note: Each signaling group can support up to 31 trunks. If you need more than

31 trunks between the same two switches, add a second signaling group with different listen ports, and add a second trunk group. See Signaling

group assignments (page 50) for more information about the relationship

between signaling groups and H.323 trunk groups.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

H.323 Trunk Administration

2 H.323 Trunks

> Enter gr oup members

Field Conditions/Comments Port Enter ip. When the screen is submitted , this value will

automatically be changed to a “T” number of the form Txxxxx.

Name Enter a 10-character descriptive name for the trunk. The

name is to help you identify the trunk – it is not used by the system.

Sig Grp Enter the number of the signaling group that you set up

for H.323 trunks.

>Submit the screen When the screen is submitted, the Port field for the IP (H.323) trunks is changed to a

Txxxxx number, as shown below.

display trunk-group 3 Page 4 of 10 TRUNK GROUP Administered Members (min/max): 1/3 GROUP MEMBER ASSIGNMENTS Total Administered Members: 3

Port Code Sfx Name Night Sig Grp 1: T00004 H.323 Tr 1 3 2: T00005 H.323 Tr 2 3 3: T00006 H.323 Tr 3 3 4: 5:

End

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

H.323 Trunk Administration 2 H.323 Trunks

Task 6 — Modify signaling group

This task modifies the signaling group form to add a trunk group number to the Trunk Group for Channel Selection field.

Task 6 Steps

Begin

> Busy out the signaling group — enter bu sig 3 > Open the Signaling Group form — enter ch sig 3

change signaling-group 3 Page 1 of 5 SIGNALING GROUP

Group Number: 3 Group Type: h.323 Max number of NCA TSC: 0 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 3 Supplementary Service Protocol: a

Near-end Node Name: clan-a1 Far-end Node Name: clan-b1 Near-end Listen Port: 1720 Far-end Listen Port: 1720

LRQ Required? n Calls Share IP Signaling Connection? n Bypass If IP Threshold Exceeded? n

> Enter values

Field Conditions/Comments

Trunk Group for Channel Selection

Enter the trunk group number. If there is more than one trunk group assigned to this signaling group, the group entered in this field will be the one that can accept incoming calls.

> Submit the screen > Release the signaling group — enter rel sig 3.

End

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

H.323 Trunk Administration

Task 7 — Specify codecs

This task modifies the IP Media Parameters screen to specify the type of codecs available on this switch and the preferred order of use of the different types.

Task 7 Steps

Begin

> Open the IP Parameters screen — enter ch ip-p

change ip-parameters Page 1 of 1 IP Media Parameters Audio Codec

Preferences 1: G.711MU

2: G.723-6.3K

3: G.729A

UDP Port Range

2 H.323 Trunks

Min: 2048 Max: 65535 n

> Enter values

Field Conditions/Comments

Audio Codec Preferences Enter up to four codec types in the order of

preference of use. Valid types are: G711A, G711Mu, G723-6.3k, G723-5.3k, G.729A.

Note: The codec ordering must be the same on

DEFINITY switches at both ends of an H.323 trunk connection. The set of codecs listed need not be the same, but the order of the listed codecs must be the same.

See IP Parameters (page 34) for a description of the differences between codec types.

UDP Port Range Enter a minimum and maximum port number to

specify a block of port numbers to be used for audio connections. Valid values are 1 to 65535, with Min < Max.

> Submit the screen

End

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

Troubleshooting IP Solutions 2 H.323 Trunks

Troubleshooting IP Solutions

This section provides solutions to some commonly encountered problems wi th H.323 tr unk s an d IP Sof tpho nes .

H.323 Trunk Problem Solving

Signaling group assignments

Multiple H.323 trunk groups can be assigned to a single signaling group, as with standard trunk groups that use circuit-switched paths. However, when multiple H.323 trunk groups have different attributes, it is usually better to assign each H.323 trunk group to a separate signaling group. An H.323 signaling group directs all incoming

calls to a single trunk group, regardless of how many trunk groups are assigned to that signaling group. This is specified in the field “Trunk Group for Channel

Selection” on the H.323 signaling group screen. In the example shown in Figure 2, two trunk groups are assigned to the same

signaling group on each of two switches, A and B. Trunk groups A1 and B1 are set up to route calls over a private network. Trunk g roups A2 and B2 are set up to route calls over the public network. The signaling group on switch B terminates all incoming calls on trunk group B1 as specified by the “Trunk Group for Channel Selection” field. Calls from switch A to switch B using trunk group A1 and the private NW are terminated on trunk group B1, as desired. However, calls from switch A to switch B using trunk group A2 and the public NW are also terminated on trunk group B1, not trunk group B2, which would be the desired outcome.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Troubleshooting IP Solutions

The solution to this problem is to set up a separate signaling group for each trunk group, as shown in Figure 3. More generally, set up a separate signaling group for each set of trunk groups that have common attributes.

Figure 2. Shared signaling group

2 H.323 Trunks

TGA1

Private NW

SGA1

TGA2

Public NW

Switch A

Figure 3. Separate signaling group

TGA1

TGA2

SGA1

SGA2

Private NW

Public NW

SGB1

Trunk Group for Channel Selection = TGB1

SGB1

Trunk Group for Channel Selection = TGB1

SGB2

Trunk Group for Channel Selection = TGB2

TGB1

TGB2

Switch B

TGB1

TGB2

No MedPro resources available

Switch A

If two switches are connected via an H.323 trunk and all MedPro resources are in use on the call-destination switch when a call is made, the call will fail even when a 2nd

Switch B

preference is administered in the routing pattern on the source switch. This can be

avoided by setting the first preference look ahead routing (LAR) to “next” in the routing pattern.

C-LAN sharing Depending on the network configuration , a single C-LAN b oard has the capacity to

handle the signaling for multiple applications. For example, the call center Call Management System (CMS) would typically use a small portion of a C-LAN’s capacity so the same C-LAN could easily handle the signaling for other IP endpoints at the same time. There are many variables that affect the number of C-LAN and TN802B (MedPro) circuit packs that you will need for your network configuration. To accurately estimate the C-LAN and MedPro resources needed, a network configuration tool is available from Lucent. See Appendix D, Capacities and

Performance for a summary of this tool.

Traffic congestion is potentially a problem when multiple IP Interfaces (such as C-LAN, MedPro, PCs, CMS) share a network and some of the endpoints are heavily used. This problem can be minimized by using a switched network and assigning endpoints ( s uch as CMS) to a s eparate LAN/WAN segment.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

Troubleshooting IP Solutions 2 H.323 Trunks

IP Softphone Problem Solving

Codecs used with Netmeeting

Telecommuter use of phone lines

Voice quality for the road-warrior application of DEFINITY IP softphone will vary depending on several factors. Poor voice quality can be caused by the use of the high-compression codecs (G.723 or G.729) in situations where the low-compression codec (G.711) should be used. This can hap pen unexpectedly when using NetMeeting

— when the G.711 is set as the preferred codec on the switch, NetMeeting m ay fail to use it. Since there is no way to monitor which codec is being used, the only way to determine that this is the problem is to disable all but the G.711 codecs. Then, if calls no longer work, it can be concluded that NetMeeting is failing to use the G.711. The solution to this problem is to reinstall NetMeeting.

The telecommuter application of the IP Softphone requires the use of two phone lines: one for the IP connection to DEFINITY, which is used for softphone registration and call signaling, and the other for a PSTN connection, which DEFINITY uses as a callback number to establish the voice path. How you allocate your phone lines to these two functions may make a difference.

For example, assume that you have telephone services provided by the local phone company, such as voice mail, associated with one of your lines and not the other. In this case, you should use the line with the services to make the initial IP connection to register the softphone and use the line without the services as the POTS callback for the voice path. Otherwise, there could be undesirable interactions between the softphone and the local services. For example, if your telecommuter application is registered and you were using your POTS callback line for a personal call when a business associate dialed your work extension, the business associate would hear your home voice mail message.

NetMeeting drops unanswered calls

NetMeeting ignores out-of-band tones

For calls made to a NetMeeting softphone, if the call is not answered or if coverage is not administered, after about 5 rings NetMeeting drops the call and the station stops ringing but the caller continues to hear ringback. To avoid this situation, make sure that coverage is administered for the NetMeeting softphone.

NetMeeting ignores any H.323 digits received out-of-band, so it never hears DTMF from DEFINITY, which always strips DTMF from the audio path and plays it out-of-band with H.323.

For example, if you are on a call on a NetMeeting softphone and the calling party presses a number or character on their keypad, you will not hear the tone.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

3 C-LAN Administration

This chapter describes how to administer TCP/IP data connections between DEFINITY ECS switches using the C-LAN circuit pack. This chapter does not cover the use of the IP Interface circuit pack for H.323 connectivity.

Overview

This chapter provides an update of the R7 administration procedures, which were

described in Chapter 2, “DCS Administration,” of issue 1 of this b ook. The R8 changes described in this chapter are:

• R8 administration procedures using the changed ethernet Data Module s creen and

the new IP Interfaces screen

• use of IP Routes, which, in some cases, are not needed in R8 when they were

needed in R7

• additional procedures for administering CMS and Intuity AUDIX

TCP/IP connections (ppp or ethernet) require DEFINITY ECS Release 7 or later hardware and software. ISDN and BX.25 connections are supported on switches upgrading to R8 and pre-R7 switches can be connected to R8 switches via ISDN or BX.25. However, new systems are not sold with X.25 connections. Therefore, all switches in the configuration are assumed to be upgraded to release R7 or later.

Supported Switches and Adjuncts

Csi-model switches cannot have X.25 connections. New R8si and R8r switches cannot have new X.25 connections but pr e-R7 switches with X.25 conn ections can be upgraded to R8 and keep the X.25 connections.

The vs model of DEFINITY ECS cannot be upgraded t o R8 — R6.3 is the last release supported for the vs model. However, pre-R7 releases of the vs model will be supported (via X.25 and ISDN, not TCP/IP) in customer networks that include R8 versions of the csi, si, and r models.

The call management system (CMS) and Intuity adjuncts can be connected to the DEFINITY ECS R8csi with an ethernet connection and to the si and r models with either an ethernet or Bx.25 connection. Procedures for administering these connections are not covered in this book. They are documented in CentreVu CMS

Switch Connections and Administration (585-215-876) for CMS and in Intuity Messaging Solutions, LAN Integration with DEFINITY ECS (585-313-602) for Intuity. CMS administration is covere d in Centre CMS Software Installation and Setup, 585-215-866.

Administration for Network Connectivity

555-233-504 — Issue 1 — April 2000 CID: 77730

Overview 3 C-LAN Administration

Checklist for Prerequisite Administration

This is a checklist of things that need to be completed before you can proceed with the network administration tasks. Review this checklist before starting the administration tasks.

✔ Checklist Item

The prerequisite administration needed depends on whether the system is new or is being upgraded from an R7 or pre-R7 system to R8. Use the following map to determine which steps to perform.

New

Pre-R7 si with ISDN connections

1 2 3 4 5 6 7

to be preserved

Other Pre-R7

For more information about the checklist items, refer to Appendix A or the appropriate upgrades book in "References", page 56.

UPGRADES ONLY:

Steps 1–6 apply only to systems being upgraded to R8

from an R7 or pre-R7 release. For new systems, skip to step 7.

1 Save translations on customer flash card (csi or si models) or tape (r

model). For R7 systems, skip to step 5.

2 This step is for the si model only. It preserves ISDN-PRI connections,

which (for R7 and later) are carried on the NetPkt circuit pack inst ead of the PI or PACCON circuit packs. ISDN-PRI connections are preserved transparently on the csi and r models.

If:

the si switch has existing ISDN-PRI connections that the customer wants to keep, complete the following steps:

~ De-administer the ISDN-PRI connections:

• busy the ISDN links

• remove comm-interface links of type ISDN

• remove comm-interface processor channels that use ISDN links

• remo ve da ta mod ules us ing those links

~ Save translations on a “working” flash card

Otherwise:

skip to step 3.

1 of 3

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Overview

3 C-LAN Administration

✔ Checklist Item

3 Remove old circuit packs:

~ Turn off the power. ~ For the csi model, remove the Processor (TN798) circuit pack (Don’t

remove the processor circuit pack if it is a TN798B).

~ For the si model, remove the Processor (TN790), PACCON (TN778),

and NETCON (TN777) circuit packs. If there are X.25 connections that the customer wants to keep, leave the PI (TN765) circuit pack in the switch; otherwise remove it.

~ For the r model, if there are X.25 connections that the customer wants

to keep, leave the PGATE (TN755) circuit pack in the switch; otherwise, remove it.

4 Install new circuit packs on all switches upgrading from a pre-R7

software load to R8:

~ For csi models: install the TN798B (processor) and TN799B

(C-LAN) circuit packs.

~ For si models: install the TN790B (processor), TN794 (NetPkt), and

TN799B (C-LAN) circuit packs. For any PPN or EPN that will be carrying packet data, replace the TN776 (Expansion Interface) with the TN570B or TN570C circuit pack.

~ For r models: install TN799B (C-LAN.)

The C-LAN circuit pack is required for TCP/IP (ppp and ethernet) connections. In all cases, the R8 software will run without the TN799B (C-LAN) circuit pack; all other new circuit packs are required for R8.

5 Install the R8.1 Software on all switches upgrading to R8.1 6 Copy translations from translations flash card or tape (G3r). Use the

“working” flash card if step 3 was performed.

NEW and UPGRADE Systems — the following items apply to both new systems and systems being upgraded to R8 from a previous release. For more information about the checklist item, refer to the appropriate installation book in "References",

page 56.

7 Established physical connections at each node. 8 Set software version on the System Parameters Customer Options form.

General Administration for new installations — the following translations should already be in place for existing systems and usually should not need to be changed for an upgrade to R8 unless new nodes are being added to the network. Refer to appendix A for more information about these tasks.

9 DS1 circuit packs administered

2 of 3

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

Overview 3 C-LAN Administration

✔ Checklist Item

10 Signaling group administered

~ page 1 — Trunk board address and Interface ID

~ Page 2 — Administered NCA TSC assignment 11 Synchronization plan administered 12 Trunk groups assigned 13 Dial plan administered 14 Uniform dial plan administered 15 AAR analysis administered 16 Route pattern administered 17 Hunt groups assigned

3 of 3

Configurations

The task descriptions are presented in six relatively simple configurations. Each configuration describes how to administer either a 2-switch connection or a 3-switch gateway connection. The procedures for administering these configurations can be

used either individually or in groups as “building blocks” for constructing most networks involving DEFINITY ECS R8 and pre-R7 switches.

The following table lists the configurations described in this chapter.

Config-

uration

Switch2Connection 1Switch1Connection 2Switch3Page

1 R7si ppp R7r page 60 2 R7csi ethernet R7r

page 73

(+CMS)

3 si bx.25 R7r ethernet R7si page 99 4 csi isdn R7si ppp R7csi page 124 5A R7csi ppp R7r ethernet R7si page 146 5B R7csi ppp R7r

ethernet R7si page 171 (2 C-LAN boards)

The first 2 configurations are simple 2-switch networks. The next two are 3-switch networks with Switch 1 serving as a gateway between different signaling types for connection 1 and connection 2. The last two configurations are ppp–ethernet networks; 5B, is the same as 5A except the Switch 1 has two C-LAN boards instead of one.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Overview

TCP/IP connections (ppp or ethernet) require DEFINITY ECS Release 7 or later hardware and software. ISDN and BX.25 connections are supported on switches upgrading to R8 and pre-R7 switches can be connected to R8 switches via ISDN or BX.25. However, new systems will not be sold with X.25 connections. Therefore, all switches in the five configurations are assumed to be upgraded to release R7 or later except the si connected via BX.25 and the cs i connected via I SDN in configur ations 3

and 4 — these 2 switches could be either R7 or pre-R7 versions.

Organization of this chapter

The descriptions of the configurations have a common format. Each configuration section has the following subsections:

• Configurat ion overview

• Task summary

• Checklist of prerequisite tasks

• Configurat ion diagram

• Administration tasks

3 C-LAN Administration

The subsections are described below.

Configuration Overview Each of the configuration sections begins with a brief description of the network

represented by the configuration. This section includes a high-level diagram and a description of the switches and their connections for each node in the network.

Task Summary Lists the tasks that need to be performed to administer this configuration.

1 Review checklist 2 Assign node names 3 Assign links 4 Assi gn processor chan nels

Procedures for completing each of these tasks are described in detail following this summary.

Configuration Diagram A detailed diagram of the configuration is shown after the task summary. The

diagram is in two parts — one part showing the software-defined connections and the other part showing the hardware connections. The diagram shows many of the parameters that are entered on the administration screens

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

Overview 3 C-LAN Administration

In the hardware part of the diagram, the paths for voice and signaling data are shown by dashed or dotted lines. The data for voice and call-setup signaling usually takes a different path through the switch hardware from the path for DCS and ISDN signaling data. These two types of data are distinguished in the hardware part of the diagram by the following convention.

A dashed line, " ", indicates voice and call-setup data. A dotted line, " ", indicates DCS signaling data. In the software part of the diagram, the virtual path from processor to processor

between two nodes is traced by dashed lines. The path starts at a processor channel on one node, through the link/interface-channels on each node, to the processor channel on the connected node.

Administration tasks This section gives the detailed steps for administering the connections between

switches. For each configuration, there are several tasks and each task consists of several steps. All of the tasks needed to administer all the nodes in the network are included in each configuration.

The administration task sections list the steps for completing a screen (or "form") and show a representation of the filled-in screen. Many of the field values shown in the

screens are examples — you will use different values that are appropriate for your system. Information about the fields and their values — when and why different values are used — is given for each screen. More detailed information about the screens and their fields is given in Appendix A.

Supported Switches and Adjuncts

The call management system (CMS) and Intuity adjuncts can be connected to the DEFINITY ECS R7csi with an ethernet connection and to the si and r models with either an ethernet or Bx.25 connection. Procedures for administering these connections are not covered in this book. They are documented in CentreVu CMS

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Overview

Intuity AUDIX LAN Setup Summary

The following list summarizes the steps for setting up an Intuity AUDIX on a LAN.

1 Assign node name and IP address 2 Assign UNIX machine name, IP address, configure LAN card.

“Networki ng Administration, TCP/IP Administration”

3 Assign country and switch type

“Switch Interface Administration, Switch Selection”

4 Assign extension length, Host Switch Number (switch node from dial plan),

Audix Number, Switch Number IP address of the switch, and TCP Port. “Switch Interface Administration, Call Data Interface Administration, Switch

Link Administration.”

5 Reboot the Intuity AUDIX

“Customer/Services Administration, System management, System Control, Shutdown System.”

6 Set up the DCS Net work Time Zones

3 C-LAN Administration

7 “Audix Administration, change switch-time-zone.”

CMS LAN Setup Summary

The following list summarizes the steps for setting up a CMS server.

1 Edit the /etc/hosts file to add switch names and IP addresses 2 Set up a second NIC 3 Add a default router 4 Set up the local/remote port 5 Choose between x. 25 and TCP/IP signaling 6 For X.25, define which phys ical port is us ed on CMS 7 For TCP/IP, assign the switch host name or IP address and TCP port number

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

Configuration 1: R8r <—ppp—> R8si 3 C-LAN Administration

Configuration 1: R8r <—ppp—> R8si

Configuration 1 is a ppp connection between a DEFINITY ECS R8r and a DEFINITY ECS R8si switch in a DCS network.

Task Summary

Switch 1

DEFINITY ECS R8r

DS1

C-LAN

node-1

ppp

node-2

Complete the following tasks for Switch 1 and Switch 2:

1 Review prerequisite administration checklist 2 NO DE 1 adminis tration

a Assign node names b Assign link (via a data module) to node-2 c Assign pr ocessor channe ls

3 NODE 2 administration

a Assign node names b Assign link to (via a data module) node-1 c Assign pr ocessor channe ls

4 Enable links and processor channels

Switch 2

DEFINITY ECS

R8si

DS1

C-LAN

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Configuration 1: R8r <—ppp—> R8si

Prerequisite Administration

There are some system administration tasks that need to be completed before you can proceed with the connectivity administration described in this section.

Review the checklist of prerequisite administration tasks in Checklist for Prerequisite

Administration (page 54), before proceeding with the connectivity administration in

this section.

3 C-LAN Administration

SWITCH 1 SWITCH 2

DEFINITY ECS R7r

Processor

channels

1 2

384

Processor

UN331B

PktInt

TN1655

Network

control

UN332B

Interface

channels

1 5000 5001

5003

64500

Link 1

Processor bus

DS1

TN767/

TN464

Configuration 1

software-defined connections

hardware connections

Voice data

ppp data

DEFINITY ECS R7si

Interface

channels

1 5000 5001

x(any)

64500

Link 3

Processor bus

DS1

TN767/

TN464

Processor

channels

1 2

256

Processor

TN790B

NetPkt TN794

TDM bus

C-LAN TN799

node-1

Ext 2010

loc 1b0115

192.168.10.31

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

node-2

Ext 3020

loc 1a1206

192.168.10.32

cydfec1a EWS 052099

C-LAN TN799

TDM bus

Packet busPacket bus

Configuration 1: R8r <—ppp—> R8si 3 C-LAN Administration

Switch 1 Task — Assign Node Names

This task assigns node names and IP addresses to each node in the network. This screen is administered on Switch 1. A Node Names screen must be administered on each switch in the network.

Note: Enter node names for Intuity AUDIX and MSA adjuncts on page 1. Enter

node names for switches, routers, and CMS starting on page 2.

Steps

Begin

> Open Node Names screen — enter ch node-n > Go to page 2 of the screen

change node-names Page 2 of 6 NODE NAMES

Name IP Address Name IP Address default node-1____________ 192.168.10_.31_ __________________ ___.___.___.___ node-2 __________________ ___.___.___.___ __________________ ___.___.___.___

___________ 0__.0__.0__.0__ __________________ ___.___.___.___

____________ 192.168.10_.32_ __________________ ___.___.___.___

> Enter values.

Field Conditions/Comments

Name Enter unique node names for the following 2 nodes:

• C-LAN PPP port on Switch 1

• C-LAN PPP port on Switch 2.

IP Address The unique IP addresses of the nodes named in the previous field.

> Submit the screen

End

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Configuration 1: R8r <—ppp—> R8si

3 C-LAN Administration

Switch 1 Task — Assign Link via ppp Data Module to Switch 2

This task administers a ppp data module on Switch 1 for the ppp connection to Switch

2. The data module defines a network interface — it associates a link number with a port address and node name for the C-LAN port on Switch 1. It also specifies the node name for the destination node, which is a C-LAN port on Switch 2.

Steps

Begin

Open Data Module form — enter ad da n

add data-module next Page 1 of x DATA MODULE

Data Extension: 2010 Name: _ppp on link 1 to node-2___ BCC: 2 Type: ppp COS: 1 Port: 01b0115 COR: 1 Link: 1_ TN: 1 Enable Link? n

Node Name: node-1 _____

Subnet Mask: 255.255.255.0

Establish Connection: y

DESTINATION Digits: 6113020

Node Name: node-2_________

CHAP? n

________

[The system assigns the extension 2010 to this data module. Instead of n (next) in the command line, you could specify any unused extension in the dial plan.]

> Enter values

Field Conditions/Comments

Type: This indicates the data-module type for this connection (ppp). Port: In this example, the C-LAN circuit pack is in slot 01b01; the ppp

Link: For G3r, t he link number must be in the range 1 – 33, not

Enable Link? If you need to add an IP route that uses this node as a gateway,

Name: Information-only; appears in list generated by the "list data

connection is through port 15.

previously assigned on this switch.

this field must be set to leave this field set to

y before adding the IP route. Otherwise

n until the link administration is complete;

that is, until after all data modules and the processor channels are assigned, then set to

module" command.

1 of 2

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

Configuration 1: R8r <—ppp—> R8si 3 C-LAN Administration

Field Conditions/Comments

COS COR:

The values for these fields will be specified by the system administrator.

TN: BCC: Bearer Capability Class. This is a display-only field. Node Name: The node name for the interface (C-LAN port) defined by this

data module. This must be a name previously entered on the

Node Names screen. Subnet Mask: Establish

Connection?

y means that this switch will be responsible for the call setup for

this connection. Enter n when administering the data module for

Switch 2. Destination

Digits:

Trunk access code (611) plus ex tension of data modu le on node 2

(3020). If you use just the extension, then you must administer

UDP and AAR route patterns to access the correct trunk group. Destination

Node Name:

Name of the node at the far end (Switch 2) of this connection.

This must be a name entered on the Node Names screen (on both

switches). CHAP? This field enables/disables the Challenge Handshake

Authentication Protocol security mechanism on this link. If you

enter y, another field will appear prompting for a CHAP secret

(password).

> Submit the screen

End

2 of 2

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Configuration 1: R8r <—ppp—> R8si

3 C-LAN Administration

Switch 1 Task — Assign Processor Channels

This task associates data links (hardware) with processor channels (software) on Switch 1 and specifies the destination node and machine ID.

Steps

Begin

> Open the Processor Channel Assignment form — enter ch com p

change communications-interface processor-channels Page 1 of X

PROCESSOR CHANNEL ASSIGNMENT

Proc Gtwy Interface Destination Session Mach Chan Enable Appl. To Mode Link/Chan Node Port Local/Remote ID 1: n 2: n

12: y

64: n _______ _ __ _____ __________ 0____ ___ ___ __

_______ _ __ _____ __________ 0____ ___ ___ __ _______ _ __ _____ __________ 0____ ___ ___ __

dcs ___ s 1_ 5003 node-2____ 0____ 12_21_ 2_

> Enter values for processor channel 12

Field Conditions/Comments

Enable Set to y. Appl. Set to dcs for DCS signaling. Mode node-1 is the "server" for this session. Set node-2 to "client"

(c).

Interface Link This must match the link number assigned on the node-1

data module screen in the previous task.

Interface Chan For TCP/IP, interface channel numbers are in the range 5000

– 64500. The recommended values are: 5001 for CMS, 5002 for

Intuity AUDIX, and 5003 for DCS connections that are not gateways. These three values should be reused for multiple instances of these applications; for example, if there are two Intuity AUDIX’s, use 5002 for both; or if there are four DEFINITY ECS’s, use 5003 for all four. The combination of Link, Interface Channel, and Mach ID must be unique.

The recommended values for gateway switches is 6001–6099. The interface channel number must be unique for each gateway.

This number must match the Destination Port number on the node-2 Processor Channel screen.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

1 of 2

Configuration 1: R8r <—ppp—> R8si 3 C-LAN Administration

Field Conditions/Comments

Destination Node Name of the far-end node for this channel. This must be a

name entered on the Node Names screen. For ppp connections, it must match the Destination Node Name entered on the ppp Data Module screen.

Destination Port A valu e of 0 allows any available interface channel on the

destination node to be used for this connection. The Interface Channel number for this connection on the

Switch-2 Processor Channel screen must also be set to 0. Session - Local The Local and Remote Session numbers can be any value Session - Remote

between 1 an d 256 (si model) or 384 (r model), but th ey

must be consistent between endpoints. For each connection,

the Local Session number on this switch must equal the

Remote Session number on the remote switch and vice

versa.

It is allowed, and sometimes convenient, to use the same

number for the Local and Remote Session numbers. It is

allowed, but not recommended, to use the same Session

numbers for two or more connections. Mach ID Destination switch ID identified on the dial plan of the

destination switch (in the Local Node Number field).

>Submit the screen

End

2 of 2

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Configuration 1: R8r <—ppp—> R8si

3 C-LAN Administration

Switch 2 Task — Assign Node Names

This task assigns node names and IP addresses to each node in the network. This screen is administered on Switch 2. A Node Names screen must be administered on each switch in the network.

Note: Enter node names for Intuity AUDIX and MSA adjuncts on page 1. Enter

node names for switches, routers, and CMS starting on page 2.

Steps

Begin

> Open Node Names form — enter ch node-n > Go to page 2 of the screen

change node names Page 2 of 6 NODE NAMES

Name IP Address Name IP Address default_________ 0__.0__.0__.0__ __________________ ___.___.___.___ node-1 __ node-2 ___ ________________ ___.___.___.___ _______________ ___.___.___.___ ________________ ___.___.___.___ _______________ ___.___.___.___

192.168.10_.31_ _______________ ___.___.___.___

192.168.10_.32_ _______________ ___.___.___.___

> Enter values.

Field Conditions/Comments

Name Enter unique node names for the following 2 nodes:

• C-LA N PPP port on Switch 2

• C- LAN PPP port on Switch 1.

IP Address T he unique IP a ddresses of the nodes name d in the previ ous

field.

> Submit the screen

End

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

Configuration 1: R8r <—ppp—> R8si 3 C-LAN Administration

Switch 2 Task — Assign Link via ppp Data Module to Switch 1

This task administers a ppp data module on Switch 2 for the ppp connection to Switch

1. The data module defines a network interface — it associates a link number with a port address and node name for the C-LAN port on Switch 2. It also specifies the node name for the destination node, which is a C-LAN port on Switch 1.

Steps

Begin

Open Data Module form — enter ad da n

add data-module next Page 1 of x DATA MODULE

Data Extension: 3020 Name: _ppp on link 3 to node-1___ BCC: 2 Type: ppp COS: 1 Port: 01a1206 COR: 1 Link: 3_ TN: 1 Enable Link? n

Node Name: node-2_ ____

Subnet Mask: 255.255.255.0

Establish Connection: n

DESTINATION Digits: __________

Node Name: node-1___

CHAP? n

______

[This data module is assigned the next available extension, 3020.] >Enter values

Field Conditions/Comments

Type: This indicates the data-module type for this link. Port: In this example, the C-LAN circuit pack is in slot 01a12; the ppp

Link: The link number must be in the range 1 – 25 , not previously

Enable Link? If you need to add an IP route that uses this node as a gateway,

Name: Information-only; ap pears in list generated by the “list data

connection is through port 06.

assigned on this switch.

this field must be set to leave this field set to

y before adding the IP route. Otherwise

n until the link administration is complete;

that is, until after all data modules and the processor channels are assigned, then set to

module” command.

1 of 2

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Configuration 1: R8r <—ppp—> R8si

Field Conditions/Comments

COS COR: TN: BCC: This is a display-only field. Node Name: The node name for the interface (C-LAN port) defined by this

Subnet Mask:

3 C-LAN Administration

The values for these fields will be specified by the system administrator.

data module. This must be a name entered on the Node Names screen.

Establish Connection?

n means that the switch at the remote end of this connection (Switch 1 in this case) will be responsible for the call setup. Enter y when administering the data module for Switch 1.

Destination

Not needed if the “Establish Connection?” field is set to n

Digits:

Destination Node Name:

Name of the node at the far end (Switch 1) of this connection. Must be a name entered on the Node Names screen.

CHAP? This field enables/disables the Challenge Handshake

Authentication Protocol security mechanism on this link. If you enter y, the system will prompt for a CHAP secret (password).

>Press the ENTER/SAVE key to save and exit

End

2 of 2

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

Configuration 1: R8r <—ppp—> R8si 3 C-LAN Administration

Switch 2 Task — Assign Processor Channels

This task associates data links (hardware) with processor channels (software) on Switch 2.

Steps

Begin

> Open the Processor Channel Assignment form — enter ch com p

change communications-interface processor-channels Page 1 of X

PROCESSOR CHANNEL ASSIGNMENT

Proc Gtwy Interface Destination Session Mach Chan Enable Appl. To Mode Link/Chan Node Port Local/Remote ID 1: n 2: n

21: y

64: n _______ _ __ _____ __________ 0____ ___ ___ __

_______ _ __ _____ __________ 0____ ___ ___ __ _______ _ __ _____ __________ 0____ ___ ___ __

dcs ___ c 3_ 0____ node-1____ 5003 21_12_ 1_

> Enter values

Field Conditions/Comments

Processor Channel 21: (ppp connection to Switch 1) Enable Set to y. Appl. Set to dcs for DCS signaling. Mode Node-2 is the “client” for this session. Set node-1 to “serv e r”

(s).

Interface Link This must match the link number on the node-2 data module

screen in the previous task.

Interface Chan A value of 0 allows any available interface channel to be used

for this connection. The Destination Port number on the Switch-1 Processor Channel screen must also be set to 0.

Destination Node Name of the far-end node for this channel. This must be a

name entered on the Node Names screen. For ppp connections, it must match the Destination Node Name entered on the ppp Data Module screen.

Destination Port This number must match the Interface Channel number

assigned on the Switch-1 Processor Channel screen.

1 of 2

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Configuration 1: R8r <—ppp—> R8si

Field Conditions/Comments

Session - Local The Local and Remote Session numbers can be any value Session - Remote

Mach ID Destination switch ID identified on the dial plan of the

> Submit the screen

End

3 C-LAN Administration

between 1 and 256 (si mod el) or 384 (r model), but the y mu st be consistent between endpoints. For each connection, the Local Session number on this switch must equal the Remote Session number on the remote switch and vice versa.

It is allowed, and sometimes convenient, to use the same number for the Local and Remote Session numbers. It is allowed, but not recommended, to use the same Session numbers for two or more connections.

destination switch.

2 of 2

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

Configuration 1: R8r <—ppp—> R8si 3 C-LAN Administration

Enable links and processor channels

You must enable links and processor channels before the connections can be used. To enable a link, open its data module screen (ch da [ext]) and set the Enable

Link? field to y.

[note: to view a list of assigned data modules and their extensions, enter the “list data-module” com mand (l da)]

To enable the processor channels, open the processor channel screen (ch com p) and set the Enable field to y for each assigned processor channel.

Note: 1. You must disable a link or processor channel before you can ch ange its

parameters.

Note: 2. The busy-out command overrules the data module Enable Link? field. Note: 3. On the C-LAN boards, low-level connectivity can remain intact when

higher-level applications such as DCS are not functioning. For example, an external ping to a C-LAN’s ethernet port could be successful even when the board is busied-out. When debugging connectivity problems, pinging only checks low-level connectivity.

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Configuration 2: R7r (+CMS) <—ethernet—> R7csi

This configuration is a 10BaseT ethernet connection between a DEFINITY ECS R8r and a DEFINITY ECS R8csi switch in a DCS network, which includes routers between the switches. The R8r is connected to a CMS adjunct (the DEFINITY administration for Intuity AUDIX would be similar) via the LAN.

3 C-LAN Administration

Switch 1

DEFINITY

R8r

ECS

C-LAN

LAN

Ethernet

node-1

node-2

CMS

Intuity

AUDIX

node-3

Router

WAN

node-4

node-5

Switch 2

DEFINITY ECS

R8csi

C-LAN

Note: This network has 5 IP nodes: 2 DCS nodes, 2 nodes on the router and one

adjunct node. The router separates two subnets, so IP routes are needed from each switch to the nodes on the other side of the network.

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

Configuration 2: R7r (+CMS) <—ethernet—> R7csi 3 C-LAN Administration

Task Summary

The following tasks need to be completed for Switch 1 and Switch 2:

1 Review prerequisite administration checklist 2 Switch 1 administration

a Assign node names b Assign IP Interfaces c Assign link (via a data module) to the LAN d Assign processor chann e ls

3 Switch 2 admini str a tion

a Enable bus bridge connectivity b Assign node names c Assign IP Interfa ces d Assign link (via a data module) to the LAN e Assign IP routes f Assign pr ocessor channels

4 Intuity AUDIX administration

a Administer the UNIX name and IP address b Administer the switch interface link c Administer extension numbers, channels, and services d Administer subscribers

5 CMS a dministration.

See CentreVu CMS Software Installation and Setup, 585-215-866 and CentreVu CMS Switch Connections and Administration, 585-215-876 for details of CMS setup and administration. (For Intuity AUDIX connections, see Intuity Messaging Solutions LAN Integration with DEFINITY ECS, 585-313-602.)

6 Enable links and processor channels

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Configuration 2: R7r (+CMS) <—ethernet—> R7csi

3 C-LAN Administration

SWITCH 1

DEFINITY ECS R8r

Processor

channels

1 2

384

Processor

UN331B

Processor bus

PktInt

TN1655

Network

control

UN332B

TDM bus

Packet bus

Interface channels

1 5000 5001

5003

64500

Link 2

DS1

TN767/

TN464

C-LAN TN799

Configuration 2

software-defined connections

hardware connections

Voice data

Router

Ethernet

data

LAN

CMS or

Intuity

AUDIX

WAN

Router

SWITCH 2

DEFINITY ECS R8csi

Interface channels

1 5000 5001

x(any)

64500

Link 5

DS1 TN767/ TN464

TDM bus

C-LAN

TN799

Processor

channels

Bus

bridge

Packet bus

1 2

256

Processor

TN798B

node-1

Ext 2377

node-2

192.168.1.125

node-3

192.168.1.97

node-4

192.168.1.39

loc 1co877

192.168.1.124

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

Node-5

Ext 3201

loc 1a0517

192.168.1.51

cydfec2b KLC 101899

Configuration 2: R7r (+CMS) <—ethernet—> R7csi 3 C-LAN Administration

Switch 1 Task — Assign Node Names

This task assigns node names and IP addresses to each node in the network. This screen is administered on Switch 1. A Node Names screen must be administered on each switch in the network.

Note: Enter node names for Intuity AUDIX and MSA adjuncts on page 1. Enter

node names for switches, routers, and CMS starting on page 2.

Steps

Begin

> Open Node Names form — enter ch node-n > Go to page 2

change node names Page 2 of 6 NODE NAMES

Name IP Address Name IP Address default node-1 __ 192.168.1 _.124 _______________ ___.___.___.___ node-2___ node-3_____ node-5__________ 192.168.1 _.51_ _______________ ___.___.___.___

_________ 0__.0__.0__.0__ _______________ ___.___.___.___

192.168.1 _.125 _______________ ___.___.___.___

_____ 192.168.1 _.97_ _______________ ___.___.___.___

> Enter values.

Field Conditions/Comments

Name: Enter node names for the f ollowing 4 nodes:

• node-1: C- LAN Ethernet port on Switch 1

• node-2: CMS node (for consistency, use the host name of the

CMS computer assigned during the CMS setup procedure — see CentreVu CMS Software Installation and Setup, 585-215-866)

• node-3: Interface on the router to the subnet of Switch 1.

• node-5: C- LAN Ethernet port on Switch 2 .

IP Address: The unique IP addresses for the nodes nam ed in the p revious f ield.

See the description of the Subnet Mask field in the next task for information on valid IP addresses.

> Submit the screen

End

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Configuration 2: R7r (+CMS) <—ethernet—> R7csi

3 C-LAN Administration

Switch 1 Task — Assign IP Interfaces

The IP interface for each C-LAN and MedPro board on the switch must be defined on the IP Interfaces form. Each DEFINITY switch in an IP network has one IP Interfaces form.

Steps

Begin

> Open IP Interfaces form — enter ch ip-i

change ip-interfaces Page 1 of 2

IP Interfaces

Inter-region IP connectivity allowed? n Enable Net Eth Pt Type Slot Code Sfx Node Name Subnet Mask Gateway Addr Rgn

y C-LAN 01c08 TN799 B node-1 255.255.255.224 192.168.1_.97_ 1 n 255.255.255.0 n 255.255.255.0 n 255.255.255.0

> Enter values

Field Conditions/Comments

Inter-region IP connectivity allowed?

Enter y to allow IP endpoint s (phones and tru nks) to use MedPro resources administered in regions that are different from the endpoints’ regions.

Enable Eth Pt The Ethernet port must be enabled (y) before it can be used. The

port must be disabled (n) before changes can be made to its

attributes on this screen. Type Enter c-lan or medpro. Slot Enter the slot location for the circuit pack. Code Display only. This field is automatically populated with TN799

for C-LAN or TN802 for MedPro. Sfx Display only. This field is automatically populated with B for

the TN802 and TN799. Node name Enter the unique node n a me f or th e IP interf ace. Th e no de n ame

here must already be administered on the Node Names screen

1 of 2

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

Configuration 2: R7r (+CMS) <—ethernet—> R7csi 3 C-LAN Administration

Field Conditions/Comments

Subnet Mask Enter the subnet mask associated with the IP address for this IP

interface.

The IP address for node-1, specified on the Node Names screen,

is 192.168.1.124. The 192 in the first octet puts this address in

the range of “Class C” addresses, which means the first 3 octets

are used for the network ID and the fourth octet is used for host

IDs.

The subnet mask defines the network and host parts of the IP

addresses. In the Subnet Mask for this example (192 .168.1.224),

the 224 in the fourth octet indicates that 3 high-order bits from

the fourth octet are used to define subnets on the network

192.168.1 (224 = 128+64+32 = 11100000). The first 3 bits are

used for subnet IDs and the last 5 bits are used for host IDs.

Eight subnets can be defined with 3 bits and each subnet can

have a maxim um of 32 hosts, de fined with the remaining 5 bits.

Of these, only 6 subnets with 30 hosts each are usable.

The usable IP addresses in the 6 subnets have the following

ranges of values for the fourth octet: 33–62, 65–94, 97–126,

129–158, 161–190, and 193–222. The IP address for this (node-1) IP interface, 192.168.1.124, is on the third subnet because 124 lies in the rang e 9 7–1 26. Note th at no de 2 (adjunct,

192.168.1 .125) and no de 3 (router, 192.168.1. 97) are both a lso on the third subnet. Node 4 (192.168.1.51) and node 5 (192.168.1.39) are both on the first subnet.

The first and last IP addresses in each subnet are not usable as host addresses because they have all 0’s or all 1’s for host IDs. For example, in the third subnet, the fourth octet of the first IP address is 96 (= 01100000 address is 127 (= 01111111

) and the fourth octet of the last IP

The “network address” of a subnet is the first IP address (the all 0’s host ID) of that subnet. In this example, the subnet addres ses of the six subnets are — 1st: 192.168.1.32 2nd: 192.168.1.64

3rd: 192.168.1.96 4th: 192.168.1.128 5th: 192.168.1.160 6th: 192.168.1.192.

See Chapter 1 for more information on IP addresses and subnetting.

Gateway Addr Enter the address of a network node that will serve as the default

gateway for the IP interface.

Net Rgn Enter the region number for this IP interface.

> Submit the screen

End

2 of 2

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

Configuration 2: R7r (+CMS) <—ethernet—> R7csi

3 C-LAN Administration

Switch 1 T ask — Assign Link via ethernet Data Module to the LAN

This task administers an ethernet data module for the ethernet connection to the CMS

adjunct and to Switch 2. The data module defines a network interface — it associates a link number with a port address and node name for the C-LAN port used for this connection.

Steps

Begin

> Open Data Module form — enter a da n

add data-module next Page 1 of X DATA MODULE

Data Extension: 2377 Name: ethernet on link 2

Port: 01c0817_ Link: 2

Network uses 1’s for broadcast addresses? y

Type: ethernet

> Enter values

Field Conditions/Comments

Type: This indicates the data-module type for this link. Port: Ethernet connections must be assigned to port 17 on the C-LAN

circuit pack.

Link: The link number must be in the range 1 – 33 (for G3r), not

previously assigned on this switch.

Name: This field is information-only; it appears in lists generated by the

“list data module” command.

Network uses 1’s for broadcast addresses?

> Submit the screen

End

Administration for Network Connectivity

555-233-504 — Issue 1 — Apr il 2000 CID: 77730

Configuration 2: R7r (+CMS) <—ethernet—> R7csi 3 C-LAN Administration

Switch 1 Task — Assign Processor Channels

This task associates data links (hardware) with processor channels (software) on the node 1 switch.

Steps

Begin

> Open the Processor Channel Assignment form — enter ch com p

change communications-interface processor-channels Page 1 of X

PROCESSOR CHANNEL ASSIGNMENT

Proc Gtwy Interface Destination Session Mach Chan Enable Appl. To Mode Link/Chan Node Port Local/Remote ID 1: y 2: n 3: n _______ _ __ _____ __________ 0____ ___ ___ __ 4: n :

12: y

64: n

mis____ s 2_ 5001__ node-2____ 0____ 1 _ 1_ __ _______ _ __ _____ __________ 0____ ___ ___ __

_______ _ __ _____ __________ 0____ ___ ___ __

dcs ___ s 2_ 5003__ node-5____ 0____ 12_21_ 2_

________ _ __ _____ __________ 0____ ___ ___ __

> Enter values

Field Conditions/Comments

Processor Channel 1: (connection to CMS) Enable Set to y. Appl. Enter mis for the CMS connection on Processor Channel 1. Mode Set the Mode to s (“server”) on both switches for con nections

to CMS.

Interface Link This must match the link number assigned on the node-1 data

module screen.

Interface Chan For TCP/IP, interface channel numbers are in the range 5000

– 64500. The recommended values are: 5001 for CMS, 5 002 for Intuity

AUDIX, and 5003 for DCS connections that are not gateways. These three values should be reused for multiple instances of these applications; for example, if there are two Intuity AUDIX’s, use 5002 for both; or if there are four DEFINITY ECS’s, use 5003 for all four. The combination of Link, Interface Channel, and Mach ID must be unique.

The recommended values for gateway switc hes is 6001–6099. The interface channel number must be unique for each gateway.

1 of 3

Administration for Network Connectivity

CID: 77730 555-233-504 — Issue 1 — April 2000

AT&T Definity Enterprise R 8-2 Admin for Network - Connectivity

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Preface

Purpose

Audience

Issue Status

Organization

Terminology

How to order more copies

Tell us what you think

How to Order Books

How to Comment on This Book

Trademarks

1 Networking Overview

DEFINITY Switch Connectivity

Connectivity Overview

DEFINITY Connection types and capacities

IP Softphones

Physical Addressing

Logical Addressing

When to use IP routes

2 H.323 Trunks

Overview

IP Solutions

IP-Connected Trunks

IP Softphones

H.323 Trunk Administration

Enabling Administration

H.323 Trunk Administration — Task Summary

H.323 Trunk Administration — Task Detail

Task 2 — Define IP Interfaces

Troubleshooting IP Solutions

H.323 Trunk Problem Solving

IP Softphone Problem Solving

3 C-LAN Administration

Overview

Supported Switches and Adjuncts

Checklist for Prerequisite Administration

Configurations

Organization of this chapter

Supported Switches and Adjuncts

Intuity AUDIX LAN Setup Summary

CMS LAN Setup Summary

Task Summary

Prerequisite Administration

Task Summary