Closed GoogleCodeExporter closed 9 years ago
It could be interesting if you can collect logs (there is maybe more error
details from server when it replies with "internal server error").
See http://code.google.com/p/csipsimple/wiki/HowToCollectLogs?wl=en
From description what I can tell is that if the app shows "internal server
error" it's because sip server reply "internal server error" and encounter an
internal server error. So logs from sip provider side could help to understand
what is going wrong.
Most of the time "internal server error" is something with configuration (for
example having the account configured as proxy while not supported by sip
server) or something with some SIP feature not supported properly by sip
server. (Normally all sip features not understood by a sip server should be
gracefully ignored, but some sip server implementation are buggy).
However, in that case this is 100% reproducible.
So some more random root cause is too find. So another problem that could be
encountered is when sip server only allows limited number of registration and
refuse any new registration if already has too many registrations ongoing. (A
good behavior is usually to disconnect the oldest one or refuse with a clear
message about that).
This situation happens if the application gets killed brutally or if lost
network brutally. In this case the application is not able to un-register
properly (obviously there is no network or were killed). And will be able to
register again only when older previous registration will expire.
If this last point is actually the problem, there is some workaround expert
options available in csipsimple account settings (not sure it works with an
"internal server error" however)
Original comment by r3gis...@gmail.com
on 1 Oct 2012 at 6:24
Hi R3gis, I am waiting for the sip provider to send me a log.
Strange enough, the service has been working all day today, no problems.
No word from sip provider until now, Ill let you know.
By the way, you have a 5 star+ software, its incredible, thanks a lot!
Original comment by prad...@gmail.com
on 3 Oct 2012 at 1:56
Seems to be a configuration issue. I called technical support and they helped
me. I wrote a tutorial on how to configure CSipSimple (in spanish):
http://cjenkins.wordpress.com/2013/01/11/configurar-csipsimple-para-callmyway-vo
ip-costa-rica/
I can make calls, but not receive. I'm still working on it, I think is another
configuration setting. This bug should be closed I think.
My system:
- Samsung Galaxy Player 5.0
- Android Gingerbread 2.3.5
- CSipSimple 0.04-04 r1916 with codec pack.
Original comment by car...@jenkins.co.cr
on 11 Jan 2013 at 5:56
@carlos :
I switch the issue to accepted as wizard enhancement.
Let me know when you find the way to receive the calls.
Some point about the tutorial, you don't need the codec pack for g729. It's in
the main app ;). (the pack contains opus, g726 and codec2)
About the incoming call problem, I can suggest you to follow steps of this wiki
entry :
http://code.google.com/p/csipsimple/wiki/FAQ?wl=en#I_receive_calls_twice_/_Regis
tration_is_done_on_the_sip_server_t
(the entry about double registrations).
Sometimes the method used results in having server lost when they don't support
inline unregistration. Regarding description and solution it is probably the
case for this provider.
It could be interesting to test latest nightly build too :
http://nightlies.csipsimple.com/trunk/
Original comment by r3gis...@gmail.com
on 11 Jan 2013 at 6:41
This issue was closed by revision r2141.
Original comment by r3gis...@gmail.com
on 23 Feb 2013 at 11:53
Original issue reported on code.google.com by
prad...@gmail.com
on 1 Oct 2012 at 5:49