Section 13.3.1. General

13.3.1. General

Synchronized announcements are used for providing callers with a specific sequence of information prompts in order to achieve specific reactions. This is dependent on the call progress/traffic situation of the incoming call.

The prompts/announcements are achieved by connecting external announcement units to TMOM2 boards. Each prompt or announcement is heard from the beginning. Up to 50 callers can listen to an announcement at any one time. If more than 50 callers are to be able to listen to the same announcement or, if the time callers spend waiting for an announcement to begin is to be minimized, then the appropriate number of additional announcement units of the required announcement type must be configured.

The attributes of an announcement are defined in a specific announcement type (= announcement name). Between 1 and 64 announcement units or tone sources can be combined to form a single announcement type. This is done by configuring the TMOM2 Q2214-X boards for synchronized announcement units (RAS), and assigning them to the same announcement type. Up to 64 announcement types can be configured, provided each announcement type is only assigned 1 announcement unit or tone source.

Synchronized announcements can only be connected in certain call processing situations. The situations are defined by the reasons for the announcements. Presently, the following announcements are configured:

hold-the-line announcement for call to an AC
announcement for calls to multiple paging equipment
announcement for calls to a hunting group call queue
announcement for calls to busy station for suffix dialing
announcement for calls to busy station with attendant intercept
announcement for calls to free station for suffix dialing
announcement for calls to free station with or without attendant intercept
announcement for calls to busy station with automatic camp on
announcement for DDI with incoming call from analog CO
announcement for internal caller if the call is forwarded to CO

Synchronized announcements are cross-LTG.

The attributes of an announcement type consist of:

Name:
- can be freely assigned
- up to 20 characters
Status:
- on or off.
Repeats:
- number of times the announcement cycle is to be repeated.
Linked announcements:
- announcement type to continue after completion of current announcement cycle.
Operating mode:
- Continuous or Start/Stop
Announcement delay timer:
- only applies if operating mode is Start/Stop. This value defines the delay time before the announcement is started, following seizure by the first caller.
Idle release limit:
- only applies if operating mode is Continuous. This value defines the number of times an announcement cycle is to be repeated under no-load conditions before the announcement unit is switched off.
Type of first internal tone:
- This tone type defines the tone which is to be applied at the end of the announcement text.
Duration of first internal tone:
- can be set as required
Status of first internal tone:
- on or off.
Type of second internal tone:
- This tone type defines the tone which is to be applied after the first internal tone, or, if no first internal tone is applied, at the end of the announcement text.
Duration of second internal tone:
- can be set as required
Status of second internal tone:
- on or off.
Type of third internal tone:
- This tone type defines the tone which is to be applied after the first or second internal tone. If a first or second internal tone is not applied, it defines the tone to be applied at the end of the announcement text.
Duration of third internal tone:
- can be set as required
Status of third internal tone:
- on or off.
A synchronized announcement will run until interrupted by an external action (call release or answer etc.), or until it terminates itself, depending on the announcement type attributes defined. In the latter case, a return tone (exit tone) is applied. This tone must be defined for each announcement reason.

The selection of a particular announcement type depending on the call progress situation/internal traffic restriction matrix is configured via AMO SYNCA, by means of an Announcement Reason / Announcement Type table.

Short announcements can be run in CONTINUOUS operating mode (i.e. looped). The waiting time for callers before the start of an announcement text can be bridged with the entry tone, which must be defined for each announcement type.

Longer announcements (from approx. 10 seconds onward) should be run in START/STOP mode, since callers would otherwise have to wait too long before hearing the start of an announcement text. However, this can only be done if the announcement unit has a start/stop input. In this mode, the system searches for an idle announcement unit assigned to the announcement type and starts playback.

Wait times may differ from case to case in the CONTINUOUS operating mode, and may even be as long as the announcement. However, you can minimize wait times in the START/STOP operating mode by connecting several announcement units and by selecting the correct announcement delay time in relation to the text length.

Use the following example to calculate the optimum size of the synchronized announcement with regard for the shortest wait time for text start by optimizing the announcement length.

The text length of the first active announcement unit must be covered by the result of the start delay time and the number of additional announcement units.

Ergo: Text length = start delay time multiplied by the number of announcement units.

Example:

Text length	::	40 sec
Start delay time	::	5 sec/10 sec/20 sec
Number of announcement units	::	8 / 4 / 2

In figures:

40 sec	=	5 sec multiplied by 8 or
		10 sec multiplied by 4 or
		20 sec multiplied by 2 or ...

The number of necessary announcement units in relation to the set delay time results from the following formula:

number of announcement units

text length / start delay time + 1

In figures:

Number of announcement units	=	40 sec /5 sec + 1 = 8 + 1 = 9 or
	=	40 sec / 10 sec + 1 = 4 + 1 = 5 or
	=	40 sec / 20 sec + 1 = 2 + 1 = 3 or ...

If this procedure is used

the maximum possible wait time for text start is always equal to the set start delay time.
the average wait time for text start is equal to half the maximum possible wait time.

The value combination you use depends on the number of announcement units you require (matter of costs) to reduce the wait times for text start to a justifiable value.

The delay timer is necessary in order to avoid having to start a separate announcement unit for each caller. This allows up to 50 callers to be connected to the same announcement unit, provided they all call within the start delay time. In this operating mode, if an idle announcement unit cannot be found for an announcement type, the system switches to CONTINUOUS mode until an announcement unit becomes idle again. This means that any caller(s) will have to wait for the beginning of the announcement text, i.e. despite START/STOP operation the wait times are irregular in length.

