Create an Announcement Server

Create an announcement server to specify details of an Interactive Voice Response (IVR) system on which to play announcements, such as the address of the IVR, and whether it is internal or external.

Procedure

  1. In Announcements, on the Servers tab, click New Server.
  2. In Create New Server:
    1. In Name, enter a unique name.
    2. (Optional) In Description, enter descriptive information about the item.
    3. (Optional) In External ID, enter any alphanumeric character to serve as a unique ID on this pricing object. The external ID can be used for any reason that is meaningful to your implementation of MATRIXX Engine. External IDs are saved to the pricing configuration file and loaded into the Pricing database.
    4. Click Create.
  3. In Edit Announcement Server, if required, change the general properties (the name, description, or external ID of the item) and click Save.
    Note: Any time you edit the value of a general property, you must click Save for your changes to take effect.
  4. To use the announcement server to perform announcements using the Diameter protocol, select the VolTE Server check box, and click Save to save your changes.
    A row for the new announcement server is displayed on the announcements Servers tab.
    Note: Configure only one VoLTE announcement server per pricing file.
  5. To use the announcement server to perform announcements using the Camel protocol:
    1. In Address Digits String, specify the address (up to 24 digits) of the announcement server.
    2. In Both Way Through Connection, select how to set the bothwayThroughConnectionInd parameter in EstablishTemporaryConnection (ETC) and ConnectToResource (CTR) operations. One of:
      • Not Set — The bothwayThroughConnectionInd parameter is not sent in ETC and CTR operations.
      • Both Way Path Required — Enables the sound path between the caller and the announcement server in both directions.

        When Both Way Through Connection is either Not Set or set to Both Way Path Required, you can assign an announcement prompt collect definition to PostRating profiles that use this announcement server so that digits can be collected from the caller during announcements.

      • Both Way Path Not Required — Disables the sound path from the caller to the announcement server. You cannot assign an announcement prompt collect to PostRating profiles using this announcement server.
      Note: During engine configuration, when configuring a voice service, MATRIXX Support recommends that you accept the default value of Not set for the bothwayThroughConnectionInd parameter. If set, the voice service configuration for the bothwayThroughConnectionInd parameter overrides the announcement server pricing configuration, which could lead to errors being reported. For more information about voice service configuration, see MATRIXX Call Control Framework Integration.
  6. (Optional) If the announcement server is external, select the External Server check box. Leave unchecked if the server is internal.
  7. If you selected External Server, configure the following external server details:
    1. (Optional) To include the correlation ID for announcement requests in the announcement server address, select the Correlation ID in Address check box.
    2. In Numbering Plan, select the numbering plan to use.
    3. In Nature of Address, select the nature of address value to use.
    4. (Optional) To set the correlation ID length for the announcement server, in Correlation ID Length, enter the number of digits to use. The value must be in the range: 4 to 255.
      The Correlation ID Length value overrides the correlation ID length configured for the voice service in create_config.info. The correlation ID length is 10 by default.
    5. In Send Extra ConnectToResource to External Server, select whether to send an extra CTR operation to the external announcement server, in a separate TCAP CONTINUE message, before the first Play Announcement or PACUI operation. Select one of:
      • Do not send — (Default). Do not send an extra CTR.
      • Without Both Way Through Connection — Send an extra CTR with the bothwayThroughConnectionInd parameter not set.
      • Both Way Path Required — Send an extra CTR with the bothwayThroughConnectionInd parameter set to 0 (bothwayPathRequired).
      • Both Way Path Not Required — Send an extra CTR with the bothwayThroughConnectionInd parameter set to 1 (bothwayPathNotRequired).
      Note: Sending CTR before the first PlayAnnouncement or PACUI (prompt and collect) operation is non-standard functionality that is not supported by most external IVRs.
    6. (Optional) In Default SCF ID, specify the default SCF ID, or leave undefined. If specified, the SCF ID must contain only hexadecimal characters in the range 0–9, A-F. If you leave Correlation ID in Address unselected, you must enter an even number of characters.
    7. (Optional) To specify to use a different SCF ID per engine ID, click Add Mapping and enter the Engine ID to SCF ID mappings in the relevant columns. SCF IDs must contain only hexadecimal characters in the range 0–9, A-F. If you leave Correlation ID in Address unselected, each SCF ID must contain an even number of characters.
  8. Click Save.