HTTP Response Codes and Error Codes

3 HTTP Response Codes and Error Codes

The following are the HTTP Response Codes:

Table 3-1 HTTP Response Codes and Error Codes

Data Type	Mandat ory(M)/Optional(O)/Conditi onal(C )	Cardinality	Response Code	Description
ProblemDetails	C	1	400 - BAD REQUEST	SEPP config-mgr-svc shall send the response when the Request body received is not as per defined Data Model.
ProblemDetails	C	1	500 - INTERNAL SERVER ERROR	SEPP config-mgr-svc shall send the response when an internal error has occurred.
Response Body as per Data Model defined	C	1	200 - OK	SEPP config-mgr-svc shall send the response when the request is successful.
ProblemDetails	C	1	404 -NOT FOUND	SEPP config-mgr-svc shall send the response when the requested entry is not present in the database.

Error Codes and Recovery Steps

The following tables list the various SEPP error codes and the recovery steps:

Table 3-2 Error Codes and Recovery Steps

Error Code	Error Text	Command/Method	Description	Recovery Steps
SEPP-COM-DB-ERROR-0002	Remote Sepp record not found	GET remotesepp/{name} DELETE remotesepp/{name} PATCH remotesepp/{name}	This error is observed if the provided name in the request is not present.	Verify that Remote SEPP name given in request parameter is present.
SEPP-COM-DB-ERROR-0003	N32F Context not found record not found	GET handshakestatus/fqdn/{fqdn} GET handshakestatus/name/{name}	This error is observed if the context with given name or fqdn in the request parameter is not found.	Verify that context with given name or fqdn in request parameter is present in DB.
SEPP-COM-DB-ERROR-0005	Database connection is down	Can be thrown from any Method (Generic Exception if application is unable to connect with Database)	This error is observed if the application is unable to make the connection with Database.	Verify that DB is up and running.
SEPP-COM-DB-ERROR-0007	SQL Grammer exception	PUT remoteseppset/{name}	This error is observed if there is some corruption in the Database related to Remote SEPP Set table (This error gets generated for all the commands that is trying to access corrupted table or Database).	Recheck the corruption in database and re-install SEPP
SEPP-COM-DB-ERROR-0008	Constraint violation exception of database table columns	PUT {remoteSepp}	This error is observed when one of the mandatory parameters required for remote SEPP are not present.	Verify that mandatory parameter like name, seppfqdn are present.
SEPP-COM-DB-ERROR-0009	Unsupported security capability list exception	POST /remotesepp PUT remotesepp/{name} PATCH remotesepp/{name}	This error is observed if unsupported securityCapabilityList is provided in request.	Make sure securityCapabilityList provided is supported by SEPP. Allowed security capability list is 'TLS' and 'TLS and PRINS.
SEPP-COM-DB-ERROR-0010	Update not allowed on table entry exception	PUT remotesepp/{name} PATCH remotesepp/{name}	This error is observed if given parameter to update is same as configured one or trying to update mandatory parameter.	Verify that the parameter provided in the request to update is different from the configured one or not while updating any mandatory parameter like name, seppfqdn etc.
SEPP-COM-DB-ERROR-0011	Remote Sepp already present	POST /remotesepp	This error is observed if Remote SEPP with same seppfqdn is already present in DB.	Verify that seppfqdn provided in configuration request is not already present in DB.
SEPP-COM-DB-ERROR-0012	Mandatory Parameter Update Not Allowed	PUT remotesepp/{name} PATCH remotesepp/{name}	This error is observed if the user is trying to update the value of mandatory parameter which is not allowed.	Verify that some of the mandatory parameters are not allowed to be updated. Those allowed should match with the value in the request.
SEPP-COM-ERROR-0013	Invalid PLMN List in Request	POST /remotesepp PUT /remotesepp	This error is observed if the user has configured PLMN in incorrect format in PLMNID List.	Verify the entered PLMN (mcc and mnc) in PLMNID List while configuring Remote Sepp.
SEPP-COM-DB-ERROR-0020	Remote Sepp Set not found	GET RemoteSeppSet/{name}	This error is observed if the Remote Sepp Set is not present	Give the Remote SEPP Set name that exist in the database
SEPP-COM-DB-ERROR-0021	Remote Sepp Set associated with Remote SEPP	DELETE RemoteSepp/{name} PUT RemoteSepp/{name} PATCH RemoteSepp/{name}	This error is observed if Remote SEPP is associated with Remote Sepp Set, it gives this error on deletion.	Disassociate the Remote Sepp from Remote SEPP Set by executing the Remote SEPP Set PUT command. Or Do the following: Delete the Remote Sepp Set Delete the Remote Sepp Create Remote Sepp Set again
SEPP-COM-DB-ERROR-0022	Remote Sepp Set already exists	POST RemoteSeppSet/{name}	This error is observed if Remote Sepp Set already exists and same entry is added again.	Use a unique name in Remote Sepp Set
SEPP-COM-DB-ERROR-0023	Remote Sepp Set configuration error	PUT RemoteSeppSet/{name} POST RemoteSeppSet/{name}	Remote Sepp Set does not exists Requested Remote Sepp does not exists At least one Remote Sepp should be associated with Remote Sepp Set Configured Domains are different between peers Remote Sepp Set exists with same domain Configured PLMNs are different between peers Remote Sepp Set exists with same PLMN Configured PLMNs/Domains are different between peers Associating Remote Sepp should be unique for Remote Sepp Set	Give the Remote SEPP Set name that exists in the database Give the Remote SEPP name that exists in the database Give at least a single Remote Sepp name while creating a Remote Sepp Set Check that each Remote Sepp has same Domain when creating a Remote Sepp Set Check that each Remote Sepp has same PLMN when creating a Remote Sepp Set Check that each Remote Sepp name is unique while creating a Remote Sepp Set
SEPP-COM-xx-ERROR-0101	Config Not Acceptable	PUT POST PATCH /v1/remotesepp/	This error is observed if PLMNIdList is empty or PLMNIdList size is greater than max size allowed or if domain is null.	Verify that PLMNIdList is not empty or PLMNIdList size is not greater than max size allowed or if domain is not null.
SEPP-COM-xx-ERROR-0102	Mandatory Parameter Missing	POST /remotesepp POST /remoteseppset	This error is observed if mandatory parameter is missing in request.	Verify that all mandatory parameter for configuration of Remote SEPP or Remote SEPP Set is present
SEPP-COM-xx-ERROR-0103	Connection could not be established on N32c interface	POST /remotesepp DELETE remotesepp/{name} PUT remotesepp/{name} PATCH remotesepp/{name}	This error is observed if n32c service is down or not up and running.	Verify that n32c service is up and running
SEPP-COM-xx-ERROR-0104	Invalid Value for Parameter		This Error occurs when user enters the invalid value for Enum Field in SEPP.
SEPP-COM-SVR-ERROR-0404	Unable to connect to EGW to sync config	PUT peerconfiguration/peersetconfiguration /routesconfiguration	This error is observed if config mgr is not able to update peer/peerset/routes configurations at EGW.	Verify that common configuration server is up and running.
SEPP-CN32FSEPP-ERROR-0013	PLMN ID Validation In Header Failed	NA	This error is observed if PLMN ID is not matched in header of the incoming request on CN32F microservice.	Verify if correct regex is configured against the header identifier in Header Configuration. Verify if MCC & MNC combination is present in the Remote PLMN ID List.
SEPP-CN32FSEPP-ERROR-0014	PLMN ID Validation In Body Failed	NA	This error is observed if PLMN ID is not matched in body of the incoming request on CN32F microservice.	Verify if correct regex is configured against the body IE in Body IE Configuration. Verify f MCC & MNC combination is present in the Remote PLMN ID List.
SEPP-PN32FSEPP-ERROR-0016	PLMN ID Validation In Header Failed	NA	This error is observed if PLMN ID is not matched in header of the incoming request on PN32F microservice.	Verify if correct regex is configured against the header identifier in Header Configuration. Verify if MCC & MNC combination is present in the helm based local PLMN ID list.
SEPP-PN32FSEPP-ERROR-0017	PLMN ID Validation In Body Failed	NA	This error is observed if PLMN ID is not matched in body of the incoming request on PN32F microservice.	Verify if correct regex is configured against the body IE in Body IE Configuration. Verify if MCC & MNC combination is present in the helm based local PLMN ID list.
SEPP-SECURITY-PLMN-HEADER-ERROR-0015	PLMN ID Validation In Header Failed	NA	Verify if correct regex is configured against the header in header Configuration. Verify if MCC & MNC combination is present in the helm based local PLMN ID list.	if PLMN ID is not matched in the header of the incoming request. Metrics can be checked for the details for which it has failed.
SEPP-SECURITY-PLMN-BODY-ERROR-0016	PLMN ID Validation in body failed	NA	Verify if correct regex is configured against the body IE in Body IE Configuration. Verify if MCC and MNC combination is present in the helm based local PLMN ID list.	if PLMN ID is not matched in the body of the incoming request. Metrics can be checked for the details for which it has failed.

