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

can't decode message #35

Closed
EugeneBogush opened this Issue Mar 14, 2018 · 6 comments

Comments

Projects
None yet
2 participants
@EugeneBogush

EugeneBogush commented Mar 14, 2018

[03/14 12:18:00.841] ERRR: Unknown procedure ID (8) for initiating message (s1ap_decoder.c:185)
200 bytes hex:
00080800 00000000 20080200 80200802 00802008 02008020 00080200 80200802
00802008 02008020 08020000 80200802 00802008 00020080 20080200 80200802
00802008 02008040 04004004 00400400 40040040 04004004 00400400 40040040
04004004 00400400 40040040 04004004 00400400 40040040 04004004 00400400
40040040 04004002 00800000 00200802 00802010 0201a002 0e330357 58826014
00523068 0090d031 f1af3432 b259666c 01000360 026f8b19 9b004000 d800bbe8
c666c010 00360000
[03/14 12:18:00.841] ASSERT: !(0). Can't decode S1AP_PDU (mme_sm.c:184)

@acetcom

This comment has been minimized.

Owner

acetcom commented Mar 14, 2018

E-RAB Release Indication(8) is not implemented yet.

Could you send wireshark packet capture file? We would like to know the conditions under which the eNodeB initiates the E-RAB Release indication (8).

Thanks!

@acetcom

This comment has been minimized.

Owner

acetcom commented Mar 14, 2018

I cannot find the packet that failed to decode in wireshark's pcapng.
I'll try to find out if there is another reason.

Thanks!

@EugeneBogush

This comment has been minimized.

EugeneBogush commented Mar 14, 2018

I think this is due to decoding id-UECapabilityInfoIndication.

@acetcom

This comment has been minimized.

Owner

acetcom commented Mar 14, 2018

Ok! Let us simulate it tomorrow!

Thank you very much!

@acetcom

This comment has been minimized.

Owner

acetcom commented Mar 15, 2018

We found out the reason. Our SCTP recv buffer is 2048. So, NextEPC cannot handle the UECapabilityInfoIndication(2248). We changes the recv buffer to 4096.

If you want to use this patch, you need to compile and install NextEPC.

Thank you for your help!

@EugeneBogush

This comment has been minimized.

EugeneBogush commented Mar 15, 2018

yes. this work correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment