• State Not Answered
  • Replies 3 replies
  • Subscribers 74 subscribers
  • Views 1049 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 324865
Options

ESM Reject Cause #32

Gova

Dear team,

I am in Sri Lanka and I got a sim card from Dialog Networks.

The network provider told, they added the APN to my SIM. They also mentioned 140 kbps data limit and network works on B8 band.

They gave me the APN name "nbiot" to get connected to their network.

I programmed the board with AT_CLIENT and 1.3.6 mfw.

I used XSYSTEM mode with 0,1,0,2 expecting the device to work only in NB-IoT.

I used AT+COPS=1,2,"41302" to manually connect to the network, with their MCC-MNC code.

Then I used, AT+CGDCONT=0,"IP","nbiot" to add the APN name before I start the modem.

Below are my logs.

2024-04-05T09:11:19.245Z DEBUG Application data folder: C:\Users\Govardhanan\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2024-04-05T09:11:19.413Z DEBUG App pc-nrfconnect-linkmonitor v2.0.4 local
2024-04-05T09:11:19.413Z DEBUG App path: C:\Users\Govardhanan\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2024-04-05T09:11:19.413Z DEBUG nRFConnect 4.4.1, required by the app is (>=4.0.0)
2024-04-05T09:11:19.413Z DEBUG nRFConnect path: C:\Users\Govardhanan\AppData\Local\Programs\nrfconnect\resources\app.asar
2024-04-05T09:11:19.413Z DEBUG HomeDir: C:\Users\Govardhanan
2024-04-05T09:11:19.414Z DEBUG TmpDir: C:\Users\GOVARD~1\AppData\Local\Temp
2024-04-05T09:11:20.130Z INFO Using nrf-device-lib-js version: 0.6.12
2024-04-05T09:11:20.131Z INFO Using nrf-device-lib version: 0.15.3
2024-04-05T09:11:20.131Z INFO Using nrfjprog DLL version: 10.19.1
2024-04-05T09:11:20.131Z INFO Using JLink version: JLink_V7.88 
2024-04-05T09:11:20.232Z INFO Installed JLink version does not match the provided version (V7.94e)
2024-04-05T09:11:23.590Z INFO Modem port is opened
2024-04-05T09:11:23.612Z DEBUG modem >> AT+CFUN?
2024-04-05T09:11:23.639Z DEBUG modem << +CFUN: 0
2024-04-05T09:11:23.651Z DEBUG modem << OK
2024-04-05T09:11:27.451Z DEBUG modem >> AT
2024-04-05T09:11:27.480Z DEBUG modem << OK
2024-04-05T09:11:28.232Z DEBUG modem >> AT+CFUN?
2024-04-05T09:11:28.265Z DEBUG modem << +CFUN: 0
2024-04-05T09:11:28.291Z DEBUG modem << OK
2024-04-05T09:11:31.297Z DEBUG modem >> AT+CEREG=5
2024-04-05T09:11:31.330Z DEBUG modem << OK
2024-04-05T09:11:32.363Z DEBUG modem >> AT%XEPCO=0
2024-04-05T09:11:32.391Z DEBUG modem << OK
2024-04-05T09:11:42.024Z DEBUG modem >> AT+CNEC=24
2024-04-05T09:11:42.049Z DEBUG modem << OK
2024-04-05T09:11:47.302Z DEBUG modem >> AT%MDMEV=1
2024-04-05T09:11:47.319Z DEBUG modem << OK
2024-04-05T09:11:58.115Z DEBUG modem >> AT+COPS=1,2,"41302"
2024-04-05T09:11:58.145Z DEBUG modem << OK
2024-04-05T09:12:01.903Z DEBUG modem >> AT%XSYSTEMMODE=0,1,0,2
2024-04-05T09:12:01.930Z DEBUG modem << OK
2024-04-05T09:13:36.596Z DEBUG modem >> AT+CGDCONT=0,"IP","nbiot"
2024-04-05T09:13:36.618Z DEBUG modem << OK
2024-04-05T09:16:29.575Z DEBUG modem >> AT+CFUN=1
2024-04-05T09:16:29.633Z DEBUG modem << OK
2024-04-05T09:16:30.526Z DEBUG modem >> AT+CFUN?
2024-04-05T09:16:30.562Z DEBUG modem << +CFUN: 1
2024-04-05T09:16:30.626Z DEBUG modem << OK
2024-04-05T09:16:30.660Z DEBUG modem >> AT+CGSN=1
2024-04-05T09:16:30.690Z DEBUG modem << +CGSN: "350457794434702"
2024-04-05T09:16:30.703Z DEBUG modem << OK
2024-04-05T09:16:30.729Z DEBUG modem >> AT+CGMI
2024-04-05T09:16:30.784Z DEBUG modem << Nordic Semiconductor ASA
2024-04-05T09:16:30.795Z DEBUG modem << OK
2024-04-05T09:16:30.827Z DEBUG modem >> AT+CGMM
2024-04-05T09:16:30.850Z DEBUG modem << nRF9160-SICA
2024-04-05T09:16:30.861Z DEBUG modem << OK
2024-04-05T09:16:30.886Z DEBUG modem >> AT+CGMR
2024-04-05T09:16:30.914Z DEBUG modem << mfw_nrf9160_1.3.6
2024-04-05T09:16:30.929Z DEBUG modem << OK
2024-04-05T09:16:30.941Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.6] SerNr: 350457794434702
2024-04-05T09:16:30.958Z DEBUG modem >> AT+CEMODE?
2024-04-05T09:16:30.999Z DEBUG modem << +CEMODE: 0
2024-04-05T09:16:31.023Z DEBUG modem << OK
2024-04-05T09:16:31.064Z DEBUG modem >> AT%XCBAND=?
2024-04-05T09:16:31.118Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66)
2024-04-05T09:16:31.127Z DEBUG modem << OK
2024-04-05T09:16:31.153Z DEBUG modem >> AT+CMEE?
2024-04-05T09:16:31.185Z DEBUG modem << +CMEE: 0
2024-04-05T09:16:31.208Z DEBUG modem << OK
2024-04-05T09:16:31.231Z DEBUG modem >> AT+CMEE=1
2024-04-05T09:16:31.259Z DEBUG modem << OK
2024-04-05T09:16:31.311Z DEBUG modem >> AT+CNEC?
2024-04-05T09:16:31.348Z DEBUG modem << +CNEC: 24
2024-04-05T09:16:31.371Z DEBUG modem << OK
2024-04-05T09:16:31.397Z DEBUG modem >> AT+CGEREP?
2024-04-05T09:16:31.449Z DEBUG modem << +CGEREP: 0,0
2024-04-05T09:16:31.460Z DEBUG modem << OK
2024-04-05T09:16:31.474Z DEBUG modem >> AT+CGDCONT?
2024-04-05T09:16:31.511Z DEBUG modem << +CGDCONT: 0,"IP","nbiot","",0,0
2024-04-05T09:16:31.520Z DEBUG modem << OK
2024-04-05T09:16:31.561Z DEBUG modem >> AT+CGACT?
2024-04-05T09:16:31.590Z DEBUG modem << +CGACT: 0,0
2024-04-05T09:16:31.603Z DEBUG modem << OK
2024-04-05T09:16:31.638Z DEBUG modem >> AT+CGEREP=1
2024-04-05T09:16:31.676Z DEBUG modem << OK
2024-04-05T09:16:31.708Z DEBUG modem >> AT+CIND=1,1,1
2024-04-05T09:16:31.733Z DEBUG modem << OK
2024-04-05T09:16:31.759Z DEBUG modem >> AT+CEREG=5
2024-04-05T09:16:31.795Z DEBUG modem << OK
2024-04-05T09:16:31.834Z DEBUG modem >> AT+CEREG?
2024-04-05T09:16:31.863Z DEBUG modem << +CEREG: 5,4
2024-04-05T09:16:31.881Z DEBUG modem << OK
2024-04-05T09:16:31.927Z DEBUG modem >> AT%CESQ=1
2024-04-05T09:16:31.958Z DEBUG modem << OK
2024-04-05T09:16:32.005Z DEBUG modem >> AT+CESQ
2024-04-05T09:16:32.034Z DEBUG modem << +CESQ: 99,99,255,255,255,255
2024-04-05T09:16:32.046Z DEBUG modem << OK
2024-04-05T09:16:32.083Z DEBUG modem >> AT%XSIM=1
2024-04-05T09:16:32.119Z DEBUG modem << OK
2024-04-05T09:16:32.165Z DEBUG modem >> AT%XSIM?
2024-04-05T09:16:32.208Z DEBUG modem << %XSIM: 1
2024-04-05T09:16:32.231Z DEBUG modem << OK
2024-04-05T09:16:32.274Z DEBUG modem >> AT+CPIN?
2024-04-05T09:16:32.319Z DEBUG modem << +CPIN: READY
2024-04-05T09:16:32.348Z DEBUG modem << OK
2024-04-05T09:16:32.391Z DEBUG modem >> AT+CPINR="SIM PIN"
2024-04-05T09:16:32.485Z DEBUG modem << +CPINR: "SIM PIN",5
2024-04-05T09:16:32.495Z DEBUG modem << OK
2024-04-05T09:16:32.539Z DEBUG modem >> AT+CIMI
2024-04-05T09:16:32.572Z DEBUG modem << 413027067631713
2024-04-05T09:16:32.584Z DEBUG modem << OK
2024-04-05T09:16:32.592Z INFO IMSIdentity: 413027067631713
2024-04-05T09:16:46.344Z DEBUG modem << %CESQ: 66,3,29,4
2024-04-05T09:16:46.368Z DEBUG modem << +CEREG: 2,"3A99","00543565",9
2024-04-05T09:16:46.558Z DEBUG modem << %CESQ: 64,3,23,3
2024-04-05T09:16:47.907Z DEBUG modem << %CESQ: 63,3,28,4
2024-04-05T09:16:48.700Z DEBUG modem << +CNEC_ESM: 32,0
2024-04-05T09:16:48.799Z DEBUG modem << +CNEC_EMM: 19
2024-04-05T09:16:48.900Z DEBUG modem << %MDMEV: SEARCH STATUS 2
2024-04-05T09:16:48.936Z DEBUG modem << +CEREG: 2,"3A99","00543565",9,0,19
2024-04-05T09:16:49.005Z DEBUG modem << %CESQ: 68,3,24,3
2024-04-05T09:16:51.598Z DEBUG modem << %CESQ: 68,3,18,2

