Collapse AllExpand All

13.3.2.1. Prerequisites, Interrelationships Previous topic Parent topic Child topic Next topic

AMO - ZAND
Required for enabling the synchronized announcements feature; also for enabling the feature synchronized announcements for CCM calls.
Also required for enabling the synchronized announcements feature for "No answer on AC", for "Call to CSM" and for "Call to hunting group".
AMO - VFGR
Required for marking all ATND groups with a synchronized announcement service for callers.
AMO - SA
Required for marking all hunt groups with a synchronized announcement service for callers waiting in the call queue.
AMO - DIMSU
Required for defining the number of available announcement buffers. This value also defines the total number of lines in a particular node which can be switched to an announcement unit at the same time.
AMO - CTIME
Required for defining the start time of an announcement if calls rung at the attendant console are not answered.
Required for defining the timeout after seizure of a station to either start the announcement for suffix dialing or "Station no answer".
AMO - DTIM1
Required for defining the maximum delay time before the beginning of the announcement is heard after the announcement unit is activated, and for defining the maximum delay time before the beginning of the next announcement in the chain is heard.
Attention: With Genius ST in the text memory from 1 to 3 minutes!
AMO - COT
Required for defining the additional COT parameters necessary for allowing callers to be switched to synchronized announcements.
for asynchronous operation:
ANOD (for TMOM circuit)
for announcements at the attendant console:
WAAN (for calling circuit)
for announcements at an SA AO
ANHT&BSHT (for calling circuit)
for announcements with busy station:
ABNA&IBSY (for calling circuit)
for announcements for camp on
ABNA&KNDI (for calling circuit)
for announcements for station no answer:
ABNA &(IFR) (for calling circuit)
for announcements suffix dialing station busy:
PDOB (for calling circuit)
for announcements suffix dialing station no answer:
PDOT (for calling circuit)
for announcements for DDI:
RDDI (for calling circuit)
for announcements for third-party systems:
SANH (for calling circuit)
for announcements with PSM:
APSM (for calling circuit)
for answering before suffix-dialing or announcement:
ABPD (for calling circuit)
for transporting the announcement type to the CAC node
SATR (for calling circuit)
AMO - COP
The COP parameter set in TSCSU for the TMOM board must contain the parameters SACK and LSUP.
If an announcement is operated in asynchronized mode (with a/b wires only) the COP parameter AANT must be set.
AMO-COSSU
Set the COS ANSYN for the terminal which is to hear the synchronized announcement.
AMO - TSCSU
Once the announcement types have been defined, the TSCSU AMO must be used to configure the TMOM board as a RAS and assign the appropriate announcement type.
AMO - SYNCA
Configure the announcement type. Assign an entry tone and exit tone to an announcement reason. Define, whether you reach the announcement either by ITR or the last dialed number (for hold-the-line announcement at AC).
AMO - LDAT Required for enabling the synchronized announcements feature for calls which are forwarded outside of customer’s network by usage of SYNCA reason ANREASON=FWDOUT
Parameter to be used under AMO LDAT of CO trunk: LATTR=FWDOUT

Example 1: Hold-the-line Announcement at the AC

The Meier company can be reached via ATND group 2. If calls are not answered within a defined time, callers are to hear the first in a series of announcements. This announcement is to be repeated once. If the call has still not been answered at the end of the second repeat, the caller is to be switched to a further announcement, which will then be continuously repeated (looped), until the call is finally answered (or the caller hangs up). The text announcements should be interrupted by 10 seconds of music and 20 seconds of PLEASE_HOLD_THE_LINE. The first announcement is to be configured in START/STOP mode, with a start delay time of 3 seconds. The second announcement is to be set up in CONTINUOUS mode, with a no-load release value of 5 repeats.
ATNDGR 2 is marked as 'with synchronized announcements'. (VFGR AMO).
The last announcement type in a chain of linked announcements must always be defined first
Assign announcement type 2:
AD-SYNCA: ANTT,2,Meier_Inc,ON,255,,MUSIC,10,
ON,HOLDLINE,20,ON,,,, CONT,5;
Assign announcement type 1:
AD-SYNCA: ANTT,1,Meier_Inc,ON,1,2,MUSIC,10,ON,
HOLDLINE,20,ON,,,, STA_STO,3;
Assign entry tone/exit tone for WANNAOHK announcement reason
AD-SYNCA: ANNTONE,WANNAOHK,CAMP,RNGBK;
Create the Announcement Reason/Announcement Type table entries:
You must assign the announcement type 1 to the announcement reason WANNAOHK, depending on the ITR number or last dialed digit with which the ATND group is reached.
If an ATNDGR is reached by direct dialing, the last dialed digit (e.g. 2) is relevant.
The last digit in the attendant code is relevant for CAC (satellite PBX AMO-NAVAR,CD-CASEXT)
AD-SYNCA: ANNMCI,WANNOHK, <ldigit-stno-atnd-cd>, 1;
 
