DataFailCause

Access attempt is already in progress.

Access blocked by the base station.

Access blocked by the base station for all mobile devices.

Access class blocking restrictions for the current camped cell.

Access control list check failure at the lower layer.

UE requested to modify QoS parameters or the bearer control mode, which is not compatible with the selected bearer control mode.

Activation rejected by Gateway GPRS Support Node (GGSN), Serving Gateway or PDN Gateway.

Activation rejected, unspecified.

Max number of Packet Data Protocol (PDP) context reached.

If connection failed for all matching URSP rules.

APN has been disabled.

PDN connection to the APN is disallowed on the roaming network.

New PDN bring up is rejected during interface selection because the UE has already allotted the available interfaces for other PDNs.

APN-related parameters are changed.

Interface bring up is attempted for an APN that is yet to be handed over to target RAT.

APN type conflict.

Authentication failure on emergency call.

Procedure requested by the UE was rejected because the bearer handling is not supported.

Roaming is disallowed during call bring up.

Emergency call bring up on a different ePDG.

Unable to encode the OTA message for MT PDP or deactivate PDP.

Received an alert stop from the base station due to incoming only.

Receiving an incoming call from the base station.

Received an intercept order from the base station.

Device in CDMA locked state.

Receiving a release from the base station with a SO (Service Option) Reject reason.

Receiving a reorder from the base station.

Receiving a retry order from the base station.

Channel acquisition failures.

Tearing down is in progress.

Network has already initiated the activation, modification, or deactivation of bearer resources that was requested by the UE.

Companion interface in use.

The concurrent services requested were not compatible.

In favor of a voice call or SMS when concurrent voice and data are not supported.

Concurrent service is not supported by base station.

Conditional Information Element (IE) error.

Network cannot serve a request from the MS due to congestion.

Indicate the connection was released.

CS domain is not available.

CS fallback call establishment is not allowed.

Network initiates a detach on LTE with error cause ""data plan has been replenished or has expired.

PDN Connection to a given APN is disallowed because data roaming is disabled from the device user interface settings and the UE is roaming.

PDN Connection to a given APN is disallowed because data is disabled from the device user interface settings.

DBM or SMS is in progress.

DDS (Default data subscription) switch occurs.

Default data subscription switch is in progress.

Data radio bearer is released by the RRC.

Dedicated bearer will be deactivated regardless of the network response.

Dual switch from single standby to dual standby is in progress.

Dial up networking (DUN) call bring up is rejected since UE is in eHRPD RAT.

Active dedicated bearer was requested using the same default bearer ID.

Device falls back from eHRPD to HRPD.

Data call has been brought down because EMBMS is not enabled at the RRC layer.

EMBMS data call has been successfully brought down.

Emergency interface only.

Device is operating in Emergency mode.

EPS (Evolved Packet System) Mobility Management (EMM) access barred.

EPS (Evolved Packet System) Mobility Management (EMM) access barred infinity retry.

Attach procedure is rejected by the network.

Attach procedure is started for EMC purposes.

UE is detached.

T3417 timer expiration of the service request procedure.

Extended service request fails due to expiration of the T3417 EXT timer.

EPS and non-EPS services are not allowed by the network.

EPS services are not allowed in the PLMN.

Data call fail due to unspecific errors.

Bad OTA message is received from the network.

Bearer must be deactivated to synchronize with the network.

Collision scenarios for the UE and network-initiated procedures.

PDN was disconnected by the downlaod server due to IRAT.

Download server rejected the call.

ESM level failure.

EPS Session Management (ESM) information is not received.

No specific local cause is mentioned, usually a valid OTA cause.

Active dedicated bearer was requested for an existing default bearer.

ESM procedure maximum attempt timeout failure.

Invalid EPS bearer identity in the request.

Received a connection deny due to billing or authentication failure on EVDO network.

Received a connection deny due to general or network busy on EVDO network.

HDR system has been changed due to redirection or the PRL was not preferred.

Connection setup on the HDR system was time out.

Device exited HDR due to redirection or the PRL was not preferred.

Device does not have an HDR session.

It is ending an HDR call origination in favor of a GPS fix.

Device lost the system due to fade.

Device failed to acquire a co-located HDR for origination.

Feature not supported.

Semantic errors in packet filter.

Syntactical errors in packet filter(s).

PDN being brought up with an APN that is part of forbidden APN Name list.

Data fail due to GPRS registration failure.

Not allowed to operate either GPRS or non-GPRS services.

MS is not allowed to operate GPRS services.

UE requests GPRS service or the network initiates a detach request in a PLMN that does not offer roaming for GPRS services.

System preference change back to SRAT during handoff

HDR system access failure.

HDR module released the call due to fade.

HDR module could not be obtained because of the RF locked.

Interface mismatch.

ME could not be authenticated and the ME used is not acceptable to the network.

Network refuses service to the MS because either an identity of the MS is not acceptable to the network or the MS does not pass the authentication check.

IMEI of the UE is not accepted by the network.

Mobile reachable timer has expired, or the GMM context data related to the subscription does not exist in the SGSN.

IMSI present in the UE is unknown in the home subscriber server.

The other clients rejected incoming call.

Insufficient resources.

The current interface is being in use.

Internal data call preempt by high priority APN.

Rejected/Brought down since UE is transition between EPC and NONEPC RAT.

No PDP exists with the given connection ID while modifying or deactivating or activation for an already active PDP.

Not receiving a DNS address that was mandatory.

Invalid EMM state.

Invalid mandatory information.

Device operational mode is different from the mode requested in the traffic channel bring up.

Invalid Proxy-Call Session Control Function (P-CSCF) address.

Not receiving either a PCSCF or a DNS address, one of them being mandatory.

Primary context for NSAPI does not exist.

SIM was marked by the network as invalid for the circuit and/or packet service domain.

Invalid transaction id.

IPv6 address transfer failed.

Device failure to obtain the prefix from the network.

IP address mismatch.

New call bring up is rejected since the existing data call IP type doesn't match the requested IP.

Data call was unsuccessfully transferred during the IRAT handover.

Maximum access probes for the IS-707B call.

The user is barred from using the non-3GPP access or the subscribed APN.

The requested service was rejected because of congestion in the network while accessing the IWLAN ePDG.

Unable to resolve FQDN for the ePDG to an IP address

No response received from the DNS Server due to a timeout

Sent in the response to an IKE_AUTH message when, for some reason, the authentication failed.

IKE Certification validation failure

IKE configuration error resulting in failure

IKE message timeout, tunnel setup failed due to no response from EPDG

The Mobile Equipment used is not acceptable to the network

The network does not accept emergency PDN bringup request using an IMEI

The PDN connection has been rejected.

The network has determined that the requested procedure cannot be completed successfully due to network failure.

No non-3GPP subscription is associated with the IMSI.

The requested APN is not included in the user's profile, and therefore is not authorized for that user.

The PDN connection corresponding to the requested APN has been rejected.

The ePDG performs PLMN filtering (based on roaming agreements) and rejects the request from the UE.

The access type is restricted to the user.

The PDN connection has been rejected due to sematic errors in the packet filter.

The PDN connection has been rejected due to a semantic error in TFT operation.

The PDN connection has been rejected due to syntactic errors in the packet filter.

The PDN connection has been rejected due to a syntactic error in TFT operation.

Expected to update or bring down an ePDG tunnel, but no tunnel found

The ePDG does not support un-authenticated IMSI based emergency PDN bringup *

The user identified by the IMSI is unknown.

IPv6 interface bring up fails because the network provided only the IPv4 address for the upcoming PDN permanent client can reattempt a IPv6 call bring up after the IPv4 interface is also brought down.

IPv4 interface bring up fails because the network provided only the IPv6 address for the upcoming PDN permanent client can reattempt a IPv4 call bring up after the IPv6 interface is also brought down.

Logical Link Control (LLC) Sub Network Dependent Convergence Protocol (SNDCP).

Client ended the data call.

MS requests service, or the network initiates a detach request, in a location area where the HPLMN determines that the MS, by subscription, is not allowed to operate.

Data connection was lost.

Lower layer registration failure.

Device is going into lower power mode or powering down.

Service request procedure failure.

Throttling is not needed for this service request failure.

