Attention is currently required from: pespin.

fixeria has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/39524?usp=email )

Change subject: erab_fsm: handle RELEASE.{cmd,ind} in state erab_wait_setup_rsp ......................................................................

Patch Set 1:

(1 comment)

File src/erab_fsm.erl:

https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/39524/comment/7d6ab708_c19bc... : PS1, Line 266: {next_state, session_delete,

imho this may be wrong. You probably need to wait first for create resolution

The PFCP session has already been created at this state, it's just not modified yet. In other words, we have received E-RAB SETUP.req from the core network, created a PFCP session, and forwarded modified F-TEID to the eNB. But we haven't heard from the eNB yet.

As we have seen in the field, it may happen that the core network orders E-RAB SETUP, and then releases the UE CONTEXT before the eNB response with E-RAB SETUP.rsp. This patch helps to tear the FSMs down properly in such case.