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
351
Administration for Network Connectivity
555-233-504 — Issue 1 — April 2000 CID: 77730
B 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.
Each extension code can be assigned to 1 of 6 possible treatments.
• UDPCode — Conversion to AAR with given location code, further conversion
suppressed
• AARCode — Conversion to AAR with given location code, further conversion
allowed
• ENPCode — Conversion to private network number (via ENP form), route to
given node number routing
• TempOOS — Temporarily out of service, give reorder
• Local — Local range of extensions
• blank — Similar to local, however, this extension is not chosen when the system is
asked to “add a station”
When a user at a switch that is included in a UDP dials an extension, DEFINITY ECS
first checks to see if the extension is assigned to a local station on that switch. If so,
the call is routed to the station, and UDP is not invoked. If the extension is not found
locally, the system checks to see if the extension matches an assigned extension code.
If the extension matches an assigned extension code, the system performs the
specified conversion into a private network number and routes the call as specified. If
more than one extension code matches, the “best” match (most explicit digits) is used.
For example, 1234x is chosen over 123xx if 12345 is dialed. However, 123xx is
chosen if 12355 is dialed. If no matching extension code is found, the user receives
intercept treatment. Or, if Extended Trunk Access (ETA) is enabled, the call routes
via ETA.
Example of how UDP
works
To administer, assign each UDP code:
• To a private network location code (RNX) or node number. (The RNX is
equivalent to an office code of a central office in a public network. This RNX
determines how a UDP call is routed.)
• Assign each UDP code as either local or remote to the switch.
To understand the function of a UDP, review the following example.