.
Problem Description ------------------- AUD112 is printed in unknown scenario.
MPLR32014 DIAG002 and DIAG004 messages are printed on every audit loop.
AUD112 529 0 31877 1 AUD112 240 7 39103 0
DIAG004 : MPLR32014 2:56:05
16/07/2014 GHT:483 1 DN:28806 NOT FOUND IN DN_GHBLK DIAG004 : MPLR32014 2:56:0
5 16/07/2014 GHT:483 2 DN:28805 NOT FOUND IN DN_GHBLK
Problem Analysis ----------------
The customer did not mention any scenario leading to the messages AUD112, DIAG002, DIAG004. I
. One scenario with AUD112 has been found.
Actions:
1. A user creates new group hunt list GHT in LD 18 with a DN and assigns a new key SCC <GHT> to a digital set (A)
. 2. The user makes all appearances of the DN busy.
3. The user presses SCC key on the set A, dials position number to change, dials a DN, presses SCC key again to save the changes
. 4. The user runs the audit in LD 44.
Expected:
1. GHT is created, TN is changed.
2. The DN is busy.
3. The DN is accepted by Group Hunt feature, the DN is stored against the dialed position number.
4. AUD112 is printed, the last number is one showing the SCC modification has marked as idle but not busy (turned on dfo 5 shows DN state).
Design team has created a GEN patch MPLR33311
MPLR32014 DIAG002 and DIAG004 messages are printed on every audit loop.
AUD112 529 0 31877 1 AUD112 240 7 39103 0
DIAG004 : MPLR32014 2:56:05
16/07/2014 GHT:483 1 DN:28806 NOT FOUND IN DN_GHBLK DIAG004 : MPLR32014 2:56:0
5 16/07/2014 GHT:483 2 DN:28805 NOT FOUND IN DN_GHBLK
Problem Analysis ----------------
The customer did not mention any scenario leading to the messages AUD112, DIAG002, DIAG004. I
. One scenario with AUD112 has been found.
Actions:
1. A user creates new group hunt list GHT in LD 18 with a DN and assigns a new key SCC <GHT> to a digital set (A)
. 2. The user makes all appearances of the DN busy.
3. The user presses SCC key on the set A, dials position number to change, dials a DN, presses SCC key again to save the changes
. 4. The user runs the audit in LD 44.
Expected:
1. GHT is created, TN is changed.
2. The DN is busy.
3. The DN is accepted by Group Hunt feature, the DN is stored against the dialed position number.
4. AUD112 is printed, the last number is one showing the SCC modification has marked as idle but not busy (turned on dfo 5 shows DN state).
Design team has created a GEN patch MPLR33311
