Periods On The Ip Data Network; Esn5 Network Signaling; On The Ip Data Network - Nortel 1000 Description, Installation And Operation Manual
Networks communication server, ip trunk installation
Hide thumbs
Also See for 1000:
- Features and services fundamentals (616 pages) ,
- Fundamentals (492 pages) ,
- Installation and commissioning manual (468 pages)
Table of Contents
Advertisement
Page 306 of 644
Turn off IP Trunk 3.01 (and later) route during peak traffic
periods on the IP data network
ESN5 network signaling
553-3001-363
Standard 2.00
Install and configure IP Trunk 3.01 (and later) node
Based on site data, if fallback routing occurs frequently and consistently for
a data network during specific busy hours (for example, every Monday
10-11am, Tuesday 2-3pm), these hours should be excluded from the RLB to
maintain a high QoS for voice services. By not offering voice traffic to a data
network during known peak traffic hours, the incidence of conversation with
marginal QoS can be minimized.
The time schedule is a 24-hour clock which is divided up the same way for
all 7 days. Basic steps to program Time of Day for IP Trunk 3.01 (and later)
routes are as follows:
1
Go to LD 86 ESN data block to configure the Time of Day Schedule
(TODS) for the required IP Trunk 3.01 (and later) control periods.
2
Go to LD 86 RLB and apply the TODS on/off toggle for that route list
entry associated with an IP Trunk 3.01 (and later) trunk route.
The original ITG-T ISDN application had two major categories of endpoints:
•
ISDN-capable endpoints
•
Non-ISDN endpoints
ESN5 information transmission is a mechanism allowing the transmission of
NCOS information. ESN5 digit transmission was added when the ISDN
capability was added to ITG Trunks. ITG Trunk ISDN endpoints were able
to insert the ESN5 prefix in an outgoing message if necessary, and did so
based on the information in the dialing plan tables. This was the only possible
alternative, since the flag indicating the type of ESN5 prefix and the two
prefix digits were also legitimate dialed digits. Non-ISDN endpoints were, by
definition, unable to handle ISDN, and therefore were not ESN5-capable.
IP Trunk 3.01 (or later) and ITG Trunk 2.x support a mixed network of
remote nodes with ESN5 and standard (non-NCOS broadcasting) signaling.
September 2004
Advertisement
Table of Contents
