13.3.4.5. General Announcements if Called Station is Busy 
- Have the COT parameters ABNA&IBSY been set for the connecting line?
- Are you sure that the COT parameter KNDI has NOT been set for the connecting line?
- Is the announcement reason (ANNBUSY) entered in the ANNTONE branch in the AMO-SYNCA?
- Have the correct entries been made in the announcement reason/announcement type table,
ANNMITR?
(SYNCA)
- For direct lines:
- For direct dialing to the a station user, the appropriate announcement types must be entered for the ANNBUSY announcement reason in the ANNMITR table for the ITR number of the called station user.
- For callers who reach the station user via FWD/FNANS/FBSY, the appropriate announcement types must be entered for the ANNBUSY announcement reason in the ANNMITR table for the ITR number of the forwarding station. However, this only works for forwarding stations in the same node as the announcement unit or in homogeneous OS4k networks, where the partner node can provide the ITR group information for the redirecting station. Otherwise, the ITR number of the called, busy station user applies.
- For transit lines:
In this case, the connection is cleared back to the node with the exchange line interface (originating node).
- Is the synchronized announcement configured in the originating node?
- For direct dialing to the a station user, the appropriate announcement types must be entered for the ANNBUSY announcement reason in the ANNMITR table for the ITR number of the calling exchange line.
- For callers who reach the station user via FWD/FNANS/FBSY, the appropriate announcement types must be entered for the ANNBUSY announcement reason in the ANNMITR table for the ITR number of the forwarding station. However, this only works for forwarding stations in the same node as the announcement unit or in homogeneous OS4k networks, where the partner node can provide the ITR group information for the redirecting station. Otherwise, the ITR number of the exchange line applies.
- For direct lines: