This pseudo class documents the set of messages that can be
issued by the IBM Telecom Web Services Server components.
- SOAM0001I: Privacy Check reported the following error: %1.
- Explaination:
- Privacy Check reported the following error: %1.
- Response:
- Contact the system administrator.
- SOAM0002I: Common Layer reported the following error: %1.
- Explaination:
- Common Layer reported the following error: %1.
- Response:
- Contact the system administrator.
- SOAM0003I: Admission Control reported the following error: %1.
- Explaination:
- Admission Control reported the following error: %1.
- Response:
- Contact the system administrator.
- SOAM0004I: No message is defined for fault/alarm %1.
- Explaination:
- No message is defined for fault/alarm %1.
- Response:
- Contact the system administrator.
- SOAM0005I: Traffic Shaper reported the following error: %1.
- Explaination:
- Traffic Shaper reported the following error: %1.
- Response:
- Contact the system administrator.
- SOAM0006I: Service %1 was not implemented.
- Explaination:
- Service %1 was not implemented.
- Response:
- Contact the system administrator.
- SOAM0007I: Asynchronous Service Implementation reported the following error: %1.
- Explaination:
- Asynchronous Service Implementation reported the following error: %1.
- Response:
- Contact the system administrator.
- SOAM0008I: Asynchronous service message %1 was not enqueued.
- Explaination:
- Asynchronous service message %1 was not enqueued.
- Response:
- Contact the system administrator.
- SOAM0009I: The backend service implementation encountered an exception: %1.
- Explaination:
- The backend service implementation encountered an exception: %1.
- Response:
- Contact the system administrator.
- SOAM0010I: Address plan %1 was not available.
- Explaination:
- Address plan %1 was not available.
- Response:
- Contact the system administrator.
- SOAM0011I: The transaction state transition took too long: %1.
- Explaination:
- The transaction state transition took too long: %1.
- Response:
- Contact the system administrator.
- SOAM0012I: Service usage record writing reported the following error: %1.
- Explaination:
- Service usage record writing reported the following error: %1.
- Response:
- Contact the system administrator.
- SOAM0013I: Group resolution is disabled: %1.
- Explaination:
- Group resolution is disabled: %1.
- Response:
- Contact the system administrator
- SOAM0018E: The request contains incorrect semantic content or is not structured properly.
- Explaination:
- The request contains incorrect semantic content or is not structured properly.
- Response:
- Check the input values and resend the request.
- SOAM0019E: The Notification Management component could not process this request due to a service error.
- Explaination:
- The Notification Management component could not process this request due to a service error.
- Response:
- Contact the system administrator.
- SOAM0020E: The Notification Management component has no current or live notification with the specified requester, service and correlator.
- Explaination:
- The Notification Management component has no current or live notification with the specified requester, service and correlator.
- Response:
- Check the request to ensure that the requester, service, and correlator identify a known notification. Then resend the request.
- SOAM0021E: The specified requester, service, and correlator are already registered with Notification Management.
- Explaination:
- The specified requester, service, and correlator are already registered with Notification Management.
- Response:
- Check the request to ensure that the requester, service, and correlator are not already registered with Notification Management. Then resend the request.
- SOAM0800EI: An unexpected error occurred %1.
- Explaination:
- Internal Error: The following unexpected error occurred: %1 .
- Response:
- Contact the system administrator.
- SOAM0801EI: CommonLayer reports null response.
- Explaination:
- The CommonLayer reports that it has received a null response.
- Response:
- Contact the system administrator.
- SOAM0802EI: Database reports SQL exception %1.
- Explaination:
- The database reports the following SQL exception: %1.
- Response:
- Contact the system administrator.
- SOAM0803EI: An unexpected database error occurred: %1. The transaction ID is %2.
- Explaination:
- Internal Error: An unexpected database error occurred: %1. The transaction ID is %2.
- Response:
- Contact the system administrator.
- SOAM0804EI: The address pattern %1 was not valid.
- Explaination:
- The address pattern %1 was not valid.
- Response:
- Contact the system administrator.
- SOAM0805EI: The Third Party Call Web Service could not read the service policy value for %1. The error was %2.
- Explaination:
- The Third Party Call Web Service could not read the service policy value for %1. The error was %2.
- Response:
- Contact the system administrator.
- SOAM0806EI: Failed on policy:%1=%2 while field:%3=%4.
- Explaination:
- Failed on policy:%1=%2 while field:%3=%4.
- Response:
- Contact the system administrator.
- SOAM0807EI: The specified service policy was not valid. The default value will be used.
- Explaination:
- The specified service policy was not valid. The default value will be used.
- Response:
- Contact the system administrator.
- SOAM0808EI: The Third Party Call Web service could not read the management bean value for %1. The error was %2.
- Explaination:
- The Third Party Call Web service could not read the management bean value for %1. The error was %2.
- Response:
- Contact the system administrator.
- SOAM0809EI: Failed on MBean attribute:%1=%2 while field:%3=%4.
- Explaination:
- Failed on MBean attribute:%1=%2 while field:%3=%4.
- Response:
- Contact the system administrator.
- SOAM0810EI: Internal Error: An attempt was made to get a service usage record for an unknown operation (%1).
- Explaination:
- Internal Error: An attempt was made to get a service usage record for an unknown operation (%1).
- Response:
- Contact the system administrator.
- SOAM0811EI: Could not clean up a %1 resource: %2.
- Explaination:
- Could not clean up a %1 resource: %2.
- Response:
- Contact the system administrator.
- SOAM0812EI:The JNDI Name was not resolved %1.
- Explaination:
- Internal Error: The JNDI Name was not resolved %1.
- Response:
- Contact the system administrator
- SOAM0900EI: The service implementation was not found.
- Explaination:
- The service implementation was not found
- Response:
- Contact the system administrator.
- SOAM0901EI: A server internal error occurred.
- Explaination:
- A server internal error occurred.
- Response:
- Contact the system administrator.
- SOAM0902EI: A database failure occurred.
- Explaination:
- A database failure occurred.
- Response:
- Contact the system administrator.
- SOAM0903EI: Could not discover MPCC SCF using the specified name.
- Explaination:
- Could not discover MPCC SCF using the specified name.
- Response:
- Contact the system administrator.
- SOAM0904EI: The operation %1 is not supported by the Parlay gateway in its current configuration.
- Explaination:
- The operation %1 is not supported by the Parlay gateway in its current configuration.
- Response:
- Contact the system administrator.
- SOAM0905EI: An error occurred while invoking an EJB operation: %1.
- Explaination:
- An error occurred while invoking an EJB operation: %1.
- Response:
- Contact the system administrator.
- SOAM1503E: The delivery status data records could not be retrieved for the following reason: %1.
- Explaination:
- The delivery status data records could not be retrieved for the following reason %1.
- Response:
- Contact the system administrator.
- SOAM1506E: The correlator provided is in use: %1.
- Explaination:
- The correlator provided is in use: %1.
- Response:
- Select a correlator that is not already in use, and retry.
- SOAM1508E: The correlator provided is in use: %1.
- Explaination:
- The correlator provided is in use: %1.
- Response:
- Select a correlator that is not already in use, and retry.
- SOAM1509E: The criteria provided are in use: %1.
- Explaination:
- The criteria provided are in use: %1.
- Response:
- Select criteria that are not already in use, and retry.
- SOAM1520I: Null input value for the addresses parameter.
- Explaination:
- No value was specified for the addresses parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1521I: Empty string input value for an address parameter.
- Explaination:
- An empty string was specified for one of the address parameters. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1522I: Null input value for the message parameter.
- Explaination:
- No value was specified for the message parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1523I: Empty string input value for the message parameter.
- Explaination:
- An empty string was specified for the message parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1525E: Creating Send SMS data record failed.
- Explaination:
- An attempt to create a Send SMS data record was not successful.
- Response:
- Contact the system administrator.
- SOAM1526I: Null input value for the requestIdentifier parameter.
- Explaination:
- No value was specified for the requestIdentifier parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1527I: Empty string input value for the requestIdentifier parameter.
- Explaination:
- An empty string was specified for the requestIdentifier parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1528I: Could not find delivery status for this request identifier.
- Explaination:
- Could not find delivery status for this request identifier.
- Response:
- Check that you have specified a valid value for the request identifier, and retry.
- SOAM1529E: Unknown delivery status value.
- Explaination:
- Unknown delivery status value.
- Response:
- Contact the system administrator.
- SOAM1530E: Requester ID is null in MDS context.
- Explaination:
- Requester ID is null in MDS context.
- Response:
- Contact the system administrator.
- SOAM1531E: MDS context is null.
- Explaination:
- MDS context is null.
- Response:
- Contact the system administrator.
- SOAM1532E: Error when creating notification record for SendSms request.
- Explaination:
- Error when creating notification record for SendSms request.
- Response:
- Contact the system administrator.
- SOAM1533E: Problem obtaining Parlay Connector.
- Explaination:
- Problem obtaining Parlay Connector.
- Response:
- Make sure the Parlay Connector is started.
- SOAM1534I: Privacy check failed for this address.
- Explaination:
- Privacy check failed for this address.
- Response:
- Check to make sure that privacy is configured correctly for this address.
- SOAM1535I: Empty string input value for correlator parameter.
- Explaination:
- An empty string was specified for the correlator parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1536I: Null input value for correlator parameter.
- Explaination:
- No value was specified for the correlator parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1537I: Null input value for reference parameter.
- Explaination:
- No value was specified for the correlator parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1538I: Null input value for endpoint parameter.
- Explaination:
- No value was specified for the endpoint parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1539I: Empty string input value for endpoint parameter.
- Explaination:
- An empty string was specified for the endpoint parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1540I: Null input value for interfaceName parameter.
- Explaination:
- No value was specified for the interfaceName parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1541I: Empty string input value for interfaceName parameter.
- Explaination:
- An empty string was specified for the interfaceName parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1542I: Null input value for smsServiceActivationNumber parameter.
- Explaination:
- No value was specified for the smsServiceActivationNumber parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1543I: Empty string input value for smsServiceActivationNumber parameter.
- Explaination:
- An empty string was specified for the smsServiceActivationNumber parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1544I: Null input value for registrationIdentifier parameter.
- Explaination:
- No value was specified for the registrationIdentifier parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1545I: Empty string input value for registrationIdentifier parameter.
- Explaination:
- An empty string was specified for the registrationIdentifier parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1555E: Unexpected operation for this method.
- Explaination:
- This method is not expected to be called by the operation being performed.
- Response:
- Contact the system administrator.
- SOAM1556E: URISyntaxException during creation of URI.
- Explaination:
- A URISyntaxException occurred during creation of the URI.
- Response:
- Contact the system administrator.
- SOAM1557E: Error creating notification record for startNotification call.
- Explaination:
- An error occurred during creation of the notification record for the startNotification call.
- Response:
- Contact the system administrator.
- SOAM1558I: The SMS service activation number was not valid.
- Explaination:
- The SMS service activation number was not valid.
- Response:
- Enter a valid value for the SMS service activation number, and retry.
- SOAM1559I: The SMS service is disabled.
- Explaination:
- The SMS service is disabled.
- Response:
- Enable the SMS service if you want to use it.
- SOAM1560W: Charging is not supported.
- Explaination:
- Charging is not supported.
- Response:
- Change the service policy setting if you want to support charging.
- SOAM1561W: The registration identifier does not exist.
- Explaination:
- The registration identifier does not exist.
- Response:
- Check that you have specified a valid value for the registration identifier, and retry.
- SOAM1562I: Null input value for the image parameter.
- Explaination:
- No value was specified for the image parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1563I: Length 0 for image parameter.
- Explaination:
- A string of zero length was specified for the image parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1564I: Null input value for the ringtone parameter.
- Explaination:
- No value was specified for the ringtone parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1565I: Empty string input value for ringtone parameter.
- Explaination:
- An empty string was specified for the ringtone parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1566W: Problem in UDH Encoding.
- Explaination:
- Problem in UDH Encoding.
- Response:
- Check that you have specified a valid value for UDH Encoding, and retry.
- SOAM1567E: The service policy %1 is not in the MdsContext.
- Explaination:
- The service policy %1 is not in the MdsContext.
- Response:
- Contact the system administrator.
- SOAM1568E: The service policy value is not as expected. Service Policy: %1. Policy Value: %2
- Explaination:
- The service policy value is not as expected. Service Policy: %1. Policy Value: %2
- Response:
- Contact the system administrator.
- SOAM1569I: Null input value for the smsFormat parameter.
- Explaination:
- No value was specified for the SmsFormat parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM1575E: Could not find the notification data for the correlator.
- Explaination:
- Could not find the notification data for the correlator.
- Response:
- Contact the system administrator.
- SOAM1576E: There is no connection to the database.
- Explaination:
- There is no connection to the database.
- Response:
- Contact the system administrator.
- SOAM1577E: An unknown error occurred.
- Explaination:
- An unknown error occurred. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1578E: Could not create the record of the session object.
- Explaination:
- Could not create the record of the session object. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1579E: A problem occurred while updating the status for the destination.
- Explaination:
- A problem occurred while updating the status for the destination. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1580E: A problem occurred while finding the segment status for the transaction.
- Explaination:
- A problem occurred while finding the segment status for the transaction. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1581E: Could not find the notification data for the assignment ID.
- Explaination:
- Could not find the notification data for the assignment ID. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1582E: A problem occurred while finding the first word of the message.
- Explaination:
- A problem occurred while finding the first word of the message. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1583E: A problem occurred with a key when storing the receive data.
- Explaination:
- A problem occurred with a key when storing the receive data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1584E: A problem occurred with a create operation when storing the receive data.
- Explaination:
- A problem occurred with a create operation when storing the receive data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1585E: Could not find the notification data for this send transaction ID.
- Explaination:
- Could not find the notification data for this send transaction ID. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1586E: Could not perform the notification for this transaction ID.
- Explaination:
- Could not perform the notification for this transaction ID. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1587E: Could not find the notification data for this receive transaction ID.
- Explaination:
- Could not find the notification data for this receive transaction ID. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1588E: Could not find the notification data to delete.
- Explaination:
- Could not find the notification data to delete. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1589E: Could not remove the session object for the assignment ID.
- Explaination:
- Could not remove the session object for the assignment ID. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1590E: Could not find expired send data.
- Explaination:
- Could not find expired send data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1591E: Could not remove expired send data.
- Explaination:
- Could not remove expired send data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1592E: Could not find expired notification data.
- Explaination:
- Could not find expired notification data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1593E: Could not remove expired notification data.
- Explaination:
- Could not remove expired notification data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1594E: Could not find expired received data.
- Explaination:
- Could not find expired received data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1595E: Could not remove expired received data.
- Explaination:
- Could not remove expired received data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1596E: Could not find expired session object data.
- Explaination:
- Could not find expired session object data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1597E: Could not remove expired session object data.
- Explaination:
- Could not remove expired session object data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1598E: Could not reach a client to notify it of a Notification event.
- Explaination:
- Could not reach a client to notify it of a Notification event.
- Response:
- Check the endpoint address and the PxNotification configuration.
- SOAM1599E: Could not access a table: the table is not defined, or the initial data source was not created.
- Explaination:
- Could not access a table: the table is not defined, or the initial data source was not created.
- Response:
- Make sure that the table you are trying to access exists, and check the configuration for the data source.
- SOAM1600E: The database service is not running, or database authentication failed.
- Explaination:
- The database service is not running, or database authentication failed.
- Response:
- Start the database service or check the authentication credentials. Then retry.
- SOAM1650E: The service policy service.config.target.Aliases is not in the MdsContext.
- Explaination:
- The service policy service.config.target.Aliases is not in the MdsContext.
- Response:
- Contact the system administrator.
- SOAM1651E: The service policy service.config.messaging.ConfirmDelivery is not in the MdsContext.
- Explaination:
- The service policy service.config.messaging.ConfirmDelivery is not in the MdsContext.
- Response:
- Contact the system administrator.
- SOAM1652E: No alias names were defined in the Administration Console.
- Explaination:
- No alias names were defined in the Administration Console.
- Response:
- Contact the system administrator.
- SOAM1653E: An MBeanException occurred while attempting to get the MBean attribute.
- Explaination:
- An MBeanException occurred while attempting to get the MBean attribute.
- Response:
- Contact the system administrator.
- SOAM1654E: could not connect to the specified server.
- Explaination:
- Could not connect to the specified server. A ConnectorException was encountered.
- Response:
- Contact the system administrator
- SOAM1655E: An internal error occurred in the SMPP Session Manager.
- Explaination:
- An internal error occurred in the SMPP Session Manager (SmppSessionManager).
- Response:
- Contact the system administrator.
- SOAM1656E: An error occurred while sending the message to the SMSC.
- Explaination:
- An error occurred while sending the message to the SMSC.
- Response:
- Contact the system administrator.
- SOAM1657E: The Enquire Link Response message was not sent.
- Explaination:
- The Enquire Link Response message was not sent.
- Response:
- Contact the system administrator.
- SOAM1658E: The Deliver SM Response message was not sent.
- Explaination:
- The Deliver SM Response message was not sent.
- Response:
- Contact the system administrator.
- SOAM1659E: The Generic Non-Acknowledge message was not sent.
- Explaination:
- The Generic Non-Acknowledge message was not sent.
- Response:
- Contact the system administrator.
- SOAM1660E: No alias name was defined in the Administration Console. %1
- Explaination:
- No alias name was defined in the administration console. %1
- Response:
- Contact the system administrator.
- SOAM1663E: The specified endpoint URI for Notification was not valid.
- Explaination:
- The specified endpoint URI for Notification was not valid.
- Response:
- Enter the correct URI and retry.
- SOAM1664E: Null input value for the charging description.
- Explaination:
- No value was specified for the charging description. A value must be specified.
- Response:
- Enter a valid charging description and retry.
- SOAM1665E: Empty string input value for the charging description.
- Explaination:
- An empty string was specified for the charging description. A value must be specified.
- Response:
- Enter a valid charging description and retry.
- SOAM1800E: The service policy service.standard.VirtualNumber is not in the MdsContext.
- Explaination:
- The service policy service.standard.VirtualNumber is not in the MdsContext.
- Response:
- Contact the system administrator.
- SOAM1801E: The service policy service.config.messaging.ConfirmDelivery is not in the MdsContext.
- Explaination:
- The service policy service.config.messaging.ConfirmDelivery is not in the MdsContext.
- Response:
- Contact the system administrator
- SOAM1802E: An AttributeNotFoundException occurred while attempting to get the MBean attribute.
- Explaination:
- An AttributeNotFoundException occurred while attempting to get the MBean attribute.
- Response:
- Contact the system administrator.
- SOAM1803E: An MBeanException occurred while attempting to get the MBean attribute.
- Explaination:
- An MBeanException occurred while attempting to get the MBean attribute.
- Response:
- Contact the system administrator.
- SOAM1804E: A ReflectionException occurred while attempting to get the MBean attribute.
- Explaination:
- A ReflectionException occurred while attempting to get the MBean attribute.
- Response:
- Contact the system administrator.
- SOAM1805E: An openMultiMediaMessaging Parlay call failed with an exception.
- Explaination:
- An openMultiMediaMessaging Parlay call failed with an exception.
- Response:
- Contact the system administrator.
- SOAM1806E: An openMultiMediaMessaging Parlay call failed with a P_INVALID_ADDRESS exception.
- Explaination:
- An openMultiMediaMessaging Parlay call failed with a P_INVALID_ADDRESS exception.
- Response:
- Contact the system administrator.
- SOAM1807E: close call for IpMultiMediaMessaging reference failed.
- Explaination:
- close call for IpMultiMediaMessaging reference failed.
- Response:
- Contact the system administrator.
- SOAM1808E: A createNotification call for IpMultiMediaMessagingManager failed.
- Explaination:
- A createNotification call for IpMultiMediaMessagingManager failed.
- Response:
- Contact the system administrator.
- SOAM1809E: A destroyNotification call for IpMultiMediaMessagingManager failed.
- Explaination:
- A destroyNotification call for IpMultiMediaMessagingManager failed.
- Response:
- Contact the system administrator.
- SOAM1810E: A sendMessageReq call for IpMultiMediaMessaging failed.
- Explaination:
- A sendMessageReq call for IpMultiMediaMessaging failed.
- Response:
- Contact the system administrator.
- SOAM1811E: A setConfirmDelivery call for MmmCallBack failed.
- Explaination:
- A setConfirmDelivery call for MmmCallBack failed.
- Response:
- Contact the system administrator.
- SOAM1812E: Could not get EJB reference for MmmCallBack.
- Explaination:
- Could not get EJB reference for MmmCallBack.
- Response:
- Contact the system administrator.
- SOAM2003E: The delivery status data records could not be retrieved for the following reason: %1.
- Explaination:
- The delivery status data records could not be retrieved for the following reason: %1.
- Response:
- Contact the system administrator.
- SOAM2006E: The correlator provided is in use: %1.
- Explaination:
- The correlator provided is in use: %1.
- Response:
- Enter a valid value and retry.
- SOAM2008E: The correlator provided is in use: %1.
- Explaination:
- The correlator provided is in use: %1.
- Response:
- Enter a valid value and retry.
- SOAM2009E: The criteria provided is in use: %1.
- Explaination:
- The criteria provided is in use: %1.
- Response:
- Enter a valid value and retry.
- SOAM2020I: Null input value for the addresses parameter.
- Explaination:
- No value was specified for the addresses parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2021I: Empty string input value for one of the address parameters.
- Explaination:
- An empty string was specified for one of the address parameters. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2025E: Creating Send Message data record failed.
- Explaination:
- Creating Send Message data record failed.
- Response:
- Contact the system administrator.
- SOAM2026I: Null input value for requestIdentifier parameter.
- Explaination:
- No value was specified for the requestIdentifier parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2027I: Empty string input value for requestIdentifier parameter.
- Explaination:
- An empty string was specified for the requestIdentifier parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2028I: Could not find the delivery status for this request identifier.
- Explaination:
- Could not find the delivery status for this request identifier.
- Response:
- Enter a valid value and retry.
- SOAM2029E: Unknown delivery status value.
- Explaination:
- The value specified for delivery status was unknown.
- Response:
- Contact the system administrator.
- SOAM2030E: The requester ID is null in the MDS context.
- Explaination:
- The requester ID is null in the MDS context.
- Response:
- Contact the system administrator.
- SOAM2031E: The MDS context is null.
- Explaination:
- The MDS context is null.
- Response:
- Contact the system administrator.
- SOAM2032E: An error occurred while creating notification record for SendMessage request.
- Explaination:
- An error occurred while creating notification record for SendMessage request.
- Response:
- Contact the system administrator.
- SOAM2035I: Empty string input value for correlator parameter.
- Explaination:
- An empty string was specified for the correlator parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2036I: Null input value for correlator parameter.
- Explaination:
- No value was specified for the correlator parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2037I: Null input value for reference parameter.
- Explaination:
- No value was specified for the reference parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2038I: Null input value for endpoint parameter.
- Explaination:
- No value was specified for the endpoint parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2039I: Empty string input value for endpoint parameter.
- Explaination:
- An empty string was specified for the endpoint parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2040I: Null input value for interfaceName parameter.
- Explaination:
- No value was specified for the interfaceName parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2041I: Empty string input value for interfaceName parameter.
- Explaination:
- An empty string was specified for the interfaceName parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2042I: Null input value for messageServiceActivationNumber parameter.
- Explaination:
- No value was specified for the messageServiceActivationNumber parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2043I: Empty string input value for messageServiceActivationNumber parameter.
- Explaination:
- An empty string was specified for the messageServiceActivationNumber parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2044I: Null input value for registrationIdentifier parameter.
- Explaination:
- No value was specified for the registrationIdentifier parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2045I: Empty string input value for registrationIdentifier parameter.
- Explaination:
- An empty string was specified for the registrationIdentifier parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2046I: Null input value for messageRefIdentifier parameter.
- Explaination:
- No value was specified for the messageRefIdentifier parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2047I: Empty string input value for messageRefIdentifier parameter.
- Explaination:
- An empty string was specified for the messageRefIdentifier parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM2048I: The type value specified for messageRefIdentifier was not valid.
- Explaination:
- The type value specified for messageRefIdentifier was not valid.
- Response:
- Enter a valid value and retry.
- SOAM2055E: Unexpected operation for this method.
- Explaination:
- This method is not expected to be called by this operation.
- Response:
- Contact the system administrator
- SOAM2057E: An error occurred creating a notification record for the startNotification call.
- Explaination:
- An error occurred while creating a notification record for the startNotification call.
- Response:
- Contact the system administrator
- SOAM2058I: The Message Service activation number was not valid.
- Explaination:
- The Message service activation number was not valid.
- Response:
- Enter valid value for message service activation number.
- SOAM2059I: The MMS service is disabled.
- Explaination:
- The MMS service is disabled.
- Response:
- Enable the MMS service and retry.
- SOAM2060W: Charging is not supported.
- Explaination:
- Charging is not supported.
- Response:
- Change the service policy setting if you want to support charging.
- SOAM2061W: The value specified for registration identifier does not exist.
- Explaination:
- The value specified for registration identifier does not exist.
- Response:
- Enter a valid value and retry.
- SOAM2062W: The message with this MessageRef Identifier has expired.
- Explaination:
- The message with this MessageRef Identifier has expired.
- Response:
- Enter a valid value and retry.
- SOAM2063W: The value specified for MessageRef Identifier does not exist.
- Explaination:
- The value specified for MessageRef Identifier does not exist.
- Response:
- Enter a valid value and retry.
- SOAM2064W: The message with this MessageRef Identifier is new and has not been retrieved.
- Explaination:
- The message with this MessageRef Identifier is new and has not been retrieved.
- Response:
- Retrieve new messages, and retry.
- SOAM2069E: Could not find an attachment ID corresponding to this transaction ID.
- Explaination:
- Could not find an attachment ID corresponding to this transaction ID.
- Response:
- Contact the system administrator.
- SOAM2070E: Could not find attachment data corresponding to this attachment ID.
- Explaination:
- Could not find attachment data corresponding to this attachment ID.
- Response:
- Contact the system administrator.
- SOAM2071E: The attachments were not deleted. Could not find an attachment ID corresponding to this transaction ID.
- Explaination:
- The attachments were not deleted. Could not find an attachment ID corresponding to this transaction ID.
- Response:
- Contact the system administrator.
- SOAM2072E: The attachments were not deleted. Could not find attachment data corresponding to this attachment ID.
- Explaination:
- The attachments were not deleted. Could not find attachment data corresponding to this attachment ID.
- Response:
- Contact the system administrator.
- SOAM2073E: A problem occurred while deleting attachment content.
- Explaination:
- A problem occurred while deleting attachment content.
- Response:
- Contact the system administrator.
- SOAM2074E A problem occurred while deleting attachment metadata.
- Explaination:
- A problem occurred while deleting attachment metadata.
- Response:
- Contact the system administrator.
- SOAM2075E: Could not find the notification data for the correlator.
- Explaination:
- Could not find the notification data for the correlator.
- Response:
- Contact the system administrator.
- SOAM2076E: There is no connection to the database.
- Explaination:
- There is no connection to the database.
- Response:
- Contact the system administrator.
- SOAM2077E: An unknown error occurred.
- Explaination:
- An unknown error occurred. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2079E: A problem occurred while updating the status for the destination.
- Explaination:
- A problem occurred while updating the status for the destination. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2080E: A duplicate key problem occurred while storing attachment content.
- Explaination:
- A duplicate key problem occurred while storing attachment content. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2081E: A problem occurred while storing attachment content.
- Explaination:
- A problem occurred while storing attachment content. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2082E: A problem occurred while storing attachment metadata.
- Explaination:
- A problem occurred while storing attachment metadata. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2083E: A key-related problem occurred while storing the receive data.
- Explaination:
- A key-related problem occurred while storing the receive data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2084E: A create problem occurred while storing the receive data.
- Explaination:
- A create problem occurred while storing the receive data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2085E: Could not find the notification data for this send transaction ID.
- Explaination:
- Could not find the notification data for this send transaction ID. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2086E: Could not perform the notification for this transaction ID.
- Explaination:
- Could not perform the notification for this transaction ID. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2088E: Could not find the notification data to delete.
- Explaination:
- Could not find the notification data to delete. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2090E: Could not find expired send data.
- Explaination:
- Could not find expired send data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2091E: Could not remove expired send data.
- Explaination:
- Could not remove expired send data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2092E: Could not find expired notification data.
- Explaination:
- Could not find expired notification data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2093E: Could not remove expired notification data.
- Explaination:
- Could not remove expired notification data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2094E: Could not find expired received data.
- Explaination:
- Could not find expired received data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2095E: Could not remove expired received data.
- Explaination:
- Could not remove expired received data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2096E: Could not find expired session object data.
- Explaination:
- Could not find expired session object data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2097E: Could not remove expired session object data. Check the error log.
- Explaination:
- Could not remove expired session object data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM2098E: Could not reach a client to notify it of a Notification event.
- Explaination:
- Could not reach a client to notify it of a Notification event.
- Response:
- Check the endpoint address and the PxNotification configuration, and retry.
- SOAM2099E: The table is not defined, or the data source could not be created.
- Explaination:
- The table you are trying to access is not defined, or a problem occurred during initial creation of the data source.
- Response:
- Make sure that the table exists, or check the data source configuration.
- SOAM2148E: The service policy %1 is not in the MdsContext.
- Explaination:
- The service policy %1 is not in the MdsContext.
- Response:
- Contact the system administrator.
- SOAM2149E: The service policy value is not as expected. Service Policy: %1. Policy Value: %2
- Explaination:
- The service policy value is not as expected. Service Policy: %1. Policy Value: %2
- Response:
- Contact the system administrator.
- SOAM2150E: The service policy service.common.target.Aliases is not in the MdsContext.
- Explaination:
- The service policy service.common.target.Aliases is not in the MdsContext.
- Response:
- Contact the system administrator.
- SOAM2151E: The service policy service.config.messaging.ConfirmDelivery is not in the MdsContext.
- Explaination:
- The service policy service.config.messaging.ConfirmDelivery is not in the MdsContext.
- Response:
- Contact the system administrator.
- SOAM2152E: No alias names were defined in the Administration Console.
- Explaination:
- No alias names were defined in the Administration Console.
- Response:
- Contact the system administrator.
- SOAM2153E: An MBeanException occurred while attempting to get the MBean attribute.
- Explaination:
- An MBeanException occurred while attempting to get the MBean attribute.
- Response:
- Contact the system administrator.
- SOAM2154E: The MM7 JCA connector was found.
- Explaination:
- A ConnectorException occurred. The MM7 JCA connector was not found.
- Response:
- Contact the system administrator.
- SOAM2156E: An error occurred while sending the message to the MMSC.
- Explaination:
- An error occurred while sending the message to the MMSC.
- Response:
- Contact the system administrator.
- SOAM2160E: No alias name was defined in the Administration Console. %1
- Explaination:
- No alias name was defined in the Administration Console. %1
- Response:
- Contact the system administrator.
- SOAM2163E: The specified endpoint URI for Notification was not valid.
- Explaination:
- The specified endpoint URI for Notification was not valid.
- Response:
- Enter the correct URI and retry.
- SOAM3800E: An unexpected internal error occurred within the Terminal Status service.
- Explaination:
- An unexpected internal error occurred within the Terminal Status service.
- Response:
- Contact the system administrator.
- SOAM3808W: An internal error occurred. An attempt was made to get a service usage record for an unknown Terminal Status operation.
- Explaination:
- An internal error occurred. An attempt was made to get a service usage record for an unknown Terminal Status operation.
- Response:
- Contact the system administrator.
- SOAM3809E: An unexpected database error occurred in the Terminal Status notification service.
- Explaination:
- An unexpected database error occurred in the Terminal Status notification service.
- Response:
- Retry the request. If the problem persists, contact the system administrator.
- SOAM3810E: Could not create a database entry for a Terminal Status notification service request.
- Explaination:
- Could not create a database entry for a Terminal Status notification service request.
- Response:
- Retry the request. If the problem persists, contact the system administrator.
- SOAM3811E: Could not locate a database entry for a Terminal Status notification service request.
- Explaination:
- Could not locate a database entry for a Terminal Status notification service request.
- Response:
- Retry the request. If the problem persists, contact the system administrator.
- SOAM3812W: Could not reach a client to notify it of a Terminal Status notification event.
- Explaination:
- Could not reach a client to notify it of a Terminal Status notification event.
- Response:
- Check the endpoint address and the PxNotification configuration, and retry.
- SOAM3813W: Could not clean up a Terminal Status notification resource. An error occurred.
- Explaination:
- Could not clean up a Terminal Status notification resource. An error occurred.
- Response:
- Retry the request. If the problem persists, contact the system administrator.
- SOAM3814E: An internal error occurred while attempting to resolve a Terminal Status JNDI reference.
- Explaination:
- An internal error occurred while attempting to resolve a Terminal Status JNDI reference.
- Response:
- Contact the system administrator.
- SOAM3815I: The Terminal Status service could not read a service policy value.
- Explaination:
- The Terminal Status service could not read a service policy value.
- Response:
- Make sure a valid value is specified for the service policy, and retry.
- SOAM3816I: The Terminal Status service could not read a management bean value.
- Explaination:
- The Terminal Status service could not read a management bean value.
- Response:
- Make sure a valid value is specified for the management bean, and retry.
- SOAM3900E: A Terminal status service request failed. A Parlay error occurred.
- Explaination:
- A Terminal Status service request failed. A Parlay error occurred.
- Response:
- Check the Parlay configuration and the Parlay gateway, and retry.
- SOAM3902E: A Terminal Status service request failed. The synchronization object timed out.
- Explaination:
- A Terminal Status service request failed. The synchronization object timed out.
- Response:
- Verify that the Parlay gateway is operational, or increase the timeout value. Then retry.
- SOAM3904E: A Terminal Status service request failed. A Parlay Unauthorized network error occurred.
- Explaination:
- A Terminal Status service request failed. A Parlay Unauthorized network error occurred.
- Response:
- Check the Parlay configuration and retry.
- SOAM3905E: A Terminal Status service request failed. A Parlay Position method failure occurred.
- Explaination:
- A Terminal Status service request failed. A Parlay Position method failure occurred.
- Response:
- Check the Parlay configuration and retry.
- SOAM3908E: A Terminal Status service request failed. The request could not obtain a compatible service manager object from Parlay.
- Explaination:
- A Terminal Status service request failed. The request could not obtain a compatible service manager object from Parlay.
- Response:
- Check the Terminal Status service name or the Parlay configuration, then retry.
- SOAM3909E: A Terminal Status service request failed. The operation invoked is not supported.
- Explaination:
- A Terminal Status service request failed. The operation invoked is not supported.
- Response:
- Make sure the Terminal Status Web service settings match the capabilities of the Parlay gateway. Then retry.
- SOAM3911E: The Terminal Status notification Request failed. The specified correlator is already in use.
- Explaination:
- The Terminal Status notification Request failed. The specified correlator is already in use.
- Response:
- Provide a unique correlator for this request, and retry.
- SOAM3912E: Could not create a database entry for a Terminal Status notification service request.
- Explaination:
- Could not create a database entry for a Terminal Status notification service request.
- Response:
- Retry the request. If the problem persists, contact the system administrator.
- SOAM3916I: The Terminal Status notification request failed. The specified correlator is not registered.
- Explaination:
- The Terminal Status notification request failed. The specified correlator is not registered.
- Response:
- Provide a registered correlator for this request, and retry.
- SOAM3917E: The Terminal Status notification request failed. The specified correlator was not valid.
- Explaination:
- The Terminal Status notification request failed. The specified correlator was not valid.
- Response:
- Provide a valid correlator for this request, and retry.
- SOAM3918E: A Terminal Status service request failed. The Parlay gateway refused a parameter in the request.
- Explaination:
- A Terminal Status service request failed. The Parlay gateway refused a parameter in the request.
- Response:
- Check that all of the parameters in the request are valid, and retry.
- SOAM3919E: A Terminal Status service request failed. The Parlay gateway reported a system failure.
- Explaination:
- A Terminal Status service request failed. The Parlay gateway reported a system failure.
- Response:
- Check the Parlay gateway for error details.
- SOAM3920E: A Terminal Status service request failed. A Parlay Unauthorized Application error occurred.
- Explaination:
- A Terminal Status service request failed. A Parlay Unauthorized Application error occurred.
- Response:
- Check the Parlay configuration and retry.
- SOAM3921E: A Terminal Status service request failed. An unknown Parlay error occurred.
- Explaination:
- A Terminal Status service request failed. An unknown Parlay error occurred.
- Response:
- Check the Parlay configuration and the Parlay gateway, then retry.
- SOAM3922E: A Terminal Status notification service received a notification from the Parlay gateway that was not valid. The notification was ignored.
- Explaination:
- A Terminal Status notification service received a notification from the Parlay gateway that was not valid. The notification was ignored.
- Response:
- Check the Parlay configuration and the Parlay gateway.
- SOAM4000E: An unexpected internal error occurred with the Terminal Location service.
- Explaination:
- An unexpected internal error occurred with the Terminal Location service.
- Response:
- Contact the system administrator.
- SOAM4008W: An unknown error occurred within the Terminal Location service while attempting to get a service usage record.
- Explaination:
- An unknown error occurred within the Terminal Location service while attempting to get a service usage record.
- Response:
- Contact the system administrator.
- SOAM4009E: An unexpected database error occurred in the Terminal Location Notification service.
- Explaination:
- An unexpected database error occurred in the Terminal Location Notification service.
- Response:
- Retry the request. Contact the system administrator if the problem persists.
- SOAM4010E: A database entry could not be created for a Terminal Location Notification service request.
- Explaination:
- A database entry could not be created for a Terminal Location Notification service request.
- Response:
- Retry the request. Contact the system administrator if the problem persists.
- SOAM4011E: A database entry could not be located for a Terminal Location Notification service request.
- Explaination:
- A database entry could not be located for a Terminal Location Notification service request.
- Response:
- Retry the request. Contact the system administrator if the problem persists.
- SOAM4012W: Could not reach a client to notify it of a Location Notification event.
- Explaination:
- Could not reach a client to notify it of a Location Notification event.
- Response:
- Check the endpoint address and the PxNotification configuration, then retry.
- SOAM4013W: Could not clean up a Terminal Location Notification resource because an error occurred.
- Explaination:
- Could not clean up a Terminal Location Notification resource because an error occurred.
- Response:
- Retry the request. Contact the system administrator if the problem persists.
- SOAM4014E: An internal error occurred while attempting to resolve a Terminal Location JNDI reference.
- Explaination:
- An internal error occurred while attempting to resolve a Terminal Location JNDI reference.
- Response:
- Contact the system administrator.
- SOAM4015I: The Terminal Location service could not read a service policy value.
- Explaination:
- The Terminal Location service could not read a service policy value.
- Response:
- Make sure a valid value is specified for the service policy, and retry.
- SOAM4016I: The Terminal Location service could not read a management bean value.
- Explaination:
- The Terminal Location service could not read a management bean value.
- Response:
- Make sure a valid value is specified for the management bean, and retry.
- SOAM4017I: The service policy value was not valid. The default value will be used.
- Explaination:
- The service policy value was not valid. The default value will be used.
- Response:
- No action is required.
- SOAM4150E: The Terminal Location request failed. A system failure occurred in the in MLP location server.
- Explaination:
- The Terminal Location request failed. A system failure occurred in the MLP location server.
- Response:
- Contact the system administrator.
- SOAM4151E: The Terminal Location Web service had an authorization problem.
- Explaination:
- The Terminal Location Web service reported the following error: MLP Unauthorized Network.
- Response:
- Check the configuration for the MLP connector, and retry the operation.
- SOAM4152E: The request failed. An Unknown Subscriber error was reported.
- Explaination:
- The request failed. An Unknown Subscriber error was reported.
- Response:
- Contact the system administrator.
- SOAM4153E: The request failed. An Absent Subscriber error was reported.
- Explaination:
- The request failed. An Absent Subscriber error was reported.
- Response:
- Retry at another time.
- SOAM4154E: The request failed. There was congestion in the MLP location server.
- Explaination:
- The request failed. There was congestion in the MLP location server.
- Response:
- Retry when the location server is less busy.
- SOAM4155E: The request failed. There was congestion in the mobile network.
- Explaination:
- The request failed. There was congestion in the mobile network.
- Response:
- Retry when there is less traffic in the network.
- SOAM4156E: The response from the MLP location server was corrupted or not valid.
- Explaination:
- The response from the MLP location server was corrupted or not valid.
- Response:
- Contact the system administrator.
- SOAM4157E: The request failed. There were too many position items.
- Explaination:
- The request failed for the following reason: Too many position items.
- Response:
- Check your request to ensure it contains the proper number of items, and retry.
- SOAM4158E: The request was rejected. The operation is not supported by the current configuration.
- Explaination:
- The request was rejected. The operation is not supported by the current configuration.
- Response:
- Make sure that support for this operation is enabled. Then retry.
- SOAM4159E: The request failed. The operation is not allowed by Local regulations.
- Explaination:
- The request failed for the following reason: Disallowed by local regulations.
- Response:
- Contact the system administrator.
- SOAM4160E: The request failed. The location server is not configured properly.
- Explaination:
- The request failed for the following reason: Misconfiguration of location server.
- Response:
- Check the configuration of the location server, and retry.
- SOAM4161E: The correlator provided in a start notification request is already registered.
- Explaination:
- The correlator provided in a start notification request is already registered.
- Response:
- Provide a unique correlator for this request, and retry.
- SOAM4162E: The correlator provided in a end notification request is not registered.
- Explaination:
- The correlator provided in a end notification request is not registered.
- Response:
- Provide a registered correlator for this request, and retry.
- SOAM4163E: The request failed. It did not contain valid target addresses.
- Explaination:
- The request failed. It did not contain valid target addresses.
- Response:
- Provide valid target information for the request, and retry.
- SOAM4174E: The correlator provided was not valid.
- Explaination:
- The correlator provided was not valid.
- Response:
- Provide a valid correlator for the request, and retry.
- SOAM4178E: The Terminal Location Web service reported the following error: MLP Position Method Failure.
- Explaination:
- The Terminal Location Web service reported the following error: MLP Position Method Failure.
- Response:
- Contact the system administrator.
- SOAM4179E: The Terminal Location Web service reported the following error: Unsupported Protocol Version.
- Explaination:
- The Terminal Location Web service reported the following error: Unsupported Protocol Version.
- Response:
- Contact the system administrator.
- SOAM4180E: The Terminal Location Web Service reported the following error: Unknown MLP Failure.
- Explaination:
- The Terminal Location Web Service reported the following error: Unknown MLP Failure.
- Response:
- Contact the system administrator.
- SOAM4181E: The request failed. It contained an incorrect parameter.
- Explaination:
- The request failed. The MLP location server rejected a request that contained an incorrect parameter.
- Response:
- Contact the system administrator.
- SOAM4182E: The request failed. Positioning is not allowed for the target.
- Explaination:
- The request failed. The MLP location server reports that positioning is not allowed for the target.
- Response:
- Contact the system administrator.
- SOAM4183E: The MLP location server reported the following error: The requested QoP is not attainable.
- Explaination:
- The MLP location server reported the following error to the Terminal Location Web Service: The requested QoP is not attainable.
- Response:
- Contact the system administrator.
- SOAM4184E: The MLP location server reported the following error: The requested service is not supported.
- Explaination:
- The MLP location server reported the following error to the Terminal Location Web Service: The requested service is not supported.
- Response:
- Contact the system administrator.
- SOAM4185E: The MLP location server reported the following error: The protocol element or attribute is not supported.
- Explaination:
- The MLP location server reported the following error to the Terminal Location Web Service: The protocol element or attribute is not supported.
- Response:
- Contact the system administrator.
- SOAM4186E: The Terminal Location Web Service received the following response: Cancellation of triggered location request.
- Explaination:
- The Terminal Location Web Service received the following response: Cancellation of triggered location request.
- Response:
- Contact the system administrator.
- SOAM4187E: The MLP location server reported the following error: Unknown MLP protocol.
- Explaination:
- The MLP location server reported the following error to the Terminal Location Web Service: Unknown MLP protocol.
- Response:
- Contact the system administrator.
- SOAM4188E: The MLP connector could not communicate with the MLP location server.
- Explaination:
- The MLP connector could not communicate with the MLP location server.
- Response:
- Contact the system administrator.
- SOAM4189E: The report from the MLP location server was corrupted or not valid.
- Explaination:
- The report from the MLP location server was corrupted or not valid.
- Response:
- No action is required.
- SOAM4300E: A Terminal Location service request failed. A Parlay error occurred.
- Explaination:
- A Terminal Location service request failed. A Parlay error occurred.
- Response:
- Check the Parlay configuration and the Parlay gateway for errors. Then retry.
- SOAM4302E: A Terminal Location service request failed. The synchronization object timed out.
- Explaination:
- A Terminal Location service request failed. The synchronization object timed out.
- Response:
- Verify that the Parlay gateway is operational, or increase the timeout value. Then retry.
- SOAM4304E: A Terminal Location service request failed. A Parlay Unauthorized Network error occurred.
- Explaination:
- A Terminal Location service request failed. A Parlay Unauthorized Network error occurred.
- Response:
- Check the Parlay configuration and retry.
- SOAM4305I: A Terminal Location service request failed A Parlay Position method failure occurred.
- Explaination:
- A Terminal Location service request failed. A Parlay Position method failure occurred.
- Response:
- Check the Parlay configuration and retry.
- SOAM4308I: A Terminal Location service request failed. The request could not obtain a compatible service manager object from Parlay.
- Explaination:
- A Terminal Location service request failed. The request could not obtain a compatible service manager object from Parlay.
- Response:
- Check the Terminal Location service name or the Parlay configuration. Then retry.
- SOAM4309I: A Terminal Location service request failed. The operation invoked is not supported.
- Explaination:
- A Terminal Location service request failed. The operation invoked is not supported.
- Response:
- Make sure the Terminal Location Web service settings match the capabilities of the Parlay gateway. Then retry.
- SOAM4311I: The Terminal Location notification request failed. The specified correlator is already in use.
- Explaination:
- The Terminal Location notification request failed. The specified correlator is already in use.
- Response:
- Provide a unique correlator for this request, and retry.
- SOAM4312W: Could not create a database entry for a Terminal Location notification request.
- Explaination:
- Could not create a database entry for a Terminal Location notification request.
- Response:
- Retry the request. If the problem persists, contact the system administrator.
- SOAM4316I: The Terminal Location notification request failed. The specified correlator is not registered.
- Explaination:
- The Terminal Location notification request failed because. The specified correlator is not registered.
- Response:
- Provide a registered correlator for this request, and retry.
- SOAM4317I: The Terminal Location notification request failed. The specified correlator was not valid.
- Explaination:
- The Terminal Location notification request failed. The specified correlator was not valid.
- Response:
- Provide a valid correlator for this request, and retry.
- SOAM4318W: A Terminal Location service request failed. The Parlay gateway refused a parameter in the request.
- Explaination:
- A Terminal Location service request failed. The Parlay gateway refused a parameter in the request.
- Response:
- Check that the parameters of the request are valid, and retry.
- SOAM4319E: A Terminal Location service request failed. The Parlay gateway reported a system failure.
- Explaination:
- A Terminal Location service request failed. The Parlay gateway reported a system failure.
- Response:
- Check the Parlay gateway for error details.
- SOAM4320E: A Terminal Location service request failed. A Parlay Unauthorized Application error occurred.
- Explaination:
- A Terminal Location service request failed. A Parlay Unauthorized Application error occurred.
- Response:
- Check the Parlay configuration, and retry.
- SOAM4321E: A Terminal Location service request failed. An unknown Parlay error occurred.
- Explaination:
- A Terminal Location service request failed. An unknown Parlay error occurred.
- Response:
- Check the Parlay configuration and the Parlay gateway, and retry.
- SOAM4322W: A Terminal Location notification service received a notification from the Parlay gateway that was not valid. The notification was ignored.
- Explaination:
- A Terminal Location notification service received a notification from the Parlay gateway that was not valid. The notification was ignored.
- Response:
- Check the Parlay configuration and the Parlay gateway.
- SOAM6003E: The delivery status data records could not be retrieved for the following reason: %1.
- Explaination:
- The delivery status data records could not be retrieved for the following reason: %1.
- Response:
- Contact the system administrator.
- SOAM6006E: The specified correlator provided is in use: %1.
- Explaination:
- The specified correlator is in use: %1.
- Response:
- Enter a valid value and retry.
- SOAM6015I: Null input value for the href parameter.
- Explaination:
- No value was specified for the href parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM6016I: Empty string input value for the href parameter.
- Explaination:
- An empty string was specified for the href parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM6017I: Null input value for the action parameter.
- Explaination:
- No value was specified for the action parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM6018I: Empty string input value for the action parameter.
- Explaination:
- An empty string was specified for the action parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM6019I: The input string for the action parameter was not valid. Valid values are signal-none, signal-low, signal-medium, signal-high, and signal-delete.
- Explaination:
- The input string for the action parameter was not valid. Valid values are signal-none, signal-low, signal-medium, signal-high, and signal-delete.
- Response:
- Enter a valid value and retry.
- SOAM6020I: Null input value for the addresses parameter.
- Explaination:
- No value was specified for the addresses parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM6021I: Empty string input value for one of the address parameters.
- Explaination:
- An empty string was specified for one of the address parameters. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM6022I: Null input value for the message parameter.
- Explaination:
- No value was specified for the message parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM6023I: Empty string input value for message parameter.
- Explaination:
- An empty string was specified for the message parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM6025E: The Send SMS data record was not created.
- Explaination:
- The Send SMS data record was not created.
- Response:
- Contact the system administrator.
- SOAM6026I: Null input value for requestIdentifier parameter.
- Explaination:
- No value was specified for the requestIdentifier parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM6027I: Empty string input value for requestIdentifier parameter.
- Explaination:
- An empty string was specified for the requestIdentifier parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM6028I: Could not find a delivery status for this request identifier.
- Explaination:
- Could not find a delivery status for this request identifier.
- Response:
- Enter a valid value and retry.
- SOAM6029E: The delivery status value is unknown.
- Explaination:
- The delivery status value is unknown.
- Response:
- Contact the system administrator.
- SOAM6030E: The requester ID is null in the MDS context.
- Explaination:
- The requester ID is null in the MDS context.
- Response:
- Contact the system administrator.
- SOAM6031E: The MDS context is null.
- Explaination:
- The MDS context is null.
- Response:
- Contact the system administrator.
- SOAM6032E: An error occurred while creating a notification record for the SendWAPpush request.
- Explaination:
- An error occurred while creating a notification record for the SendWAPpush request.
- Response:
- Contact the system administrator.
- SOAM6055E: Unexpected operation for this method.
- Explaination:
- This method is not expected to be called by this operation.
- Response:
- Contact the system administrator.
- SOAM6059I: The WAP Push service is disabled.
- Explaination:
- The WAP Push service is disabled.
- Response:
- Enable the WAPPush service and retry.
- SOAM6060W: Charging is not supported.
- Explaination:
- Charging is not supported.
- Response:
- Change the service policy setting if you want to support charging.
- SOAM6075E: Could not find the notification data for the correlator.
- Explaination:
- Could not find the notification data for the correlator.
- Response:
- Contact the system administrator.
- SOAM6076E: There is no connection to the database.
- Explaination:
- There is no connection to the database.
- Response:
- Contact the system administrator.
- SOAM6077E: An unknown error occurred.
- Explaination:
- An unknown error occurred. Check the error log.
- Response:
- Contact the system administrator.
- SOAM6079E: A problem occurred while updating the status for the destination.
- Explaination:
- A problem occurred while updating the status for the destination. Check the error log.
- Response:
- Contact the system administrator.
- SOAM6080E: A problem occurred while finding the segment status for the transaction.
- Explaination:
- A problem occurred while finding the segment status for the transaction. Check the error log.
- Response:
- Contact the system administrator.
- SOAM6085E: Could not find the notification data for this send transaction ID.
- Explaination:
- Could not find the notification data for this send transaction ID. Check the error log.
- Response:
- Contact the system administrator.
- SOAM6086E: Could not perform the notification for this transaction ID.
- Explaination:
- Could not perform the notification for this transaction ID. Check the error log.
- Response:
- Contact the system administrator.
- SOAM6088E: Could not find the notification data to delete.
- Explaination:
- Could not find the notification data to delete. Check the error log.
- Response:
- Contact the system administrator.
- SOAM6090E: Could not find expired send data.
- Explaination:
- Could not find expired send data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM6091E: Could not remove expired send data.
- Explaination:
- Could not remove expired send data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM1593E: Could not remove expired notification data.
- Explaination:
- Could not remove expired notification data. Check the error log.
- Response:
- Contact the system administrator.
- SOAM6099E: The table is not defined, or the data source could not be created.
- Explaination:
- The table you are trying to access is not defined, or a problem occurred during initial creation of the data source.
- Response:
- Make sure that the table exists, or check the data source configuration.
- SOAM6100E: The database service is not running, or database authentication failed.
- Explaination:
- The database service is not running, or database authentication failed.
- Response:
- Start the database service or check the authentication credentials. Then retry.
- SOAM6101I: Null input value for the HREF parameter.
- Explaination:
- No value was specified for the HREF parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM6102I: Empty string input value for the HREF parameter.
- Explaination:
- An empty string was specified for the HREF parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM6103I: Null input value for the action parameter.
- Explaination:
- No value was specified for the action parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM6104I: Empty string input value for the action parameter.
- Explaination:
- An empty string was specified for the action parameter. A value must be specified.
- Response:
- Enter a valid value and retry.
- SOAM6148E: The service policy %1 is not in the MdsContext.
- Explaination:
- The service policy %1 is not in the MdsContext.
- Response:
- Contact the system administrator.
- SOAM6149E: The service policy value is not as expected. Service Policy: %1. Policy Value: %2
- Explaination:
- The service policy value is not as expected. Service Policy: %1. Policy Value: %2
- Response:
- Contact the system administrator.
- SOAM6150: The service policy service.config.target.Aliases is not in the MdsContext.
- Explaination:
- The service policy service.config.target.Aliases is not in the MdsContext.
- Response:
- Contact the system administrator.
- SOAM6151E: The service policy service.config.messaging.ConfirmDelivery is not in the MdsContext.
- Explaination:
- The service policy service.config.messaging.ConfirmDelivery is not in the MdsContext.
- Response:
- Contact the system administrator.
- SOAM6152E: No alias names were defined in the Administration Console.
- Explaination:
- No alias names were defined in the Administration Console.
- Response:
- Contact the system administrator.
- SOAM6153E: An MBeanException occurred while attempting to get an MBean attribute.
- Explaination:
- An MBeanException occurred while attempting to get an MBean attribute.
- Response:
- Contact the system administrator.
- SOAM6154E: Could not connect to the specified server.
- Explaination:
- Could not connect to the specified server. A ConnectorException error occurred.
- Response:
- Contact the system administrator.
- SOAM6155E: An internal error occurred in the SMPP Session Manager.
- Explaination:
- An internal error occurred in the SMPP Session Manager (SmppSessionManager).
- Response:
- Contact the system administrator.
- SOAM6156E: An error occurred while sending the message to the SMSC.
- Explaination:
- An error occurred while sending the message to the SMSC.
- Response:
- Contact the system administrator.
- SOAM6157E: The Enquire Link Response message was not sent.
- Explaination:
- The Enquire Link Response message was not sent.
- Response:
- Contact the system administrator.
- SOAM6158E: The Deliver SM Response message was not sent.
- Explaination:
- The Deliver SM Response message was not sent.
- Response:
- Contact the system administrator.
- SOAM6159E: The Generic Non-Acknowledge message was not sent.
- Explaination:
- The Generic Non-Acknowledge message was not sent.
- Response:
- Contact the system administrator.
- SOAM6160E: No alias name was defined in the Administration Console. %1
- Explaination:
- No alias name was defined in the Administration Console. %1
- Response:
- Contact the system administrator.
- SOAM6163E: The specified endpoint URI for notification was not valid.
- Explaination:
- The specified endpoint URI for notification was not valid.
- Response:
- Enter the correct URI and retry.
- SOAM6164I: The value for the Receipt Request parameter was not null.
- Explaination:
- A value was specified for the Receipt Request parameter. In order to perform the operation, this parameter must be null.
- Response:
- Deselect the Receipt Request Required option, and retry.
- SOAM6302E: An AttributeNotFoundException occurred while attempting to get an MBean attribute.
- Explaination:
- An AttributeNotFoundException occurred while attempting to get an MBean attribute.
- Response:
- Contact the system administrator.
- SOAM6303E: An MBeanException occurred while attempting to get an MBean attribute.
- Explaination:
- An MBeanException occurred while attempting to get an MBean attribute.
- Response:
- Contact the system administrator.
- SOAM6304E: A ReflectionException occurred while attempting to get an MBean attribute.
- Explaination:
- A ReflectionException occurred while attempting to get an MBean attribute.
- Response:
- Contact the system administrator.