UCS-10107: Could not find a property editor for class ''{0}''.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10108: Error initializing the editor. Reason: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10109: Failed to export command {1}. Reason: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10110: Could not create progress writer. Progress information will be lost.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10111: Exception when converting to string. Reason: {0}
Cause: Internal error
Action: No action required.
Level: 1
Type: ERROR
Impact: Process
UCS-10112: Could not connect to remote resource. Reason: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10113: Property class {0} was not found.
Cause: Malformed command-service.xml.
Action: Correct command-service.xml.
Level: 1
Type: WARNING
Impact: Process
UCS-10114: Command ''{0}'' has no help!
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10115: Missing name element for command.
Cause: Malformed command-service.xml.
Action: Correct command-service.xml.
Level: 1
Type: ERROR
Impact: Process
UCS-10116: Object evicted from cache "{0}". Increase the size of the cache or change the expiry delay. Key = "{1}", value = "{2}".
Cause: An object has been evicted form the cache since the cache is to small.
Action: Increase the size of the cache or change the expiry delay.
Level: 1
Type: WARNING
Impact: Process
UCS-10195: Failed to read commands from file ''{1}''. Reason: {0}.
Cause: Reading and/or parsing of commands failed.
Action: Correct the command description.
Level: 1
Type: ERROR
Impact: Process
UCS-10196: Creating Command Service
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-10197: Starting Command Service.
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-10198: Command Service already started.
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-10199: Stopping Command Service.
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-10200: Command Service already stopped.
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-10201: Destroying Command Service.
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-10202: Loading command: {0}.
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-10203: Could not instantiate the class ''{1}''. Reason: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10204: The class or its nullary constructor is not accessible. Reason: {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10205: Could not find the class ''{0}''. Make sure that it is available to the system and verify that you wrote the class name correctly.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10206: Loaded {0} (out of {1}) commands into the system.
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-10207: Could not find the attribute. The only valid attribute names are \"class", \"resource\" and "\"description\". Please verify that you spelled them correctly.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10249: Failed to send error message to client: {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10250: MemoryMonitor starting
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-10251: MemoryMonitor stopping
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-10252: Expected an Integer but found: {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10253: Cannot create a tree of type {0}, returning null
UCS-10322: Registering MBean {0} with object name {1}
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-10323: Failed to load Mbean.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10324: Failed to deregister Mbean.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10325: Failed to persist MBean.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10326: Failed to load metadata for Mbean from {1}. Reason: {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10327: Failed to call MBean lifecycle {1} for bean {2}. Reason: {0}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-10328: Failed to load the jmxframework.
Cause: Internal Error, possibly misconfiguration or missing jars.
Action: Confirm JMX framework is configured / set up properly.
Level: 1
Type: ERROR
Impact: Process
UCS-11051: Error when looking up userservice.
Cause: The J2EE application SubscriberDataServices may not be deployed or started.
Action: Ensure that the J2EE application SubscriberDataServices is running.
Level: 1
Type: ERROR
Impact: Process
UCS-11052: Error when creating userservice.
Cause: The J2EE application SubscriberDataServices may not be deployed or started.
Action: Ensure that the J2EE application SubscriberDataServices is running.
Level: 1
Type: ERROR
Impact: Process
UCS-11179: Command Line Interface connection problems.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11180: No value for ''{0}'' was provided.
Cause: A configuration value for the indicated property was not specified in the ejb-jar.xml file for the subscriberdataservice application.
Action: Specify the corresponding property.
Level: 1
Type: ERROR
Impact: Process
UCS-11181: Failed to find the user ''{0}''. Reason: {1}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11182: Failed to close connection to LDAP store. Reason: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11183: Unable to find a user with attribute ''{0}'' = ''{1}''. Reason: {2}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11184: Failed to find user attributes for privateId = ''{0}''. Reason: {1}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11185: Error performing SQL operation.
Cause: A SQL operation against the database failed.
Action: Verify that the database is accessible and correctly configured.
Level: 1
Type: ERROR
Impact: Process
UCS-11186: Format error in public identity stored in the database.
Cause: A public identity stored in the database is not a valid SIP URI.
Action: Correct the public identity.
Level: 1
Type: ERROR
Impact: Process
UCS-11187: More than one privateId found for publicId ''{0}''.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11188: Failed to get account status for user ''{0}''. Reason: {1}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11189: {0} is not supported in DAO implementation {1}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11191: Failed to obtain the ha1 digest hash for user ''{0}'' for realm ''{1}''. Reason: {2}
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11192: Failed to obtain the group membership for user ''{0}'' for realm ''{1}''. Reason: {2}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11193: Failed to obtain all the defined roles. Reason: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11194: Failed to get ejb environment property ''{0}''. Reason: {1}.
Cause: The value of the given JNDI name is not in a proper format.
Action: Ensure that the value of the JNDI name is a boolean (that is, true or false).
Level: 1
Type: ERROR
Impact: Process
UCS-11208: Invalidating DirContextPool
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-11209: Failed to get an instance of {0}. Reason: {1}.
Cause: Installation is not properly configured.
Action: Verify installation.
Level: 1
Type: ERROR
Impact: Process
UCS-11210: Unable to fetch verifier for ''{0}''. Crypto Scheme not supported.
Cause: User in OID not configured properly.
Action: Correct the configuration of OID.
Level: 1
Type: ERROR
Impact: Process
UCS-11211: Unable to fetch verifier for ''{0}''. User without reversible password.
Cause: User in OID not configured properly.
Action: Correct the configuration of OID.
Level: 1
Type: ERROR
Impact: Process
UCS-11212: Unable to fetch verifier; user name missing.
Cause: User in OID not configured properly.
Action: Correct the configuration of OID.
Level: 1
Type: ERROR
Impact: Process
UCS-11213: Failed to obtain an error code for dynamic verifier. Reason: {0}.
Cause: Problems accessing OID
Action: Verify the availability of OID.
Level: 1
Type: ERROR
Impact: Process
UCS-11214: Invalid response control for ''{0}''
Cause: User in OID not configured in a proper way.
Action: Correct the configuration of OID.
Level: 1
Type: ERROR
Impact: Process
UCS-11215: Empty verifier found for ''{0}''.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11216: No {0} attribute found for verifier.
Cause: User in OID not configured properly.
Action: Correct the configuration of OID.
Level: 1
Type: ERROR
Impact: Process
UCS-11217: Empty password attribute found for verifier.
Cause: User in OID not configured properly.
Action: Correct the configuration of OID.
Level: 1
Type: ERROR
Impact: Process
UCS-11218: More than one password verifier found.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11219: Failed to close NamingEnumeration in dynamic verifier.
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-11220: Failed to parse expiration time ''{0}''.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11221: Failed to parse lockout time ''{0}''.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11222: No user attributes were retrieved!
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11223: Invalid password format for LDAP credentials
Cause: The format of the LDAP password is not recognized.
Action: Verify the configuration of the OID.
Level: 1
Type: ERROR
Impact: Process
UCS-11224: The registered componenent under the JNDI name {0} was not of type {1}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11225: The function with ObjectName ''{0}'' is not a valid math function.
Cause: Configuration of LockoutService uses a math function that is not recognized.
Action: Correct the configuration.
Level: 1
Type: ERROR
Impact: Process
UCS-11226: Could not find the MBean. Have you configured it correctly?. Reason: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11227: The math function threw an exception. Reason: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11228: A user tried to login with the username ''{0}'', which is not a known username.
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-11231: Could not create ObjectName for LoginFailure pattern ''{0}''. Reason: {1}.
Cause: Misconfigured installation.
Action: Correct the configuration.
Level: 1
Type: ERROR
Impact: Process
UCS-11232: User ''{0}'' failed to log in. Will call all the configured LoginFailure-handlers in the system.
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-11233: User ''{0}'' exceeded the maximum number of login attempts.
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-11234: Did not find account for ''{0}''.
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-11235: Problems getting account for ''{0}''. Reason: {1}.
Cause:
Action:
Level: 1
Type: NOTIFICATION
Impact: Process
UCS-11236: Could not create SecurityService => Could not unlock account. Reason: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-11237: Failed to setup radius client pool. Reason: {0}.
Cause: Configuration of Radius Client pool is probably faulty.
Action: Verify and correct configuration of Radius Client pool.
Level: 1
Type: ERROR
Impact: Process
UCS-11238: RadiusException when authenticating: {0}.
Cause:
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30001: Charging is not allowed
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:
Level: 1
Type: WARNING
Impact: Process
UCS-30003: Failed to ACK the 2xx repsonse.
Cause: IOException received when trying to send ACK.
Action:
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:
Level: 1
Type: WARNING
Impact: Process
UCS-30005: Failed to send SIP request.
Cause: IOException when trying to send SIP request.
Action:
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:
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:
Level: 1
Type: WARNING
Impact: Process
UCS-30008: Failed to end the call leg.
Cause: Failed to send Bye.
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30009: Could not cancel call in connected state.
Cause: Illegal state to cancel call.
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30010: Failed to parse the SIP address.
Cause: Illegal SIP address
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30011: Failed to create the call.
Cause: Check the exception.
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30012: Could not find call with id: {0}.
Cause: Check the exception.
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30013: Failed to execute the action.
Cause: Check the exception.
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30014: Failed to terminate the call: {0}.
Cause: Check the exception.
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30015: Could not find the application session for call id: {0}.
Cause: Check the exception.
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30016: Failed to create SIP Invite Message.
Cause: Check the exception.
Action:
Level: 1
Type: WARNING
Impact: Process
UCS-30017: Failed to send INVITE to ''{0}'' from ''{1}''.
Cause: Check the exception.
Action:
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-30032: Could not find the WorkManager "{0}" in JNDI.
Cause: The WorkManager was not defined in the web.xml.
Action: Define the WorkManager in a resource-ref element in the web.xml
Level: 1
Type: ERROR
Impact: Process
UCS-30033: Could not call ThirdPartyCallListener at address "{1}" due to: {0}.
Cause: The registered ThirdPartyCallListener at specified address could not be invoked.
Action: Make sure that the ThirdPartyCallListener web services is available.
Level: 1
Type: WARNING
Impact: Process
UCS-30034: Could not schedule ThirdPartyCallListener work with callIdentifier "{1}" due to: {0}.
Cause: A work item for the work manager could not be scheduled
Action:
Level: 1
Type: WARNING
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-31201: JEE application name is not available: {0}.
Cause: JEE application name is not available
Action: Verify that the domain is correctly installed.
Level: 1
Type: WARNING
Impact: Process
UCS-31202: Server name is not available: {0}.
Cause: Server name is not available
Action: Verify that the domain is correctly installed.
Level: 1
Type: WARNING
Impact: Process
UCS-31203: The call detail record (CDR) could not be stored since the CDR is invalid: {0}.
Cause: The call detail record (CDR) could not be stored to the database since the CDR is invalid.
Action: Inspect the logged call detail record (CDR). Correct it and insert manually into the database.
Level: 1
Type: WARNING
Impact: Process
UCS-31204: The call detail record (CDR) could not extracted from the JMS message: {0}.
Cause: The call detail record (CDR) could not be extracted from the JMS message.