Explanation: The host name entered is not valid.
User response: Enter a fully qualified host name.
Explanation: The realm name entered is not valid.
User response: Enter a fully qualified realm name.
Explanation: A fully qualified destination realm name parameter is required by the Web service.
User response: Provide a fully qualified destination realm value for the type of data you wish to retrieve.
Explanation: The value specified for the serviceIndication parameter is not valid.
User response: Provide a valid serviceIndication value for the type of data you wish to retrieve.
Explanation: A serviceIndication parameter is required by the Web service.
User response: Start the Web service call again, and provide the serviceIndication parameter.
Explanation: The value specified for the MSISDN parameter is not valid.
User response: Provide a valid MSISDN value for the type of data you wish to retrieve.
Explanation: The MSISDN parameter is required by the Web service.
User response: Start the Web service call again, and provide the MSISDN parameter.
Explanation: The value specified for the serverName parameter is not valid.
User response: Provide a valid serverName value for the type of data you wish to retrieve.
Explanation: A serverName parameter is required by the Web service.
User response: Start the Web service call again, and provide the serverName parameter.
Explanation: The value specified for the identitySet parameter is not valid.
User response: Provide a valid identitySet value for the type of data you wish to retrieve.
Explanation: The value specified for the SubsReqType parameter is not valid.
User response: Provide a valid SubsReqType value for the type of data you wish to retrieve.
Explanation: The value specified for the serviceData parameter is not valid.
User response: Provide a valid serviceData value for the type of data you wish to retrieve.
Explanation: A serviceData parameter is required by the Web service.
User response: Start the Web service call again, and provide the serviceData parameter.
Explanation: The value specified for the sequenceNumber parameter must be a value between 0 and 65535.
User response: Provide a valid sequenceNumber value for the type of data you wish to retrieve.
Explanation: The value specified for the userData parameter is not valid.
User response: Provide a valid userData value for the type of data you wish to retrieve.
Explanation: A userData parameter is required by the Web service.
User response: Start the Web service call again, and provide the userData parameter.
Explanation: The value specified for the callbackUri parameter is not valid.
User response: Provide a valid callbackUri value for the type of data you wish to retrieve.
Explanation: A callbackUri parameter is required by the Web service.
User response: Start the Web service call again, and provide the callbackUri parameter.
Explanation: The value specified for the sessionId parameter is not valid.
User response: Provide a valid sessionId value for the type of data you wish to retrieve.
Explanation: A sessionId parameter is required by the Web service.
User response: Start the web service call again, and provide the sessionId parameter.
Explanation: The value specified for the publicIdentity or MSISDN parameter is not valid.
User response: Provide a valid publicIdentity or MSISDN value for the type of data you wish to retrieve.
Explanation: This web service method requires the publicIdentity or MSISDN parameter.
User response: Start the Web service call again, and provide the publicIdentity or MSISDN parameter.
Explanation: The value specified for the HostIPAddress parameter is not valid.
User response: Provide a valid HostIPAddress value for the type of data you wish to retrieve.
Explanation: An error occurred while trying to access the subscription entry in the Diameter subscription database.
User response: Ensure that the database has been created and configured correctly.
Explanation: An entry for this subscriber and associated data already exists in the Diameter subscription database.
User response: Verify your program logic, this subscriber already exists in the database.
Explanation: An entry for this subscriber and associated data does not exist in the Diameter subscription database.
User response: Verify your program logic, this subscriber does not exist in the database.
Explanation: An error occurred creating the XML user profile to send to the Diameter peer.
User response: Contact IBM support.
Explanation: The user ID and (or) password used to access the database are not valid.
User response: Ensure that you are using the correct user ID and password to access the database.
Explanation: The value entered for the dataReference parameter is not valid.
User response: Select a valid dataReference value for the type of data you wish to retrieve.
Explanation: The Diameter Sh Web service was not able to establish a connection with a Diameter peer.
User response: Verify the configuration values specified in DiameterSh.properties.
Explanation: The Diameter Sh Web service received an invalid response from the Diameter peer for a updateRepositoryData request.
User response: Verify the configuration values specified in DiameterSh.properties.
Explanation: An error occurred parsing the User Profile data received from the Diameter peer.
User response: Verify that the Web service parameters are correct and retry the request. If the error occurs again, contact IBM support.
Explanation: The Diameter Sh Web service received an invalid response from the Diameter peer for a User Data request.
User response: Verify the configuration values specified in DiameterSh.properties.
Explanation: The User-Data-Answer received an error result code from the Diameter peer for a User-Data-Request command.
User response: Verify the configuration values specified in DiameterSh.properties.
Explanation: The User-Data-Answer contains an experimental result code from the Diameter peer for a User-Data-Request command.
User response: The experimental codes will help you determine what action to take next.
Explanation: The Profile-Update-Answer received an error result code from the Diameter peer for a Profile-Update-Request command.
User response: Verify the configuration values specified in DiameterSh.properties.
Explanation: The Profile-Update-Answer contains an experimental result code from the Diameter peer for a Profile-Update-Request command.
User response: The experimental codes will help you determine what action to take next.
Explanation: The Subscribe-Notification-Answer received an error result code from the Diameter peer for a Subscribe-Notifications-Request command.
User response: Verify the configuration values specified in DiameterSh.properties.
Explanation: The Subscribe-Notification-Answer contains an experimental result code from the Diameter peer for a Subscribe-Notifications-Request command.
User response: The experimental codes will help you determine what action to take next.
Explanation: The Diameter Sh Web service is not able to instantiate the parser used to parse the user profile XML document received from the HSS.
User response: Contact IBM support.
Explanation: The Diameter Sh web service is not able to instantiate the parser used to parse the user profile XML document received from the HSS.
User response: Contact IBM support.
Explanation: The Diameter Sh web service is not able to parse an IMSPublicIdentifier received from the HSS.
User response: No action required.
Explanation: The Diameter Sh web service is not able to parse the IMSUserState received from the HSS.
User response: No action required.
Explanation: The Diameter Sh web service is not able to parse the SCSCFName received from the HSS.
User response: No action required.
Explanation: The Diameter Sh web service is not able to parse the InitialFilterCriteria - Application Server received from the HSS.
User response: No action required.
Explanation: The Diameter Sh web service is not able to parse the PSUserState received from the HSS.
User response: No action required.
Explanation: The Diameter Sh web service is not able to parse the CSUserState received from the HSS.
User response: No action required.
Explanation: The data requested by the Diameter Sh web service was not present in the user profile returned from the HSS.
User response: No action required.
Explanation: The Diameter Sh web service is not able to parse a ChargingInfromation Diameter URI received from the HSS.
User response: No action required.
Explanation: The Diameter Sh web service is not able to parse the CSLocationInformation AgeofLocationInformation element received from the HSS.
User response: No action required.
Explanation: The Diameter Sh web service is not able to parse the PSLocationInformation AgeofLocationInformation element received from the HSS.
User response: No action required.
Explanation: The Diameter Sh web service is not able to parse the InitialFilterCriteria DefaultHandling element received from the HSS.
User response: No action required.
Explanation: The Diameter Sh web service is not able to parse the InitialFilterCriteria RegistrationType element received from the HSS.
User response: No action required.
Explanation: The Diameter Sh web service is not able to parse the InitialFilterCriteria SessionCase element received from the HSS.
User response: No action required.
Explanation: The Diameter Sh web service is not able to parse the RepositoryData SequenceNumber element received from the HSS.
User response: No action required.
Explanation: The Diameter Sh web service received an invalid response from the Diameter peer for a Subscribe-Notification request.
User response: Verify the configuration values specified in DiameterSh.properties.
Explanation: The Diameter Sh web service has detected a Diameter protocol error in the request packet received from the Diameter peer.
User response: No action required.
Explanation: The Diameter Sh web service received an invalid Push-Notification-Request packet from the Diameter peer.
User response: No action required.
Explanation: The Diameter Sh web service is not able to transmit the Push-Notification-Answer packet to the Diameter peer.
User response: verify the configuration values specified in DiameterSh.properties and ensure a valid route to the peer exists.
Explanation: The Diameter Sh web service is not able to notify the Notification web service that a notification request was received.
User response: Ensure the subsription database can be accessed, and that a valid user id and password are provided for the Notification web service if it is secured.
Explanation: The Diameter Sh web service received data that is not valid in the Push-Notification-Request packet from the Diameter peer.
User response: No action required.
Explanation: An error occured while trying to access the subscription entries in the Diameter subscription database.
User response: Ensure that the database has been created and configured correctly.
Explanation: An error occured when trying to send the notification to the client by way of its Notification Web service.
User response: Ensure the Callback URI, User ID, and Password are correct for this client's Notification Web service. The client may need to unsubscribe and resubscribe with the correct connection information, or its record may be manually deleted from the subscription database.
Explanation: An error occured when creating the Sh Notification EJB.
User response: Ensure that Enterprise Beans where deployed when installing the Diameter Sh Enterprise Application.
Explanation: The HostIPAddress has no value defined in the configuration file.
User response: Verify the configuration values specified in DiameterSh.properties.
Explanation: Could not find a subscription in the Diameter subscription database for the requested public identity and data reference values.
User response: Ensure that the database has been created and configured correctly.
Explanation: Not able to find the Sh Subscription/Notification EJB Homes or Work Manager in the JNDI namespace.
User response: Ensure the defaults were used for Resource References when deploying the Sh Enterprise Application.
Explanation: The supplied user id or password is null or blank for this subscribe request.
User response: Notify the developer or administrator of this Sh application client to provide both a user id and password on their subscribe calls if their Notification Web service is protected.
Explanation: The HSS at the Diameter peer sent a user data XML string specifiying a schema that is not supported.
User response: Verify that the HSS and Diameter network is configured correctly.
Explanation: The Diameter Sh web service is not able to parse the PSIActivation received from the HSS.
User response: No action required.
Explanation: The value specified for the activation parameter is not valid.
User response: Provide a valid activation value for the type of data you wish to retrieve.
Explanation: The Sh Application can process PNR requests and UDA, PUA, SNA responses.
User response: Contact the HSS and check the command code and request bit of the sent packet for correctness.
Explanation: The Diameter Enabler was unable to fulfill the request.
User response: Examine java traces in the log file for an error in the transactions.
Explanation: The Work Manager queue has surpassed it's capacity and the push notification request will not be sent to the client application.
User response: Increase the default Work Manager Max Thread Pool Size. Ensure the inbound traffic does not exceed traffic capacity for a single node.