MAC level failure.

No matching rule available for the request, and match-all rule is not allowed for it.

Maximum NSAPIs have been exceeded during PDP activation.

Maximum size of the L2 message was exceeded.

Maximum access probes transmitted.

IPv4 data call bring up is rejected because the UE already maintains the allotted maximum number of IPv4 data connections.

IPv6 data call bring up is rejected because the UE already maintains the allotted maximum number of IPv6 data connections.

Maximum PPP inactivity timer expired.

Incorrect message semantic.

Unsupported message type.

UE is in MIP-only configuration but the MIP configuration fails on call bring up due to incorrect provisioning.

Foreign agent administratively prohibited MIP (Mobile IP) registration.

Foreign agent rejected MIP (Mobile IP) registration because of delivery style was not supported.

Foreign agent rejected MIP (Mobile IP) registration because of requested encapsulation was unavailable.

Foreign agent rejected MIP (Mobile IP) registration because of home agent authentication failure.

Foreign agent rejected MIP (Mobile IP) registration because of insufficient resources.

Foreign agent rejected MIP (Mobile IP) registration because of malformed reply.

Foreign agent rejected MIP (Mobile IP) registration because of malformed request.

Foreign agent rejected MIP (Mobile IP) registration because of missing challenge.

Foreign agent rejected MIP (Mobile IP) registration because of missing Home Address.

Foreign agent rejected MIP (Mobile IP) registration because of missing Home Agent.

Foreign agent rejected MIP (Mobile IP) registration because of missing NAI (Network Access Identifier).

Foreign agent rejected MIP (Mobile IP) registration because of MN-AAA authenticator was wrong.

Reason unspecified for foreign agent rejected MIP (Mobile IP) registration.

Foreign agent rejected MIP (Mobile IP) registration because of requested lifetime was too long.

Foreign agent rejected MIP (Mobile IP) registration because of reverse tunnel was mandatory but not requested by device.

Foreign agent rejected MIP (Mobile IP) registration because of reverse tunnel was unavailable.

Foreign agent rejected MIP (Mobile IP) registration because of stale challenge.

Foreign agent rejected MIP (Mobile IP) registration because of unknown challenge.

Foreign agent rejected MIP (Mobile IP) registration of VJ Header Compression was unavailable.

Home agent administratively prohibited MIP (Mobile IP) registration.

Home agent rejected MIP (Mobile IP) registration because of encapsulation unavailable.

Home agent rejected MIP (Mobile IP) registration because of foreign agent authentication failure.

Home agent rejected MIP (Mobile IP) registration because of insufficient resources.

Home agent rejected MIP (Mobile IP) registration because of malformed request.

Home agent rejected MIP (Mobile IP) registration because of MN-HA authenticator was wrong.

Reason unspecified for home agent rejected MIP (Mobile IP) registration.

Home agent rejected MIP (Mobile IP) registration because of registration id mismatch.

Home agent rejected MIP (Mobile IP) registration because of reverse tunnel is mandatory but not requested by device.

Home agent rejected MIP (Mobile IP) registration because of reverse tunnel was unavailable.

Home agent rejected MIP (Mobile IP) registration because of unknown home agent address.

Missing or unknown APN.

Another application in modem preempts the data call.

Modem restart.

Mobile switching center is temporarily unreachable.

Message and protocol state uncompatible.

Message type uncompatible.

No matching identity or context could be found in the network.

Multiple PDP call feature is disabled.

Multiple connections to a same PDN is not allowed.

Non-Access Spectrum layer failure.

Non-access stratum (NAS) request was rejected by the network.

NAS signalling.

Network Failure.

Network-initiated detach without reattach.

Network-initiated detach with reattach.

Brought down by the network.

There is no failure

UE is unable to bring up a non-IP data call because the device is not camped on a NB1 cell.

Receiving a release from the base station with no reason.

Device does not have CDMA service.

There is no co-located HDR.

No EPS bearer context was activated.

GPRS context is not available.

Device has no hybrid HDR service.

MS requests an establishment of the radio access bearers for all active PDP contexts by sending a service request message indicating data to the network, but the SGSN does not have any active PDP context.

There was no response received from the base station.

