If the application does not run as expected:
View the following log files from /var/log/avaya/aes 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 exceptions. The dmcc-error.log file is the latest log file.
See the following table for resolving the application error messages.
Table 1: Troubleshooting error messages for the sample application
Application error message |
Troubleshooting procedure |
Registration failed because Gatekeeper Reject reason: terminalExcluded |
Verify that the extension number in tutorial.properties corresponds to a correctly administered extension number in Communication Manager. |
Registration failed because Gatekeeper Reject reason: securityDenial |
Verify that the password in tutorial.properties matches the password administered in Communication Manager for the station. |
Registration failed because Protocol Timeout reason: GRQ timer, tried 3 times |
Verify that the IP address in tutorial.properties for the call server (media server) is correct. Try to ping the media server from the AE Services server to verify 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 explicitly lists the IP address of the AE Services server, in addition to the localhost line. Verify that the cmapi1.server_port=4721 is listed in the tutorial.properties file. Further verify that port 4721 is listening for incoming TCP connections. Use netstat command on the AE Services server. |
