Closed GoogleCodeExporter closed 9 years ago
It looks like program is encountering accidental problem during re-registration
and..
it dosen't tries to register again (after first failure). Instead of that red
color is next to operator, and message says: "error while registering - bad
request"
Sme kind of auto retry (configurable? with retry limit) may solve that problem..
Original comment by kukuniun...@gmail.com
on 21 May 2011 at 5:00
In fact there is already something in the sip stack that does re registration
retries. By default it's 1 minutes. There is no ways to configure that for now,
but 1 minute is not so bad for a mobile where we have to take care about
battery on one hand and unstable connections on the other hand.
However, the root of your problem is more "why it fails to register?". Maybe if
you can collect logs (see how to collect logs wiki page), I could find some
clues.
Most of the time it's about the way the android OS manage sleep and connections
vs the way csipsimple is configured for availablity. (for example if you use
the wifi lock, or can depend of the wifi sleep policy configured on android OS).
Original comment by r3gis...@gmail.com
on 22 May 2011 at 9:00
Hello
I know that SIP "have to" re-register in some amount of time, but it looks
that sometimes
1) program fails to re-register in automatic way, it not happens often,
usualy once in 24-48 hours period
2) program stays in unregistered state unitl I press "accounts" and force
csipsiple to connect to op again
3) it happens on two phones, BOTH have "WiFi lock" enabled, and even one of
them have seperate option to "lock WiFi" in OS.
4) I may collect logs, if it's not extremly complicated, I'll do it.
I wouldn't anynoy You if ealier every other possible solution failed. In
every other aspect program works perfectly.
Original comment by kukuniun...@gmail.com
on 22 May 2011 at 10:04
Hello. I have the same problem as described.
Got the "error while registering" message. Then i just deactivate the
connection (button left of the status) and reactivate the connection and
Voilà! Got the "registered" status in green.
It started to do that since the last update. I reverted back to 0.02-02 r913
but no luck. Still the same problem
Original comment by patrick....@gmail.com
on 28 Jun 2011 at 2:29
Original issue reported on code.google.com by
kukuniun...@gmail.com
on 7 May 2011 at 1:16