Errors
Errors displayed in the log file should provide some indication of what the problem is and where to start looking to fix the errors. The following are example errors and troubleshooting steps:
- In the following error, the endpoint failed to receive the notification because “there was no endpoint listening” at the address specified. To troubleshoot this error, start by ensuring that the Notifier is communicating with Revolution and Call Manager. Then verify that the endpoint is listed as Registered and was pulled in by the Notifier. From there troubleshooting might get more specific based on the answers to those questions.23 Mar 2017 17:57:10 ERROR [17] SAAnnounceRevolution.NotificationHandlerBlast.CheckFor75PercentResponse [(null)] : Failed to obtain ActivationResult from BlastNotifier Notifier System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://192.168.10.101:8008/SAAnnounceSDK/BlastNotifier/SAAnnounceSDK that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.10.101:8008.
- The Notifier is currently inactive. If you check theSAAnnounceLog.txtfile in this scenario, you cannot see a heartbeat from BlastNotifier to Revolution, meaning they are not communicating. To troubleshoot this error, start by getting the Notifier to communicate with Revolution.23 Mar 2017 18:19:05 WARN [8] SAAnnounceRevolution.NotificationHandler.SendCommandToken [(null)] : Could not send notification to notifier: BlastNotifier because the Notifier is NOT active.