WebSphere brand IBM WebSphere IP Multimedia Subsystem Connector, Version 6.2

Messages

DHAS0001E: The host name value of {0} is not valid.

Explanation: The host name entered is not valid.

User response: Enter a fully qualified host name.

DHAS0002E: The realm name value of {0} is not valid.

Explanation: The realm name entered is not valid.

User response: Enter a fully qualified realm name.

DHAS0003E: The required destination realm name parameter is not specified.

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.

DHAS0004E: The serviceIndication value of {0} is not valid.

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.

DHAS0005E: The required serviceIndication is not specified.

Explanation: A serviceIndication parameter is required by the Web service.

User response: Start the Web service call again, and provide the serviceIndication parameter.

DHAS0006E: The MSISDN value of {0} is not valid.

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.

DHAS0007E: The required MSISDN is not specified.

Explanation: The MSISDN parameter is required by the Web service.

User response: Start the Web service call again, and provide the MSISDN parameter.

DHAS0008E: The serverName value of {0} is not valid.

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.

DHAS0009E: The required serverName is not specified.

Explanation: A serverName parameter is required by the Web service.

User response: Start the Web service call again, and provide the serverName parameter.

DHAS0010E: The identitySet value of {0} is not valid.

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.

DHAS0011E: The SubsReqType value of {0} is not valid.

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.

DHAS0012E: The serviceData value of {0} is not valid.

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.

DHAS0013E: The required serviceData is not specified.

Explanation: A serviceData parameter is required by the Web service.

User response: Start the Web service call again, and provide the serviceData parameter.

DHAS0014E: The sequenceNumber value of {0} is not valid.

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.

DHAS0015E: The userData value of {0} is not valid.

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.

DHAS0016E: The required userData is not specified.

Explanation: A userData parameter is required by the Web service.

User response: Start the Web service call again, and provide the userData parameter.

DHAS0017E: The callbackUri value of {0} is not valid.

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.

DHAS0018E: The required callbackUri is not specified.

Explanation: A callbackUri parameter is required by the Web service.

User response: Start the Web service call again, and provide the callbackUri parameter.

DHAS0019E: The sessionId value of {0} is not valid.

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.

DHAS0020E: The required sessionId is not specified.

Explanation: A sessionId parameter is required by the Web service.

User response: Start the web service call again, and provide the sessionId parameter.

DHAS0021E: The publicIdentity or MSISDN value specified is not valid.

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.

DHAS0022E: The required publicIdentity or MSISDN is not specified.

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.

DHAS0023E: The HostIPAddress value of {0} is not valid.

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.

DHAS0024E: An error occurred accessing the subscription database for {0}.

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.

DHAS0025E: A subscription for subscriber {0} already exists in the database.

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.

DHAS0026E: A subscription for subscriber {0} does not exist 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.

DHAS0027E: An error occurred creating the XML user profile.

Explanation: An error occurred creating the XML user profile to send to the Diameter peer.

User response: Contact IBM support.

DHAS0028E: The user ID and (or) password used to access the database are not valid.

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.

DHAS0030E: The value entered for the dataReference parameter is not valid.

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.

DHAS0040E: Not able to obtain a Diameter interface {0}.

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.

DHAS0041E: The Profile-Update-Answer packet [{0}] received from the Diameter peer is not valid: {1}.

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.

DHAS0042E: Parser error: The user profile data received is not valid.

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.

DHAS0043E: The User-Data-Answer packet [{0}] received from the Diameter peer is not valid: {1}.

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.

DHAS0044E: The User-Data-Answer contains an error result code of {0}.

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.

DHAS0045E: The User-Data-Answer contains an experimental result code of {0}.

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.

DHAS0046E: The Profile-Update-Answer contains an error result code of {0}.

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.

DHAS0047E: The Profile-Update-Answer contains an experimental result code of {0}.

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.

DHAS0048E: The Subscribe-Notification-Answer contains an error result code of {0}.

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.

DHAS0049E: The Subscribe-Notification-Answer contains an experimental result code of {0}.

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.

DHAS0050E: Not able to obtain the SAX parser factory.

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.

DHAS0051E: The SAX parser configuration features specified are not valid.

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.

DHAS0052W: Not able to parse IMSPublicIdentifier URI

Explanation: The Diameter Sh web service is not able to parse an IMSPublicIdentifier received from the HSS.

User response: No action required.

DHAS0053W: Not able to parse the IMSUserState received from the HSS.

Explanation: The Diameter Sh web service is not able to parse the IMSUserState received from the HSS.

