The system allows calls that are either queuing or alerting, to hear announcements. When the system plays an announcement, the current state of the call changes to Connected Announcement . The call remains in that state until either answered or cleared. System Status displays the type of announcement and details of the queued or alerting parties.

Example:

1. Call 37 is alerting at two extensions, as well as listening to Announcement 2 for the hunt group 'just two'.
2. Call 38 is queuing for the hunt group 'just two', as well as listening to Announcement 2 for the hunt group 'just two'.
3. Call 39 is queuing for the hunt group 'just two'.

The following trace shows the same call sequence, traced from the trunk from which the call originated:

IP Office supports both synchronous and asynchronous announcements. The examples in this section are typical of asynchronous announcements. For synchronous announcements, IP Office sets up a call between voicemail and a multicasting point. Each call that is listening to the same announcement connects to the same multicasting point.

The multicasting call is set up as soon as there is a call that will require it, even if it is not yet time to play the announcement. A multicasting call that is currently playing an announcement will show the announcement details and a state of 'Connected'. A multicasting call that is waiting to play an announcement will show the announcement details and a state of 'Waiting Announcement'.

The trace of a call hearing an announcement indicates the call reference of the multicasting call.

Example:

1. Call 47 is the multicasting call for Announcement 1 of the hunt group 'just one'. This announcement is being played on call 49, which is queuing for hunt group 'just one'.
2. Call 49 is the multicasting call for Announcement 2 of the hunt group 'just two'. It has been created in readiness to play to call 45. Call 45 is alerting at two extensions. Announcement 1 of the hunt group 'just one' has already been played to it and it is waiting for Announcement 2 to begin.

The following trace shows the same call sequence, traced from the trunk from which the calls originated: