WP7611 ATT R16 Voice Call Terminated_undefined

IoT Modules WP Series
1

Hello, we are using R16 ATT release with WP7611 module with mangoh yellow. Oftentimes we are getting voice calls terminated for unknown reason. The call event handler is returning termination with reason: LE_VOICECALL_TERM_UNDEFINED

I’m thinking this is module firmware or network related and not legato specific. Any help or debug steps would be much appreciated.

WP7611 chip with mangoh yellow hardware:
Firmware Version: SWI9X07Y_02.37.00.00 6c0fe9 jenkins 2020/01/17 01:29:47
Bootloader Version: SWI9X07Y_02.37.00.00 6c0fe9 jenkins 2020/01/17 01:29:47

Oftentimes, we reboot the modem and calls will be successful. It doesn’t appear to matter how long the modem has been booted up. It could happen 2 minutes after the modem has been booted up, or it could happen 6 hours after bootup and calls have been successful for the first 6 hours. Logs showing the exact legato logs are below. It shows the modem ringing and then an abrupt terminate with unknown reason. I am getting the call on my cell phone and try to answer but then it just terminates from modem side.

Mar 17 16:03:47 swi-mdm9x28-wp user.info Legato: INFO | voiceCallExe[2007]/voiceCallComponent T=main | voiceCallComp.c MyCallEventHandler() 689 | LE_VOICECALL_EVENT_ALERTING
Mar 17 16:03:47 swi-mdm9x28-wp user.info Legato: INFO | voiceCallExe[2007]/voiceCallComponent T=main | voiceCallComp.c MyCallEventHandler() 690 | Destination phone is ringing…
Mar 17 16:03:47 swi-mdm9x28-wp user.debug Legato: DBUG | messageRouter[1943]/messageRouter T=main | messageRouter.c handleVoiceCallStatusUpdate() 304 | Inside handleVoiceCallStatusUpdate
Mar 17 16:03:47 swi-mdm9x28-wp user.debug Legato: DBUG | messageRouter[1943]/messageRouter T=main | messageRouter.c handleVoiceCallStatusUpdate() 305 | timeStamp = 1647551027
Mar 17 16:03:47 swi-mdm9x28-wp user.debug Legato: DBUG | messageRouter[1943]/messageRouter T=main | messageRouter.c handleVoiceCallStatusUpdate() 306 | CallStatus = “RINGING”
Mar 17 16:03:47 swi-mdm9x28-wp user.info Legato: INFO | messageRouter[1943]/messageRouter T=main | messageRouter.c handleVoiceCallStatusUpdate() 307 | contextPtr = 0xb6f0a218
Mar 17 16:03:47 swi-mdm9x28-wp user.info Legato: INFO | messageRouter[1943]/messageRouter T=main | messageRouter.c handleVoiceCallStatusUpdate() 335 | Call status update message {“MessageID”:59,“TimeStamp”:1647551027,“CallStatusUpdate”:[{“CallStatus”:“RINGING”,"DestinationNo
Mar 17 16:03:47 swi-mdm9x28-wp user.info Legato: INFO | mqttClientService[1944] | 20220317 160347.423 sent 0 256 buflen 5
Mar 17 16:03:47 swi-mdm9x28-wp user.info Legato: INFO | mqttClientService[1944] | 20220317 160347.423 10 89011702272006457771 → PUBLISH msgid: 61 qos: 2 retained: 0 (0) payload: {“MessageID”:59,"Tim
Mar 17 16:03:47 swi-mdm9x28-wp user.err kernel: [ 3766.887430] voice_get_session: Invalid session_id : 0
Mar 17 16:03:47 swi-mdm9x28-wp user.err kernel: [ 3766.891597] voc_set_route_flag: invalid session_id 0x0
Mar 17 16:03:47 swi-mdm9x28-wp user.err kernel: [ 3766.896604] voice_get_session: Invalid session_id : 0
Mar 17 16:03:47 swi-mdm9x28-wp user.err kernel: [ 3766.902193] voc_set_device_config: Invalid session_id 0x0
Mar 17 16:03:47 swi-mdm9x28-wp user.err kernel: [ 3766.907031] voice_get_session: Invalid session_id : 0
Mar 17 16:03:47 swi-mdm9x28-wp user.err kernel: [ 3766.912339] voc_get_route_flag: invalid session_id 0x0
Mar 17 16:03:48 swi-mdm9x28-wp user.info Legato: INFO | mqttClientService[1944] | 20220317 160348.028 received 0 256 buflen 5
Mar 17 16:03:48 swi-mdm9x28-wp user.info Legato: INFO | mqttClientService[1944] | 20220317 160348.029 10 89011702272006457771 ← PUBREC msgid: 61
Mar 17 16:03:48 swi-mdm9x28-wp user.info Legato: INFO | mqttClientService[1944] | 20220317 160348.029 sent 0 256 buflen 5
Mar 17 16:03:48 swi-mdm9x28-wp user.info Legato: INFO | mqttClientService[1944] | 20220317 160348.029 10 89011702272006457771 → PUBREL msgid: 61 (0)
Mar 17 16:03:48 swi-mdm9x28-wp user.info Legato: INFO | mqttClientService[1944] | 20220317 160348.031 received 0 256 buflen 5
Mar 17 16:03:48 swi-mdm9x28-wp user.info Legato: INFO | mqttClientService[1944] | 20220317 160348.040 10 89011702272006457771 ← PUBCOMP msgid:61
Mar 17 16:03:50 swi-mdm9x28-wp user.warn Legato: -WRN- | audioDaemon[1811]/le_pa_audio T=unknown | pa_audio.c CallHandler() 375 | CallHandler called
Mar 17 16:03:50 swi-mdm9x28-wp user.warn Legato: -WRN- | audioDaemon[1811]/le_pa_audio T=unknown | pa_audio.c CallHandler() 427 | Identify call ID 0
Mar 17 16:03:50 swi-mdm9x28-wp user.info Legato: INFO | modemDaemon[1894]/le_pa T=unknown | pa_mcc_qmi.c CallHandler() 690 | QMI ID.1 State.END (0x09) Type.0x02 Dir.0x01 Mode.0x04 Mparty.0 ALS.0
Mar 17 16:03:50 swi-mdm9x28-wp user.info Legato: INFO | modemDaemon[1894]/le_pa T=unknown | pa_mcc_qmi.c GetTerminationReason() 557 | Specific QMI termination reason: 0x14e
Mar 17 16:03:50 swi-mdm9x28-wp user.info Legato: INFO | voiceCallExe[2007]/voiceCallComponent T=main | voiceCallComp.c MyCallEventHandler() 681 | New Call event: 2 for Call 0x1f5, from 4405335102
Mar 17 16:03:50 swi-mdm9x28-wp user.info Legato: INFO | voiceCallExe[2007]/voiceCallComponent T=main | voiceCallComp.c MyCallEventHandler() 721 | LE_VOICECALL_EVENT_TERMINATED
Mar 17 16:03:50 swi-mdm9x28-wp user.debug Legato: DBUG | voiceCallExe[2007]/voiceCallComponent T=main | voiceCallComp.c ProcessTerminateEvent() 602 | Got terminatation reason:5 for call with reference:0x1f5
Mar 17 16:03:50 swi-mdm9x28-wp user.info Legato: INFO | voiceCallExe[2007]/voiceCallComponent T=main | voiceCallComp.c GenerateCallStatusEvent() 326 | Setting destinationNo to 4405335102
Mar 17 16:03:50 swi-mdm9x28-wp user.info Legato: INFO | voiceCallExe[2007]/voiceCallComponent T=main | voiceCallComp.c GenerateCallStatusEvent() 334 | Setting termination reason to UNDEFINED
Mar 17 16:03:50 swi-mdm9x28-wp user.info Legato: INFO | voiceCallExe[2007]/voiceCallComponent T=main | voiceCallComp.c ProcessTerminateEvent() 638 | LE_VOICECALL_TERM_UNDEFINED
Mar 17 16:03:50 swi-mdm9x28-wp user.debug Legato: DBUG | voiceCallExe[2007]/voiceCallComponent T=main | voiceCallComp.c ProcessTerminateEvent() 648 | Successfully deleted call with reference:0x1f5

2

Does anyone have any insight in how to look up what this error code means? Its coming quite often for us.

3

Hi james.wollaeger,

You are using firmware AT&T release 16. If I’m not wrong, Are you using the AT&T SIM? If yes, your problem could be that AT&T shut down the 3G network in late February 2022. Please check it with the AT&T operator.

4

We are running an ATT sim card but we have VOLTE enabled and using a VOLTE certified module per ATT PTCRB certification. Voice calls are functional after 3G sunset till they aren’t. After a power cycle of the modem, calls will work again after all calls start failing with Specific QMI termination reason: 0x14e .