Verifying communication between the Experience Portal server and the external systems

Last Updated : Jun 23, 2021 |
Prolog information
Metadata
Keywords:
The planned Experience Portal server must have a static IP address and hostname, and it must be able to communicate with the external systems using either:
  • A Domain Name Server (DNS) to translate hostnames to their corresponding IP addresses
  • The /etc/hosts file to map the IP addresses and hostnames
Note:
Avaya is responsible only for the systems Avaya provides. External systems are the customers' responsibility.
  1. On the Experience Portal server, log in to Linux as any user.
  2. Verify the primary EPM server's IP address and hostname:
    1. Enter the hostname -i command.
      STEP RESULT:
      This command should return the server’s IP address and not 127.0.0.1. If this check fails, you need to manually map the hostnames as described in If both these checks fails, you need to manually map the hostnames as described in Implementing Avaya Experience Portal on multiple servers on http://support.avaya.com.
    2. Enter the hostname -s command.
      STEP RESULT:
      This command should return the server’s hostname and not localhost. If both these checks fails, you need to manually map the hostnames as described in Implementing Avaya Experience Portal on multiple servers on http://support.avaya.com.
  3. Verify that the EPM server can communicate with all the external servers:
    1. Enter the ping -c 4 <server_hostname> command, where:
      ADDITIONAL INFORMATION:
      <server_hostname> is the hostname of the one of the following external components attached to your Experience Portal system:
      • A PBX server.
      • An application server.
      • A speech server.
      • Communication Manager.
      • Avaya Aura® Session Manager.
    2. Wait for the system to respond with the contact information.
    3. If this check fails, enter the ping -c 4 <server_ipaddress> command, where:
      ADDITIONAL INFORMATION:
      <server_ipaddress> is the IP address of the server whose hostname you specified in the previous ping command.
    4. Wait for the system to respond with the contact information.
    5. If both these checks fails, you need to manually map the hostnames as described in Implementing Avaya Experience Portal on multiple servers on http://support.avaya.com.
    6. Repeat this procedure for each external server in your Experience Portal system.