UE attach problem about open5gs HOT 17 CLOSED

Sorry now I undestand, I need to set the db in order to use nexepc.
Everything works thanks

from open5gs.

If UE sends TAU-request and MME does not know the GUTI, NextEPC-MME sends Identity Request. In this case, UE/eNB should send Identity Response according to NAS spec document. However, UE/eNB does not send any response.

On the other hand, the OAI immediately sends a TAU reject. So, to improve compatibility, NextEPC is also modified to send TAU-Reject in this case.

Note that it is not yet released to the Ubuntu package. To test this, you need to build the source code from git. You can refer to http://nextepc.org/guides/2-build/

Thanks!

from open5gs.

thanks

following the procedure in the link I have some problem in the installation of the webui
at the step: npm install the output

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

Then running (npm run dev) the web interface doesnot work

can you help me with this problem?

from open5gs.

Here is my trial. (2017 Macbook Pro 14.1, Ubuntu 17.10)

For the most part, I've installed nodejs.

sudo apt-get -y install curl
curl -sL https://deb.nodesource.com/setup_9.x | sudo -E bash - 
sudo apt-get install nodejs

And then, I've installed the dependency package.

acetcom@artful:~/Documents/git/nextepc/webui$ npm i

> [email protected] postinstall /home/acetcom/Documents/git/nextepc/webui/node_modules/uglifyjs-webpack-plugin
> node lib/post_install.js

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 618 packages in 36.726s

Are you seeing the last line "added 618 packages in 36.726s"?

In my case, "npm run dev" is successfully worked.

acetcom@artful:~/Documents/git/nextepc/webui$ npm run dev

I'm hoping that you can solve the problem.

Thanks!

from open5gs.

I launch the command npm i as follow:

