[srslte-users] UE attached but without IP

Fri Feb 8 12:46:49 UTC 2019

Hi Pedro again,

I have found one option within phone settings to enable/disable the  
VoLTE IMS. Nevertheless, the mobile is still not able to get an IP. I  
attach two new log and pcap files with VoLTE IMS activated and  
deactivated. If you take a look both configurations say at some time  
that there is and integrity failure (Integrity check failure.  
Algorithm=EIA1), and the errors start from that moment. However, if I  
change from EIA1 to EIA2 is still not working?

Any other option to check?

Pedro Alvarez <pedro.alvarez at softwareradiosystems.com> escribió:

> Eduardo,
>
> The problem does not seem to be in the OP/OPc, AMF, etc., since the
> phone accepts the authentication/security-mode-command.
>
> The problem seems to be in the APN settings. You are replying to ESM
> information request with the APN name == "ims".
> Can you try to see why you are sending "ims" as the APN name? Any
> setting on the phone to disable IMS?
>
> You do not need to set apnuser/apnpass.
>
> Regards,
> Pedro
>
> On Thu, Feb 7, 2019 at 12:55 PM Eduardo Garro Crevillen
> <edgarcre at iteam.upv.es> wrote:
>>
>> Hello Pedro,
>>
>> We have checked that the same apn configuration (apn = srsapn) is in
>> both, the epc.conf and in Bittium. We don't know if we need to
>> configure something else, e.g. apnuser/apnpass. Since these fields are
>> not defined in epc.conf, we have left blank in our mobile. May be the
>> problem caused because of a bad USIM <-> user_db.csv configuration? We
>> have been reading previous question were an AMF = 8000 was
>> recommended, but we are using 9001. In addition, another comment was
>> that milenage algorithm is not supported for opc in previous srsLTE
>> releases.
>>
>> Kind regards, Eduardo.
>>
>> PS: In case it helps, we have succusfully connected with a virtual
>> srsUE (ue.conf), but Bittium is not able to connect.
>>
>> Pedro Alvarez <pedro.alvarez at softwareradiosystems.com> escribió:
>>
>>> Can you double check if the APN configuration matches in the EPC  
>>> and the UE?
>>>
>>> On Thu, Feb 7, 2019 at 10:59 AM Eduardo Garro Crevillen
>>> <edgarcre at iteam.upv.es> wrote:
>>>>
>>>>
>>>> Hello everyone,
>>>>
>>>> We have just started trying to implement the srsLTE suite. We are
>>>> using the srsepc, the srsenb which is connected to a USRP B210 and
>>>> a sysmocom USIM inside a Bittium phone as UE. However, although it
>>>> seems that the UE is correctly attached, it does not get any IP
>>>> address. In the attachment you can find the .log and .pcap files.
>>>> Taking a look to the epc.log it seems that there is an error in the
>>>> NAS authentication protocol. We have thought that there was a
>>>> problem with the USIM data. However, we have checked several times
>>>> that the IMSI, OPC and K are correctly included within the
>>>> ue_db.csv. This the included line:
>>>>
>>>> ue4,901700000000004,99728e5d250001ba5f322c82d002db86,opc,b8993ca66ce802c03a2c16d237e90cd1,9001,0000000012fa,7
>>>>
>>>> Maybe there is an error regarding the SQN or the QCI? Since we have
>>>> not found any message on the mailing list archives talking about
>>>> these problem, we kindly ask for your help.
>>>>
>>>> Kind regards, Eduardo
>>>>
>>>> -----------------------------------------
>>>>   Eduardo Garro Crevillén, R&D Engineer
>>>>   Universitat Politècnica de València
>>>>   iTEAM Research Institute
>>>>   Mobile Communications Group
>>>> -----------------------------------------
>>>> _______________________________________________
>>>> srslte-users mailing list
>>>> srslte-users at lists.softwareradiosystems.com
>>>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>
>>
>>
>> -----------------------------------------
>>   Eduardo Garro Crevillén, R&D Engineer
>>   Universitat Politècnica de València
>>   iTEAM Research Institute
>>   Mobile Communications Group
>> -----------------------------------------

-----------------------------------------
   Eduardo Garro Crevillén, R&D Engineer
   Universitat Politècnica de València
   iTEAM Research Institute
   Mobile Communications Group
-----------------------------------------
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: epc_EIA2.log
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20190208/c54b0baa/attachment.ksh>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: epc_EIA2.pcap
Type: application/vnd.tcpdump.pcap
Size: 1810 bytes
Desc: not available
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20190208/c54b0baa/attachment.pcap>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: epc_imsOFF.log
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20190208/c54b0baa/attachment-0001.ksh>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: epc_imsOFF.pcap
Type: application/vnd.tcpdump.pcap
Size: 1427 bytes
Desc: not available
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20190208/c54b0baa/attachment-0001.pcap>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: epc_imsON.log
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20190208/c54b0baa/attachment-0002.ksh>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: epc_imsON.pcap
Type: application/vnd.tcpdump.pcap
Size: 2060 bytes
Desc: not available
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20190208/c54b0baa/attachment-0002.pcap>