LhoScpApp

Parameter configuration at startup.

Logic application configuration.

The SCP service logic shutdown cleanly but the logic state had not returned to state NONE.

A new TCAP state machine guard timer was started while a previous one was still running.

The internal SCP state machine attempt to cancel a TCAP guard timer which is not currently running.

Request to cancel TCAP guard timer that does not match current TCAP guard timer.

The SCP service logic shutdown cleanly but we have no logic application handle.

ASN.1 structure check failure.

An error was encountered sending application statistics.

Received request to get handle for unknown peer application.

Failed discovery of an application name.

Successful discovery of an application name.

Parameter configuration at startup.

Configured application SHM information.

Parameter configuration at startup.

Configured application discovery information.

Parameter configuration at startup.

Configured IPC socket listen port.

Failed to create a new socket client handle.

EDR application discovery immediate failure.

Parameter configuration at startup.

Configured application trace level.

Parameter configuration at startup.

Configured application max trace level.

Parameter configuration at startup.

Configured application trace per second.

Parameter configuration at startup.

Configured application instance retention count.

Parameter configuration at startup.

Configured application statistics slice count.

Parameter configuration at startup.

Configured application statistics slice seconds.

Parameter configuration at startup.

Configured EDR application name.

Parameter configuration at startup.

Configured EDR stream.

Configured EDR application to utilize does not map to known application.

SNMP set request could not be completed due to update failure.

SNMP set request could not roll back updated parameter after subsequent update failure.

Parameter configuration at startup.

Application supports EDRs but they are not enabled.

Received timeout that the underlying application did not handle.

Application configuration scalar value updated.

Application configuration vector updated.

Application access has transitioned between ONLINE <=> SHUTDOWN/OFFLINE/QUIESCE.

Application access has transitioned between SHUTDOWN/OFFLINE/QUIESCE <=> ONLINE.

Instance received duplicate 'over' handler.

Instance not found when performing 'over' handler.

Failed to cancel in progress timer.

Received application message from unknown sender.

Failed to process admin queue message.

Failed to process user queue message.

Failed to query application configuration vector.

Failed to query application resource.

Failed to update application configuration scalar.

Received instance message with no context.

Configuration environment not defined.

Failed to execute variable command.

Variable command execution exited with non-zero exit code.

Variable command execution exited with non-zero exit code.

Failed to convert Hostname into address.

Hostname is not known.

Application unable to handle message.

Application is now overloaded to the point where processing is affected.

Application is no longer overloaded.

Parameter configuration at startup.

Configured application throttling parameters.

Application is now at high-load (processing is not yet affected).

Application is no longer at high-load.

Application resource vector operation successful.

Failed to thaw message byte envelope.

Failed to perform resource operation.

A single instance has received an unexpected shutdown/abort message.

Depending on the application, an "instance" may represent a

transaction, call, session, request/response pair, etc.

Cannot write EDR due to no configured EDR application.

Received EDR write event after application shutdown.

Failed to send EDR record to EDR writer process.

Received timeout that the underlying application did not handle timeout.

The timer was discarded.

A message was received that was not handled.

The message was discarded.

Attempting to send message to application handle that contains non SCALAR 'sender_context'.

Attempting to send message to application with non SCALAR context.

Attempting to send message to application with non SCALAR/HASH/ARRAY details.

Received non-administrative message while in application shutdown.

Failed to clone message parts for delivery in single-process.

Failed to queue message to application.

Attempting to send shm IPC message to application handle that contains non SCALAR 'sender_context'.

Attempting to send shm IPC message to application with non SCALAR context.

Attempting to send shm IPC message to application with non SCALAR/HASH/ARRAY details.

Failed to freeze message (N2 encoding) for delivery in socket IPC.

Failed to write message to SHM queue. Most likely full.

Attempting to send socket IPC message to application handle that contains non SCALAR 'sender_context'.

Attempting to send socket IPC message to application with non SCALAR context.

