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

nextepc failure on ims attach v0.5.2.36-2eac6-dirty #288

Closed
gilberto-marano opened this issue Sep 24, 2019 · 19 comments
Closed

nextepc failure on ims attach v0.5.2.36-2eac6-dirty #288

gilberto-marano opened this issue Sep 24, 2019 · 19 comments
Labels
Housekeeping:ToClose Issues reviewed and closed. Old requests, issues which are not bug, feature or documentation request

Comments

@gilberto-marano
Copy link

Hi

I'm trying to attach a Huawei with sysmocom USIM and APN ims but a verify the following crash 👍 👍
09/24 12:45:52.189: [mme] WARNING: Unknown UE by GUTI[G:2,C:1,M_TMSI:0xd7005eea] (mme-context.c:2337)
09/24 12:45:52.479: [gtp] INFO: gtp_connect() [127.0.0.1]:2123 (path.c:57)
09/24 12:45:52.479: [gtp] INFO: gtp_connect() [127.0.0.3]:2123 (path.c:57)
09/24 12:45:52.479: [gtp] INFO: gtp_connect() [127.0.0.2]:2123 (path.c:57)
09/24 12:45:52.479: [pgw] INFO: UE IMSI:[901700000028351] APN:[internet] IPv4:[172.30.100.2] IPv6:[cafe::2] (pgw-context.c:770)
09/24 12:45:52.479: [gtp] INFO: gtp_connect() [127.0.0.2]:2152 (path.c:57)
09/24 12:45:52.481: [gtp] INFO: gtp_connect() [127.0.0.3]:2152 (path.c:57)
09/24 12:45:52.754: [gtp] INFO: gtp_connect() [172.30.1.6]:2152 (path.c:57)
09/24 12:45:54.108: [pgw] INFO: UE IMSI:[901700000028351] APN:[ims] IPv4:[172.30.100.3] IPv6:[] (pgw-context.c:770)
09/24 12:45:54.112: [mme] FATAL: s1ap_handle_e_rab_setup_response: Assertion `E_RABSetupListBearerSURes' failed. (s1ap-handler.c:782)
/home/italtel/nextepc/lib/ogslib/src/core/.libs/libogscore-1.0.so.0(ogs_abort+0x2b)[0x7f014ad5b91b]
/home/italtel/nextepc/.libs/nextepc-epcd(+0x48ba3)[0x55d9b5c18ba3]
/home/italtel/nextepc/lib/ogslib/src/core/.libs/libogscore-1.0.so.0(ogs_fsm_dispatch+0x11)[0x7f014ad6aed1]
/home/italtel/nextepc/.libs/nextepc-epcd(+0x7914)[0x55d9b5bd7914]
/home/italtel/nextepc/lib/ogslib/src/core/.libs/libogscore-1.0.so.0(ogs_fsm_dispatch+0x11)[0x7f014ad6aed1]
/home/italtel/nextepc/.libs/nextepc-epcd(+0x6b5c)[0x55d9b5bd6b5c]
/home/italtel/nextepc/lib/ogslib/src/core/.libs/libogscore-1.0.so.0(+0xdb88)[0x7f014ad62b88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db)[0x7f014ab3d6db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f014a86688f]
Aborted (core dumped)
@bg80211
Copy link

bg80211 commented Sep 24, 2019

Hi

I'm trying to attach a Huawei with sysmocom USIM and APN ims but a verify the following crash
09/24 12:45:52.189: [mme] WARNING: Unknown UE by GUTI[G:2,C:1,M_TMSI:0xd7005eea] (mme-context.c:2337)
09/24 12:45:52.479: [gtp] INFO: gtp_connect() [127.0.0.1]:2123 (path.c:57)
09/24 12:45:52.479: [gtp] INFO: gtp_connect() [127.0.0.3]:2123 (path.c:57)
09/24 12:45:52.479: [gtp] INFO: gtp_connect() [127.0.0.2]:2123 (path.c:57)
09/24 12:45:52.479: [pgw] INFO: UE IMSI:[901700000028351] APN:[internet] IPv4:[172.30.100.2] IPv6:[cafe::2] (pgw-context.c:770)
09/24 12:45:52.479: [gtp] INFO: gtp_connect() [127.0.0.2]:2152 (path.c:57)
09/24 12:45:52.481: [gtp] INFO: gtp_connect() [127.0.0.3]:2152 (path.c:57)
09/24 12:45:52.754: [gtp] INFO: gtp_connect() [172.30.1.6]:2152 (path.c:57)
09/24 12:45:54.108: [pgw] INFO: UE IMSI:[901700000028351] APN:[ims] IPv4:[172.30.100.3] IPv6:[] (pgw-context.c:770)
09/24 12:45:54.112: [mme] FATAL: s1ap_handle_e_rab_setup_response: Assertion `E_RABSetupListBearerSURes' failed. (s1ap-handler.c:782)
/home/italtel/nextepc/lib/ogslib/src/core/.libs/libogscore-1.0.so.0(ogs_abort+0x2b)[0x7f014ad5b91b]
/home/italtel/nextepc/.libs/nextepc-epcd(+0x48ba3)[0x55d9b5c18ba3]
/home/italtel/nextepc/lib/ogslib/src/core/.libs/libogscore-1.0.so.0(ogs_fsm_dispatch+0x11)[0x7f014ad6aed1]
/home/italtel/nextepc/.libs/nextepc-epcd(+0x7914)[0x55d9b5bd7914]
/home/italtel/nextepc/lib/ogslib/src/core/.libs/libogscore-1.0.so.0(ogs_fsm_dispatch+0x11)[0x7f014ad6aed1]
/home/italtel/nextepc/.libs/nextepc-epcd(+0x6b5c)[0x55d9b5bd6b5c]
/home/italtel/nextepc/lib/ogslib/src/core/.libs/libogscore-1.0.so.0(+0xdb88)[0x7f014ad62b88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db)[0x7f014ab3d6db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f014a86688f]
Aborted (core dumped)