AD-SYNCA: ANNMCI,WANNAOHK, <ldigit-stno-casext>, 1;
Up to EV2.0 it was only possible to assign an announcement type to the last dialed digit (company index). From HV 3.0 you can assign 999 different digit sequences with up to 6 digits to one announcement type. These digits are the last dialed digits. The switch in AMO ZAND must be set to this alternative. 
CHA-ZAND: RESERVE,102, YES;
Then enter the digit sequence (e.g. 471199).
AD-SYNCA: ANNMCI,WANNOHK, 471199, 1;
If the attendant group is reached via an internal FWD, FWDBSY or FNANS, the ITR number of the forwarding station is used (ITR=4). If the group is reached via an external FWD, FWDBSY or FNANS, the ITR number of the caller is used (ITR=0), since the ITR groups are not unambiguous throughout a network.
If the attendant group is reached via "attendant intercept", the ITR number is relevant. If no destination number can be determined, e.g. in the case of attendant intercept due to misdialing or because the station is not authorized for direct inward dialing, the ITR number of the caller is used (ITR-A-STN).
AD-SYNCA: ANNMITR,WANNAOHK, <ITR_A_STN>, 1;
and 
AD-SYNCA: ANNMITR,WANNAOHK, <ITR-FWD-STN>, 1;
If an internal destination (internal user or internal hunting group) can be determined, the ITR number of the internal user or hunting group master is used (ITR = 3). If the destination number is an external number, the ITR number of the caller is used.
AD-SYNCA: ANNMITR,WANNAOHK,<ITR-DEST>, 1;
If you want to activate a synchronized announcement for terminals you must enable the internal application using AMO ZAND
CHA-ZAND: TYPE = ATND,ISYNCAC=YES;
When you assign a COS, you select the user who should hear the synchronous announcement.
CHA-COSSU: TYPE = COS, COS = <ITR-A-STN>, 
AVCE = ANSYN;

Example 2: Announcement with PSM

Callers to the multiple code-calling system CCM are to hear an announcement. The announcement is not to be repeated. After the announcement, the CCM hold tone is to be fed in for as long as possible. The call waiting tone (knocking/camp-on tone) is to be defined as the entry tone, and the ringback tone is to be defined as the exit tone. The required operating mode is START/STOP, and an announcement start delay timer of 2 seconds is to be set.
Synchronized announcements for CCM callers are currently only possible if the announcement unit and the CCM are in the same node. Remote applications are also supported in EV 3.0 and higher.
Use the ZAND AMO to enable synchronized announcements for CCM callers. Parallel ringing and synchronous announcement are possible at the same time. You must disable parallel ringing before you can activate the synchronous announcement for call forwarding on no reply or call forwarding.
CHA-ZAND: TYPE = CCM, SYNCACCM = YES, STNRNG = NO;
Set the APSM parameter in the calling circuit's COT.
CHA-COT: COTNO = <number>, COTTYPE = COTADD, 
PAR = APSM
Assign announcement type 4:
AD-SYNCA: ANTT,2,Meier_Inc,ON,,,HOLDCCS,255,ON,,,,,,,
STA_STO,2;
Assign entry tone/exit tone for ANNCCM announcement reason
AD-SYNCA: ANNTONE,ANCCM,CAMP,RNGBK;
Assign announcement reason/announcement type table: Depending on the ITR code number of the incoming call, the announcement type 4 must be assigned to the announcement reason ANNCCM 4. The ITR numbers used depend on the types of call situation for which the announcement is required.
If the CCM is reached by direct dialing, and the code-calling number dialed belongs to an internal user, the called user's ITR (5) is used.
AD-SYNCA: ANNMITR,ANCCM, <ITR-SEARCHNO-STN>,4;
If the code-calling number dialed belongs to an external user, the calling user's ITR (7) is used.
AD-SYNCA: ANNMITR,ANCCM,7,4;
If the CCM is reached via call forwarding/forwarding on no answer after dialing an internal user's number, the ITR of the internal (forwarding) user (8) is used. 
AD-SYNCA: ANNMITR,ANCCM,8,4;
If the CCM is reached via call forwarding/forwarding on no answer after dialing an external user's number, the caller's ITR (7) is used.
If you want to activate a synchronized announcement for terminals you must enable the internal application using AMO ZAND.
CHA-ZAND: TYPE = CCM,ISYNCCCM=YES;
When you assign a COS, you select the user who should hear the synchronous announcement.
CHA-COSSU: TYPE = COS, COS = <ITR-A-SEARCHER>, 
AVCE = ANSYN;

