# Ar755x eCall MSD not sent because Unknown state **URL:** \ **Category:** Legato Application Framework\ **Created:** [July 21, 2017, 9:36am UTC](https://forum.legato.io/t/ar755x-ecall-msd-not-sent-because-unknown-state/2560 "2017-07-21T09:36:59Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mihaipop](https://avatars.discourse-cdn.com/v4/letter/m/41988e/32.png) [@mihaipop](https://forum.legato.io/u/mihaipop)\ **Post date:** [July 21, 2017, 9:36am UTC](https://forum.legato.io/t/ar755x-ecall-msd-not-sent-because-unknown-state/2560/1 "2017-07-21T09:36:59Z")
Hi all, I have a problem using an AR755X modem running the eCallDemo app and a u-blox LISA U200 PSAP simulator. While the simulator is running i trigger the eCallDemo app, then the call is successful but the MSD is not sent because from `LE_ECALL_STATE_WAITING_PSAP_START_IND` state it goes directly into `Unknown eCall state 20!`. The debug log is: ``` root@swi-mdm9x15:~# execInApp eCallDemo trig 2 && logread -f [1746.227376] afe_callback: cmd = 0x100cd returned error = 0x9 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.111734] mdm9615_ar7_enable_codec_ext_clk: enable = 1 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.180283] mdm9615_ar7_enable_codec_ext_clk: enable = 1 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.190050] 100c3 0 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.190660] 11025 0 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.190965] 11279 0 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.191515] 11025 0 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.206012] 11275 0 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.206500] 11277 0 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.210804] 100c6 0 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.225392] 1123e 0 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.225911] 11103 0 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.226216] 110ee 9 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.226277] mute value =0 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.226521] 11022 0 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.227071] 11190 0 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.227132] afe_sidetone: tx_port_id:1 rx_port_id:0 enable:0 gain:0 Jan 6 00:49:43 swi-mdm9x15 user.err kernel: [1746.227376] afe_callback: cmd = 0x100cd returned error = 0x9 Jan 6 00:49:43 swi-mdm9x15 user.info kernel: [1746.390233] mdm9615_enable_codec_ext_clk: enable = 1 Jan 6 00:49:44 swi-mdm9x15 user.info Legato: INFO | modemDaemon[546]/le_pa T=unknown | pa_mcc_qmi.c CallHandler() 631 | QMI ID.1 State.ALERTING (0x05) Type.0x00 Dir.0x01 Mode.0x03 Mparty.0 ALS.0 Jan 6 00:49:44 swi-mdm9x15 user.warn Legato: -WRN- | audioDaemon[534]/le_pa_audio T=unknown | pa_audio.c CallHandler() 1711 | CallHandler called Jan 6 00:49:44 swi-mdm9x15 user.warn Legato: -WRN- | audioDaemon[534]/le_pa_audio T=unknown | pa_audio.c CallHandler() 1763 | Identify call ID 0 Jan 6 00:49:47 swi-mdm9x15 user.debug kernel: [1750.989989] NMEA read driver miss interrupt, abandon current buff Jan 6 00:49:48 swi-mdm9x15 user.info Legato: INFO | eCallDemo[7877]/eCallAppComponent T=main | eCallApp.c ECallStateHandler() 137 | New eCall state for eCallRef.0x10000001 Jan 6 00:49:48 swi-mdm9x15 user.info Legato: INFO | eCallDemo[7877]/eCallAppComponent T=main | eCallApp.c ECallStateHandler() 148 | New eCall state is LE_ECALL_STATE_CONNECTED. Jan 6 00:49:48 swi-mdm9x15 user.info Legato: INFO | eCallDemo[7877]/eCallAppComponent T=main | eCallApp.c ECallStateHandler() 137 | New eCall state for eCallRef.0x10000001 Jan 6 00:49:48 swi-mdm9x15 user.info Legato: INFO | eCallDemo[7877]/eCallAppComponent T=main | eCallApp.c ECallStateHandler() 159 | New eCall state is LE_ECALL_STATE_WAITING_PSAP_START_IND. Jan 6 00:49:48 swi-mdm9x15 user.info Legato: INFO | modemDaemon[546]/le_pa T=unknown | pa_mcc_qmi.c CallHandler() 631 | QMI ID.1 State.CONVERSATION (0x03) Type.0x00 Dir.0x01 Mode.0x03 Mparty.0 ALS.0 Jan 6 00:49:48 swi-mdm9x15 user.warn Legato: -WRN- | audioDaemon[534]/le_pa_audio T=unknown | pa_audio.c CallHandler() 1711 | CallHandler called Jan 6 00:49:48 swi-mdm9x15 user.warn Legato: -WRN- | audioDaemon[534]/le_pa_audio T=unknown | pa_audio.c CallHandler() 1763 | Identify call ID 1 Jan 6 00:49:48 swi-mdm9x15 user.info kernel: [1751.857439] 11027 0 Jan 6 00:49:53 swi-mdm9x15 user.info Legato: INFO | eCallDemo[7877]/eCallAppComponent T=main | eCallApp.c ECallStateHandler() 137 | New eCall state for eCallRef.0x10000001 Jan 6 00:49:53 swi-mdm9x15 user.warn Legato: -WRN- | eCallDemo[7877]/eCallAppComponent T=main | eCallApp.c ECallStateHandler() 234 | Unknown eCall state 20! Jan 6 00:49:58 swi-mdm9x15 user.info kernel: [1761.872027] 11027 0 Jan 6 00:49:58 swi-mdm9x15 user.info kernel: [1761.899740] 11027 0 Jan 6 00:50:08 swi-mdm9x15 user.info kernel: [1771.922447] 11027 0 Jan 6 00:50:08 swi-mdm9x15 user.info kernel: [1771.950251] 11027 0 ``` Do you have any idee why is this happening? or give me some hints on how to debug this further? Thank you ---
**Author:** ![CoRfr](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/corfr/32/69_2.png) [@CoRfr](https://forum.legato.io/u/CoRfr)\ **Post date:** [July 21, 2017, 11:32pm UTC](https://forum.legato.io/t/ar755x-ecall-msd-not-sent-because-unknown-state/2560/2 "2017-07-21T23:32:21Z")
Hi @mihaipop, which version of Legato do you have? ---
**Author:** ![mihaipop](https://avatars.discourse-cdn.com/v4/letter/m/41988e/32.png) [@mihaipop](https://forum.legato.io/u/mihaipop)\ **Post date:** [July 22, 2017, 4:50am UTC](https://forum.legato.io/t/ar755x-ecall-msd-not-sent-because-unknown-state/2560/3 "2017-07-22T04:50:57Z")
16\_01 for automotive, AR755x compiler ---
**Author:** ![CoRfr](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/corfr/32/69_2.png) [@CoRfr](https://forum.legato.io/u/CoRfr)\ **Post date:** [July 24, 2017, 11:13pm UTC](https://forum.legato.io/t/ar755x-ecall-msd-not-sent-because-unknown-state/2560/4 "2017-07-24T23:13:30Z")
> [@mihaipop](#): > > Unknown eCall state 20 Looks like this issue is known and the fix has just been checked-in. It should be provided in the next maintenance release. Please contact your SWI representative for this.