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
Distributed Communications System B Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
324
DCS Over ISDN-PRI
D-channel
considerations
• 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.25 processor channel links) Remote
Port in the “Processor Channel Assignments” form refers to the processor
channel of the destination PBX. In an Integrated DCS network, Remote Proc
Chan in the “Processor Channel Assignments” form refers to the processor
channel of the Gateway PBX (if the destination PBX is an ISDN DCS PBX), not
the destination PBX.
On the contrary, Machine-ID in the “Processor Channel Assignments” form
refers to the destination PBX, either an ISDN DCS PBX or a traditional DCS
PBX. The Gateway PBX number
must not be used in this field if the destination
PBX is an ISDN DCS PBX.
Enhanced DCS
considerations
• If the DCS link fails, the administrator can choose to allow calls to continue
without class of restriction checking or to block all DCS calls to inward-restricted
stations.
LWC considerations • LWC cannot be successfully activated toward any system that is not capable of
storing the messages, either internally or in an associated adjunct.
• Messages from one node, through an intermediate node, to a remote node do not
require storage capability at the intermediate node.
• LWC transparency is supported for all DCS configurations except for cases when
either the activating node or the remote node is either an ENHANCED
DIMENSION PBX or a System 85 R2V1.
• Retrieval of LWC messages is permitted only from a terminal at the node where
the messages are stored.
• DCS LWC cannot be activated from an attendant console.
Trunk Group
Busy/Warning
Indication
considerations
• Trunk Group Busy and Trunk Group Warning Indication is particularly useful
with the Attendant Control of Trunk Group Access feature. The indicators alert
the attendant when control of access to local and remote trunk groups is necessary.