-
Notifications
You must be signed in to change notification settings - Fork 598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
5G can't handle userLocationInformationNR timestamp field #12846
Comments
This is the packet dissection of the failing case. |
This issue or pull request has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs in the next 14 days. |
This issue or pull request has exceeded its lifecylce and was automatically closed. Should you wish to continue working on this, please reopen it. |
This issue or pull request has exceeded its lifecylce and was automatically closed. Should you wish to continue working on this, please reopen it. |
…12846 The issue reported with magma#12846 is caused by the missaligment of the NGAP R16 ASN.1 file used to generate the NGAP message library with the published standard. The file was previously modified to avoid an error that the asn1 compiler was throwing for the missing external reference. The fix is returning the NGAP R16 ASN.1 to the published standard and is dereferencing the `ProtocolIE-SingleContainer` to avoid the compiler error (untill the compiler issue is addressed). All sanity test had passed on the fix. Signed-off-by: Jordan Vrtanoski <jordan.vrtanoski@gmail.com>
…12846 The issue reported with magma#12846 is caused by the missaligment of the NGAP R16 ASN.1 file used to generate the NGAP message library with the published standard. The file was previously modified to avoid an error that the asn1 compiler was throwing for the missing external reference. The fix is returning the NGAP R16 ASN.1 to the published standard and is dereferencing the `ProtocolIE-SingleContainer` to avoid the compiler error (untill the compiler issue is addressed). All sanity test had passed. Signed-off-by: Jordan Vrtanoski <jordan.vrtanoski@gmail.com>
…12846 The issue reported with magma#12846 is caused by the missaligment of the NGAP R16 ASN.1 file used to generate the NGAP message library with the published standard. The file was previously modified to avoid an error that the asn1 compiler was throwing for the missing external reference. The fix is returning the NGAP R16 ASN.1 to the published standard and is dereferencing the `ProtocolIE-SingleContainer` to avoid the compiler error (untill the compiler issue is addressed). All sanity test had passed. Signed-off-by: Jordan Vrtanoski <jordan.vrtanoski@gmail.com>
Has this been added to AGW v1.8? I am still getting the same error |
…12846 The issue reported with magma#12846 is caused by the missaligment of the NGAP R16 ASN.1 file used to generate the NGAP message library with the published standard. The file was previously modified to avoid an error that the asn1 compiler was throwing for the missing external reference. The fix is returning the NGAP R16 ASN.1 to the published standard and is dereferencing the `ProtocolIE-SingleContainer` to avoid the compiler error (untill the compiler issue is addressed). All sanity test had passed. Signed-off-by: Jordan Vrtanoski <jordan.vrtanoski@gmail.com>
…12846 The issue reported with magma#12846 is caused by the missaligment of the NGAP R16 ASN.1 file used to generate the NGAP message library with the published standard. The file was previously modified to avoid an error that the asn1 compiler was throwing for the missing external reference. The fix is returning the NGAP R16 ASN.1 to the published standard and is dereferencing the `ProtocolIE-SingleContainer` to avoid the compiler error (untill the compiler issue is addressed). All sanity test had passed. Signed-off-by: Jordan Vrtanoski <jordan.vrtanoski@gmail.com>
…12846 The issue reported with magma#12846 is caused by the missaligment of the NGAP R16 ASN.1 file used to generate the NGAP message library with the published standard. The file was previously modified to avoid an error that the asn1 compiler was throwing for the missing external reference. The fix is returning the NGAP R16 ASN.1 to the published standard and is dereferencing the `ProtocolIE-SingleContainer` to avoid the compiler error (untill the compiler issue is addressed). All sanity test had passed. Signed-off-by: Jordan Vrtanoski <jordan.vrtanoski@gmail.com>
…12846 The issue reported with magma#12846 is caused by the missaligment of the NGAP R16 ASN.1 file used to generate the NGAP message library with the published standard. The file was previously modified to avoid an error that the asn1 compiler was throwing for the missing external reference. The fix is returning the NGAP R16 ASN.1 to the published standard and is dereferencing the `ProtocolIE-SingleContainer` to avoid the compiler error (untill the compiler issue is addressed). All sanity test had passed. Signed-off-by: Jordan Vrtanoski <jordan.vrtanoski@gmail.com>
…12846 The issue reported with magma#12846 is caused by the missaligment of the NGAP R16 ASN.1 file used to generate the NGAP message library with the published standard. The file was previously modified to avoid an error that the asn1 compiler was throwing for the missing external reference. The fix is returning the NGAP R16 ASN.1 to the published standard and is dereferencing the `ProtocolIE-SingleContainer` to avoid the compiler error (untill the compiler issue is addressed). All sanity test had passed. Signed-off-by: Jordan Vrtanoski <jordan.vrtanoski@gmail.com>
…12846 The issue reported with magma#12846 is caused by the missaligment of the NGAP R16 ASN.1 file used to generate the NGAP message library with the published standard. The file was previously modified to avoid an error that the asn1 compiler was throwing for the missing external reference. The fix is returning the NGAP R16 ASN.1 to the published standard and is dereferencing the `ProtocolIE-SingleContainer` to avoid the compiler error (untill the compiler issue is addressed). All sanity test had passed. Signed-off-by: Jordan Vrtanoski <jordan.vrtanoski@gmail.com>
…12846 The issue reported with magma#12846 is caused by the missaligment of the NGAP R16 ASN.1 file used to generate the NGAP message library with the published standard. The file was previously modified to avoid an error that the asn1 compiler was throwing for the missing external reference. The fix is returning the NGAP R16 ASN.1 to the published standard and is dereferencing the `ProtocolIE-SingleContainer` to avoid the compiler error (untill the compiler issue is addressed). All sanity test had passed. Signed-off-by: Jordan Vrtanoski <jordan.vrtanoski@gmail.com>
Your Environment
Describe the Issue
Tested the AGW against UERANSIM v3.2.6. The InitialUEMessage fails. The mme log says "tasks/ngap/ngap_amf_decoder.c:0043 Failed to decode PDU". There was no reply message from the AGW. The timestamp field is optional per ts 38.413 UserLocationInformationNR section 9.4.5.
To Reproduce
Expected behavior
The UERANSIM UE should register, get an IP, and be able to pass traffic. Although I modified UERANSIM to get my test to work (see below), I believe the actual bug is in the amf because it should have accepted the timestamp field.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
I was able to modify UERANSIM to make it work, by commenting out the timestamp field in file UERANSIM/src/gnb/ngap/transport.cpp function NgapTask::sendNgapUeAssociated. See below. The two commented out lines below are the changes.
The text was updated successfully, but these errors were encountered: