Before you begin please read the FAQ!
Attention!
Don't post doubles!
Why is it important to find doubles?
Sipdroid is a community project. This is no dropbox for your personal
issue. You need to find others having the same problem to get it fixed. If
the problem has already been reported you add more details and ideas to the
existing discussion. If it has not been reported yet you include as many
background info as possible to give the community a chance to follow up on
it. No one will just sit there and try to replicate your setup. The root
cause of the problem will need to be identified to get it fixed.
How can I find doubles?
When clicking on issues tab there is a search box. Enter keywords for your
issue to find previous reports matching yours. Choose find all to match
closed tickets as well.
How can I investigate an incompatiblity?
Just mentioning a SIP server or device that does not interoperate with
Sipdroid won't help much because the developers might not have that
particular setup on hands. So you will try to add a SIP or logcat trace
from your network/phone to make a fix at all possible.
Did you carefully read above?
If yes, please fill out the following form and provide all necessary
details.
If not, you may continue in the Forum where you can discuss your problem to
clear things up before filing an issue report.
What steps will reproduce the problem?
1. Switch to airplane mode
2. Wait couple of hours
3. Check battery states
What is the expected output? What do you see instead?
What version of the product are you using? On what device/operating system?
Version 3.0
Which SIP server are you using? What happens with PBXes?
Pbxes.org
Which type of network are you using?
Hdspa
Please provide any additional information below.
Test with jelly bean, android 4.2
Original issue reported on code.google.com by justamai...@gmail.com on 19 May 2013 at 9:27
Original issue reported on code.google.com by
justamai...@gmail.com
on 19 May 2013 at 9:27