On Sat, May 26, 2012 at 2:09 PM, R?gis Montoya <r3gis.3r at gmail.com> wrote: > There is several approaches to fix the issue in CSipSimple. One is to get > ticket 1049 of pjsua fixed. But there is other ways to do so, that would > involve some intelligence in the application layer to anticipate end of call > state. which intelligence could you imagine to apply here? > Besides, most of the time when you get this problem it's actually that you > are running some bad configuration. If there is a timeout, it means that > there is a problem somewhere. And in 99% cases it's something wrong with the > configuration. So if you get this problem each time you disconnect, you have > probably a *real* problem in the configuration that you should first try to > fix before thinking about modifying application. to my experience the application and the configuration works fine. in 2 out of 3 cases the speech quality is ok, and hangup works as well. in some cases it looks like some timeout occurs. in many of the cases the reason is just a temporary cut of the mobile internet line. this means a forcibly cut off line is "the normal case". i saw it happening also with collegues, using android, and some dellmont service, like actionvoip. or would you say these services are so low quality that it is pointless to adress it? > On 26/05/2012 10:49, rupert THURNER wrote: >> >> hi, >> >> there is a longstanding issue with CSipSimple not ending a call: >> http://code.google.com/p/csipsimple/issues/detail?id=386 >> as far as i understand it, when i press "end call", it sends this to >> the server, and does not get a reply, or not the appropriate reply. >> CSipSimple then just stays open and lets the user feel the whole >> timeout period. Given that sip over mobile internet is such an >> unreliable connection, a voip server has to deal with "dying" clients >> without saying "bye" all the time, and i am pretty sure this is >> properly implemented. so i was wondering why CSipSimple canont take a >> more aggressive approach and just ending the connection if the user >> desires to. >> >> the issue mentions that pjsip/pjsua should be responsible for this. i >> tried to find if there is already an issue, and found: >> http://trac.pjsip.org/repos/ticket/1049 >> does this match the CsipSimple issue? i am pretty sure there must have >> been some discussion about this in the past so bear if i did not find >> the correct one now ... >> >> rupert. >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing list >> pjsip at lists.pjsip.org >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20120607/d6f12278/attachment.html>
