6 SEPP Response Codes
Following are the SEPP Response Codes:
- N32c Handshake Response Codes
 - N32f Message Forwarding Response Codes
 
N32c Handshake Response Codes
Table 6-1 N32c Handshake Response Codes
| Request | Response Code | ResponseBody | Reference | Use Case | Comment/Remarks | 
|---|---|---|---|---|---|
| Capability Exchange | 200 OK | SecNegotiateRspBody | TS29573_N32_Handshake.yaml | Handshake success | Handshake Success | 
| 400 Bad Request | Problem Details | TS29573_N32_Handshake.yaml | 
                                    
                                    
  | 
                                 Handshake fail | |
| 404 Not Found | Problem Details | 3gpp Spec 29500 | Incorrect API | ||
| 405 Method Not Allowed | Problem Details | 3gpp Spec 29500 | When request method other than POST is used | ||
| 411 Length Required | Problem Details | TS29573_N32_Handshake.yaml | When Content Length header is not present in request. | ||
| 413 Payload Too Large | Problem Details | TS29573_N32_Handshake.yaml | When request entity is larger than limits defined by server. | ||
| 415 Unsupported Media Type | Problem Details | TS29573_N32_Handshake.yaml | When payload format is not in json. When "Content-Type:application/json" is not present. | ||
| 429 Too Many Requests | Problem Details | TS29573_N32_Handshake.yaml | Too many requests in a given amount of time ("rate limiting"). | ||
| 500 Internal Server Error | Problem Details | TS29573_N32_Handshake.yaml | 
                                    
                                    
  | 
                                 ||
| 503 Service Unavailable | null | TS29573_N32_Handshake.yaml | When sepp backend service is down. | ||
| 501 Not Implemented | Problem Details | When capability mismatch happens. | |||
| 401 Unauthorized | Problem Details | When request received for unknown peer sepp. | |||
| 403 Forbidden | Problem Details | When request received for disabled peer sepp. | 
N32f Message Forwarding Response Codes
Table 6-2 N32f Message Forwarding Response Codes
| Pod Name | Response Code | ResponseBody | Use Case | Reference | Comment | 
|---|---|---|---|---|---|
| cN32f-Sepp | 200 OK | Success Body | Success | TS29573_JOSEProtectedMessageForwarding.yaml | |
| 404 Not Found | Problem Details | N32f Context Not Found | 3gpp Spec 29500 | ||
| 401 Unauthorised | Problem Details | Context Not Established | 3gpp Spec 29500 | ||
| 401 Unauthorised | Problem Details | Security Capability apart from TLS | 3gpp Spec 29500 | ||
| 400 Bad Request | Problem Details | 3GPP-target-sbi-apiroot/destination producer NF is absent | TS29573_JOSEProtectedMessageForwarding.yaml | ||
| 503 Service Unavailable | Problem Details | Service Unavailable | TS29573_JOSEProtectedMessageForwarding.yaml | ||
| pN32f-Sepp | 400 Bad Request | Problem Details | 3GPP-target-sbi-apiroot/destination producer NF is absent | TS29573_JOSEProtectedMessageForwarding.yaml | |
| 503 Service Unavailable | Problem Details | Service Unavailable | TS29573_JOSEProtectedMessageForwarding.yaml | 
Note:
All the exceptions/error response codes sent by the N32-EGW at consumer sand PLMN-EGW at producer will be same and we will be adding a problem statement which contains the reason why it occured.