Universal Trace Analyzer
Error codes › GTPv2-C cause

GTPv2 cause 109 Invalid peer

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

What it means

The peer that sent this request isn't a recognized/expected peer (Invalid peer).

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 the peer/route configuration on the responding node.

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

Got a trace with GTPv2 cause 109 Invalid peer? 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