Configuring Communication Manager to integrate Application Enablement Services with Presence Services

Last Updated : Oct 28, 2022 |
Prolog information
Metadata
Keywords:
  1. Log in to Communication Manager by using Putty.
  2. Run the change node-names IP command and do the following on the change node-names IP page:
    1. In Name, type a name for the Application Enablement Services IP node.
    2. In IP Address, type the IP address of the Application Enablement Services server.
    3. Save the changes.
  3. Run the change system-parameters customer-options command and do the following on the change system -parameters customer-options page:
    1. In Computer Telephony Adjunct Links, type y.
    2. Save the changes.
  4. Run the add cti-link <x> command, where <x> is the CTI link number that is not assigned anywhere else in Communication Manager. Do the following on the change cti-link <x> page:
    1. In Extension, type an extension number that complies with the numbering plan and is not assigned anywhere else in Communication Manager.
    2. In Type, type ADJ-IP.
    3. In Name, type a name for the Application Enablement Services link. For example, Link_To_Aes130.
    4. Save the changes.
  5. Run the change ip-services command and do the following on the change ip-services page:
    1. In Service Type, type AESVCS.
    2. In Enabled, type y.
    3. In Local Node, type procr or clan depending on what is configured for your setup.
    4. In Local port, type 8765.
    5. In AE Services Server, type the hostname of the primary Application Enablement Services server.
    6. In Password, type the password of the Application Enablement Services switch connection.
      ADDITIONAL INFORMATION:
      Note:
      The Application Enablement Services switch connection password must have 12 characters and must match the password that is configured on the Application Enablement Services server for the Application Enablement Services switch connection.
    7. In Enabled, type y.
    8. Save the changes.
  6. To generate the universal call ID (UCID) and send it over the Adjunct Switch Application Interface (ASAI) protocol, run the change system-parameters features command and do the following on the change system-parameters features page:
    1. In Create Universal Call ID (UCID), type y.
    2. In UCID Network Node ID, type an identity number for the UCID network node.
      ADDITIONAL INFORMATION:
      This value must be unique within the network.
    3. In Send UCID to ASAI?, type y.
    4. Save the changes.
  7. Run the change signaling-group <n> command, where <n> is the signaling group number that is configured in the trunk group.
    ADDITIONAL INFORMATION:
    This trunk group is configured in the route pattern of the AAR digit analysis table. This AAR digit analysis table contains the first digits of the extension numbers.
    Do the following on the change signaling-group <n> page:
    1. In IMS Enabled, type n.
  8. Run the save translation all command to save the changes.
  9. To perform automatic alternate routing (AAR) analysis, run the change aar analysis <n> command, where <n> is the first digit of the extension number. Do the following on the change aar analysis <n> page:
    1. If the numbering format at trunk is set to private, in Call Type, type lev0, lev1, or lev2 depending on the network level configuration for the route pattern.
  10. Run the status aesvcs cti-link command to verify the status of TSAPI link.
Related links
Application Enablement Services Collector