Operator (TURKCELL) connection problem (AT+COPS=0) with nRF9160-DK

Hi,
I'm Bunyamin from Turkey. I've obtained an nRF9160-DK and inserted a TURKCELL M2M SIM card.
1- I installed modem firmware mfw_nrf9160_1.3.3
2- I flashed nrf9160dk_asset_tracker_v2_ltem_2022-06-02_880c82db.hex (or nrf9160dk_asset_tracker_v2_nbiot_2022-06-02_880c82db.hex , I get the same result)
3- I connected to nRF9160-DK with LTE Link Monitor
4- I sent the AT commands below:
->> AT+CFUN=0
->> AT+CEREG=5
->> AT+CSCON=3
->> AT%XEPCO=0
->> AT%XSYSTEMMODE=0,1,1,0
->> AT+CGDCONT= 0,"IP","nbiot"
->> AT%XSYSTEMMODE=0,1,1,0
->> AT+CFUN=1
->> AT+CFUN?
5- After these commands, I receive the log below:

2023-01-06T09:15:08.639Z DEBUG Application data folder: C:\Users\bunya\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2023-01-06T09:15:08.753Z INFO Using nrf-device-lib-js version: 0.4.13
2023-01-06T09:15:08.754Z INFO Using nrf-device-lib version: 0.12.8
2023-01-06T09:15:08.754Z INFO Using nrfjprog DLL version: 10.16.0
2023-01-06T09:15:08.754Z INFO Using JLink version: JLink_V7.66a
2023-01-06T09:15:08.811Z DEBUG App pc-nrfconnect-linkmonitor v2.0.2 official
2023-01-06T09:15:08.812Z DEBUG App path: C:\Users\bunya\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2023-01-06T09:15:08.812Z DEBUG nRFConnect 3.12.0, required by the app is (^3.12.0)
2023-01-06T09:15:08.812Z DEBUG nRFConnect path: C:\Users\bunya\AppData\Local\Programs\nrfconnect\resources\app.asar
2023-01-06T09:15:08.812Z DEBUG HomeDir: C:\Users\bunya
2023-01-06T09:15:08.812Z DEBUG TmpDir: C:\Users\bunya\AppData\Local\Temp
2023-01-06T09:15:11.022Z INFO Modem port is opened
2023-01-06T09:15:11.043Z DEBUG modem >> AT+CFUN?
2023-01-06T09:15:11.070Z DEBUG modem << +CFUN: 1
2023-01-06T09:15:11.081Z DEBUG modem << OK
2023-01-06T09:15:11.104Z DEBUG modem >> AT+CGSN=1
2023-01-06T09:15:11.115Z DEBUG modem << +CGSN: "351358811475372"
2023-01-06T09:15:11.119Z DEBUG modem << OK
2023-01-06T09:15:11.134Z DEBUG modem >> AT+CGMI
2023-01-06T09:15:11.149Z DEBUG modem << Nordic Semiconductor ASA
2023-01-06T09:15:11.153Z DEBUG modem << OK
2023-01-06T09:15:11.158Z DEBUG modem >> AT+CGMM
2023-01-06T09:15:11.169Z DEBUG modem << nRF9160-SICA
2023-01-06T09:15:11.173Z DEBUG modem << 
2023-01-06T09:15:11.176Z DEBUG modem << OK
2023-01-06T09:15:11.185Z DEBUG modem >> AT+CGMR
2023-01-06T09:15:11.198Z DEBUG modem << mfw_nrf9160_1.3.3
2023-01-06T09:15:11.201Z DEBUG modem << OK
2023-01-06T09:15:11.203Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.3] SerNr: 351358811475372
2023-01-06T09:15:11.205Z DEBUG modem >> AT+CEMODE?
2023-01-06T09:15:11.215Z DEBUG modem << +CEMODE: 2
2023-01-06T09:15:11.219Z DEBUG modem << OK
2023-01-06T09:15:11.237Z DEBUG modem >> AT%XCBAND=?
2023-01-06T09:15:11.257Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)
2023-01-06T09:15:11.264Z DEBUG modem << OK
2023-01-06T09:15:11.281Z DEBUG modem >> AT+CMEE?
2023-01-06T09:15:11.287Z DEBUG modem << +CMEE: 0
2023-01-06T09:15:11.289Z DEBUG modem << OK
2023-01-06T09:15:11.300Z DEBUG modem >> AT+CMEE=1
2023-01-06T09:15:11.305Z DEBUG modem << OK
2023-01-06T09:15:11.316Z DEBUG modem >> AT+CNEC?
2023-01-06T09:15:11.322Z DEBUG modem << +CNEC: 0
2023-01-06T09:15:11.324Z DEBUG modem << 
2023-01-06T09:15:11.330Z DEBUG modem << OK
2023-01-06T09:15:11.335Z DEBUG modem >> AT+CNEC=24
2023-01-06T09:15:11.341Z DEBUG modem << OK
2023-01-06T09:15:11.350Z DEBUG modem >> AT+CGEREP?
2023-01-06T09:15:11.355Z DEBUG modem << +CGEREP: 0,0
2023-01-06T09:15:11.365Z DEBUG modem << OK
2023-01-06T09:15:11.372Z DEBUG modem >> AT+CGDCONT?
2023-01-06T09:15:11.381Z DEBUG modem << OK
2023-01-06T09:15:11.385Z DEBUG modem >> AT+CGACT?
2023-01-06T09:15:11.390Z DEBUG modem << OK
2023-01-06T09:15:11.398Z DEBUG modem >> AT+CGEREP=1
2023-01-06T09:15:11.403Z DEBUG modem << OK
2023-01-06T09:15:11.406Z DEBUG modem >> AT+CIND=1,1,1
2023-01-06T09:15:11.415Z DEBUG modem << OK
2023-01-06T09:15:11.420Z DEBUG modem >> AT+CEREG=5
2023-01-06T09:15:11.432Z DEBUG modem << OK
2023-01-06T09:15:11.435Z DEBUG modem >> AT+CEREG?
2023-01-06T09:15:11.440Z DEBUG modem << +CEREG: 5,4
2023-01-06T09:15:11.451Z DEBUG modem << OK
2023-01-06T09:15:11.467Z DEBUG modem >> AT%CESQ=1
2023-01-06T09:15:11.472Z DEBUG modem << OK
2023-01-06T09:15:11.481Z DEBUG modem >> AT+CESQ
2023-01-06T09:15:11.487Z DEBUG modem << +CESQ: 99,99,255,255,255,255
2023-01-06T09:15:11.490Z DEBUG modem << OK
2023-01-06T09:15:11.506Z DEBUG modem >> AT%XSIM=1
2023-01-06T09:15:11.515Z DEBUG modem << OK
2023-01-06T09:15:11.519Z DEBUG modem >> AT%XSIM?
2023-01-06T09:15:11.524Z DEBUG modem << %XSIM: 1
2023-01-06T09:15:11.532Z DEBUG modem << OK
2023-01-06T09:15:11.541Z DEBUG modem >> AT+CPIN?
2023-01-06T09:15:11.550Z DEBUG modem << +CPIN: READY
2023-01-06T09:15:11.552Z DEBUG modem << OK
2023-01-06T09:15:11.565Z DEBUG modem >> AT+CPINR="SIM PIN"
2023-01-06T09:15:11.583Z DEBUG modem << +CPINR: "SIM PIN",3
2023-01-06T09:15:11.585Z DEBUG modem << OK
2023-01-06T09:15:11.601Z DEBUG modem >> AT+CIMI
2023-01-06T09:15:11.607Z DEBUG modem << 286016329698669
2023-01-06T09:15:11.616Z DEBUG modem << OK
2023-01-06T09:15:11.619Z INFO IMSIdentity: 286016329698669
2023-01-06T09:15:25.369Z DEBUG modem >> AT+CFUN=0
2023-01-06T09:15:25.376Z DEBUG modem << %MDMEV: SEARCH STATUS 2
2023-01-06T09:15:25.380Z DEBUG modem << +CEREG: 0
2023-01-06T09:15:25.396Z DEBUG modem << %XSIM: 0
2023-01-06T09:15:25.476Z DEBUG modem << OK
2023-01-06T09:15:26.385Z DEBUG modem << [00:00:24.421,386] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2023-01-06T09:15:35.136Z DEBUG modem >> AT+CEREG=5
2023-01-06T09:15:35.150Z DEBUG modem << OK
2023-01-06T09:15:40.872Z DEBUG modem >> AT+CSCON=3
2023-01-06T09:15:40.886Z DEBUG modem << OK
2023-01-06T09:15:46.448Z DEBUG modem >> AT%XEPCO=0
2023-01-06T09:15:46.462Z DEBUG modem << OK
2023-01-06T09:15:55.968Z DEBUG modem >> AT%XSYSTEMMODE=0,1,1,0
2023-01-06T09:15:55.984Z DEBUG modem << OK
2023-01-06T09:16:02.160Z DEBUG modem >> AT+CGDCONT= 0,"IP","nbiot"
2023-01-06T09:16:02.176Z DEBUG modem << OK
2023-01-06T09:16:07.960Z DEBUG modem >> AT%XSYSTEMMODE=0,1,1,0
2023-01-06T09:16:07.977Z DEBUG modem << OK
2023-01-06T09:16:09.637Z DEBUG modem >> AT+CFUN=1
2023-01-06T09:16:09.679Z DEBUG modem << OK
2023-01-06T09:16:10.100Z DEBUG modem >> AT+CFUN?
2023-01-06T09:16:10.105Z DEBUG modem << +CFUN: 1
2023-01-06T09:16:10.114Z DEBUG modem << OK
2023-01-06T09:16:10.119Z DEBUG modem >> AT+CGSN=1
2023-01-06T09:16:10.131Z DEBUG modem << +CGSN: "351358811475372"
2023-01-06T09:16:10.135Z DEBUG modem << OK
2023-01-06T09:16:10.141Z DEBUG modem >> AT+CGMI
2023-01-06T09:16:10.150Z DEBUG modem << Nordic Semiconductor ASA
2023-01-06T09:16:10.152Z DEBUG modem << OK
2023-01-06T09:16:10.156Z DEBUG modem >> AT+CGMM
2023-01-06T09:16:10.167Z DEBUG modem << nRF9160-SICA
2023-01-06T09:16:10.169Z DEBUG modem << OK
2023-01-06T09:16:10.173Z DEBUG modem >> AT+CGMR
2023-01-06T09:16:10.183Z DEBUG modem << mfw_nrf9160_1.3.3
2023-01-06T09:16:10.185Z DEBUG modem << OK
2023-01-06T09:16:10.188Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.3] SerNr: 351358811475372
2023-01-06T09:16:10.189Z DEBUG modem >> AT+CEMODE?
2023-01-06T09:16:10.200Z DEBUG modem << +CEMODE: 0
2023-01-06T09:16:10.203Z DEBUG modem << OK
2023-01-06T09:16:10.217Z DEBUG modem >> AT%XCBAND=?
2023-01-06T09:16:10.233Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66)
2023-01-06T09:16:10.236Z DEBUG modem << OK
2023-01-06T09:16:10.249Z DEBUG modem >> AT+CMEE?
2023-01-06T09:16:10.265Z DEBUG modem << +CMEE: 0
2023-01-06T09:16:10.268Z DEBUG modem << OK
2023-01-06T09:16:10.271Z DEBUG modem >> AT+CMEE=1
2023-01-06T09:16:10.276Z DEBUG modem << OK
2023-01-06T09:16:10.285Z DEBUG modem >> AT+CNEC?
2023-01-06T09:16:10.290Z DEBUG modem << +CNEC: 0
2023-01-06T09:16:10.292Z DEBUG modem << OK
2023-01-06T09:16:10.301Z DEBUG modem >> AT+CNEC=24
2023-01-06T09:16:10.307Z DEBUG modem << OK
2023-01-06T09:16:10.310Z DEBUG modem >> AT+CGEREP?
2023-01-06T09:16:10.319Z DEBUG modem << +CGEREP: 0,0
2023-01-06T09:16:10.323Z DEBUG modem << OK
2023-01-06T09:16:10.326Z DEBUG modem >> AT+CGDCONT?
2023-01-06T09:16:10.338Z DEBUG modem << +CGDCONT: 0,"IP","nbiot","",0,0
2023-01-06T09:16:10.341Z DEBUG modem << OK
2023-01-06T09:16:10.357Z DEBUG modem >> AT+CGACT?
2023-01-06T09:16:10.367Z DEBUG modem << +CGACT: 0,0
2023-01-06T09:16:10.370Z DEBUG modem << OK
2023-01-06T09:16:10.382Z DEBUG modem >> AT+CGEREP=1
2023-01-06T09:16:10.388Z DEBUG modem << OK
2023-01-06T09:16:10.392Z DEBUG modem >> AT+CIND=1,1,1
2023-01-06T09:16:10.400Z DEBUG modem << OK
2023-01-06T09:16:10.406Z DEBUG modem >> AT+CEREG=5
2023-01-06T09:16:10.426Z DEBUG modem << OK
2023-01-06T09:16:10.440Z DEBUG modem >> AT+CEREG?
2023-01-06T09:16:10.454Z DEBUG modem << +CEREG: 5,4
2023-01-06T09:16:10.456Z DEBUG modem << OK
2023-01-06T09:16:10.471Z DEBUG modem >> AT%CESQ=1
2023-01-06T09:16:10.483Z DEBUG modem << OK
2023-01-06T09:16:10.488Z DEBUG modem >> AT+CESQ
2023-01-06T09:16:10.500Z DEBUG modem << +CESQ: 99,99,255,255,255,255
2023-01-06T09:16:10.502Z DEBUG modem << OK
2023-01-06T09:16:10.508Z DEBUG modem >> AT%XSIM=1
2023-01-06T09:16:10.517Z DEBUG modem << OK
2023-01-06T09:16:10.521Z DEBUG modem >> AT%XSIM?
2023-01-06T09:16:10.525Z DEBUG modem << %XSIM: 1
2023-01-06T09:16:10.536Z DEBUG modem << OK
2023-01-06T09:16:10.553Z DEBUG modem >> AT+CPIN?
2023-01-06T09:16:10.558Z DEBUG modem << +CPIN: READY
2023-01-06T09:16:10.568Z DEBUG modem << OK
2023-01-06T09:16:10.575Z DEBUG modem >> AT+CPINR="SIM PIN"
2023-01-06T09:16:10.588Z DEBUG modem << +CPINR: "SIM PIN",3
2023-01-06T09:16:10.589Z DEBUG modem << OK
2023-01-06T09:16:10.603Z DEBUG modem >> AT+CIMI
2023-01-06T09:16:10.609Z DEBUG modem << 286016329698669
2023-01-06T09:16:10.617Z DEBUG modem << OK
2023-01-06T09:16:10.619Z INFO IMSIdentity: 286016329698669
2023-01-06T09:16:28.435Z DEBUG modem << %CESQ: 22,1,14,2
2023-01-06T09:16:28.447Z DEBUG modem << +CEREG: 2,"1600","0042DC67",9
2023-01-06T09:16:28.960Z DEBUG modem << +CSCON: 1,7,4
2023-01-06T09:16:29.445Z DEBUG modem << [00:01:27.484,741] [0m<inf> app_event_manager: MODEM_EVT_LTE_DISCONNECTED[0m
2023-01-06T09:16:29.452Z DEBUG modem << [00:01:27.485,382] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2023-01-06T09:16:29.784Z DEBUG modem << %CESQ: 26,1,9,1
2023-01-06T09:16:30.723Z DEBUG modem << +CNEC_EMM: 15
2023-01-06T09:16:30.730Z DEBUG modem << +CEREG: 2,"1600","0042DC67",9,0,15
2023-01-06T09:16:30.789Z DEBUG modem << +CSCON: 0,7,4
2023-01-06T09:16:31.459Z DEBUG modem << %CESQ: 255,0,255,0
2023-01-06T09:16:31.465Z DEBUG modem << +CEREG: 2
2023-01-06T09:16:32.468Z DEBUG modem << [00:01:30.507,293] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2023-01-06T09:16:47.065Z DEBUG modem >> AT+COPS=?
2023-01-06T09:17:02.731Z DEBUG modem << %CESQ: 18,0,17,2
2023-01-06T09:17:02.734Z DEBUG modem << +CEREG: 2,"C246","00E54E16",9
2023-01-06T09:17:03.482Z DEBUG modem << [00:02:01.523,956] [0m<inf> app_event_manager: APP_EVT_DATA_GET_ALL[0m
2023-01-06T09:17:03.494Z DEBUG modem << [00:02:01.524,627] [0m<inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, MOD_STAT)[0m
2023-01-06T09:17:03.504Z DEBUG modem << [00:02:01.525,360] [0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
2023-01-06T09:17:03.510Z DEBUG modem << [00:02:01.782,775] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2023-01-06T09:17:04.707Z DEBUG modem << +CSCON: 1,7,4
2023-01-06T09:17:05.177Z DEBUG modem << +CNEC_EMM: 14
2023-01-06T09:17:05.183Z DEBUG modem << +CEREG: 2,"C246","00E54E16",9,0,14
2023-01-06T09:17:05.314Z DEBUG modem << +CSCON: 0,7,4
2023-01-06T09:17:05.484Z DEBUG modem << [00:02:03.525,848] [0m<inf> app_event_manager: DATA_EVT_DATA_READY[0m
2023-01-06T09:17:05.633Z DEBUG modem << %CESQ: 255,0,255,0
2023-01-06T09:17:06.140Z DEBUG modem << %CESQ: 66,3,26,3
2023-01-06T09:17:06.142Z DEBUG modem << +CEREG: 2
2023-01-06T09:17:07.148Z DEBUG modem << [00:02:05.189,697] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2023-01-06T09:19:03.474Z DEBUG modem << [00:04:01.523,956] [0m<inf> app_event_manager: APP_EVT_DATA_GET_ALL[0m
2023-01-06T09:19:03.486Z DEBUG modem << [00:04:01.524,597] [0m<inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS)[0m
2023-01-06T09:19:03.493Z DEBUG modem << [00:04:01.525,268] [0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
2023-01-06T09:19:05.475Z DEBUG modem << [00:04:03.525,756] [0m<inf> app_event_manager: DATA_EVT_DATA_READY[0m
2023-01-06T09:21:03.467Z DEBUG modem << [00:06:01.523,956] [0m<inf> app_event_manager: APP_EVT_DATA_GET_ALL[0m
2023-01-06T09:21:03.478Z DEBUG modem << [00:06:01.524,597] [0m<inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, GNSS)[0m
2023-01-06T09:21:03.480Z DEBUG modem << 
2023-01-06T09:21:03.489Z DEBUG modem << [00:06:01.530,883] [0m<inf> app_event_manager: GNSS_EVT_ACTIVE[0m
2023-01-06T09:21:03.492Z DEBUG modem << [00:06:01.531,341] [0m<inf> app_event_manager: GNSS_EVT_AGPS_NEEDED[0m
2023-01-06T09:21:03.506Z DEBUG modem << [00:06:01.531,921] [0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
2023-01-06T09:21:03.509Z DEBUG modem << [00:06:01.532,318] [1;33m<wrn> data_module: Failed to request A-GPS data, error: -13[0m
2023-01-06T09:21:03.523Z DEBUG modem << [00:06:01.532,318] [1;33m<wrn> data_module: This is expected to fail if we are not in a connected state[0m
2023-01-06T09:21:53.622Z DEBUG modem << +COPS: (1,"","","28601",9),(3,"","","28602",9)
2023-01-06T09:21:53.625Z DEBUG modem << OK
2023-01-06T09:21:53.633Z DEBUG modem >> AT+COPS?
2023-01-06T09:21:53.642Z DEBUG modem << +COPS: 0
2023-01-06T09:21:53.645Z DEBUG modem << OK
2023-01-06T09:21:53.676Z DEBUG modem << [00:06:52.691,772] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2023-01-06T09:21:53.681Z DEBUG modem << [00:06:52.696,166] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2023-01-06T09:21:53.683Z DEBUG modem << [00:06:52.696,228] [1;31m<err> modem_info_params: Network data not obtained: -27[0m
2023-01-06T09:21:53.684Z DEBUG modem << [00:06:52.696,228] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2023-01-06T09:21:53.712Z DEBUG modem << [00:06:52.696,289] [0m<inf> app_event_manager: MODEM_EVT_MODEM_STATIC_DATA_NOT_READY[0m
2023-01-06T09:21:53.716Z DEBUG modem << [00:06:52.699,829] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2023-01-06T09:21:53.728Z DEBUG modem << [00:06:52.706,359] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2023-01-06T09:21:53.730Z DEBUG modem << [00:06:52.706,390] [1;31m<err> modem_info_params: Network data not obtained: -27[0m
2023-01-06T09:21:53.732Z DEBUG modem << [00:06:52.706,420] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2023-01-06T09:21:53.733Z DEBUG modem << [00:06:52.706,481] [0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m
2023-01-06T09:21:53.746Z DEBUG modem << [00:06:52.710,021] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2023-01-06T09:21:53.793Z DEBUG modem << %NCELLMEAS: 0,"0F2F5965","28601","1600",65535,6446,213,66,21,412360,6446,101,58,10,0,6446,108,55,3,0,0
2023-01-06T09:21:53.811Z DEBUG modem << [00:06:52.797,973] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2023-01-06T09:21:53.826Z DEBUG modem << [00:06:52.798,034] [1;31m<err> modem_info_params: Network data not obtained: -27[0m
2023-01-06T09:21:53.829Z DEBUG modem << [00:06:52.798,034] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2023-01-06T09:21:53.833Z DEBUG modem << [00:06:52.798,126] [0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY[0m
2023-01-06T09:21:53.848Z DEBUG modem << [00:06:52.860,748] [0m<inf> app_event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2023-01-06T09:21:53.850Z DEBUG modem << [00:06:52.863,891] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2023-01-06T09:21:53.865Z DEBUG modem << [00:06:52.868,255] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2023-01-06T09:21:53.879Z DEBUG modem << [00:06:52.868,286] [1;31m<err> modem_info_params: Network data not obtained: -27[0m
2023-01-06T09:21:53.882Z DEBUG modem << [00:06:52.868,316] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2023-01-06T09:21:53.884Z DEBUG modem << [00:06:52.868,377] [0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m
2023-01-06T09:21:53.897Z DEBUG modem << [00:06:52.869,201] [0m<inf> app_event_manager: DATA_EVT_DATA_READY[0m
2023-01-06T09:21:53.955Z DEBUG modem << %NCELLMEAS: 0,"0F2F5965","28601","1600",65535,6446,213,67,22,412520,6446,339,59,12,0,6446,101,59,12,0,6446,108,56,5,0,0
2023-01-06T09:21:53.976Z DEBUG modem << [00:06:52.954,895] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2023-01-06T09:21:53.983Z DEBUG modem << [00:06:52.959,289] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2023-01-06T09:21:53.996Z DEBUG modem << [00:06:52.959,320] [1;31m<err> modem_info_params: Network data not obtained: -27[0m
2023-01-06T09:21:53.999Z DEBUG modem << [00:06:52.959,350] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2023-01-06T09:21:54.013Z DEBUG modem << [00:06:52.959,411] [0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY[0m
2023-01-06T09:21:54.015Z DEBUG modem << [00:06:53.022,918] [0m<inf> app_event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2023-01-06T09:21:54.029Z DEBUG modem << [00:06:53.026,062] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2023-01-06T09:21:54.032Z DEBUG modem << [00:06:53.030,792] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2023-01-06T09:21:54.034Z DEBUG modem << [00:06:53.030,822] [1;31m<err> modem_info_params: Network data not obtained: -27[0m
2023-01-06T09:21:54.048Z DEBUG modem << [00:06:53.030,853] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2023-01-06T09:21:54.050Z DEBUG modem << [00:06:53.030,914] [0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m
2023-01-06T09:21:54.114Z DEBUG modem << %NCELLMEAS: 0,"0F2F5965","28601","1600",65535,6446,213,66,21,412679,6446,101,59,11,0,6446,339,58,10,0,6446,108,56,6,0,0
2023-01-06T09:21:55.059Z DEBUG modem << [00:06:53.118,225] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2023-01-06T09:21:55.066Z DEBUG modem << [00:06:53.123,657] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2023-01-06T09:21:55.077Z DEBUG modem << [00:06:53.123,687] [1;31m<err> modem_info_params: Network data not obtained: -27[0m
2023-01-06T09:21:55.081Z DEBUG modem << [00:06:53.123,718] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2023-01-06T09:21:55.095Z DEBUG modem << [00:06:53.123,779] [0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY[0m
2023-01-06T09:21:55.098Z DEBUG modem << [00:06:53.182,067] [0m<inf> app_event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m

6- Still AT+COPS=0. I cannot connect to the operator (TURKCELL).

7- It is interesting that, I receive +COPS: (1,"","","28601",9),(3,"","","28602",9) than +COPS: 0 again.


Can anyone help me?

Parents
  • Hi,

    The log shows that the device finds two different cells that it tries to connect to, but it gets rejected with reject cause #15 and #14 respectively.

     +CEREG: 2,"1600","0042DC67",9
    2023-01-06T09:16:28.960Z DEBUG modem << +CSCON: 1,7,4
    2023-01-06T09:16:29.784Z DEBUG modem << %CESQ: 26,1,9,1
    2023-01-06T09:16:30.723Z DEBUG modem << +CNEC_EMM: 15
    2023-01-06T09:16:30.730Z DEBUG modem << +CEREG: 2,"1600","0042DC67",9,0,15
    2023-01-06T09:16:30.789Z DEBUG modem << +CSCON: 0,7,4
    2023-01-06T09:16:31.459Z DEBUG modem << %CESQ: 255,0,255,0
    2023-01-06T09:16:31.465Z DEBUG modem << +CEREG: 2
    2023-01-06T09:17:02.731Z DEBUG modem << %CESQ: 18,0,17,2
    2023-01-06T09:17:02.734Z DEBUG modem << +CEREG: 2,"C246","00E54E16",9
    2023-01-06T09:17:04.707Z DEBUG modem << +CSCON: 1,7,4
    2023-01-06T09:17:05.177Z DEBUG modem << +CNEC_EMM: 14
    2023-01-06T09:17:05.183Z DEBUG modem << +CEREG: 2,"C246","00E54E16",9,0,14

    (I have cleaned up the log a bit to highlight the relevant lines)

    Here is what the LTE spec says about the reject causes:

    Cause #14 – EPS services not allowed in this PLMN
    This EMM cause is sent to the UE which requests service, or if the network initiates a detach request, in a PLMN
    which does not offer roaming for EPS services to that UE.

    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.

    Both reject causes point to a problem with your subscription and/or coverage.

    Does your SIM card support NB-IoT or LTE-M (you only have NB-IoT enabled in the log)?

    Is there NB-IoT coverage at your location?

    Best regards,

    Didrik

Reply
  • Hi,

    The log shows that the device finds two different cells that it tries to connect to, but it gets rejected with reject cause #15 and #14 respectively.

     +CEREG: 2,"1600","0042DC67",9
    2023-01-06T09:16:28.960Z DEBUG modem << +CSCON: 1,7,4
    2023-01-06T09:16:29.784Z DEBUG modem << %CESQ: 26,1,9,1
    2023-01-06T09:16:30.723Z DEBUG modem << +CNEC_EMM: 15
    2023-01-06T09:16:30.730Z DEBUG modem << +CEREG: 2,"1600","0042DC67",9,0,15
    2023-01-06T09:16:30.789Z DEBUG modem << +CSCON: 0,7,4
    2023-01-06T09:16:31.459Z DEBUG modem << %CESQ: 255,0,255,0
    2023-01-06T09:16:31.465Z DEBUG modem << +CEREG: 2
    2023-01-06T09:17:02.731Z DEBUG modem << %CESQ: 18,0,17,2
    2023-01-06T09:17:02.734Z DEBUG modem << +CEREG: 2,"C246","00E54E16",9
    2023-01-06T09:17:04.707Z DEBUG modem << +CSCON: 1,7,4
    2023-01-06T09:17:05.177Z DEBUG modem << +CNEC_EMM: 14
    2023-01-06T09:17:05.183Z DEBUG modem << +CEREG: 2,"C246","00E54E16",9,0,14

    (I have cleaned up the log a bit to highlight the relevant lines)

    Here is what the LTE spec says about the reject causes:

    Cause #14 – EPS services not allowed in this PLMN
    This EMM cause is sent to the UE which requests service, or if the network initiates a detach request, in a PLMN
    which does not offer roaming for EPS services to that UE.

    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.

    Both reject causes point to a problem with your subscription and/or coverage.

    Does your SIM card support NB-IoT or LTE-M (you only have NB-IoT enabled in the log)?

    Is there NB-IoT coverage at your location?

    Best regards,

    Didrik

Children
Related