WP7607 - LTE data session drops every 60 sec on SKU 1104192 samples

Legato Application Framework
1

Hi,

my WP7607 application works fine on UMTS and GSM technology, and creates a stable data connection on our APN network.
Data connections on LTE are OK with our SKU 1103511 samples, but, are not OK with our SKU 1104192 samples.
All our WP7607 samples have been reprogrammed with our own builds (based upon R13.2). We use our own yocto build (based upon 2.5).

With the 1104192 samples, the LTE data session drops every 60 seconds.
QMINewSessionStateHandler() suddenly gets called and removes the wdsClient of the active data session.
Please, check wdsClient 0xcaa in the attached logs.

Nov 14 10:25:23 | swiQmi.c WdsIndicationsHandler() 219 | serviceType=0x3
Nov 14 10:25:23 | swiQmi.c WdsIndicationsHandler() 220 | msg_id=0x22
Nov 14 10:25:23 | swiQmi.c WdsIndicationsHandler() 222 | clientHandle 0xcaa
Nov 14 10:25:23 | pa_mdc_qmi.c QMINewSessionStateHandler() 1065 | wdsClient: 0xcaa, profile index: 1
Nov 14 10:25:23 | pa_mdc_qmi.c mdc_qmi_ReleaseWdsClient() 2781 | Remove WdsClient [0][0] 0xcaa

What could be the reason why the SKU 1104192 samples behave worse than the 1103511 samples?

Device: WP7607
IMEI: 359779080199074
IMEISV: 6
FSN: V3929400150910
Firmware Version: SWI9X07Y_02.28.03.01 000000 jenkins 2019/04/17 03:08:11
Bootloader Version: SWI9X07Y_02.28.03.01 000000 jenkins 2019/04/17 03:08:11
MCU Version: 002.011
PRI Part Number (PN): 9908663
PRI Revision: 001.002
Carrier PRI Name: GENERIC
Carrier PRI Revision: 002.064_000
SKU: 1104192

Device: WP7607
IMEI: 359779080110022
IMEISV: 6
FSN: VN829285000810
Firmware Version: SWI9X07Y_02.28.03.01 000000 jenkins 2019/04/17 03:08:11
Bootloader Version: SWI9X07Y_02.28.03.01 000000 jenkins 2019/04/17 03:08:11
MCU Version: 002.011
PRI Part Number (PN): 9907327
PRI Revision: 001.004
Carrier PRI Name: GENERIC
Carrier PRI Revision: 002.064_000
SKU: 1103511

Greetings,
annaertd

LTE data session drops every 60sec (40.5 KB)

2

Our provider confirmed that our modems are able to establish an LTE data session without any problem.
But, 60 seconds after the LTE data connection has been established, the modem apparently tries to setup a VoIP session.
This VoIP session is rejected immediately by the network provider, because VoIP is not supported by our APN network.
This rejection will also drop the existing LTE data session.

Our application does not implement anything related to voice or VoIP.
Our SKU 1104192 modems have VoLTE on board, but, how can we disable this?
Can we use the Legato API to disable VoLTE, or, do we need to change a config file?

3

@annaertd, if you try with the standard R13.2 (without your customisation) what happen? can you establish a permanent connection! However, we need all the logs, please (logs provided are cut)?

What do you mean per “Our SKU 1104192 modems have VoLTE on board”? please. and if the 1103511 unit has the same?

4

Hi,

WP7607 samples with SKU 1104192 have Voice over LTE on board.
If you use AT commands, you can see that these samples also have a predefined profile 2 and 3:
AT+CGDCONT?

  • +CGDCONT: 1,“IP”,“myAPNname”,“0.0.0.0”,0,0,0,0*
  • +CGDCONT: 2,“IPV4V6”,“ims”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0*
  • +CGDCONT: 3,“IPV4V6”,“sos”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,1*

I was able to fix the issue: my LTE data session doesn’t get interrupted anymore every 60 seconds.

At startup of my application, I use Legato API calls le_mdc_GetProfileList(), le_mdc_GetProfile() and le_mdc_GetAPN() to check the APN name of all profile index numbers (except default index 1).
In case an APN name is different from the empty string, I use le_mdc_SetAPN() to give the APN an empty string name.

With this solution I can avoid to clear the modem profile 2 and 3, using AT commands:
AT+CGDCONT=2
AT+CGDCONT=3

As an exercise, you can double check the result after startup, using the AT command:
AT+CGDCONT?

  • +CGDCONT: 1,“IP”,“myAPNname”,“0.0.0.0”,0,0,0,0*
  • +CGDCONT: 2,“IPV4V6”,“”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0*
  • +CGDCONT: 3,“IPV4V6”,“”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,1*

greetings,
annaertd