13.3.4.4. Announcements for Hunting Group Call Queue 
- Is the call queue capacity of the hunt group large enough? (SA: CQMAX > 0)?
- Is the hunting group configured "with synchronized announcements"? (SA: CSANS=Y)?
- Are the COT parameters ANHT and BSHT set for the connecting lines?
- Is the announcement reason (WANNHG) 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 dialing to the hunting group, the appropriate announcement types must be entered for the WANNHG announcement reason in the ANNMITR table for the ITR number of the first station in the hunting group.
- For callers who reach the hunting group via FWD/FNANS/FBSY, the appropriate announcement type must be entered for the WANNHG 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 first station in the hunting group applies.
- Has the internal application (calling party is terminal) been enabled
for internal traffic using AMO ZAND (from EV 3.0)?
AMO-ZAND BRANCH ALLDATA2, parameter ISYNCHG = YES
- Is the parameter ANSYN set in the internal terminal's COS?
- Is ZAND:ALLDATA HOLDHUNT set to "NO"? If it is "YES", then music on hold/please hold will be heard instead of the configured announcement.