CSCF SIP Hexadecimal Error Codes

Call Session Control Function

1	Introduction
2	Error Code Description
2.1	Error Code Version
2.2	Use Case
2.3	Node Type
2.4	Internal Node Type
2.5	Node Path
2.6	Reason
2.7	Optional Code

1 Introduction

This document describes the Call Session Control Function (CSCF) Session Initial Protocol (SIP) hexadecimal error response codes that can be generated by the CSCF because of internal errors or received Diameter error codes.

Hexadecimal error codes consist of 9–15 hexadecimal digits that are added to the end of the Reason-Phrase in SIP responses. As stated in RFC 3261, the Reason-Phrase is intended for the human user, a troubleshooter in this case, and is to be ignored or removed by clients.

Note:: Hexadecimal error response codes can be added, removed, or modified between different releases.

2 Error Code Description

In the initial version (version 0), the hexadecimal error code is made up of five mandatory parts and one optional part as shown in Figure 1. In the subsequent version (version 1), the hexadecimal error code is made up of five mandatory parts and one optional part as shown in Figure 2. The hexadecimal error code is added to the reason phrase of some SIP responses and provides further information describing the error cause.

Figure 1 Hexadecimal Error Code Example with Version 0

Figure 2 Hexadecimal Error Code Example with Version 1

The parts that make up an error code are described in the following sections:

Section 2.1 Error Code Version
Section 2.2 Use Case
Section 2.3 Node Type
Section 2.4 Internal Node Type
Section 2.5 Node Path
Section 2.6 Reason
Section 2.7 Optional Code

2.1 Error Code Version

The version part of the code describes the error code version in use. The error code version is updated when the format of the error code or the existing values are modified. Backwards compatibility is not guaranteed when the version is updated.


Value	Description
0	For version 0, full hexadecimal error code consists of Error Code Version, Use Case, Node Type, Internal Node Type, Reason and Optional Code.
1	For version 1, full hexadecimal error code consists of Error Code Version, Use Case, Node Type, Node Path, Reason and Optional Code.
2-F	Reserved for future use

2.2 Use Case

The use case part of the code describes the error code type, as follows:


Value	Description
0	Undefined
1	Registration
2	Originating
3	Terminating
4	Originating from AS
5-F	Reserved for future use

2.3 Node Type

The node types part of the code defines the origin of the error code, as follows:


Value	Description
00	Undefined
01	CSCF
02	I-CSCF
03	S-CSCF
04	P-CSCF
05	E-CSCF
06	BCF
07	EATF
08-FF	Reserved for future use

2.4 Internal Node Type

This field is only applicable for error code version 0. The internal node type part of the code defines the origin of the error code, as follows:


Value	Description
0	CSCF executes as ISP-CSCF
1	CSCF executes as SP-CSCF
2	CSCF executes as PI-CSCF
3	CSCF executes as IS-CSCF
4	CSCF executes as I-CSCF
5	CSCF executes as S-CSCF
6	CSCF executes as P-CSCF
7	CSCF executes as BCF
8	CSCF executes as E-CSCF
9	CSCF executes as P-CSCF handling an emergency call
A	CSCF executes as EATF
B-F	Reserved for future use

2.5 Node Path

This field is only applicable for error code version 1. The node path part of the code defines the logic, which had been executed by the node when the SIP request was rejected. Each single digit of the node path field represents a node as defined below:


Value	Description
0	Undefined
1	Reserved for future use
2	I-CSCF executed
3	S-CSCF executed
4	P-CSCF executed
5	E-CSCF executed
6	BCF executed
7	EATF executed
8-F	Reserved for future use

The field consists of three digits which are read from left to right and represent the collocated nodes the request passed. Examples of values for this field follow:


Value	Description
000	Undefined
002	Logic for I-CSCF executed
003	Logic for S-CSCF executed
004	Logic for P-CSCF executed
005	Logic for E-CSCF executed
006	Logic for BCF executed
023	Logic for I-CSCF followed by S-CSCF executed
034	Logic for S-CSCF followed by P-CSCF executed
042	Logic for P-CSCF followed by I-CSCF executed
043	Logic for P-CSCF followed by S-CSCF executed
234	Logic for I-CSCF followed by S-CSCF and P-CSCF executed
423	Logic for P-CSCF followed by I-CSCF and S-CSCF executed

2.6 Reason

The reason part of the code defines the reason for the error code, as follows:


