string |
-
cscfUserDataDelete
(
UserDataDeletePotDT pot
,
string key
,
UserDataDeleteModeDT mode
);
-
WARNING: Please consult Ericsson Personnel before executing this action. This action can corrupt and damage the database.
This action deletes user specific data from the database. It takes three mandatory input parameters:
--pot <pot-name> --key <all | pot-key> --mode <NON_RECURSIVE>
Please refer to the description of the ”pot”, ”key” and ”mode” parameters for further details.
Below is an example of deleting an Implicit Registration Set POT:
cscfUserDataDelete --pot CscfImplicitRegistrationSetPot --key sip:u0000000000@cscf99.lab --mode NON_RECURSIVE
-
Parameters
Name: pot
Description: This parameter defines the keyed Persistent Object Type (POT) name to be deleted. Possible values and meanings are:
- CscfPrivateIdentificationPot: Private Identity POT
- CscfImplicitRegistrationSetPot: Implicit Registration Set POT
- CscfServiceProfilePot: Service Profile POT
- CscfPublicIdentificationPot: Public Identity POT
- CscfImpuReferencePot: Public Identity Reference POT
- CscfContactContainerPot: Contact Container POT
- CscfSipDigestAuthenticationChallengePot: SIP Digest Authentication Challenge POT
- CscfSipDigestAuthenticationNoncePot: SIP Digest Authentication Nonce POT
- CscfSipDigestAuthenticationVectorPot: SIP Digest Authentication Vector POT
- CscfAuthenticationBlacklistPot: Authentication Blacklist POT
- CscfAkaAuthenticationPot: Authentication and Key Agreement (AKA) Authentication POT
- CscfDialogueContainerPot: Dialogue Container POT
- CscfDialogueDataPot: Dialogue Data POT
- CscfOfflineChargingSession: Offline Charging Session POT
Name: key
Description: This parameter defines the key of the Persistent Object Type (POT) instance(s) to be deleted.
If "all" is used as key then all instances associated with the POT specified will be deleted. Note: It is strongly recommended that "all" shall only be used in test environment.
Selecting a specific POT instance to delete can be accomplished in two ways:
1. Use the POT key value in hexadecimal format which can be obtained from the "clurun.sh list_instances" command or DBN browser. The syntax for this method is to append a prefix "0x" in front of the hexadecimal string: --key 0x<hexadecimal string>.
2. Specify a given POT instance key information in clear text depending on the POT type as depicted below:
- CscfPrivateIdentificationPot: <IMPI>
- CscfImplicitRegistrationSetPot: <IMPU>
- CscfServiceProfilePot: <IMPU>
- CscfPublicIdentificationPot: <IMPU>
- CscfImpuReferencePot: <IMPU>
- CscfContactContainerPot: <IMPU#IMPI>
- CscfSipDigestAuthenticationChallengePot: <Call-ID>
- CscfSipDigestAuthenticationNoncePot: <Nonce>
- CscfSipDigestAuthenticationVectorPot: <IMPI>
- CscfAuthenticationBlacklistPot: only "all" is supported as clear-text key
- CscfAkaAuthenticationPot: <IMPI>
- CscfDialogueContainerPot: <IMPU1#IMPU2> where IMPU1 is the default IMPU and IMPU2 is the Service Profile Identity. If it happens that both IMPU1 and IMPU2 are the same, then put IMPU1#IMPU1 as key.
- CscfDialogueDataPot: only "all" is supported as clear-text key
- CscfOfflineChargingSession: only "all" is supported as clear-text key
Name: mode
Description: This parameter specifies how the Persistent Object Type (POT) instance(s) are deleted. Possible values and meanings are:
1: NON_RECURSIVE: delete only the POT instance specified by the key.
Even though only one mode is currently supported, other modes may be supported in the future.
|