Page 82 of 910 Features
553-3001-365 Standard 4.00 August 2005
Main office failure for branch office
(scenario 2):
• IP Phones A and B register with the Media
Gateway 1000B and are redirected to the
main office.
• Branch office warm or cold starts.
• Branch users A and B registered with the
main office establish a call.
• A serious main office failure occurs so the
active branch IP Phones cannot reregister
with the main office and they reregister
with the Branch office in local mode. IP
Phone A reregisters in local mode first.
The call is not lost.
Although the branch office LTPS wrote the IP
Phones A and B data to its RLM table when it
redirected the IP Phones to the main office,
the RLM data is lost and cannot be restored
when the branch office restarts. The transition
is similar to a Call Server cold start: PARTIAL
REBUILT -> REBUILT.
Primary Call Server failure (WAN
geographically redundant system):
• A call is established between IP Phones A
and B that are registered with the primary
site in the geographically redundant
system.
• The primary site fails.
• The IP Phones are reregistered with the
secondary site. IP Phone A reregisters
first.
The call is not lost.
IP Phones can be configured in 2 ways:
1Site 1 is the secondary site and Site 2 is
not configured.
In this case the scenario is the same as
main office failure for branch office
(scenario 1): the HALF REBUILT->
REBUILT transition.
2IP Phones have Site 1 defined as the
primary site while Site 2 is defined as the
secondary site. Registration by Site 1
fails.
In this case, the secondary site’s Call
Server does not have the RLM entries for
the reregistering IP Phones and the
scenario is the same as main office failure
for branch office (scenario 2): the
PARTIAL REBUILT -> REBUILT
transition.
Table 13
ACF behaviors (Part 4 of 8)
Scenario Result