Advanced Communications Controller B.03.32.00 Release Notes
Advanced Communications Controller B.03.32.00 Release Notes
Patches and Fixes for this Version
Chapter 1 13
The problem occurred because the $STAT message in the DAM was given lower priority
compared to messages in Express Queue, High Priority Queue and Low Priority queue.
Because of this, the status always got updated after processing messages in the queues.
Hence the % activity always showed 0% because the CPU already finished processing
messages and is now idle. The code change has been done such that the $STAT message is
given higher priority than the messages in the Express Queue, High Priority, and Low
Priority Queue.
• JAGad40862
Symptoms: The x25stat command needs enhancment to show “VC Up Time” for all active
virtual circuits.
Defect/Fix: Provided -u option in the x25stat command so that the user can request the
“VC Up Time” for all active virtual circuits. A new ioctl has been added for this purpose.
This option must be used in conjunction with the -v option of the x25stat command.
• JAGad56962
Symptoms: ACC firmware does not free buffers when the terminal is deactivated and
disabled.
Defect/Fix: When messages are sent down to an HDLC-LAPB terminal after enabling it,
but before the link is established, those messages are never completed or flushed unless
the link comes up. This leads to a variety of problems, including card buffer limits being
reached.
The Level 2 state machine has been adjusted to make sure messages are flushed after the
first attempt at link establishment. After the T1 x N2 SABM attempt, all messages are
flushed and no further messages are accepted by the protocol as the link down status is
set.
• JAGad66065
Symptoms: zmasterd stop causes system panic.
Defect/Fix: The customer is using ACC/ISDN cards with OTS and FTAM software for
collecting information from phone pbx. During the night transfers, the card is
intermittently hung and transfer is stalled. When trying to stop the card by the MC/SG
scripts, the stopping of zmasterd caused system panic.
The panic is due to accessing a null pointer and trying to do bcopy of a value accessed by
that null pointer. Now the defect has been fixed by checking if the pda->resp_qdb is
NULL. Only if it is not NULL, bcopy is done.










