Express (Distributed operating systems), v8.0 > Reference > Messages
CWSCT
CWSCT0001I: SIP Container initialization completed.
Explanation The SIP container is up and ready to receive messages from the network. Action Informational message. No user action is necessary.
CWSCT0002I: SIP Container {0}
Explanation vnumber of the SIP container component. Action Informational message. No user action is necessary.
CWSCT0003W: SIP Container MBean unable to start.
Explanation SIP Container MBean unable to start. JMX operations will not be available for the SIP Container. Action No action is required.
CWSCT0004E: The following exception has occurred:
Explanation An exception was caught by the SIP container. Action No action is required.
CWSCT0006I: Failover started. Number of received objects {0} for logical name {1}.
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.
CWSCT0008I: Failover ended for logical name {0}
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.
CWSCT0010E: Error configuring sip.xml parser.
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.
CWSCT0011E: Parser not available; unable to load application configuration.
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".
CWSCT0012E: Parse exception; failed to parse sip.xml {0}.
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. We 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).
CWSCT0013E: Listener Class: {0} not found for application: {1}.
Explanation The class loader could not find the listener class. Action Check your sip.xml file and verify that the listener class name is correct. Make sure the listener class is included in the class path.
CWSCT0014E: Failed to create Listener Class: {0} for application: {1}.
Explanation The SIP container could not instantiate the listener class. Action Check your sip.xml file and verify that the listener class name is correct. Make sure the listener class has a public constructor that expects no arguments.
CWSCT0015E: Invalid XML - more than one Timer Listener assigned to application {0}.
Explanation The sip.xml document defines more than one TimerListener for the same application. Action Check your sip.xml file and make sure there is only one TimerListener class for the application.
CWSCT0016E: Error parsing session TTL for Sip Application: {0}.
Explanation The sip.xml document does not contain a valid application session time-out value. Action Check your sip.xml file to make sure the session-timeout setting is expressed in whole number of minutes.
CWSCT0017E: Mapping for nonexisting siplet: {0}, Application: {1}.
Explanation The sip.xml document contains a servlet mapping for an undefined servlet Action Check your sip.xml file 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.
CWSCT0018E: Invalid Condition Type in sip.xml: {0}.
Explanation The sip.xml document does not contain a valid type of servlet matching condition. Action Check your sip.xml file to make sure the matching rules are compliant with JSR 116 (SIP Servlet API) 11.3 (Conditions).
CWSCT0019E: Error parsing {0} condition, var: {1} ,value: {2}.
Explanation The sip.xml document does not contain a valid servlet matching rule. Action Check your sip.xml file to make sure the matching rules are compliant with JSR 116 (SIP Servlet API) chapter 11 (Mapping Requests to Servlets).
CWSCT0020E: Error parsing AND condition; sub-elements not found.
Explanation The sip.xml document contains an AND condition with no sub-elements. Action Check your sip.xml file to make sure there are matching rules under the AND tag.
CWSCT0021E: Error in xml definition for sip-app.
Explanation The sip.xml document contains zero or multiple sip-app sections. There may only be one. Action Check your sip.xml file to make sure there is exactly one sip-app section.
CWSCT0022E: Error - local SIP DTD document not found.
Explanation There is no local definition for /javax/servlet/sip/sip-app_1_0.dtd Action No action is required.
CWSCT0023I: Server is no longer overloaded. Load factor reduced to {0}
Explanation The SIP container is no longer considered overloaded, and is now ready to handle new sessions Action No action is required.
CWSCT0024I: New server weight set to {1} by {0}
Explanation The server weight was changed, due to a change in SIP activity Action No action is required.
CWSCT0025E: Failed to create SIP stack.
Explanation The internal SIP stack failed to initialize. Action No action is required.
CWSCT0026E: Exception in SIP stack.
Explanation An exception was caught in the SIP stack layer. The stack will attempt to continue running normally. Action No action is required.
CWSCT0028I: SIP Container Listening Point {0}:{1}/{2}
Explanation 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.
CWSCT0029E: SIP failed to forward; response request is {0}
Explanation The SIP container failed to forward a SIP message. Action No action is required.
CWSCT0030E: SIP failed proxying to branch; URI is {0}
Explanation The SIP container, acting as a proxy, failed to forward a request to one of the destinations. Action No action is required.
CWSCT0031E: SIP failed to create record route {0}
Explanation The SIP container, acting as a proxy, failed to create a Record-Route header. Action No action is required.
CWSCT0032E: SIP cannot change proxy to parallel after proxyTo
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()
CWSCT0033E: SIP cannot recurse with stateless proxy.
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.
CWSCT0034E: SIP cannot change proxy to stateful after proxyTo
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()
CWSCT0035E: SIP failed cancellation request in proxy; cancel request: {0}
Explanation The SIP container failed sending out a CANCEL request. Action No action is required.
CWSCT0036E: SIP failed to send response upstream; response: {0}
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.
CWSCT0037E: SIP cannot set record route after proxyTo
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()
CWSCT0040E: SIP failed to create request; request: {0}
Explanation The SIP container failed creating a SIP request message. Action No action is required.
CWSCT0041E: Failed to get route header.
Explanation The SIP container failed getting a Route header in a request. Action No action is required.
CWSCT0042E: Failed to resolve internet address.
Explanation Failed resolving an internet address from host name to IP address. Action No action is required.
CWSCT0043E: Unable to set record route for a non dialog request: {0}
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.
CWSCT0044E: Proxy has reached an unexpected function call.
Explanation The SIP container received a message where it does not expect it. Action No action is required.
CWSCT0045E: Unable to proxy subsequent requests without route header: {0}
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.
CWSCT0046E: Unknown URI type; unable to access parameters from header: {0}
Explanation The SIP container cannot process a message because the URI is not a sip or sips URI. Action No action is required.
CWSCT0048E: Error processing Strict Routing; request URI does not contain session ID. {0}
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.
CWSCT0049E: Error sending response
Explanation The SIP container failed to send out a response. Action No action is required.
CWSCT0051E: Unable to find a siplet for invocation; default handler not available.
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.
CWSCT0052E: Unable to find dialog for received BYE request. Call-Id is {0}
Explanation The SIP container received a BYE request that is not matched to any existing dialog. Action No action is required.
CWSCT0053E: Invalid variable in operator; var: {0}
Explanation The sip.xml document does not contain a valid variable. Action Check your sip.xml file to make sure the variable is valid according to JSR 116 (SIP Servlet API) 11.2 (SIP Request Object Model)
CWSCT0054E: Failed to evaluate operator {0}; subelements not available.
Explanation The sip.xml document contains a condition with no sub-elements. Action Check your sip.xml file to make sure that pattern matching is valid according to JSR 116 (SIP Servlet API) 11.3 (Conditions).
CWSCT0055E: IPAuthenticator failed parsing configuration
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
CWSCT0056E: IPAuthenticator failed, unknown host
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
CWSCT0057E: IPAuthenticator failed parse header
Explanation The SIP container failed to parse a Via header for IP authentication. Action No action is required.
CWSCT0058E: IPAuthenticator header problem.
Explanation The SIP container failed to find a Via header in the message for IP authentication. Action No action is required.
CWSCT0059E: SIP failed to get expirations; not properly formatted: {0}
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.
CWSCT0060E: SIP failed to set display name; name: {0}
Explanation The application call to Address.setDisplayName() failed. Action Check the application code to make sure the display name is valid and not null.
CWSCT0061E: SIP failed to set expirations; seconds: {0}
Explanation The application call to Address.setExpires() failed. Action No action is required.
CWSCT0062E: SIP failed to set parameters; name: {0}, value: {1}
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.
CWSCT0063E: SIP failed to set q; value: {0}
Explanation The application call to Address.setQ() failed. Action Check the application code to make sure the priority value is valid.
CWSCT0064E: SIP failed to get method from submitted request: {0}
Explanation The application call to SipServletMessage.getMethod() failed. Action No action is required.
CWSCT0065E: SIP failed to get request URI from submitted request: {0}
Explanation The application call to SipServletRequest.getRequestURI() failed. Action No action is required.
CWSCT0066E: SIP failed to create response to request: {0}
Explanation The SIP container failed to create a response to the request. Action No action is required.
CWSCT0067E: SIP failed to send request using JAIN; URI: {0}
Explanation The SIP container failed sending out a request. Action No action is required.
CWSCT0069E: SIP failed to add header; name: {0}, value: {1}
Explanation The SIP container failed to add a header to the message. Action No action is required.
CWSCT0070E: SIP failed to send response, {0}
Explanation An error occurred while the SIP container was trying to send out a response. Action No action is required.
CWSCT0071E: SIP failed to set header; name: {0}, value: {1}
Explanation The SIP container failed to set a header value in the message. Action No action is required.
CWSCT0072E: SIP failed to set host; host: {0}
Explanation The application call to SipURI.setHost() failed. Action Check the application code to make sure the host name is valid and not null.
CWSCT0073E: SIP failed to set port; port: {0}
Explanation The application call to SipURI.setPort() failed. Action No action is required.
CWSCT0074E: SIP failed to set secure; value: {0}
Explanation The application call to SipURI.setSecure() failed. Action No action is required.
CWSCT0075E: SIP failed to set user; user: {0}
Explanation The application call to SipURI.setUser() failed. Action Check the application code to make sure the user name is valid and not null.
CWSCT0076E: SIP failed to set user password; password: {0}
Explanation The application call to SipURI.setUserPassword() failed. Action Check the application code to make sure the user password is valid and not null.
CWSCT0077E: SIP failed to get accepted language, {0}
Explanation The application call to SipServletMessage.getAcceptLanguage() failed. Action No action is required.
CWSCT0078E: SIP failed to get accepted languages, {0}
Explanation The application call to SipServletMessage.getAcceptLanguages() failed. Action No action is required.
CWSCT0079E: SIP failed to get address header; name: {0}
Explanation The application call to SipServletMessage.getAddressHeader() failed. Action No action is required.
CWSCT0080E: SIP failed to get address headers; name: {0}
Explanation The application call to SipServletMessage.getAddressHeaders() failed. Action No action is required.
CWSCT0081E: SIP failed to get character encoding {0}
Explanation The application call to SipServletMessage.getCharacterEncoding() failed. Action No action is required.
CWSCT0082E: SIP failed to get content length {0}
Explanation The application call to SipServletMessage.getContentLength() failed. Action No action is required.
CWSCT0083E: SIP failed to get content type {0}
Explanation The application call to SipServletMessage.getContentType() failed. Action No action is required.
CWSCT0084E: SIP failed to get header; name: {0}
Explanation The application call to SipServletMessage.getHeader() failed. Action No action is required.
CWSCT0085E: SIP failed to get header; names {0}
Explanation The application call to SipServletMessage.getHeaderNames() failed. Action No action is required.
CWSCT0086E: SIP failed to get headers; name: {0}
Explanation The application call to SipServletMessage.getHeaders() failed. Action No action is required.
CWSCT0087E: SIP failed to set content; content: {0}, content type: {1}
Explanation The application call to SipServletMessage.setContent() failed. Action Check the application code to make sure the message content is valid and not null.
CWSCT0088E: SIP failed to get via headers {0}
Explanation The application call to SipServletMessage.getViaHeaders() failed. Action No action is required.
CWSCT0089E: SIP failed to get contact header {0}
Explanation The application call to SipServletMessage.getContactHeader() failed. Action No action is required.
CWSCT0090E: SIP failed to get JAIN SIP headers {0}
Explanation The SIP container failed getting one or more headers from the internal JAIN message object. Action No action is required.
CWSCT0091E: SIP failed to get maximum forwards {0}
Explanation The application call to SipServletRequest.getMaxForwards() failed. Action No action is required.
CWSCT0092E: SIP failed to get reason phrase {0}
Explanation The application call to SipServletResponse.getReasonPhrase() failed. Action No action is required.
CWSCT0093E: SIP failed to get status {0}
Explanation The application call to SipServletResponse.getStatus() failed. Action No action is required.
CWSCT0094E: SIP failed to set status; status: {0}, reason phrase: {1}
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.
CWSCT0095E: SIP failed to create address; URI: {0}, display name: {1}
Explanation The application call to SipFactory.createAddress() failed. Action Check the application code to make sure the URI and display name are valid.
CWSCT0097E: SIP failed to create SIP URI; user: {0}, host: {1}
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.
CWSCT0098E: SIP failed to create URI; URI: {0}
Explanation The application call to SipFactory.createURI() failed. Action Check the application code to make sure the URI string represents a valid URI.
CWSCT0099E: Failed to push route; URI: {0}
Explanation The application call to SipServletRequest.pushRoute() or SipServletRequest.pushRecordRoute() failed. Action Check the application code to make sure the SipURI is valid.
CWSCT0100E: SIP failed to set URI; URI: {0}
Explanation The application call to Address.setURI() failed. Action Check the application code to make sure the URI is valid.
CWSCT0101E: Failed to send an ACK request.
Explanation The SIP container failed to send out an ACK request. Action No action is required.
CWSCT0102E: Failed to send a CANCEL request.
Explanation The SIP container failed to send out a CANCEL request. Action No action is required.
CWSCT0103E: Failed to generate a timeout response.
Explanation A request that was sent out from the SIP container was not responded to for 32 seconds, and the SIP container failed to generate a timeout response to the application. Action No action is required.
CWSCT0104E: Failed to clone address.
Explanation Internal error in the SIP container cloning an Address object. Action No action is required.
CWSCT0105E: Invalid Telephony URL: {0}
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).
CWSCT0106E: Error on sending a 487 response {0}
Explanation While canceling a request, the SIP container failed sending the 487 (Request Terminated) response to the original request. Action No action is required.
CWSCT0108E: Error setting character encoding: {0}
Explanation The application call to SipServletMessage.setCharacterEncoding() failed. Action Check the application code to make sure the encoding parameter is valid and not null.
CWSCT0109E: Error setting tag value: {0}
Explanation The application call to Address.setTag() failed. Action Check the application code to make sure the tag parameter is valid.
CWSCT0113I: SIP Session sequence logger is enabled, level: {0}
Explanation The logger for SIP session/dialog sequence is enabled. Action No action is required.
CWSCT0116I: SIP Container is using standalone configuration.
Explanation The SIP container is not running as a Websphere service. Action No action is required.
CWSCT0117E: Failed to initialize siplet {0}
Explanation The SIP container failed loading or instantiating a SIP servlet class. Action Check your sip.xml file to make sure the class name is correct and has a public constructor that expects no arguments.
CWSCT0118E: Service siplet failed {0}
Explanation An exception was created by the SIP servlet code. Action No action is required.
CWSCT0119E: Invoke siplet failed; servlet unavailable: {0}, {1}
Explanation The SIP servlet does not exist. Action Check your sip.xml file to make sure the servlet class name is correct.
CWSCT0120E: Error initializing the SIP container
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.
CWSCT0122W: Error dispatching timer event; timer listener not available for: {0}
Explanation The SIP servlet timer was triggered, but no listener is associated with it. Action No action is required.
CWSCT0124W: TimerServiceImpl is unavailable
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".
CWSCT0125E: Transaction ID already set for transaction; current {0}, new {1}
Explanation The SIP transaction is already initialized with a transaction ID, and cannot be changed. Action No action is required.
CWSCT0139E: SIP Failed to invoke request; message is {0}
Explanation An exception was created while the SIP container tried to invoke a request. Action No action is required.
CWSCT0140E: SIP failed to send response to prepare to write.
Explanation The SIP container failed to send out the response from within the call to prepareHeadersForWrite(). Action No action is required.
CWSCT0142E: Error dispatcher has not completed dispatching previous message.
Explanation The SIP container cannot dispatch a message because the previous message dispatching has not completed yet. Action No action is required.
CWSCT0145E: Received a {0} request while expecting javax.servlet.//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ .HttpServletRequest
Explanation The SIP container received a request from the web container that is not a javax.servlet.//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ .HttpServletRequest. Action No action is required.
CWSCT0146E: Failed to register {0} collaborator
Explanation The SIP container failed to register itself as a listener to Websphere. Action No action is required.
CWSCT0185E: Error - The cache algorithm does not exist.
Explanation The cache algorithm requested by the SIP container session manager does not exist. Action No action is required.
CWSCT0186E: Error - Replicator exception
Explanation Replication exception caught by the SIP container session manager. Action No action is required.
CWSCT0187I: SIP HA {0}
Explanation The SIP container high availability component initialized. Action No action is required.
CWSCT0188E: Error - Class Not Found Exception; unable to deserialize.
Explanation The SIP container caught an exception of type ClassNotFoundException during object serialization. Action No action is required.
CWSCT0189E: Error - IO exception; unable to serialize / deserialize.
Explanation The SIP container caught an exception of type IOException during object serialization. Action No action is required.
CWSCT0219E: Error - drs exception
Explanation Exception caught in the SIP container during DRS replication. Action No action is required.
CWSCT0220E: Error - admin JMX exception
Explanation Exception caught in the SIP container while activating the MBean for the session manager. Action No action is required.
CWSCT0222E: Error - DRS multibroker exception.
Explanation Exception caught in the SIP container using the DRS multi broker. Action No action is required.
CWSCT0224E: Error - DRS mode is not BOTH_CLIENT_SERVER (peer to peer)
Explanation The DRS mode is not suitable for data replication in the SIP container. Action No action is required.
CWSCT0225E: Info - DRS not set
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.
CWSCT0226I: Info - SIP container failover disabled.
Explanation SIP container failover disabled. Action Use the "enable.replication" custom property (for sip container) to enable.
CWSCT0227I: Info - SIP container High Availability component enabled.
Explanation The SIP container High Availability component is enabled for load balancing and failover. Action No action is required.
CWSCT0228E: Error - HAGroupLeftException
Explanation The SIP container caught an exception of type HAGroupLeftException while being activated as a group member. Action No action is required.
CWSCT0229E: Error - HAParameterRejectedException
Explanation The SIP container caught an exception of type HAParameterRejectedException while being activated as a group member. Action No action is required.
CWSCT0231E: Error - IO exception; unable to deserialize.
Explanation Data serialization failed in the SIP container. Action No action is required.
CWSCT0232E: Error - HA exception
Explanation An exception was caught in the SIP container High Availability component. Action No action is required.
CWSCT0233E: Error - Datastack exception
Explanation A DataStackException was caught in the SIP container High Availability component. Action No action is required.
CWSCT0237E: Error - IO excpetion
Explanation A IOException was caught in the SIP container. Action No action is required.
CWSCT0238E: Error - UCF Exception; no cluster defined.
Explanation The SIP container cannot join or depart from cluster because no cluster is defined. Action No action is required.
CWSCT0240E: Error - no cluster member service.
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.
CWSCT0241E: Error - UCF Exception - no member available.
Explanation The SIP container failed getting SIP proxy endpoint information from UCF. Action No action is required.
CWSCT0243E: Error - Class not found exception.
Explanation A ClassNotFoundException was caught in the SIP container. Action No action is required.
CWSCT0244E: Error - cannot obtain ORB object
Explanation The SIP container cannot publish its logical names due to an error obtaining ORB object. Action No action is required.
CWSCT0245E: Error - ORB class cast exception
Explanation The SIP container cannot publish its logical names due to a ClassCastException. Action No action is required.
CWSCT0246E: Error - invalid ORB name request
Explanation The SIP container cannot publish its logical names due to InvalidName exception. Action No action is required.
CWSCT0259E: Error - class not found
Explanation The SIP container TAI failed to initialize due to a ClassNotFoundException Action No action is required.
CWSCT0260E: Error - instantiation exception
Explanation The SIP container TAI failed to initialize due to InstantiationException. Action No action is required.
CWSCT0261E: Error - illegal access exception.
Explanation The SIP container TAI failed to initialize due to IllegalAccessException. Action No action is required.
CWSCT0262E: Error - file not found.
Explanation The SIP container security cannot open passwords file. Action No action is required.
CWSCT0264E: Error - Login Context - failed
Explanation A LoginException was caught by the SIP container TAI while getting the user subject. Action No action is required.
CWSCT0266E: Error - naming exception
Explanation A NamingException was caught in the SIP container security. Action No action is required.
CWSCT0267E: Error - parse exception.
Explanation A parse exception was caught in the SIP container TAI (Trust Association Interceptor). Action No action is required.
CWSCT0315E: Exception in SIP Stack.
Explanation An exception was caught initializing the SIP stack. Action No action is required.
CWSCT0316I: SIP Stack {0}
Explanation The SIP stack is initializing Action No action is required.
CWSCT0317E: Unknown host exception; unable to resolve hostname.
Explanation An UnknownHostException was caught in the SIP stack while trying to resolve a host name to IP address. Action No action is required.
CWSCT0318E: Parser exception; failed to write to output stream.
Explanation The SIP stack failed writing to output stream. Action No action is required.
CWSCT0321I: SIP stack init configuration
Explanation The SIP stack configuration is initialized. Action No action is required.
CWSCT0322I: SIP stack init transport.
Explanation The SIP stack transport is initialized. Action No action is required.
CWSCT0323I: SIP stack init finished.
Explanation The SIP stack initialization is complete. Action No action is required.
CWSCT0324I: SIP Stack, Timer B Set to {0} milliseconds.
Explanation The SIP stack timer B is set. More information on timer B in RFC 3261. Action No action is required.
CWSCT0328I: SIP starting to listen on {0}.
Explanation The SIP stack is starting to listen on specified listening point. Action No action is required.
CWSCT0332I: SIP Container was launched successfully but will only be initialized when first SIP application is loaded.
Explanation SIP Container will be initialized when first SIP application is loaded. Action No action is required.
CWSCT0333E: Replication failed.
Explanation Exception occurred in the SIP container during replication. Action No action is required.
CWSCT0334E: Failed to deserialize replication.
Explanation Exception occurred in the SIP container replication during object deserialization. Action No action is required.
CWSCT0335E: Failed to reactivate objects after failover.
Explanation Exception occurred in the SIP container during session activation after failover. Action No action is required.
CWSCT0336E: VirtualHostAlias.init: cannot lookup host {0}
Explanation The SIP container failed resolving the host name of a virtual host alias to an IP address. Action No action is required.
CWSCT0337W: Display name in sip.xml ({0}) is different from display name in web.xml ({1}).
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.
CWSCT0338W: Failed to dispatch SIP message to thread pool. Message= {0}, Call ID= {1}, Error code= {2}.
Explanation The SIP container failed to dispatch a message to the thread pool. Action No action is required.
CWSCT0339E: Deserialize: Cannot identify object type.
Explanation The SIP container cannot identify object type for deserialization. Action No action is required.
CWSCT0340E: Error - cannot retrieve password attribute.
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.
CWSCT0341W: The server is overloaded.
Explanation The 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.
CWSCT0342W: The server is overloaded because there are too many application sessions.
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 SIP container.
CWSCT0343W: The server is overloaded because too many messages were received during an averaging period.
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 SIP container.
CWSCT0344W: The server is overloaded because the server response time is too slow.
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 SIP container, consider modifying it to a higher value.
CWSCT0345W: The maximum dispatch queue size of {0} has been exceeded. New messages will be dropped.
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 SIP container.
CWSCT0346E: The dispatch queue is overloaded. The following message has been rejected: {0}
Explanation The SIP container threads cannot handle the current load of tasks. Action Reduce any possible sources of stress on the server machine, especially SIP messages traffic. In addition, review the amount of resources that are consumed by the SIP application code.
CWSCT0347I: Bootstrap replication has started.
Explanation The SIP container is replicating its sessions data to a newly connected peer. Action No action is required.
CWSCT0348I: Bootstrap replication has finished.
Explanation The SIP container has finished replicating its sessions data to the newly connected peer. Action No action is required.
CWSCT0349I: SIP stack timer [{0}] value set to [{1}]
Explanation The timer value is modified in configuration Action No action is required
CWSCT0350I: Entering quiesce mode
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
CWSCT0351I: Exiting quiesce mode
Explanation The SIP container MBean received an administrative de-quiesce command. Action No action is required
CWSCT0352E: Failed to get Server Type. Error = {0}.
Explanation Exception occured while getting server type. Action No action is required
CWSCT0353E: Failed to get Configuration on startup. Error = {0}.
Explanation Exception occured while getting configration. Action No action is required
CWSCT0354I: Running on Stanalone server
Explanation The SIP container is running in a stand-alone environment. The High Availability Manager is not enabled. Action No action is required
CWSCT0355E: Cannot run on this server type: {0}.
Explanation SipContainer cannot run on the specified server type. Action No action is required
CWSCT0356E: Failed to parse authentication header.
Explanation The application call to SipServletResponse.getChallangeRealm() failed. Action No action is required.
CWSCT0357E: Error - Couldn't get message body.
Explanation An IOException was caught in the SIP container security code. Action No action is required.
CWSCT0358W: Unknown authentication realm {0}
Explanation A SIP request for an unknown authentication realm was recieved Action No action is required
CWSCT0359I: Hashed Credential attributes not found.
Explanation Attributes needed for using hashed credentials were not found. Using unhashed user password lookup for authentication. Action No action is required
CWSCT0360I: Server quiesce ended successfully
Explanation The SIP container quiesce operation has ended and all application sessions have been invalidated. Action No action is required
CWSCT0361I: Network heartbeat from a new proxy {0} timeout {1} limit {2}
Explanation The SIP container detected a new SIP proxy in the cluster, and SIP network outage detection is enabled. Action No action is required
CWSCT0362I: Network heartbeat limit exceeded with SIP proxy {0}. {1} heartbeats missed.
Explanation The SIP container 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.
CWSCT0363I: SIP container detected network outage, and will restart itself.
Explanation The SIP container 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. We can use a network sniffer to trace the SIP KEEPALIVE messages between the proxy and the container.
CWSCT0364I: SIP container failed to restart
Explanation The SIP container attempted to restart itself as a result of network outage, but this action failed. The container will shut down without restarting itself. Action Restart the application server manually.
CWSCT0365E: Failed to find Sip Session for B2B linkage {0} after failover
Explanation Error occurred in the SIP container during replication. Action No action is required.
CWSCT0401I: Default application router has been initialized.
Explanation The default application router choose application by weight assigned in the admin console. Action No action is required
CWSCT0403I: External application router has been loaded according to the defined custom property - javax.servlet.sip.ar.spi.SipApplicationRouterProvider, class name - {0}.
Explanation The external application router is application router that is implemented and loaded as a third party. Action No action is required
CWSCT0404I: Default Application Router (DAR) property file was loaded, file name - {0}.
Explanation Default Application Router (DAR) supplied by the user was located and loaded Action No action is required
CWSCT0405I: The application router is configured to select applications by the weight.
Explanation The default application router choose application by weight assigned in the admin console. Action No action is required
CWSCT0406E: Error creating default application router repository: {0}.
Explanation Some internal error. Action No action is required
CWSCT0407E: No state for default application router.
Explanation When application router receives request with directive different than NEW it should contain a state index in the application chain. Action No action is required
CWSCT0408E: Default application router, property strategy, failed to load property file.
Explanation Application router property file is in the wrong format. Action Verify that application router property file is in the right format.
CWSCT0409W: Proxies are configured with different outbound interfaces.
Explanation All proxies must be configured with the same virtual IP. Action No action is required.
CWSCT0410E: Failed to generate a application router response.
Explanation Application router raised unexpected exception the container have tried to generate 500 response and failed. Action Contact application router owner.
CWSCT0411W: The custom property [{0}] is deprecated.
Explanation It is still honored and it's value is used if it is defined in the configuration, it is higher precedence than the attribute - for backward compatibility reasons. Action Set this value via Admin UI Sip Container configuration settings.
CWSCT0412W: a SIP task related to {0} is appeared to be hung. This task will be ignored.
Explanation The task has exceeded the configuration time for a thread hung detection. Subsequent SIP messages on this session may fail. Action No action is required.
CWSCT0413W: The server is overloaded since container threads queues reached maximum capacity.
Explanation The SIP server cannot accept any more incoming messages while it is overloaded. Action Reduce the incoming messages traffic or set the maximum of SIP container queue size to the higher value.
CWSCT0414I: SIP Replication mode is:{0}
Explanation The frequency in which SIP sessions are replicated across replication domain (if exists). Action No action is required
CWSCT0415I: Loading default application router, weight strategy.
Explanation No custom application router or DAR configuration file were supplied, the SIP container will use its default behavior of sorting applications according to weight. Action No action is required
CWSCT0416E: Default Application Router (DAR) configuration file was not located in the path supplied {0}.
Explanation Default Application Router (DAR) configuration file supplied by the user was not found Action Check that the path supplied in SIP container properties "javax.servlet.sip.ar.dar.configuration" was correct
CWSCT0417E: Siplet class name defined in sip.xml was not found, class name: {0}.
Explanation The sip.xml document defines a siplet class name that can not be loaded. Action Check your sip.xml file and make sure that the class name was written correctly.