- 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

ITG Engineering Guidelines Page 127 of
378
ITG Trunk 2.0 ISDN Signaling Link (ISL) Description, Installation and Operation
In most corporate environments, the intranet is primarily supporting data and
other services. When planning to offer voice services over the intranet the
technician needs to assess the following:
• Are there existing QoS mechanisms? What kind? The ITG traffic should
take advantage of established mechanisms if possible.
• What is the traffic mix? If the ITG traffic is small compared to data traffic
on the intranet, then IP QoS mechanisms can suffice. If ITG traffic is
significant, data services might be impacted when those mechanisms are
biased toward ITG traffic.
TCP traffic behavior
The majority of corporate intranet traffic is TCP-based. Unlike UDP which
has no flow control, TCP uses a sliding window flow control mechanism.
Under this scheme TCP increases its window size, increasing throughput,
until congestion occurs. Congestion is detected by packet losses, and when
that happens the throughput is quickly throttled down, and the whole cycle
repeats. When multiple TCP sessions flow over few bottleneck links in the
intranet, the flow control algorithm can cause TCP sessions in the network to
throttle at the same time, resulting in a periodic and synchronized surge and
ebb in traffic flows. WAN links would appear to be congested at one time,
and then followed by a period of under-utilization. There are two
consequences:
• poor efficiency of WAN links, and
• ITG traffic streams are unfairly affected
ITG support for TOS field and IP QoS
You can configure the DiffServ/TOS value for Control and Voice packets, if
required, to obtain better QoS over the IP data network (LAN/WAN). Do not
change DiffServ/TOS from default value of 0 unless instructed by the IP
network administrator.
The Type of Service (TOS) byte or Differentiated Service (DiffServ) code
point determine the priority of the control and voice packets in the network
router queues. The values entered in these two boxes must be coordinated
across the entire IP data network. Do not change them arbitrarily.