<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>Am 18.02.2012 um 11:44 schrieb Dr. H. Nikolaus Schaller:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>Am 18.02.2012 um 07:08 schrieb NeilBrown:<br><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">If I call my GTA04, answer the call, and then hang up, I do not get <br></blockquote><blockquote type="cite"> NO CARRIER<br></blockquote><blockquote type="cite">on the 'Application' port (which is where I get e.g. "RING" indications).<br></blockquote><blockquote type="cite">However I *do* get "NO CARRIER" on the Modem port.<br></blockquote><blockquote type="cite">A little surprising but possibly quite usable. There may be other surprises<br></blockquote><blockquote type="cite">for those willing to explore.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">When I dial out it seems a little different. I try to hang up with ATH<br></blockquote><blockquote type="cite">but "AT+CPAS" indicates I am still on a call. When the other end hangs up,<br></blockquote><blockquote type="cite">then I get NO CARRIER.<br></blockquote><blockquote type="cite">I'm not sure if this is always consistent. More experimentation is needed.<br></blockquote><br>I have recompiled the hso driver with debug enabled and could no longer see<br>the USB re-enumeration issue (which does not prove that one has to do anything<br>with the other, i.e. this is a step towards a solution).<br></div></blockquote><div><br></div>Here is some strange log entry:</div><div><br></div><div>[ 7974.712158] [1219:hso_std_serial_read_bulk_callback]: Actual length = 8<br>[ 7974.712188] <br>[ 7974.720672] hso[1220:hso_std_serial_read_bulk_callback]0d 0a 52 49 4e 47 0d 0a ..RING..<br>[ 7974.720703] [2069:put_rxbuf_data]: data to push to tty<br><b>[ 7974.726135] usb 2-2: hso received invalid serial state notification<br></b>[ 7974.732696] hso[1536:tiocmget_intr_callback]a1 20 00 00 06 00 02 00 0b 00 . ........<br><b>[ 7980.619812] usb 2-2: hso received invalid serial state notification<br></b>[ 7980.626403] hso[1536:tiocmget_intr_callback]a1 20 00 00 06 00 02 00 03 00 . ........<br>[ 7980.721954] [1219:hso_std_serial_read_bulk_callback]: Actual length = 8<br>[ 7980.721984] <br>[ 7980.730468] hso[1220:hso_std_serial_read_bulk_callback]0d 0a 52 49 4e 47 0d 0a ..RING..<br>[ 7980.730499] [2069:put_rxbuf_data]: data to push to tty<br><b>[ 7980.735900] usb 2-2: hso received invalid serial state notification<br></b>[ 7980.742462] hso[1536:tiocmget_intr_callback]a1 20 00 00 06 00 02 00 0b 00 . ........<br><b>[ 7981.419860] usb 2-2: hso received invalid serial state notification<br></b>[ 7981.426452] hso[1536:tiocmget_intr_callback]a1 20 00 00 06 00 02 00 03 00 . ........<br>[ 7987.059143] [1976:hso_std_serial_write_bulk_callback]: <br>[ 7987.064910] [1976:hso_std_serial_write_bulk_callback]: <br>[ 7988.661804] [1355:hso_serial_close]: Closing serial port<br><b>[ 7988.667510] [696:log_usb_status]: hso_std_serial_read_bulk_callback: received USB status - endpoint not enabled (-2)<br></b>[ 8054.969085] [1355:hso_serial_close]: Closing serial port<br>[ 8054.974822] [696:log_usb_status]: hso_std_serial_read_bulk_callback: received USB status - endpoint not enabled (-2)<br>[ 8054.986053] [696:log_usb_status]: hso_std_serial_read_bulk_callback: received USB status - endpoint not enabled (-2)<br>[ 8054.997283] [696:log_usb_status]: tiocmget_intr_callback: received USB status - endpoint not enabled (-2)<br><br></div><div>But this time the USB interface did not re-enumerate.</div><div><br><blockquote type="cite"><div><br>But I can confirm that the "NO CARRIER" message is there. And I also did<br>see it on an outgoing call if the called party ends the call. I.e. it comes<br>independently of who has initiated the call.<br><br>Both times the message appears on the /dev/ttyHS_Modem port.<br><br>It also works to answer an incoming "RING" with ATA and hang up<br>with AT+CHUP. If I do a AT+CHUP after "RING", the call is terminated<br>with a busy indication on the remote phone.<br><br>So the firmware bug may reduce to the modem sending the "NO CARRIER"<br>to the wrong interface. I.e.. the correct workaround is to monitor both and<br>merge the messages. Then, we don't need polling.<br><br>Nikolaus<br><br>_______________________________________________<br>Gta04-owner mailing list<br><a href="mailto:Gta04-owner@goldelico.com">Gta04-owner@goldelico.com</a><br>http://lists.goldelico.com/mailman/listinfo/gta04-owner<br></div></blockquote></div><br></body></html>