Adding two APN from profile UE , First APN example name "CONNECT" ARP Priority 2 Qos 6, Second APN name "Internet", ARP 8, QOS 69. Next Profile in usb 4g device "Internet " check Default.

This error : Bbu3900 not send E_RABSetupListBearerSURes, becose session on tru first --->"[pgw] INFO: UE IMSI:[901700000028351] APN:[internet] IPv4:[172.30.100.2] IPv6:[cafe::2] (pgw-context.c:770)"

@bg80211
Copy link

bg80211 commented Sep 24, 2019 •
edited
Loading

You used BBU3900 ? NextEPC not send bearer different is (simple id5 and id6)

@gilberto-marano
Copy link
Author

The Huawei I'm referring to is a mobile p30

@bg80211
Copy link

bg80211 commented Sep 24, 2019

Who BS (BBU) ?

@gilberto-marano
Copy link
Author

Teh BS is a casa-systems prototype of small cell family.

@gilberto-marano
Copy link
Author

Attached the pcap
HUAWEY.zip

@bg80211
Copy link

bg80211 commented Sep 25, 2019 •
edited
Loading

### Huawei does not give you a list of E_RABSetupListBearerSURes because the session has already been established with another ERAB-ID

Attached the pcap
HUAWEY.zip

!!! Adding two APN from profile UE , First APN example name "CONNECT" ARP Priority 2 Qos 6, Second APN name "Internet", ARP 8, QOS 69. Next Profile in usb 4g device "Internet " check Default.

This error : Bbu3900 not send E_RABSetupListBearerSURes, becose session on tru first --->"[pgw] INFO: UE IMSI:[901700000028351] APN:[internet] IPv4:[172.30.100.2] IPv6:[cafe::2] (pgw-context.c:770)"

@gilberto-marano
Copy link
Author

Hi

thanks for you support.
May be I was too short in my scenario description. I want to activate a Volte UE so I need
a double PDN and a double bearer ( reference in attached ) . In the pcap trace I see that when the BBU send the second E_RABSetupRequest to MME this one answer with Protocol-cause=semantic-error.
This is caused by crash or is a consequence of it ?
Where is my error ?

BR
Wonderful_s1ap-lte-attach-eps-bearer-setup.pdf

@gilberto-marano
Copy link
Author

Rectify

"when the MME send the second E_RABSetupRequest to BBU"

@gilberto-marano
Copy link
Author

May be it's useful

In the trace I don't see the ESM information request from MME to BBU ...

@gilberto-marano
Copy link
Author

Any comment ?

Thanks

@nickvsnetworking
Copy link
Contributor

I've got SIP messaging coming out of a Samsung Galaxy handset by creating a new APN called "ims" (IMS is a reserved APN name according to 3gpp so Android sees this as to do with VoLTE).

I'll share my HSS settings when I get home.

@spencersevilla
Copy link
Contributor

@nickvsnetworking would love to see those settings when you get a chance! on my side we're very interested in hooking up IMS/VoLTE, and I have a couple of follow-up questions to make sure I'm understanding things correctly. In terms of necessary configs to get SIP messages out of a handset, to my understanding we'd have to do the following:

  • setup an IMS server in our network at a specific IP address.
  • Device: create a new APN with name "ims" and IP address = (the address of the IMS).
  • MME: from some pcaps it looks like the MME already indicates support for Voice over PS in s1ap messages, so no need to do anything?
  • HSS: for the user's IMSI, add a new PDN for ims support with high QoS. We also need to expose an interface to the P-CSCF I believe?

@nickvsnetworking
Copy link
Contributor

@spencersevilla - Flick me an email, happy to help. I've got an IMS lab you're welcome to connect into.
nick@nickvsnetworking.com

@nickvsnetworking
Copy link
Contributor

Hey @gilberto-marano and @bg80211 ,
Here are my APN settings for IMS for a Samsung UE:

IMS APN

Once I added these I had to add the APN "ims" with type "ims" and then the additional bearer was setup, the PCO for P-CSCF was requested from the P-GW and the rest is up to the UE & the IMS network.

S1APNAS-EPS E-RABSetupRequest Activate default EPS bearer context request

@spencersevilla - You're pretty much right,

  • You setup the IMS servers with the P-CSCF IP address specified in the PGW config file of Open5GS,

  • On the device you create a new APN (If you're on Android you may find it's created for you by the Android carrier settings XML depending on the MNC / MCC combination you're using) called "ims" with the type set to IMS, but you don't set the IP address of the P-CSCF here - The UE requests it in the NAS messaging (Protocol Configuration Options) when setting up the additional bearer.

  • No changes required on the MME

  • HSS just needs a new APN also with the name IMS. Through the web interface of Open5Gs you can set a dedicated bearer underneath that to the IP address of your P-CSCF but I've found the UEs I've played with haven't cared about the QCI values.

@gilberto-marano
Copy link
Author

Hi Nick

You wrote "the PCO for P-CSCF was requested from the P-GW", but really what in your trace seems the answer of PGW with the requested IPs. I think the request MUST start from UE.

Do you agree ?

Thanks

@nickvsnetworking
Copy link
Contributor

nickvsnetworking commented Dec 5, 2019 via email

@gilberto-marano
Copy link
Author

gilberto-marano commented Dec 5, 2019 via email

@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
5 participants
@pobk @spencersevilla @nickvsnetworking @bg80211 @gilberto-marano