Universal Trace Analyzer
Error codes › GTPv2-C cause

GTPv2 cause 64 Context Not Found

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

What it means

The responding node has no record of the context (session/bearer) this request refers to (Context Not Found) -- often means the session was already torn down on that side.

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 whether the session was recently released or timed out on the responding node before this request arrived.

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

Got a trace with GTPv2 cause 64 Context Not Found? 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 65 Invalid Message FormatThe request's message format itself was invalid (Invalid Message Forma…GTPv2 cause 66 Version not supported by next peerThe responding node doesn't support this GTPv2 version (Version not su…GTPv2 cause 67 Invalid lengthAn information element in the request had the wrong length (Invalid le…GTPv2 cause 68 Service not supportedThe responding node doesn't support the requested service (Service not…GTPv2 cause 69 Mandatory IE incorrectA required field in the request had an invalid value (Mandatory IE inc…GTPv2 cause 70 Mandatory IE missingA required field was missing from the request entirely (Mandatory IE m…