Example 3: Announcement with Hunting Group Call Queue

Callers to a certain hunt group are to hear a synchronized announcement, if put on hold in the call queue. This announcement is to be repeated 3 times. A 15-second hunting group wait tone is to be fed in between each repeat. The ringback tone is to be used as the entry tone and exit tone. The announcement is to be operated in START/STOP mode, with an announcement start delay of 3 seconds.
Use the SA AMO to mark the hunting group as 'with synchronized announcements' .
Set up announcement type 5:
AD-SYNCA: ANTT,5,Meier_Inc,,ON,3,,HOLDHT,15,ON,,,,,,,
STA_STO,3;
Assign entry tone/exit tone for WANNHG announcement reason
AD-SYNCA: ANNTONE,WANNHG,RNGBK,RNGBK;
Assign announcement reason / announcement type table: Depending on the ITR code number of the incoming call, the announcement type 5 must be assigned to the announcement reason WANNHG. The ITR numbers used depend on the types of call situation for which the announcement is required.
If the hunting group is reached by direct dialing, the ITR number of the hunting group master or the first hunting group member is used (ITR-HT-MASTER).
AD-SYNCA: ANNMITR,WANNHG,7,5;
If the hunting group is reached via call forwarding/forwarding on no answer after dialing an internal user's number, the ITR of the internal (forwarding) user (8) is used. 
AD-SYNCA: ANNMITR,WANNHG,8,5;
If the hunting group is reached via call forwarding/forwarding on no answer after dialing an external user's number, the ITR of the destination number is used (i.e. of the hunting group).
If you want to activate a synchronized announcement for terminals you must enable the internal application using AMO ZAND.
CHA-ZAND: TYPE = ALLDATA2,ISYNCHG=YES;
When you assign a COS, you select the user who should hear the synchronous announcement.
CHA-COSSU: TYPE = COS, COS = <ITR-A-STN>, 
AVCE = ANSYN;

Example 4: General Announcement "Station busy"

