DEFINITY® Enterprise Communications Server Release 8.
Copyright 2000, Lucent Technologies All Rights Reserved Printed in U.S.A. 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 unauthorized use of your telecommunications system by an unauthorized party, for example, persons other than your company’s employees, agents, subcontractors, or persons working on your company’s behalf.
Contents Preface ix Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Issue Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Organization . . . . . . . . . . . . . . . . . . . .
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 . . . . . . . .
Contents Switch-Node 3 Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 DS1 Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Synchronization Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Signaling Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Circuit Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Signaling Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 ISDN TSC Gateway Channel Assignments . . . . . . . . . . . . . . . . . . . . . . . . 291 Other Networking-Related DEFINITY Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293 Communication Interface Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents QSIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 QSIG Basic Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 QSIG Basic Supplementary Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 QSIG Centralized Attendant Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 QSIG Supplementary Services with Rerouting . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . . . . . . . .
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.
Issue Status Screen Changes Preface 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.
Issue Status Preface 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: Type: Port: Link: Enable Link? 1994 ppp 01c1502 4_ n Name: COS: COR: TN: _ppp on link 4 to node 4___ 1 1 1 BCC: 2 Node Name: ppp14_____ Subnet Mask: 255.255.255.
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.
Issue Status Reorganization Preface 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.
Organization Preface Organization This document is organized into four chapters and seven appendixes. Chapter 2 gives the essential information needed to administer H.323 trunk connections. Chapter 1 – Overview Appendix C Security A brief discussion of security issues as related to networking. An overview of DEFINITY Connectivity and IP Addressing Appendix D – Capacity and Performance Chapter 2 – H.
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.
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.
Tell us what you think Preface 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 Product Documentation Group Room 22-2H15 11900 North Pecos Street Denver, CO 80234 USA Fax to: 303-538-1741 Send email to: document@drmail.lucent.
Where to Call for Technical Support Preface Where to Call for Technical Support Use the telephone numbers in the following table for technical support.
Trademarks Preface Trademarks 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 is a registered tra
Trademarks xx Preface CID: 77730 Administration for Network Connectivity 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.
1 DEFINITY Switch Connectivity Networking Overview Networks When two or more switches are connected via tie trunks, they form a private network. 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.
1 DEFINITY Switch Connectivity Networking Overview 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.
1 DEFINITY Switch Connectivity Figure 1.
1 DEFINITY Switch Connectivity Networking Overview 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 interface between the switch processor and the transmission facilities.
1 DEFINITY Switch Connectivity 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.
1 DEFINITY Switch Connectivity 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.
1 DEFINITY Switch Connectivity R8si model Networking Overview The following table shows the hardware required for an upgrade to an R8si. Connection Type BX.
1 DEFINITY Switch Connectivity Networking Overview DEFINITY Connection types and capacities This subsection gives an overview of the types of connections that can be set up with DEFINITY switches and adjuncts and capacities for some connectivity parameters. Types of connections 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 ISDN-PRI DCS+ H.
1 DEFINITY Switch Connectivity DEFINITY Capacities Networking Overview The following table shows maximum 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.
1 IP Softphones 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 DEFINITY 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.
1 IP Softphones Networking Overview 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 Link Mode: as-needed 4 Install the IP Softphone software on the user’s PC 5 Install an H.
1 IP Addressing Networking Overview IP Addressing This section describes IP addressing, subnetting, and routing. Physical Addressing The Address Resolution Protocol (ARP) software on 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.
1 IP Addressing Conversion between binary and decimal IP Address Classes Networking Overview Conversion from binary to decimal notation is accomplished by adding the powers of 2 corresponding to the 1’s positions in each byte: 27 = 128 26 = 64 25 = 32 24 = 16 23 = 8 22 = 4 21 = 2 20 = 1 194 = 1 1 0 0 0 0 1 0 13 = 0 0 0 0 1 1 0 1 219 = 1 1 0 1 1 0 1 1 7= 0 0 0 0 0 1 1 1 The IP address space (232 or about 4.
1 IP Addressing 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 Class A 7 bits 126 Networks: 1 to 126 Host ID Range Total IP Addresses 24 bits 16.
1 IP Addressing Networking Overview Subnetting Subnetting is the grouping of IP addresses associated with a network 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 individual subnets.
1 IP Addressing 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.
1 IP Addressing Class-C subnets Networking Overview The following table shows that Class-C IP addresses can have 5 subnetting schemes, each with a different number of subnets per network. The first and last subnet, formed 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. Binary No. of Subnet No. of Hosts Usable IP ID per Addresses (4th Subnet Octet) No. Subnet bits No.
1 IP Addressing 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.
1 IP Addressing 192 11000000 192 11000000 192 11000000 Subnet mask 255 11111111 Networking Overview 168 10101000 50 00110010 168 50 10101000 00110010 168 50 10101000 00110010 255 255 11111111 11111111 75 01001011 91 01011011 100 01100100 224 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.
1 IP Addressing Valid subnet masks Networking Overview The valid subnets for each Class of address are: 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.
1 IP Addressing Networking Overview 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.
1 IP Addressing Networking Overview 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.
1 IP Addressing IP Routing Screen Networking Overview The following diagram shows the IP Routing screen. display ip-route 1 Page 1 of 1 IP ROUTING Route Number: Destination Node: Gateway: C-LAN Board: Metric: Route Type: 1 clan-a2_ router-1 1b01 0 host ___ 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.
1 IP Addressing IP Route Examples Networking Overview 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.
1 IP Addressing Networking Overview 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.
1 IP Addressing 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. Switch A IP Route IP Route Node Destination Gateway Connections Node Node 2 —> 7 3 —> 4 7 4 Comments 5 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.
1 IP Addressing Networking Overview 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.
1 IP Addressing 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. Node IP Route IP Route Switch Connec- Destination Gateway tions Node Node 1 —> 6 6 4 Route Type host 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.
1 IP Addressing 30 CID: 77730 Networking Overview Administration for Network Connectivity 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.
2 Overview 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 using IP connectivity provide cost-reduction and simplified management. Benefits include a reduction in long distance voice and fax expenses, facilitation of global communications, full-function networks with data and voice convergence, and network optimization by using the existing network resources. H.
2 H.323 Trunk Administration H.323 Trunks H.323 Trunk Administration This section describes the administration steps needed to setup H.323 trunks. The first subsection 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.
2 H.323 Trunk Administration Maintenance-Related System Parameters H.323 Trunks Four parameters on the Maintenance-Related System Parameters screen set threshold values for network performance: page 4 • Roundtrip Propagation Delay (sec) • Packet Loss (%) • Ping Test Interval (sec): 20 • Pings per Measurement Interval: 10 High: 800_ Low: 400_ High: 40__ Low: 15__ These parameters have no effect unless the bypass function is activated on the Signaling Group screen.
2 H.323 Trunk Administration H.323 Trunks 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 your network is equipped with the appropriate data filtering devices, audio data can be segregated from other data traffic to improve quality of service.
2 H.323 Trunk Administration 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.
2 H.323 Trunk Administration Signaling Group H.323 Trunks Each H.323 trunk must be assigned to a signaling group.
2 H.323 Trunk Administration IP Media Parameters H.323 Trunks 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.
2 H.323 Trunk Administration H.323 Trunks Task 1 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 clan-a1______ clan-a2______ default medpro-a1___ medpro-a2___ medpro-a3___ medpro-b1___ ___ IP Address 192.168.10_.31_ 192.168.20_.31_ 0 .0 .0 .0 192.168.10_.81_ 192.168.20_.81_ 192.168.10_.82_ 192.168.10_.83_ ___.___.___.
2 H.323 Trunk Administration 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.
2 H.323 Trunk Administration H.323 Trunks Field Conditions/Comments Subnet Mask Enter the subnet mask associated with the IP address for this IP interface. (The IP address is associated with the node name on the Node Names screen). 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.
2 H.323 Trunk Administration 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.
2 H.323 Trunk Administration 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.
2 H.323 Trunk Administration 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.
2 H.323 Trunk Administration 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 previous releases and are described in the Administrator’s Guide.
2 H.323 Trunk Administration H.
2 H.323 Trunk Administration H.323 Trunks > Enter group 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.
2 H.323 Trunk Administration 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.
2 H.323 Trunk Administration H.323 Trunks 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.
2 Troubleshooting IP Solutions H.323 Trunks Troubleshooting IP Solutions This section provides solutions to some commonly encountered problems with H.323 trunks and IP Softphones. 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.
2 Troubleshooting IP Solutions H.323 Trunks 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 Private NW TGA1 TGB1 SGB1 SGA1 Public NW TGA2 Trunk Group for Channel Selection = TGB1 TGB2 Switch A Figure 3.
2 Troubleshooting IP Solutions H.323 Trunks IP Softphone Problem Solving Codecs used with Netmeeting 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 happen unexpectedly when using NetMeeting — when the G.
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 book.
3 Overview 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.
3 Overview ✔ 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.
3 Overview ✔ 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.
3 Overview C-LAN Administration 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.
3 Overview 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, " A dotted line, " ", indicates voice and call-setup data. ", indicates DCS signaling data.
3 Overview C-LAN Administration 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.
3 Configuration 1: R8r <—ppp—> R8si Configuration 1: R8r C-LAN Administration <—ppp—> R8si Configuration 1 is a ppp connection between a DEFINITY ECS R8r and a DEFINITY ECS R8si switch in a DCS network.
3 Configuration 1: R8r <—ppp—> R8si C-LAN Administration 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 Configuration 1: R8r <—ppp—> R8si 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. 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.
3 Configuration 1: R8r <—ppp—> R8si 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.
3 Configuration 1: R8r <—ppp—> R8si Field C-LAN Administration 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.
3 Configuration 1: R8r <—ppp—> R8si 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 Chan Enable Appl.
3 Configuration 1: R8r <—ppp—> R8si 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 value of 0 allows any available interface channel on the destination node to be used for this connection.
3 Configuration 1: R8r <—ppp—> R8si 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. 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.
3 Configuration 1: R8r <—ppp—> R8si 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.
3 Configuration 1: R8r <—ppp—> R8si Field C-LAN Administration Conditions/Comments COS COR: The values for these fields will be specified by the system administrator. TN: BCC: 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 entered on the Node Names screen.
3 Configuration 1: R8r <—ppp—> R8si 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 Chan Enable Appl.
3 Configuration 1: R8r <—ppp—> R8si C-LAN Administration Field Conditions/Comments Session - Local The Local and Remote Session numbers can be any value between 1 and 256 (si model) or 384 (r model), but they 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. Session - Remote It is allowed, and sometimes convenient, to use the same number for the Local and Remote Session numbers.
3 Configuration 1: R8r <—ppp—> R8si 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.
3 Configuration 2: R7r (+CMS) <—ethernet—> R7csi C-LAN Administration 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.
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 b c d Assign node names Assign IP Interfaces Assign link (via a data module) to the LAN Assign processor channels 3 Switch 2 administration a b c d e f Enable bus bridge connectivity Assign node names Assign IP Interfaces Assign link (via a data module) to the LAN Assign IP route
3 Configuration 2: R7r (+CMS) <—ethernet—> R7csi C-LAN Administration Configuration 2 SWITCH 1 SWITCH 2 DEFINITY ECS R8csi DEFINITY ECS R8r Processor channels Interface channels 1 2 software-defined connections Interface channels Processor channels 1 5000 5001 1 5000 5001 1 2 5003 x(any) 64500 64500 Link 2 Link 5 12 21 384 256 hardware connections Processor UN331B Processor bus PktInt TN1655 Network control UN332B DS1 TN767/ TN464 DS1 TN767/ TN464 Voice data Processor TN798B
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. 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.
3 Configuration 2: R7r (+CMS) <—ethernet—> R7csi 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.
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.
Configuration 2: R7r (+CMS) <—ethernet—> R7csi 3 C-LAN Administration Switch 1 Task — 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.
3 Configuration 2: R7r (+CMS) <—ethernet—> R7csi 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 Chan Enable Appl.
Configuration 2: R7r (+CMS) <—ethernet—> R7csi 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. Destination Port A value of 0 allows any available interface channel on the destination node to be used for this connection. The Interface Channel number on the Switch-2 Processor Channel screen must also be set to 0.
Configuration 2: R7r (+CMS) <—ethernet—> R7csi 3 C-LAN Administration Field Conditions/Comments Session - Local The Local and Remote Session numbers can be any value between 1 and 256 (si model) or 384 (r model), but they 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.
3 Configuration 2: R7r (+CMS) <—ethernet—> R7csi C-LAN Administration Switch 2 Task — Enable Bus Bridge Connectivity This task enables the bus bridge functionality on the C-LAN circuit pack to provide a path between the packet bus and the processor. Note: Bus Bridge Connectivity is used on the csi model only. This task may have been completed when the C-LAN circuit pack was installed.
Configuration 2: R7r (+CMS) <—ethernet—> R7csi 3 C-LAN Administration Switch 2 Task — Assign Node Names This task assigns node names and IP addresses to each node in the network on the Node Names screen. This screen is administered on Switch 2. A Node Names screen must be administered on each switch in the network. The node names and IP addresses in a network should be assigned in a logical and consistent manner from the point of view of the whole network.
3 Configuration 2: R7r (+CMS) <—ethernet—> R7csi C-LAN Administration Switch 2 Task — 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.
3 Configuration 2: R7r (+CMS) <—ethernet—> R7csi C-LAN Administration Field Conditions/Comments Subnet Mask Enter the subnet mask associated with the IP address for this IP interface. (The IP address is associated with the node name on the Node Names screen). Since the node-1 and node-5 IP interfaces are on the same network (192.168.1), they must be assigned the same subnet mask. In this example, the subnet mask 255.255.255.224 divides the network 192.168.10 into 6 (usable) subnets.
Configuration 2: R7r (+CMS) <—ethernet—> R7csi 3 C-LAN Administration Switch 2 Task— Assign Link via ethernet Data Module to the LAN This task administers an ethernet data module on Switch 2 for the ethernet connection to Switch 1. The data module associates a link number with a port address, extension number, and node name for the C-LAN port used for this connection.
3 Configuration 2: R7r (+CMS) <—ethernet—> R7csi C-LAN Administration Switch 2 Task — Assign IP Route (to Switch 1) This task specifies a route for packets sent by the node 5 IP interface (the ethernet port on the switch-2 C-LAN board) to the nodes 1 and 2. An IP route is required because node 5 is on a different subnetwork from nodes 1&2 (as defined in the Subnet Mask field on the IP Interfaces screen), and the Gateway Address field for node 5 on the IP Interfaces screen was left blank.
Configuration 2: R7r (+CMS) <—ethernet—> R7csi Note: 3 C-LAN Administration We could have defined 2 individual IP routes, one each to node-1 and node-2, instead of this IP route. However, the network route is easier because we need only one. The network route enables packets to get to any IP address on the 192.168.1.96 subnet (that is, addresses 192.168.1.97 through 192.168.1.126), so no other IP routes are needed.
3 Configuration 2: R7r (+CMS) <—ethernet—> R7csi 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 Chan Enable Appl.
Configuration 2: R7r (+CMS) <—ethernet—> R7csi 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. Destination Port A value of 0 allows any available interface channel on the destination node to be used for this connection. The Interface Channel number on the Switch-2 Processor Channel screen must also be set to 0.
3 Configuration 2: R7r (+CMS) <—ethernet—> R7csi C-LAN Administration Field Conditions/Comments Session - Local The Local and Remote Session numbers can be any value between 1 and 256 (si model) or 384 (r model), but they 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.
Configuration 2: R7r (+CMS) <—ethernet—> R7csi • 3 C-LAN Administration Apply the coverage path to stations, and if the switch is an r model, specify the node name of the Intuity system for each station that has a voice mailbox on the Intuity system. Intuity system administration The following procedures must be done on the Intuity system: Administer the TCP/IP Network Addressing • Administer the UNIX name and IP address for the Intuity system.
3 Configuration 2: R7r (+CMS) <—ethernet—> R7csi Administer the Switch Interface C-LAN Administration You must now administer the switch interface. Do the following. 1 Starting at the Lucent INTUITY Main menu, select: > Switch Interface Administration > Call Data Interface Administration > Switch Link Administration The system responds with the Switch Interface Administration window.
3 Configuration 2: R7r (+CMS) <—ethernet—> R7csi C-LAN Administration Administer Subscribers Subscribers must be administered on the Intuity system. For more information on this, see the Lucent INTUITY Messaging Solutions Release 5 documentation. The following screens show examples of subscriber screens on the Intuity system.
3 Configuration 2: R7r (+CMS) <—ethernet—> R7csi C-LAN Administration Worksheet A: Names and IP Addresses for Lucent Intuity System Complete the information on this worksheet to collect information required to administer the Lucent INTUITY system for integration with the switch.
3 Configuration 2: R7r (+CMS) <—ethernet—> R7csi C-LAN Administration Worksheet B: LAN Data for the Lucent Intuity System Complete the information on this worksheet to administer the Lucent INTUITY system for integration with the switch. Field Recommended Your Entry Lucent INTUITY System Switch Interface Administration Window Extension Length 4 Use the extension length from the switch dial plan 1 Host Switch Number Use 1 if the integration supports only one DEFINITY switch.
Configuration 2: R7r (+CMS) <—ethernet—> R7csi 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.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si Configuration 3: C-LAN Administration R8si<—x.25 —> R8r Gateway <—ethernet—> R8si In this configuration, a DEFINITY ECS R8r acts as a gateway between two other nodes — one connected via X.25 to an R8si and the other via ethernet to another R8si. Switch 2 DEFINITY ECS R8si Switch 1 PGATE PI BX.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si C-LAN Administration 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.
Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> 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. A node is defined as any of the following — a C-LAN port, a bridge or router, a CMS ethernet port, or an Intuity AUDIX or other MSA network interface card.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si C-LAN Administration Switch 1 Task — Assign pdm Data Module This task administers a pdm data module for the connection between the PGATE board and the DS1 board for the connection to node-2. The data module associates a link number with a port address and extension number for the PGATE port used for this connection.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si Field Conditions/Comments Secondary data modules? Enter n. Connected To Enter dte. C-LAN Administration Keep the default values for the rest of the fields.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si C-LAN Administration Switch 1 Task — Assign Link via x.25 Data Module to Switch 2 This task administers an x.25 data module for the connection to node 2. The data module associates a link number with a port address and extension number for the PGATE port used for this connection.
Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si 3 C-LAN Administration Field Conditions/Comments Name: Information-only; appears in list generated by the “list data module” command. COS: COR: The values for these fields will be specified by the system administrator. TN: DTE/DCE: The DTE/DCE assignments must be opposites on the two ends of the connection. Use dce for node 2. Enable Link? Set to y after the processor channels have been assigned.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si C-LAN Administration Switch 1 Task — Assign IP Interfaces The IP interface for each C-LAN board on the switch must be defined on the IP Interfaces form. Each DEFINITY switch in an IP network has one IP Interfaces form.
Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si 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 is associated with the node name on the Node Names screen). In this example, leave the default subnet mask, 255.255.255.0, which indicates no subnetting for a Class C IP address.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si C-LAN Administration Switch 1 Task — Assign Link via ethernet Data Module to the LAN This task administers an ethernet data module for ethernet connections. The data module associates a link number with a port address, extension number, and node name for the C-LAN port used for this connection.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si 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 Processor Channel Assignment form — enter ch com p change communications-interface processor-channels Page 1 of X PROCESSOR CHANNEL ASSIGNMENT Proc Gtwy Chan Enable Appl.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si C-LAN Administration Field Conditions/Comments Session - Local The Local and Remote Session numbers can be any value between 1 and 256 (si model) or 384 (r model), but they 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.
Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si 3 C-LAN Administration Field Conditions/Comments 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.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si C-LAN Administration Field Conditions/Comments Destination Port A value of 0 allows any available interface channel on the destination node to be used for this connection. The Interface Channel number on the Switch-3 Processor Channel screen must also be set to 0. Session - Local For each connection, the Local Session number on this switch must equal the Remote Session number on the remote switch and vice versa.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si C-LAN Administration Switch 2 Task — Assign Link via procr-intf Data Module to Switch 1 This task administers a processor-interface data module for the x.25 connection to node 1. The data module associates a link number with a physical channel number and extension number for the PI port used for this connection.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si C-LAN Administration Field Conditions/Comments Enable Link?: Set to y after the processor channels have been assigned. Maintenance Extension: Specified on dial plan. Destination Number: TAC (812) + extension (2102) of the data module on the far end that will establish the connection. 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.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si 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 Processor Channel Assignment form — enter ch com p change communications-interface processor-channels Page 1 of X PROCESSOR CHANNEL ASSIGNMENT Proc Gtwy Chan Enable Appl.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si C-LAN Administration Field Conditions/Comments Session - Local The Local and Remote Session numbers can be any value between 1 and 256 (si model) or 384 (r model), but they 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.
Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si 3 C-LAN Administration Switch 3 Task — Assign Node Names This task assigns node names and IP addresses to each node in the network. This screen is administered on Switch 3. A Node Names screen must be administered on each switch in the network. 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.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si C-LAN Administration Switch 1 Task — Assign IP Interfaces The IP interface for each C-LAN board on the switch must be defined on the IP Interfaces form. Each DEFINITY switch in an IP network has one IP Interfaces form.
Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si 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 is associated with the node name on the Node Names screen). In this example, leave the default subnet mask, 255.255.255.0, which indicates no subnetting for a Class C IP address.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si C-LAN Administration Switch 3 Task — Assign Link via ethernet Data Module to the LAN This task administers an ethernet data module on Switch 3 for the ethernet connection to Switch 1. The data module associates a link number with a port address, extension number, and node name for the C-LAN port used for this connection.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si C-LAN Administration Switch 3 Task — Assign Processor Channels This task associates data links (hardware) with processor channels (software) on Switch 3. Steps Begin > Open Processor Channel Assignment form — enter ch com p change communications-interface processor-channels Page 1 of X PROCESSOR CHANNEL ASSIGNMENT Proc Gtwy Chan Enable Appl.
3 Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> R8si C-LAN Administration Field Conditions/Comments Destination Port The Destination Port number must match the Interface Channel number for this connection on the Switch-1 Processor Channel screen. Session - Local The Local and Remote Session numbers can be any value between 1 and 256 (si model) or 384 (r model), but they must be consistent between endpoints.
Configuration 3: R8si<—x.25 —> R8r Gateway <—ethernet—> 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.
3 Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi Configuration 4: C-LAN Administration R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi In this configuration, a DEFINITY ECS R8r provides gateway conversion between ISDN and TCP/IP.
3 Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi C-LAN Administration 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 Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi 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. 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.
Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi 3 C-LAN Administration Switch 1 Task — Assign Link via ppp Data Module to Switch 3 This task administers a ppp data module for the ppp connection to node 3. The data module associates a link number with a port address, extension number, and node name for the C-LAN port used for this connection.
Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi 3 C-LAN Administration Field Conditions/Comments BCC: Bearer Capability Class. This is a display-only field. COS COR: The values for these fields will be specified by the system administrator. TN: Node Name: The node name for the interface defined by this data module. This must be a name entered on the Node Names screen. Establish Connection? y means that this switch will be responsible for call setup for this connection.
3 Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi 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 Chan Enable Appl.
Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi 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 value of 0 allows any available interface channel on the destination node to be used for this connection.
Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi 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 value of 0 allows any available interface channel on the destination node to be used for this connection.
Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi 3 C-LAN Administration Switch 1 Task — Assign Signaling Group and administered NCA TSC This task assigns a signaling group and an administered NCA TSC for the ISDN connection to Switch 2.
3 Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi C-LAN Administration Page 2 of 5 ADMINISTERED NCA TSC ASSIGNMENT Service/Feature: __________ TSC Index 1: 2: 3: : Local Ext. 2951_ 2952_ _____ As-needed Inactivity Time-out (min): __ Enabled Established y permanent y permanent _ _________ Dest. Digits 1701___________ 1702___________ _______________ Appl. dcs____ gateway _______ Mach.
Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi 3 C-LAN Administration Field Conditions/Comments Dest. Digits Extension number of the ISDN interface on the Switch-2 DS1 circuit pack. Appl. Specifies that TSC #2 will carry signaling that will be converted in Switch-1 to another protocol (TCP/IP), which will then be forwarded to Switch-3.
3 Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi C-LAN Administration Switch 1 Task — Assign ISDN-TSC Gateway This task assigns the ISDN TSC gateway channels needed for ISDN signaling between node 1 and node2 Steps Begin > Open the ISDN TSC Gateway Channel Assignment form — enter ch isdn tsc change isdn tsc-gateway ISDN TSC GATEWAY CHANNEL ASSIGNMENT Sig Group 1: 1_ 2: __ 3: __ 4: __ 5: __ 6: __ : Adm’d NCA TSC Index 2_ __ __ __ __ __ Processor Channel 14_ ___ ___ ___ ___ ___ Application
3 Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi C-LAN Administration Switch 2 Task — Assign Signaling Group and administered NCA TSC This task assigns a signaling group and an administered NCA TSC for the ISDN connection to Switch 1.
3 Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi C-LAN Administration > Press the Next Page key Page 2 of 5 ADMINISTERED NCA TSC ASSIGNMENT Service/Feature: __________ TSC Index 1: 2: 3: : Local Ext. 1701_ 1702_ _____ Enabled Established y permanent y permanent _ _________ As-needed Inactivity Time-out (min): __ Dest. Digits 2951___________ 2952___________ _______________ Appl. dcs____ dcs____ _______ Mach.
Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi 3 C-LAN Administration Field Conditions/Comments Dest. Digits Extension number of the ISDN interface for TSC #2on the Switch-1 DS1 circuit pack. Appl. TSC #2 carries DCS signaling between Switch 2 and Switch 1. As specified on the Switch-1 NCA TSC Assignment screen, TSC #2 is administered as a gateway on Switch 1, where the ISDN signals are converted to TCP/IP. Mach ID Destination is node 3.
3 Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi C-LAN Administration Switch 3 Task — Enable Bus Bridge Connectivity This task enables the bus bridge functionality on the C-LAN circuit pack to provide a path between the packet bus and the processor. Note: Bus Bridge Connectivity is used on the csi model only. This task may have been complete when the C-LAN circuit pack was installed.
3 Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi C-LAN Administration Switch 3 Task — Assign Node Names This task assigns node names and IP addresses to each node in the network. This screen is administered on Switch 3. A Node Names screen must be administered on each switch in the network. 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.
Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi 3 C-LAN Administration Switch 3 Task — Assign Link via ppp Data Module to Switch 1 This task administers a ppp data module on Switch 3 for the ppp connection to Switch 1. The data module associates a link number with a port address, extension number, and node name for the C-LAN port used for this connection.
Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi 3 C-LAN Administration Field Conditions/Comments BCC: Bearer Capability Class. This is a display-only field. COS COR: The values for these fields will be specified by the system administrator. TN: Node Name: The node name for the interface defined by this data module. This must be a name entered on the Node Names screen.
3 Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi C-LAN Administration Switch 3 Task — Assign Processor Channels This task associates data links (hardware) with processor channels (software) on Switch 3. 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 Chan Enable Appl.
3 Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi C-LAN Administration Field Conditions/Comments Session - Local The Local and Remote Session numbers can be any value between 1 and 256 (si model) or 384 (r model), but they 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.
Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi 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.
3 Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si C-LAN Administration Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si In this configuration, a DEFINITY ECS R8r acts as a gateway between two other nodes — one connected via ppp to an R8csi and the other via ethernet to another R8si.
3 Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si C-LAN Administration 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 the Checklist for Prerequisite Administration (page 54), before proceeding with the connectivity administration in this section.
3 Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si 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. 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.
Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> 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 associates a link number with a port address, extension number, and node name for the C-LAN port used for this connection.
Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si Field 3 C-LAN Administration Conditions/Comments COS COR: The values for these fields will be specified by the system administrator. TN: Node Name: The node name for the interface defined by this data module. This must be a name entered on the Node Names screen. Subnet Mask: Establish Connection? y means that this switch will be responsible for call setup for this connection. Enter n when administering the data module for Switch 2.
3 Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si C-LAN Administration Switch 1 Task — Assign IP Interfaces The IP interface for each C-LAN board on the switch must be defined on the IP Interfaces form. Each DEFINITY switch in an IP network has one IP Interfaces form.
3 Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si C-LAN Administration Field Conditions/Comments Subnet Mask Enter the subnet mask associated with the IP address for this IP interface. (The IP address is associated with the node name on the Node Names screen). In this example, leave the default subnet mask, 255.255.255.0, which indicates no subnetting for a Class C IP address.
Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si 3 C-LAN Administration Switch 1 Task — Assign Link via ethernet Data Module to Ethernet This task administers an ethernet data module for the ethernet connection to node 3. The data module associates a link number with a port address, extension number, and node name for the C-LAN port used for this connection.
3 Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si C-LAN Administration Switch 1 Task — Assign Processor Channels This task associates data links (hardware) with processor channels (software) on the Switch 1. 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 Chan Enable Appl.
Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> 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 value of 0 allows any available interface channel on the destination node to be used for this connection.
Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si 3 C-LAN Administration Field Conditions/Comments Session - Local For each connection, the Local Session number on this switch must equal the Remote Session number on the remote switch and vice versa. Session - Remote Mach ID Destination switch ID identified on the dial plan of the destination switch.
3 Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si C-LAN Administration Switch 2 Task — Enable Bus Bridge Connectivity This task enables the bus bridge functionality on the C-LAN circuit pack to provide a path between the packet bus and the processor. Note: Bus Bridge Connectivity is used on the csi model only. This task may have been complete when the C-LAN circuit pack was installed.
3 Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si 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. 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.
Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> 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 associates a link number with a port address, extension number, and node name for the C-LAN port used for this connection.
Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si Field 3 C-LAN Administration Conditions/Comments COS: COR: The values for these fields will be specified by the system administrator. TN: Node Name: The node name for the interface defined by this data module. This must be a name 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.
3 Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si C-LAN Administration Switch 2 Task — Assign Processor Channels This task associates data links (hardware) with processor channels (software) on the 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 Chan Enable Appl.
3 Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si C-LAN Administration Field Conditions/Comments Session - Local The Local and Remote Session numbers can be any value between 1 and 256 (si model) or 384 (r model), but they 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.
Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si 3 C-LAN Administration Switch 2 Task — Assign IP Route to node-3 This task specifies an initial route for messages handled by node-2 that are destined for node-3. An IP route is required for this route because there are intermediate nodes between node-2 and node-3. Steps Begin > Enable the ppp link on the node-2 data module screen: ch da 3020, set Enable Link? to y.
3 Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si C-LAN Administration Switch 3 Task — Assign Node Names This task assigns node names and IP addresses to each node in the network. This screen is administered on Switch 3. A Node Names screen must be administered on each switch in the network. 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.
3 Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si C-LAN Administration Switch 3 Task — Assign IP Interfaces The IP interface for each C-LAN board on the switch must be defined on the IP Interfaces form. Each DEFINITY switch in an IP network has one IP Interfaces form.
3 Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si C-LAN Administration Field Conditions/Comments Subnet Mask Enter the subnet mask associated with the IP address for this IP interface. (The IP address is associated with the node name on the Node Names screen). In this example, leave the default subnet mask, 255.255.255.0, which indicates no subnetting for a Class C IP address.
Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si 3 C-LAN Administration Switch 3 Task — Assign Link via ethernet Data Module to the LAN This task administers an ethernet data module on Switch 3 for the ethernet connection. The data module associates a link number with a port address, extension number, and node name for the C-LAN port used for this connection.
Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si 3 C-LAN Administration Switch 3 Task — Assign Processor Channels This task associates data links with processor channels on Switch 3. 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 Chan Enable Appl.
Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si 3 C-LAN Administration Field Conditions/Comments Session - Local The Local and Remote Session numbers can be any value between 1 and 256 (si model) or 384 (r model), but they 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.
Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> 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.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si Configuration 5B: C-LAN Administration R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si In this configuration, a DEFINITY ECS R8r acts as a gateway between two other nodes — one connected via ppp to an R8csi and the other via ethernet to another R8si. This configuration is the same as configuration 5A except that Switch 1 has two C-LAN circuit packs instead of one.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si 3 C-LAN Administration 4 Switch 3 administration a Assign node names b Assign link (via a data module) to the LAN c Assign processor channels 5 Enable links and processor channels 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.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si C-LAN Administration Configuration 5B SWITCH 2 SWITCH 1 SWITCH 3 DEFINITY ECS R7csi DEFINITY ECS R7r DEFINITY ECS R7si software-defined connections Processor channels Interface channels Interface channels Processor channels Interface channels Interface channels Processor channels 1 2 1 5000 1 5000 1 1 5000 1 500 1 2 21 23 x1(any) x2(any) 5003 12 13 5003 x(any) 6004 31 32 128 64500 64500 384 64500 64500 256
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si 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.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> 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 associates a link number with a port address, extension number, and node name for the C-LAN port used for this connection.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si Field 3 C-LAN Administration Conditions/Comments COS COR: The values for these fields will be specified by the system administrator. TN: Node Name: The node name for the interface defined by this data module. This must be a name entered on the Node Names screen. Establish Connection? y means that this switch will be responsible for the call setup. Enter n when administering the data module for Switch 2.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si C-LAN Administration Switch 1 Task — Assign IP Interfaces The IP interface for each C-LAN board on the switch must be defined on the IP Interfaces form. Each DEFINITY switch in an IP network has one IP Interfaces form.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si C-LAN Administration Field Conditions/Comments Subnet Mask Enter the subnet mask associated with the IP address for this IP interface. (The IP address is associated with the node name on the Node Names screen). In this example, leave the default subnet mask, 255.255.255.0, which indicates no subnetting for a Class C IP address.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si 3 C-LAN Administration Switch 1 Task — Assign Link via ethernet Data Module to the LAN This task administers an ethernet data module on Switch 1 for the ethernet connection. The data module associates a link number with a port address, extension number, and node name for the C-LAN port used for this connection.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si C-LAN Administration Switch 1 Task — Assign Link via ppp Data Module to C-LAN(a) This task administers a ppp data module on Switch 1 for the ppp connection from the C-LAN(b) circuit pack to the C-LAN(a) circuit pack.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si Field 3 C-LAN Administration Conditions/Comments COS COR: The values for these fields will be specified by the system administrator. TN: Node Name: The node name for the interface defined by this data module. This must be a name entered on the Node Names screen. Subnet Mask: Establish Connection? n means that the node at the remote end of this connection (node-1b in this case) will be responsible for the call setup.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si C-LAN Administration Switch 1 Task — Assign Link via ppp Data Module to C-LAN(b) This task administers a ppp data module on Switch 1 for the ppp connection from the C-LAN(a) circuit pack to the C-LAN(b) circuit pack.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si Field 3 C-LAN Administration Conditions/Comments COS COR: The values for these fields will be specified by the system administrator. TN: Node Name: The node name for the interface defined by this data module. This must be a name entered on the Node Names screen. Subnet Mask: Establish Connection? y means that this node is responsible for the call setup for the link to node-1c. Enter n when administering the data module for node-1c.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si C-LAN Administration Switch 1 Task — Assign Processor Channels This task associates data links (hardware) with processor channels (software) on Switch 1. Note that there are no processor channels or interface channels associated with the ppp connection between the two C-LAN circuit packs. Steps Begin > Open the Processor Channel Assignment form — enter ch com p.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> 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 value of 0 allows any available interface channel on the destination node to be used for this connection.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si 3 C-LAN Administration Field Conditions/Comments Session - Local For each connection, the Local Session number on this switch must equal the Remote Session number on the remote switch and vice versa. Session - Remote Mach ID Destination switch ID identified on the dial plan of the destination switch.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si 3 C-LAN Administration Switch 1 Task — Assign IP Route: C-LAN(a) to node-3 This task specifies a route for packets handled by C-LAN(a) destined for node-3. This route is needed because node-1a and node-3 are connected via ppp and there are intermediate nodes between them. Steps Begin > Enable the ppp link on the node-1a data module screen: ch da 2013, set Enable Link? to y.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si C-LAN Administration Switch 1 Task — Assign IP Route: C-LAN(b) to node-2 This task specifies a route for packets handled by C-LAN(b) destined for node-2. This route is needed because node-1b and node-2 are connected via ppp and there are intermediate nodes between them. Steps Begin > Enable the ppp link on the node-1b data module screen: ch da 2378, set Enable Link? to y.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si C-LAN Administration Switch 2 Task — Enable Bus Bridge Connectivity This task enables the bus bridge functionality on the C-LAN circuit pack to provide a path between the packet bus and the processor. Note: Bus Bridge Connectivity is used on the csi model only. This task may have been complete when the C-LAN circuit pack was installed.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si 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. 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.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> 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 associates a link number with a port address, extension number, and node name for the C-LAN port used for this connection.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si Field 3 C-LAN Administration Conditions/Comments COS: COR: The values for these fields will be specified by the system administrator. TN: Node Name: The node name for the interface defined by this data module. This must be a name entered on the Node Names screen. Subnet Mask: 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.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si C-LAN Administration Switch 2 Task — Assign Processor Channels This task associates data links (hardware) with processor channels (software) on Switch 1. 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 Chan Enable Appl.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si C-LAN Administration Field Conditions/Comments Session - Local The Local and Remote Session numbers can be any value between 1 and 256 (si model) or 384 (r model), but they 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.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si 3 C-LAN Administration Switch 2 Task — Assign IP Route to node-3 This task specifies a route for packets handled by node-2 that are destined for node-3. An IP route is required for this route because there are intermediate nodes between node-2 and node-3. Steps Begin > Enable the ppp link on the node-2 data module screen: ch da 3020, set Enable Link? to y.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si C-LAN Administration Switch 3 Task — Assign Node Names This task assigns node names and IP addresses to each node in the network. This screen is administered on Switch 3. A Node Names screen must be administered on each switch in the network. 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.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si C-LAN Administration Switch 3 Task — Assign IP Interfaces The IP interface for each C-LAN board on the switch must be defined on the IP Interfaces form. Each DEFINITY switch in an IP network has one IP Interfaces form.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si C-LAN Administration Field Conditions/Comments Subnet Mask Enter the subnet mask associated with the IP address for this IP interface. (The IP address is associated with the node name on the Node Names screen). In this example, leave the default subnet mask, 255.255.255.0, which indicates no subnetting for a Class C IP address.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si 3 C-LAN Administration Switch 3 Task — Assign Link via ethernet Data Module to the LAN This task administers an ethernet data module on Switch 3 for the ethernet connection to Switch 1. The data module associates a link number with a port address, extension number, and node name for the C-LAN port used for this connection.
3 Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si C-LAN Administration Switch 3 Task — Assign Processor Channels This task associates data links (hardware) with processor channels (software) on Switch 3. 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 Chan Enable Appl.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si 3 C-LAN Administration Field Conditions/Comments Session Local The Local and Remote Session numbers can be any value between 1 and 256 (si model) or 384 (r model), but they 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.
Configuration 5B: R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> 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.
4 Networking Example This chapter provides an example of a complex network. It describes procedures for administering trunk groups, dial plans, signaling groups, and data links for a four-switch network with an Intuity AUDIX and a CMS. The network example is unchanged from the example in Issue 1 (for R7) of this book. The screens have been updated for R8.
4 Overview Networking Example Network Diagram The following diagram shows a high-level view of the example network. Switch Node 3 Switch Node 2 X.
4 Overview Networking Example Task Summary The following matrix summarizes the administration tasks required to set up this network.
4 Link/Channel/TSC Map Networking Example Link/Channel/TSC Map The link/channel/TSC map shows the link, processor channel, and temporary signaling connection numbers, and the connection types for each Switch Node in the network. Node 2 Processor channels N1 N3 N4 Int Node 1 Interface channels PI interface channels 11 12 13 2 11 12 13 2 11 12 13 59 Link 2 BX.25 Link 1 DEFINITY ECS R8csi ISDN–X.25 Gateway ISDN–IP Gateway X.
4 Network Map Networking Example Network Map The network map shows the RNX, trunk group, hunt group numbers, data module type, and extension for each Switch Node in the network. For TCP/IP connections, the node name and IP address is shown for each node. Node 2 R6si RNX 222 Voice TG 12 TAC 712 DS1 REM-AUDIX PI HG 99 Ext. 2992 DTE Ext. 2111 Exts. 2000-2999 BX.
4 Switch-Node 1 Administration Networking Example Switch-Node 1 Administration This section displays the filled-in screens for the administration of Switch Node 1. DS1 Circuit Packs Connection to Switch Node 2 add ds1 1c19 Page 1 of 2 DS1 CIRCUIT PACK Location: Bit Rate: Line Compensation: Signaling Mode: 01c19 1.
4 Switch-Node 1 Administration Connection to Switch Node 4 add ds1 1c17 Networking Example Page 1 of 2 DS1 CIRCUIT PACK Location: Bit Rate: Line Compensation: Signaling Mode: 01C17 1.
4 Switch-Node 1 Administration Networking Example Signaling Group Page 1 change signaling group next Group Number: 1 Page 1 of 5 SIGNALING GROUP Group Type: Associated Signaling? y Primary D-Channel: 01c1824 Max number of NCA TSC: 5_ Max number of CA TSC: 23 Trunk Group for NCA TSC: 13 Trunk Group for Channel Selection: ___ Supplementary Service Protocol: a__ Page 2 – Administered NCA TSC Assignment Page 2 of 5 ADMINISTERED NCA TSC ASSIGNMENT Service/Feature: __________ TSC Index 1: 2: 3: 4: 5: : 16
4 Switch-Node 1 Administration Networking Example Trunk Groups Group 12 (tie to Switch Node 2) — page 1 add trunk-group 12 Page 1 of 10 TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Comm Type: 12 Group Type: tie CDR Reports: y Switch 1 to Switch 2 tg12 COR: 1 TN: 1 TAC: 712 two-way Outgoing Display? n Trunk Signaling Type: Busy Threshold: 99 Night Service: y 0 Incoming Destination: Auth Code? n avd Trunk Flash? n BCC: 0 TRUNK PARAMETERS Incoming Rotary Timeout(sec): 5 T
4 Switch-Node 1 Administration Group 22 (data to Switch Node 2)— page1 add trunk-group 22 Networking Example Page 1 of 10 TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Comm Type: 22 Group Type: tie CDR Reports: y DCS data to node 2 - TG22 COR: 1 TN: 1 TAC: 722 two-way Outgoing Display? n Trunk Signaling Type: Busy Threshold: 99 Night Service: y 0 Incoming Destination: Auth Code? n data Trunk Flash? n BCC: 0 TRUNK PARAMETERS Incoming Rotary Timeout(sec): 5 Trunk Type (in
4 Switch-Node 1 Administration Group 13 (ISDN-PRI to Switch Node 3) — page 1 add trunk-group 13 Networking Example Page 1 of 10 TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Service Type: 13 Group Type: isdn CDR Reports: y ISDN TG 13 to Switch 3 COR: 1 TN: 1 TAC: 713 Outgoing Display? n ATM? _ two-way Busy Threshold: 99 Night Service: _____ n 0 Auth Code? n TestCall ITC: rest tie Far End Test Line No: TestCall BCC: 4 TRUNK PARAMETERS Codeset to Send TCM,Lookahead: 6 Cod
4 Switch-Node 1 Administration Group 14 (tie to Switch Node 4) — page 1 add trunk-group 14 Networking Example Page 1 of 10 TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Comm Type: 14 Group Type: tie CDR Reports: y Switch 1 to Switch 4 tg14 COR: 1 TN: 1 TAC: 714 two-way Outgoing Display? n Trunk Signaling Type: Busy Threshold: 99 Night Service: y 0 Incoming Destination: Auth Code? n voice Trunk Flash? n BCC: 0 TRUNK PARAMETERS Incoming Rotary Timeout(sec): 5 Trunk Type (
4 Switch-Node 1 Administration Group 24 (data to Switch Node 4) — page1 add trunk-group 24 Networking Example Page 1 of 10 TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Comm Type: 24 Group Type: tie CDR Reports: y DCS data to node 4-TG24 COR: 1 TN: 1 TAC: 724 two-way Outgoing Display? n Trunk Signaling Type: Busy Threshold: 99 Night Service: y 0 Incoming Destination: Auth Code? n rbavd Trunk Flash? n BCC: 0 TRUNK PARAMETERS Incoming Rotary Timeout(sec): 5 Trunk Type (in
4 Switch-Node 1 Administration Networking Example Uniform Dialing Plan display udp 2 Page 1 of 2 UNIFORM DIALING PLAN Ext Codes: ddxx_ Ext Code: _____ Type: _______ ___ dd 0x: 00: 01: 02: 03: 04: 05: 06: 07: 08: 09: Type _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ dd 1x: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: Type local__ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ ___ ___ ___
4 Switch-Node 1 Administration Networking Example ISDN TSC Gateway Channel Assignment change isdn tsc-gateway ISDN TSC GATEWAY CHANNEL ASSIGNMENT Sig Group 1: 1_ 2: 1_ 3: 1_ 4: __ : Adm’d NCA TSC Index 2_ 3_ 4_ __ Processor Channel 12_ 16_ 3__ ___ Application dcs__ dcs__ audix _____ Sig Group 17: __ 18: __ 19: __ 20: __ Adm’d NCA TSC Index __ __ __ __ Page Processor Channel ___ ___ ___ ___ 1 of 2 Application ______ ______ ______ ______ Routing Patterns Pattern 102 display route-pattern 102 Pat
4 Switch-Node 1 Administration Networking Example Pattern 103 add route-pattern 103 Pattern Number: 103 Grp. No. 1:13 2: 3: 4: 5: 6: 1: 2: 3: 4: 5: 6: FRL NPA Pfx Hop Toll No.
4 Switch-Node 1 Administration Networking Example page 2 change node names Page 2 of 6 NODE NAMES Name 1.ppp14________ __ 2.ppp41____ 3.CMS_____________ 4.router__________ 5.ethernet1_______ : 16. IP Address 192.168.200.12_ 192.168.200.14_ 192.168.201.10_ 192.168.200.1__ 192.168.200.11_ Name _______________ _______________ _______________ _______________ 17. 18. 19. 20. IP Address ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ Data Modules x.
4 Switch-Node 1 Administration pdm data module add data-module 1900 Networking Example Page 1 of 1 DATA MODULE Data Extension: 1900 Name: BCC: 2 Type: pdm COS: 1 Remote Loop-Around Test? n Port: 01c2001 COR: 1 Secondary data module? n ITC: restricted TN: 1 Connected To: dte ABBREVIATED DIALING List1: SPECIAL DIALING OPTION: ASSIGNED MEMBER ( Station with a data extension button for this data module ) Ext Name 1: ppp data module add data-module 1994 Page 1 of x DATA MODULE Data Extensio
4 Switch-Node 1 Administration Networking Example ethernet data module add data 1191 Page 1 of X DATA MODULE Data Extension: Type: Port: Link: Name: ethernet on link 1_____________ 1191 ethernet 01c1517_ 1_ BCC: 2 Network uses 1’s for Broadcast Addresses? y IP Interface change ip-interfaces Page 1 of 2 IP Interfaces Network regions are interconnected? n Enabled Type Slot Code Sfx Node Name C-LAN 01c15 TN799 B ethernet1 y _ _____ _____ _____ _ _________ _ _____ _____ _____ _ _________ _ _____ ___
4 Switch-Node 2 Administration Networking Example Switch-Node 2 Administration This section displays the filled-in screens for the administration of Switch Node 2. DS1 Circuit Packs add ds1 1a10 DS1 CIRCUIT PACK Location: Bit Rate: Line Compensation: Signaling Mode: 01a10 1.
4 Switch-Node 2 Administration Networking Example Synchronization Plan Page 1 of X SYNCHRONIZATION PLAN SYNCHRONIZATION SOURCE (circuit pack location) Stratum: 4 Port Network: 1 Primary: 01a10 Secondary: ___ Location Name Slip Type y UDS1-BD 01a10 ______________ ______________ _ _____ _______________ _ _____ _______________ _ _____ _______________ _ _____ _______________ _ _____ _______________ _ _____ _______________ _ NOTE: TN722B & TN464B DS1 sources result in Location Name Slip Type _____ __________
4 Switch-Node 2 Administration Group 12 — Page 2 display trunk-group 12 TRUNK FEATURES ACA Assignment? n Networking Example Page Measured: Internal Alert? Data Restriction? Glare Handling: PBX ID: 1 none n n none 2 of 10 Maintenance Tests? y Used for DCS? y Suppress # Outpulsing? n Seize When Maintenance Busy: neither-end Incoming Tone (DTMF) ANI: no Connected to CO? n Per Call CPN Blocking Code: Per Call CPN Unblocking Code: Group 12 — member assignments TRUNK GROUP Administered Members (min/ma
4 Switch-Node 2 Administration Networking Example AAR Digit Analysis change aar analysis 1 Page 1 of 2 AAR DIGIT ANALYSIS TABLE Percent Full: Dialed String Total Min Max 7 7 7 7 7 7 221 223 224 Route Pattern 101 101 101 Call Type aar aar aar Node Num 1 3 4 6 ANI Reqd n n n Routing Patterns display route-pattern 101 Pattern Number: 101 Grp. No. 1:12 2: 3: 4: 5: 6: FRL NPA Pfx Hop Toll No.
4 Switch-Node 2 Administration Networking Example Processor Channel Assignments Release 6 Processor Channel Assignment screen change communications-interface processor-channels Page 1 of 4 PROCESSOR CHANNEL ASSIGNMENT Proc Interface Chan Appl.
4 Switch-Node 2 Administration Networking Example Hunt Group page 1 add hunt-group 99 Page 1 of 10 HUNT GROUP Group Number: Group Name: Group Extension: Group Type: TN: COR: Security Code: ISDN Caller Display: 99 Intuity 1 2111 ucd-mia 1 1 ACD? Queue? Vector? Coverage Path: Night Service Destination: MM Early Answer? page 2 add hunt-group 1 n n n n Page 2 of 10 HUNT GROUP Message Center: rem-audix AUDIX Extension: 1111 Calling Party Number to INTUITY AUDIX? n LWC Reception: none Administra
4 Switch-Node 3 Administration Networking Example Switch-Node 3 Administration This section displays the filled-in screens for the administration of Switch Node 3. DS1 Circuit Packs add ds1 1a11 Page 1 of 2 DS1 CIRCUIT PACK Location: Bit Rate: Line Compensation: Signaling Mode: 01a11 1.
4 Switch-Node 3 Administration Networking Example Synchronization Plan change synch Page 1 of X SYNCHRONIZATION PLAN SYNCHRONIZATION SOURCE (circuit pack location) Stratum: 4 Port Network: 1 Primary: 1a11 Secondary: ___ Location Name Slip Type y UDS1-BD 01a11 DCS SW1_______ _____ ______________ _ _____ _______________ _ _____ _______________ _ _____ _______________ _ _____ _______________ _ _____ _______________ _ _____ _______________ _ NOTE: TN722B & TN464B DS1 sources result in Location Name Slip T
4 Switch-Node 3 Administration Networking Example Trunk Groups Group 13 (ISDN-PRI) — page 1 add trunk-group 13 Page 1 of 10 TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Service Type: 13 Group Type: isdn-pri CDR Reports: y ISDN TG 13 to sw 1 COR: 1 TN: 1 TAC: 713 two-way Outgoing Display? n n Busy Threshold: 99 Night Service: 0 tie Auth Code? n TestCall ITC: rest Far End Test Line No: TestCall BCC: 4 TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send TCM,Lookah
4 Switch-Node 3 Administration Group 13 — member assignments display trunk-group 13 Page 4 of 10 TRUNK GROUP Administered Members (min/max): 0/0 Total Administered Members: 0 GROUP MEMBER ASSIGNMENTS Port 01a1101 01a1102 01a1103 01a1104 1: 2: 3: 4: 5: 6: Networking Example Code Sfx Name TN464 e TN464 e TN464 e TN464 e Night Sig Grp 1 1 1 1 Uniform Dialing Paln change udp x Page 1 of 2 UNIFORM DIALING PLAN Ext Codes: ddxx dd 0x: 00: 01: 02: 03: 04: 05: 06: 07: 08: 09: Type _______ _______ _______
4 Switch-Node 3 Administration Networking Example Routing Patterns add route-pattern 101 Pattern Number: 101 Grp. No. 1:13 2: 3: 4: 5: 6: 1: 2: 3: 4: 5: 6: FRL NPA Pfx Hop Toll No.
4 Switch-Node 4 Administration Networking Example Switch-Node 4 Administration This section displays the filled-in screens for the administration of Switch Node 4.
4 Switch-Node 4 Administration Networking Example Dial Plan change dialplan DIAL PLAN RECORD Local Node Number: 4 ETA Node Number: Uniform Dialing Plan: 4-digit ETA Routing Pattern: Extension Search Order: local-extensions-first DIGIT TABLE Length - 1 - 2 - 3 - 4 - 5 - 6 extension extension extension extension UDP FIRST First Digit 1: 2: 3: 4: 5: 6: 7: 8: fac 9: fac 0: attd *: #: dac dac dac Synchronization Plan Page 1 of X SYNCHRONIZATION PLAN SYNCHRONIZATION SOURCE (circuit pack location) Stratum:
4 Switch-Node 4 Administration Networking Example Trunk Groups Group 14 — page 1 display trunk-group 14 Page 1 of 10 TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Comm Type: 14 Group Type: tie CDR Reports: y Node 4 to Node 1 - TG14 COR: 1 TN: 1 TAC: 714 two-way Outgoing Display? n Trunk Signaling Type: y Busy Threshold: 99 Night Service: 0 Incoming Destination: voice Auth Code? n Trunk Flash? n BCC: 0 TRUNK PARAMETERS Trunk Type (in/out): wink/wink Incoming Rotary Timeo
4 Switch-Node 4 Administration Group 24 (data to Switch Node 1) — page1 add trunk-group 24 Page Networking Example 1 of 10 TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Comm Type: 24 Group Type: tie CDR Reports: y dcs data to Switch 1 COR: 1 TN: 1 TAC: 124 two-way Outgoing Display? n Trunk Signaling Type: y Busy Threshold: 99 Night Service: 0 Incoming Destination: rbavd Auth Code? n Trunk Flash? n BCC: 0 TRUNK PARAMETERS Trunk Type (in/out): wink/wink Incoming Rotary Ti
4 Switch-Node 4 Administration Networking Example Uniform Dialing Paln change udp x Page 1 of 2 UNIFORM DIALING PLAN Ext Codes: ddxx dd 0x: 00: 01: 02: 03: 04: 05: 06: 07: 08: 09: Type _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ dd 1x: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ Type udpcode _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ 221 ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
4 Switch-Node 4 Administration Networking Example Node Names page 1 change node-names Page 1 of 6 NODE NAMES Audix Names intuity1 IP Address 192.168.200.10 MSA Names msa IP Address . . . page 2 change node names Page 2 of 6 NODE NAMES Name 1.ppp41 __ 2.ppp14__________ 3.CMS_____________ 4.router__________ 5.ethernet1_______ : 16. IP Address 192.168.200.14_ 192.168.200.12_ 192.168.201.10_ 192.168.200.1__ 192.168.200.11_ 17. 18. 19. 20. 21.
4 Switch-Node 4 Administration Networking Example Processor Channel Assignments change communications-interface processor-channels Page 1 of X PROCESSOR CHANNEL ASSIGNMENT Proc Chan Enable Appl.
4 Switch-Node 4 Administration Networking Example Hunt Group page 1 add hunt-group 99 Page 1 of 10 HUNT GROUP Group Number: Group Name: Group Extension: Group Type: TN: COR: Security Code: ISDN Caller Display: 99 Intuity 1 4111 ucd-mia 1 1 ACD? Queue? Vector? Coverage Path: Night Service Destination: MM Early Answer? page 2 add hunt-group 1 Page n n n n 2 of 10 HUNT GROUP Message Center: rem-audix AUDIX Extension: 1111 Calling Party Number to INTUITY AUDIX? n LWC Reception: none 240 CID:
4 Intuity Translations for DCS AUDIX Networking Example Intuity Translations for DCS AUDIX This screen is administered on Intuity, not on the DEFINITY ECS. Switch Interface Administration Switch Link Type:_LAN_ Extension Length:_4___ Host Switch Number:_1___ Audix Number:_1___ Switch Number IP Address/Host Name 1__ 2__ 3__ 4__ 5__ : 10_ Switch:_Definity_____ Country:_United States_ TCP Port Switch Number IP Address/Host Name TCP Port 192.168.200.11_______ 192.168.200.11_______ 192.168.200.
4 CMS Administration 242 CID: 77730 Networking Example Administration for Network Connectivity 555-233-504 — Issue 1 — April 2000
A Screens Reference This appendix gives detailed field descriptions for a selection of DEFINITY administration screens (forms). The screen descriptions are divided into two groups — a) Networking Screens, which are needed for network administration and are used in other chapters of this document, and b) Other Network-related Screens, which are related to network administration but not referred to elsewhere in this document.
A Screens Reference Other Network-Related DEFINITY Screens Communication Interface Links, page 293 Data Modules: netcon, analog-dm, page 295 Extended Trunk Access (ETA) Call Screening, page 298 Extension Number Portability Numbering Plan, page 299 Hop Channel Assignments, page 300 Node Number Routing, page 302 Message Waiting Indication Subscriber Number Prefixes, page 303 Synchronization Plan, page 304 Uniform Dialing Plan, page 307 244 CID: 77730 Administration for Network Connectivity 555-233-504 —
A Networking Screens Screens Reference Networking Screens Node Names In this context, a node is defined as any of the following — a C-LAN port, a bridge or router, a CMS ethernet port, or an Intuity AUDIX, or other MSA (Message Server Adjunct) 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, including CMS, must be entered on pages 2–6.
A Networking Screens IP Address Screens Reference The IP address associated with the node name. (Not needed for X.25 connections). Pages 2 – 6 Page 2 of 6 NODE NAMES Name 1. Default 2. _______________ 3. _______________ 4. _______________ 5. _______________ 6. _______________ 7. _______________ 8. _______________ 9. _______________ 10. _______________ 11. _______________ 12. _______________ 13. _______________ 14. _______________ 15. _______________ 16. _______________ Name IP Address IP Address 0.
A Networking Screens Screens Reference IP Interfaces Use the IP Interfaces screen to define an interface to the LAN from either the C-LAN or MedPro circuit packs. The physical interface is port 17 on the C-LAN board and is a network interface card on the MedPro. This screen specifies the IP address (via the Node Names screen), subnet mask, default gateway address, and the network region for each IP interface on the local DEFINITY ECS.
A Networking Screens Enable Eth Pt Screens Reference Used to enable or disable the C-LAN or MedPro IP Ethernet port. Valid Values Usage y/n 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.
A Networking Screens Subnet Mask Screens Reference 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.
A Networking Screens Net Rgn Specifies the network region assigned to the IP interface. Valid Values Usage 1–10 The Region field on the IP Interfaces screen allows you to set up segregated groups of MedPro resources. This feature can be used in a variety of ways. For example, you could use regions to allocate specific MedPro boards to H.323 trunks and others to stations; or you could use regions to avoid traffic over low bandwidth or high-latency network links. Default is 1.
A Networking Screens Screens Reference IP Routing add ip-route 3 Page 1 of 1 IP ROUTING Route Number: 3 Destination Node: Gateway: C-LAN Board: Metric: Route Type: General Description IP routes are needed when switches are connected in an IP network and default gateways are not assigned and you want network nodes on different (sub)networks to communicate. There are two type of IP routes — host and network.
A Networking Screens Route Number Destination Node Gateway C-LAN Board 252 Screens Reference A number that identifies this IP route. Valid Value Usage 1–400 Command-line entry. Enter a specific number or n for the next available number. The node name of the final destination for this connection. Valid Value Usage A name previously entered on the Node Names screen. This is the final destination of the IP route for this connection. The node name of the first intermediate node.
A Networking Screens Metric Screens Reference The metric value indicates the desirability of the IP route in terms of the efficiency of the data transmission between two nodes. Valid Values Usage 0 or 1 A metric value of 1 is used only on a switch that has more than one C-LAN board installed. You can always enter either 0 or 1 in the Metric field but the choice should be guided by the information below.
A Networking Screens Screens Reference A message originating on Switch B destined for node 6 can use either route 2 or the implied route. The switch will choose the implied route because it has metric 0 while route 2 has metric 1. By using the implied route, the message goes directly from the source to C-LAN2, without passing through C-LAN1. If route 2 had been administered with metric 0, the switch may have used route 2, which goes through C-LAN1 to C-LAN2.
A Networking Screens Screens Reference IP Media Parameters This screen specifies the types of codecs available on the IP Interface board (TN802B). The codecs encode and compand the analog voice data for transmission over the IP facilities. The order in which the codecs are listed is the preferred order of use by the switch. Note: The codec ordering must be the same on DEFINITY switches at both ends of an H.323 trunk connection.
A Networking Screens Screens Reference Data Module Screens The Data Module screen must be administered at both ends of a DCS connection, except for ISDN connections. There are two types of data modules used with TCP/IP connections — ppp and ethernet. There are two types of data modules used with BX.25 connections — the proc-intf data module is used for the csi and si models, and the x.25 data module is used with the r model.
A Networking Screens Port Screens Reference Seven characters to specify the port location for this data module in the format NNCSSPP. Valid Entries Data Module Types Usage NN = cabinet number: ppp ethernet x.25 pdm You can enter x in the Port field to indicate that there is no hardware associated with the port assignment (Administration Without Hardware).
A Networking Screens COR Class of restriction. COR identifies caller and called-party privileges for telephones, telephone groups, data modules, and trunk groups. Valid Entries Data Module Types Usage 0-95 ppp procr-intf x.25 pdm The values for these fields will be specified by the system administrator. Default is 1 TN Administer the COR so that account codes are not required. Forced entry of account codes is turned off for wideband endpoints. Tenant partition number.
A Networking Screens Node Name The node name for the interface (C-LAN port) defined by this data module. Valid Entries Data Module Types Usage A name administered on the Node Names Screen. ppp This name is associated with an IP address of the port on the Node Names screen. For a ppp data module, AUDIX and MSA names listed on page 1 of the Node Names screen are not allowed in this field — only names listed on pages 2–6 of the Node Names screen are valid.
A Networking Screens Establish Connection? Screens Reference Specifies whether this switch will be responsible for the call setup for this connection. Valid Entries Data Module Types Usage y/n procr-intf x.25 Enter y if the System is responsible for any part of the call setup for the link defined by this data module. Default is n.
A Networking Screens Screens Reference When adding an access endpoint with the ITC administered as restricted, its associated port can be a channel from a DS1 circuit pack with Zero Code Suppression administered as zcs or b8zs. For an existing access endpoint, ITC can only be changed from restricted to unrestricted if its associated port is a channel of a DS1 circuit pack with its Zero Code Suppression field administered as b8zs.
A Networking Screens Screens Reference Data Module — Type ethernet Use the ethernet data module type to define an interface between port 17 on the C-LAN board and the LAN. This data module associates a link number and extension number with the C-LAN port address.
A Networking Screens Screens Reference Data Module — Type ppp Use the ppp data module for direct point to point TCP/IP connections between DCS nodes. This data module associates a link number and destination node with the port address and node name for the local node. The fields on this form can be changed only when the corresponding port on the C-LAN circuit pack has been busied-out.
A Networking Screens Screens Reference Valid Value Usage The default subnet mask is one of three values depending on the class of the IP address of the local C-LAN port: Enter a value for the subnet mask to specify the subnet group to which the IP address of this node belongs. • Class A: 255.0.0.0 • Class B: 255.255.0.0 • Class C: 255.255.255.0 The valid subnets for each Class of address are: Class A (default 255.0.0.0) Class B: (default 255.255.0.0) Class C (default 255.255.255.0) 255.192.
A Networking Screens Destination Digits Screens Reference Used to enable access to the correct trunk group at the far end of the connection. This is typically the trunk access code (TAC) plus the extension of data module on the far end. If you use just the extension, then you must administer UDP and AAR route patterns to access the correct trunk group. Valid Value Usage The extension or TAC + extension of the destination data module.
A Networking Screens Screens Reference Data Module — Type procr-intf (used for BX.25 connections with the si model) Use the procr-intf data module type to define an interface between the Processor Interface circuit pack and the DS1 facilities carrying the X.25 data for the connection to far end switch. This data module associates a link number with a physical channel number and extension number for the PI port used for the connection. This form applies when the Destination Number field is not set to eia.
A Networking Screens Screens Reference Common Fields See Common Data Module Fields (256) for descriptions of fields on this screen that are not listed below. Physical Channel A number used by the switch software to identify the physical channel. Valid Value Usage A 2-digit number equal to the link number entered on this screen.
A Networking Screens Screens Reference Assigned Member Ext and Name Display only. Extension and name of a previously administered user who has an associated Data Extension button and who will share the use of the module. Clocking Displays only when the Destination Number field is set to eia (and Link = 1). This field sets the clocking for the physical layer of the protocol.
A Networking Screens Screens Reference Data Module - type X.25 (used for BX.25 connections with the r model) This form applies only to the r model. Page 1 of 2 DATA MODULE Data Extension: ____ Name: Type: x.
A Networking Screens Error Logging? Permanent Virtual Circuit? Screens Reference Used to record X.25 protocol errors in the hardware error log. Valid Value Usage y/n Set to n for normal operations. Set to y for testing. Indicates that the logical channels for PVC are allowed for this port; default is y (cannot be changed). Valid Value Usage y/n Default is y. Switched Virtual Circuit? Indicates that the Switched Virtual Circuit is not allowed for this port; default is n (cannot be changed).
A Networking Screens Screens Reference Retry Attempt Counter (N2) Specifies the number of times (0–7) to send one frame when this frame is not confirmed for a period of time. Default is 2. Frame Size (N1) Specifies the number of bytes (135–263) in a frame. Default is 135. If the value is 135, there can be up to 1080 bits within a frame. This value is suitable for all adjuncts and for DCS. Retransmission (T1) The T1 timer is started at the beginning or the end of the transmission of a frame.
A Networking Screens Screens Reference Data Module - type pdm (used for BX.25 connections with the r model) This form applies only to the r model. This form assigns a Modular Processor Data Module (MPDM) data module (700D, 7400B, 7400D or 8400B).
A Networking Screens Screens Reference Communication-Interface Processor Channel PROCESSOR CHANNEL ASSIGNMENT Proc Chan 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: Gtwy Enable Appl.
A Networking Screens Appl. Screens Reference Identifies the switch application used on this link. Valid entries Usage audix, dcs, fp-mwi, gateway, gtwy-tcp, mis, msaamwl, msaclk, msahlwc, msallwc, msamcs, qsig-mwi, and blank The gateway application is used for conversion between ISDN and either TCP/IP or BX.25. The gtwy-tcp application is used for conversion between BX.25 and TCP/IP. These application types are used on the gateway switch only. Gtwy To Used for gtwy-tcp applications only.
A Networking Screens Interface Link Screens Reference Identifies the physical link carrying this processor (virtual) channel. Valid entries Usage 1-25 (csi, si) For the csi model, all links (up to 25) must be used for tcp/ip connections. 1-33 (r) For the si model, links numbered 1 through (4 times the number of PI circuit packs) can be either x.25 or tcp/ip. The rest of the links (up to 25) must be tcp/ip.
A Networking Screens Destination Port Session Local Screens Reference Identifies the port number of the destination. Valid entries Usage 0, 5000-64500 The channel number 0 means any available port can be used (which will be automatically selected by the system). A number used by the system to identify one end of a connection. Valid entries Usage 1-128 (csi) 1-256 (si) 1-384 (r) The Local and Remote Session numbers can be any value between 1 and 256, but they must be consistent between endpoints.
A Networking Screens Screens Reference Circuit Packs This screen administers circuit packs to carrier slots before the circuit packs are actually installed in the carrier or cabinet. This allows the system to be configured (administered) when the circuit packs have not yet been physically inserted in their appropriate slots.
A Networking Screens Carrier Screens Reference This field shows the letter of the carrier (A through E) circuit packs are being administered on. Valid entries Usage Display-only field. Cabinet Layout Carrier Type This field is only displayed for G3r. This field describes the physical layout of the cabinet. Valid entries Usage Display-only field. Values that may display are five-carrier and single-carrier-stack. This field shows the type of carrier.
A Networking Screens Code Screens Reference Enter the circuit pack code. If there is a physical circuit pack installed in the slot, the entry must match that of the circuit pack. If there is equipment administered on a slot, the equipment must be removed from the circuit pack before the circuit pack can be changed or removed. Valid entries Usage TN followed by a 3- or 4-digit number of a valid DEFINITY circuit pack.
A Networking Screens Screens Reference Signaling Group The Signaling Group screen defines the signaling parameters for ISDN-PRI, H.323, and ATM signaling groups. Type ISDN-PRI The ISDN-PRI Signaling Group screen identifies groups of DS1 interface B-channels for which a given D-channel or D-channel pair carries associated signaling information.
A Networking Screens Screens Reference Group Number Display-only field when the screen is accessed using an administration command such as display or change. Valid entries Usage Display-only field Associated Signaling For FAS, the D-channel can carry signaling information only for B-channels located on the same DS1 circuit pack. Valid entries Usage y Indicates Facility Associated Signaling n Indicates Non-Facility Associated Signaling.
A Networking Screens Screens Reference Secondary D-channel Enter a 6- to 7-character port number associated with the DS1 Interface circuit pack port used for secondary D-channel signaling. Displays when the Associated Signaling field is n (indicates NFAS). The port number assigns the secondary D-channel in the Signaling Group. For 24-channel facilities, the 24th port is assigned as the D-channel. For 32-channel facilities, the 16th port is assigned as the D-channel.
A Networking Screens Screens Reference Trunk Group for Channel Selection Enter the assigned trunk group number. (An ISDN-BRI trunk group may not be used.) Valid entries Usage 1 to 99. blank Supplementary Service Protocol Determines whether AT&T NCA TSCs or QSIG NCA TSCs are sent over the interface. To change this field from a to b, first check the Adm’d NCA TSC Index field on the ISDN TSC Gateway Channel Assignments (page 291).
A Networking Screens NCA TSC Screens Reference The Non-call associated temporary signaling connections (NCA TSC) are administered on pages 2–5 of the ISDN-PRI and H.323 Signaling Group screens, and on pages 3–6 of the ATM Signaling Group screen. ADMINISTERED NCA TSC ASSIGNMENT Page 2 of 5 Service/Feature: __________ As-needed Inactivity Time-out (min): __ TSC Local Adj. Mach. Index Ext. Enabled Established Dest. Digits Appl.
A Networking Screens Screens Reference As-needed Inactivity Time-out (min) The inactivity time-out for as-needed NCA-TSCs assigned in the Signaling Group. An as-needed administered NCA-TSC staying inactive in this time period will be removed from service. Valid entries Usage 10 to 90 blank TSC Index Specifies the administered NCA-TSCs assigned. Valid entries Usage Display-only field. The administered NCA TSC index represents one DCS or DCS AUDIX logical channel connecting any two switches.
A Networking Screens Screens Reference Dest. Digits Used to route the administered NCA-TSC to the far end switch. These digits are sent as entered to the destination switch; no routing or other digit manipulation is performed. Valid entries Usage 0 through 9 Can include up to 15 digits. + * # blank Appl. Specifies the application this administered NCA-TSC is going to be used for. Valid entries Usage audix Used for ISDN-PRI D-channel DCS AUDIX feature.
A Networking Screens Screens Reference The H.323 signaling group type is used for H.323 trunks. Type H.323 Page 1 of 5 SIGNALING GROUP Group Number: 2 Group Type: h.
A Networking Screens Screens Reference Far-end Listen Port . Valid entries Usage blank or Optional. If entered, the same number as entered in the Near-end Listen Port field is recommended; if not left blank, this number must match the number entered in the Near-end Listen Port field on the signaling group form for the far-end switch. 0–65535 IRQ Required? . Valid entries Usage y Leave the default (n) if the far-end switch is a DEFINITY ECS.
A Networking Screens Screens Reference The atm signaling group type is used for atm trunks.
A Networking Screens Screens Reference Country Protocol . Valid entries Usage 1–25 or etsi Use 1 for the U.S. Protocol version . Valid entries Usage a, b, or c Circuit Type . Valid entries Usage T1 or E1 Use T1 for U.S. and Japan. Use E1 elsewhere. Connect . Valid entries Usage host, network, or pbx DCP/Analog Bearer Capability . Valid entries Usage 3.1kHz or speech Internetworking Message .
A Networking Screens Screens Reference ISDN TSC Gateway Channel Assignments This screen is required when the switch is to act as a gateway between a switch that supports the Temporary Signaling Connections (TSC) feature and a non-TSC-compatible switch. The gateway provides interface protocols necessary for communications to exist between a switch administered with Non-Call Associated TSCs in a Signaling Group on the ISDN side and a processor channel (BX.25) on the non-ISDN side.
A Networking Screens Processor Channel Screens Reference Used to indicate the processor channel to which the administered NCA-TSC index will be mapped. This processor channel is used as another endpoint of the connection in this gateway assignment. Valid entries Usage 1 to 64 blank Application Used to indicate the feature this gateway is used for. Gateway channels can be used for DCS+ or ISDN-PRI DCS AUDIX feature.
A Other Networking-Related DEFINITY Screens Screens Reference Other Networking-Related DEFINITY Screens Communication Interface Links This screen is display-only starting with Release 7. The fields are now administered on the Data Module screens associated with the link. There is one Interface Link screen per System. Interface Links provide a physical interface between the system and the other nodes in a DCS, ISDN, a Message Server Adjunct, a CMS, an ISDN Gateway adjunct (supports CPN/BN), or AUDIX.
A Other Networking-Related DEFINITY Screens Est Conn Screens Reference If the physical link is over a DS1 interface, it is possible (except for ISDN signaling links) for one switch to set up the entire connection (see Destination below). In this case, the other switch will not initiate any part of the connection between the two endpoints.
A Other Networking-Related DEFINITY Screens Screens Reference Data Module - type netcon Page 1 of 1 DATA MODULE Data Extension: ____ Type: netcon Physical Channel: __ Name: ______________ ITC: restricted Name: COS: _ COR: _ TN: _ BCC: _ Maintenance Extension: ____ Maximum Bit Rate: ____ ABBREVIATED DIALING List1: _______________ SPECIAL DIALING OPTION: ____ HOT LINE DESTINATION Abbreviated Dialing Dial Code (From above list): _ ASSIGNED MEMBER (Station with a data extension button for this data modul
A Other Networking-Related DEFINITY Screens Abbreviated Dialing List 1 Specifies the type of abbreviated dialing list. Valid Value Usage s (system) g (group) p (personal) e (enhanced) blank If g or p is entered, a group number or personal list number also is required. Entry in this field supports Data Hot Line. This field can be left blank.
A Other Networking-Related DEFINITY Screens Screens Reference Data Module - type analog-dm This type of data module behaves identically to a 2500 set, but it accepts rotary dial pulses.
A Other Networking-Related DEFINITY Screens Screens Reference Extended Trunk Access Call Screening This screen allows a set of digit strings to be identified that should not be routed via ETA. This screen can also block the routing of certain FACs or TACs.
A Other Networking-Related DEFINITY Screens Screens Reference Extension Number Portability Numbering Plan Page 1 of 1 ENP Code 0x: ___ 00: ___ 01: ___ 02: ___ 03: ___ 04: ___ 05: ___ 06: ___ 07: ___ 08: ___ 09: ___ EPN Code ENP Code 1x: ___ 10: ___ 11: ___ 12: ___ 13: ___ 14: ___ 15: ___ 16: ___ 17: ___ 18: ___ 19: ___ ENP Code 2x: ___ 20: ___ 21: ___ 22: ___ 23: ___ 24: ___ 25: ___ 26: ___ 27: ___ 28: ___ 29: ___ EXTENSION NUMBER PORTABILITY NUMBERING PLAN ENP ENP ENP ENP Code Code Code Code 3x: _
A Other Networking-Related DEFINITY Screens Screens Reference Hop Channel Assignments Screen This screen assigns Hop Channels. The maximum number of connections that may be established between channels on the system’s interface links varies depending on System configuration.
A Other Networking-Related DEFINITY Screens Link Screens Reference Enter an interface link number in each field. Valid entries Usage 1 to 8 blank Chan(nel) Enter a channel number in each field. This field is labeled "Channel" for G3r and "Chan" for G3si. Valid entries Usage 1 to 64 blank Priority Indicates whether the hop channel has high or low priority. Priorities should be assigned based on the operational speed of the links and the number of hops in the network channel.
A Other Networking-Related DEFINITY Screens Screens Reference Node Number Routing This screen specifies the routing pattern associated with each node in a public or private network. NNR is a required capability for Extension Number Portability (ENP) and is associated with the Uniform Dial Plan (UDP).
A Other Networking-Related DEFINITY Screens Screens Reference Message Waiting Indication Subscriber Number Prefixes The information entered on this screen enables MWI messages to be routed to the subscriber’s switch in a QSIG network.
A Other Networking-Related DEFINITY Screens Screens Reference Synchronization Plan This screen assigns primary and secondary external synchronization sources. This provides synchronization between the switch and digital facilities that the switch is connected to. When the switch is connected to digital facilities, the switch (both Processor Cabinets and Expansion Cabinets) must be synchronized to the incoming data rate of 8,000 frames-per-second.
A Other Networking-Related DEFINITY Screens Primary Screens Reference Enter the 5-character circuit pack location number for the circuit pack that will function as the primary synchronization source. The clock circuit pack’s internal source is the implicit last choice. Only one switch in the network can function as the primary synchronization source. Only displays when the Stratum field is 4.
A Other Networking-Related DEFINITY Screens Slip Screens Reference Displays as y if the Slip Detection field has been enabled for any of the 8 ports on the DS1 Circuit Pack screen. Valid entries Usage Display-only field. Type Contains a value for each displayed circuit pack that indicates the circuit pack’s maintenance name. For example, UDS1-BD appears for a TN464 circuit pack, and TBR1-BD appears for a TN2185 circuit pack. Valid entries Usage Display-only field.
A Other Networking-Related DEFINITY Screens Screens Reference Uniform Dial Plan This screen administers the Uniform Dial Plan (UDP).
A Other Networking-Related DEFINITY Screens Ext Code, Type (and associated data) Screens Reference Displays what rules apply if the entries on the screen are not administered. For example, shows a screen for Ext Codes starting with 512. If these entries are not administered, the entry for Ext Code 51xxx applies to these entries, and if Ext Code 51xxx is not administered, the entry for Ext Code 5xxxx applies to these entries.
A Other Networking-Related DEFINITY Screens Type Screens Reference Specify the type of treatment for the extension. That is, specify whether the extension should receive intercept treatment, be converted to AAR, or be converted via ENP. The difference between AAR Location Codes and UDP Location Codes is that 7-digit AAR Numbers created from AAR Location Codes may be changed during AAR analysis by AAR digit conversion before being routed.
A Other Networking-Related DEFINITY Screens 310 CID: 77730 Screens Reference Administration for Network Connectivity 555-233-504 — Issue 1 — April 2000
B Private Networking This appendix contains five main sections: (1) a description of Distributed Communications System (DCS) and the features that can be used transparently on a DCS network, (2) a description of ISDN Plus networking capability, (3) a description of QSIG and its features, (4) a brief description of Centralized Voice Mail with Mode codes, and (5) a brief description of Japan TTC private networking protocols.
B Distributed Communications System Private Networking Distributed Communications System Distributed Communications System (DCS) allows you to configure 2 or more switches as if they were a single, large DEFINITY ECS. DCS provides attendant and voice-terminal features between these switch locations. DCS simplifies dialing procedures and allows transparent use of some of the DEFINITY ECS features.
B Distributed Communications System Private Networking DCS Features Once you have connected and set up your DCS network, you can provide the following features across the network: Alphanumeric Display for Terminals This feature allows calling-name display, called-name display, and miscellaneous identifiers to be transferred from a terminal on one node to a terminal on another node.
B Distributed Communications System Private Networking Automatic Callback DCS Automatic Callback allows a user at one node to make an automatic callback call to a user at another node in the DCS. A DCS Automatic Callback call can be initiated from a terminal at one node to a terminal at another node in the same way as if at a local node under the following conditions.
B Distributed Communications System Private Networking Call Coverage DCS Call Coverage provides DCS messaging required for calls to be covered on remote systems when there is a DCS signaling link (BX.25, PPP, or ISDN-PRI) for the trunk groups. Calls to an extension on one system are covered by extensions on remote systems that are administered as coverage points. Figure 4 shows an example of DCS Call Coverage. Figure 4. DCS Call Coverage 1. Station A 7. PGATE or PI Board 2.
B Distributed Communications System Private Networking Error Condition Action DCS link not up. The call is routed to the remote coverage point. If the call is answered, it is treated as Call Coverage Off Premises (also called Remote Call Coverage). If the call is redirected at the remote coverage point before the DCS SRI expires, the remote point’s path is followed.
B Distributed Communications System Private Networking ~ A call to the principal redirects to the remote coverage point. While the remote coverage point is ringing, the principal answers the call. In this case the call is not cut through to the coverage point. Instead, ringing and ringback is removed from the coverage point and the call is cut through to the principal.
B Distributed Communications System Private Networking Multiappearance Conference/ Transfer DCS Multiappearance Conference/Transfer provides transparency for transferring calls and conferencing calls within a DCS network. A user in the DCS can initiate conference calls among or transfer calls originated from extensions in the DCS network to another extension within the DCS by dialing the UDP extension. (For transferred calls, the destination need not be within the DCS.
B Distributed Communications System Private Networking Interactions • When interworking with non-ISDN trunks or non-Supplementary Service Option E ISDN trunks, DEFINITY acts as a gateway in the following sense: ~ When a call is tandeming through a DEFINITY system from a non-ISDN trunk to an SSE trunk or from a non-Option E to an SSE trunk, the system acts as an incoming gateway.
B Distributed Communications System Private Networking ISDN/X.25 gateway DEFINITY ECS can serve as an interface between PBXs that support the D-channel signaling feature and those that do not support this feature. The switch providing this interface is known as the ISDN-DCS Gateway node and provides backward compatibility to existing traditional DCS networks. It maintains a mapping between processor channels and Administered NCA-TSCs.
B Distributed Communications System How to administer DCS Over ISDN-PRI D-channel Form Private Networking Field Signaling Group • Max number of NCA TSC • Max number of CA TSC • Trunk Group for NCA TSC • Administered NCA TSC Assignment fields • Service/Feature • Inactivity Time-out (min) ISDN TSC Gateway Channel Assignments • All Trunk Group (ISDN-PRI) • Used for DCS Node Number DCS Signaling • NCA TSC Trunk Member • TSC • CA TSC Request • Application Route Pattern Processor
B Distributed Communications System Private Networking NCA-TSC An NCA-TSC is a connection not related with any ISDN B-channel connections. DECINITY ECS supports two types of NCA-TSC that conform to two different protocol standards: • The QSIG type of NCA-TSC is used for certain QSIG features such as Call Completion (Automatic Call Back). This type of NCA-TSC is referred to in the QSIG protocol standards as a Call-Independent Signaling Connection (CISC).
B Distributed Communications System Private Networking DCS feature considerations Attendant • If you call an attendant on another switch in the DCS network, your display shows the attendant’s name, but does not show the attendant’s extension, instead you see a zero where the extension should be. Alphanumeric Display considerations • On outgoing DCS calls, display of the called name may be delayed for a few seconds until the required information arrives from the distant node.
B Distributed Communications System DCS Over ISDN-PRI D-channel considerations • Private Networking The gateway node serves as the terminating node to the D-channel DCS network as well as the terminating node to the traditional DCS network. A PBX serving as an ISDN DCS Gateway node introduces some interesting situations when administering processor channels in an associated traditional DCS PBX. In a traditional DCS network, (BX.
B Distributed Communications System Private Networking DCS Interactions Alphanumeric Display The following features allow transparency with respect to Calling or Called Name Display and miscellaneous ID. • Call Coverage At the calling terminal, the miscellaneous id “cover” is not displayed. • Call Forwarding When a system user calls a party on a different node in the DCS and the call is forwarded, the miscellaneous ID “forward” is not displayed.
B Distributed Communications System Private Networking Attendant Display • When both ISDN and DCS display information, or only DCS display information, is received, the switch displays the DCS display information in the DCS format. If ISDN display information is received, and no DCS display information is received, then the ISDN display information displays in the ISDN formats.
B Distributed Communications System • Private Networking Leave Word Calling Back to Principal With DCS Call Coverage, a covering user on a different node cannot press their LWC button to leave a message for the principal to call the covering user. • Queuing DCS Call Coverage interacts with queuing in the following way.
B Distributed Communications System • Private Networking D-channel Backup In the event of a D-channel switchover (primary to secondary or secondary back to primary) in a private network, administered NCA-TSCs that were active are assumed to have remained active. Any unacknowledged user-user service requests are assumed to be rejected, and administered NCA-TSCs which were in the process of being established at the time of the switchover are dropped when the switchover occurs.
B Distributed Communications System Enhanced DCS • Private Networking Class of Restriction When a call goes to coverage, it is the called party’s (not the covering party’s) restrictions that are used. LWC • DCS Multi-appearance Conference/Transfer Activation of LWC is denied after a DCS call has been conferenced or transferred. Multiappearance Conference/Transfer • Voice Terminal Display No display transparency is provided for DCS Multi-Appearance Conference/Transfer.
B Distributed Communications System Figure 5. Private Networking 2-Node private network G3i PBX ID 1 RNX 221 AUDIX G3i PBX ID 2 RNX 222 SWITCH 2 SWITCH 1 BX.25 Link 1 AUDIX 1 1/1 1/2 AUDIX 2 1 Link 2 D-CHANNEL 1 DCS 1-2 TSC 2/1 . . . . . . . . . . . . . . . . . . 4/1 TSC . . . . . . . . . . .2/2 . . . . . . .AUDIX . . . . . . . . . .2. . . . 4/2 1/1 1/2 The following tables show you how you would complete each of the necessary forms.
B Distributed Communications System • • • • • Private Networking Signaling Group form (signaling group 2) TSC Local Enabled Index Ext. 1 4900 y 2 4901 y Establish Dest. Far-end Appl. Ext. PBX-ID permanent 5900 2 dcs permanent 5901 - gateway Trunk Group form Group # Grp Type Used for DCS? DCS Sig.
B Distributed Communications System • • • • • 3-Node public/private network with AUDIX 332 Private Networking AAR Digit Conversion form Matching Pattern Min Max Del Replacemen t String Net Conv 222 7 7 3 - ext n AAR Analysis Table Dialed String Min Max Rte Pat Call Type Node Num 221 7 7 1 aar 1 Signaling Group form (signaling group 4) TSC Index Local Ext. Enabled Establish Dest. Far-end Ext.
B Distributed Communications System Figure 6. 3-Node public/private network G3i PBX ID 1 RNX 221 AUDIX G3i PBX ID 2 RNX 222 SWITCH 1 BX.25 1 AUDIX 1 1/1 AUDIX 2 1/2 AUDIX 3 1/3 Private Networking 1 Link 2 SWITCH 2 D CHANNEL 1 1/1 1/2 DCS 1-2 TSC 2/1 . . . . . . . . . . . . . . . . . . . . . . . . . 4/1 TSC AUDIX 2 . . . . . .2/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4/2 1/3 DCS 1-3 2/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AUDIX 3 . . . . .
B Distributed Communications System Private Networking Administration for switch 1 • • • • • • 334 Dial Plan form Start Dig.
B Distributed Communications System • • • Private Networking Routing Pattern form Routing Pattern # Trunk Group # FRL Del TSC CA-TSC Request 2 2 0 3 y at-setup 3 3 0 3 y at-setup Gateway Channel form Signaling Group TSC Index Processor Channel Application 2 2 60 audix 2 4 61 audix Processor Channel form Proc Channel Application Inter. Link Channel Remote Proc.
B Distributed Communications System • • Private Networking AAR Analysis Table Dialed String Min Max Rte Pat Call Type Node Num 221 7 7 1 aar 1 223 7 7 3 aar 3 Signaling Group form Signaling group 4 TSC Local Enabled Index Ext. 1 5900 y 2 5901 Establish Dest. Far-end Appl. Ext. PBX-ID permanent 4900 1 dcs y permanent 4901 - audix Enabled Establish Dest. Far-end Appl. Ext. PBX-ID 6905 3 Signaling group 5 • TSC Local Index Ext.
B Distributed Communications System • • • • • • Private Networking Uniform Dial Plan form Ext Code Type Location Code 4xxx UDPcode 221 5xxx UDPcode 222 AAR Digit Conversion form Matching Pattern Min Max Del Replacement String Net Conv 223 7 7 3 - ext n AAR Analysis Table Dialed String Min Max Rte Pat Call Type Node Num 221 7 7 1 aar 1 222 7 7 2 aar 2 Signaling Group form (signaling group 4) TSC Index Local Ext. Enable d Establish Dest. Ext.
B Distributed Communications System Private Networking Centralized Attendant Service Centralized Attendant Service (CAS) allows attendants in a private network of switching systems to be concentrated at a central or main location. Thus, CAS reduces the number of attendants required at a branch. For example, a chain of department stores can have a centralized attendant location at the main store to handle calls for the branch stores. Form Field Page System-Parameters Customer-Options Async.
B Distributed Communications System Detailed description Private Networking Each branch in a CAS has its own LDN or other type of access from the public network. Incoming trunk calls to the branch, as well as attendant-seeking voice terminal calls, route to the centralized attendants over release link trunks (RLT). The CAS attendants are at the main location. The main location can be a DEFINITY ECS, a DEFINITY System Generic 1 or 3, a DEFINITY System Generic 2.
B Distributed Communications System Private Networking Branch-generated call-identification tones The branch in a CAS network generates call-identification tones and transmits them to the CAS attendant by way of the RLT. These tones indicate the type of call coming from the branch or the status of a call extended to or held at the branch. The attendant hears these tones in the console handset before being connected to the caller. The tones may vary by country.
B Distributed Communications System Interactions Private Networking • When an analog-station call goes to coverage, the station drops from the call. This is the exception to the branch leaving the extended-to party ringing. If the main attendant extends a call to an analog station and that call goes to coverage and later returns to the main attendant, the call is treated as an incoming LDN call and the attendant must re-extend the call, if requested by the user.
B Distributed Communications System • Private Networking DCS Operation If an RLT trunk group is administered as a DCS trunk, the following interaction applies: On an incoming CAS call to the attendant, the DCS message displays instead of the name of the incoming RLT trunk group. Upon answering the call, the attendant hears call-identification tones, indicating that the call is a CAS call. Use a TRUNK-NAME button to obtain the name of the RLT trunk group.
B Distributed Communications System Emergency (911) Calls Private Networking The Enhanced 911 (E911) systems installed in many jurisdictions in the U.S. are equipped so that by dialing a service code (911 in the U.S.) a victim of a fire, accident, crime, or medical emergency may quickly access a public safety agency that will dispatch the appropriate response.
B Distributed Communications System Private Networking Extended Trunk Access Use Extended Trunk Access (ETA) in conjunction with Uniform Dial Plan (UDP) to allow DEFINITY ECS to send any unrecognized number (such as an extension not administered locally) to another switch for analysis and routing. Such unrecognized numbers can be Facility Access Codes, Trunk Access Codes, or extensions that are not in the UDP table.
B Distributed Communications System Private Networking In this case, the ETA Route Pattern routes undefined dialed strings. However, since an ETA Node Number is not specified, non-call-related DCS messages are not routed. CASE #3 • ETA Route Pattern — Not administered • ETA Node Number — Administered In this case, the ETA Node Number provides the route pattern. Non-call-related DCS messages also can route since a node number is supplied.
B Distributed Communications System Private Networking Extension Number Portability Extension Number Portability (ENP) gives you the ability to assign any extension to any switch in an ENP subnetwork. Stations can be moved across switches while retaining the original extension number, as long as the switches are part of the ENP subnetwork. EPN is used in conjunction with Automatic Alternate Routing (AAR) and Uniform Dial Plan (UDP).
B Distributed Communications System Interactions • Private Networking Distributed Communications System If you use DCS, the ENP node numbers must correspond to DCS node numbers. Inter-PBX Attendant Service Inter-PBX Attendant Service (IAS) allows attendants for multiple branches to be concentrated at a main location. Incoming trunk calls to the branch, as well as attendant-seeking voice-terminal calls, route over tie trunks to the main location.
B Distributed Communications System • Private Networking Centralized Attendant Service CAS and Inter-PBX attendant calling cannot be used at the same time. • Dial Access to Attendant Administer Dial Access to Attendant via the dial platform to the same digit on both the IAS main switch and the IAS branch switch. On the branch switch, administer the PBX attendant access code (Console Parameters form) to match the main PBX attendant-group dial access code.
B Distributed Communications System Detailed description Private Networking Private networks can include: • Common-control switching arrangement (CCSA) • Distributed Communications Systems (DCS) and Enhanced DCS (EDCS) • Electronic tandem network (ETN) • Enhanced private-switched communications service (EPSCS) • Tandem-tie-trunk network (TTTN) • Italian Traslatore Giunzione Uscente/Entrante/Interno (TGU/TGE/TGI) trunks Unless prohibited by the COR, all incoming private network trunks, except
B Distributed Communications System Private Networking Uniform Dial Plan Uniform Dial Plan (UDP) provides a common 4- or 5-digit dial plan (specified in the Dial Plan Record) that can be shared among a group of switches. Interswitch dialing and intraswitch dialing both require 4- or 5-digit dialing. UDP is used with an electronic tandem network (ETN); main, satellite, and tributary switches; and Distributed Communications Systems (DCS).
B Distributed Communications System Private Networking UDP conversion is specified for individual extensions or groups of extensions sharing the same leading digits, via the UDP form and extension codes. An extension code is the desired leading digits of an extension followed by an “x” (wildcard). For example, “123xx” “12345”is the extension code for all 100 possible extensions beginning with “123” plus two wild cards. “12345” is an extension code specifying one extension.
B Distributed Communications System Private Networking A given station is called using the same 5-digit extension regardless of where in the ETN the call originates. Three switches are included in the example. Each has been assigned a list of RNX and UDP codes. See Figure 7. Figure 7. SWITCH RNX UDP CODE A 224 41 C 223 51 C 223 52 B 222 60 B 222 61 UDP Example 2 1 5 4 6 3 7 8 r764905 CJL 062296 1. Switch A Dial Plan for extensions is 41XXX RNX=224 4. Extension 41000 2.
B Distributed Communications System Private Networking If a user at extension 41000 wants to call extension 61234, there are two choices: • Dial 61234 • Dial the AAR access code followed by 222-1234 If 61234 is dialed, the system recognizes 61 as a remote UDP, determines the associated RNX (222), and uses AAR to route the call to 222-1234. If the AAR access code and 222-1234 are dialed, the system finds the route pattern for RNX 222 and routes the call to the switch associated with that RNX.
B Distributed Communications System • Private Networking If AAR is active, FRLs and Traveling Class Marks (TCMs) can be sent along with the private network number. UDPCode and AARCode conversions use the FRL assigned to the caller. ENPNode conversion always raises the FRL to the maximum (7). If an FRL is insufficient to access the facility, access is denied. There is no prompt for an authorization code even if authorization codes are enabled and administered.
B ISDN Feature Plus Private Networking ISDN Feature Plus This feature allows you to have basic feature transparency over public networks without having a dedicated leased line. This provides a lower cost option for using the switched public network. How to administer ISDN Feature Plus Note: Only Lucent representatives perform step 1. 1 On the System-Parameters Customer-Options form, set the: ~ G3 Version field to V8. ~ ISDN Feature Plus field to y.
B ISDN Feature Plus Private Networking Description ISDN Feature Plus uses a DEFINITY ECS proprietary signaling protocol. The features do not function in the same way as their QSIG or DCS counterparts. To use Feature Plus, Phase I, you need DID extensions. In addition to the general Feature Plus call handling, Feature Plus includes the following features: • Centralized AUDIX — A simple, one step “coverage” to voice mail. If voice mail is unavailable for any reason, the call does not cover elsewhere.
B ISDN Feature Plus Private Networking Interrogation When performing an audit, the Served User PBX sends a request towards the Message Center PBX. As a Message Center PBX, the DEFINITY ECS receives the request message, maps it into a MW STATUS REQUEST - SINGLE STATION message, and sends it to AUDIX on the BX.25 link. When AUDIX replies to the DEFINITY on the BX.25 link with a MW STATUS UPDATE, the Message Center PBX sends the information on to the appropriate Served User PBX.
B ISDN Feature Plus • Private Networking Feature Plus Forwarding (Diversion) ~ Calling Line Identification Presentation (CLIP) If the public network supports CLIP and the forwarded-to user has subscribed to the service, then calling party information is available to the forwarded-to user’s display.
B ISDN Feature Plus • Private Networking Feature Plus Message Waiting Indication ~ Audio Information Exchange (AUDIX) Feature Plus MWI depends on the presence of a Message Center. Whenever DEFINITY ECS acts as a Message Center switch, there is an interaction between DEFINITY ECS and AUDIX. DEFINITY ECS must be able to receive messages from AUDIX then, if applicable, send the appropriate Feature Plus MWI message to the network.
B QSIG Private Networking QSIG QSIG is the generic name for a family of signaling protocols. The Q reference point or interface is the logical point where signaling is passed between two switches in a private network. QSIG signaling allows certain features to work in a single-vendor or multi-vendor network. QSIG complies with the International Organization for Standardization (ISO) Integrated Services Digital Network (ISDN) private-networking specifications.
B QSIG Private Networking QSIG Basic Call Setup Transit Counter (ANF–TC) DEFINITY ECS provides QSIG ANF-TC as defined in ISO/IEC 6B032 and 6B033. It prevents indefinite looping, connections giving poor transmission performance, and inefficient use of network resources. ANF-TC is invoked automatically for ISDN basic calls and the Route Pattern form indicates the number of switches through which a call may be routed.
B QSIG Private Networking Tandem switch information However, in the case of tandemed calls (calls involving two ISDN trunks that are not both administered for Supplementary Service Protocol B), trunk group administration may override both incoming name and number information, as long as doing so does not lower the restriction on the information.
B QSIG Call Offer Private Networking This feature is the QSIG equivalent of Call Waiting. A Private Telecommunication Network (PTN) offers up to four ways of invoking QSIG Supplementary Service - Call Offer (SS-CO) (listed below). DEFINITY ECS uses only the first way. • Network invocation (immediate) — the PTN automatically invokes SS-CO whenever the calling user makes a call to a user that is busy, if required by the service profile of the calling user.
B QSIG Private Networking An analog voice terminal user activates SS-CCBS or SS-CCNR by pressing the Recall button or flashing the switchhook and then dialing the Automatic Callback (ACB) Activation feature access code. An analog user can activate only one ACB call at any given time. A multiappearance voice terminal user can activate SS-CCBS or SS-CCNR for the number of ACB buttons assigned to the terminal.
B QSIG Private Networking Other QSIG Centralized Messaging With a QSIG centralized messaging system, the remote switch is called a served user switch. When an AUDIX system supports a QSIG network, the served user switch does not need to be a DEFINITY ECS, but the host, or message center, switch must be. QSIG allows a DEFINITY switch to be a served user switch of a non-DEFINITY message center switch.
B QSIG Path Retention Private Networking Path Retention is a generic mechanism for retaining a network connection that can be used by supplementary services during call establishment. The Originating PBX invokes path retention for one supplementary service or for several simultaneous supplementary services. Invoking a particular supplementary service means retaining the network connection if the Terminating PBX encounters the appropriate conditions.
B QSIG Private Networking QSIG CAS functions in RLT-CAS The following QSIG-CAS functions are currently in RLT-CAS: • Attendant-seeking calls at a branch reach the attendant at the main • Attendant splitting away and calling the extended to party • Night Service • Monitoring agents, per attendant group QSIG CAS functions not in RLT CAS The following QSIG-CAS functions are currently not in RLT-CAS: • Announcements for attendant seeking calls • Attendant calls enter the attendant queue, with pr
B QSIG QSIG Call Forwarding (Diversion with Rerouting) Private Networking This feature allows a forwarded call can be rerouted in a private network to find a more cost-effective or resource-efficient path.
B QSIG Private Networking QSIG Protocols QSIG signaling protocols are based on ITU-T (formerly CCITT) Q.931 access protocols across the Q reference point. QSIG standards are also supported by the ISDN Private Networking Specification (IPNS) Forum. DEFINITY ECS QSIG complies with a number of international regulations. For example, QSIG: • Complies with ISO standard 11572 for layer 3 to support private-network connectivity.
B QSIG NCA-TSC Private Networking An NCA-TSC is a connection not related with any ISDN B-channel connections. DECINITY ECS supports two types of NCA-TSC that conform to two different protocol standards: • The non-QSIG AT&T type of NCA-TSC is used for the DCS over ISDN-PRI D-channel and DCS AUDIX applications. Only ISDN-PRI Signaling Groups administered with Supplementary Service Protocol a support AT&T NCA-TSCs. For further information, see page 322.
B QSIG Private Networking Setting Up QSIG Steps Begin 1 Verify with your sales representative or project manager what QSIG capabilities the system should have. The following capabilities apply: Table 1.
B QSIG Private Networking 3 Enter display system-parameters customer-options on the command line of your system administration screen. 4 On page 1, verify fields as follows: ~ G3 Version field is V8 or later. 5 If the system is using ATM for QSIG, go to page 2 and verify the following field: ~ Async. Transfer Mode (ATM) Trunking field is y. 6 On page 3, verify fields as follows: If the system is using ISDN-BRI for QSIG: ~ ISDN-BRI Trunks field is y.
B QSIG Private Networking 10 Administer or check the QSIG ISDN trunk group(s) (PRI or BRI) connected to the DS-1 or BRI circuit pack (see Appendix A).
B QSIG Setting Up QSIG Supplementary Services Private Networking Steps Begin 1 Administer or check the ISDN Numbering - Public/Unknown screen (see Appendix A). 2 Administer or check the ISDN Numbering - Private screen (see Appendix A). 3 Administer or check the Signaling Group screen (see Appendix A).
B QSIG Private Networking Call Completion In addition to the Basic QSIG Supplementary Services administration described above, complete the following administration: • On the Trunk Group screen, page 1, set the Supplementary Service Protocol field to b and administer the trunk for Call Independent Signalling Connections.
B QSIG Setting Up QSIG VALU Call Coverage Private Networking Steps Begin 1 Enable the QSIG Basic Supplementary Services on the Customer Options screen, page 6, described above. 2 Enable (enter y) Value-Added Lucent (VALU) on the System-Parameters Customer-Options screen, page 6, as described above. 3 On a Trunk Group screen, enter y in the QSIG Value-Added Lucent field, page 1, and sent b in the supplementary Service Protocol Option field, page 1.
B QSIG • Private Networking Maintain SBA at Principal - Enter y to allow the user who originally receives the call to have simulated bridged appearance capability in the event the coverage point(s) are unavailable. This capability allows the user to break into the call before it is answered by a coverage endpoint. Note: If Maintain SBA at Principal is enabled (y), then Path Replacement is disabled.
B QSIG Private Networking See the Octel Serenade documentation for Serenade administration. Steps Begin 1 (Local node message center switch only) Complete the Processor Channel Assignment screen (see Appendix A). 2 (Local node message center switch only) Complete the Message Waiting Indication Subscriber Number Prefixes screen (see Appendix A). 3 (Local node message center switch only) Complete the Station screen as specified in the Intuity or DEFINITY AUDIX documentation.
B QSIG Private Networking QSIG Interactions Call Forwarding (Diversion) The interactions that apply to the standard DEFINITY ECS Call Forwarding features also apply to Call Forwarding (Diversion) with QSIG. The following are additional interactions. • Alternate Facilities Restriction Levels The AFRL of the original call is the AFRL used for Call Forwarding with Reroute. • Authorization Codes Call Forwarding with Reroute is denied to calls that require an Authorization Code.
B QSIG Call Transfer • Private Networking Call Forwarding (Diversion) When a call is forwarded and transferred or transferred and forwarded, the forwarding indication displays to the caller until the call is answered. This display includes the trunk group name and word “forward.” When the call is answered, the word “forward” is removed and the name and number of the answering party displays.
B QSIG • Private Networking Data-Call Setup A data call is denied ANF-PR. • Data Privacy If Data Privacy is active, ANF-PR is denied. • Data Restriction If Data Restriction is active, ANF-PR is denied. • Malicious Call Trace If MCT is active, ANF-PR is denied. • Recorded Announcement A call that is receiving a recorded announcement cannot have its path replaced. • Trunk Access Code The paths of outgoing calls made using a TAC are not replaced.
B QSIG • Private Networking Attendant Control of Trunk Group Access You cannot activate QSIG SS-CC if the call uses a controlled trunk group. • AUDIX You cannot activate QSIG SS-CC towards AUDIX. SS-CC to any transferred-to station is not allowed. • Automatic Call Distribution (ACD) You cannot activate QSIG SS-CC towards a voice terminal after dialing the ACD group extension. It is possible to invoke SS-CC towards a station when dialing the individual’s extension number.
B QSIG • Private Networking Internal Automatic Answer (IAA) If the IAA feature is enabled, QSIG SS-CC calls are not answered automatically. • Manual Originating Line Service A manual originating service cannot request QSIG SS-CC. • Multimedia Endpoints You cannot activate QSIG-CC towards multimedia data endpoints. • Restriction Features ~ Class of restriction (COR): Any terminal that is Origination-restricted cannot activate SS-CC.
B QSIG • Private Networking Authorization Codes The authorization codes do not block routing because the routing of TSCs used for QSIG MWI uses FRL 7. • Automatic Alternate Routing (AAR) AAR may be used to route the QSIG TSCs. • Automatic Route Selection (ARS) ARS may be used to route the QSIG TSCs. • Call Coverage Features The served user switch uses call coverage paths to route calls to users in the served user switch to the AUDIX hunt group on the Message Center switch.
B QSIG Called/Busy Name • Private Networking Adjunct Switch Applications Interface (ASAI) A Connected Number is sent in the Connected Event to ASAI adjuncts. Therefore, upon receipt of a Called/Busy Number, it is stored in such a way that it is not be sent accidentally as a Connected Number if no actual Connected Number is received in the CONNECT message when the call is answered.
B QSIG • Private Networking QSIG Centralized Attendant Service (CAS) The calls that cover from a QSIG CAS branch to main are not treated as QSIG-VALU Coverage calls. This is because calls covered to “attd” (administered as a coverage point on a Coverage Path form) do not utilize Remote Call Coverage table and QSIG-VALU Call Coverage is supported only for coverage points associated with Remote Call Coverage table.
B QSIG • Private Networking QSIG Call Transfer If a call that is transferred using QSIG Call Transfer transfer-by-join to a secondary user (i.e. Principal user for QSIG VALU Call Coverage) and the call is routed to a covering user by QSIG VALU Call Coverage and if the Principal user has a Simulated Bridge Appearance (SBA) and if a call goes through a QSIG Path Replacement successfully, the Principal user will loose the SBA.
B QSIG • Private Networking Attendant Control of Trunk Group Access Attendant control of trunk group access for QSIG-CAS functions as for RLT-CAS. • Attendant Crisis Alert Attendant crisis alert for QSIG-CAS functions as for RLT-CAS. • Attendant Direct Extension Selection With Busy Lamp (standard and enhanced) For QSIG-CAS the DXS allows attendants to use the DXS for monitoring and placing calls to users on the main PBX and for placing calls to users on a branch PBX only when UDP is used.
B QSIG • Private Networking Attendant Release Loop Operation Attendant Release Loop Operation is a local switch feature. It allows an unanswered extended call on the main to return to the attendant after an administrable amount of time. The call first tries to return to the same attendant that originally answered the call and, if that attendant is not available, the call goes to the next available attendant (waiting in the Attendant Queue if necessary).
B QSIG • Private Networking Call coverage The attendant group is allowed to be a coverage point. If the call covers from the branch to the main over a non-QSIG ISDN trunk, then the call is treated as a forwarded call. That is, Call Coverage Off Net (CCRON) procedures do not apply and the call is not brought back to the branch PBX.
B QSIG • Private Networking Conference If a user on a branch calls the attendant and conferences the attendant onto the call, the attendant’s display is not updated with “conference”. There is no QSIG standard defined for Conference and Definity has not implemented conference via MSI. • Centralized AUDIX When a user zero’s out of AUDIX, if the host PBX is a QSIG-CAS branch, then the call is sent to the QSIG-CAS attendant.
B QSIG • Private Networking Malicious Call Trace (MCT) MCT is a feature that is performed on existing calls. MCT does not generate new attendant seeking calls. MCT will work in QSIG-CAS provided the attendants performing MCT-Activate, MCT-Control, and MCT-Deactivate are all on the same PBX. That is, an attendant on the main cannot work with an attendant on the branch to perform MCT.
B QSIG • Private Networking Extending a Call QSIG CAS ensures that QSIG Path Replacement is attempted after split/swap, provided that all three parties (original calling party, the attendant, and the called party) are never conferenced together.
B QSIG • Private Networking Timed reminder and Attendant timers Attendant timers are: ~ Timed Reminder on Hold — starts when an attendant puts a call on hold. When this timer expires, the held call alerts the attendant. ~ Return Call Timeout — starts when a call is extended and then released from an attendant console. If this timer expires, the call is returned to the attendant. ~ Time In Queue Warning — indicates the amount of time a call can wait in the attendant queue before activating an alert.
B Centralized Voice Mail Via Mode Code Private Networking Centralized Voice Mail Via Mode Code You can use a single voice mail system to support multiple DEFINITY and Merlin Legend/Magix systems in a network via mode code. This capability is available for: • DEFINITY ECS R8 • Prologix R3 • BCS Issue 6 • Merlin Legend R6.1 • Merlin Magix 1.0 Note: DEFINITY One and Guestworks are not supported. Voice mail systems that support these connections are: • Intuity AUDIX R4.
B Centralized Voice Mail Via Mode Code Configuration example Private Networking Figure 8 shows what a configuration of centralized voice mail via mode might look like. In this configuration, DEFINITY system A is the hub. Voice mail system X is the centralized voice mail system. All other systems in the network are supported by voice mail system X except Legend system E and DEFINITY system D. These switches do not have a direct ISDN-PRI connection to the hub. Figure 8.
B Centralized Voice Mail Via Mode Code Private Networking Setting Up Centralized Voice Mail Via Mode Code The following step describe how to set up DEFINITY switches to support centralized voice mail. For information on setting up Merlin Legend/Merlin Magix, see Merlin Magix Integrated Systems Network Reference, 555-715-114. For information on setting up INTUITY Messaging Solutions, see INTUITY Messaging Solutions Integration with System 75, Generic 1 and 3, and R5/6.
B Centralized Voice Mail Via Mode Code Private Networking 10 On page 2, verify fields as follows: ~ Leave Word Calling Send a Message field is #90. ~ Leave Word Calling Cancel a Message field is #91. Note: All nodes in the system and the Voice Mail system must match this setting 11 For each DEFINITY node, enter add ds1UUCSS on the command line, where UUCSS is the address of the DS1 circuit pack. 12 On page 1, verify fields as follows: ~ Line Code field is B8ZS. ~ Framing field is extended superframe.
B Centralized Voice Mail Via Mode Code Private Networking 22 On Page 2 of the Station screen, administer or verify the following: ~ LWC Reception field is msa-spe (Message Server Adjunct-System Processing Element). ~ Leave Word Calling field is y. ~ Adjunct Supervision field is y. ~ Distinctive Audible Alert field is n. ~ Switchhook Flash field is y. ~ LWC Activation field is y. 23 For each remote DEFINITY node, enter change coverage remote on the command line.
Japan TTC Q931-a Private Networking Protocols B Private Networking Japan TTC Q931-a Private Networking Protocols The Telecommunications Technology Committee (TTC) of Japan defines national standards that are to be used in domestic public and private network facilities. The TTC typically modify other international standards as defined by ITU-T for use in Japan with additional national protocols to enhance operation for their customers.
Japan TTC Q931-a Private Networking Protocols B Private Networking TTC Q931-a Protocols The TTC defined private networking ISDN protocol is largely based upon ITU-T Q.931 protocol.
B Japan TTC Q931-a Private Networking Protocols Private Networking Setting Up TTC Q931-a Complete the following steps to set up TTC connections. Steps Begin 1 Verify that you have the appropriate DEFINITY circuit pack for integration 2 Enter “change system-parameters customer-options” on the command line of your system administration screen. 3 On page 1, verify that the G3 Version field is V8 or later 4 On page 2, verify that ISDN-PRI field is y. 5 Administer the TTC DS-1 circuit pack.
C Security Issues This Appendix briefly discusses issues related to system security for DEFINITY ECS in a TCP/IP network environment. Network Security Issues This section describes a strategy to ensure the security of an intranet that is connected to DEFINITY ECS R7 or later systems.
C Network Security Issues Security Issues A second line of defense can be thought of as damage control — how to limit the amount of damage that can be done if someone does gain unauthorized access to the system? Damage control can be provided by application restrictions. Each of these control methods is described below. Access control — network topology Network topology refers to how the DEFINITY ECS network is connected to the customer’s network.
C Network Security Issues Damage control — application restrictions Security Issues Release 7 provides damage control by what can be termed application restrictions. This simply means that DEFINITY ECS R7 has been designed to support only specific applications; that is, DCS and adjuncts. Other applications that could present security risks have been deliberately disabled.
C Network Security Issues 406 CID: 77730 Security Issues Administration for Network Connectivity 555-233-504 — Issue 1 — April 2000
D Capacities and Performance This Appendix discusses issues related system capacities and performance for DEFINITY ECS in an IP network environment. It provides a method of estimating the number of C_LAN and MedPro circuit packs that are needed to support various levels of traffic. This appendix provides performance and traffic configuration guidelines for the C-LAN (TN799B) and the MedPro (TN802B) circuit packs.
D Capacities and Performance The following table gives the number of sockets (connections) needed for IP softphones and H.323 trunks. For C-LAN Number of Sockets Required Number of sockets per road-warrior application (The H.323 sockets are held up = 3 (1 DCP + 2 H.323) 2 (1 DCP + 1 H.
D Capacities and Performance Performance Overview This section presents methods for estimating: • the impact on the processor • the impact on the TDM bus • the number of C-LAN boards • the number of MedPro boards Given assumptions about: • the number of H.323 endpoints: ~ # of road-warrior applications ~ # of telecommuter applications ~ # of native H.323 phones ~ # of H.323 Tie trunks ~ # of H.323 DID trunks Definitions • average number of C-LAN connections per H.
D Capacities and Performance Erlang. The Erlang is a unit of measure of the intensity of telephone traffic. It measures the average utilization of a set of system resources during a given time period. For example, if a server (trunk) is busy for 30 seconds over a measurement period of 2 minutes, the traffic intensity for that measurement period is 0.25 (30sec/120sec) Erlangs.
D Number of MedPros needed Capacities and Performance The following table gives the approximate carried load (CLm), in Erlangs, for m MedPro boards installed. Carried loads are shown for a = 22 and 31 audio streams per MedPro board, corresponding to having the G.723 or G.729A (a=22) or the G.711 (a=31) codecs administered. Number of MedPro boards CLm for GOS = P001 a = 22 a=31 a = 22 a=31 1 10.5 17.0 22 31 2 26.9 41.4 44 62 3 44.7 65.7 66 93 4 63.2 94.3 88 124 5 82.1 121.
D Number of C-LANs needed Capacities and Performance The number of C-LAN circuit packs needed can be estimated as follows: 1 Calculate the C-LAN socket carried load, for c sockets, CLc 2 The number of C-LANs needed is: # C-LANS = CLc/448 for infinite source, GOS of P001 # C-LANS = CLc/508 for “full availability.” Assumptions This formula assumes: Example • 508 is the maximum number of simultaneous TCP/UDP connections per C-LAN.
E C-LAN Installation This chapter provides instructions for installing and making the physical connections to the circuit packs that are new for R7 — the C-LAN (TN799) and the NetPkt (TN794) circuit packs. The C-LAN circuit pack is optional for R7 but required for TCP/IP connectivity in all switch models. The NetPkt circuit pack is required for R7 in the si model only. These instructions are also included in the upgrades and installation documents for each switch model.
E C-LAN Installation Install the C-LAN Circuit Pack The following sections describe the steps for installing the C-LAN circuit pack. Insert C-LAN Circuit Packs TCP/IP connections (10BaseT ethernet or ppp) require a TN799 C-LAN circuit pack. Complete the following steps to install these circuit packs. 1 Determine the carrier/slot assignments of the circuit packs to be added.
E Install C-LAN Cables C-LAN Installation Hub connection Install a cable from the backplane peripheral connector to a hub or wall field as required. See the figure below. 1 Connect the 259A connector to the backplane connector of the port slot containing the C-LAN circuit pack. 2 Connect the D8W cable between the 259A connector and a 10BaseT hub. Figure 9. Cable Connection for C-LAN 10BaseT Connectivity 1 2 3 cydflan2 EWS 101398 Figure Notes 1. 259A Connector 2. D8W Cable (max length 100m) 3.
E C-LAN Installation The following table shows the relationship between the backplane and the peripheral (Amphenol) pinouts, and the RJ45 pinouts on the D8W cable, for the C-LAN circuit pack in any port slot.
F IP Trunk Installation and Administration This appendix describes the procedures for installing and administering IP Trunk connections using the TN802 IP Interface circuit pack or the TN802B IP Interface set for IP Trunk mode. This appendix does not cover the TN802B IP Interface set for medpro mode for H.323 trunks — this material is covered in Chapter 2.
F IP Trunk Administration IP Trunk Installation and Administration IP Trunk Administration This section tells you how to administer the IP Trunk service after all installation procedures are complete. Prerequisites Before you can administer an IP trunk group, you must have one or more TN802 circuit packs (or TN802B set to IP Trunk mode) and a right-to-use license for the number of ports you need. Refer to DEFINITY ECS System Description for information on the TN802 circuit pack.
F IP Trunk Administration IP Trunk Installation and Administration NT Tasks • Log on to Windows NT and start the IP Trunk service • Use the Configuration Manager to administer the routes and dialing permissions you defined on the Dial/Routing Plan worksheets or the procedures for extension dialing between sites.
F IP Trunk Administration IP Trunk Installation and Administration For any two-site configuration, you would fill out Worksheet 1 and one of the worksheets 2–8. Use the worksheets as follows: 1 Fill out the general information about your sites using Worksheet 1. The Field Codes on Worksheet 1 consist of a number (1 or 2) that indicates the site, and a letter (A–J) that indicates a field on an administration screen.
F IP Trunk Administration IP Trunk Installation and Administration DEFINITY administration procedures The following procedures must be performed on the DEFINITY ECS to administer IP Trunks. ! CAUTION: The fields described in the following procedure must be completed as shown. If they are not, the IP Trunk service may not work properly. Other fields may be completed as appropriate for your system.
F IP Trunk Administration IP Trunk Installation and Administration More information The table below summarizes field settings on the DS1 screen for the T1 and E1 service emulated for IP Trunk service. Field Setting for T1 Setting for E1 Bit Rate 1.544 2.
F IP Trunk Administration IP Trunk Installation and Administration TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Comm Type: 5__ Group Type: tie CDR Reports: y IP Trunk 01A09 COR: 85_ TN: 1__ TAC: 105_ two-way_ Outgoing Display? y Trunk Signaling Type: ____ n Busy Threshold: 99_ Night Service: ____ 0__ Incoming Destination: ____ voice Auth Code? n TRUNK PARAMETERS Trunk Type (in/out): wink/wink___ Outgoing Dial Type: tone_____ Wink Timer (msec): 300 Digit Treatment: inserti
F IP Trunk Administration IP Trunk Installation and Administration TRUNK GROUP Administered Members(min/max): 1/12 Total Administered Members: 12 GROUP MEMBER Port 1: 01A0901 2: 01A0902 3: 01A0903 4: 01A0904 5: 01A0905 6: 01A0906 7: 01A0907 8: 01A0908 9: 01A0909 10: 01A0910 11: 01A0911 12: 01A0912 13: _______ 14: _______ 15: _______ ASSIGNMENTS Code Sfx ___________ ___________ ___________ ___________ ___________ ___________ ___________ ___________ ___________ ___________ ___________ ___________ ________
F IP Trunk Administration IP Trunk Installation and Administration Backing up configuration manager Lucent recommends you perform a backup to the Personal Computer Memory Card International Association (PCMCIA) flash disk whenever you make a change in the configuration manager. Keep the flash disk in a safe place so you can use the backup information if your MAPD circuit pack fails or if you want to restore to a previous known state.
F IP Trunk Administration IP Trunk Installation and Administration Confirming the number of available ports To confirm that all ports allowed under your license are available, start at the Windows NT desktop: 1 Double-click the Configuration Manager icon. IP Trunk Configuration Manager appears. 2 Click the Telephony tab. The Telephony property page appears. 3 Click Show All Ports. Verify that the number of enabled port matches the maximum your license allows.
F IP Trunk Administration IP Trunk Installation and Administration The Dial/Routing Plan window appears. 5 In the Machine Name list, select the machine name of the local IP Trunk server. 6 Select Originating and click Add (under Routing Info). The Add Originating Entry dialog box appears.
F IP Trunk Administration IP Trunk Installation and Administration 7 In the Add Originating Entry dialog box, you enter information that routes the call data between originating and terminating locations. You need to enter information that allows the IP Trunk to route calls based on dialed digits or on the line (port) that a call arrives on. Note: It is not possible to mix dialing strategies in the IP Trunk software.
F IP Trunk Administration IP Trunk Installation and Administration 12 In the Destination Address (IP) field, type the Internet Protocol (IP) address of the destination IP Trunk on the remote switch. 13 In the Port field, type the port number to be used for this connection. The port number used in all IP Trunk servers is “5000”. 14 Click OK. The Add Originating Entry dialog box closes and the Dial/Routing Plan dialog box appears showing the information you entered.
F IP Trunk Administration IP Trunk Installation and Administration 3 In the Machine Name box, select the local machine name for the local IP Trunk server. 4 Select Terminating 5 Click Add (under Routing Info). The Add Terminating Entry dialog box appears. 6 In the Add Terminating Entry dialog box, you enter information that routes the incoming call to a terminating location.
F IP Trunk Administration IP Trunk Installation and Administration For example, the code numbers 01, 02, ..., were prepended to the dialed string in the originating switch. For each line number, the code number is entered in the Search Digits field (as in the display above) as a unique digit string associated with the line number. Since the code number is not intended to be routed to the DEFINITY to complete the call, none is entered in the Replace Digits filed to prevent digit replacement.
F IP Trunk Administration Starting IP Trunk service IP Trunk Installation and Administration Use this procedure only if you have manually stopped your IP Trunk service. To start IP Trunk service: 1 Log onto the NT server. 2 Open the Windows NT Control Panel. 3 Double-click Services. The Services dialog box appears. 4 In the Service column, select IP Trunk Service. 5 Click Start. Started appears in the Status column. 6 Click Close. 7 Release the IP trunk group on DEFINITY ECS.
F Procedures for Extension Dialing Between Sites IP Trunk Installation and Administration Procedures for Extension Dialing Between Sites These procedures outline two different extension dialing configurations that may be used from a particular site to other IP Trunk sites. The first configuration is non-DCS, where one trunk group exists in DEFINITY and is routed through the IP Trunk server to many different IP Trunk locations.
F Procedures for Extension Dialing Between Sites IP Trunk Installation and Administration In Switch A above, the IP Trunk server’s originating entries will be as follows, in order for calls through that IP Trunk server to be routed to Switch B and Switch C appropriately. Line Search String Replace String IP Address Any 44 44 198.152.169.238 (Switch B) Any 49 49 198.152.169.238 (Switch B) Any 43 43 198.152.169.236 (Switch C) Any 34 34 198.152.169.
F DCS over IP Trunk IP Trunk Installation and Administration DCS over IP Trunk IP Trunk supports most of the DCS features. DCS signaling with IP Trunk can be either X.25 or TCP/IP. For X.25 DCS signaling, the signaling data path is over a tie trunk connection between the switches. For TCP/IP DCS signaling, the signaling data is handled by the C-LAN circuit pack and can be either point-to-point (ppp) across a tie trunk facility or over the IP network.
F DCS over IP Trunk IP Trunk Installation and Administration TCP/IP signaling For TCP/IP signaling, you administer the connection on the Data Module screen and the Processor Channel Assignment screen. The data module type is ppp for a point-to-point signaling connection or ethernet for signaling over an IP network. In addition, TCP/IP signaling requires administration of the Node Names screen and, in some cases, the IP Routing screen.
F DCS over IP Trunk IP Trunk Installation and Administration On Switch A Line Search String Replace String IP Address 1 None 01 198.152.169.236 (Switch C) 2 None 02 198.152.169.236 (Switch C) 3 None 03 198.152.169.236 (Switch C) 4 None 04 198.152.169.238 (Switch B) 5 None 05 198.152.169.238 (Switch B) 6 None 06 198.152.169.238 (Switch B) On Switch B Line Search String Replace String IP Address 4 None 04 198.152.169.240 (Switch A) 5 None 05 198.152.169.
F DCS over IP Trunk IP Trunk Installation and Administration On Switch A Line Search String Replace String 1 01 None (From Switch C) 2 02 None (From Switch C) 3 03 None (From Switch C) 4 04 None (From Switch B) 5 05 None (From Switch B) 6 06 None (From Switch B) On Switch B Line Search String Replace String 7 07 None (From Switch C) 8 08 None (From Switch C) 9 09 None (From Switch C) 4 04 None (From Switch A) 5 05 None (From Switch A) 6 06 None (From
F DCS over IP Trunk IP Trunk Installation and Administration Rerouting calls when IP transmission quality is poor When transmission quality over the IP network is unacceptable, use AAR or ARS with Configuration Manager to reroute calls over private and public telephone networks. This is called PSTN Fallback.
F DCS over IP Trunk More information IP Trunk Installation and Administration The Packet Loss Threshold and Round Trip Delay Threshold fields work like this: • If the value in either High field is exceeded, access to the IP trunk group is blocked. • Access to the IP trunk group is only allowed again when the average for both measurements drops below the values in the Low field.
F DCS over IP Trunk IP Trunk Installation and Administration 4 In the dialog box, enter the NT networking computer names for the systems on which alerts should be received. For example: ICB189-85, ICB189-14. Note: Do not specify the IP address of the system. You must specify the NT networking computer name. If another person is responsible for LAN administration, consider making this a joint activity. To set up the receiving machines 1 On each system which received alerts, start the Messenger service.
F DCS over IP Trunk IP Trunk Installation and Administration Alert types IP trunk generates alerts when: Testing Alerts • The IP trunk service stops. • The DSP card does not respond. • The Dial Plan has changed. • The access rules have changed. • The initialization file (its.ini) is missing. • The dial/routing plan file (gk.ini) is missing. You can test alerts by generating a “dial plan has changed” alert. To generate a “dial plan has changed” alert: 1 Open Configuration Manager.
F DCS over IP Trunk IP Trunk Installation and Administration Troubleshooting IP trunk If IP calls are not going through, try these basic procedures before contacting an authorized Lucent Technologies Service Center for assistance. Check the IP trunk service Check that the IP trunk service is running. 1 Go to the Windows NT™ Control Panel 2 Double-click on the Services icon to launch the Services Control Manager.
F DCS over IP Trunk Network Test Function DOS Test Command (type at the DOS prompt for your computer) Local network connectivity Ping IP address of default gateway (available from your LAN administrator) For example, ping 192.20.239.
F DCS over IP Trunk IP Trunk Installation and Administration Configuring Microsoft NetMeeting™ on a PC After NetMeeting 2.0 is installed, the first time you start it the Configuration Wizard prompts you to provide general information. After you provide the general information, you must change some audio settings. Procedures for these tasks follow. Providing general information for the Configuration Wizard The first time you start NetMeeting, follow these steps.
F DCS over IP Trunk Changing Audio Settings IP Trunk Installation and Administration To change the audio settings so that NetMeeting operates properly with the IP trunk application, follow these steps. 1 From the Tools menu choose Options and then select the Audio tab. The Audio tab settings appear as shown in Figure 5. Figure 11. Audio Tab Settings in Options Dialog Box 2 Click the check box for Enable full duplex audio so I can speak while receiving audio.
F DCS over IP Trunk Making Calls to the IP trunk application from NetMeeting IP Trunk Installation and Administration Before you place a call, make sure the following settings are correct. • If You Have a LAN Connection: • Make sure the TCP/IP settings are correct on the client machine. To verify this, open an NT command window and ping the IP trunk. • If You Have a Modem Connection: Make sure you have the correct dial-up networking settings for the remote RAS server that you are connecting to.
F DCS over IP Trunk IP Trunk Installation and Administration 2 In the NetMeeting main window, click the Call icon located in the upper left-hand corner of the tool bar. The New Call dialog box appears. 3 In the Address box, type the phone number you want to call. Type the number exactly as you dial it from a regular phone. Do not use spaces or hyphens between numbers.
IP Trunk Worksheets Administration for Network Connectivity 555-233-504 — Issue 1 — April 2000 IP Trunk Worksheets Worksheet 1: Two Site Solution: Both DEFINITY T1 SITE 1 Field Code SITE 2 Field Name Field Value Field Code Field Name CID: 77730 1A International Access Code 2A International Access Code 1B Country Code 2B Country Code 1C Long Distance Access Code 2C Long Distance Access Code 1D Area Code 2D Area Code 1E Exchange 2E Exchange 1F ARS Feature Access Code 2F ARS Feat
450 Worksheet 2: Two Site Solution: DEFINITY T1 Administration (No Off-Premise Dialing at Remote Site Only) SITE 1 SITE 2 PBX Admin Add ARS analysis entry with: If Sites 1 and 2 are in: Fill in with your actual values Dialed String PBX Admin Same country, different area code Different Country Same area code Add ARS analysis entry with: If Sites 1 and 2 are in: Fill in with your actual values Same area code 1A2B2D2E 1C2D2E 2E 2A1B1D1E 2C1D1E 1E Total Mn * * * Total Mn * * * Total
SITE 1 SITE 2 MMCX Admin Create entries: Fill in with your actual values If Sites 1 and 2 are in: Different Country Same country, different area code MMCX Admin Same area code Originating Search string Create entries: Fill in with your actual values If Sites 1 and 2 are in: Different Country Same country, different area code Same area code Originating 1A2B2D2E 1C2D2E 2E Search string 2A1B1D1E 2C1D1E 1E Replace string 2E 2E 2E Replace string 1E 1E 1E IP Address 2G 2G 2G IP Add
452 Worksheet 3: Two Site Solution: DEFINITY T1 Administration (Off-Premise Dialing at Remote Site [same area code, any exchange]) SITE 1 SITE 2 PBX Admin Add ARS analysis entry with: If Sites 1 and 2 are in: Fill in with your actual values Dialed String Same country, different area code Different Country 1A2B2D 1C2D Total Mn * * Total Mx * * 1H 1H Rte Pat PBX Admin Same area code NA** CID: 77730 *Set this value to the total length of the number the user will dial, not including the ARS
SITE 1 SITE 2 PBX Admin Add ARS analysis entry with: If Sites 1 and 2 are in: Fill in with your actual values Dialed String PBX Admin Same country, different area code Different Country Same area code Add ARS analysis entry with: If Sites 1 and 2 are in: Fill in with your actual values Same country, different area code Different Country Same area code 1A2B2DX 1C2DX X Dialed String 2A1B1DX 2C1DX X Total Mn * * * Total Mn * * * Total Mx * * * Total Mx * * * 1H 1H 1H 2
454 Worksheet 5: Two Site Solution: DEFINITY T1 Administration (Off-Premise Dialing at Remote Site [same country, any area code]) SITE 1 SITE 2 PBX Admin Add ARS analysis entry with: If Sites 1 and 2 are in: Fill in with your actual values Dialed String PBX Admin Same country, different area code Different Country Same area code Add ARS analysis entry with: If Sites 1 and 2 are in: Fill in with your actual values Same area code 1A2B 1C 1C 2A1B 2C 2C Total Mn * * * Total Mn * * *
SITE 1 SITE 2 PBX Admin Add ARS analysis entry with: If Sites 1 and 2 are in: Fill in with your actual values Dialed String PBX Admin Same country, different area code Different Country Same area code Add ARS analysis entry with: If Sites 1 and 2 are in: Fill in with your actual values Same area code 1A2BX 1CX 1CX 2A1BX 2CX 2CX Total Mn * * * Total Mn * * * Total Mx * * * Total Mx * * * 1H 1H 1H 2H 2H 2H Rte Pat CID: 77730 *Set this value to the total length of th
456 Worksheet 7: Two Site Solution: DEFINITY T1 Administration (Off-Premise Dialing at Remote Site [any different country]) SITE 1 SITE 2 PBX Admin Add ARS analysis entry with: If Sites 1 and 2 are in: Fill in with your actual values Dialed String PBX Admin Same country, different area code Different Country Same area code 1A 1A 1A Total Mn * * * Total Mx * * * 1H 1H 1H Rte Pat *Set this value to the total length of the number the user will dial, not including the ARS feature acces
SITE 1 SITE 2 PBX Admin Add ARS analysis entry with: If Sites 1 and 2 are in: Fill in with your actual values Dialed String Total Mn Total Mx Rte Pat PBX Admin Same country, different area code Different Country Same area code Same country, different area code Different Country Same area code 1AX 1AX 2AX 2AX 2AX * * * Total Mn * * * Total Mx * * * 2H 2H 2H * * * 1H 1H 1H CID: 77730 MMCX Admin Fill in with your actual values Fill in with your actual values 1AX *Set t
IP Trunk Worksheets 458 CID: 77730 Administration for Network Connectivity 555-233-504 — Issue 1 — April 2000
G References This Appendix lists the complete set of current DEFINITY ECS user documentation and selected related documents. This appendix contains a list of user documents for the DEFINITY Enterprise Communications Server (ECS) Release 8.2. Most of these documents are backward compatible with DEFINITY ECS Release 7 systems. To order these or other DEFINITY documents, contact the Lucent Technologies Publications Center at the address and phone number on the back of the title page of this document.
G References DEFINITY System’s Little Instruction Book for basic administration, 555-233-756, Issue 1 Provides step-by-step procedures for performing basic switch administration tasks. Includes managing phones, managing features, routing outgoing calls, and enhancing system security.
G Installation and maintenance References DEFINITY ECS Release 8.2 — Installation and Test for Single-Carrier Cabinets, 555-233-120, Issue 1 Provides procedures and information for hardware installation and initial testing of single-carrier cabinets. This document is availabe in languages other than English and can be ordered from the BCS Publications Catalog web site. DEFINITY ECS Release 8.
G References DEFINITY ECS Release 8.2 — Maintenance for R8.2r, 555-233-117, Issue 1 Provides detailed descriptions of the procedures for monitoring, testing, troubleshooting, and maintaining the R8.2r ECS. Included are maintenance architecture, craft commands, step-by-step trouble-clearing procedures, the procedures for using all tests, and explanations of the system’s error codes. DEFINITY ECS Release 8.2 — Maintenance for R8.
G CentreVu CMS References The following documents provide information about administration and use of the CentreVu Call Management System (CMS).
G Console operations References The primary audience for these documents consists of attendant console users. DEFINITY ECS Release 7 — Console Operations, 555-230-700, Issue 4 Provides operating instructions for the attendant console. Included are descriptions of the console control keys and functions, call-handling procedures, basic system troubleshooting information, and routine maintenance procedures.
Glossary A AAR See Automatic Alternate Routing (AAR). Abbreviated Dialing (AD) A feature that allows callers to place calls by dialing just one or two digits. AD See Abbreviated Dialing (AD) ADU See Asynchronous data unit (ADU). adjunct A processor that does one or more tasks for another processor and that is optional in the configuration of the other processor. Intuity AUDIX and CentreVu CMS are considered adjuncts to the DEFINITY ECS.
asynchronous data transmission Glossary asynchronous data transmission A method of transmitting data in which each character is preceded by a start bit and followed by a stop bit, thus permitting data characters to be transmitted at irregular intervals. This type transmission is advantageous when transmission is not regular (characters typed at a keyboard). Also called asynchronous transmission.
B8ZS B Glossary B8ZS See Bipolar 8 Zero Substitution (B8ZS). Basic Rate Interface (BRI) A standard ISDN frame format that specifies the protocol used between two or more communications systems. As used in North America, BRI provides 23 64-kbps B-channels (voice or data) and one 64-kbps D-channel (signaling). The D-channel is the 24th channel of the interface and contains multiplexed signaling information for the other 23 channels.
bit (binary digit) Glossary bit (binary digit) One unit of information in binary notation, having two possible values: 0 or 1. bit rate The speed at which bits are transmitted, usually expressed in bits per second. Also called data rate. bps Bits per second. BOS Bit-oriented signaling. BRI See Basic Rate Interface (BRI) bridge A device that connects two or more packet-switched networks and directs packets sent from one to the other. See router.
Call Management System (CMS) Glossary Call Management System (CMS) An application, running on an adjunct processor, that collects information from an ACD unit. CMS enables customers to monitor and manage telemarketing centers by generating reports on the status of agents, splits, trunks, trunk groups, vectors, and VDNs, and enables customers to partially administer the ACD feature for a communications system. call redirection See restricted facilities.
channel Glossary channel A communication path linking two points for transmitting voice and data. Also: 1. A circuit-switched call. 2. In wideband, all of the time slots (contiguous or noncontiguous) necessary to support a call. Example: an H0-channel uses six 64-kbps time slots. 3. A DS0 on a T1 or E1 facility not specifically associated with a logical circuit-switched call; analogous to a single trunk. circuit 1. An arrangement of electrical elements through which electric current flows. 2.
COR Glossary COR See Class of Restriction (COR). COS See Class of Service (COS). CP Circuit pack. CSN See circuit-switched network. CSU Channel service unit. cyclic redundancy checking (CRC) A method for detecting read, transmit, and write errors in data. At the transmission end, the system treats a block of data as a single binary number, divides it by some specified binary number, and appends the remainder (called the CRC character) to the data.
data path Glossary data path The end-to-end connection used for a data communications link. A data path is the combination of all elements of an interprocessor communication in a DCS. data port A point of access to a computer that uses trunks or lines for transmitting or receiving data. data service unit (DSU) A device that transmits digital data on transmission facilities. data terminal equipment (DTE) Equipment consisting of the endpoints in a connection over a data circuit.
DID Glossary DID Direct Inward Dialing. digital communications protocol (DCP) A proprietary protocol used to transmit both digitized voice and digitized data over the same communications link. A DCP link is made up of two 64-kbps information (I-) channels and one 8-kbps signaling (S-) channel. The DCP protocol supports 2 information-bearing channels, and thus two telephones/data modules. digital signal level 0 (DS0) A single 64-kbps voice channel.
DSU Glossary DSU Data service unit. DTDM Digital-terminal data module. DTE Data-terminal equipment. E E-1 A digital transmission link with a capacity of 2.048 Mbps (2,048,000 bits per second). The European equivalent of the T-1. It can support 30 multiplexed 64-Kbps voice and data channels plus separate 64-Kbps channels for signalling and framing (synchronization). Also spelled E1. EIA See Electronics Industries Association (EIA). EIA-232 A physical interface specified by the EIA.
facility F Glossary facility A telecommunications transmission pathway and associated equipment. facility-associated signaling (FAS) Signaling for which a D-channel carries signaling only for those channels on the same physical interface. FAS Facility-associated signaling framing The data-formatting conventions that allow a receiver to synchronize with the transmitting end of a circuit.
High Density Bipolar 3-Bit Substitution (HDB3) Glossary High Density Bipolar 3-Bit Substitution (HDB3) HDB3 line coding is similar to Bipolar 8 Zero Substitution (B8ZS) in some ways. It replaces every 4 consecutive zero in a stream of AMI-encoded data (see line coding) with either of two sequences.
interserver routing table Glossary interserver routing table A database that keeps track of the interserver routing tables on a multiserver MMCX network. When a server sets up a Point-to-Point Protocol connection with a remote server, the local server looks up the dialed-digit sequences in the interserver routing table. (Calls that involve only one MMCX server are routed using the dial-plan table.
LAN L Glossary LAN See local area network. LAN emulation (LANE) A technique that lets ATM networks communicate with Ethernet LAN cards. ATM service is not widely available at the desktop and ATM interface cards are expensive, so ATM networks usually emulate LANs when communicating with user terminals. Typically, a LAN-emulation configuration server (LECS) keeps track of the relationships between ATM-network addresses and IP addresses on the LAN.
link-access procedure on the D-channel (LAPD) Glossary link-access procedure on the D-channel (LAPD) A link-layer protocol on the ISDN-BRI and ISDN-PRI data-link layer (level 2). LAPD provides data transfer between two devices, and error and flow control on multiple logical links. LAPD is used for signaling and low-speed packet data (X.25 and mode 3) on the signaling (D-) channel and for mode-3 data communications on a bearer (B-) channel.
MDR Glossary MDR Message detail record. MIB See Management Information Base (MIB). MMCH Multimedia call handling. MSA Message Server Adjunct. multicasting A transmission method that promotes efficient bandwidth utilization on a multimedia data network when several parties are transmitting and receiving simultaneously. Normally, each party sends a separate video stream to each of the other parties and receives a separate video stream from each in return (this is called unicasting).
NEMA Glossary NEMA National Electrical Manufacturer’s Association. NETCON Network-control circuit pack. Network A collection of computer-like devices ("nodes") that are connected by, and can communicate across, a common transmission medium. Network Adapter The interface between a node and the network; has a unique physical address. Network Interface Card (NIC) A circuit board that can be fitted to a personal computer (PC) to allow the PC to communicate with other machines on a network.
Open System Interconnect (OSI) Model O Glossary Open System Interconnect (OSI) Model An International Standards Organization (ISO) interoperability specification. OSI defines standard services that compliant communications networks and equipment must provide, rather than specific implementations. It divides network operations into 7 steps, called layers, and arranges them hierarchically, in a protocol stack.
PBX Glossary PBX Private Branch Exchange: a customer-owned telephone switch that connects a company’s internal telephone network with the local telephone service provider’s central office. Lucent’s DEFINITY PBX is a good example. PDM See processor data module (PDM). PGATE Packet gateway. Point-to-Point Protocol A TCP/IP implementation tailored for use over telephone lines. It supports router-to-router and host-to-network connections over both synchronous and asynchronous circuits.
protocol Glossary protocol A set of conventions or rules governing the format and timing of message exchanges to control data movement and correction of errors. PSDN Packet-switch public data network. PSTN See Public Switched Telephone Network (PSTN). PSN Packet-switched network. Public Switched Telephone Network (PSTN) The worldwide voice telephone system. Q QPPCN Quality Protection Plan Change Notice. QSIG A set of open standards for Enterprise Networking.
routing plan Glossary routing plan Routing plans direct outgoing voice-interworking and interserver calls to the first available PRI trunk group in a list. This arrangement lets you allow for trunk groups that are busy, out of service, or out of bandwidth. Each routing plan is identified by a routing-plan number in the range 1-32. RPN Routing-plan number. RTP Real-time protocol. S Socket An address formed by concatenating the IP address and the port number. server 1.
Simple Network Management Protocol (SNMP) Glossary Simple Network Management Protocol (SNMP) An International Standards Organization (ISO) protocol that sets standards for communications between network components and network management stations. SNMP handles network resources using the information contained in a management information base (MIB), a virtual database resident on the various parts of the network.
T-carrier Glossary T-carrier A hierarchy of digital voice- and data-transmission systems used in North America and based on multiples of the capacity of the T-1 line. tandem switch A switch within an electronic tandem network (ETN) that provides the logic to determine the best route for a network call, possibly modifies the digits outpulsed, and allows or denies certain calls to certain users. tandem-through The switched connection of an incoming trunk to an outgoing trunk without human intervention.
time slot Glossary time slot 64 kbps of digital information structured as eight bits every 125 microseconds. In the switch, a time slot refers to either a DS0 on a T1 or E1 facility or a 64-kbps unit on the TDM bus or fiber connection between port networks. trunk A communication line linking two switches (public-network, PBX, or MMCX-server). trunk group A collection of trunks that all terminate at the same public switch, PBX, or MMCX server. U UDP 1.
virtual circuit (virtual connection) Glossary virtual circuit (virtual connection) The pre-arranged route through the ATM network that all cells in an ATM transmission follow. virtual circuit number The route identifier contained in an ATM cell header. A VCI and a VPI together constitute the virtual circuit number. virtual path identifier See VPI. VPI The ATM virtual path identifier. ATM is a connection-oriented service that sets up a virtual circuit between the transmitter and the receiver.
ZCS Z Glossary ZCS See Zero Code Suppression (ZCS). Zero Code Suppression (ZCS) ZCS line coding substitutes a 1 for the second least-significant bit of every all-zero byte in AMI-encoded data (see line coding). ZCS encoding has no effect on voice communications, but it corrupts digital data (see restricted facilities). In MMCX communications, ZCS corrupts the ISDN D-channel.
Index A AAR and ARS features interactions Centralized Attendant Service (CAS) 341 QSIG Call Forwarding (Diversion) 379 QSIG Message Waiting Indication 384 Uniform Dial Plan (UDP) 354 AAR and ARS Partitioning feature interactions QSIG Message Waiting Indication 383 AAR digit analysis example 216, 225, 231 AAR/ARS administration, IP Trunk 424 Abbreviated Dialing (AD) feature interactions Centralized Attendant Service (CAS) 341 Extended Trunk Access (ETA) 345 abstract syntax notation 1 (ASN-1) 369 additional
Index B B Call Forwarding feature, interactions, (continued) QSIG Call Forwarding (Diversion) 379 QSIG Call Transfer 380 QSIG Supplementary Service - Call Completion B8ZS.
D Index Centralized Attendant Service (CAS) feature, interactions, (continued) Call Forwarding 341 DCS Alphanumeric Display for Terminals 325 Distributed Communications System (DCS) 342 DTGS buttons 342 DXS buttons 342 Emergency Access to Attendant 342 Hunt Groups 342 Inter-PBX Attendant Service (IAS) 348 Leave Word Calling (LWC) 342 Night Service 342 nonattendant consoles 342 queues 339 release link trunks (RLT) 339 remote hold 339 changing audio settings on Microsoft NetMeeting 446 channel service unit
Index D DCS Attendant Direct Trunk Group Selection feature 313, 323 DCS Attendant Display feature 313, 323 interactions DCS Attendant Control of Trunk Group Access 325 Inter-PBX Attendant Service (IAS) 347 DCS Automatic Callback (ACB) feature 314, 323 interactions Attendant Control of Trunk Group Access 326 DCS Attendant Control of Trunk Group Access 326 DCS Automatic Circuit Assurance (ACA) feature 314 DCS Busy Verification of Terminals and Trunks feature 314 interactions routing patterns 326 Trunk Iden
E Index Distributed Communications System (DCS) feature, (continued) AUDIX configuration examples 329 configuring DCS networks 312 DCS features 313 feature considerations 323 forms 293 interactions Centralized Attendant Service (CAS) 342 Extension Number Portability (ENP) 347 QSIG Call Forwarding (Diversion) 379 QSIG Call Transfer 380 QSIG Name and Number Identification 380 Uniform Dial Plan (UDP) 354 network configurations 312 documents how to order xvi dotted decimal notation 13 DS1 circuit pack example
Index I hop channel assignment screen 300 hop channels per system 10 host IP route 23, 251 Hotline Service feature interactions QSIG Supplementary Service - Call Completion IP routing example 229, 239 gateway 252 metric 253 screen 251 IP Softphone 11, 32 IP Solutions 31 IP Solutions, configurations 31 IP Solutions, troubleshooting 50 IP Trunk 32 AAR/ARS administration 424 administration 418 alert types 442 Configuration Manager 426 confirming the number of available ports 426 DEFINITY administration proc
L Index ISDN Feature Plus feature, interactions, (continued) Feature Plus Forwarding (Diversion) Automatic Callback 358 Call Coverage 358 Call Park 358 Calling Line Identification Presentation (CLIP) 358 Connection Line Identification Presentation (COLP) 358 Feature Plus Centralized AUDIX 358 Feature Plus Message Waiting Indication Audio Information Exchange (AUDIX) 359 Off-Premise Station 359 QSIG 359 ISDN Private Networking Specification (IPNS) forum M maintaining performance of the IP trunk server 444
Index O node names example 218, 238 node names screen 245 node names, assign 38 node number routing screen 302 nonattendant consoles 342 noncall associated–temporary signaling connections (NCA–TSC) 321, 369 NT administration, IP Trunk 426 Private Networking features, (continued) Extension Number Portability (ENP) 346 Inter-PBX Attendant Service (IAS) 347 Italian DCS Protocol DCS 319 Private Network Access 348 QSIG Additional Network Feature Path Replacement (ANF-PR) 367 QSIG Call Forwarding (Diversion) 3
R Index QSIG Call Transfer feature 362 interactions Call Forwarding 380 Distributed Communications System (DCS) 380 QSIG Additional Network Feature Path Replacement (ANF–PR) 380 QSIG Name and Number Identification 380 QSIG Centralized AUDIX 364 what you get with QSIG Centralized AUDIX 365 QSIG feature call associated–temporary signaling connections (CA–TSC) 369 interactions ISDN Feature Plus 359 QSIG Features QSIG NCA-TSC 370 QSIG features 360, 366 additional network features (ANF) 369 Busy name 361 Call
Index S supplementary service B (SSB) routes 367 supported switches and adjuncts 53, 58 switch components 4 synchronization plan example 210, 229, 234 synchronization plan screen 304 restoring IP trunk 425 routing pattern example 225, 232 routing patterns example 217 S T satellite switches 344 Screen xv screen IP routing 251 screens analog-dm data module 297 circuit packs 277 communications interface links 293 communications-interface processor channel 273 data module 256 extension number portability n
U Index trunk access codes (TAC) QSIG Additional Network Feature Path Replacement (ANF–PR) 381 QSIG Additional Network Feature–Transit Counter (ANF–TC) 381 trunk group example 211, 223, 230, 235 for IP Trunk 422 Trunk Group Select buttons 313 trunk group, create 45 Trunk Identification by Attendant feature interactions DCS Busy Verification of Terminals and Trunks uniform dialing plan example 216, 224, 231 uniform dialing plan screen 307 utility programs ipconfig 443 ping 444 traceroute 444 V vectory di
Index 502 Z CID: 77730 Administration for Network Connectivity 555-233-504 — Issue 1 — April 2000
We’d like your opinion. Lucent Technologies welcomes your feedback on this document. Your comments can be of great value in helping us improve our documentation. DEFINITY® ECS Release 8.2 Administration for Network Connectivity 555-233-504, Issue 1, April 2000, Comcode 108678749 1. Please rate the effectiveness of this document in the following areas: Excellent Good Fair Poor Ease of Finding Information Clarity Completeness Accuracy Organization Appearance Examples Illustrations Overall Satisfaction 2.
