Filter
Top Products
Page 186 of
378
Install and configure ITG ISL Trunk node
553-3001-202 Standard 1.00 April 2000
Turn off ITG route during peak traffic periods on the
IP data network
Based on site data, if fall back routing occurs frequently and consistently for
a data network during specific busy hours (e.g., 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 ITG routes are as follows:
a Go to LD 86 ESN data block to configure the Time of Day Schedule
(TODS) for the required ITG control periods.
b Go to LD 86 RLB and apply the TODS on/off toggle for that route
list entry associated with an ITG trunk route.
ESN5 network signaling
ITG Trunk 2.0 supports ESN5 Network Signaling protocol only, in addition
to standard (i.e., non-network) signaling. ITG 2.0 supports a mixed network
consisting of ESN5 and standard network signaling nodes.
For example, the network may contain some ITG Trunk 1.0 basic trunk
signaling nodes or other IP telephony gateways that use H.323 V2 instead of
SL1 (MCDN) signaling, and do not support ESN5. You must configure an
ESN5 prefix for the non-ESN5 IP telephony gateways by using the
“esn5PrefixSet” command from the ITG shell CLI.
For ITG Trunk 2.0 nodes that are configured in the Node Properties to use
SL1ESN5 Protocol, the ESN5 prefix configured on the ITG Trunk card is
inserted in front of the called number on incoming calls from IP Telephony
gateways using the H.323 V2 protocol.
For ITG Trunk 2.0 nodes that are configured in the Node Properties to use the
SL1 protocol (i.e., they do not support ESN5 to their host Meridian 1), the
ESN5 prefix configured on the ITG Trunk card is inserted in front of the
called number on outgoing calls to ITG Trunk 2.0 nodes that are configured
to use ESN5 with their host Meridian 1.