Attempting to send socket IPC message to application with non SCALAR/HASH/ARRAY details.

Failed to freeze message (BSON encoding) for delivery in socket IPC.

Failed to write message to socket queue.

Application outbound (client) socket connection has identified the peer endpoint.

Application outbound (client) socket connection has been lost.

Application outbound (client) socket connection has been ended during shutdown.

Failed to thaw message BSON byte envelope.

Application inbound (server) socket connection has identified the peer endpoint.

Failed to thaw message BSON byte envelope.

Application inbound (server) socket connection has been lost.

Failed to start new service instance for received InitialDP.

Parameter configuration at startup.

Add extended fields to IDP EDRs.

Parameter configuration at startup.

Model INAP configuration.

Parameter configuration at startup.

Automatic model INAP configuration.

Parameter configuration at startup.

SSP selector configuration.

Parameter configuration at startup.

Automatic SSP selector configuration.

Parameter configuration at startup.

Language map configuration.

Parameter configuration at startup.

SRF configuration.

Parameter configuration at startup.

Mask entered DIGITS in prompt/collect EDRs.

Received unsupported INAP/CAMEL Operation Code.

SSP TCAP not closed at end of supposedly normal call completion.

Failed to send SSP empty TCAP END at supposedly normal call completion.

Failed to encode SSP cleanup INAP/CAMEL ReleaseCall at supposedly normal call completion.

Failed to send SSP cleanup INAP/CAMEL ReleaseCall at supposedly normal call completion.

Failed to send SSP cleanup INAP/CAMEL Continue at supposedly normal call completion.

Failed to send SSP TCAP ABORT to terminate call during exception handling.

SRF in state SRF_STATE_NONE but still has open transaction.

The SRF INAP/CAMEL interaction did not cleanly terminate.

SRF is in an unexpected state at call cleanup time.

Failed to send SRF TCAP ABORT.

SRF is in open state during cleanup, but does not have active definition or transaction.

Call that supposedly ended cleanly is still running a timer for expected TCAP activity.

Failed to send SRF empty TCAP END to close the transaction at call shutdown.

Failed to send SRF TCAP ABORT to close the transaction at call shutdown.

Attempt to use SRF language for which no language transport mechanism is configured.

Attempt to use a language map which is not defined.

Requested language is not known in SSP language map.

SRF configuration has missing NAP mechanism language extension type.

SRF uses unsupported language mechanism.

The SSP has ended the TCAP transaction unexpectedly within in the SCP call state machine for a charged call.

Failed to send SSP TCAP ABORT after unable to find SSP model definition for undefined TCAP AC.

Failed to send SSP TCAP ABORT after unable to find SSP model definition.

Failed to send SSP TCAP ABORT after service logic failure handling InitialDP.

Received ERBCSM for unarmed trigger. Ignoring this event.

Received ERBCSM for unarmed trigger. Ignoring this event.

Received ERBCSM for unarmed trigger. Ignoring this event.

Received ERBCSM when A-leg is no longer active.

Received ERBCSM for unarmed trigger. Ignoring this event.

Received ERBCSM for unarmed trigger. Ignoring this event.

Received ApplyChargingReport with both callReleasedAtTcpExpiry and callActive set.

The SSP was requested to tear down the call at the end of the just-finished grant period, but does not appear to have done so.

Received ApplyChargingReport with callReleasedAtTcpExpiry but we did not request releaseIfdurationExceeded.

Received ApplyChargingReport with callActive flag set, but previously received ERBCSM(N) ABANDON EDP.

Received ApplyChargingReport with missing timeIfNoTariffSwitch.

Received ApplyChargingReport with callActive flag set following Leg Disconnect.

Received ApplyChargingReport with missing timeIfNoTariffSwitch.

Received ApplyChargingReport in call TEARDOWN following unsupported EDP.

The PlayAnnouncement request was rejected by the on-switch or external SRF.

The service logic may choose to continue, or may abandon processing.