In this case, the system can output diagnosis advisory messages, in order to allow system owners to react to the problem by expanding the system if necessary. For this, bit 11 of the diagnosis bit string must be set with the aid of the DIAGS AMO. This information will enable you to reconfigure your system and to avoid the bottle neck.

If you wish to operate an announcement unit in asynchronous mode, you must set the new parameter ANOD in the COT of the TMOM board to which the announcement unit is connected. In this case, callers will be switched to an announcement unit without delay. This is useful if the announcement to be switched is a looped announcement, e.g. please hold the line with background music, where a start of text signal is not required.

For this type of operation (without start-of-text recognition), announcement units can also be connected to TMOM via the a/b wires only. The c- and d-wires must be bridged in order to avoid a line alarm. In addition, the new parameter AANT must be set in the COP of the TMOM lines.

COT parameter value = ANOD (asynchronous operation)
COP parameter value = AANT (connection via a/b wires only)

You must set the operating mode to START/STOP for this type of connection, since the TMOM circuit will otherwise not be released when required. (If you set the operating mode to CONTINUOUS, the TMOM circuit would normally be released when the release limit is reached. However, since no text repetitions can be defined, this is not possible).

For start and stop control via the TMOM board, the p-wire and j-wire can be additionally connected.

You can also install and operate the synchronized announcement for the application "wait announcement on the AC" in the CAC node. Installation in all originating nodes is therefore no longer necessary. Prerequisites are:

Set the COT parameters WAAN and ABPD for the tie line to the CAC node, even if the calling party in the originating switch is an analog trunk. The digit in last position in the CAC's attendant code (satellite PBX: AMO-NAVAR, last digit CD- CASEXT) is entered in the branch ANNMCI in the AMO-SYNCA. In addition, you must set the COT parameter ABNA, if the synchronized announcement in the CAC node is only to be started, when the attendant console is in night service.

You can operate a new announcement, if a digital trunk with external traffic performs automatic camp-on on a Digite, Anate or functional station. For this, configure and assign an announcement type for the new announcement reason "Announcement with automatic camp on".

You can operate a synchronized announcement for analog trunks with automatic camp-on on a Digite or Anate. The announcement is also activated for a transfer during camp on.

You can have different wait announcements at the AC for day and night operation. For this purpose, the additional announcement reason "Wait announcement on AC no answer with night service" (WANNDNS) was implemented for both local ACs and the CAC. With a CAC the TMOM connection and the CAC can be located in different nodes.

If no special administrative settings are made for night service, the day service settings also apply for night service.

You can also use the ITR of the night station to determine the announcement type for wait announcements at the AC during night operation if these were configured in the same node as the announcement unit.

Synchronized announcement can also be used for three applications, provided the calling device has the COS for synchronized announcement (COS=ANSYN) and is not an AC. Each of these three application cases must be released using AMO ZAND. If you want third-party systems to hear the synchronized announcement, set the COT parameter SANH in the incoming tie lie. The three possible application cases are:

no answer on AC (day and night service)
```
CHA-ZAND:TYPE=ATND,ISYNCAC=YES;
```
call to CSM (CSM with MEETME)
```
CHA-ZAND:TYPE=CCM,ISYNCCCM=YES;
```
call to a hunting group call queue.
```
CHA-ZAND:TYPE=ALLDATA2,ISYNCHG=YES;
```
Synchronized announcement can be remotely operated for
call to CSM (CSM with MEETME) and
call to a hunting group call queue

The announcement need therefore not be configured in the same node as the hunting group or the CSM. Instead, the announcement can be configured in the originating node for these application cases.

Any discrepancies within the network when setting the remote operation of the synchronized announcement can be avoided by setting the COT parameter TNDV (tone is injected from the station) for the outgoing digital tie trunk.

Remote operation of the synchronized announcement are generally prohibited for other applications (Announcement with station no answer), if this COT parameter is not set.

It is also possible to administrate up to 999 different station numbers between 1 and 6 digits as an alternative to the administration of the company index. Use the corresponding switch setting in AMO ZAND to select one of the two variants.

AMO ZAND: TYPE = ATND, COMP1000 = YES

IMPORTANT:

When you switch to 1000 company announcements for the first time, you must regenerate the existing data for the AC DAR.

You can also use the announcement for transfer purposes for the applications "Announcement with PSM" and "Announcement with camp-on". This option is also available for the application "Announcements for Hunting Group Call Queue". The position of the hunt group, the announcement unit or the transferring party in the network is not important.

You can also use the synchronized announcement for the individual night service (AMO ZAND: TYPE = ATND, INIGHT = YES) if you set a subscriber call number for the trunk as an individual night station (AMO TDCSU: INIGHT = nnnnn).

The announcement type determined in the originating node can be transported via the CAC traffic to the CAC node and used there for connection. Up until now, if the announcement unit was configured in the CAC node, the announcement type was also determined in this node. In certain applications, the relevant information was not available to determine the correct announcement type.

You cannot set a different entry tone or exit tone, however, with this procedure. The tone settings made in the CAC node for the announcement reason WANNAOHK or WANNDNS apply here.

If you want to use this procedure, follow the rules listed here:

Ensure that the announcement type information unit is consistent throughout the entire OpenScape4000/HiPath 4000 network.
Configure the synchronous announcement in all OpenScape 4000 nodes as if you wanted to operate the announcement locally. However, you only have to configure the TMOM2 board in the CAC node and assign the announcement type to the board (AMO TSCSU).
Set the COT parameter SATR for all trunks used to reach the CAC node from the originating node.

${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.