Cause: Attempted to use charging when charging is not allowed (according to the configuration).
Action: Verify ChargingAllowed configuration
Level: 1
Type: WARNING
Impact: Process
UCS-30002: Ignore the 2xx response at state: {0}.
Cause: Received a 2xx response in an illegal state.
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30003: Failed to ACK the 2xx repsonse.
Cause: IOException received when trying to send ACK.
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30004: Could not ACK a dialog in the state: {0}.
Cause: Illegal state when trying to ACK dialog
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30005: Failed to send SIP request.
Cause: IOException when trying to send SIP request.
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30006: Could not cancel a call in the state: {0}.
Cause: Illegal state when trying to cancel call
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30007: Failed to send out response to BYE.
Cause: IOException when trying to send out response to BYE.
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30008: Failed to end the call leg.
Cause: Failed to send Bye.
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30009: Could not cancel call in connected state.
Cause: Illegal state to cancel call.
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30010: Failed to parse the SIP address.
Cause: Illegal SIP address
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30011: Failed to create the call.
Cause: Check the exception.
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30012: Could not find call with id: {0}.
Cause: Check the exception.
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30013: Failed to execute the action.
Cause: Check the exception.
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30014: Failed to terminate the call: {0}.
Cause: Check the exception.
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30015: Could not find the application session for call id: {0}.
Cause: Check the exception.
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30016: Failed to create SIP Invite Message.
Cause: Check the exception.
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30017: Failed to send INVITE to ''{0}'' from ''{1}''.
Cause: Check the exception.
Action: UNSPECIFIED ( see log/cause )
Level: 1
Type: WARNING
Impact: Process
UCS-30018: Failed to handle response.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30019: Failed to handle BYE.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30020: Ignore an error response at call state: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30021: Should not receive a BYE message in state: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30022: Failed to retrieve MaxiumCallDuration from configuration store.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30023: The session should not be NULL here; bad internal state.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30024: Could not terminate a call that is not in connected state.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30025: Failed to cancel the call: {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30026: Failed to connect the call due to invalid state: {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30027: Failed to connect the call due to resource unavailable: {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30028: Could not find the Coherence cache "{0}" in JNDI. Will use a cache created from the com.tangosol.net.CacheFactory.
Cause: The cache was not defined in the web.xml.
Action: Define the cache in a resource-ref element in the web.xml
Level: 1
Type: WARNING
Impact: Process
UCS-30029: The call length supervisor failed to end call: {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30030: Could not find the TimerManager "{0}" in JNDI. Call-length supervisor is disabled.
Cause: The TimerManager was not defined in the web.xml.
Action: Define the TimerManager in a resource-ref element in the web.xml
Level: 1
Type: WARNING
Impact: Process
UCS-30031: The cache "{0}" could not be retrieved from the CacheFactory. Make sure that the cache is defined in /config/ucs-thirdpartycall-coherence-cache-config.xml.
Cause: Coherence configuration for the cache is missing in the /config/ucs-thirdpartycall-coherence-cache-config.xml file in the thirdpartycallservice.jar
Action: Define the cache.
Level: 1
Type: ERROR
Impact: Process
UCS-31000: UCS-31000: PLACE-HOLDER MESSAGE
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-31001: UCS-31001: Call Control is starting...
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-31002: UCS-31002: Call Control has been started
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-31003: UCS-31003: Call Control is shutting down...
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-31004: UCS-31004: Call Control has been shut down
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-31100: UCS-31100: Failed to handle BYE.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-31101: UCS-31101: Failed to handle response.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-31102: UCS-31102: Exception when handling expired SipApplicationSession. Exception {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-31103: UCS-31103: Could not send ACK. Exception {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-31104: UCS-31104: Configured P-Asserted-Identity header is not an accepted address. Exception {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-31105: UCS-31105: Could not send BYE. Exception {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-31106: UCS-31106: Could not send CANCEL. Exception {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-31107: UCS-31107: Could not send response to BYE. Exception {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-31108: UCS-31108: Could not deliver event ''{1}'' to application due to exception in application. Exception {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-45200: CcaProvider starting...
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-45201: CcaProvider started
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-45202: CcaProvider stopping...
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-45203: CcaProvider stopped
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-45204: Could not deliver Session event ''{2}'' to application due to exception in application. SessionId={1}. Exception {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-45205: Could not deliver UserAgent event ''{2}'' to application due to exception in application. User={1}. Exception {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-45206: Could not access CCA Web Services API. Exception {0}.
Cause:
Action:
Level: 1
Type: SEVERE
Impact: Process
UCS-45207: Could not set initial status for CCA user ''{1}''. Exception {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-45208: Could not access mbean "{1}" to get the attribute "{2}" due to: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-45209: Could not find the Coherence cache "{0}" in JNDI. Will use a cache created from the com.tangosol.net.CacheFactory.
Cause: The cache was not defined in the web.xml.
Action: Define the cache in a resource-ref element in the web.xml
Level: 1
Type: WARNING
Impact: Process
UCS-45400: CcaService starting...
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-45401: CcaService started
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-45402: CcaService stopping...
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-45403: CcaService stopped
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-45404: Could not post logout event on queue. Queue full for {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-45405: Could not post chat accepted event on queue. Queue full for {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-45406: Could not post message on queue. Queue full for {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-45407: Could get messages from CCA. Result code: {0} {1}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-45408: Could get messages from CCA. Reason: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-45409: CcaService is using CCA version {0}.
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-45410: Could not post login event on queue. Queue full for {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-45411: Can not close session, sessionId={0}. Reason: {1} {2}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-45412: Could not find the Coherence cache "{0}" in JNDI. Will use a cache created from the com.tangosol.net.CacheFactory.
Cause: The cache was not defined in the web.xml.
Action: Define the cache in a resource-ref element in the web.xml
Level: 1
Type: WARNING
Impact: Process
UCS-45413: Work could not be scheduled in the WorkManager. Exception: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-45414: Could not post LocalMessage on queue. Queue full for {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-45415: Could not post CcaMessage on queue. Queue full for {0}.