Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Error in S1 setup #156

Closed
hypercloud2017 opened this issue Mar 7, 2019 · 5 comments
Closed

Error in S1 setup #156

hypercloud2017 opened this issue Mar 7, 2019 · 5 comments
Labels
Housekeeping:ToClose Issues reviewed and closed. Old requests, issues which are not bug, feature or documentation request

Comments

@hypercloud2017
Copy link

[03/07 22:01:51.430] INFO: NextEPC daemon start (main.c:157)
[03/07 22:01:51.431] INFO: CONNECTED TO 'hss.localdomain' (TCP,soc#8): (fd_logger.c:93)
[03/07 22:02:01.921] eNB-S1 accepted[10.2.40.1]:1024 in s1_path module
[03/07 22:02:01.921] eNB-S1 accepted[10.2.40.1] in master_sm module
[03/07 22:02:01.922] ASSERT: !(enb_id). Invalid param (mme_context.c:1702)
@hypercloud2017
Copy link
Author

why whould this be

@acetcom
Copy link
Member

acetcom commented Mar 8, 2019

IMHO, there is no Global-ENB-ID in S1Setup Request message.
I recommend attaching pcap file to determine the root cause.

Thanks!

@hypercloud2017
Copy link
Author

Hi found the issue END-ID set to zero which I believe is allowed, I set to other values then its ok now.

Thanks very good project this.

acetcom added a commit that referenced this issue Mar 10, 2019
@acetcom
Set ENB-ID to zero in S1AP message. (#156)
58bcda3
@acetcom
Copy link
Member

acetcom commented Mar 10, 2019

You made a good point. At this point, ENB-ID can be set to zero.
Thank you for your hard work!

@pobk pobk added the Housekeeping:ToClose Issues reviewed and closed. Old requests, issues which are not bug, feature or documentation request label Feb 17, 2023
@github-actions
Copy link

This issue has been closed automatically due to lack of activity. This has been done to try and reduce the amount of noise. Please do not comment any further. The Open5GS Team may choose to re-open this issue if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Housekeeping:ToClose Issues reviewed and closed. Old requests, issues which are not bug, feature or documentation request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pobk @acetcom @hypercloud2017