The following are the error codes of Mediation feature:

Table 3-3 Mediation Error Codes and Recovery Steps

Error Code	Error Text	Command/ Method	Description	Recovery Steps
SEPP-MEDIATION-ERROR-001	Mediation Trigger Rule Not Found.	GET x`/sepp-mediation-trigger-rule-list/{triggerRuleListName} DELETE /sepp-mediation-trigger-rule-list/{triggerRuleListName}	Requested Trigger Rule List does not exist.	Give the Trigger Rule List Name that exist in Database.
SEPP-MEDIATION-ERROR-002	Unsupported Trigger Points	PUT /sepp-mediation-trigger-rule-list/{triggerRuleListName}	Trigger Points provided in configuration request body is not supported.	Provide valid Trigger Points in Configuration Request. Valid Trigger Points : N32_Egress_Request N32_Ingress_Response N32_Ingress_Request N32_Egress_Response
SEPP-MEDIATION-ERROR-003	Mediation Trigger Mandatory Parameter Update Not Allowed.	PUT /sepp-mediation-trigger-rule-list/{triggerRuleListName}	Trigger Rule List mandatory parameter like TriggerRuleListName can not be updated.	Make sure TriggerRuleListName you are providing in configuration request url is same as name in request url path.
SEPP-MEDIATION-ERROR-004	Trigger Rule is Mandatory Parameter.	PUT /sepp-mediation-trigger-rule-list/{triggerRuleListName}	If MediationAllEnabled is false and there is no TriggerRules or empty TriggerRules in request.	If MediationAllEnabled is false, then make sure there is TriggerRules Provided in Request.
SEPP-MEDIATION-ERROR-005	Invalid Error Status Code	PUT /mediation/feature	Invalid Http Status Code is provided is Error Configuration Request.	Make sure to provide valid HTTP Status Code in statusCode field in Error Configuration Request
SEPP-MEDIATION-ERROR-006	Invalid ResourceURI and HTTPMethod Error	PUT /sepp-mediation-trigger-rule-list/{triggerRuleListName}	ResourceURI and HttpMethod provided in Request is not valid.	Make sure to provide ResourceURI and HttpMethod combination that is configuration for SEPP, already present in Database.
SEPP-MEDIATION-ERROR-007	DELETE Not Allowed	DELETE /sepp-mediation-trigger-rule-list/{triggerRuleListName}	Trigger Rule List Delete Not Allowed.	Ensure you are deleting only that Trigger Rule List that is not associated with Remote SEPP Set.
SEPP-MEDIATION-ERROR-008	Trigger Rule Configuration Error	PUT /sepp-mediation-trigger-rule-list/{triggerRuleListName}	Error in Configuration of Trigger Rule List.	Ensure there is no duplicated ResourceURI and Method in request body.
SEPP-MEDIATION-ERROR-009	Mediation Trigger Rules Configuration Mandatory Parameter Missing Error	PUT /sepp-mediation-trigger-rule-list/{triggerRuleListName}	Mediation Trigger Rules Configuration Mandatory Parameter Missing in configuration request.	Ensure all mandatory parameters are present in Mediation Trigger Rule Configuration request.
SEPP-MEDIATION-ERROR-010	Multiple Local Trigger Rule List Configuration Error	PUT /sepp-mediation-trigger-rule-list/{triggerRuleListName}	Multiple Local Trigger Rule List Configuration is Not Allowed.	Make sure we are not configuring another Local Trigger Rule List if there is already one configured in DB. Only one Local Trigger Rule List can be configured for SEPP.
SEPP-MEDIATION-ERROR-011	Mediation Feature Mandatory Parameter Error	PUT /mediation/feature	Mediation Feature Configuration Mandatory Parameter is missing.	Make sure if FeatureEnabled is true in request then all field Error Configuration is present in request.
SEPP-MEDIATION-ERROR-012	Mediation Local Trigger Rule IPX Mode Error	PUT /sepp-mediation-trigger-rule-list/{triggerRuleListName}	In IPX Mode SEPP allow only 2 Trigger Points (N32 Ingress Request, N32 Egress Response) in local TRL configuration.	Make sure there is not any invalid Trigger Points like N32 Egress Request or N32 Ingress Response in Local Trigger Rule Configuration Request.
SEPP-MEDIATION-ERROR-013	Mediation service is not available	PUT /mediation/feature	Mediation Service Not deployed.	Before Enabling Mediation Feature through API , make sure Mediation Service is being deployed for SEPP.
SEPP-MEDIATION-ERROR-014	Invalid Error Action	PUT /mediation/feature	Invalid Error Action in Mediation Feature Configuration request.	Make sure to provide valid ErrorAction in Mediation Feature Configuration request in ErrorConfiguration section.

The following are the error codes of Cat-1 feature:

Table 3-4 Cat-1 Error Codes and Recovery Steps

Error Code	Error Text	Description	Recovery
SEPP-SECURITY-ERROR-001	Service API not in allowed list	If resource URI and Http Method is not matched as per the configured allowed list on SEPP.	Verify whether the proper Resource URI and HTTP method is configured in the CNC Console GUI. Go to the Security Countermeasure section, check under the Service API Allowed List for that particular Allowed list name for N32 Egress or N32 Ingress Direction.
SEPP-CN32FSEPP-ERROR-0012	Service API Validation Failed	This error occurs on CN32F microservice. If resource URI and Http Method is not matched as per the configured allowed list on SEPP.	Verify whether the proper Resource URI and HTTP method is configured in the CNC Console GUI. Go to the Security Countermeasure section, check under the Service API Allowed List for that particular Allowed list name for N32 Egress or N32 Ingress Direction.
SEPP-PN32FSEPP-ERROR-0015	Service API Validation Failed	This error occurs on PN32F microservice. If resource URI and Http Method is not matched as per the configured allowed list on SEPP.	Verify whether the proper Resource URI and HTTP method is configured in the CNC Console GUI. Go to the Security Countermeasure section, check under the Service API Allowed List for that particular Allowed list name for N32 Egress or N32 Ingress Direction.

The following are the error codes of Cat-2 Network ID Validation feature:

Table 3-5 Cat-2 Network ID Error Codes and Recovery Steps

Error Code	Error Text	Description	Recovery
SEPP-CN32FSEPP-ERROR-0013	Network ID Validation In Header Failed	Check whether PLMN ID is not matched in header of the incoming request on CN32F microservice.	Verify if correct regex is configured against the header identifier in Header Configuration. Verify if MCC and MNC combination is present in the visitor or target PLMN ID List based on the associated SEPP configuration
SEPP-CN32FSEPP-ERROR-0014	Network ID Validation In Body Failed	Check whether PLMN ID is not matched in body of the incoming request on CN32F microservice.	Verify if correct regex is configured against the body IE in Body IE Configuration. Verify f MCC and MNC combination is present in the home or visitor PLMN ID List based on configuration of associated SEPP.
SEPP-PN32FSEPP-ERROR-0016	Network ID Validation In Header Failed	Check whether PLMN ID is not matched in header of the incoming request on PN32F microservice.	Verify if correct regex is configured against the header identifier in Header Configuration. Verify if MCC and MNC combination is present in the target or visitor PLMN ID list based on the associated SEPP configuration.
SEPP-PN32FSEPP-ERROR-0017	Network ID Validation In Body Failed	Check whether PLMN ID is not matched in body of the incoming request on PN32F microservice.	Verify if correct regex is configured against the body IE in Body IE Configuration. Verify if MCC and MNC combination is present in the target or visitor PLMN ID list based on the associated SEPP configuration.

Table 3-6 Cat-3 Previous Location Check Error Codes

Error Code	Error Text	Description	Recovery
SEPP-PREVIOUS-LOCATION-CHECK-VALIDATION-ERROR-0019 or SEPP-PN32FSEPP-ERROR-0018	Previous Location Check Validation Failed	This error code is observed only on PN32F microservice. If Serving Network ID is not matching against the serving network ID coming from UDR response, to check whether UE authentication is success. This error also occurs if the authentication from UDR is false.	Verify whether the correct regex is configured against the serving network identifier in either Header or Body Configuration. Verify whether the MCC and MNC combination is present in the Serving Network ID. Verify whether the identifier coming in the ingress request on PN32F microservice is also same as the serving Network name coming as part of the UDR response if UE authentication is successful.
SEPP-PREVIOUS-LOCATION-CHECK-VALIDATION-EXCEPTION-0020	Previous Location Check Validation Failed Due To Exception	This error will occur if the system is not able to extract the SUPI, or if the incoming message doesn't contain SUPI, or if there are any sort of connectivity issues with NRF or UDR.	Verify if correct regex for UE ID in Header or Body configuration screen is configured due to which correct UE ID value is extracted. Verify if the incoming message has SUPI. Verify whether the FQDN or IP fetched for the UDR as part of NRF discovery call is reachable. Verify if UDR discovery procedure from NRF is successful. Verify if the SUPI received in the Ingress request message is part of the SUPI range received in UDR profile from discovery response from NRF.

Error Code

Error Text

Description

Recovery

SEPP-PREVIOUS-LOCATION-CHECK-VALIDATION-ERROR-0019 or

SEPP-PN32FSEPP-ERROR-0018

Previous Location Check Validation Failed

This error code is observed only on PN32F microservice.

If Serving Network ID is not matching against the serving network ID coming from UDR response, to check whether UE authentication is success.

This error also occurs if the authentication from UDR is false.

Verify whether the correct regex is configured against the serving network identifier in either Header or Body Configuration.
Verify whether the MCC and MNC combination is present in the Serving Network ID.
Verify whether the identifier coming in the ingress request on PN32F microservice is also same as the serving Network name coming as part of the UDR response if UE authentication is successful.

SEPP-PREVIOUS-LOCATION-CHECK-VALIDATION-EXCEPTION-0020

Previous Location Check Validation Failed Due To Exception

This error will occur if the system is not able to extract the SUPI, or if the incoming message doesn't contain SUPI, or if there are any sort of connectivity issues with NRF or UDR.

Verify if correct regex for UE ID in Header or Body configuration screen is configured due to which correct UE ID value is extracted.
Verify if the incoming message has SUPI.
Verify whether the FQDN or IP fetched for the UDR as part of NRF discovery call is reachable.
Verify if UDR discovery procedure from NRF is successful.
Verify if the SUPI received in the Ingress request message is part of the SUPI range received in UDR profile from discovery response from NRF.