Callers who reach busy internal stations are to hear a one-off announcement (announcement type =3). The announcement can only be set up if COT parameters with subsequent attendant intercept are set. If an announcement with subsequent attendant intercept is used, and the call is not answered by the attendant within a specific time limit, callers are to be switched to a second announcement (announcement type =5). The delay time until the call is answered by the attendant, or until the second announcement is started, is to be filled in with music. The second announcement is to start after approx. 15 seconds. After the second announcement, more music is to be fed in for another 30 seconds, followed by 10 seconds of "please hold the line". This cycle is to be repeated 3 times. Since the text of the first announcement is very short, the operating mode is to be set to CONTINUOUS, with a no-load release limit of 5 repeats. The operating mode of the second announcement is to be set to START/STOP, with a start delay time of 3 seconds. The call waiting tone (camp-on) is to be used as the entry tone, and the ringback tone as the exit tone
In this example, the second announcement (if call is not answered within a specific time after attendant intercept) cannot be reached except through the first announcement. The reason for this is that the announcements would otherwise interrupt each other. This means that the wait time for the second announcement can be influenced by the settings for the first announcement. For example, if the first announcement has a length of 4 seconds, the subsequent music feed-in must be set for 9 seconds. The actual start delay of the second announcement thus lies between 13 seconds and 17 seconds. If precise delay times are required, this can only be achieved by running the first announcement in START/STOP mode as well.
Whereas the first announcement, with subsequent attendant intercept, will always be played back in the specified situation, the second announcement will only be played if the attendant intercept destination (ATND group) is marked as "with synchronized announcements".
The synchronous announcement must be configured in the node in which it is required. For example, if an exchange call reaches an internal user via an S0/S2 transit connection, and the call is to be cleared down back to the originating node, the announcement will have to be configured in this node.
Assign announcement type 5 (second announcement):
AD-SYNCA:ANNTT,5,Meier_Inc,ON,3,,MUSIC,30,ON,
HOLDLINE,10,ON,,, STA_STO,3;
Assign announcement type 3 (first announcement):
AD-SYNCA: ANNTT,3,Müller_Inc,ON,,5,MUSIC,9,ON
,,,,,,,CONT,5;
Assign entry tone/exit tone for ANNBUSY announcement reason
AD-SYNCA:ANNTONE,ANNBUSY,CAMP,RNGBK;
Assign announcement reason/announcement type table: Depending on the ITR code number of the incoming call, the announcement type 3 must be assigned to the announcement reason ANNBUSY. The ITR numbers used depend on the types of call situation for which the announcement is required.
If the busy station is reached by direct dialing the ITR of the called station (5) is used.
AD-SYNCA: ANNMITR,ANNBUSY,5,3;
If the busy station is reached via call forwarding/forwarding on no answer after dialing an internal user's number, the ITR of the internal (forwarding) user (8) is used.
AD-SYNCA: ANNMITR,ANNBUSY,8,3;
If the busy station is reached via call forwarding/forwarding on no answer after dialing an external user's number, the ITR of the destination number is used (i.e. of the busy station).
If a call is switched to the attendant (attendant intercept) in the originating node after dialing a network number in another node, the ITR of the destination station number is also used (i.e. ATND).
This announcement cannot be used for a terminal.

Example 5: General Announcement "Station no Answer"

This is the same as example 4, except that the announcement reason is to be "no answer" as opposed to "busy". Substitute the announcement reason parameter for this example ANNBUSY by ANNOHK. Other than with the "General announcement "Station busy" this announcement is not combined with an attendant intercept. You need not set the COT parameter IFR (Intercept when no answer) in order to connect a synchronized announcement.
If the COT parameter IFR is set for the calling trunk, the announcement is interrupted for the attendant intercept. To avoid this, the size of the intercept timer must be in relation with the announcement length and to the configured value of the announcement start timer (minimum value = 5).
This announcement cannot be used for a terminal.

Example 6: General Announcement with Automatic Camp on

Calls to a station in a two-party call are to hear a synchronized announcement during automatic camp on. Set the COT parameter KNDI for automatic camp-on on a busy station. The announcement is also activated during transfer.
Assign announcement type 7 as required, e.g.:
AD-SYNCA: Anntt,7,Camp,On,,5,Camp,10,On,,,,,,,Stasto,2;
Assign the entry/exit tone for the "Anknock" announcement reason : 
AD-SYNCA:Anntone,Anncamp,Camp,Camp;
Assign announcement reason/announcement type table: Set announcement type 7 for the ANKNOCK announcement reason, depending on the ITR number of the camped-on party. For DDI to a busy station the ITR (ITR =5) of the busy station is valid. 
AD-SYNCA: Annmitr, Anncamp, 5, 7;
This announcement cannot be used for a terminal.

Example 7: Announcement "Station Busy with Suffix Dialing"

Callers via analog trunks who reach a busy user, but can re-route via DTMF suffix-dialing, are to hear an appropriate announcement (announcement type 11). In this case, the COT parameter IBSY must not be set. The announcement is not to be repeated, and is to be followed by 10 seconds of music. The operating mode is to be Start/Stop, with a start delay time of 3 seconds. The busy tone is to be defined as the entry tone and exit tone.
Assign announcement type 11:
AD-SYNCA:,ANTT,11,Meier_Inc,ON,,,MUSIC,10,ON
,,,,,,,STA_STO,3;
Assign entry tone/exit tone for SDBUSY announcement reason
AD-SYNCA:,ANNTONE,SDBUSY,BUSY,BUSY;
Assign announcement reason / announcement type table:
The same rules apply as for example 4, except that the announcement reason ANNBUSY must be replaced with SDBUSY instead.

