How cellphone to use srsepc to access internet

hello all:
I build the srsLTE on my laptop,and write the white card with the given IMSI and other information,then run the srsepc and srsenb,it seems work,but when I ping the ue’s ip address from labtop terminal,it receive nothing data packet.Dose anybody tell me what is wrong,thanks~

miro@miro-Inspiron-7447:~$ sudo srsepc

Built in Release mode using commit 0e89fa9f on branch master.

— Software Radio Systems EPC —

Reading configuration file /home/miro/.config/srslte/epc.conf…
HSS Initialized.
MME S11 Initialized
MME GTP-C Initialized
MME Initialized. MCC: 0xf001, MNC: 0xff01
SPGW GTP-U Initialized.
SPGW S11 Initialized.
SP-GW Initialized.
Received S1 Setup Request.
S1 Setup Request - eNB Name: srsenb01, eNB id: 0x19b
S1 Setup Request - MCC:001, MNC:01, PLMN: 61712
S1 Setup Request - TAC 7, B-PLMN 0
S1 Setup Request - Paging DRX 2
Sending S1 Setup Response
Initial UE message: LIBLTE_MME_MSG_TYPE_TRACKING_AREA_UPDATE_REQUEST
Received Initial UE message – Tracking Area Update Request
Tracking Area Update Request – S-TMSI 0x5dddb293
Tracking Area Update Request – eNB UE S1AP Id 7
Warning: Tracking area update requests are not handled yet.
Could not find IMSI from M-TMSI. M-TMSI 0x5dddb293
Received UE Context Release Request. MME-UE S1AP Id 524290
No UE context to release found. MME-UE S1AP Id: 524290
Initial UE message: LIBLTE_MME_MSG_TYPE_TRACKING_AREA_UPDATE_REQUEST
Received Initial UE message – Tracking Area Update Request
Tracking Area Update Request – S-TMSI 0x5dddb293
Tracking Area Update Request – eNB UE S1AP Id 8
Warning: Tracking area update requests are not handled yet.
Could not find IMSI from M-TMSI. M-TMSI 0x5dddb293
Received UE Context Release Request. MME-UE S1AP Id 524290
No UE context to release found. MME-UE S1AP Id: 524290
Initial UE message: LIBLTE_MME_MSG_TYPE_ATTACH_REQUEST
Received Initial UE message – Attach Request
Attach request – M-TMSI: 0x5dddb293
Attach request – eNB-UE S1AP Id: 9
Attach request – Attach type: 2
Attach Request – UE Network Capabilities EEA: 11110000
Attach Request – UE Network Capabilities EIA: 01110000
Attach Request – MS Network Capabilities Present: true
PDN Connectivity Request – EPS Bearer Identity requested: 0
PDN Connectivity Request – Procedure Transaction Id: 200
PDN Connectivity Request – ESM Information Transfer requested: true
UL NAS: Received Identity Response
ID Response – IMSI: 208920100001100
Downlink NAS: Sent Authentication Request
UL NAS: Received Authentication Response
Authentication Response – IMSI 208920100001100
UE Authentication Accepted.
Generating KeNB with UL NAS COUNT: 0
Downlink NAS: Sending NAS Security Mode Command.
UL NAS: Received Security Mode Complete
Security Mode Command Complete – IMSI: 208920100001100
Sending ESM information request
UL NAS: Received ESM Information Response
ESM Info: APN srsapn
Getting subscription information – QCI 7
Sending Create Session Request.
Creating Session Response – IMSI: 208920100001100
Creating Session Response – MME control TEID: 1
Received GTP-C PDU. Message type: GTPC_MSG_TYPE_CREATE_SESSION_REQUEST
SPGW: Allocated Ctrl TEID 1
SPGW: Allocated User TEID 1
SPGW: Allocate UE IP 172.16.0.2
Received Create Session Response
Create Session Response – SPGW control TEID 1
Create Session Response – SPGW S1-U Address: 127.0.1.100
SPGW Allocated IP 172.16.0.2 to IMSI 208920100001100
Adding attach accept to Initial Context Setup Request
Initial Context Setup Request – eNB UE S1AP Id 9, MME UE S1AP Id 1
Initial Context Setup Request – E-RAB id 5
Initial Context Setup Request – S1-U TEID 0x1. IP 127.0.1.100
Initial Context Setup Request – S1-U TEID 0x1. IP 127.0.1.100
Initial Context Setup Request – QCI 7
Received Initial Context Setup Response
E-RAB Context Setup. E-RAB id 5
E-RAB Context – eNB TEID 0x900003; eNB GTP-U Address 127.0.1.1
UL NAS: Received Attach Complete
Unpacked Attached Complete Message. IMSI 208920100001100
Unpacked Activate Default EPS Bearer message. EPS Bearer id 5
Received GTP-C PDU. Message type: GTPC_MSG_TYPE_MODIFY_BEARER_REQUEST
Sending EMM Information
Unhandled NAS integrity protected message LIBLTE_MME_MSG_TYPE_PDN_CONNECTIVITY_REQUEST
Received UE Context Release Request. MME-UE S1AP Id 1
There are active E-RABs, send release access bearers request
Received GTP-C PDU. Message type: GTPC_MSG_TYPE_RELEASE_ACCESS_BEARERS_REQUEST
UE is ECM IDLE.
Received UE Context Release Complete. MME-UE S1AP Id 1
UE is not ECM connected. No need to release S1-U. MME UE S1AP Id 1
UE Context Release Completed.
Found UE for Downlink Notification
MME Ctr TEID 0x2, IMSI: 208920100001100
T3413 expired – Could not page the ue.
Received GTP-C PDU. Message type: GTPC_MSG_TYPE_DOWNLINK_DATA_NOTIFICATION_FAILURE_INDICATION
Found UE for Downlink Notification
MME Ctr TEID 0x2, IMSI: 208920100001100
T3413 expired – Could not page the ue.
Received GTP-C PDU. Message type: GTPC_MSG_TYPE_DOWNLINK_DATA_NOTIFICATION_FAILURE_INDICATION
Found UE for Downlink Notification
MME Ctr TEID 0x2, IMSI: 208920100001100
T3413 expired – Could not page the ue.
Received GTP-C PDU. Message type: GTPC_MSG_TYPE_DOWNLINK_DATA_NOTIFICATION_FAILURE_INDICATION
Found UE for Downlink Notification
MME Ctr TEID 0x2, IMSI: 208920100001100
T3413 expired – Could not page the ue.
Received GTP-C PDU. Message type: GTPC_MSG_TYPE_DOWNLINK_DATA_NOTIFICATION_FAILURE_INDICATION
Found UE for Downlink Notification
MME Ctr TEID 0x2, IMSI: 208920100001100
T3413 expired – Could not page the ue.
Received GTP-C PDU. Message type: GTPC_MSG_TYPE_DOWNLINK_DATA_NOTIFICATION_FAILURE_INDICATION
Found UE for Downlink Notification
MME Ctr TEID 0x2, IMSI: 208920100001100
T3413 expired – Could not page the ue.
Received GTP-C PDU. Message type: GTPC_MSG_TYPE_DOWNLINK_DATA_NOTIFICATION_FAILURE_INDICATION
Found UE for Downlink Notification
MME Ctr TEID 0x2, IMSI: 208920100001100
T3413 expired – Could not page the ue.
Received GTP-C PDU. Message type: GTPC_MSG_TYPE_DOWNLINK_DATA_NOTIFICATION_FAILURE_INDICATION
Found UE for Downlink Notification

