Universal Trace Analyzer
Error codes › GTPv2-C cause

GTPv2 cause 116 Multiple PDN connections for a given APN not allowed

GTPv2-C cause3GPP TS 29.274 §8.4 (Table 8.4-1)

What it means

This subscriber already has the maximum allowed PDN connections for this APN (Multiple PDN connections for a given APN not allowed).

Where you see it

In the Cause IE of a GTPv2-C response (Create Session, Modify Bearer, Delete Session…) on S11, S5 or S8.

What to check

Check which node sent the response (MME, SGW or PGW): the cause belongs to that node's decision.

Got a trace with GTPv2 cause 116 Multiple PDN connections for a given APN not allowed? Drop it in the analyzer: it finds the step that really failed first, which node sent the code and what to ask the other side. Captures, test-system PDFs and vendor exports. 5 free analyses a month, no sign-up.

Analyze a trace free

Related codes

GTPv2 cause 115 UE already re-attachedThe UE has already re-attached, making this request obsolete (UE alrea…GTPv2 cause 117 Target access restricted for the subscriberThis subscriber is restricted from the access type/area being used for…GTPv2 cause 113 APN CongestionThe responding node is congested for this specific APN (APN Congestion…GTPv2 cause 119 MME/SGSN refuses due to VPLMN PolicyThe MME/SGSN refused this request due to Visited-PLMN policy (MME/SGSN…GTPv2 cause 120 GTP-C Entity CongestionThe responding GTP-C node itself is congested (GTP-C Entity Congestion…GTPv2 cause 111 Modifications not limited to S1-U bearersThe requested bearer modification wasn't limited to S1-U bearers as re…