CWSPX

CWSPX0001W: Problems occurred while creating error logs.
CWSPX0002W: Caught unhandled exception from initFilterConfig in SipClusterSelectorRequestFilter exception={0}.
CWSPX0003W: Caught unhandled exception from doFilter in SipClusterSelectorRequestFilter exception={0}.
CWSPX0004W: Unable to find least loaded server for request in cluster {0}.
CWSPX0005W: Unable to find partition id {0} in clusters {1}. The call id for the message is [{2}].
CWSPX0006W: Invalid SIP message received. Header in question [{0}] for call id [{1}].
CWSPX0007W: Unable to retrieve configuration data.
CWSPX0008W: Invalid VIA header in SIP response message.
CWSPX0009W: Unable to route message due to invalid VIA header in SIP response message.
CWSPX0010W: Unable to find least loaded server for request in cluster {0} repeated {1} times with last failure {2}.
CWSPX0011W: Unable to find partition id {3} in cluster {0} repeated {1} times with last failure {2}.
CWSPX0012I: SIP Proxy detected server down {0} in cluster {1}.
CWSPX0013I: SIP Proxy detected server up {0} in cluster {1}.
CWSPX0014I: SIP Proxy detected partition id added {0} to server {1}.
CWSPX0015I: SIP Proxy detected partition id removed {0} from server {1}.
CWSPX0016W: SIP Proxy detected overloaded server {1} for request in cluster {0}.
CWSPX0017W: SIP Proxy detected overloaded server {3} for request in cluster {0} repeated {1} times with last failure {2}.
CWSPX0018I: SIP Proxy detected that previously overloaded server {0} is now okay.
CWSPX0019I: SIP Proxy detected server {0} that has a MMAP {1} with AP {2} with calculated MMAP {3}.
CWSPX0035I: Custom property {0} with value {1} has overridden server configuration property with value {2}.
CWSPX0050I: SIP Proxy detected SIP Proxy server up in cluster {4}, recalculating server {0} that has a MMAP {1} with AP {2} with calculated MMAP {3}.
CWSPX0051I: SIP Proxy detected SIP Proxy server down in cluster {4}, recalculating server {0} that has a MMAP {1} with AP {2} with calculated MMAP {3}.
CWSPX0052W: SIP Proxy detected overloaded server {1} for request due to MMAP in cluster {0}.
CWSPX0053W: SIP Proxy detected overloaded server {3} for request due to MMAP in cluster {0} repeated {1} times with last failure {2}.
CWSPX0054W: SIP Proxy detected SIP heartbeat failure for server {0}.
CWSPX0055I: SIP Proxy detected previously down server {0} is now responding to SIP heartbeats.
CWSPX0056I: SIP Proxy has informed the load balancer of readiness.
CWSPX0057W: The Session Initiation Protocol (SIP) logic in the control region encountered an error when it attempted to contact the SIP Container to start the failover process.
CWSPX0058W: The last Session Initiation Protocol (SIP) Container has failed. The failover process has been canceled.
CWSPX0059I: The Session Initiation Protocol (SIP) logic in the control region will start routing new requests to a new logical server name named {0}.
CWSPX0060I: The Session Initiation Protocol (SIP) logic in the control region will stop routing new requests to the {0} logical server name.
CWSPX0061I: Network heartbeat from a new proxy {0} timeout {1} limit {2}
CWSPX0062W: Network heartbeat limit exceeded with Session Initiation Protocol (SIP) proxy {0}. {1} heartbeats missed.
CWSPX0063E: Session Initiation Protocol (SIP) container failed to restart
CWSPX0064E: Session Initiation Protocol (SIP) logic in the control region detected network outage, and will restart itself.
CWSPX0065I: SIP Proxy startup delay is enabled for {0} milliseconds.
CWSPX0066I: SIP Proxy startup delay is completed.
CWSPX0067I: Session Initiation Protocol (SIP) proxy detected server {0} being quiesced.
CWSPX0068I: Session Initiation Protocol (SIP) proxy detected server {0} coming out of a quiesce.
CWSPX0070I: SIP Proxy is communicating with the Load Balancer at address {0}.
CWSPX0071W: SIP Proxy is no longer communicating with the Load Balancer at address {0}.


Terms and conditions for information centers | Feedback

Last updated: June 12, 2013 12:15 PM EDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.proxy.filter.sip.resources.sipfilters.dita
File name: com.ibm.ws.proxy.filter.sip.resources.sipfilters.html