[NGAP] Fix incorrect AMF Set ID type (uint8 → uint16) causing AMF lookup failure

Rakesh B Brequested to merge
Rakesh_B_B/openairinterface5g:develop into develop

📄 Description

This PR fixes issue #1012 (closed) , a data type issue related to the AMF Set ID used during UE RRC reestablishment. The AMF Set ID was mistakenly declared as uint8_t instead of uint16_t, even though it is a 10-bit field as specified in 3GPP TS 23.003 section 2.10.1. As a result, AMF Set IDs greater than 255 were truncated, leading to failed AMF lookups and the following warning: No matching AMF found for PLMN (MCC=%03d MNC=%0*d) and AMF SetID=%u.

Verified reestablishment succeeds with AMF Set IDs >255.

amf-set-id_warning_resolved

Acknowledgement:
Work carried out under the XnHO development and testing at the Indian Institute of Science, Bengaluru. Co-authored-by: Venkatareddy Akumalla

Merge request reports