Maintenance test for Call Processing status fails

Last Updated : Nov 30, 2017 |

The maintenance test for Call Processing status might fail because of the following reasons:

  • PfA is not deployed.

  • Configuration errors while installing or upgrading the Avaya Breeze® platform server.

  • WebSphere or Secmod is not running.

Solution

Procedure

  1. Establish an SSH session with the Avaya Breeze® platform server.
  2. If the maintenance test fails after installing or upgrading the Avaya Breeze® platform server, verify the AvayaNetSetup logs for configuration-related errors.

    The AvayaNetSetup logs are located at:

    • Configuration information: /var/log/Avaya/SMnetSetup.log

    • Installation summary: /var/log/Avaya/install-summary.log

    • Upgrade summary: /var/log/Avaya/asm-install.log

  3. Verify the status of the WebSphere and Secmod applications using the following command: statapp
  4. If the status of the WebSphere or Secmod application is DOWN, start the service using the following command: restart <app name>
  5. Check if PfA and the platformApp are deployed using the following command: deploy_service -cb.

    Avaya Breeze® platform displays the activity count of the services in the following format:

    0 0 0 pfa
0 0 0 platformApp
  6. If the troubleshooting steps fail to solve the problem, perform the configuration update procedure without changing the values using the following command: AvayaNetSetup
  7. If performing the configuration update procedure fails to resolve the problem, download the ISO and run the following command: upgradeCE <iso-file>
Related information
Avaya Breeze platform troubleshooting