Explanation | No logging will occur due to the unhandled event. |
Action | Make sure the specified log file name(s) are valid and accessible. |
Explanation | The SipClusterSelectorRequestFilter filter failed to be initialized from the ProxyConfig. |
Action | Make sure that the configuration for cluster routing rules is correct. |
Explanation | The SipClusterSelectorRequestFilter filter has a possible configration problem. |
Action | Make sure that the configuration for cluster routing rules is correct. |
Explanation | There are no available servers in the cluster. |
Action | Make sure that there are servers in the cluster running. |
Explanation | The partition id is not available in the available clusters. |
Action | None. |
Explanation | An non valid Session Initiation Protocol (SIP) message was received. The message is missing a required header. |
Action | None. |
Explanation | Configuration error, the SipViaHeaderRequestFilter is unable to retrieve the configuration information. |
Action | None. |
Explanation | The topmost VIA header in the Session Initiation Protocol (SIP) response message is not valid. |
Action | None. |
Explanation | The address in the VIA header is not valid. |
Action | None. |
Explanation | There are no available servers in the cluster. |
Action | Make sure that there are servers in the cluster running. |
Explanation | The partition id is not available in the available clusters. |
Action | None |
Explanation | The proxy determined that a server has went down in a cluster that the proxy was using. |
Action | None |
Explanation | The proxy determined that a server has been started in a cluster that the proxy is using. |
Action | None |
Explanation | The proxy determined that a partition has been added to a server. |
Action | None |
Explanation | The proxy determined that a partition has been removed from a server. |
Action | None |
Explanation | The server that was selected, was overloaded. |
Action | Check the server logs to see what caused the server to be overloaded. |
Explanation | The server that was selected, was overloaded. |
Action | Check the server logs to see what caused the server to be overloaded. |
Explanation | The server that was overloaded is now not overloaded. |
Action | None |
Explanation | This is the Maximum Messages per Averaging Interval for this server instance. |
Action | None |
Explanation | A Custom property has overridden a server configuration property. |
Action | Administrator should check configuration to ensure it is configured correctly. |
Explanation | This is the Maximum Messages per Averaging Interval for this server instance. |
Action | None |
Explanation | This is the Maximum Messages per Averaging Interval for this server instance. |
Action | None |
Explanation | The server that was selected, was overloaded. |
Action | None |
Explanation | The server that was selected, was overloaded. |
Action | None |
Explanation | This server is not responding to Session Initiation Protocol (SIP) heartbeats. |
Action | Check the server logs to see if the server is up. |
Explanation | This server is now responding to Session Initiation Protocol (SIP) heartbeats. |
Action | None |
Explanation | The Proxy is successfully responding to load balancer inquiries. |
Action | None |
Explanation | The SIP logic in the control region is attempting to notify the container to to start the failover process. However, the container is not responding. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A SIP Container has failed. The SIP logic in the control region attempted to notify an existing container to handle the failover, but containers are not running. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A SIP Container has registered a new logical server name. The SIP logic in the control region will add that name to its load balancing list. |
Action | No action is required. |
Explanation | A SIP Container is unregistering a logical server name. The SIP Router will remove the name from its load balancing list. |
Action | No action is required. |
Explanation | The Session Initiation Protocol (SIP) logic in the control region detected a new SIP proxy in the cluster, and SIP network outage detection is enabled. |
Action | No action is required |
Explanation | The SIP logic in the control region has not received heartbeat messages from the front-end proxy within the pre-configured timeout value. |
Action | Verify that the SIP proxy is still running, and the SIP network line between the proxy and the container is in order. |
Explanation | The SIP container attempted to restart itself as a result of network outage, but this action failed. |
Action | Please restart the application server manually. |
Explanation | The SIP logic in the control region has lost touch with all front-end proxies in the cluster. It is now restarting itself. Active sessions will migrate to a backup container, if one is present in the replication domain. |
Action | Determine the cause for SIP network outage. Focus on the network line between the proxy and the application server. You can use a network sniffer to trace the SIP KEEPALIVE messages between the proxy and the container. |
Explanation | The SIP Proxy startup delay is used to allow for the replication of all data from all the configured clusters before processing of any messages. |
Action | None. |
Explanation | The SIP Proxy startup delay is completed and is now processing SIP messages. |
Action | None. |
Explanation | The SIP Proxy recieved notification that the server has started its quiesce sequence. |
Action | No action is required |
Explanation | The SIP Proxy recieved notification that the server has gone from being quiesced to active. |
Action | No action is required |
Explanation | The SIP Proxy received a message from the Load Balancer. |
Action | No action is required |
Explanation | The SIP Proxy has not received a message from the Load Balancer recently. |
Action | No action is required |