Feature Interactions And Compatibility - Avaya G250 Maintenance Manual

Avaya Communication Manager controlled maintenance

Feature interactions and compatibility

H.248 Link Recovery and Connection Preservation can affect the performance of features or
adjuncts within the configuration
interactions on page 78).
Table 26: 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)
78 Maintenance for the Avaya G250 and Avaya G350 Media Gateways
(Table 26: H.248 Link Recovery feature/adjunct
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. This information can be
stored in flash NVRAM or directed to a syslog
server for later processing.
Measurements collected during the recovery
period might be inaccurate in those reports that
rely upon time-related data.
1 of 6