[srslte-users] UE not identifying ENB

devifr devifr at gmail.com
Tue Dec 18 23:11:14 UTC 2018


No go on either of the resource block configs.  I'll send the logs/pcaps
separately. They exceed the max size .

A couple of items that I notice in both of the epc logs is that 1) both the
HSS and MME identify the MCC/MNC as 61441/65281 and 2) it indicates that
IPv6 is not supported.  To address the first item, the PLMN in both the
enb.conf and the epc.conf indicate a MCC/MNC of 00101.  To address the
second item, I've confirmed in the APN settings that it is set to IPv4.
I'm not sure where either of the previously mentioned errors are coming
from.

Additionally, I've attached a screenshot of my SIM parameters.  This is
just to ensure that I've got everything correct.  Also, I've tried this SIM
in an Essential device....no joy.

Any input is greatly appreciated.

Derek

On Tue, Dec 18, 2018 at 11:22 AM Kewin Rausch <krausch at fbk.eu> wrote:

> Can you try using n_prb=25 or 50 and see what happens?
> Srsenb should be tuned with particular configuration for 75 and 100
> resource blocks; I've never been able to use it with wide bw and default
> configuration setup.
>
> Cheers,
> Kewin R.
>
> On Tue, Dec 18, 2018 at 4:52 PM devifr <devifr at gmail.com> wrote:
>
>>
>> Here's the updated log, pcap and conf files.
>>
>> Thanks,
>> Derek
>>  enb (1).log
>> <https://drive.google.com/file/d/1heErabbCYp0dHbq0N1dfZT7rwLEu82M2/view?usp=drive_web>
>>  enb (1).pcap
>> <https://drive.google.com/file/d/1GXSCqd3xN_lpLltWAFXicW4PsK7Ihn42/view?usp=drive_web>
>>  epc (1).log
>> <https://drive.google.com/file/d/1zdgrCn266e9RF7xfjgNhh-Ncj9Iv7jdx/view?usp=drive_web>
>>  epc (1).pcap
>> <https://drive.google.com/file/d/18E0IfucG5-rSPzzn94lqdJsycIdD0gTM/view?usp=drive_web>
>>
>>
>> On Tue, Dec 18, 2018 at 2:36 AM Kewin Rausch <krausch at fbk.eu> wrote:
>>
>>> Hey there,
>>> just a couple of comments.
>>>
>>>    - Log is basically not existing (you are running enb in error level
>>>    Warning, while it should be set to Info or Debug).
>>>    For example, the enb.log file has only two lines!
>>>
>>>    - No configuration of the enb/epc is present, so we can't say how
>>>    you configured it either.
>>>
>>> When you ask for help you should commit to present the more information
>>> possible, not the less. :-)
>>>
>>> Cheers,
>>> Kewin R.
>>>
>>> On Mon, Dec 17, 2018 at 4:19 PM devifr <devifr at gmail.com> wrote:
>>>
>>>> I'm having issues getting with the UE attaching to the ENB.  With
>>>> regards to the ENB, I've used both the USRP Mini B200 as well as the
>>>> BladeRF.  I had another computer running SDRSharp with an Airspy SDR and I
>>>> can confirm that I can see power coming off the ENB.  (NOTE: the BladeRF
>>>> had a much more consistent, solid spike in the RF waterfall versus the
>>>> USRP.  The USRP ebbed and flowed with the "U" trace.)
>>>>
>>>> With regards to the UE's I have a Nexus 5X as well as a Nemo Handy to
>>>> measure drive test data.  Both devices have a programmable SIM with the
>>>> default parameters listed in user_db.csv.
>>>>
>>>> After launching the EPC/ENB, I've ensured that I've ran the
>>>> ./srsepc_if_masq.sh <wireless interface>.  Still...no joy.
>>>>
>>>> I've attached the logs and pcaps.  Any suggestions are greatly
>>>> appreciated.  Thanks.
>>>> _______________________________________________
>>>> srslte-users mailing list
>>>> srslte-users at lists.softwareradiosystems.com
>>>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>>>
>>>
>>> --
>>> Le informazioni contenute nella presente comunicazione sono di natura privata
>>> e come tali sono da considerarsi riservate ed indirizzate esclusivamente
>>> ai destinatari indicati e per le finalità strettamente legate al
>>> relativo contenuto. Se avete ricevuto questo messaggio per errore, vi
>>> preghiamo di eliminarlo e di inviare una comunicazione all’indirizzo
>>> e-mail del mittente.
>>> --
>>> The information transmitted is intended only for the person or entity to
>>> which it is addressed and may contain confidential and/or privileged
>>> material. If you received this in error, please contact the sender and
>>> delete the material.
>>>
>>
> --
> Le informazioni contenute nella presente comunicazione sono di natura privata
> e come tali sono da considerarsi riservate ed indirizzate esclusivamente
> ai destinatari indicati e per le finalità strettamente legate al relativo
> contenuto. Se avete ricevuto questo messaggio per errore, vi preghiamo di
> eliminarlo e di inviare una comunicazione all’indirizzo e-mail del
> mittente.
> --
> The information transmitted is intended only for the person or entity to
> which it is addressed and may contain confidential and/or privileged
> material. If you received this in error, please contact the sender and
> delete the material.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20181218/77e92d5c/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: srslte default sim params V2 18dec2018.PNG
Type: image/png
Size: 236678 bytes
Desc: not available
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20181218/77e92d5c/attachment.png>


More information about the srsran-users mailing list