Collapse AllExpand All

13.3.4.1. General Requirements: Previous topic Parent topic Child topic Next topic

  • Is the system feature "Synchronous Announcements" enabled (FEASU: SYNCANN)?
  • Is the "Synchronous Announcements" feature activated in the central system data (ZAND: ALLDATA2, ANSES =Y)?
  • Has the internal application for "No answer on AC", for "Call to CSM" and for "Call to hunting group call queue" been enabled using AMO ZAND?
  • Is a sufficient number of announcement buffers assigned (DIMSU: SYNAN)?
    50 announcement buffers must be assigned per announcement unit (max. 64 announcement units).
  • Have the necessary announcement types been defined, and assigned to the appropriate TMOM2 boards (TSCSU)
  • Have the announcement types been activated, i.e. set to "ON" status? (SYNCA) - if ANSTATE parameter of AMO SYNCA is not specified during first configuration (ADD-SYNCA), then the default value is set: ANSTATE=OFF.
  • Are you sure that the appropriate incoming direct exchange traffic or tie-traffic is being received?
  • Are the TMOM2 connections compatible with the device type used?
    Genius ST and MUSIFONE 5000 S have different interfaces.
  • If you are running the announcements in START/STOP mode, have you set the start delay timer value appropriately? (SYNCA)
  • Have you defined an entry tone and a return tone for the appropriate announcement reasons? (SYNCA)
  • Announcement reason/announcement type table (ANNMITR/ANNMCI)
    If the announcement type is to be used independently of an ITR value or the last dialed digit, the announcement type must be explicitly entered into the table for all ITR values and all last digits.
  • Has the COT parameter ABPD (answering before suffix-dialing or announcement) for the digital exchange trunks been set?
    This COT parameter is mandatory for digital exchange lines, since the exchange will otherwise not receive the necessary criterion for switching through the call, i.e. the caller will not be able to hear the announcement.
    For analog exchange lines, this parameter is not checked. However, it must still be assigned if the exchange requires an answering criterion before switching through the connection.
    The same applies for incoming exchange traffic via transit lines, i.e. the COT parameter is not checked for the transit line. The parameter must be set if the calling exchange in the originating node requires an answering criterion before switching through the connection.
    If the parameter is set, call charge pulses are signaled immediately the announcement is started.
    Have the 2 timers WFIRST and WNEXT of the device handler of the TMOM2 been set to the appropriate values? (DTIM1)
    WFIRST defines the wait time for the first start of the announcement after connecting to the announcement unit. In START/STOP operation, this value can be kept small (1 - 4 sec.). If the announcement is run in CONTINUOUS mode, the value must be greater than the length of the announcement. If this timer runs down, a line alarm is set for the TMOM board. In this case, you must check the JP interface cables.
    WNEXT defines the wait time for the next start of the announcement following the first start. This value must always be set to a longer value than the announcement length. If timer runs down a line alarm is also set.
  • If the diagnosis bit is set, call processing errors while attempting to access the announcement unit are output by means of advisory messages
  • (DIAGS: CC, CP, S06=Y).
  • If a fault occurs, the error message F4066 CP ADVISORY is output for diagnostic purposes.
  • With remote parties: Has the COT parameter TNDV (tone injected from terminal) been set for the digital tie trunk (EV 3.0 and higher)?
  • With internal parties (calling party is terminal): Has the COS (ANSYN) been set for the terminal (from EV3.0)?
  • No synchronized announcement is injected after a call transfer (e.g. to CCM), although the transferring party heard the announcement before transfer.
    This can happened under the following circumstances:
    • The announcement type of the synchronized announcement is in START/STOP operating mode.
    • Only one announcement unit is assigned to this announcement type
    • The transferring terminal was the only device connected with the synchronized announcement.
    In this constellation the announcement unit is released during the transfer procedure and needs several seconds to become operable again. Therefore, for the transferred station there is no seizable announcement unit available at the time of transfer (from EV 3.0).
    Solution: Assign a second announcement unit to this announcement type.
    Set the operating mode of the announcement type to CONT.