Device has no service.

No service on the gateway.

The Network Service Access Point Identifier (NSAPI) is in use.

PDN is attempted to be brought up with NULL APN but NULL APN is not supported.

Network supports IPv4v6 PDP type only.

Packet Data Protocol (PDP) type IPv4 only allowed.

Packet Data Protocol (PDP) type IPv6 only allowed.

Network supports non-IP PDP type only.

Single address bearers only allowed.

Operator determined barring.

OTASP commit is in progress.

PDN connection does not exist.

PDN inactivity timer expired due to no data transmission in a configurable duration of time.

IPV4 PDN is in throttled state due to network providing only IPV6 address during the previous VSNCP bringup (subs_limited_to_v6).

IPV4 PDN is in throttled state due to previous VSNCP bringup failure(s).

IPV6 PDN is in throttled state due to network providing only IPV4 address during the previous VSNCP bringup (subs_limited_to_v4).

IPV6 PDN is in throttled state due to previous VSNCP bringup failure(s).

Non-IP PDN is in disallowed state due to the network providing only an IP address.

Non-IP PDN is in throttled state due to previous VSNCP bringup failure(s).

SM attempts PDP activation for a maximum of four attempts.

PDP context already exists.

Expiration of the PDP establish timer with a maximum of five retries.

Expiration of the PDP deactivate timer with a maximum of four retries.

PDP activation failed due to RRC_ABORT or a forbidden PLMN.

MO PDP modify collision when the MT PDP is already in progress.

Expiration of the PDP modify timer with a maximum of four retries.

PDP PPP calls are not supported.

Packet Data Protocol (PDP) without active traffic flow template (TFT).

Device is in use (e.g., voice call).

Physical link is in the process of cleanup.

UE requests GPRS service, or the network initiates a detach request in a PLMN which does not offer roaming for GPRS services to that MS.

Data call bring up fails in the PPP setup due to an authorization failure.

Data call bring up fails in the PPP setup due to a CHAP failure.

Data call bring up fails in the PPP setup because the PPP is in the process of cleaning the previous PPP session.

Data call bring up fails in the PPP setup due to an option mismatch.

Data call bring up fails in the PPP setup due to a PAP failure.

Data call bring up fails in the PPP setup due to a timeout.

Preferred technology has changed, must retry with parameters appropriate for new technology.

APN bearer type in the profile does not match preferred network mode.

Protocol errors.

Quality of service (QoS) is not accepted.

Radio access bearer failure.

Radio access bearer is not established by the lower layers during activation, modification, or deactivation.

Data fail due to radio not unavailable.

data call was disconnected because radio was resetting, powered off.

Device is in the process of redirecting or handing off to a different target system.

Data fail due to registration failure.

Regular deactivation.

The base station rejecting the call.

Radio resource control (RRC) connection was aborted by the non-access stratum (NAS) after an IRAT to LTE IRAT handover.

Radio resource control (RRC) connection was aborted before deactivating the LTE stack after a successful LTE to GSM/EDGE IRAT cell change order procedure.

Radio resource control (RRC) connection was aborted before deactivating the LTE stack due to a successful LTE to WCDMA/GSM/TD-SCDMA IRAT change.

Radio resource control (RRC) connection was aborted in the middle of a LTE to GSM IRAT cell change order procedure.

Connection has been released by the radio resource control (RRC) due to an abort request.

Radio resource control (RRC) connection establishment failed due to access barrred.

Radio resource control (RRC) connection failure at access stratum.

Radio resource control (RRC) connection establishment is aborted due to another procedure.

Connection establishment failed as the radio resource control (RRC) is not camped on any cell.

Radio resource control (RRC) connection establishment failed due to cell reselection at access stratum.

Connection establishment failed due to configuration failure at the radio resource control (RRC).

Radio resource control (RRC) connection establishment failure due to an error in the request message.

Connection establishment failed due to a link failure at the radio resource control (RRC).

Normal radio resource control (RRC) connection release.

UE is out of service during the call register.

Radio resource control (RRC) connection release failed due to radio link failure conditions.

Radio resource control (RRC) connection re-establishment failure.

