Audio calls work fine in WP7610 but no audio is heard on WP7609

Hi All,

I’ve been working with the WP7609 and WP7610 modems specifically around voice calls. I’ve successfully tested voice call functionality on the WP7610, however, when I attempt to use the same code with the WP7609 no audio is heard in the phone call. When I check the device log, I see the following error messages:

Oct 23 18:37:52 swi-mdm9x28-wp user.info Legato: INFO | VoiceManagerExe[886]/VoiceManager T=main | debug.cpp Log() 37 | VoiceManager: Call: INCOMING from +1xxxxxxxxxx
Oct 23 18:37:52 swi-mdm9x28-wp user.warn Legato: -WRN- | modemDaemon[892]/le_pa T=main | pa_sim_qmi.c MapSimState() 1009 | More than one application 2
Oct 23 18:37:52 swi-mdm9x28-wp user.info Legato: INFO | MainApp[880]/modem_access T=main | debug.cpp Log() 37 | Main: Answering incoming voice call.
Oct 23 18:37:52 swi-mdm9x28-wp user.warn Legato: -WRN- | audioDaemon[855]/le_pa_audio T=unknown | pa_audio.c CallHandler() 375 | CallHandler called
Oct 23 18:37:52 swi-mdm9x28-wp user.warn Legato: -WRN- | audioDaemon[855]/le_pa_audio T=unknown | pa_audio.c CallHandler() 427 | Identify call ID 1
Oct 23 18:37:52 swi-mdm9x28-wp user.info Legato: INFO | modemDaemon[892]/le_pa T=unknown | pa_mcc_qmi.c CallHandler() 689 | QMI ID.1 State.CONVERSATION (0x03) Type.0x00 Dir.0x02 Mode.0x03 Mparty.0 ALS.0
Oct 23 18:37:52 swi-mdm9x28-wp user.info Legato: INFO | VoiceManagerExe[886]/VoiceManager T=main | debug.cpp Log() 37 | VoiceManager: Call: CONNECTED from +1xxxxxxxxxx
[ 95.472346] Circuit-Switch Voice: ASoC: no backend DAIs enabled for Circuit-Switch Voice
[ 95.492671] voc_end_voice_call: Error: End voice called in state 0
[ 95.513708] Circuit-Switch Voice: ASoC: no backend DAIs enabled for Circuit-Switch Voice
[ 95.521455] voc_end_voice_call: Error: End voice called in state 0
Oct 23 18:37:53 swi-mdm9x28-wp user.err kernel: [ 95.472346] Circuit-Switch Voice: ASoC: no backend DAIs enabled for Circuit-Switch Voice**
Oct 23 18:37:53 swi-mdm9x28-wp user.err kernel: [ 95.492671] voc_end_voice_call: Error: End voice called in state 0
Oct 23 18:37:53 swi-mdm9x28-wp user.err kernel: [ 95.513708] Circuit-Switch Voice: ASoC: no backend DAIs enabled for Circuit-Switch Voice
Oct 23 18:37:53 swi-mdm9x28-wp user.err kernel: [ 95.521455] voc_end_voice_call: Error: End voice called in state 0

This looks like the WP76xx modem binary driver is throwing kernel errors, but I have no idea what they actually mean. We are seeing this on UMTS/HSPA only while in North America, however, we are seeing similar symptoms in Australia. Any help would be appreciated.

Thanks,
Chris

Are you testing the latest FW R16?

No. We are using 13.3 for the WP7609, and 13.2 for the WP7610.

is it possible to give a try on latest FW?

I don’t see an R16 release for the WP7609…

R16 (Generic — GCF & PTCRB) — WP7601, WP7603, WP7607, WP7610, WP7611
R16 (AT&T — PTCRB) — WP7603, WP7610, WP7611
R16 (Sierra Wireless — GCF) — WP7603, WP7607, WP7610, WP7611
R16 (Sprint — GCF) — WP7611
R16 (T-Mobile — PTCRB) — WP7611
R16 (Verizon — GCF) — WP7601, WP7610, WP7611

can the generic GCF register on your network?

After updating the modem to R16, I was able to successfully make an audio connection on the device. However, I’m a little concerned that the Firmware isn’t listed as supported for the WP7609. And though it works here, it may not work for our customers in Australia who are using WP7609.

hi
R16 is under certification for GCF on WP7609, and should be available soon.

Hi,

It seems that R16 is still not certified for GCF on WP7609. May I ask when it will be certified?

I think it will be in R16.1 later

Thank you for the reply. By “later” do you mean later this year?

yes, i think so.
BTW, did you contact your distributor?

Yes and I was told there are no expected updates for WP76xx modules this quarter. I thought I would respond on this forum thread, though, as the WP7609 support for R16 “should be available soon” according to @plu 's comment in November 2020, so was unsure if WP7609 support for R16 had already been released

I have faced a silent audio issue, please see: