<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="ES" link="#0563C1" vlink="#954F72" style="word-wrap:break-word"> <div class="WordSection1"> <p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Hi, Alex, thanks for your quick answer.<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Nice to know you worked </span><span lang="EN-US">at Elecnor/Deimos Space </span><span lang="EN-US" style="font-family:"Segoe UI Emoji",sans-serif">😊</span><span lang="EN-US"><br> <br> </span><span class="MsoIntenseEmphasis"><span lang="EN-US"><o:p></o:p></span></span></p> <p class="MsoNormal"><span class="MsoIntenseEmphasis"><span lang="EN-US">This is definitely a bug to fix. </span>That transition to "terminated" shouldn't happen when the callee picks up the call. Can you get MM debug logs while reproducing the issue? Also, is this using AT or QMI?<o:p></o:p></span></p> <p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span lang="EN-US">Two logs are attached: one with transition from ringing-out to active and another with the wrong state transition (ringing-out -> terminated).<o:p></o:p></span></p> <p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span lang="EN-US">At first sight I couldn’t find any significative trace to explain this behavior, I hope you can get some related info in them.<o:p></o:p></span></p> <p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span class="MsoIntenseEmphasis"><span lang="EN-US">1.18 or 1.20 you mean I guess. Either way, the solution is to avoid getting into that wrong terminated state I think.<o:p></o:p></span></span></p> <p class="MsoNormal"><span class="MsoIntenseEmphasis"><span lang="EN-US">Could</span></span><span lang="EN-US"> </span><span class="MsoIntenseEmphasis"><span lang="EN-US">be due to some update in recent versions. We did include the call list management logic as well as the waiting call setup logic. Maybe some of that is not working as expected in your Sierra modem.<o:p></o:p></span></span></p> <p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span lang="EN-US">We updated another device to 1.12 ModemManager version and we still cannot reproduce this issue in that device (our software is using “mm_modem_voice_hangup_all_sync” and compiling well against 1.12 ModemManager version), so we still cannot say wether it’s a hardware related issue or not. We will continue testing and any interesting information or logs we get will be provided to this mail list.<br> <br> Thank you!<o:p></o:p></span></p> <p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p> <div> <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p> <table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="450" style="width:337.5pt"> <tbody> <tr> <td width="150" valign="top" style="width:112.5pt;border:none;border-right:solid #DF0024 1.5pt;padding:0cm 11.25pt 0cm 0cm"> <p class="MsoNormal" align="center" style="text-align:center"><a href="https://www.gmv.com/" target="_blank"><span style="font-family:"Verdana",sans-serif;color:blue;text-decoration:none"><img border="0" width="175" height="68" style="width:1.8263in;height:.7083in" id="Imagen_x0020_1" src="cid:image001.jpg@01D95D8B.D01A4480" alt="Logo"></span></a><span style="font-family:"Verdana",sans-serif"><o:p></o:p></span></p> </td> <td valign="top" style="padding:0cm 0cm 0cm 11.25pt"> <p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:9.0pt;font-family:"Verdana",sans-serif;color:#333333">Héctor Jiménez Méndez</span></b><span style="font-size:9.0pt;font-family:"Verdana",sans-serif"><br> <span style="color:#333333">Firmware engineer</span><br> <br> <span style="color:#333333">T. 983 54 65 54<br> M. 696 297 286<br> </span><br> </span><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#333333">Juan de Herrera, nº 17, P.T.B.</span><span style="font-size:9.0pt;font-family:"Verdana",sans-serif"><br> </span><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#333333">47151 Boecillo, Valladolid | Spain</span><span style="font-size:9.0pt;font-family:"Verdana",sans-serif"><o:p></o:p></span></p> </td> </tr> <tr> <td style="border:none;border-right:solid #DF0024 1.5pt;padding:0cm 0cm 0cm 0cm"> <div align="center"> <table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="150" style="width:112.5pt"> <tbody> <tr> <td style="padding:0cm 0cm 0cm 0cm"> <p class="MsoNormal"><a href="http://www.gmv.com/communication/blog" target="_blank"><span style="color:blue;text-decoration:none"><img border="0" width="34" height="23" style="width:.3541in;height:.243in" id="Imagen_x0020_2" src="cid:image002.jpg@01D95D8B.D01A4480"></span></a><o:p></o:p></p> </td> <td width="24" style="width:18.0pt;padding:0cm 0cm 0cm 0cm"> <p class="MsoNormal"><a href="http://www.facebook.com/infoGMV" target="_blank"><span style="color:blue;text-decoration:none"><img border="0" width="22" height="22" style="width:.2291in;height:.2291in" id="Imagen_x0020_3" src="cid:image003.jpg@01D95D8B.D01A4480"></span></a><o:p></o:p></p> </td> <td width="24" style="width:18.0pt;padding:0cm 0cm 0cm 0cm"> <p class="MsoNormal"><a href="http://www.twitter.com/infoGMV" target="_blank"><span style="color:blue;text-decoration:none"><img border="0" width="22" height="22" style="width:.2291in;height:.2291in" id="Imagen_x0020_4" src="cid:image004.jpg@01D95D8B.D01A4480"></span></a><o:p></o:p></p> </td> <td width="24" style="width:18.0pt;padding:0cm 0cm 0cm 0cm"> <p class="MsoNormal"><a href="http://www.youtube.com/infoGMV" target="_blank"><span style="color:blue;text-decoration:none"><img border="0" width="22" height="22" style="width:.2291in;height:.2291in" id="Imagen_x0020_5" src="cid:image005.jpg@01D95D8B.D01A4480"></span></a><o:p></o:p></p> </td> <td width="24" style="width:18.0pt;padding:0cm 0cm 0cm 0cm"> <p class="MsoNormal"><a href="https://www.instagram.com/companygmv/" target="_blank"><span style="color:blue;text-decoration:none"><img border="0" width="22" height="22" style="width:.2291in;height:.2291in" id="Imagen_x0020_6" src="cid:image006.jpg@01D95D8B.D01A4480"></span></a><o:p></o:p></p> </td> <td width="24" style="width:18.0pt;padding:0cm 0cm 0cm 0cm"> <p class="MsoNormal"><a href="https://www.linkedin.com/company/gmv" target="_blank"><span style="color:blue;text-decoration:none"><img border="0" width="22" height="22" style="width:.2291in;height:.2291in" id="Imagen_x0020_7" src="cid:image007.jpg@01D95D8B.D01A4480"></span></a><o:p></o:p></p> </td> </tr> </tbody> </table> </div> </td> <td style="padding:0cm 0cm 0cm 11.25pt"> <p class="MsoNormal"><span style="font-family:"Verdana",sans-serif"><a href="http://www.gmv.com/" target="_blank"><b><span style="font-size:9.0pt;color:#DF0024">www.gmv.com</span></b></a><o:p></o:p></span></p> </td> </tr> </tbody> </table> <p class="MsoNormal"><o:p> </o:p></p> </div> <p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm"> <p class="MsoNormal"><b>De:</b> Aleksander Morgado <aleksandermj@chromium.org> <br> <b>Enviado el:</b> martes, 21 de marzo de 2023 11:43<br> <b>Para:</b> Héctor Jiménez Méndez <hector.jimenez.m@gmv.com><br> <b>CC:</b> modemmanager-devel@lists.freedesktop.org<br> <b>Asunto:</b> Re: modem terminates call when accepted remotely<o:p></o:p></p> </div> </div> <p class="MsoNormal"><o:p> </o:p></p> <div> <div> <p class="MsoNormal">Hoola Héctor!<o:p></o:p></p> </div> <div> <div> <p class="MsoNormal"> <o:p></o:p></p> </div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"> <div> <div> <div> <p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p> <p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span lang="EN-US">First of all, I would like to thank you all your effort to develop and maintain this API as it’s being very useful to us for handling modem connections in our embedded devices.</span><o:p></o:p></p> </div> </div> </div> </blockquote> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">I'm really glad to see GMV is using all this :) I worked at Elecnor/Deimos Space in a past life!<o:p></o:p></p> </div> <div> <p class="MsoNormal"> <o:p></o:p></p> </div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"> <div> <div> <div> <p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">We are facing an issue with ModemManager 1.16.2 (libmm-glib) and RC7620 SIERRA modem.<br> <br> Sometimes, after starting a call to another SIM card device (mobile phone), the call gets into “terminated” state (seen by ModemManager) in the moment the call is accepted by the remote device, while it remains active at this remote point.<br> <br> The call state becomes “dialing”, then “ringing-out”, and finally “terminated” so there is no option to finish the call from ModemManager side as it’s seen as already terminated.</span><o:p></o:p></p> <p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><o:p></o:p></p> </div> </div> </div> </blockquote> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">This is definitely a bug to fix. That transition to "terminated" shouldn't happen when the callee picks up the call. Can you get MM debug logs while reproducing the issue? Also, is this using AT or QMI?<o:p></o:p></p> </div> <div> <p class="MsoNormal"> <o:p></o:p></p> </div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"> <div> <div> <div> <p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span lang="EN-US">We managed to actually finish the call (remote side too) by the use of ”mm_modem_voice_hangup_all_sync” function (defined in mm-modem-voice.h), but it’s only available since ModemManager 1.12 Version. </span><o:p></o:p></p> </div> </div> </div> </blockquote> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">1.18 or 1.20 you mean I guess. Either way, the solution is to avoid getting into that wrong terminated state I think.<o:p></o:p></p> </div> <div> <p class="MsoNormal"> <o:p></o:p></p> </div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"> <div> <div> <div> <p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span lang="EN-US">Some of our devices are using other hardware and older versions of ModemManager (1.10) and we have never been able to reproduce this issue so we didn’t need to make use of “mm_modem_voice_hangup_all_sync” function.</span><o:p></o:p></p> </div> </div> </div> </blockquote> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">Could be due to some update in recent versions. We did include the call list management logic as well as the waiting call setup logic. Maybe some of that is not working as expected in your Sierra modem.<o:p></o:p></p> </div> <div> <p class="MsoNormal"> <o:p></o:p></p> </div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"> <div> <div> <div> <p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">I would like to know if this issue has been already reported, and if so, if it has been resolved or if it’s related to the hardware we installed on our device or, on the other hand, if has something to do with the ModemManager version being used.</span><o:p></o:p></p> <p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> </span><o:p></o:p></p> </div> </div> </div> </blockquote> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">Don't recall an issue like this, truth be told. <o:p></o:p></p> </div> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">Cheers<o:p></o:p></p> </div> </div> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <p class="MsoNormal"><span class="gmailsignatureprefix">-- </span><o:p></o:p></p> <div> <div> <div> <p class="MsoNormal">Aleksander<o:p></o:p></p> </div> </div> </div> </div> <p class="MsoNormal"><br> <span style="font-size:18.0pt;font-family:Webdings;color:green">P </span><span style="font-size:7.0pt;font-family:"Arial",sans-serif;color:green">Please consider the environment before printing this e-mail.</span> <o:p></o:p></p> </div> </body> </html>