If the application does not run as expected, view the following log files from the /var/log/avaya/aes directory on the AE Services server:
dmcc-error.log.x
dmcc-api.log.x
dmcc-trace.log.x
dmcc-wrapper.log
Use the dmcc-error.log file to check for exceptions. The dmcc-error.log file is the latest log file.
The following table lists the sample application error messages and troubleshooting methods:
Application error message |
Troubleshooting procedure |
Registration failed because Gatekeeper Reject reason: terminalExcluded |
Verify that the extension number in tutorial.properties corresponds to an administered extension number on the Configuration Server web portal. |
Registration failed because Gatekeeper Reject reason: securityDenial |
Verify that the password in tutorial.properties matches the password administered on the Configuration Server web portal for the endpoint. |
Registration failed because Protocol Timeout reason: GRQ timer, tried 3 times |
Verify that the IP address in tutorial.properties for the media server is correct. Ping the media server from the AE Services server to test connectivity. |
Connection refused |
Verify that the IP address of the AE Services server is correct in the tutorial.properties file. Check for network problems between the client application computer and the AE Services server. For example, ping the AE Services server from the client application server. View the /etc/hosts files. Verify that you included a line that contains the IP address of the AE Services server and a localhost line. Verify that the cmapi1.server_port=4721 is listed in the tutorial.properties file. Verify that port 4721 is listening for incoming TCP connections. To view network status, use the netstat command on the AE Services server. |
