Loudspeaker paging

Last Updated : Feb 13, 2020 |
Prolog information
In CS 1000, paging is available as both part of the Park and Page operation and as a stand-alone feature. The Loudspeaker paging feature is commonly used for this service, but the Avaya Aura® service variant called Voice Paging is effectively identical to the paging on CS 1000.
  • CS 1000 endpoint user experience
    The CS 1000 paging description says:
    "The system provides switching access and trunk circuit interface to a customer-supplied speaker or radio paging equipment. Paging equipment is accessed by dial access or a Page key on attendant consoles. Telephones cannot be assigned a Page key and must dial access this feature."
    The paging service is configured to access a paging trunk card that is connected to the speakers or a trunk card that is connected to a radio distribution trunk. An administrator can provision a flexible feature code (FFC) to allow users to access the trunk route.
    To perform the paging, the user does the following:
    1. Goes off hook and enters the feature (FFC) code.
    2. Accesses the page trunk, makes the announcement, and then goes on hook.
    3. Attendant consoles may also use the paging key.
  • Communication Manager endpoint user experience
    The Loudspeaker Paging feature of Communication Manager is similar to the paging on CS 1000.
    Like CS 1000, Communication Manager offers other paging options, such as Park and Page. But, paging without an active call provides the same user experience as the paging on CS 1000. That is, the user accesses the paging system and makes an announcement.
    However,
    • Communication Manager uses Trunk Access Code (TAC) to access the paging resources. This has the same appearance as using the FFC and is identical to using the CS 1000 route access code to reach the paging trunk.
    • In addition, you can configure up to 9 paging zones. This requires up to 9 different ports (one port per zone) along with a TAC and class of restriction (COR) group per zone.
  • Device Adapter endpoint user experience
    Device Adapter does not support the analog trunk cards that were used on CS 1000 for paging. Instead, like Communication Manager, Device Adapter uses Loudspeaker Paging.
    In Device Adapter, you must provision the Avaya Aura® system with the Voice Paging configuration, and use the MM711 card to perform loudspeaker paging. For more information about configuring paging in Avaya Aura®, see the Communication Manager documentation.
    To perform the paging, the user does the following:
    1. Goes off hook and dials the TAC of the paging zone.
    2. Makes the announcement.
    3. Goes back on hook.
    Note:
    For a user experience similar to CS 1000, Avaya recommends that you configure the TAC to match the FFC that is used on CS 1000.
    For more information, see Loudspeaker paging in Appendix H: Call processing features and services.