User response: No action required.

DHAS0054W: Not able to parse the SCSCFName received from the HSS.

Explanation: The Diameter Sh web service is not able to parse the SCSCFName received from the HSS.

User response: No action required.

DHAS0055W: Not able to parse the InitialFilterCriteria - Application Server received from the HSS.

Explanation: The Diameter Sh web service is not able to parse the InitialFilterCriteria - Application Server received from the HSS.

User response: No action required.

DHAS0056W: Not able to parse the PSUserState received from the HSS.

Explanation: The Diameter Sh web service is not able to parse the PSUserState received from the HSS.

User response: No action required.

DHAS0057W: Not able to parse the CSUserState received from the HSS.

Explanation: The Diameter Sh web service is not able to parse the CSUserState received from the HSS.

User response: No action required.

DHAS0058E: The requested data was not present in the user profile received from the HSS.

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.

DHAS0059W: Not able to parse ChargingInformation Diameter URI

Explanation: The Diameter Sh web service is not able to parse a ChargingInfromation Diameter URI received from the HSS.

User response: No action required.

DHAS0060W: Not able to parse the CSLocationInformation AgeofLocationInformation element received from the HSS.

Explanation: The Diameter Sh web service is not able to parse the CSLocationInformation AgeofLocationInformation element received from the HSS.

User response: No action required.

DHAS0061W: Not able to parse the PSLocationInformation AgeofLocationInformation element received from the HSS.

Explanation: The Diameter Sh web service is not able to parse the PSLocationInformation AgeofLocationInformation element received from the HSS.

User response: No action required.

DHAS0062W: Not able to parse the InitialFilterCriteria DefaultHandling received from the HSS.

Explanation: The Diameter Sh web service is not able to parse the InitialFilterCriteria DefaultHandling element received from the HSS.

User response: No action required.

DHAS0063W: Not able to parse the InitialFilterCriteria RegistrationType received from the HSS.

Explanation: The Diameter Sh web service is not able to parse the InitialFilterCriteria RegistrationType element received from the HSS.

User response: No action required.

DHAS0064W: Not able to parse the InitialFilterCriteria SessionCase received from the HSS.

Explanation: The Diameter Sh web service is not able to parse the InitialFilterCriteria SessionCase element received from the HSS.

User response: No action required.

DHAS0065W: The RepositoryData SequenceNumber received from the HSS is not valid.

Explanation: The Diameter Sh web service is not able to parse the RepositoryData SequenceNumber element received from the HSS.

User response: No action required.

DHAS0066E: The Subscription-Notification packet [{0}] received from the Diameter peer is not valid: {1}.

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.

DHAS0067E: A protocol error was detected in the request packet.

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.

DHAS0068E: The Push-Notification-Request packet [{0}] received from the Diameter peer is not valid: {1}.

Explanation: The Diameter Sh web service received an invalid Push-Notification-Request packet from the Diameter peer.

User response: No action required.

DHAS0069E: Not able to transmit the Push-Notification-Answer packet.

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.

DHAS0070E: Not able to notify the client that a Push-Notification-Request was received.

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.

DHAS0071E: User data in the notification packet received from the Diameter peer is not valid.

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.

DHAS0072E: Error retrieving subscriptions for data reference {0} and public identity {1}.

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.

DHAS0073E: Error sending notification to the client.

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.

DHAS0074E: Error creating the Sh Notification EJB.

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.

DHAS0075E: The HostIPAddress is not specified in the configuration file.

Explanation: The HostIPAddress has no value defined in the configuration file.

User response: Verify the configuration values specified in DiameterSh.properties.

DHAS0076E: Could not find a subscription for data reference {0} and public identity {1}.

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.

DHAS0077E: Not able to find the Sh Subscription/Notification EJB Homes or Work Manager.

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.

DHAS0078W: Either the supplied user id or password is null or blank. Both the user id and password will be ignored. The public identity for this subscribe request is {0} and the callback URI is {1}

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.

DHAS0079E: The schema name {0} specified in the XML data string received is not supported.

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.

DHAS0080W: Not able to parse the PSIActivation received from the HSS.

Explanation: The Diameter Sh web service is not able to parse the PSIActivation received from the HSS.

User response: No action required.

DHAS0081E: The activation value of {0} is not valid.

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.

DHAS0082E: The received packet has been discarded because of protocol error {0}.

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.

DHAS0083E: A failure was detected during packet transmittal: {0}.

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.

DHAS0084E: The PNR client notification has been discarded.

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.




Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.