Radio resource control (RRC) connection establishment failed due to the network rejecting the UE connection request.

If the UE has an LTE radio link failure before security is established, the radio resource control (RRC) connection must be released and the UE must return to idle.

Radio resource control (RRC) connection establishment failure due to the RF was unavailable.

Radio resource control (RRC) connection released due to a system information block read error.

Connection establishment failed due to a service interval failure at the radio resource control (RRC).

Radio resource control (RRC) connection could not be established in the time limit.

Radio resource control (RRC) connection establishment failure due to a change in the tracking area ID.

Radio resource control (RRC) uplink data delivery failed due to a connection release.

Transmission failure of radio resource control (RRC) uplink data.

Radio resource control (RRC) uplink data delivery failed due to a handover.

Radio resource control (RRC) is not connected but the non-access stratum (NAS) sends an uplink data request.

Radio resource control (RRC) uplink data delivery failed due to a radio link failure.

RUIM not being present.

Unspecified security mode reject.

Service is not allowed on the requested PLMN.

Requested service option not subscribed.

Service option not supported.

Service option temporarily out of order.

Data call drop due to network/modem disconnect.

Card was refreshed or removed.

Data call fail due to the slice not being allowed for the data call.

Synchronization failure.

Test loop-back data call has been successfully brought down.

Data call was disconnected by modem because tethered.

Semantic error in the Traffic flow templates (TFT) operation.

Syntactical error in the Traffic flow templates (TFT) operation.

Put device in thermal emergency.

Thermal level increases and causes calls to be torn down when normal mode of operation is not allowed.

Target RAT swap failed.

UE performs a detach or disconnect PDN action based on TE requirements.

UE is entering power save mode.

RAT change on the UE.

UE security capabilities mismatch.

UMTS interface is brought down due to handover from UMTS to iWLAN.

Universal Mobile Telecommunications System (UMTS) reactivation request.

Data fail due to unacceptable network parameter.

Unacceptable non-EPS authentication.

Unknown data failure cause.

Unknown info element.

Unknown Packet Data Protocol (PDP) address type.

Unknown Packet Data Protocol (PDP) context.

RAT on which the data call is attempted/connected is no longer the preferred RAT.

P_rev supported by 1 base station is less than 6, which is not supported for a 1X data call.

Unsupported APN in current public land mobile network (PLMN).

QCI (QoS Class Identifier) indicated in the UE request cannot be supported.

User authentication.

Data call bring up fails in the VSNCP phase due to a network rejection of the VSNCP configuration request with the reason of administratively prohibited at the HSGW.

Data call bring up fails in the VSNCP phase due to a network rejection of the VSNCP configuration request because the requested APN is unauthorized.

Data call bring up fails in the VSNCP phase due to a general error.

Data call bring up fails in the VSNCP phase due to a network rejection of the VSNCP configuration request with the reason of insufficient parameter.

Data call bring up fails in the VSNCP phase due to the network rejected the VSNCP configuration request due to no PDN gateway address.

Data call bring up fails in the VSNCP phase due to a network rejection of the VSNCP configuration request because the PDN exists for this APN.

Data call bring up fails in the VSNCP phase due to a network rejection of the VSNCP configuration request due to a PDN gateway reject.

Data call bring up fails in the VSNCP phase due to a network rejection of the VSNCP configuration request because the PDN gateway is unreachable.

Data call bring up fails in the VSNCP phase due to a network rejection of PDN ID in use, or all existing PDNs are brought down with this end reason because one of the PDN bring up was rejected by the network with the reason of PDN ID in use.

Data call bring up fails in the VSNCP phase due to a network rejection of the VSNCP configuration request because the PDN limit has been exceeded.

Data call bring up fails in the VSNCP phase due to a network rejection of the VSNCP configuration request with reconnect to this PDN not allowed, or an active data call is terminated by the network because reconnection to this PDN is not allowed.

Data call bring up fails in the VSNCP phase due to a network rejection of the VSNCP configuration request with the reason of resource unavailable.

Data call bring up fails in the VSNCP phase due to a network rejection of the VSNCP configuration request for the reason of subscriber limitation.

Data call bring up fails in the VSNCP phase due to a VSNCP timeout error.