- LG Software Innovations Coffeemaker User Manual
Table Of Contents
- Title Page
- Revision history
- Contents
- About this guide
- Description
- System requirements
- List of ITG ISDN components
- Ordering rules and guidelines
- ITG ISL Trunk card description
- ITG ISL Trunk card physical description
- ISDN Signaling Link
- Dialing plans
- Quality of Service
- Fallback to alternate facilities
- Type of Service
- Fax support
- Remote Access
- Per-call statistics support using RADIUS Client
- SNMP MIB
- Codec profiles
- Security passwords
- ITG Engineering Guidelines
- Introduction
- Network engineering guidelines overview
- ITG traffic engineering
- Configuration of Meridian 1 routes and network translation
- Assess WAN link resources
- QoS Evaluation Process Overview
- Set QoS
- Measure intranet QoS
- Implement QoS in IP networks
- ITG Trunk DSP profile settings
- Post-installation network measurements
- Estimate QoS level
- ITG MAT PC management configuration
- Install and configure ITG ISL Trunk node
- Before you begin
- Installation Procedure Summary
- Create the ITG Trunk Installation Summary Sheet
- Install and cable ITG trunk cards
- Install NTCW84JA Large System I/O Panel 50-Pin filter adapter
- Install NTMF94EA and NTCW84KA cables
- D-channel cabling for the NT0961AA 24-Port ITG Trunk card
- Set NT6D80 MSDL switches
- Install filter and NTND26 cable (for MSDL and DCHIP cards in same Large System equipment row)
- Install filter and NTND26 cable (for MSDL and DCHIP cards in different Large System equipment rows)
- Configure ITG Trunk data on the Meridian 1
- Configure dialing plans within the corporate network
- Configure ITG Trunk data on MAT
- Transmit ITG trunk card configuration data from MAT to the ITG trunk cards
- Set date and time for the ITG ISL Trunk node
- Change the default ITG shell password to maintain access security
- Change default ESN5 prefix for non-ESN5 IP telephony gateways
- Check card software
- Configure MAT Alarm Management to receive SNMP traps from ITG ISL Trunk cards
- Make test calls to the remote ITG nodes
- Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks
- Upgrade procedure summary
- Before you begin
- Install the DCHIP hardware upgrade kit
- Upgrade the 8-port ITG basic trunk software to ITG ISL trunk software
- Remove ITG 1.0 configuration data from Meridian 1
- Configure the Meridian 1 ITG ISL Trunk data: upgrade considerations
- Verify ROM-BIOS version
- Upgrade Troubleshooting
- OA&M using MAT applications
- OA&M using the ITG shell CLI and overlays
- Maintenance
- Appendix A: Calbe description and NT8D81BA cable replacement
- NTMF94EA E - LAN, T - LAN and Serial Port cable
- NTCW84KA E-LAN, T-LAN, DCH & Serial cable
- NTAG81CA Faceplate Maintenance cable
- NTAG81BA Maintenance Extender cable
- NTCW84EA DCH PC Card Pigtail cable
- NTMF04BA MSDL extension cable
- NTCW84LA and NTCW84MA upgrade cables
- Prevent ground loops on connection to external customer LAN equipment
- Replace cable NT8D81BA with NT8D81AA
- Tools list
- NT8D81BA cable removal procedures
- Appendix B: Environmental and electrical regulatory data
- Appendix C: Subnet mask conversion from CIDR to dotted decimal format
- Appendix D: Configure a Netgear RM356 modem router for remote access
- Index
- Back
Page 132 of
378
ITG Engineering Guidelines
553-3001-202 Standard 1.00 April 2000
Multiple ITG nodes on the same E-LAN and T-LAN segments
There are several configurations where it can be acceptable to put multiple
ITG nodes on the same dedicated E-LAN and T-LAN segments (separate
subnets), or on a dedicated E-LAN/T-LAN segment (single subnet):
1 Several ITG nodes belonging to the same customer in the same
Meridian 1 PBX may be configured to route calls with different
CODECs depending on the digits dialed or the NCOS of the originating
terminal, or to limit the maximum number of ITG calls to a particular
destination node. The traffic engineering considerations on the T-LAN
should determine how many different ITG nodes can be configured on
the same LAN segment.
2 Layer Two (10 BaseT or 100 Base TX) switching equipment or ATM
infrastructure can support a virtual LAN (VLAN) segment that is
distributed across a campus or larger corporate network. In this case
some or all of the ITG destination nodes can be on the same subnet.
3 In test labs, training centers, and trade shows it is common for destination
nodes to be located on the same LAN segment and subnet.
You must not place other IP devices, either Nortel Networks’ or other
vendors’ products, on the same T-LAN subnet with the ITG nodes.
Setting up the E-LAN or management subnet
The management LAN, or E-LAN, is 10BaseT Ethernet. Very little traffic is
generated by the ITG node on this network. Cards generate this traffic when
the cards have been reset and are looking for the active leader, and when
SNMP traps are emitted due to ITG card events and errors. A standard
configuration is an 8-port passive hub connecting the ITG system
management Ethernet to the MAT PC through the E-LAN. If the E-LAN also
carries functional signalling traffic for Symposium Call Center Server
(SCCS), Small Symposium Call Center (SSCC), or Call Pilot multimedia
message server, then the E-LAN can be configured on a switching hub to
maximize data throughput.
Selecting public or private IP addresses
The customer must consider a number of factors to determine if the T-LAN
and E-LAN will use private (internal IP addresses) or public IP addresses.