Page 34 of 378 Description
553-3001-202 Standard 1.00 April 2000
Each customer requires one or more dedicated ITG nodes. ITG trunks on the
same ITG node share the same dialing plan and IP network connectivity . ITG
trunks cannot be shared between customers th at have indepe ndent numb ering
plans and IP networks.
It is possible to configure multiple ITG nodes for one customer. This
configuration allows load balancing among multiple Leaders for systems
with more traffic than a single Leader card can support. The configur ation of
multiple ITG nodes on one customer requir es spli tting the dialing plan a mong
the Leaders. Each Leade r must h av e a dist inc t ran ge o f the dia lin g pl an . Thi s
restriction exists so that a remote gateway can relate a DN with a single IP
address.
Note: For information about engineering an ITG node, please refer to
the Engineering Guidelines section.
Interactions among card functionsActive Leader and Follower card interaction
The Active Leader card controls the assignment of IP addresses for all new
ITG ISL Trunk cards in its node. If a new ITG ISL Trunk card is added as a
Follower, the new Card Configuration data, as programmed in MAT, is
downloaded only to the Active Leader card. When it boots up, the new
Follower card requests its IP address from the Active Lea der card thro ugh the
protocol. When the Follower cards boot up, they receive their IP
address and Active Leader card IP address from the Active Leader card.
Follower cards continuously send Update messages to the Active Leader
card. These messages in form the Active Lead er car d of th e Fo ll owers’ most
recent status and resources. The Active Leader s ends Upd at e messag es to the
Follower cards, informing them of the updated dial ing number to IP address
translation information. Also the Active Leader card continuously sends
messages about changes in the network performance of each destina tion nod e
in the dialing plan.
If a Follower card fails (for example, DSP failure), it reports to the Active
Leader that its failed resources are not availabl e. The trunk ports involved are
considered faulty and appear busy to the Meridian 1. Ca ll processing is
maintained on the remaining ITG trunks.