forked from acouzens/open5gs
47419be650
There is an issue with SESSION RELEASE not working properly depending on the PDU session release complete order in the PDUSessionResourceReleaseResponse. If the AMF receives PDUSessionResourceReleaseResponse followed by PDU session release complete, it works correctly. However, if it receives PDU session release complete followed by PDUSessionResourceReleaseResponse, it does not work correctly and sends an Error Indication to the UE/gNB. To fix this issue, we added pdu_session_release_complete_received and pdu_session_resource_release_response_received to the content so that CLEAR_SM_CONTEXT_REF() is executed when both are received. |
||
|---|---|---|
| .. | ||
| 310014 | ||
| af | ||
| app | ||
| attach | ||
| common | ||
| core | ||
| crypt | ||
| csfb | ||
| fuzzing | ||
| handover | ||
| non3gpp | ||
| registration | ||
| sctp | ||
| slice | ||
| unit | ||
| volte | ||
| vonr | ||
| meson.build | ||