This document describes problems, symptoms, and a possible resolution
which relates to the Daylight Saving Time time change on the Avaya Definity G3.
The purpose is for call routing to run efficiently after the time
If the Multi-Application Platform on the Definity (MAPD) card does not
handle the time change properly, the Peripheral Gateway (PG) and Peripheral
Interface Manager (PIM) go offline. Due to this, the Cisco Intelligent Contact
Management (ICM) fails to route calls to a site with an Avaya Definity
Cisco recommends that you have knowledge of these topics:
The information in this document is based on these software and
The information presented in this document was created from devices in
a specific lab environment. All of the devices used in this document started
with a cleared (default) configuration. If your network is live, make sure that
you understand the potential impact of any command before you use it.
Technical Tips Conventions for more information on document
These are possible problems after the Daylight Saving Time change on
Avaya Definity G3:
Definity G3 PG PIM goes offline
Call routing does not work correctly to sites which have an Avaya
Sites that have Avaya Definity G3 do not take any
AlarmTracker shows a peripheral is
Maximize the PIM process window on the PG which experiences the
problem. Notice these items:
The PIM process window taskbar shows the PIM in "a"
Error message Activation Timeout on ASAI Link
appears in the PIM process window.
This problem occurs if the MAPD card does not handle the time change
properly. This problem can be fixed if you reset the MAPD card on the Avaya
Definity G3. Most often this can be accomplished in one of three ways by the
Avaya support on site.
If the PIM is still not active, inspect the PIM logs to see if the Call
Management System (CMS) feed is active. If it is not active, restart the CMS
If the problem continues,
case with Cisco Technical Support.