The PromptAndCollectUserInformation request was rejected by the on-switch or external SRF.

The service logic may choose to continue, or may abandon processing.

The ConnectToResource request was rejected by the SSP.

The service logic may choose to continue, or may abandon processing.

The EstablishTemporaryConnection request was rejected by the SSP.

The service logic may choose to continue, or may abandon processing.

The AssistRequestInstructions from the external SRF did not arrive within the expected interval of sending EstablishTemporaryConnection.

A new TCAP state machine guard timer was started while a previous one was still running.

The internal SCP state machine attempt to cancel a TCAP guard timer which is not currently running.

Request to cancel TCAP guard timer that does not match current TCAP guard timer.

Timeout waiting for SpecializedResourceReport from on-switch SRF.

Message was lost, or SRF failed, or interaction duration exceeded expected maximum?

Timeout waiting for SpecializedResourceReport from external SRF.

Message was lost, or SRF failed, or interaction duration exceeded expected maximum?

Timeout waiting for PACUI result from SRF.

Message was lost, or SRF failed, or interaction duration exceeded expected maximum?

Timeout waiting for PACUI result from SRF.

Message was lost, or SRF failed, or interaction duration exceeded expected maximum?

Received ApplyChargingReport with non-zero timeIfNoTariffSwitch

even though the ERBCSM indicated that the call was Abandoned before

Answer. The non-zero time has been ignored, zero time was charged.

Requesting use of FCI while INAP/CAMEL protocol variant does not support it.

Requesting use of SRF Interaction while INAP/CAMEL protocol variant does not support it.

Requesting use of CallInformation while INAP/CAMEL protocol variant does not support all/part.

Initial ApplyCharging, service logic requested use of Release Tone while INAP/CAMEL protocol variant does not support it.

Did not receive ActivityTestResult on SSP TCAP within expected window.

Message was lost, or SSP failed?

Subsequent ApplyCharging, service logic requested use of Release Tone while INAP/CAMEL protocol variant does not support it.

Did not receive ApplyChargingReport or ERBCSM on SSP TCAP within expected window.

Received ApplyChargingReport with callReleasedAtTcpExpiry = TRUE but not all granted seconds were used.

Initial grant in seconds was longer than the supported protocol-layer maximum call duration.

Grant has been reduce to the protocol-maximum. We will also set {release_at_expiry} = true.

Extension grant in seconds will make the call longer than the supported protocol-layer maximum call duration.

Grant has been reduce to the protocol-maximum. We will also set {release_at_expiry} = true.

Received CAMEL2 ApplyChargingReport with timeIfNoTariffSwitch total used time exceeding the total granted time.

Failed to get a CorrelationID for interaction.

Received old TCAP guard timer that should have been cancelled.

Received ApplyChargingReport with RADE following Abandon ERBCSM.

Received late AssistRequestInstructions after giving up waiting.

This can occur if the SRF is late in sending ARI (or network is laggy).

Requesting use of SCI while INAP/CAMEL protocol variant does not support it.

Requesting use of FCI while INAP/CAMEL protocol variant does not support it.

Requesting use of B-Party Beep while INAP/CAMEL protocol variant does not support it.

A B-Party Beep announcement was rejected by the switch.

The call will continue regardless.

Midcall beep timer was not correctly cleared.

The midcall beep state machine wasn't closed down after clean shutdown.

Midcall beep timer was not correctly cleared.

A B-Party Beep connect to resource was rejected by the switch.

We expect to receive a subsequent failed PlayAnnouncement error.

The call will continue regardless.

Received message that did not contain either an instance or transaction context.

Failed to send TCAP transaction check response notification.

Received message for expired instance_idx or transaction.

Message discarded.

Received TCAP transaction check request for unknown transaction.

Failed to send TCAP transaction check response for transaction.

Received message without message type.

Message discarded.

Received message without send context.

Message discarded.

Received associated TCAP begin for unknown instance.

Received a second TCAP_BEGIN for an already-open transaction.

