Feature #2519

GTP-U sequence numbers are enabled unconditionally

Added by laforge about 1 year ago. Updated 8 months ago.

Target version:
Start date:
Due date:
% Done:


Spec Reference:


In order to support and test all possible configuration, it should be possible to disable GTP-U sequence numbers on both the GGSN as well as the sgsnemu side.


#1 Updated by laforge about 1 year ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 20

first had to clean up the manually edited gengetopt-generated option parser, but now actually working on this.

#2 Updated by laforge about 1 year ago

  • % Done changed from 20 to 80

See and specifically

pending some automatic testing for with/without seq-nr on both sgsnemu and ggsn side.

#3 Updated by laforge about 1 year ago

patches merged to master, manually verified both with and without g-pdu sequence numbers onboth sgsnemu and osmo-ggsn.

#4 Updated by laforge about 1 year ago

  • Checklist item ttcn-3 testing added
  • Checklist item possibly some automatic testing for sgsnemu side added

leaving this open as related tests are not written yet

#5 Updated by laforge 10 months ago

  • Assignee changed from laforge to stsp

assigning to stsp for adding related test cases to the GGSN_Tests.ttcn test suite.

#6 Updated by stsp 8 months ago

#7 Updated by stsp 8 months ago

Above test case has been merged.

Does this test provide sufficient coverage?

It seems sgsnemu shares its GTP code with osmo-ggsn.
Do we need a separate test for it?

#8 Updated by stsp 8 months ago

  • Status changed from In Progress to Resolved

No response to my above question yet.

Closing this issue since as far as I can tell we are done here. Please re-open if that is not the case.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)