FYI,<div><br></div><div>for those interested this issue has been identified and fixed with a simple patch: </div><div><br></div><div><a href="http://code.google.com/p/sipdroid/issues/detail?id=311#c2">http://code.google.com/p/sipdroid/issues/detail?id=311#c2</a></div>
<div><a href="http://code.google.com/p/sipdroid/issues/detail?id=311#c2"></a><br><br><div class="gmail_quote">On Fri, Feb 5, 2010 at 3:46 PM, Carlos Talbot <span dir="ltr">&lt;<a href="mailto:carlos.talbot@gmail.com">carlos.talbot@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><br>Anyone use sipdroid on their Andorid phone? For the most part it works with the exception of when using SIP over TCP. For some reason, after 30 seconds into a call FreeSWITCH sends a bye and drops the call. Why use TCP? The author claims significantly increased standby times using SIP TCP over 3g: <a href="http://code.google.com/p/sipdroid/wiki/NewStandbyTechnique" target="_blank">http://code.google.com/p/sipdroid/wiki/NewStandbyTechnique</a></div>

<div><br></div><div>According to Brian it might be because the phone is not setting a transport in the contact field and FS is falling back to UDP.</div><div><br></div><div>This is on r16557. Here&#39;s a sip trace along with call graph:</div>

<div><br></div><div><a href="http://pastebin.freeswitch.org/12064" target="_blank">http://pastebin.freeswitch.org/12064</a></div><div><br></div><div>regards,</div><div><br></div><font color="#888888"><div>Carlos</div>
</font></blockquote></div><br></div>