Avaya MCC1 Maintenance Procedures page 138

Server initialization, recovery, and resets
Link Recovery
Table 50: H.248 Link Recovery feature/adjunct interactions
Feature or adjunct
Feature Access Codes (FAC)
Non-IP trunks/stations, including
such circuit-switched TDM resources
as DCP, analog, or ISDN-PRI.
Terminals
Adjunct Switch Application Interface
(ASAI)
Voice mail adjuncts
(INTUITY, INTUITY Audix)
Call Detail Recording (CDR)
Call Management System (CMS)
Property Management System (PMS)
Conversant voice response systems
Network fragmentation
A likely outcome to an H.248 link recovery scenario is that a network of G700 Media Gateways and IP
endpoints, initially registered to the primary server, may now be registered to a number of different LSPs
in the network. This can be very disruptive in that network capability may be highly compromised.
Resources at various points in the network may be available in only limited quantities, or not at all.
138
Description
Feature Access Codes, whether dialed or administered
buttons, do not work.
These resources are unavailable until the H.248 link is re-
established.
Time-of-Day, busy lamp states, and call appearance status
on some phones might not instantaneously reflect the correct
information until the H.248 link is re-established.
ASAI-based applications that utilize timing loops, time-
related methods, or events might not perform as intended. In
addition, applications that do not accommodate time-outs or
missing state transition(s) might behave unpredictably.
During Link Recovery, callers connected to AUDIX remain
connected even if they hang up. Such calls might be
automatically disconnected by AUDIX if the connection
remains intact without the calling party entering tone
commands to AUDIX or voicing a message.
Call records cannot reflect the correct disconnect time if the
calling party hangs up before the link recovers.
Measurements collected during the recovery period might be
inaccurate in those reports that rely upon time-related data.
Automatic Wake-up, Daily Wake-up, and Housekeeping
Status features might not operate as expected if the link fails
and the time to search for alternate resources exceeds the
PMS application's time-out parameters.
For example, if a guest has a wake-up call schedule for 6:15
AM and the H.248 link goes down at 6:10 but recovers at
6:20, then the guest receives no wake up call at 6:15.
Conversant applications that utilize timing loops, time-
related methods, or events might not perform as intended. In
addition, applications that do not accommodate time-outs or
missing state transition(s) might behave unpredictably.
Maintenance Procedures
December 2003