WP7611 ATT Calls terminate Unknown after dial/ringing events

IoT Modules WP Series
1

Has anyone ever seen an issue whereby the module will dial outbound for a call, get a ringing event, and then immediately terminate?

Nov 8 10:49:40 swi-mdm9x28-wp user.warn Legato: -WRN- | audioDaemon[1807]/le_pa_audio T=unknown | pa_audio.c CallHandler() 375 | CallHandler called
Nov 8 10:49:40 swi-mdm9x28-wp user.warn Legato: -WRN- | audioDaemon[1807]/le_pa_audio T=unknown | pa_audio.c CallHandler() 427 | Identify call ID 0
Nov 8 10:49:40 swi-mdm9x28-wp user.debug Legato: DBUG | modemDaemon[1923]/swiQmi T=unknown | swiQmi.c IndicationsHandler() 281 | serviceType=0x4
Nov 8 10:49:40 swi-mdm9x28-wp user.debug Legato: DBUG | modemDaemon[1923]/swiQmi T=unknown | swiQmi.c IndicationsHandler() 282 | msg_id=0x2E
Nov 8 10:49:40 swi-mdm9x28-wp user.debug Legato: DBUG | modemDaemon[1923]/swiQmi T=unknown | swiQmi.c IndicationsHandler() 284 | clientHandle 0x12
Nov 8 10:49:40 swi-mdm9x28-wp user.debug Legato: DBUG | modemDaemon[1923]/le_pa T=unknown | pa_mcc_qmi.c CallHandler() 661 | Call Event: call_info_len 1
Nov 8 10:49:40 swi-mdm9x28-wp user.info Legato: INFO | modemDaemon[1923]/le_pa T=unknown | pa_mcc_qmi.c CallHandler() 690 | QMI ID.1 State.DISCONNECTING (0x08) Type.0x00 Dir.0x01 Mode.0x03 Mparty.0 ALS.0
Nov 8 10:49:40 swi-mdm9x28-wp user.warn Legato: -WRN- | modemDaemon[1923]/le_pa T=unknown | pa_mcc_qmi.c MapQmiCallStateToCallEvent() 118 | QMI call state discarded: 0x08
Nov 8 10:49:40 swi-mdm9x28-wp user.debug Legato: DBUG | modemDaemon[1923]/le_pa T=unknown | pa_mcc_qmi.c CallHandler() 694 | callEvent -1
Nov 8 10:49:40 swi-mdm9x28-wp user.warn Legato: -WRN- | audioDaemon[1807]/le_pa_audio T=unknown | pa_audio.c CallHandler() 375 | CallHandler called
Nov 8 10:49:40 swi-mdm9x28-wp user.warn Legato: -WRN- | audioDaemon[1807]/le_pa_audio T=unknown | pa_audio.c CallHandler() 427 | Identify call ID 0
Nov 8 10:49:40 swi-mdm9x28-wp user.debug Legato: DBUG | modemDaemon[1923]/swiQmi T=unknown | swiQmi.c IndicationsHandler() 281 | serviceType=0x4
Nov 8 10:49:40 swi-mdm9x28-wp user.debug Legato: DBUG | modemDaemon[1923]/swiQmi T=unknown | swiQmi.c IndicationsHandler() 282 | msg_id=0x2E
Nov 8 10:49:40 swi-mdm9x28-wp user.debug Legato: DBUG | modemDaemon[1923]/swiQmi T=unknown | swiQmi.c IndicationsHandler() 284 | clientHandle 0x12
Nov 8 10:49:40 swi-mdm9x28-wp user.debug Legato: DBUG | modemDaemon[1923]/le_pa T=unknown | pa_mcc_qmi.c CallHandler() 661 | Call Event: call_info_len 1
Nov 8 10:49:40 swi-mdm9x28-wp user.info Legato: INFO | modemDaemon[1923]/le_pa T=unknown | pa_mcc_qmi.c CallHandler() 690 | QMI ID.1 State.END (0x09) Type.0x00 Dir.0x01 Mode.0x03 Mparty.0 ALS.0
Nov 8 10:49:40 swi-mdm9x28-wp user.debug Legato: DBUG | modemDaemon[1923]/le_pa T=unknown | pa_mcc_qmi.c CallHandler() 694 | callEvent 5
Nov 8 10:49:40 swi-mdm9x28-wp user.debug Legato: DBUG | modemDaemon[1923]/framework T=unknown | mem.c le_mem_ForceAlloc() 1172 | Memory pool ‘le_pa.CallEventDataPool’ overflowed. Expanded to 3 blocks.
Nov 8 10:49:40 swi-mdm9x28-wp user.debug Legato: DBUG | modemDaemon[1923]/le_pa T=unknown | pa_mcc_qmi.c CallHandler() 714 | remote_party_number_ext2_valid Len 1
Nov 8 10:49:40 swi-mdm9x28-wp user.debug Legato: DBUG | modemDaemon[1923]/le_pa T=unknown | pa_mcc_qmi.c GetRemoteNumber() 279 | Remote Number (0) Id 1 => 12149574634
Nov 8 10:49:40 swi-mdm9x28-wp user.debug Legato: DBUG | modemDaemon[1923]/le_pa T=unknown | pa_mcc_qmi.c GetTerminationReason() 329 | QMI termination reason: 0xbc