Example 8: Announcement "Station no Answer with Suffix Dialing"

Callers via analog trunks with DTMF suffix dialing, who reach a station user who does not answer within a set time, are to hear an appropriate announcement. The same rules apply as for example 5, except that the announcement reason ANOHK must be replaced with SDOHK instead.

Example 9:

Calls via analog trunks without direct dialing authorization but with DDI functionality are to receive an announcement immediately after incoming trunk seizure (announcement type 12). This announcement is not to be repeated, and no further internal tones are to follow. The ringback tone is to be defined as the entry tone, and a special dialing tone as the exit tone. The operating mode is to be Start/Stop, with a start delay time of 1 second.
Assign announcement type 12:
AD-SYNCA:ANTT,12,Meier_Inc,ON,,,,,,,,,,,,
STA_STO,1;
Assign entry tone/exit tone
AD-SYNCA:ANNTONE,RNGBK,SPEC;
Assign announcement reason/announcement type table:
For this announcement reason, there are no destination number ITRs to be used. The announcement reason must therefore be entered as dependent on the ITR number of the caller (ITR=2).
AD-SYNCA:ANNMITR,DIDSD,2,12;

Example 10: Wait announcement on AC with night service

The Meier company can be reached via ATND group 2. If the calls are not answered within a configurable time and the AC is switched to night service, an announcement of type 19 is to be injected. This announcement is to be repeated once. The text announcements should be interrupted by 10 seconds of music and 20 seconds of PLEASE_HOLD_THE_LINE. The first announcement is to be configured in START/STOP mode, with a start delay time of 3 seconds. For day time operation the settings in example 1 apply.
ATNDGR 2 is marked as 'with synchronized announcements'. (VFGR AMO).
Set up announcement type 19:
AD-SYNCA:ANNTT,19,Meier_Inc,ON,1,,,MUSIC,10,
ON,HOLDLINE,20,ON,,,, Stasto,3;
Assign entry tone/exit tone for WANNADNS announcement reason
AD-SYNCA: ANNTONE,WANNDNS,RNGBK,FRNGBK;
Create the Announcement Reason/Announcement Type table entries:
You must assign the announcement type 19 to the announcement reason WANNDNS, depending on the ITR number or last dialed digit with which the ATND group is reached.
If an ATNDGR is reached by direct dialing, the last dialed digit (e.g. 2) is relevant.
AD-SYNCA: ANNMCI,WANNDNS,2,19;
When night service is active at the night station, the night station's ITR is relevant (ITR_NIGHT) if the night station is in the same node as the announcement unit.
AD-SYNCA: ANNMITR, WANNDNS, <ITR-NIGHT>, 19
If the attendant group is reached via an internal FWD, FWDBSY or FNANS, the ITR number of the forwarding station is used (ITR=4). If the group is reached via an external FWD, FWDBSY or FNANS, the ITR number of the caller is used (ITR=0), since the ITR groups are not unambiguous throughout a network.
If the attendant group is reached via "attendant intercept", the ITR number is relevant. If no destination number can be determined, e.g. in the case of attendant intercept due to misdialing or because the station is not authorized for direct inward dialing, the ITR number of the caller is used (0).
AD-SYNCA: ANNMITR,WANNDNS, <ITR-A-STN>,  

and  
 
AD-SYNCA: ANNMITR,WANNDNS, <ITR-DEST>, 19;
If an internal destination (internal user or internal hunting group) can be determined, the ITR number of the internal user or hunting group master is used (ITR = 3). If the destination number is an external number, the ITR number of the caller is used.
AD-SYNCA: ANNMITR,WANNDNS, <ITR-DEST>, 19;
If you want to activate a synchronized announcement for terminals you must enable the internal application using AMO ZAND.
CHA-ZAND: TYPE = ATND, ISYNCAC=YES;
When you assign a COS, you select the user who should hear the synchronous announcement.
CHA-COSSU: TYPE = COS, COS = <ITR-A-STN>, 
AVCE = ANSYN;
${DocTitle}, ID: ${DocID}
© 03/2026 Mitel Networks Corporation. All rights reserved. Mitel and the Mitel logo are trademark(s) of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH & Co. KG. All other trademarks herein are the property of their respective owners.