miro@miro-Inspiron-7447:~$ sudo srsenb
.
.

==== eNodeB started ===
Type to view trace
[INFO] RX LPF configured
Set Rx bandwidth to 8.64 MHz
[INFO] Filter calibrated. Filter order-4th, filter bandwidth set to 8.64 MHz.Real pole 1st order filter set to 2.5 MHz. Preemphasis filter not active
[INFO] TX LPF configured
Set Tx bandwidth to 8.64 MHz

Warning TX/RX time offset has not been calibrated for device lime_mini. Set a value manually

[INFO] Tx calibration finished
[INFO] Rx calibration finished
RACH: tti=2381, preamble=18, offset=13, temp_crnti=0x46
Disconnecting rnti=0x46.
RACH: tti=3751, preamble=19, offset=13, temp_crnti=0x47
Disconnecting rnti=0x47.
RACH: tti=3841, preamble=50, offset=13, temp_crnti=0x48
Disconnecting rnti=0x48.
RACH: tti=3931, preamble=18, offset=13, temp_crnti=0x49
Disconnecting rnti=0x49.
RACH: tti=4021, preamble=5, offset=13, temp_crnti=0x4a
Disconnecting rnti=0x4a.
RACH: tti=4111, preamble=30, offset=13, temp_crnti=0x4b
Disconnecting rnti=0x4b.
RACH: tti=4201, preamble=26, offset=13, temp_crnti=0x4c
Disconnecting rnti=0x4c.
RACH: tti=4291, preamble=4, offset=13, temp_crnti=0x4d
Disconnecting rnti=0x4d.
RACH: tti=4381, preamble=32, offset=13, temp_crnti=0x4e
Disconnecting rnti=0x4e.
RACH: tti=4471, preamble=47, offset=13, temp_crnti=0x4f
Disconnecting rnti=0x4f.
RACH: tti=4561, preamble=29, offset=13, temp_crnti=0x50
Disconnecting rnti=0x50.
RACH: tti=4451, preamble=2, offset=13, temp_crnti=0x51
Disconnecting rnti=0x51.
RACH: tti=5811, preamble=35, offset=15, temp_crnti=0x52
Disconnecting rnti=0x52.
RACH: tti=5901, preamble=34, offset=15, temp_crnti=0x53
Disconnecting rnti=0x53.
RACH: tti=5991, preamble=37, offset=15, temp_crnti=0x54
RACH: tti=6081, preamble=22, offset=13, temp_crnti=0x55
Disconnecting rnti=0x54.
Disconnecting rnti=0x55.
RACH: tti=6171, preamble=32, offset=13, temp_crnti=0x56
Disconnecting rnti=0x56.
RACH: tti=6261, preamble=44, offset=15, temp_crnti=0x57
Disconnecting rnti=0x57.
RACH: tti=6351, preamble=11, offset=15, temp_crnti=0x58
Disconnecting rnti=0x58.
RACH: tti=6441, preamble=18, offset=15, temp_crnti=0x59
Disconnecting rnti=0x59.
RACH: tti=6531, preamble=34, offset=15, temp_crnti=0x5a
Disconnecting rnti=0x5a.
RACH: tti=6621, preamble=51, offset=15, temp_crnti=0x5b
Disconnecting rnti=0x5b.
RACH: tti=6511, preamble=9, offset=13, temp_crnti=0x5c
User 0x5c connected
Disconnecting rnti=0x5c.
RACH: tti=8031, preamble=42, offset=13, temp_crnti=0x5d
Disconnecting rnti=0x5d.
RACH: tti=4791, preamble=7, offset=13, temp_crnti=0x5e
RACH: tti=9331, preamble=10, offset=13, temp_crnti=0x5f
User 0x5f connected
Disconnecting rnti=0x5e.

miro@miro-Inspiron-7447:~/snow/SDR/srsLTE/srsepc$ ping 172.16.0.2
PING 172.16.0.2 (172.16.0.2) 56(84) bytes of data.
^C
— 172.16.0.2 ping statistics —
40 packets transmitted, 0 received, 100% packet loss, time 39931ms

If nobody responds here to advise I would suggest asking in the srsLTE community.

Hi, I am building srslte using LimeSDR-USB as base station and commercial phone huawei dongle.i succeded in eNB and EPC, i am using default configuration and loaded SIM parameter as per HSS db. SGI interface is created.but signal in the UE am no able to catch.
can you let me know what i need to change or the possible reasons for the same.

Thanks
Ram