2

How about use ATD1234567; in usb AT command port?

Btw, does your sim card support VOLTE?

3

Yes the ATT SIM supports VOLTE.

This is what I see:
AT!GSTATUS?
!GSTATUS:
Current Time: 64108 Temperature: 34
Modem Mitigate Level: 0 ModemProc Mitigate Level: 0
Reset Counter: 1 Mode: ONLINE
System mode: LTE PS state: Attached
IMS reg state: REGISTERED IMS mode: Normal
IMS Srv State: NO SMS,FULL VoIP
LTE band: B66 LTE bw: 10 MHz
LTE Rx chan: 0 LTE Tx chan: 132622
LTE CA state: INACTIVE
EMM state: Registered Normal Service
RRC state: RRC Idle

PCC RxM RSSI: -68 RSRP (dBm): -96
PCC RxD RSSI: -88 RSRP (dBm): -129
Tx Power: – TAC: 6A43 (27203)
RSRQ (dB): -11 Cell ID: 08006C16 (134245398)
SINR (dB): 11.4

OK
ATD2149574634
NO CARRIER

ATT firmware:
ATI
Manufacturer: Sierra Wireless, Incorporated
Model: WP7611
Revision: SWI9X07Y_02.37.00.00 6c0fe9 jenkins 2020/01/17 01:29:47

4

I think you missed the “;”
i.e. atd1234567;

5

Unfortunately, same result:
AT!GSTATUS?
!GSTATUS:
Current Time: 70117 Temperature: 34
Modem Mitigate Level: 0 ModemProc Mitigate Level: 0
Reset Counter: 1 Mode: ONLINE
System mode: LTE PS state: Attached
IMS reg state: REGISTERED IMS mode: Normal
IMS Srv State: NO SMS,FULL VoIP
LTE band: B66 LTE bw: 10 MHz
LTE Rx chan: 0 LTE Tx chan: 132622
LTE CA state: INACTIVE
EMM state: Registered Normal Service
RRC state: RRC Idle

PCC RxM RSSI: -72 RSRP (dBm): -101
PCC RxD RSSI: -88 RSRP (dBm): -132
Tx Power: – TAC: 6A43 (27203)
RSRQ (dB): -11 Cell ID: 08006C16 (134245398)
SINR (dB): 4.4

OK
ATD2149574634;
OK

NO CARRIER

6

Are you using at&t carrier PRI?

7

Yes. we have found out that we are unable to call att mobile phones when on VOLTE. we have questions out to the carrier about why, we can consider this issue resolved.