aboutsummaryrefslogtreecommitdiffstats
path: root/m4
diff options
context:
space:
mode:
authorNeels Hofmeyr <neels@hofmeyr.de>2022-07-27 14:59:30 +0200
committerNeels Hofmeyr <neels@hofmeyr.de>2022-07-28 13:52:17 +0200
commitd6168a81031a7caf72e1d2e3db7ed52b0d8fdb69 (patch)
tree7feaef608f23756fc87c311732ebd0193979d426 /m4
parent1a9a3ad342bcd558c8e06f238f91644116d45028 (diff)
pfcp_endpoint: fix final PFCP retrans resp_cb
After the final retransmission of a sent request, still keep the message in the queue for its expiry period, so that a later response is matched to the request. The osmo_pfcp_msg.resp_cb() depends on the sent message to remain in the queue until it times out. That was not the case in an earlier stage of libosmo-pfcp development. I noticed this during ttcn3 testing, where osmo-hnbgw continuously resends PFCP Association Setup Requests, and fails to associate if ttcn3 happens to respond to the final retransmission of a request. Related: SYS#5599 Change-Id: Iaca396891921f7057015ce6e1e4528b955757809
Diffstat (limited to 'm4')
0 files changed, 0 insertions, 0 deletions