User's Manual
Table Of Contents
- ===============================
- MAIN MENU
- MASTER INDEX
- GLOSSARY
- ===============================
- DEFINITY® ECS Release 8.2 Administration for Network Connectivity
- Contents
- Preface
- 1 Networking Overview
- 2 H.323 Trunks
- Overview
- H.323 Trunk Administration
- Enabling Administration
- H.323 Trunk Administration — Task Summary
- H.323 Trunk Administration — Task Detail
- Task 1 — Assign Node Names
- Task 2 — Define IP Interfaces
- Task 3 — Assign Link via ethernet Data Module to the LAN
- Task 4 — Create a signaling group
- Task 5 — Create a trunk group
- Task 6 — Modify signaling group
- Task 7 — Specify codecs
- Troubleshooting IP Solutions
- 3 C-LAN Administration
- Overview
- Configuration 1: R8r <—ppp—> R8si
- Task Summary
- Prerequisite Administration
- Switch 1 Task — Assign Node Names
- Switch 1 Task — Assign Link via ppp Data Module to Switch 2
- Switch 1 Task — Assign Processor Channels
- Switch 2 Task — Assign Node Names
- Switch 2 Task — Assign Link via ppp Data Module to Switch 1
- Switch 2 Task — Assign Processor Channels
- Enable links and processor channels
- Configuration 2: R7r (+CMS) <—ethernet—> R7csi
- Task Summary
- Switch 1 Task — Assign Node Names
- Switch 1 Task — Assign IP Interfaces
- Switch 1 Task — Assign Link via ethernet Data Module to the LAN
- Switch 1 Task — Assign Processor Channels
- Switch 2 Task — Enable Bus Bridge Connectivity
- Switch 2 Task — Assign Node Names
- Switch 2 Task — Define IP Interfaces
- Switch 2 Task— Assign Link via ethernet Data Module to the LAN
- Switch 2 Task — Assign IP Route (to Switch 1)
- Switch 2 Task— Assign Processor Channels
- Intuity System Administration
- Administer Subscribers
- Worksheet A: Names and IP Addresses for Lucent Intuity System
- Worksheet B: LAN Data for the Lucent Intuity System
- Enable links and processor channels
- Configuration 3:R8si<—x.25 —> R8r Gateway <—ethernet—> R8si
- Task Summary
- Prerequisite Administration
- Switch 1 Task — Assign Node Names
- Switch 1 Task — Assign pdm Data Module
- Switch 1 Task — Assign Link via x.25 Data Module to Switch 2
- Switch 1 Task — Assign IP Interfaces
- Switch 1 Task — Assign Link via ethernet Data Module to the LAN
- Switch 1 Task — Assign Processor Channels
- Switch 2 Task — Assign Link via procr-intf Data Module to Switch 1
- Switch 2 Task — Assign Processor Channels
- Switch 3 Task — Assign Node Names
- Switch 1 Task — Assign IP Interfaces
- Switch 3 Task — Assign Link via ethernet Data Module to the LAN
- Switch 3 Task — Assign Processor Channels
- Enable links and processor channels
- Configuration 4: R8csi <—ISDN—> R8si Gateway <—ppp—> R8csi
- Task Summary
- Prerequisite Administration
- Switch 1 Task — Assign Node Names
- Switch 1 Task — Assign Link via ppp Data Module to Switch 3
- Switch 1 Task — Assign Processor Channels
- Switch 1 Task — Assign Signaling Group and administered NCA TSC
- Switch 1 Task — Assign ISDN-TSC Gateway
- Switch 2 Task — Assign Signaling Group and administered NCA TSC
- Switch 3 Task — Enable Bus Bridge Connectivity
- Switch 3 Task — Assign Node Names
- Switch 3 Task — Assign Link via ppp Data Module to Switch 1
- Switch 3 Task — Assign Processor Channels
- Enable links and processor channels
- Configuration 5A: R8csi <—ppp—> R8r (one C-LAN) <—ethernet—> R8si
- Task Summary
- Prerequisite Administration
- Switch 1 Task — Assign Node Names
- Switch 1 Task — Assign Link via ppp Data Module to Switch 2
- Switch 1 Task — Assign IP Interfaces
- Switch 1 Task — Assign Link via ethernet Data Module to Ethernet
- Switch 1 Task — Assign Processor Channels
- Switch 2 Task — Enable Bus Bridge Connectivity
- Switch 2 Task — Assign Node Names
- Switch 2 Task — Assign Link via ppp Data Module to Switch 1
- Switch 2 Task — Assign Processor Channels
- Switch 2 Task — Assign IP Route to node-3
- Switch 3 Task — Assign Node Names
- Switch 3 Task — Assign IP Interfaces
- Switch 3 Task — Assign Link via ethernet Data Module to the LAN
- Switch 3 Task — Assign Processor Channels
- Enable links and processor channels
- Configuration 5B:R8csi <—ppp—> R8r (2 C-LANs) <—ethernet—> R8si
- Task Summary
- Prerequisite Administration
- Switch 1 Task — Assign Node Names
- Switch 1 Task — Assign Link via ppp Data Module to Switch 2
- Switch 1 Task — Assign IP Interfaces
- Switch 1 Task — Assign Link via ethernet Data Module to the LAN
- Switch 1 Task — Assign Link via ppp Data Module to C-LAN(a)
- Switch 1 Task — Assign Link via ppp Data Module to C-LAN(b)
- Switch 1 Task — Assign Processor Channels
- Switch 1 Task — Assign IP Route: C-LAN(a) to node-3
- Switch 1 Task — Assign IP Route: C-LAN(b) to node-2
- Switch 2 Task — Enable Bus Bridge Connectivity
- Switch 2 Task — Assign Node Names
- Switch 2 Task — Assign Link via ppp Data Module to Switch 1
- Switch 2 Task — Assign Processor Channels
- Switch 2 Task — Assign IP Route to node-3
- Switch 3 Task — Assign Node Names
- Switch 3 Task — Assign IP Interfaces
- Switch 3 Task — Assign Link via ethernet Data Module to the LAN
- Switch 3 Task — Assign Processor Channels
- Enable links and processor channels
- 4 Networking Example
- A Screens Reference
- Networking Screens
- Other Network-Related DEFINITY Screens
- Networking Screens
- Node Names
- page 1
- Pages 2 – 6
- IP Interfaces
- IP Routing
- IP Media Parameters
- Data Module Screens
- Common Data Module Fields
- Data Module — Type ethernet
- Data Module — Type ppp
- Data Module — Type procr-intf (used for BX.25 connections with the si model)
- Data Module - type X.25 (used for BX.25 connections with the r model)
- Data Module - type pdm (used for BX.25 connections with the r model)
- Communication-Interface Processor Channel
- Circuit Packs
- Signaling Group
- ISDN TSC Gateway Channel Assignments
- Other Networking-Related DEFINITY Screens
- Communication Interface Links
- Data Module - type netcon
- Data Module - type analog-dm
- Extended Trunk Access Call Screening
- Extension Number Portability Numbering Plan
- Hop Channel Assignments Screen
- Implementation notes
- Node Number Routing
- Message Waiting Indication Subscriber Number Prefixes
- Synchronization Plan
- Pages 1–X of the screen
- Uniform Dial Plan
- B Private Networking
- Contents of this Appendix
- Distributed Communications System
- Description of DCS
- DCS Features
- Italian DCS Protocol
- ISDN/X.25 gateway
- DCS Over ISDN-PRI D-channel
- DCS feature considerations
- DCS Interactions
- Example DCS configurations
- Centralized Attendant Service
- Extended Trunk Access
- Extension Number Portability
- Inter-PBX Attendant Service
- Private Network Access
- Uniform Dial Plan
- ISDN Feature Plus
- QSIG
- Centralized Voice Mail Via Mode Code
- Japan TTC Q931-a Private Networking Protocols
- C Security Issues
- D Capacities and Performance
- E C-LAN Installation
- F IP Trunk Installation and Administration
- IP Trunk Installation
- IP Trunk Administration
- Procedures for Extension Dialing Between Sites
- DCS over IP Trunk
- DCS or Dedicated Trunks to Specific Locations Configurations
- Rerouting calls when IP transmission quality is poor
- Placing a test telephone call
- Setting up alerts on IP trunks
- Alert types
- Viewing error messages
- Troubleshooting IP trunk
- Maintaining the performance of the IP trunk server
- Configuring Microsoft NetMeeting™ on a PC
- IP Trunk Worksheets
- G References
- Glossary
- Index
Configuration 5A: R8csi <—ppp—> R8r (one C-LAN)
<—ethernet—> R8si
169
Administration for Network Connectivity
555-233-504 — Issue 1 — April 2000 CID: 77730
3 C-LAN Administration
> Submit the screen
End
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.
It is allowed, and sometimes convenient, to use the same
number for the Local and Remote Session numbers. It is
allowed, but not recommended, to use the same Session
numbers for two or more connections.
Session -
Remote
Mach ID Destination switch ID identified on the dial plan of the
destination switch.
For Processor Channel 32: (connection to Switch 2 through Switch 1)
Enable Set to y.
Appl. Set to dcs for DCS signaling.
Mode Node-3 is the “server.” Set node-2 to “client” (c).
Interface Link This must match the link number assigned on the node-3 data
module screen.
Interface Chan This must match the Destination Port number on the Switch-1
Processor Channels screen.
Destination
Node
Name of the far-end node for this channel. This must be a name
entered on the Node Names screen.
Destination
Port
or TCP/IP, interface channel numbers are in the range 5000 –
64500.
The recommended values are: 5001 for CMS, 5002 for Intuity
AUDIX, and 5003 for DCS connections that are not gateways.
These three values should be reused for multiple instances of
these applications. The combination of Link, Interface Channel,
and Mach ID must be unique.
This number must match the Destination Port number on the
Switch-2 Processor Channel screen.
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.
Field Conditions/Comments
2 of 2