Product Guide - A5000 R5.4 – Aastra X series
BPS0121AENAA01
Page 53/74
5.3.9.3 Duplicating the integrated Call Distribution Service
The integrated Call Distribution function (integrated IVS, music on hold, spoken announcements) is
duplicated on AXD. In case of switchover, the function is only unavailable during the switchover, and
becomes available again thereafter without any manual intervention.
The Call Distribution service configuration and the associated voice recordings (music, spoken
announcements) are automatically updated on the passive motherboard each time the Call distribution
service is modified by the management centre, or after a new motherboard is added in the system( in
line with the answering service configuration).
Duplicating the IVR
The integrated interactive voice server function is duplicated on AXD.
In case of switchover, the function is only unavailable during the switchover, and becomes available
again thereafter without any manual intervention.
The IVR configuration and voice recordings are automatically updated on the passive motherboard
each time the call distribution service is modified by the management centre, or after a new
motherboard is added in the system (in line with the answering service configuration).
For an external IVS (an answering service application outside of the AXD) see the functional definition
of the application to find out the duplication level.
5.3.9.4 Duplicating the voice mail system
Integrated voicemail (IVB)
All messages left and also the voice signatures and customisable greeting messages are duplicated.
In case of a fault on the active motherboard, the service will restart on the passive board without loss
of messages.
External voicemail
If an external messaging system is used, see the product’s technical definition to find out the
application’s duplication level.
5.3.9.5 Duplicating the integrated billing services
Permanent connection: The function is secure.
If a billing tool is permanently connected to AXD, no ticket is lost if the motherboard of the gateway
fails, since the tickets are sent to the billing unit in real time. As soon as the motherboard takes over, it
sends the call tickets continuously.
If the billing unit or the link fails within a short period of time, the tickets are not saved in the buffer. In
such cases, the periodic connection should be preferably used.
Periodic connection: Duplication of tickets
The tickets are directly generated on both the motherboards. If a fault occurs on the active
motherboard, all tickets saved will be retrieved by the billing server (next connection) on the second
motherboard.