Received TCAP begin that exceeded the maximum expiry seconds.

TCAP begin discarded.

TCAP begin rejected.

Received message without instance/transaction context.

Message discarded.

Received message without sender context.

Message discarded.

Received message for unknown/expired instance.

Message discarded.

Received message for unknown instance transaction.

Message discarded.

Received unsupported TCAP type.

Unsupported component element.

Component discarded.

Attempt to send invalid component structure.

Attempted to close unknown transaction.

Attempted to close transaction that is already closed.

Attempt to set returned application context on unknown transaction.

Attempt to set result dialogue parameters on unknown transaction.

Attempt to get application context from unknown transaction.

Attempt to get application context from unknown transaction.

Duplicate initialise method call on non-closed transaction.

Attempt to invoke unknown transaction.

Attempt to get last sent opcode for unknown transaction.

Attempt to get last received invoke ID for unknown transaction.

Failed to abort open TCAP transaction at instance shutdown.

Attempt to get remote SCCP address from unknown transaction.

Attempt to get TIDs from unknown transaction.

Attempt to get local SCCP address from unknown transaction.

Split of undefined or non scalar element.

Index non array.

Filter non-array or hash.

Expected hash but got single entry array with non hash value.

Non hash value.

Invalid regular expression pattern.

Notification of the localised SNMP v3 authentication key generated from a plaintext password.

For strict compatibility with SNMP v3, authentication keys should be configured instead of passwords.

Notification of the localised SNMP v3 privacy key generated from a plaintext password.

For strict compatibility with SNMP v3, privacy keys should be configured instead of passwords.

Mis-formed UDP datagram detected.

Received invalid SCTP notification.

Received invalid SCTP notification.

Received invalid SCTP association change notification.

Failed to send UDP datagram with invalid attribute. Presumably bad destination address/port.

SIGTRAN SCTP connection has been restarted from the far end.

This indicates that the far-end lost and restored contact, prior to this

end having noticed that the connection association was fully lost.

Received unsupported SCTP association change notification.

Received invalid SCTP peer address change notification.

SIGTRAN SCTP connection peer is down (unreachable or potentially failed).

Note that each SCTP connection may have multiple peers, and the connection

communication will function as long as one or more other peers are still up.

SIGTRAN SCTP connection peer is up (available or confirmed).

Received unexpected SCTP notification.

Failed to send UDP datagram with invalid size. Presumably exceeded MTU for route.

Logged connection failed during connection attempt or after connecting.

A ClientConnection initiated by is now connected, meaning

that the socket transport layer handshake is completed, and if applicable

the SSL handshake is also complete. The application may now initiate

any protocol-specific validation/login process.

Non-logged connection failed during connection attempt or after connecting.

Connection has become congested.

Connection is no longer congested. This may be because the Connection has terminated.

Application startup.

Creating single UDP connection.

Socket bind failed.

Socket bind & listen succeeded.

Error accepting messages on local connection.

Failed to accept inbound TCP connection.

Failed to process new inbound connection.

Application startup.

SCTP connection accepted connection from remote IP address.

SSL is not supported on non-TCP protocol (e.g. UDP).

SNMP trap was not able to be queued for sending.

An N2SVCD class is incorrectly specified.

The same warning ID was logged too many times in a fixed interval.

SNMP application discovery immediate failure.

No SNMP user is defined for outbound SNMP traps.

Messages will be sent without security.

Queued SNMP trap was discarded due to too many pending traps in

the SNMP broker.

Queued SNMP v3 trap was was unable to be encoded.

Queued SNMP v2c trap was was unable to be encoded.

Target SNMP application is invalid or not available for

outbound proxying of SNMP trap.

Trap will not be sent.

SNMP trap was was unable to be passed to an SNMP application

for outbound proxying.

Trap will not be sent.

Queued SNMP trap was discarded due to too many pending traps in

the SNMPb broker client.

SNMP trap failed to send for a reason other than connection refused.

The trap will be discarded.