[srslte-users] srsEPC: UE unable to register on network

[Pedro Alvarez]

Hum... I haven't seen this issue before...
The fact that it's working with the Galaxy (and the phones I test
with) is making me think that it may not be an issue with the COUNT
but some other field in the protocol that is incorrect.

The only obvious mistake I found so far is that the protocol
discriminator on the ESM Information transfer seems wrong.
Could you try the following:

"""
diff --git a/lib/src/asn1/liblte_mme.cc b/lib/src/asn1/liblte_mme.cc
index 6d9dedc..523f921 100644
--- a/lib/src/asn1/liblte_mme.cc
+++ b/lib/src/asn1/liblte_mme.cc
@@ -9943,7 +9943,7 @@ LIBLTE_ERROR_ENUM
srslte_mme_pack_esm_information_request_msg(LIBLTE_MME_ESM_INF
        if(LIBLTE_MME_SECURITY_HDR_TYPE_PLAIN_NAS != sec_hdr_type)
        {
            // Protocol Discriminator and Security Header Type
-           *msg_ptr = (sec_hdr_type << 4) |
(LIBLTE_MME_PD_EPS_SESSION_MANAGEMENT);
+         *msg_ptr = (sec_hdr_type << 4) |
(LIBLTE_MME_PD_EPS_MOBILITY_MANAGEMENT);
            msg_ptr++;

            // MAC will be filled in later
"""

Let me know if that worked for you.

Cheers,
Pedro

On Wed, Jun 13, 2018 at 2:29 PM, Ignas Jarusevicius
<i.jarusevicius at limemicro.com> wrote:
> Hello Pedro,
>
> I was using Sony Xperia F3111. I have just tried it with Samsung Galaxy
> S5 and it registered successfully. I had to manually run if_masq.sh to
> get the Internet access on the phone but I guess it is how it is
> supposed to work.
>
> Would it be possible to make srsepc also work with Sony phone?
>
> Regards,
> Ignas
>
>
> On 2018.06.13 15:54, Pedro Alvarez wrote:
>> It seems like the UE does not like message authentication code of the
>> ESM information transfer. This is probably related to the downlink NAS
>> COUNT.
>>
>> Which phone are you using?
>>
>> Regards,
>> Pedro
>>
>> On Wed, Jun 13, 2018 at 7:57 AM, Ignas Jarusevicius
>> <i.jarusevicius at limemicro.com> wrote:
>>> Hi Pedro,
>>>
>>> Thank you for looking into this. I attached enb.pcab together with
>>> enb.log and epc.log from the same run.
>>> The APN settings on the phone are:
>>>
>>> APN: srsapn
>>> Proxy: not set
>>> Port: not set
>>> Username: not set
>>> Password: not set
>>> Server: not set
>>> MMSC: not set
>>> MMS proxy: not set
>>> MCC: 001
>>> MNC: 01
>>> Authentication type: none
>>> APN type: default
>>> APN protocol: IPv4
>>> APN roaming protocol IPv4
>>> Bearer: 4G
>>> MVNO type: none
>>>
>>> I have tried changing APN in epc.conf and on the phone but result was
>>> the same.
>>>
>>> Regards,
>>> Ignas
>>>
>>>
>>> On 2018.06.12 21:55, Pedro Alvarez wrote:
>>>> Hi Ignas,
>>>>
>>>> The authentication and the security mode command seem to have worked
>>>> fine and it seems to be breaking on the ESM information transfer. Did
>>>> you set any APN on the phone?
>>>>
>>>> Can you send the enb.pcap so I can have a bit more information? You
>>>> can enable it on the in the enb.conf.
>>>>
>>>> Regards,
>>>> Pedro
>>>>
>>>> On Tue, Jun 12, 2018 at 11:49 AM, Ignas Jarusevicius
>>>> <i.jarusevicius at limemicro.com> wrote:
>>>>> Hello All,
>>>>>
>>>>> I am trying to set up srsENB and srsEPC with commercial UE. When UE
>>>>> attempts to connect to the network, I get "UE Authentication Accepted"
>>>>> message in srsEPC, but UE fails to register on the network. ENB and EPC
>>>>> logs are attached.
>>>>> UE registers successfully when srsENB is used with EPC from Amarisoft so
>>>>> I think the problem is with srsEPC. Am I missing something in srsEPC
>>>>> configuration or is it some limitation of srsEPC? Any help would be
>>>>> appreciated.
>>>>>
>>>>> Regards,
>>>>> Ignas
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> srslte-users mailing list
>>>>> srslte-users at lists.softwareradiosystems.com
>>>>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>>>>
>
>