Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
The utilized SCTP stream id does not conform with requirement of 36.412 #54
According to 36.412 section 7 :
In S1AP messages recorded between OAI eNB and NextEPC :
added a commit
May 13, 2018
We've fixed the issue.
Regarding this, we added one configuration for SCTP streams.
This is only applied to MME element.
If parameter.sctp_streams is 30, output streams are defined like the followings.
The maximum input stream of SCTP is 65535. We does not provide the configuration for input stream. It is hard-corded with 65535.
Let me know if there is any problem regarding this issue.
@acetcom, one picky but possible condition comes to me that if eNB use stream id other than 0, e.g. stream id 1.. or any vaild number, for sending
@brchiu You might think that a single pair of stream identifiers for non-UE association like S1SetupRequest/Response means the same SCTP input/output stream identifier. Does it right?
I thought that S1SetupRequest/Response could be different. So, MME don’t have to see the sctp input stream id for S1SetupRequest.
Please, re-confirm it. If so, I need to change current code.
Thanks a lot!
@acetcom, you have the good point.
Because the specification uses the wording
My previous understanding might be wrong. Sorry.
Perhaps we can keep your current implementation and let other community members feedback during further interoperability tests.
Thanks for your great effort !
I tryed to connect nextepc to openairinterface (OAI)but i contue to have some probles. The nextepc log is: https://drive.google.com/open?id=1Vr3tYzQs0Skkz4i4xBpjov7qx6RtpJP-
the first woring: Unknown UE by GUTI[G:1,C:1,M_TMSI:0xe800a7b0] (mme_context.c:2160) is not a problem because i tryed with another commercial enb and with the same warning the user can correctly be attached to the nextEPC.
The main problem is the second warning: WARN: No ENB UE Context : MME_UE_S1AP_ID (s1ap_handler.c:872)
For wireshark analysis the pcap files is here: https://drive.google.com/open?id=1yfNGRtNycpfJ3j9wxBGuSE2Uplahq_Re