WebSphere brand IBM WebSphere IP Multimedia Subsystem Connector, Version 6.2

Experimental result codes

Experimental result codes are vendor defined result codes that indicate success and error conditions. The Sh subscriber profile Web service and Home Subscriber Server (HSS) define several vendor-specific failure conditions.

Experimental result codes are included inside an Experimental-Result AVP, and the Result-Code AVP does not exist. The Sh application will retrieve the error message and return it through an exception. These exceptions are logged in theWebSphere® Application Server SystemOut.log file.

Table 1. Sh application experimental result codes
Value Message Name Description
2001 DIAMETER_FIRST_REGISTRATION

The user is authorized to register this public identity. The user will be assigned an S-CSCF name.

2002 DIAMETER_SUBSEQUENT_REGISTRATION

The user is authorized to register this public identity. This user was assigned an S-CSCF name prior to this registration. A new S-CSCF name will not be selected.

2003 DIAMETER_UNREGISTERED_SERVICE

The public identity is not registered and has services that belong to an unregistered state. The user will be assigned an S-CSCF name.

2004 DIAMETER_SUCCESS_SERVER_NAME_NOT_STORED

The user has been unregistered. The S-CSCF name will be removed from the HSS.

2005 DIAMETER_SERVER_SELECTION

The user is authorized to register this public identity. An S-CSCF name has been assigned for services related to the previously unregistered state. The user may need to be assigned a new S-CSCF name.

5001 DIAMETER_ERROR_USER_UNKNOWN

The user that received this message does not exist.

5002 DIAMETER_ERROR_IDENTITIES_DONT_MATCH

The HSS cannot identify the user's corresponding private identity for the public identity submitted in the message.

5003 DIAMETER_ERROR_IDENTITY_NOT_REGISTERED

A new public identity submitted a query for LocationInformation. The user will not receive LocationInformation because its public identity has not been registered.

5004 DIAMETER_ERROR_ROAMING_NOT_ALLOWED

The user is not allowed to roam in the visited network.

5005 DIAMETER_ERROR_IDENTITY_ALREADY_REGISTERED

This identity has been assigned to a server prior to this request. The registration status will not overwrite the existing identity.

5006 DIAMETER_ERROR_AUTH_SCHEME_NOT_SUPPORTED

The authentication scheme is not supported.

5007 DIAMETER_ERROR_IN_ASSIGNMENT_TYPE

This identity has been assigned to the same server. The registration status does not allow this server assignment type.

5008 DIAMETER_ERROR_TOO_MUCH_DATA

New data will be discarded because the volume of data being pushed to the receiving entity exceeds the capacity.

5009 DIAMETER_ERROR_NOT_SUPPORTED_USER_DATA

The S-CSCF has informed the HSS that the received subscription data contained unrecognizable or unsupported information.

5010 DIAMETER_MISSING_USER_ID

The message cannot be processed because the HSS has informed the S-CSCF that the message did not contain a private identity or a public identity.

5011 DIAMETER_ERROR_FEATURE_UNSUPPORTED

The received request indicates the origin host requests that the command pair would be handled using an unsupported feature by the destination host.

5100 DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED

The data required in the XML schema does not match the data specified in the HSS.

5101 DIAMETER_ERROR_OPERATION_NOT_ALLOWED

The HSS has ignored the operation because the Sh-Update request does not includes service data.

5102 DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ

The requested user data cannot be read.

5103 DIAMETER_ERROR_USER_DATA_CANNOT_BE_MODIFIED

The requested user data cannot be updated.

5104 DIAMETER_ERROR_USER_DATA_CANNOT_BE_NOTIFIED

The requested user data cannot be notified on changes.

5105 DIAMETER_ERROR_TRANSPARENT_DATA_OUT_OF_SYNC
The request to update the repository data at the HSS cannot be completed because the requested update is based on an out-of-date version of the repository data. Two actions can cause this error:
  • The sequence number in the Sh-Update request message does not match the immediate successor of the associated sequence number stored for that repository data in the HSS.
  • It is also used when the IMS™ Application Server creates a new set of repository data when the repository data exists in the HSS.
4100 DIAMETER_USER_DATA_NOT_AVAILABLE

The requested user data is not available at this time to satisfy the requested operation.

4101 DIAMETER_PRIOR_UPDATE_IN_PROGRESS

The request to update the repository data at the HSS could not be completed because the related repository data is currently being updated by another entity.




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