Definity ECS Admin for Network Connectivity.pdf - TextFiles.com

More documents

Recommendations

Info

Networking Screens A Screens Reference Enable Eth Pt Used to enable or disable the C-LAN or MedPro IP Ethernet port. Valid Values y/n Usage 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. If an enabled Ethernet port is changed to disabled, all signaling and/or media connections will be removed and the associated calls will be torn down. The busy-out command applied to the circuit pack for the interface overrules the Enable Eth Pt field. Type Specifies the type of circuit pack for the IP network interface (C-LAN or MedPro). Slot Specifies the location of the circuit pack for the IP network interface in the standard CCcss format (CC = cabinet number, c = carrier letter, ss = slot number). Code Display only. Specifies the board code of the circuit pack for the IP interface. This field is automatically populated with TN799 for C-LAN or TN802 for MedPro. Sfx Display only. Specifies board code suffix. This field is automatically populated with B for the TN802 and the TN799. Node Name The unique node name for the IP interface. The node name must be on the Node Names screen (pages 2–6 only; node names on page 1 of the Node Names screen cannot be used in this field). 248 Administration for Network Connectivity CID: 77730 555-233-504 — Issue 1 — April 2000
Networking Screens A Screens Reference Subnet Mask The subnet mask determines which part of an IP address is the network identifier and which part is the host identifier. The subnet mask is associated with the IP address administered on the Node Names screen for the IP interface identified by the Node Names field on this screen. See Chapter 1 for more information on IP addresses and subnetting. Valid Values The valid values of the subnet mask depend on the IP address that the subnet mask is applied to — in this case, the IP address on the Node Names screen that is associated with the name entered in the Node Name field. In general, each octet value must be one of the following numbers: 255 or 0, corresponding to the network and host portions of an IP address; or 192, 224, 240, 248, or 252, corresponding to using 2, 3, 4, 5, or 6 bits from the host ID for the subnet ID. Usage This field can be used to subdivide a network into 2 or more subnetworks. The subnet mask consist of a string of n contiguous 1’s followed by a string of 32–n contiguous 0’s. When applied to a 32-bit IP address, the subnet mask indicates that the first n bits of the address form the network ID and the next 32–n bits form the host ID portion of the address. The following default values for the subnet mask are used for no subnetting: Class A addresses: 255.0.0.0 Class B addresses: 255.255.0.0 Class C addresses: 255.255.255.0 Gateway Address Specifies the address of a network node that will serve as the default gateway for the IP interface. Valid Value An IP address of a bridge or router on the network that is directly connected to the IP interface. The gateway address must be administered on the Node Names screen. Usage The default gateway enables communication with nodes on (sub)networks that are different from the (sub)network of the IP interface. A default gateway makes use of explicit IP routes unnecessary. If left blank, this node (this IP interface) can communicate with nodes on different (sub)networks only if explicit IP routes (on the IP Routing screen) are defined — communication with nodes on the same (sub)network is not affected. With the Gateway Address left blank, you can enable communications with individual nodes on other (sub)networks by creating host IP routes to them. Or you can enable communication with all nodes on a different (sub)network by defining a network IP route to that (sub)network. You can define a combination of network and host IP routes to enable communications to all nodes on some (sub)networks and individual nodes on other (sub)networks. Administration for Network Connectivity 555-233-504 — Issue 1 — April 2000 CID: 77730 249
Page 1 and 2:
DEFINITY ® Enterprise Communicatio
Page 3 and 4:
Contents Preface Purpose. . . . . .
Page 5 and 6:
Contents Switch-Node 3 Administrati
Page 7 and 8:
Contents QSIG . . . . . . . . . . .
Page 9 and 10:
Preface This book describes how to
Page 11 and 12:
Issue Status Preface ppp Data Modul
Page 13 and 14:
Issue Status Preface Reorganization
Page 15 and 16:
Terminology Preface Terminology The
Page 17 and 18:
Tell us what you think Preface Tell
Page 19 and 20:
Trademarks Preface Trademarks The f
Page 21 and 22:
1 Networking Overview This chapter
Page 23 and 24:
DEFINITY Switch Connectivity 1 Netw
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
IP Softphones 1 Networking Overview
Page 33 and 34:
IP Addressing 1 Networking Overview
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
2 H.323 Trunks This chapter describ
Page 53 and 54:
H.323 Trunk Administration 2 H.323
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Troubleshooting IP Solutions 2 H.32
Page 73 and 74:
3 C-LAN Administration This chapter
Page 75 and 76:
Overview 3 C-LAN Administration ✔
Page 77 and 78:
Overview 3 C-LAN Administration TCP
Page 79 and 80:
Overview 3 C-LAN Administration Int
Page 81 and 82:
Configuration 1: R8r R8si 3 C-LAN
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Configuration 2: R7r (+CMS) R7csi
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Configuration 3: R8si R8r Gateway
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Configuration 4: R8csi R8si Gatewa
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Configuration 5A: R8csi R8r (one C
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Configuration 5B: R8csi R8r (2 C-L
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218: Configuration 5B: R8csi R8r (2 C-L
Page 223 and 224: 4 Networking Example This chapter p
Page 225 and 226: Overview 4 Networking Example Task
Page 227 and 228: Network Map 4 Networking Example Ne
Page 229 and 230: Switch-Node 1 Administration 4 Netw
Page 261 and 262: Intuity Translations for DCS AUDIX
Page 263 and 264: A Screens Reference This appendix g
Page 265 and 266: Networking Screens A Screens Refere
Page 267: Networking Screens A Screens Refere
Page 313 and 314: Other Networking-Related DEFINITY S
Page 319 and 320:
Other Networking-Related DEFINITY S
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
B Private Networking This appendix
Page 333 and 334:
Distributed Communications System B
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
ISDN Feature Plus B Private Network
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
QSIG B Private Networking QSIG Basi
Page 383 and 384:
QSIG B Private Networking Call Offe
Page 385 and 386:
QSIG B Private Networking Other QSI
Page 387 and 388:
QSIG B Private Networking QSIG CAS
Page 389 and 390:
QSIG B Private Networking QSIG Prot
Page 391 and 392:
QSIG B Private Networking Setting U
Page 393 and 394:
QSIG B Private Networking 10 Admini
Page 395 and 396:
QSIG B Private Networking Call Comp
Page 397 and 398:
QSIG B Private Networking Note: •
Page 399 and 400:
QSIG B Private Networking QSIG Inte
Page 401 and 402:
QSIG B Private Networking • Data-
Page 403 and 404:
QSIG B Private Networking • Inter
Page 405 and 406:
QSIG B Private Networking Called/Bu
Page 407 and 408:
QSIG B Private Networking • QSIG
Page 409 and 410:
QSIG B Private Networking • Atten
Page 411 and 412:
QSIG B Private Networking • Confe
Page 413 and 414:
QSIG B Private Networking • Exten
Page 415 and 416:
Centralized Voice Mail Via Mode Cod
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Japan TTC Q931-a Private Networking
Page 423 and 424:
C Security Issues This Appendix bri
Page 425 and 426:
Network Security Issues C Security
Page 427 and 428:
D Capacities and Performance This A
Page 429 and 430:
D Capacities and Performance Perfor
Page 431 and 432:
D Capacities and Performance Number
Page 433 and 434:
E C-LAN Installation This chapter p
Page 435 and 436:
E C-LAN Installation Install C-LAN
Page 437 and 438:
F IP Trunk Installation and Adminis
Page 439 and 440:
IP Trunk Administration F IP Trunk
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Page 453 and 454:
Procedures for Extension Dialing Be
Page 455 and 456:
DCS over IP Trunk F IP Trunk Instal
Page 457 and 458:
Page 459 and 460:
Page 461 and 462:
Page 463 and 464:
Page 465 and 466:
Page 467 and 468:
DCS over IP Trunk Making Calls to t
Page 469 and 470:
Administration for Network Connecti
Page 471 and 472:
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Page 479 and 480:
G References This Appendix lists th
Page 481 and 482:
G References Installation and maint
Page 483 and 484:
G References CentreVu CMS The follo
Page 485 and 486:
Glossary A AAR See Automatic Altern
Page 487 and 488:
B8ZS Glossary B B8ZS See Bipolar 8
Page 489 and 490:
Call Management System (CMS) Glossa
Page 491 and 492:
COR Glossary COR See Class of Restr
Page 493 and 494:
DID Glossary DID Direct Inward Dial
Page 495 and 496:
facility Glossary F facility A tele
Page 497 and 498:
interserver routing table Glossary
Page 499 and 500:
link-access procedure on the D-chan
Page 501 and 502:
NEMA Glossary NEMA National Electri
Page 503 and 504:
PBX Glossary PBX Private Branch Exc
Page 505 and 506:
outing plan Glossary routing plan R
Page 507 and 508:
T-carrier Glossary T-carrier A hier
Page 509 and 510:
virtual circuit (virtual connection
Page 511 and 512:
Index A AAR and ARS features intera
Page 513 and 514:
D Index Centralized Attendant Servi
Page 515 and 516:
E Index E Distributed Communication
Page 517 and 518:
L Index L ISDN Feature Plus feature
Page 519 and 520:
R Index QSIG Call Transfer feature
Page 521 and 522:
U Index U trunk access codes (TAC)
Page 523:
We’d like your opinion. Lucent Te
show all

Definity ECS Admin for Network Connectivity.pdf - TextFiles.com

Create successful ePaper yourself

Delete template?

Save as template?