Value	Description
0100	UAA with an application error result code was received. Error result code is described in the optional-code field.
0101	Both or neither of Experimental-Result AVP and Result-Code AVP received in UAA.
0102	Both Server-Capabilities AVP and Server-Name AVP received in UAA.
0103	UAA received with a non-SIP address in Server-Name AVP.
0104	UAA received with a Server-Name AVP and an invalid Roaming-Awareness AVP.
0105	UAA received with no Server-Name AVP and an invalid Roaming-Awareness AVP.
0106	UAA contains a Server-Name AVP without any value.
0107	UAA received with a Server-Name AVP and an unexpected Result-Code described in the optional-code field.
0108	No matching configured S-CSCF names were found based on the Server-Capabilities in the UAA.
0109	UAA received containing a Server-Name AVP. Local Zone Policy is enabled but the resource broker is not configured and no colocated S-CSCF has been configured.
010A	UAA with a protocol error result code was received.
010B	No UAA was received due to a timeout or a connection problem.
010C	No UAA was received due to an internal communication error.
010D	Reselection of S-CSCF failed, since no more matching S-CSCF names could be found based on the Server-Capabilities received in the UAA.
010E	Both or neither of Experimental-Result AVP and Result-Code AVP received in UAA during reselection of an S-CSCF node.
010F	Both Server-Capabilities AVP and Server-Name AVP received in UAA during reselection of an S-CSCF node.
0110	UAA with an application error result code was received during reselection of an S-CSCF node. Error result code is described in the optional-code field.
0111	No matching configured S-CSCF names were found based on the Server-Capabilities received in the UAA. The UAA was received after requesting the registration and capabilities from HSS since the assigned S-CSCF did not respond.
0112	UAA with a protocol error result code was received during reselection of an S-CSCF node.
0113	No UAA was received due to a timeout or a connection problem. The UAR was sent to request the registration and capabilities from HSS since the assigned S-CSCF did not respond.
0114	No UAA was received due to an internal communication error. The UAR was sent to request the registration and capabilities from HSS since the assigned S-CSCF did not respond.
0115	Reselection of S-CSCF failed while processing the Second UAA, since no more matching S-CSCF names could be found based on the Server-Capabilities received in the UAA.
0116	In handling reselection of S-CSCF on the originating side, the resource broker was not able to find a server matching the requested server capabilities.
0117	In handling reselection of S-CSCF on the terminating side, the resource broker was not able to find a server matching the requested server capabilities.
0118	In processing LIA on the originating side, the resource broker was not able to find a server matching the requested server capabilities.
0119	In processing LIA on the terminating side, the resource broker was not able to find a server matching the requested server capabilities.
011A	In processing LIA of the second LIR on the originating side, the resource broker was not able to find a server matching the requested server capabilities.
011B	In processing LIA of the second LIR on the terminating side, the resource broker was not able to find a server matching the requested server capabilities.
011C	LIA on the originating side contains an invalid Server-Name AVP.
011D	LIA on the terminating side contains an invalid Server-Name AVP.
011E	Communication error with Cx interface for the 1st LIR on the originating side.
011F	Communication error with Cx interface for the 1st LIR on the terminating side.
0120	Communication error with Cx interface for the 2nd LIR on the originating side.
0121	Communication error with Cx interface for the 2nd LIR on the terminating side.
0122	Register or deregister message throttled due to HSS congestion. UAR not sent.
0123	Originating non-register message throttled due to HSS congestion. LIR not sent.
0124	Terminating non-register message throttled due to HSS congestion. LIR not sent.
0125	LIA for the first LIR on the originating side does not contain either a Result Code AVP or an Experimental Result AVP, or contains both at the same time.
0126	LIA for the first LIR on the terminating side does not contain either a Result Code AVP or an Experimental Result AVP, or contains both at the same time.
0127	LIA for the first LIR on the originating side contains both Server-Capabilities and Server-Name AVPs.
0128	LIA for the first LIR on the terminating side contains both Server-Capabilities and Server-Name AVPs.
0129	LIA for the first LIR with a Diameter error result code was received on the originating side. Error result code is described in the optional-code field.
012A	LIA for the first LIR with a Diameter error result code was received on the terminating side. Error result code is described in the optional-code field.
012B	LIA for the first LIR with a protocol error result code was received on the originating side. Error result code is described in the optional-code field.
012C	LIA for the first LIR with a protocol error result code was received on the terminating side. Error result code is described in the optional-code field.
012D	Internal error in the diameter stack for the Cx interface occurred for the first LIR on the originating side.
012E	Internal error in the diameter stack for the Cx interface occurred for the first LIR on the terminating side.
012F	LIA for the second LIR on the originating side does not contain either a Result Code AVP or an Experimental Result AVP, or contains both at the same time.
0130	LIA for the second LIR on the terminating side does not contain either a Result Code AVP or an Experimental Result AVP, or contains both at the same time.
0131	LIA for the second LIR on the originating side contains a Server-Name AVP.
0132	LIA for the second LIR on the terminating side contains a Server-Name AVP.
0133	LIA for the second LIR with a Diameter error result code was received on the originating side. Error result code is described in the optional-code field.
0134	LIA for the second LIR with a Diameter error result code was received on the terminating side. Error result code is described in the optional-code field.
0135	LIA for the second LIR with a protocol error result code was received on the originating side. Error result code is described in the optional-code field.
0136	LIA for the first LIR with a protocol error result code was received on the terminating side. Error result code is described in the optional-code field.
0137	Internal error in the diameter stack for the Cx interface occurred for the second LIR on the originating side.
0138	Internal error in the diameter stack for the Cx interface occurred for the second LIR on the terminating side.
0139	Reselection of S-CSCF failed, since no more matching S-CSCF names could be found based on the Server-Capabilities received in the UAA.
013A	Reregister message throttled due to HSS congestion. Second UAR not sent.
013B	No UAA was received for the first Uar due to a Diameter All Links congested error at registration
013C	No Lia was received for the first Lir due to a Diameter All Links congested error
013D	No Lia was received for the first Lir on the First Orig side due to a Diameter All Links congested error
013E	No UAA was received for the second Uar due to a Diameter All Links congested error
013F	No Lia was received for the second Lir due to a Diameter All Links congested error
0140	No Lia was received for the first Lir on the Second Orig side due to a Diameter All Links congested error
0200	No SAA was received after sending deregistration SAR. This SAR was sent since an invalid Supported-Features AVP was detected in the initial SAA.
0201	An unsupported or invalid Supported-Features AVP was detected in the SAA.
0202	SAA with a protocol error result code was received after sending deregistration SAR. This SAR was sent since an unsupported or invalid Supported-Features AVP was detected in the initial SAA.
0203	No SAA was received due to an internal communication error when sending deregistration SAR. This SAR was sent since an unsupported or invalid Supported-Features AVP was detected in the initial SAA.
0204	No SAA was received due to a timeout or a connection problem.
0205	Both or neither of Experimental-Result AVP and Result-Code AVP were received in SAA.
0206	The User-Name AVP was not present in the SAA.
0207	The User-Data AVP was not present in the SAA.
0208	An invalid Charging-Information AVP was detected in SAA.
0209	The Origin-Host AVP was not present in the SAA.
020A	SAA with a protocol error result code was received.
020B	Failed to parse User-Data AVP in SAA, while restoring contacts.
020C	Failed to restore user data received in SAA.
020D	Failed to restore contacts received in SAA due to internal error.
020E	The selected contact did not match any of the restored contacts received in SAA.
020F	Non-register request failed due to an internal communication error.
0210	Failed to make user data persistent in Database due to an internal error.
0211	Code is deprecated.
0212	Code is deprecated.
0213	Could not retrieve restoration information in SAA on originating side. Restoration procedure was enabled but Restoration-Info AVP was not present in SAA or HSS did not support restoration.
0214	SAA with an application error result code was received at originating side while restoration procedure was enabled. Error result code is described in the optional-code field.
0215	SAA with an application error result code was received at originating side. Error result code is described in the optional-code field.
0216	SAA with an application error result code was received at terminating side. Error result code is described in the optional-code field.
0217	Deregistration of contact has failed due to an internal database problem.
0218	No SAA was received due to a timeout or a connection problem at deregistration of last contact for IMPI.
0219	Both or none Experimental-Result AVP and Result-Code AVP received in SAA at deregistration of last contact for IMPI.
021A	SAA with an application error result code was received at deregistration of last contact for IMPI. Error result code is described in the optional-code field.
021B	Deregistration of last contact for IMPI has failed due to an internal error.
021C	SAA with a protocol error result code was received at deregistration of last contact for IMPI.
021D	No SAA was received due to an internal communication error at deregistration of last contact for IMPI.
021E	No SAA was received due to a timeout or a connection problem at deregistration of last contact.
021F	Both or neither of Experimental-Result AVP and Result-Code AVP were received in SAA at deregistration of last contact.
0220	SAA with an application error result code was received at deregistration of last contact. Error result code is described in the optional-code field.
0221	Deregistration of last contact has failed due to an internal database problem.
0222	SAA with a protocol error result code was received at deregistration of last contact.
0223	No SAA was received due to an internal communication error at deregistration of last contact.
0224	The User-Data AVP was not present in the SAA received at deregistration of last contact.
0225	An invalid Charging-Information AVP was detected in SAA received at deregistration of last contact.
0226	The Origin-Host AVP was not present in the SAA received at deregistration of last contact.
0227	Failed to restore contacts received in SAA at deregistration of last contact.
0228	Failed to parse User-Data AVP in SAA while restoring contacts at deregistration of last contact.
0229	Failed to restore user data received in SAA due to parse error of the User-Data AVP or an internal database error.
022A	Code is deprecated.
022B	No SAA was received due to a timeout or a connection problem at deregistration of last contact after restoration.
022C	Both or neither of Experimental-Result AVP and Result-Code AVP were received in SAA when CSCF deregistered last contact after restoration.
022D	SAA with an application error result code was received when CSCF deregistered last contact after restoration. Error result code is described in the optional-code field.
022E	SAA with a protocol error result code was received when CSCF deregistered last contact after restoration.
022F	No SAA was received due to an internal communication error when CSCF deregistered last contact after restoration.
0230	Registration of additional contact has failed due to an internal database problem.
0231	No SAA was received due to a timeout or a connection problem at registration of first contact for IMPI.
0232	Both or neither of Experimental-Result AVP and Result-Code AVP were received in SAA at registration of first contact of IMPI.
0233	SAA with an application error result code was received at registration of first contact for IMPI. Error result code is described in the optional-code field.
0234	The User-Name AVP was not present in the SAA received at registration of first contact for IMPI.
0235	SAA with a protocol error result code was received at registration of first contact for IMPI.
0236	No SAA was received due to an internal communication error at registration of first contact for IMPI.
0237	No SAA was received due to a timeout or a connection problem after sending deregistration SAR. This SAR was sent since the User-Data AVP could not be parsed or there was an internal database fault.
0238	The User-Data AVP could not be parsed or there was an internal database fault.
0239	SAA with a protocol error result code was received after sending deregistration SAR. This SAR was sent since the User-Data AVP could not be parsed or there was an internal database fault.
023A	No SAA was received due to an internal communication error when sending deregistration SAR. This SAR was sent since the User-Data AVP could not be parsed or there was an internal database fault.
023B	No SAA was received due to a timeout or a connection problem at initial registration.
023C	Both or neither of Experimental-Result AVP and Result-Code AVP were received in SAA at initial registration.
023D	SAA with an application error result code was received at initial registration. Error result code is described in the optional-code field.
023E	The User-Name AVP was not present in the SAA received at initial registration.
023F	SAA with a protocol error result code was received at initial registration.
0240	No SAA was received due to an internal communication error at initial registration.
0241	No SAA was received due to a timeout or a connection problem at initial registration.
0242	Both or neither of Experimental-Result AVP and Result-Code AVP were received in SAA at initial registration.
0243	SAA with an application error result code was received at initial registration. Error result code is described in the optional-code field.
0244	The User-Name AVP was not present in the SAA received at initial registration.
0245	The User-Data AVP was not present in the SAA received at initial registration.
0246	An invalid Charging-Information AVP was detected in SAA received at initial registration.
0247	The Origin-Host AVP was not present in the SAA received at initial registration.
0248	SAA with a protocol error result code was received at initial registration.
0249	No SAA was received due to an internal communication error at initial registration.
024A	Failed to restore contacts received in SAA due to faulty data in the Restoration-Info AVP or an internal database error, when performing the restoration procedure at reregistration.
024B	The selected contact could not be added to the database due to an internal error when performing the restoration procedure at reregistration.
024C	Adding the contact would exceed the maximum number of contacts limit. Contacts were restored after performing restoration procedure at reregistration.
024D	No SAA was received due to a timeout or a connection problem at reregistration after restoration.
024E	Both or neither of Experimental-Result AVP and Result-Code AVP were received in SAA when CSCF registered contact after restoration.
024F	SAA with an application error result code was received when CSCF registered contact after restoration. Error result code is described in the optional-code field.
0250	Adding the contact would exceed the maximum number of contacts limit. Contacts were restored after performing restoration procedure at reregistration.
0251	SAA with a protocol error result code was received when CSCF registered contact after restoration.
0252	No SAA was received due to an internal communication error when CSCF registered contact after restoration.
0253	Reregistration failed due to a internal database problem.
0254	Restoration failed at deregistration of last contact due to an internal database problem.
0255	Download of wildcarded user profile failed because of missing P-Profile-Key in a non-Register SIP request.
0256	Failed to restore wildcarded user because of missing P-Profile-Key in a non-Register SIP request.
0257	SAA with diameter error code was received at initial registration userNotRegistered.
0258	SAA with error code DiameterAlreadyRegistered was received at registration of first contact for IMPI.
0259	Non-Register request receives SAA with error code DiameterAlreadyRegistered
0260	SAA with diameter error code was received at initial registration userUnRegistered.
0261	Code is deprecated.
0262	Code is deprecated.
0263	Code is deprecated.
0264	Code is deprecated.
0265	User state mismatch was detected between CSCF and HSS, probably because of S-CSCF reselection, but failed to delete any user data already existing in the CSCF
0266	User data was flagged for silent delete because of user state mismatch between CSCF and HSS (S-CSCF reselection), but we failed to commit the cache with the deleted user data to DBN
0267	User data was flagged for silent delete because of user state mismatch between CSCF and HSS (S-CSCF reselection), but we will not do restoration, so we attempt to roll-back changes made to user data from the cache, and this roll-back fails
0268	Failed to restore P-CSCF contacts saved internally prior to deleting all user data.
0269	Code is deprecated.
026A	Internal logic error. Trying to execute logic for restoring a P-CSCF-only contact into a PS-CSCF-state contact, however contact is originally not a P-CSCF-only contact.
026B	Wildcarded public identity registration forbidden as ScscfwImpuEnabled configuration parameter is set to FALSE.
026C	Illegal usage of service priority by unauthorized user for initial request.
026D	Illegal usage of service priority by unauthorized user for inside request.
026E	Originating calls from users with no registration or with only emergency registration not allowed.
026F	User state mismatch was detected between CSCF and HSS for wIMPU request, probably because of S-CSCF reselection, but failed to delete any user data already existing in the CSCF
0270	Code is deprecated.
0271	Restoration failed at deregistration of contact due to an internal database problem.
0272	No Assignment SAA contains another Associated-Registered-Identities AVP.
0273	Originating non-register request received from a user that is not registered but overall restoration procedure is disabled.
0274	Originating non-register request received from a user that is not registered. Overall restoration procedure is enabled but not performed because restoration procedure to allow originating non-register requests is disabled.
0275	Emergency Registration for Wildcarded Public Identity is forbidden.
0276	Originating non-register request throttled due to HSS congestion. SAR not sent.
0277	The Loose-Route-Indication received from HSS is not allowed to be set LOOSE_ROUTE_REQUIRED when registering a "bnc" contact.
0278	No non-barred default public id in IRS.
0279	Code is deprecated.
0280	Failed to read contacts due to an internal database error.
0281	Failed to update contacts due to an internal database error.
0282	Failed to read user profile due to an internal database error.
0283	Failed to update user profile due to an internal database error.
0284	Code is deprecated.
0285	Failed to find the current contact in the restoration data.
0286	Code is deprecated.
0287	Registration of additional contact and new PrivateId has failed due to an internal database failure.
0288	Registration of additional contact and new PrivateId has failed due to an internal database failure.
0289	Registration of Public GRUU contact has failed due to an internal database failure.
028A	The selected contact could not be added to the database due to exceeding the maximum contact limit per user.
028B	Registration of additional contact has failed due to exceeding the maximum contact limit per user.
028C	Registration of additional contact and new PrivateId has failed due to exceeding the maximum contact limit per user.
028D	Registration of additional contact and new PrivateId has failed due to exceeding the maximum contact limit per user.
028E	Registration of Public GRUU contact has failed due to exceeding the maximum contact limit per user.
028F	The selected contact could not be added to the database due to exceeding the maximum contact limit per user.
0290	No SAA was received due to All Links congestion error at de-registration.
0291	No SAA was received due to All Links congestion error for Second Sar at Initial Registration
0292	No SAA was received due to All Links congestion error for Sar Initial Registration
0293	No SAA was received due to All Links congestion error for Put Only Sar Initial Registration
0294	No SAA was received due to All Links congestion error for Sar Administrative De-Registration
0295	No SAA was received due to All Links congestion error for Sar Registration of IMPI
0296	No SAA was received due to All Links congestion error for non registration
0297	No SAA was received due to All Links congestion error after sending de-registration SAR
0298	No SAA was received due to All Links congestion error after sending second de-registration SAR of last contact due to All Link congestion error.
0299	No SAA was received due to All Links congestion error after sending de-registration SAR of last contact due to All Link congestion error.
029A	The Restoration-Info AVP was not present in the SAA received with Exp-Result code set as DIAMETER_ERROR_IN_ASSIGNEMENT_TYPE.
0300	Invalid or missing username in NBA Challenge initial registration request.
0301	NBA Challenge authentication is needed for Register request without Authorization header.
0302	Initial Register request with Authorization header containing NBA Challenge credentials with empty nonce value.
0303	SIP request with NBA Challenge credentials in which one or more mandatory directives is missing or has empty value.
0304	SIP request with NBA Challenge credentials containing incorrect nonce value.
0305	Invalid authentication scheme is encountered.
0306	User is found blacklisted in originating non-registration traffic scenarios.
0307	User is found blacklisted in registration traffic scenarios.
0308	User is found blacklisted in registration query traffic scenario.
0309	Cannot find the authenticated contact by via set for registered user.
030A	No private ID is found for SIP Digest from contact or proxy-authorization header.
030B	No authentication vector for non-registration request.
030C	UE IP address for non-registration request does not match with IP address received in MAA.
030D	Invalid authorization header in registration query traffic scenario.
030E	No authentication vector in registration query traffic scenario.
030F	Invalid authentication scheme in registration traffic scenario.
0310	NBA failure due to missing DSL location in PANI header in registration traffic scenario.
0311	Invalid authorization header in unprotected AKA registration traffic scenario.
0312	Authentication failed for unprotected registration due to ongoing registration.
0313	Invalid authorization header in protected AKA registration traffic scenario.
0314	Call ID in authentication data does not match with call ID in registration traffic scenario.
0315	Register request with Authorization header containing incorrect AKA response value
0316	Invalid authorization header in SIP Digest initial registration request.
0317	No authentication vector in SIP Digest initial registration request.
0318	Missing authorization header in SIP Digest initial or query registration request.
0319	No authentication vector in SIP Digest reregistration or deregistration.
031A	NBA MAA failure due to missing DSL location in PANI header in registration traffic scenario.
031B	NBA MAA authentication failure in registration traffic scenario.
031C	UE IP address for registration request does not match with IP address received in MAA.
031D	MAA answered with an application error result code for registration traffic scenario. Error result code is described in the optional-code field.
031E	MAA protocol error received for registration traffic scenario. Error result code is described in the optional-code field.
031F	AKA MAA error result received for registration traffic scenario. Error result code is described in the optional-code field.
0320	NBA MAA error result received for registration traffic scenario. Error result code is described in the optional-code field.
0321	SIP Digest MAA error result received for registration traffic scenario. Error result code is described in the optional-code field.
0322	GIBA MAA error result received for registration traffic scenario. Error result code is described in the optional-code field.
0323	Message throttled due to HSS congestion. MAR not sent.
0324	Failed to read digest authentication data due to an internal database error.
0325	AKA authentication is needed after successful download of the AKA authentication vector from HSS.
0326	Register request with Authorization header containing AKA directives for a user whose AKA authentication vector is not available.
0327	AKA reauthentication is needed for Register request with Authorization header containing integrity-protected=no.
0328	AKA reauthentication is needed for Register request with Authorization header containing integrity-protected=yes.
0329	SIP request with SIP Digest credentials in which one or more mandatory directives is missing or has empty value.
032A	SIP request with SIP Digest credentials in which the algorithm directive is missing or has empty value when PropCxGmCompatibilityEnabled=false.
032B	SIP request with SIP Digest credentials containing incorrect realm value.
032C	SIP request with SIP Digest credentials containing incorrect algorithm value.
032D	SIP request with SIP Digest credentials containing incorrect nonce value.
032E	SIP request with SIP Digest credentials containing incorrect nonce count value.
032F	SIP request with SIP Digest credentials containing incorrect response value.
0330	SIP Digest authentication is needed for Register request without Authorization header.
0331	Register Query request with Authorization header containing SIP Digest credentials with empty response value.
0332	Second round Register Query request with Authorization header containing SIP Digest credentials and incorrect source IP address.
0333	SIP Digest authentication is needed for Register Query request.
0334	Initial Register request with Authorization header containing SIP Digest credentials with empty response value.
0335	Second round initial Register request with Authorization header containing SIP Digest credentials and incorrect source IP address.
0336	Initial Register request with Authorization header containing SIP Digest credentials with incorrect nonce value, incorrect bottom via or sent too late after the first round request.
0337	ReRegister or DeRegister request without Authorization header or containing SIP Digest credentials with empty response value.
0338	Second round ReRegister or DeRegister request with Authorization header containing SIP Digest credentials and incorrect source IP address.
0339	Second round pipelined ReRegister or DeRegister request with Authorization header containing SIP Digest credentials and incorrect source IP address.
033A	Register request with Authorization header containing SIP Digest credentials and incorrect source IP address is challenged after successful download of the HA1 digest from HSS.
033B	Register request with Authorization header containing SIP Digest credentials with empty response value is challenged after successful download of the HA1 digest from HSS.
033C	SIP Digest authentication is needed after successful download of the HA1 digest from HSS.
033D	SIP request withiout Proxy-Authorization header or containing SIP Digest credentials with empty response value.
033E	Second round SIP request with Proxy-Authorization header containing SIP Digest credentials and incorrect source IP address.
033F	Second round pipelined SIP request with Proxy-Authorization header containing SIP Digest credentials and incorrect source IP address.
0340	Failed to update digest authentication data due to an internal database error.
0341	Failed to read AKA authentication data due to an internal database error.
0342	Failed to update AKA authentication data due to an internal database error.
0343	Failed to update authentication blacklist data due to an internal database error.
0344	SIP request with NBA Challenge credentials containing incorrect nonce count value.
0345	ReRegister or DeRegister request without Authorization header or containing NBA Challenge credentials with empty nonce value.
0346	Second round ReRegister or DeRegister request with Authorization header containing NBA Challenge credentials and incorrect source IP address.
0347	Second round pipelined ReRegister or DeRegister request with Authorization header containing NBA Challenge credentials and incorrect source IP address.
0348	NBA Challenge authentication is needed after successful download of the LineIds from HSS.
0349	Register Query request without Authorization header or containing NBA Challenge credentials with empty nonce value.
034A	Second round Register Query request with Authorization header containing NBA Challenge credentials and incorrect source IP address.
034B	NBA Challenge authentication is needed for Register Query request.
034C	SIP request without Proxy-Authorization header or containing NBA Challenge credentials with empty nonce value.
034D	Second round SIP request with Proxy-Authorization header containing NBA Challenge credentials and incorrect source IP address.
034E	Second round pipelined SIP request with Proxy-Authorization header containing NBA Challenge credentials and incorrect source IP address.
034F	GIBA MAA error result received for originating non Register traffic scenario. Error result code is described in the optional-code field.
0350	MAR internal error result received for originating non Register traffic scenario.
0351	MAR internal error result received for originating non Register traffic scenario due to all Diameter links congestion
0352	MAR internal error result received for Register traffic scenario.
0353	MAR internal error result received for Register traffic scenario due to all Diameter links congestion
0400	Deregistration from an emergency contact is not allowed.
0401	Failure to remove inconsistent user from database.
0402	User is seen as registered in P-CSCF but not in S-CSCF, removal of user's registration in P-CSCF is requested.
0403	Maximum number of allowed active contacts has been reached.
0404	The request failed FQDN validation.
0405	The AKA contact already exists.
0406	Emergency Registration for Wildcarded Public Identity is forbidden.
0407	Failed to parse Authorization header in SIP request.
0408	Contact header must contain the URI parameter "bnc" if the option tag "gin" is included in the message.
0409	A "bnc" contact is not allowed to have a user portion in the URI.
040A	A "bnc" contact is not allowed to have a user parameter in the URI.
040B	The received request must contain the option tag "gin" in a "Require" header when registering a "bnc" contact.
040C	Registering a non- "bnc" contact is not allowed if the user already have "bnc" contacts registered.
040D	Registering a "bnc" contact is not allowed if the user already have non- "bnc" contacts registered.
040E	Gruu feature is disabled.
040F	Gruu is required but no sip instance is provided.
0410	Gruu is required but sip instance is not valid.
0411	SIP REGISTER request with contact expire time less than the configured parameter cscfRegistrationRefreshMin.
0412	Code is deprecated.
0413	Code is deprecated.
0414	Code is deprecated.
0700	CCA with an error result code was received on the originating side while CSCF is configured not to wait for the CCA.
0701	CCA with an error result code was received on the terminating side while CSCF is configured to wait for the CCA.
0702	CCA with an error result code was received on the originating side while CSCF is configured to wait for the CCA.
0703	CCA with an error result code was received on the terminating side while CSCF is configured not to wait for the CCA.
0704	No CCA received due to an internal communication error on the terminating side while CSCF is configured not to wait for the CCA.
0705	No CCA received due to an internal communication error on the terminating side while CSCF is configured to wait for the CCA.
0706	No CCA received due to an internal communication error on the originating side while CSCF is configured not to wait for the CCA.
0707	No CCA received due to an internal communication error on the originating side while CSCF is configured to wait for the CCA.
0800	Code is deprecated.
0801	No default PSAP address configured & no LRF configured (SIP based Ml interface).
0802	No default PSAP address configured (HTTP based Ml interface).
0803	No default PSAP address & no LRF configured (HTTP based Ml interface).
0804	No Via headers detected in emergency call when preparing SOAP request to LRF (HTTP based Ml interface).
0805	Emergency call not allowed as URN is not valid emergency service URN (SIP based Ml interface).
0806	No PSAP address received for emergency service test call due to LRF not configured.
0A00	ENUM lookup made on originating side failed due to a server or network error. CscfNumberPortabilityRejectOnFailedENUM is set to TRUE and Generic Number Portability is disabled.
0A01	ENUM lookup made on originating side failed due to a server or network error. CscfNumberPortabilityRejectOnFailedENUM is set to TRUE and Generic Number Portability is enabled.
0A02	ENUM lookup made on terminating side failed due to a server or network error. CscfNumberPortabilityRejectOnFailedENUM is set to TRUE and Generic Number Portability is enabled.
0A03	Invalid URI format is received as result from ENUM lookup.
0E00	LIA with an application error result code was received. Error result code is described in the optional-code field.
0E01	LIA contains an invalid Result AVP.
0E02	LIA contains both Server-Capabilities and Server-Name AVPs.
0E03	LIA contains an invalid Server-Name AVP.
0E04	Resource Broker encounters "InvalidServerName" scenario.
0E05	CSCF not configured with colocated S-CSCF.
0E06	Resource Broker failure due to no matching S-CSCF capabilities.
0E07	LIA contains no Wildcarded Public Identity AVP.
0E08	Communication error with Cx interface for LIR.
1200	Security Association set is not found for registration request.
1201	Security Association set is not found for originating initial request.
1202	Security Association set is not found for originating inside request.
1203	Security Association set cannot be created for registration.
1204	Authorization Header is not found for registration request.
1205	Private ID in authorization data does not match the previously used private ID.
1206	Dropped Register request to delete contact on unsecured port.
1207	Dropped Register request to delete last contact on unsecured port.
1208	Dropped Register query on unsecured port.
1209	Dropped original initial request on unsecured port.
120A	Dropped original inside request on unsecured port.
120B	Contact port in Register request does not match with port S in security client.
120C	Invalid IP address in contact header of Register request.
120D	Remote IP address in register request does not match with IP address from DNS lookup.
1300	Code is deprecated.
1400	The REGISTER Request-URI scheme type is not SIP.
1401	The REGISTER Request-URI user part is not empty.
1402	The REGISTER request To header URI scheme type is not SIP.
1403	The REGISTER request To and From header is not equal.
1404	The REGISTER request Contact header is invalid.
1405	The REGISTER request Contact header URI scheme type is not SIP.
1406	The REGISTER request Expires header is missing for the wildcard contact.
1407	The REGISTER request Expires header is not zero for the wildcard contact.
1408	More than one contact found and at least one wildcard contact in the REGISTER request.
1409	The CSeq number for the REGISTER request is out of order.
140A	SIP request with missing Vias.
1800	SIP REGISTER request temporarily rejected AS instance caching is pending.
1900	Code is deprecated.
1901	Code is deprecated.
1902	RegEvent Subscribe from an Emergency Contact is not allowed.
1903	Number of feature tags in both Reject and Accept Contact headers exceeds 20
1904	SiFC Data is invalid in User Service Profile or IRS associated with user does not exist.
1905	SiFC Data is invalid in User Service Profile.
1906	After having removed P-CSCF hanging contacts, valid contacts do not exist anymore.
1907	CSeq is not increased for inside request.
1908	Database failure is encountered, cannot store user data to database.
1909	SIP request timeout on a non-ISC interface, with SIP failure reason set to: uninitialized.
190A	SIP request timeout on an ISC interface, with SIP failure reason set to: uninitialized.
190B	SIP request timeout on a non-ISC interface, with SIP failure reason set to: extension.
190C	SIP request timeout on an ISC interface, with SIP failure reason set to: extension.
190D	SIP request timeout on a non-ISC interface, with SIP failure code set to: unknown.
190E	SIP request timeout on an ISC interface, with SIP failure code set to: unknown.
190F	SIP request timeout on a non-ISC interface, with SIP failure code set to: Invalid Request.
1910	SIP request timeout on an ISC interface, with SIP failure code set to: Invalid Request.
1911	SIP request timeout on a non-ISC interface, with SIP failure code set to: Invalid Response.
1912	SIP request timeout on an ISC interface, with SIP failure code set to: Invalid Response.
1913	SIP request timeout on a non-ISC interface, with SIP failure code set to: Transaction Timeout.
1914	SIP request timeout on an ISC interface, with SIP failure code set to: Transaction Timeout.
1915	SIP request timeout on a non-ISC interface, with SIP failure code set to: No DNS Result.
1916	SIP request timeout on an ISC interface, with SIP failure code set to: No DNS Result.
1917	SIP request timeout on a non-ISC interface, with SIP failure code set to: No SigComp Result.
1918	SIP request timeout on an ISC interface, with SIP failure code set to: No SigComp Result.
1919	SIP request timeout on a non-ISC interface, with SIP failure code set to: Common Components Database Error.
191A	SIP request timeout on an ISC interface, with SIP failure code set to: Common Components Database Error.
191B	SIP request timeout on a non-ISC interface, with SIP failure code set to: No Port Provisioned.
191C	SIP request timeout on an ISC interface, with SIP failure code set to: No Port Provisioned.
191D	SIP request timeout on a non-ISC interface, with SIP failure code set to: All Ports Locked.
191E	SIP request timeout on an ISC interface, with SIP failure code set to: All Ports Locked.
191F	SIP request timeout on a non-ISC interface, with SIP failure code set to: Message Too Large. Please see configuration parameters CscfMaxSipMessageSizeTcp and CscfMaxSipMessageSizeUdp.
1920	SIP request timeout on an ISC interface, with SIP failure code set to: Message Too Large. Please see configuration parameters CscfMaxSipMessageSizeTcp and CscfMaxSipMessageSizeUdp.
1921	SIP request timeout on a non-ISC interface, with SIP failure code set to: Not Supported.
1922	SIP request timeout on an ISC interface, with SIP failure code set to: Not Supported.
1923	SIP request timeout on a non-ISC interface, with SIP failure code set to: Destination Unreachable.
1924	SIP request timeout on an ISC interface, with SIP failure code set to: Destination Unreachable.
1925	SIP request timeout on a non-ISC interface, with SIP failure code set to: Processor Failure.
1926	SIP request timeout on an ISC interface, with SIP failure code set to: Processor Failure.
1927	SIP request timeout on a non-ISC interface, with SIP failure code set to: Request Terminated.
1928	SIP request timeout on an ISC interface, with SIP failure code set to: Request Terminated.
1929	SIP request timeout on a non-ISC interface, with SIP failure code set to: Service Unavailable.
192A	SIP request timeout on an ISC interface, with SIP failure code set to: Service Unavailable.
192B	SIP request timeout on a non-ISC interface, with DNS failure code unknown.
192C	SIP request timeout on an ISC interface, with DNS failure code unknown.
192D	SIP request timeout on a non-ISC interface, with DNS failure code set to: Illegal Lookup Input.
192E	SIP request timeout on an ISC interface, with DNS failure code set to: Illegal Lookup Input.
192F	SIP request timeout on a non-ISC interface, with DNS failure code set to: No Configured Servers.
1930	SIP request timeout on an ISC interface, with DNS failure code set to: No Configured Servers.
1931	SIP request timeout on a non-ISC interface, with DNS failure code set to: Server Error.
1932	SIP request timeout on an ISC interface, with DNS failure code set to: Server Error.
1933	SIP request timeout on a non-ISC interface, with DNS failure code set to: Socket Error.
1934	SIP request timeout on an ISC interface, with DNS failure code set to: Socket Error.
1935	SIP request timeout on a non-ISC interface, with DNS failure code set to: Timeout.
1936	SIP request timeout on an ISC interface, with DNS failure code set to: Timeout.
1937	SIP request timeout on a non-ISC interface, with DNS failure code set to: Timeout On Upgrade.
1938	SIP request timeout on an ISC interface, with DNS failure code set to: Timeout On Upgrade.
1939	SIP request timeout on a non-ISC interface, with DNS failure code set to: Internal Error.
193A	SIP request timeout on an ISC interface, with DNS failure code set to: Internal Error.
193B	SIP request timeout on a non-ISC interface, with SIP failure reason set to: SigComp Error.
193C	SIP request timeout on an ISC interface, with SIP failure reason set to: SigComp Error.
193D	SIP request timeout on a non-ISC interface, with SIP failure reason set to: Dicos Socket Error.
193E	SIP request timeout on an ISC interface, with SIP failure reason set to: Dicos Socket Error.
193F	Incorrect breakout due to User Redistribution functionality. The local I-CSCF tries to breakout to an external S-CSCF, yet the local CSCF already contains the S-CSCF specific user data. The entire user data will be removed, and user must reregister. To prevent node from breaking-out, User Redistribution functionality must be disabled.
1940	Incorrect breakout due to Local Zone Policy functionality. The local I-CSCF tries to breakout to an external S-CSCF, yet the local CSCF already contains the S-CSCF specific user data. The entire user data will be removed, and user must reregister. To prevent node from breaking-out, Local Zone Policy functionality must be disabled.
1941	Incorrect breakout scenario, where the local I-CSCF tries to breakout to an external S-CSCF, yet the local CSCF already contains the S-CSCF specific user data. The entire user data will be removed, and user must reregister.
1942	User is not authorized for registration event subscription.
1943	Calling user is not registered in database.
1944	Calling user is not registered in originating traffic scenario.
1945	User is barred in originating traffic scenario.
1946	Maximum number of sessions has been reached.
1947	Application Server is not authorized.
1948	User Agent is not configured in white list.
1949	SIP request is rejected due to missing emergency priority header.
1950	User is registered and has no contacts.
1951	Additional SIP request received while already processing a SIP request.
1952	Additional SIP request received while already processing a UAC SIP request.
1953	Additional SIP request received while already processing a SIP request with same number of vias.
1954	Additional SIP request received while already processing a SIP UAC request with same number of vias.
1955	Code is deprecated.
1956	Code is deprecated.
1957	Code is deprecated.
1958	Code is deprecated.
1959	Code is deprecated.
195A	SIP request received on an interface which is not configured.
195B	The operation failed due to inconsistent user state in the database.
195C	Routing loop detected.
195D	REGISTER request received with a CSeq value that is NOT greater than that of the existing binding in the CSCF.
195E	SIP REGISTER request received on terminating interface.
195F	Database failure encountered, could not store registration event data.
1960	Public Gruu in Request Uri is invalid.
1961	Invalid IMPU in Request URI
1962	IMPU in Request URI not found in IRS.
1963	Registration event notification destined for P-CSCF could not be parsed.
1964	The SIP request does not contain a valid public ID.
1965	The called party does not have a registered contact which matches the caller preferences.
1966	The called user is not registered.
1967	User is barred in terminating traffic scenario.
1968	SIP dialogue does not exist.
1969	Failed to create, update, or delete user for standalone P-CSCF.
196A	Method not supported.
196B	Method not supported.
196C	SIP request with missing Via header.
196D	Code is deprecated.
196E	Database transaction failure.
196F	Database transaction failure.
1970	Registration event is disabled or invalid event ID.
1971	Cannot subscribe to registration events for a user who is not registered.
1972	E-CSCF node not enabled.
1973	Inconsistent registration status for standalone P-CSCF.
1974	System is overloaded.
1975	System is overloaded.
1976	SIP REGISTER request temporarily rejected. AS instance caching is pending.
1977	Database error occurred when reading from DB for incoming SIP request
1978	The REGISTER request Expires header is missing for the wildcard contact.
1979	The REGISTER request Expires header is not zero for the wildcard contact.
1980	More than one contact found and at least one wildcard contact in the REGISTER request.
1981	Request URI in REGISTER message is not SIP URI
1982	User portion of the Request URI in REGISTER message is not empty
1983	To header in REGISTER message do not contain a SIP URI
1984	From and To header in REGISTER message are not equal
1985	Not possible to parse Contact header in REGISTER message
1986	Contact header in REGISTER message do not contain a SIP URI
1987	The received REISTER message is out of order
1988	SIP MESSAGE based P-CSCF restoration cannot be performed because user is not registered.
1989	Request is rejected based on the current overload control (oc) value for upstream node not supporting RFC 7339 when SIP Overload Control Reporting feature is enabled.
1990	RegEvent is reject due to missing contact header
1991	RegEvent is rejected due to max number of allowed subscriptions of 60 has been exceeded
1992	Request is rejected due to the SIP-URI or Route header contain invalid character(s)
1993	Request is rejected by SIP Overload Control reacting role on a non-ISC interface according to RFC 7339, with SIP failure reason set to: Destination Overloaded.
1994	Request is rejected by SIP Overload Control reacting role on an ISC interface according to RFC 7339, with SIP failure reason set to: Destination Overloaded.
1995	SIP request timeout on a non-ISC interface, with SIP failure reason set to: Dialogue Failure.
1996	SIP request timeout on an ISC interface, with SIP failure reason set to: Dialogue Failure.
1A00	CSCF generated a SIP negative response due to cancellation of the request message.
1A01	CSCF generated a SIP negative response due to cancellation of the request message.
1A02	Failed to read database due to an internal error.
1A03	Failed to read database due to an internal error.
1A04	CSCF terminated the SIP transaction due to an unknown reason.
1A05	Failed to write database due to an internal error after creating a successful SIP response.
1A06	Failed to write database due to an internal error before proxying SIP request.
1A07	Failed to write database due to an internal error after creating a successful SIP response.
1A08	Failed to write database due to an internal error when processing SIP request.
1D00	Redirect is not allowed, any 3xx response is changed to 500 Server Internal Error
1D01	Max redirects is reached for Register strategy, the 305 response is changed to 500 Server Internal Error
1D02	No new target to redirect to is available in the response for the Register strategy, the 305 response is changed to 500 Server Internal Error
1D03	Max redirects is reached for NonRegister305 strategy, the 305 response is changed to 500 Server Internal Error
1D04	No new target to redirect to is available in the response for the NonRegister305 strategy, the 305 response is changed to 500 Server Internal Error
1D05	Max redirects is reached for NonRegister3xx strategy, the 3xx response is changed to 500 Server Internal Error
1D06	No new target to redirect to is available in the response for the NonRegister3xx strategy, the 3xx response is changed to 500 Server Internal Error
1D07	After removing the tried targets from 3xx response in the NonRegister305 strategy, no targets are available anymore, the 3xx response is changed to 500 Server Internal Error
1D08	After removing the tried targets from 3xx response in the Register strategy, no targets are available anymore, the 3xx response is changed to 500 Server Internal Error
1D09	After removing the tried targets from 3xx response in the NonRegister3xx strategy, no targets are available anymore, the 3xx response is changed to 500 Server Internal Error
1D0A	Emergency call not allowed as URN is not valid emergency service URN (SIP based Ml interface)
1D0B	No default PSAP address configured (SIP based Ml interface)
1D0C	Error response from default PSAP
1D0D	No PSAP address received from LRF for emergency service test call
1D0E	All attempts to PSAP addresses failed for emergency service test call
1E00	CSCF node is administratively non-operational or locked.
1E01	E-CSCF node is administratively non-operational or locked.
1E02	BCF node is administratively non-operational or locked.
1E03	P-CSCF node is in Shutting Down state, graceful shutdown procedure is in effect.
1E04	I-CSCF node is in Shutting Down state, graceful shutdown procedure is in effect.
1E05	S-CSCF node is in Shutting Down state, graceful shutdown procedure is in effect.
1E06	E-CSCF node is in Shutting Down state, graceful shutdown procedure is in effect.
1E07	BCF node is in Shutting Down state, graceful shutdown procedure is in effect.
1E08	S-CSCF node is administratively non-operational or locked. REGISTER, Re-REGISTER and REGISTER of new contacts will be rejected.
1E09	S-CSCF node is in Shutting Down state and the registration should be redirected to the S-CSCF indicated in the Contact header, graceful shutdown procedure is in effect.
1F00	Error storing wild-Carded Public Identity(ies) to the CSCF Database.
1F01	Longest/Best match not found of Public Identity against stored wild-Carded Public Identity(ies).
2400	Stateless SIP request is received in ISC interface.
2401	Invalid syntax is encountered when evaluating Regular Expression in IFC data when executing services.
2402	Invalid syntax is encountered when evaluating Regular Expression in IFC data when continue evaluating service data.
2403	SIP request is received while in Revoked state.
2404	SIP request is received while in Failed state.
2405	SIP request is received too late while in WaitForASAnswer state.
2406	Redirect is done and SIP 305 response is replaced with SIP 500 response.
2407	Redirect is done and SIP 3xx response is replaced with SIP 500 response.
2408	No IPv4 exit address configured, request cannot be routed.
2409	No IPv6 exit address configured, request cannot be routed.
240A	Invalid application server's URI is encountered, request cannot be routed.
240B	AsLess is encountered with session_terminate when executing services for the first time.
240C	AsLess is encountered with session_terminate when continue evaluating service data.
240D	SIP REGISTER request received on ISC interface.
240E	Received an unexpected additional request within an existing SIP transaction involving proxy AS.
240F	Received an unexpected additional request within an existing SIP transaction involving proxy AS.
2410	Received an unexpected additional request from the AS after receiving a negative response.
2411	Received a SIP response from the AS which contained an unparseable Record-Route.
2412	SIP Non-REGISTER request temporarily rejected. AS instance caching is pending.
2413	Received an unexpected additional request within an existing SIP transaction involving AS.
2500	Expiration interval too short.
2501	Polling Resource State is not implemented.
2502	Dialog event function is disabled.
2503	The subscribing node is not authorized.
2504	Event type is not supported.
2505	Invalid subscription.
2506	CSeq is not incremented.
2507	Event header ID parameter is invalid.
2508	Dialog Finite State Machine does not exist.
2509	Event header to-tag parameter is missing.
2510	Event header call-id parameter is missing.
2511	Contact header is missing.
2A00	SIP request timeout on a non-ISC interface, with SIP failure reason set to: uninitialized.
2A01	SIP request timeout on an ISC interface, with SIP failure reason set to: uninitialized.
2A02	SIP request timeout on a non-ISC interface, with SIP failure reason set to: extension.
2A03	SIP request timeout on an ISC interface, with SIP failure reason set to: extension.
2A04	SIP request timeout on a non-ISC interface, with SIP failure code set to: unknown.
2A05	SIP request timeout on an ISC interface, with SIP failure code set to: unknown.
2A06	SIP request timeout on a non-ISC interface, with SIP failure code set to: Invalid Request.
2A07	SIP request timeout on an ISC interface, with SIP failure code set to: Invalid Request.
2A08	SIP request timeout on a non-ISC interface, with SIP failure code set to: Invalid Response.
2A09	SIP request timeout on an ISC interface, with SIP failure code set to: Invalid Response.
2A0A	SIP request timeout on a non-ISC interface, with SIP failure code set to: Transaction Timeout.
2A0B	SIP request timeout on an ISC interface, with SIP failure code set to: Transaction Timeout.
2A0C	SIP request timeout on a non-ISC interface, with SIP failure code set to: No DNS Result.
2A0D	SIP request timeout on an ISC interface, with SIP failure code set to: No DNS Result.
2A0E	SIP request timeout on a non-ISC interface, with SIP failure code set to: No SigComp Result.
2A0F	SIP request timeout on an ISC interface, with SIP failure code set to: No SigComp Result.
2A10	SIP request timeout on a non-ISC interface, with SIP failure code set to: Common Components Database Error.
2A11	SIP request timeout on an ISC interface, with SIP failure code set to: Common Components Database Error.
2A12	SIP request timeout on a non-ISC interface, with SIP failure code set to: No Port Provisioned.
2A13	SIP request timeout on an ISC interface, with SIP failure code set to: No Port Provisioned.
2A14	SIP request timeout on a non-ISC interface, with SIP failure code set to: All Ports Locked.
2A15	SIP request timeout on an ISC interface, with SIP failure code set to: All Ports Locked.
2A16	SIP request timeout on a non-ISC interface, with SIP failure code set to: Message Too Large. Please see configuration parameters CscfMaxSipMessageSizeTcp and CscfMaxSipMessageSizeUdp.
2A17	SIP request timeout on an ISC interface, with SIP failure code set to: Message Too Large. Please see configuration parameters CscfMaxSipMessageSizeTcp and CscfMaxSipMessageSizeUdp.
2A18	SIP request timeout on a non-ISC interface, with SIP failure code set to: Not Supported.
2A19	SIP request timeout on an ISC interface, with SIP failure code set to: Not Supported.
2A1A	SIP request timeout on a non-ISC interface, with SIP failure code set to: Destination Unreachable.
2A1B	SIP request timeout on an ISC interface, with SIP failure code set to: Destination Unreachable.
2A1C	SIP request timeout on a non-ISC interface, with SIP failure code set to: Processor Failure.
2A1D	SIP request timeout on an ISC interface, with SIP failure code set to: Processor Failure.
2A1E	SIP request timeout on a non-ISC interface, with SIP failure code set to: Request Terminated.
2A1F	SIP request timeout on an ISC interface, with SIP failure code set to: Request Terminated.
2A20	SIP request timeout on a non-ISC interface, with SIP failure code set to: Service Unavailable.
2A21	SIP request timeout on an ISC interface, with SIP failure code set to: Service Unavailable.
2A22	SIP request timeout on a non-ISC interface, with DNS failure code unknown.
2A23	SIP request timeout on an ISC interface, with DNS failure code unknown.
2A24	SIP request timeout on a non-ISC interface, with DNS failure code set to: Illegal Lookup Input.
2A25	SIP request timeout on an ISC interface, with DNS failure code set to: Illegal Lookup Input.
2A26	SIP request timeout on a non-ISC interface, with DNS failure code set to: No Configured Servers.
2A27	SIP request timeout on an ISC interface, with DNS failure code set to: No Configured Servers.
2A28	SIP request timeout on a non-ISC interface, with DNS failure code set to: Server Error.
2A29	SIP request timeout on an ISC interface, with DNS failure code set to: Server Error.
2A2A	SIP request timeout on a non-ISC interface, with DNS failure code set to: Socket Error.
2A2B	SIP request timeout on an ISC interface, with DNS failure code set to: Socket Error.
2A2C	SIP request timeout on a non-ISC interface, with DNS failure code set to: Timeout.
2A2D	SIP request timeout on an ISC interface, with DNS failure code set to: Timeout.
2A2E	SIP request timeout on a non-ISC interface, with DNS failure code set to: Timeout On Upgrade.
2A2F	SIP request timeout on an ISC interface, with DNS failure code set to: Timeout On Upgrade.
2A30	SIP request timeout on a non-ISC interface, with DNS failure code set to: Internal Error.
2A31	SIP request timeout on an ISC interface, with DNS failure code set to: Internal Error.
2A32	SIP request timeout on a non-ISC interface, with SIP failure reason set to: SigComp Error.
2A33	SIP request timeout on an ISC interface, with SIP failure reason set to: SigComp Error.
2A34	SIP request timeout on a non-ISC interface, with SIP failure reason set to: Dicos Socket Error.
2A35	SIP request timeout on an ISC interface, with SIP failure reason set to: Dicos Socket Error.
2A36	Request is rejected by SIP Overload Control reacting role on a non-ISC interface according to RFC 7339, with SIP failure reason set to: Destination Overloaded.
2A37	Request is rejected by SIP Overload Control reacting role on an ISC interface according to RFC 7339, with SIP failure reason set to: Destination Overloaded.
2A38	SIP request timeout on a non-ISC interface, with SIP failure reason set to: Dialogue Failure.
2A39	SIP request timeout on an ISC interface, with SIP failure reason set to: Dialogue Failure.
2D00	Code is deprecated.
2D01	Code is deprecated.
2D02	Code is deprecated.
2D03	Code is deprecated.
2D04	Code is deprecated.
2D05	Code is deprecated.
2D06	Code is deprecated.
2D07	Code is deprecated.
2D08	Code is deprecated.
2D09	Code is deprecated.
2F00	Failed to parse Max-Forwards header.
2F01	Max-Forwards header is zero.
3300	System is overloaded.
3301	Request is rejected based on the current overload control (oc) value for upstream node not supporting RFC 7339 when SIP Overload Control Reporting feature is enabled.
3400	Received EATF unsupported request (for example, REGISTER, REFER, SUBSCRIBE, etc).
3401	Received an INVITE with reason code 487 during a call establishment.
3402	Dynamic Payload Type check failed during call access transfer
3403	No SDP received during call access transfer.
3404	Call Id does not exist for a received BYE request.
3405	Received an INVITE with an unrecognized Call Id from CS UE.
3406	Service URN not included in received INVITE request.
3407	Received an INVITE from CS UE when there was no prior call establishment.
3408	Call Id does not exist for a received PRACK request.
3409	Call Id does not exist for a received UPDATE request.
340A	Request received while EATF is not in service.
340B	Call transfer aborted due to fallback on PS call leg.
340C	Received incorrect INVITE refresh/fallback request on PS call leg.
340D	Received incorrect UPDATE refresh/fallback request on PS call leg.
340E	Received an INVITE with no session identifier.
340F	EATF received an initial INVITE request with a top Route header that does not match the configured value in parameter eatfDomainNameEntry.
3410	EATF redirects an access transfer request when there was no prior call establishment and eatfRedundantEatfEntry is configured.
3600	No SAA was received after sending SAR due to Timeout reason.
3601	SAA with a protocol error result code was received. Error result code is described in the optional-code field.
3602	SAA with an application error result code was received. Error result code is described in the optional-code field.
3603	Error in SAA. Either none or both of base result AVP and Experimental result AVP are present at deregistration.
3604	No SAA was received due to an internal communication error after sending SAR.
3605	SAA was successfully handled and the P-CSCF Restoration Procedure was initiated from S-CSCF. P-CSCF is blacklisted.
3606	No SAA was received after sending SAR due to Unknown reason.
3607	No SAA was received after sending SAR due to Protocol Error reason.
3608	P-CSCF Restoration Procedure is ongoing.
3609	SAA was successfully handled and the P-CSCF Restoration Procedure was initiated from S-CSCF. P-CSCF returned SIP error code stored in optional code field.
360A	No SAA was received after sending SAR due to Diameter i/f connection failure.
360B	Message throttled due to HSS congestion. SAR not sent.
360C	Database transaction failure when trying to set P-CSCF Restoration In Progress.
360D	SIP MESSAGE based P-CSCF Restoration cannot be performed because feature is disabled.
360E	SIP MESSAGE based P-CSCF Restoration cannot be performed because user is associated with multiple IMPIs.
360F	SIP MESSAGE based P-CSCF Restoration cannot be performed because user is registered with emergency contact.
3610	SIP MESSAGE based P-CSCF Restoration cannot be performed because P-CSCF Restoration is already in progress.
3B00	Failed to write to database due to an internal error after receiving an anonymous INVITE request.
3C00	Failed to parse Session-Expires header in SIP request.
3C01	Session-Expires in INVITE request is smaller than the value configured in CscfSessionRefreshMin.
3C02	Expires in SUBSCRIBE request is smaller than the value configured in cscfRegistrationEventRefreshMin.
3C03	Failed to read dialog data due to an internal database error.
3C04	Failed to update dialog data due to an internal database error.
3C05	Maximum number of sessions has been reached.
3D00	Impu and Gr parameter in public GRUU are not found.
3D01	Public GRUU is not bound to any contact and no loose routing indicator.
3D02	Public GRUU parse error.
3D03	Public Gruu in Request Uri is not assigned by S-CSCF and loose routing not found in user profile.
3D04	Public Gruu in Request Uri is not in current dialog.
3F00	SIP MESSAGE based call status query cannot be performed because of missing or invalid XML-body.
3F01	SIP MESSAGE based call status query cannot be performed because queried user is not registered.
3F02	SIP MESSAGE based call status query cannot be performed because queried user is a wrong number format.
3F03	Sender of call status query is not authorized to perform the query.
4000	P-Access-Network-Info header with Access Type IEEE-802.11* (WiFi calling) is not enabled.

2.7 Optional Code

The optional code contains the received Diameter error code when applicable. The information is extracted from the value of the Result-Code AVP or the Experimental-Result-Code AVP.