Attention is currently required from: daniel, fixeria, fixeria, laforge.

View Change

1 comment:

• File sgsn/SGSN_Tests.ttcn:

  • Patch Set #6, Line 3748: f_pdp_ctx_act(apars);

    I don't think it really matters for this specific test scenario whether the requested IP address mat […]

    @axilirator@gmail.com I think it makes sense to validate the whole scenario as closely as it will usually run. That means MS requesting dynamic address. This may affect the code logic inside osmo-sgsn, turning it into a specific state where the IP address passed later on in the newly added messages may affect.

    A) To me that looks like a bug in osmo-sgsn, because afaiu the MS got an IP address assigned from GGSN previously right? Why is it not proividing the IP address to the MME then?

    Something seems really odd here and we need to agree on what's going first. Please avoid merging this patch until we are all on the same track,

    I agree it makes no sense to encode an empty PDP Address in SGSN Context Response.
    After all, a properly established pdp context should have a valid address (assigned by GGSN). If there's no valid IP address (it shouldn't happen in first place? maybe because pdp ctx creation is ongoing with GGSN?), then the SGSN should refrain from sending that PDP Context in the list, as I think is explained somewhere in the specs iirc.

To view, visit change 36601. To unsubscribe, or for help writing mail filters, visit settings.