user1@nextepc:~/workspace/nextepc/webui$ npm i
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] >
(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
[email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
up to date in 5.063s

then I launch the command "npm run dev" as below

user1@nextepc:~/workspace/nextepc/webui$ npm run dev

[email protected] dev /home/user1/workspace/nextepc/webui
node server/index.js

Using external babel configuration
Location: "/home/user1/workspace/nextepc/webui/.babelrc"

DONE Compiled successfully in 2299ms

Mongoose: accounts.count({}, {})
(node:9800) DeprecationWarning: ensureIndex() is deprecated in Mongoose >= 4.12.0, use
createIndex() instead
Ready on http://localhost:3000
Mongoose: subscribers.createIndex({ imsi: 1 }, { unique: true, background: true })
Mongoose: accounts.createIndex({ username: 1 }, { unique: true, background: true })
Mongoose: accounts.findOne({ '$or': [ { username: 'admin' } ] }, { fields: { hash: 0, salt: 0 } })

Anyway the problem continue because even if the command "npm run dev" works i cannot access to the web-interface from another desktop. (I had istalled Next EPC in a VM Server so i can manage the WebUI only from another desktop). Maybe the problem is realated to the nextepc-deamons

Using procedure http://nextepc.org/guides/1-installation/ all the deamon correctly works.

Using procedure http://nextepc.org/guides/2-build/ i can run nextepc only in the folder where it is installed using the command ~/nextepc$ ./nextepc-epcd.

All the deamon commands like: "sudo systemctl start nextepc-mmed" or "sudo systemctl status nextepc-mmed" etc .. does not find any service running even if the nextepc is running.

I launch the ./test/testepc in the following is shown the lines after the launch:

File Logging : '/home/11618196/workspace/nextepc/install/var/log/nextepc/nextepc.log'
MongoDB URI : 'mongodb://localhost/nextepc'
Configuration : '/home/11618196/workspace/nextepc/install/etc/nextepc/nextepc.conf'
s1ap_message_test : SUCCESS
nas_message_test : SUCCESS
gtp_message_test : SUCCESS
security_test : SUCCESS
s1setup_test : SUCCESS
attach_test : -Line 135: Condition is false, but expected true > -[04/06 09:57:16.584] ERRR: emm_handle_attach_request() failed (emm_sm.c:165) > [04/06 09:57:16.585] ERRR: Unknown event[MME_EVT_EMM_MESSAGE] (emm_sm.c:730) > -[04/06 09:57:16.585] ERRR: Unknown event[MME_EVT_EMM_MESSAGE] (emm_sm.c:730) > -[04/06 09:57:16.585] ASSERT: !(sess). No Session : [PTI:33] (mme_context.c:2667)
[04/06 09:57:16.585] ASSERT: !(bearer). No Bearer context (mme_sm.c:357) |> [04/06 09:57:16.885] ASSERT: !(sess). Null param (s1ap_handler.c:551)
[04/06 09:57:17.084] ERRR: Unknown event[MME_EVT_EMM_MESSAGE] (emm_sm.c:730) > /[04/06 09:57:17.384] ASSERT: !(hi). (common/testpacket.c:2516)

you can find the log file in https://drive.google.com/open?id=1r7oIWJImxRgl1oLQ0ExMaqxHRRpYL7XG

I hope all these information can help you in understanding what is missing in may nextepc installation

thanks

from open5gs.

Before testing NextEPC, you should delete test subscriber info in MongoDB. There are two ways. One is just using WebUI. In this environment, you can easily delete test subscriber. if you cannot use WebUI, you can delete the test subscriber in MongoDB client.

Sukchanui-MacBook-Pro:~ acetcom$ mongo
MongoDB shell version v3.6.3
connecting to: mongodb://127.0.0.1:27017
MongoDB server version: 3.6.3
> use nextepc
switched to db nextepc
> db.subscribers.find()
{ "_id" : ObjectId("5ac60ad8ef125eaac726fe0d"), "imsi" : "901700000017409", "pdn" : [ { "apn" : "internet2", "_id" : ObjectId("5ac60ad8ef125eaac726fe0f"), "pcc_rule" : [ ], "qos" : { "qci" : 9, "arp" : { "priority_level" : 8, "pre_emption_vulnerability" : 1, "pre_emption_capability" : 1 } }, "type" : 2 }, { "apn" : "internet", "_id" : ObjectId("5ac60ad8ef125eaac726fe0e"), "pcc_rule" : [ ], "qos" : { "qci" : 9, "arp" : { "priority_level" : 8, "pre_emption_vulnerability" : 1, "pre_emption_capability" : 1 } }, "type" : 2 } ], "ambr" : { "downlink" : NumberLong(1024000), "uplink" : NumberLong(1024000) }, "subscribed_rau_tau_timer" : 12, "network_access_mode" : 2, "subscriber_status" : 0, "access_restriction_data" : 32, "security" : { "k" : "73D16C657E8B434BCFCA74A5269728FE", "amf" : "8000", "op" : null, "opc" : "D7B4CAA787118615B8B06E9A173346FB", "rand" : "85439438 F8F4D732 87E6AD67 5D9C9B95", "sqn" : NumberLong(2602) }, "__v" : 0 }
> db.subscribers.drop()

So, NextEPC is installed well. Please, ignore the "Line 135: Condition false...".

And also, your WebUI might be successfully installed in Virtual Machine. We believe that the problem is related to network configuration between VM and anther Host.

Thanks!

from open5gs.

When I launch mong the following string appear:

user1@nextepc:~/workspace/nextepc/webui$ mongo
MongoDB shell version: 2.6.10
connecting to: test

there is some reason for connect the mongo to test?? it seem strange to me

from open5gs.

NextEPC does not set ‘test’. It’s just MongoDB default. See the link

from open5gs.

thanks now everything works.
Enyway in the web interface i can see my old configuration of UEs even if running
mongo
and then

db.subscribers.find()

This means that there is no subscribers in the db? My Web interface shows 1 subscriver, What this means?

from open5gs.

No. If there is one UE in 'db.subscribers.find()', it means that you configured one UE.

You can remove one specific UE with WebUI.
If you want to remove all UEs, just run 'db.subscribers.drop()' in mongo shell.

Happy Hacking!

from open5gs.

I already remove all the ue in the mongo, but the UEs are not removed in the WebUI.... it is possible that that the WebUI is not correctly configured with the mongodb?

from open5gs.

There is someone that reach to attach an UE using Openairinterface as eNB and nextepc as EPC. Becasuse I continue to have the same problem show at the beginning of this thread.

nexepc log
[04/13 17:20:38.007] eNB-S1 accepted[163.162.97.43]:36412 in s1_path module
[04/13 17:20:38.007] eNB-S1 accepted[163.162.97.43] in master_sm module
[04/13 17:21:34.770] WARN: Unknown message[65] (emm_sm.c:489)
[04/13 17:21:59.809] WARN: Implicit S1 release (mme_sm.c:282)
[04/13 17:21:59.809] WARN: ENB_UE_S1AP_ID[420141] MME_UE_S1AP_ID[4] (mme_sm.c:285)
[04/13 17:21:59.810] WARN: Unknown message[65] (emm_sm.c:489)
[04/13 17:22:24.809] WARN: Implicit S1 release (mme_sm.c:282)
[04/13 17:22:24.809] WARN: ENB_UE_S1AP_ID[7332060] MME_UE_S1AP_ID[5] (mme_sm.c:285)
[04/13 17:22:24.809] WARN: Unknown message[65] (emm_sm.c:489)
[04/13 17:22:49.809] WARN: Implicit S1 release (mme_sm.c:282)
[04/13 17:22:49.809] WARN: ENB_UE_S1AP_ID[16398672] MME_UE_S1AP_ID[6] (mme_sm.c:285)
[04/13 17:22:49.809] WARN: Unknown message[65] (emm_sm.c:489)

the nextepc receve an unknow message [65] what this means?

from open5gs.

Could you attach log file and wireshark packet capture?

Thanks!

from open5gs.

you can find the file here https://drive.google.com/open?id=1zJIA0IDUNGcxq23xSAWwW4U3VArLlu6y

additional information in my second log: https://drive.google.com/open?id=1aYtwkeEe4RBfVMRMLhTCBo-R0ZKrPWVq

from open5gs.

We need your all nextepc.log file.

From the restricted information, we suggest you check the followings things.

1. Compare IMSI and PLMN_ID
2. Check K, OPc between your USIM and WebUI
3. Check APN

If there is a problem above, NextEPC will not handle the message[65] which means Attach Request.

Thanks a lot!

from open5gs.

I try using an'other UE already tested with another EPC. The wireshark log link is https://drive.google.com/open?id=1fw2CcmwlDaqwPSVFVptLQGT8KKr-XjYI

the EPC log are allways:
[04/23 09:46:41.890] WARN: Implicit S1 release (mme_sm.c:282)
[04/23 09:46:41.890] WARN: ENB_UE_S1AP_ID[420141] MME_UE_S1AP_ID[1] (mme_sm.c:285)
[04/23 09:46:41.890] WARN: Unknown message[65] (emm_sm.c:489)

you can find all the nextepc.log file here https://drive.google.com/open?id=13C38QtU5-SgtjgSrK54bETv5KVEUudiP

from open5gs.

We think that it might be a OAI problem.
If MME sends Identity Request, OAI-eNB should send Identity Response according to spec document. But OAI-eNB does not send Identity Response. NextEPC did not implement this exception case.

Basically, NextEPC & another EPC should support the multiple MME feature. We'll support this feature as we described roadmap. But, at this point it is not available.

If multiple MME is supported, NextEPC may not send Identity Request. NextEPC's MME will try to get the UE information from another EPC.

Anyway, as I mentioned earlier, OAI-eNB should send Identity Response regards of supporting multiple MME features.

Thanks!

from open5gs.