Explanation | The SIP container is up and ready to receive messages from the network. |
Action | This is an informational message. No user action is necessary. |
Explanation | Version number of the SIP container component. |
Action | This is an informational message. No user action is necessary. |
Explanation | SIP Container MBean unable to start. JMX operations will not be available for the SIP Container. |
Action | No action is required. |
Explanation | An exception was caught by the SIP container. |
Action | No action is required. |
Explanation | One of the servers in the cluster has terminated, and some of its logical names are transferred to this server. The session objects associated with these logical names are now being activated on this server. |
Action | No action is required. |
Explanation | Finished activation of session objects that are associated with a logical name. See "Failover started" for the logical name and the number of objects. |
Action | No action is required. |
Explanation | An error has occurred while trying to initialize the XML parser. This does not indicate an error in the sip.xml document. |
Action | No action is required. |
Explanation | The SIP container cannot load an application from the sip.xml file because there is no XML parser. |
Action | Look for an earlier error message in the log that reads "Error configuring sip.xml parser". |
Explanation | The SIP container cannot load an application from the sip.xml file because of an error in the sip.xml document. |
Action | Check for errors in the sip.xml file. You can find information about the standard sip.xml format in JSR 116 (SIP Servlet API) chapters 11 (Mapping Requests to Servlets) and 15 (Deployment Descriptor). |
Explanation | The class loader could not find the listener class. |
Action | Check your sip.xml and verify that the listener class name is correct. Make sure the listener class is included in the class path. |
Explanation | The SIP container could not instantiate the listener class. |
Action | Check your sip.xml and verify that the listener class name is correct. Make sure the listener class has a public constructor that expects no arguments. |
Explanation | The sip.xml document defines more than one TimerListener for the same application. |
Action | Check your sip.xml and make sure there is only one TimerListener class for the application. |
Explanation | The sip.xml document contains an invalid application session timeout value. |
Action | Check your sip.xml to make sure the session-timeout setting is expressed in whole number of minutes. |
Explanation | The sip.xml document contains a servlet mapping for an undefined servlet |
Action | Check your sip.xml and make sure that all servlet-name tags under servlet-mapping correspond to an existing servlet, and make sure there is a pattern definition for the servlet mapping. |
Explanation | The sip.xml document contains an invalid type of servlet matching condition. |
Action | Check your sip.xml to make sure the matching rules are compliant with JSR 116 (SIP Servlet API) 11.3 (Conditions). |
Explanation | The sip.xml document contains an invalid servlet matching rule. |
Action | Check your sip.xml to make sure the matching rules are compliant with JSR 116 (SIP Servlet API) chapter 11 (Mapping Requests to Servlets). |
Explanation | The sip.xml document contains an AND condition with no sub elements. |
Action | Check your sip.xml to make sure there are matching rules under the AND tag. |
Explanation | The sip.xml document contains zero or multiple sip-app sections. There may only be one. |
Action | Check your sip.xml to make sure there is exactly one sip-app section. |
Explanation | There is no local definition for /javax/servlet/sip/sip-app_1_0.dtd |
Action | No action is required. |
Explanation | The SIP container is no longer considered overloaded, and is now ready to handle new sessions |
Action | No action is required. |
Explanation | The server weight was changed, due to a change in SIP activity |
Action | No action is required. |
Explanation | The internal SIP stack failed to initialize. |
Action | No action is required. |
Explanation | An exception was caught in the SIP stack layer. The stack will attempt to continue running normally. |
Action | No action is required. |
Explanation | This is an informational message printed for each host address, port number, and transport protocol, that the SIP container listens to, for incoming SIP traffic. |
Action | No action is required. |
Explanation | The SIP container failed to forward a SIP message. |
Action | No action is required. |
Explanation | The SIP container, acting as a proxy, failed to forward a request to one of the destinations. |
Action | No action is required. |
Explanation | The SIP container, acting as a proxy, failed to create a Record-Route header. |
Action | No action is required. |
Explanation | The SIP servlet code called Proxy.setParallel() after calling Proxy.proxyTo() |
Action | Change the application code so Proxy.setParallel() is not called after Proxy.proxyTo() |
Explanation | The SIP servlet code called Proxy.setRecurse() on a stateless Proxy. |
Action | Change the application code so it doesn't call Proxy.setRecurse() on a stateless Proxy. |
Explanation | The SIP servlet code called Proxy.setStateful() after calling Proxy.proxyTo() |
Action | Change the application code so Proxy.setStateful() is not called after Proxy.proxyTo() |
Explanation | The SIP container failed sending out a CANCEL request. |
Action | No action is required. |
Explanation | The SIP container failed to send a response upstream (upstream is the direction that responses flow from the UAS back to the UAC) |
Action | No action is required. |
Explanation | The SIP servlet code called Proxy.setRecordRoute() after calling Proxy.proxyTo() |
Action | Change the application code so Proxy.setRecordRoute() is not called after Proxy.proxyTo() |
Explanation | The SIP container failed creating a SIP request message. |
Action | No action is required. |
Explanation | The SIP container failed getting a Route header in a request. |
Action | No action is required. |
Explanation | Failed resolving an internet address from host name to IP address. |
Action | No action is required. |
Explanation | The SIP servlet code called Proxy.setRecordRoute() on a request that does not create a dialog. |
Action | Change the application code so it doesn't call Proxy.setRecordRoute() on requests that don't create a dialog. Examples of requests that do create dialogs are INVITE, REFER, and SUBSCRIBE. |
Explanation | The SIP container received a message where it does not expect it. |
Action | No action is required. |
Explanation | The SIP container cannot proxy a subsequent request on a dialog, because the incoming request has no Route header. |
Action | No action is required. |
Explanation | The SIP container cannot process a message because the URI is not a sip or sips URI. |
Action | No action is required. |
Explanation | The SIP container received a request on a dialog from a strict router, and the session ID parameter in the Request-URI was missing, or had the wrong value. |
Action | No action is required. |
Explanation | The SIP container failed to send out a response. |
Action | No action is required. |
Explanation | There is no matching SIP servlet for handling a request. |
Action | Check the matching rules of the installed SIP applications and make sure that at least one of them can be matched to the request. |
Explanation | The SIP container received a BYE request that is not matched to any existing dialog. |
Action | No action is required. |
Explanation | The sip.xml document contains an invalid variable. |
Action | Check your sip.xml to make sure the variable is valid according to JSR 116 (SIP Servlet API) 11.2 (SIP Request Object Model) |
Explanation | The sip.xml document contains a condition with no sub-elements. |
Action | Check your sip.xml to make sure that pattern matching is valid according to JSR 116 (SIP Servlet API) 11.3 (Conditions). |
Explanation | The SIP container failed to parse the list of trusted IP addresses from configuration. |
Action | Check the configuration property com.ibm.ws.sip.security.trusted.iplist |
Explanation | The list of trusted IP addresses for SIP authentication contains a host name that fails to resolve. |
Action | Check the list of trusted IP addresses in the configuration property com.ibm.ws.sip.security.trusted.iplist |
Explanation | The SIP container failed to parse a Via header for IP authentication. |
Action | No action is required. |
Explanation | The SIP container failed to find a Via header in the message for IP authentication. |
Action | No action is required. |
Explanation | The application call to Address.setExpires() failed because the message's address header contains a malformed expires parameter value. |
Action | No action is required. |
Explanation | The application call to Address.setDisplayName() failed. |
Action | Check the application code to make sure the display name is valid and not null. |
Explanation | The application call to Address.setExpires() failed. |
Action | No action is required. |
Explanation | The application call to Address.setParameter() or SipURI.setParameter() failed. |
Action | Check the application code to make sure the parameter's name and value are valid. |
Explanation | The application call to Address.setQ() failed. |
Action | Check the application code to make sure the priority value is valid. |
Explanation | The application call to SipServletMessage.getMethod() failed. |
Action | No action is required. |
Explanation | The application call to SipServletRequest.getRequestURI() failed. |
Action | No action is required. |
Explanation | The SIP container failed to create a response to the request. |
Action | No action is required. |
Explanation | The SIP container failed sending out a request. |
Action | No action is required. |
Explanation | The SIP container failed to add a header to the message. |
Action | No action is required. |
Explanation | An error occurred while the SIP container was trying to send out a response. |
Action | No action is required. |
Explanation | The SIP container failed to set a header value in the message. |
Action | No action is required. |
Explanation | The application call to SipURI.setHost() failed. |
Action | Check the application code to make sure the host name is valid and not null. |
Explanation | The application call to SipURI.setPort() failed. |
Action | No action is required. |
Explanation | The application call to SipURI.setSecure() failed. |
Action | No action is required. |
Explanation | The application call to SipURI.setUser() failed. |
Action | Check the application code to make sure the user name is valid and not null. |
Explanation | The application call to SipURI.setUserPassword() failed. |
Action | Check the application code to make sure the user password is valid and not null. |
Explanation | The application call to SipServletMessage.getAcceptLanguage() failed. |
Action | No action is required. |
Explanation | The application call to SipServletMessage.getAcceptLanguages() failed. |
Action | No action is required. |
Explanation | The application call to SipServletMessage.getAddressHeader() failed. |
Action | No action is required. |
Explanation | The application call to SipServletMessage.getAddressHeaders() failed. |
Action | No action is required. |
Explanation | The application call to SipServletMessage.getCharacterEncoding() failed. |
Action | No action is required. |
Explanation | The application call to SipServletMessage.getContentLength() failed. |
Action | No action is required. |
Explanation | The application call to SipServletMessage.getContentType() failed. |
Action | No action is required. |
Explanation | The application call to SipServletMessage.getHeader() failed. |
Action | No action is required. |
Explanation | The application call to SipServletMessage.getHeaderNames() failed. |
Action | No action is required. |
Explanation | The application call to SipServletMessage.getHeaders() failed. |
Action | No action is required. |
Explanation | The application call to SipServletMessage.setContent() failed. |
Action | Check the application code to make sure the message content is valid and not null. |
Explanation | The application call to SipServletMessage.getViaHeaders() failed. |
Action | No action is required. |
Explanation | The application call to SipServletMessage.getContactHeader() failed. |
Action | No action is required. |
Explanation | The SIP container failed getting one or more headers from the internal JAIN message object. |
Action | No action is required. |
Explanation | The application call to SipServletRequest.getMaxForwards() failed. |
Action | No action is required. |
Explanation | The application call to SipServletResponse.getReasonPhrase() failed. |
Action | No action is required. |
Explanation | The application call to SipServletResponse.getStatus() failed. |
Action | No action is required. |
Explanation | The application call to SipServletResponse.setStatus() failed. |
Action | Check the application code to make sure the status code is valid. If you also supplied a reason phrase, make sure it is not null and not empty. |
Explanation | The application call to SipFactory.createAddress() failed. |
Action | Check the application code to make sure the URI and display name are valid. |
Explanation | The application call to SipFactory.createSipURI() failed. |
Action | Check the application code to make sure the user and host parameters are valid and not null. |
Explanation | The application call to SipFactory.createURI() failed. |
Action | Check the application code to make sure the URI string represents a valid URI. |
Explanation | The application call to SipServletRequest.pushRoute() or SipServletRequest.pushRecordRoute() failed. |
Action | Check the application code to make sure the SipURI is valid. |
Explanation | The application call to Address.setURI() failed. |
Action | Check the application code to make sure the URI is valid. |
Explanation | The SIP container failed to send out an ACK request. |
Action | No action is required. |
Explanation | The SIP container failed to send out a CANCEL request. |
Action | No action is required. |
Explanation | A request that was sent out from the SIP container was not responded for 32 seconds, and the SIP container failed to generate a timeout response to the application. |
Action | No action is required. |
Explanation | Internal error in the SIP container cloning an Address object. |
Action | No action is required. |
Explanation | The SIP container failed to create a tel URL. |
Action | Check that the raw URL string is at least 4 bytes long (3 for the scheme plus 1 for the colon character). |
Explanation | While canceling a request, the SIP container failed sending the 487 (Request Terminated) response to the original request. |
Action | No action is required. |
Explanation | The application call to SipServletMessage.setCharacterEncoding() failed. |
Action | Check the application code to make sure the encoding parameter is valid and not null. |
Explanation | The application call to Address.setTag() failed. |
Action | Check the application code to make sure the tag parameter is valid. |
Explanation | The logger for SIP session/dialog sequence is enabled. |
Action | No action is required. |
Explanation | |
Action | No action is required. |
Explanation | The SIP container is not running as a Websphere service. |
Action | No action is required. |
Explanation | The SIP container failed loading or instantiating a SIP servlet class. |
Action | Check your sip.xml to make sure the class name is correct and has a public constructor that expects no arguments. |
Explanation | An exception was thrown by the SIP servlet code. |
Action | No action is required. |
Explanation | The SIP servlet does not exist. |
Action | Check your sip.xml to make sure the servlet class name is correct. |
Explanation | Error initializing the SIP container; additional details can be found in trace file. |
Action | Enable diagnostic tracing for the SIP container, restart the server to recreate the problem, and then pull the trace log. |
Explanation | The SIP servlet timer was triggered, but no listener is associated with it. |
Action | No action is required. |
Explanation | All timers are disabled in the SIP container |
Action | Check the SIP container configuration and remove the "enable.timers" property, or set its value to "true". |
Explanation | The SIP transaction is already initialized with a transaction ID, and cannot be changed. |
Action | No action is required. |
Explanation | An exception was thrown while the SIP container tried to invoke a request. |
Action | No action is required. |
Explanation | The SIP container failed to send out the response from within the call to prepareHeadersForWrite(). |
Action | No action is required. |
Explanation | The SIP container cannot dispatch a message because the previous message dispatching has not completed yet. |
Action | No action is required. |
Explanation | The SIP container received a request from the web container that is not a javax.servlet.http.HttpServletRequest. |
Action | No action is required. |
Explanation | The SIP container failed to register itself as a listener to Websphere. |
Action | No action is required. |
Explanation | The cache algorithm requested by the SIP container session manager does not exist. |
Action | No action is required. |
Explanation | Replication exception caught by the SIP container session manager. |
Action | No action is required. |
Explanation | The SIP container high availability component initialized. |
Action | No action is required. |
Explanation | The SIP container caught an exception of type ClassNotFoundException during object serialization. |
Action | No action is required. |
Explanation | The SIP container caught an exception of type IOException during object serialization. |
Action | No action is required. |
Explanation | Exception caught in the SIP container during DRS replication. |
Action | No action is required. |
Explanation | Exception caught in the SIP container while activating the MBean for the session manager. |
Action | No action is required. |
Explanation | Exception caught in the SIP container using the DRS multi broker. |
Action | No action is required. |
Explanation | The DRS mode is not suitable for data replication in the SIP container. |
Action | No action is required. |
Explanation | Replication in the SIP container is disabled because DRS is not set. |
Action | Make sure to configure the WebContainer SessionManager to use memory-to-memory replication. |
Explanation | SIP container failover disabled. |
Action | Use the "enable.replication" custom property (for sip container) to enable. |
Explanation | The SIP container High Availability component is enabled for load balancing and failover. |
Action | No action is required. |
Explanation | The SIP container caught an exception of type HAGroupLeftException while being activated as a group member. |
Action | No action is required. |
Explanation | The SIP container caught an exception of type HAParameterRejectedException while being activated as a group member. |
Action | No action is required. |
Explanation | Data serialization failed in the SIP container. |
Action | No action is required. |
Explanation | An exception was caught in the SIP container High Availability component. |
Action | No action is required. |
Explanation | A DataStackException was caught in the SIP container High Availability component. |
Action | No action is required. |
Explanation | A IOException was caught in the SIP container. |
Action | No action is required. |
Explanation | The SIP container cannot join or depart from cluster because no cluster is defined. |
Action | No action is required. |
Explanation | The SIP container cannot start or stop the High Availability component because an exception occurred while trying to access the cluster service. |
Action | No action is required. |
Explanation | The SIP container failed getting SIP proxy endpoint information from UCF. |
Action | No action is required. |
Explanation | A ClassNotFoundException was caught in the SIP container. |
Action | No action is required. |
Explanation | The SIP container cannot publish its logical names due to an error obtaining ORB object. |
Action | No action is required. |
Explanation | The SIP container cannot publish its logical names due to a ClassCastException. |
Action | No action is required. |
Explanation | The SIP container cannot publish its logical names due to InvalidName exception. |
Action | No action is required. |
Explanation | The SIP container TAI failed to initialize due to a ClassNotFoundException |
Action | No action is required. |
Explanation | The SIP container TAI failed to initialize due to InstantiationException. |
Action | No action is required. |
Explanation | The SIP container TAI failed to initialize due to IllegalAccessException. |
Action | No action is required. |
Explanation | The SIP container security cannot open passwords file. |
Action | No action is required. |
Explanation | A LoginException was caught by the SIP container TAI while getting the user subject. |
Action | No action is required. |
Explanation | A NamingException was caught in the SIP container security. |
Action | No action is required. |
Explanation | A parse exception was caught in the SIP container TAI (Trust Association Interceptor). |
Action | No action is required. |
Explanation | An exception was caught initializing the SIP stack. |
Action | No action is required. |
Explanation | The SIP stack is initializing |
Action | No action is required. |
Explanation | An UnknownHostException was caught in the SIP stack while trying to resolve a host name to IP address. |
Action | No action is required. |
Explanation | The SIP stack failed writing to output stream. |
Action | No action is required. |
Explanation | The SIP stack configuration is initialized. |
Action | No action is required. |
Explanation | The SIP stack transport is initialized. |
Action | No action is required. |
Explanation | The SIP stack initialization is complete. |
Action | No action is required. |
Explanation | The SIP stack timer B is set. More information on timer B in RFC 3261. |
Action | No action is required. |
Explanation | The SIP stack is starting to listen on specified listening point. |
Action | No action is required. |
Explanation | SIP Container was launched successfully. It will only be initialized when first SIP application is loaded. |
Action | No action is required. |
Explanation | Exception occurred in the SIP container during replication. |
Action | No action is required. |
Explanation | Exception occurred in the SIP container replication during object deserialization. |
Action | No action is required. |
Explanation | Exception occurred in the SIP container during session activation after failover. |
Action | No action is required. |
Explanation | The SIP container failed resolving the host name of a virtual host alias to an IP address. |
Action | No action is required. |
Explanation | The application's display name in sip.xml is different from the display name in web.xml. This is not compliant with JSR-116 section 15.2. |
Action | Change the deployment descriptors to match the application display name. |
Explanation | The SIP container failed to dispatch a message to the thread pool. |
Action | No action is required. |
Explanation | The SIP container cannot identify object type for deserialization. |
Action | No action is required. |
Explanation | Authentication failed because the SIP container cannot retrieve the userPassword attribute from the person entry in the directory. |
Action | Change the LDAP configuration settings so the server has access to the userPassword attribute in the directory. |
Explanation | The Session Initiation Protocol (SIP) server cannot accept any more incoming messages while it is overloaded. |
Action | Reduce the incoming messages, or reduce any other possible sources of stress on the server machine. |
Explanation | The SIP server cannot accept any more incoming messages while it is overloaded. Too many application sessions are active. |
Action | Reduce the number of application sessions that are created or set a higher value for the maximum application sessions on the Session Initiation Protocol (SIP) container. |
Explanation | The SIP server cannot accept any more incoming messages while it is overloaded. The messages traffic is too high. |
Action | Reduce the message load or set the maximum messages per averaging period value to a higher value on the Session Initiation Protocol (SIP) container. |
Explanation | The SIP server cannot accept any more incoming messages while it is overloaded. |
Action | Reduce the incoming messages traffic or reduce any other possible source of stress on the server machine. If the maximum response time value is enabled and set on the Session Initiation Protocol (SIP) container, consider modifying it to a higher value. |
Explanation | The SIP server cannot accept any more incoming messages while the dispatch queue is overloaded. |
Action | Reduce the message load or set the maximum dispatch queue size value to a higher value on the Session Initiation Protocol (SIP) container. |
Explanation | The SIP container threads cannot handle the current load of tasks. |
Action | Reduce any possible sources of stress on the server machine, especially Session Initiation Protocol (SIP) messages traffic. In addition, review the amount of resources that are consumed by the SIP application code. |
Explanation | The Session Initiation Protocol (SIP) container is replicating its sessions data to a newly connected peer. |
Action | No action is required. |
Explanation | The Session Initiation Protocol (SIP) container has finished replicating its sessions data to the newly connected peer. |
Action | No action is required. |
Explanation | The timer value is modified in configuration |
Action | No action is required |
Explanation | The SIP container MBean received an administrative quiesce command. In this mode, new calls are not serviced on this container instance. |
Action | No action is required |
Explanation | The SIP container MBean received an administrative de-quiesce command. |
Action | No action is required |
Explanation | The SIP container quiesce operation has ended and all application sessions have been invalidated. |
Action | No action is required |