I am facing issue with ESM Error code #32, which translates to "Service option not supported". The description for it reads "This ESM cause is used by the network when the UE requests a service which is not supported by the PLMN."

What am I missing? or is it with the operator?

Can we do anything from the device end, before we turn on the modem, for a successful registration?

Does it have anything to do with the APN name? Because, i was able to read in other questions that, ESM error code #33 means SIM was not registered to access that APN. 

Please advise.

With tons of thanks in advance,

Gova

Parents
  • 0

    Hello Gova, 

    Are you able to provide a modem trace? Did you try connecting using the PDN library? Will need more information in order to discuss with our cellular team. 

    Thanks! 

    Kind regards,
    Øyvind

  • 0 in reply to Øyvind

    Hello Oyvind,

    Thanks for your reply.

    I used the PDN sample,and made the following changes to the proj.conf file, to match my requirements.

    CONFIG_NRF_MODEM_LIB_TRACE=y
    CONFIG_LTE_NETWORK_MODE_NBIOT=y
    CONFIG_PDN_DEFAULTS_OVERRIDE=y
    CONFIG_PDN_DEFAULT_APN="nbiot"
    CONFIG_PDN_DEFAULT_FAM_IPV4=y
    I got the following output in terminal.

    Also, here is the modem trace file.
    Firstly, I dont know if i have configured the PDN sample properly for my requirement and used it.
    Because, with cellular monitor, I was able to see that, ESM Cause #111 was received.
    Also, inspite of having CONFIG_LTE_NETWORK_MODE_NBIOT = y, why was AT%XSYSMODE=1,1,1,3 was sent to the modem? 
    I still made a pristine build, before proramming it.
    Your help is much appreciated.
    Thanks,
    Gova.
  • 0 in reply to Gova

    Hi Gova, thanks for providing the logs. Are you sure you need the PDN information? Are you able to connect without adding this? 

    From the logs I see that you get reject cause EMM 15 and ESM 111, which from 3GPP TS 24.301 Annex A (EMM) and B (ESM) translates to

    Cause #15 – No suitable cells in tracking area
    This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking
    area where the UE, by subscription, is not allowed to operate, but when it should find another allowed tracking
    area or location area in the same PLMN or an equivalent PLMN.
    NOTE 3: Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the UE to search for another
    allowed tracking area on the same PLMN.

    Cause #111 – Protocol error, unspecified
    This ESM cause is used to report a protocol error event only when no other ESM cause in the protocol error class
    applies.

    Did you contact the network provider with this information?

    Cause #32 – Service option not supported
    This ESM cause is used by the network when the UE requests a service which is not supported by the PLMN.

    Kind regards,
    Øyvind

Reply
  • 0 in reply to Gova

    Hi Gova, thanks for providing the logs. Are you sure you need the PDN information? Are you able to connect without adding this? 

    From the logs I see that you get reject cause EMM 15 and ESM 111, which from 3GPP TS 24.301 Annex A (EMM) and B (ESM) translates to

    Cause #15 – No suitable cells in tracking area
    This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking
    area where the UE, by subscription, is not allowed to operate, but when it should find another allowed tracking
    area or location area in the same PLMN or an equivalent PLMN.
    NOTE 3: Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the UE to search for another
    allowed tracking area on the same PLMN.

    Cause #111 – Protocol error, unspecified
    This ESM cause is used to report a protocol error event only when no other ESM cause in the protocol error class
    applies.

    Did you contact the network provider with this information?

    Cause #32 – Service option not supported
    This ESM cause is used by the network when the UE requests a service which is not supported by the PLMN.

    Kind regards,
    Øyvind

Children
No Data
Related
Terms of service