Stopped receiving inbound & making outbound calls

[GoogleCodeExporter]

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. Do not receive incoming ringtone, instead it goes to my Google Voice 
account's voice mail. Even when the Sipdroid status shows up & running as 
indicated by green dot in the notifications bar
2. When making outbound calls, unable to hear ringtone. PBXes status shows 
extension trying to make a call because it cannot connect through, I guess.
3. This was working until I upgraded my Google Nexus S to ICS from Gingerbread

What is the expected output? What do you see instead?
I was able to make & receive call on Sipdroid

What version of the product are you using? On what device/operating system?
Sipdroid installed on my Nexus S is 2.7, Nexus S Android version 4.0.4

Which SIP server are you using? What happens with PBXes?
pbxes.org. Within status against the extension it shows trying to connect

Which type of network are you using?
I'm try making this call on my wifi and Vodafone 2G

Please provide any additional information below.
The app works just fine. I'm able to make calls using my Google Voice through 
browser window. But when trying to connect through Sipdroid, I don't see any 
attempt to make a call within the GV call history. I have also bobsled and 
vonage app installed on my phone, not sure if it's conflicting with sipdroid 
port settings. But had that been the case, it should not allow me to connect to 
PBXes, which does show trying to make a call.

Kindly help, thanks in advance.

Original issue reported on code.google.com by ajay.v...@gmail.com on 16 Jun 2012 at 3:19

[GoogleCodeExporter]

The same thing just happened to me a few days ago on my Samsung GS2 Skyrocket.  
Something really funky must have happened when I got a regular incoming 
cellular call after I had just placed an outgoing call with SIPdroid.  It just 
stopped making and receiving calls after that.  Check the Call Monitor page of 
your PBXes.org account and check to see if it looks something like mine did.  
For some very strange reason, the extension I was using got stuck in a 
backwards loop.  When I made an outgoing call using SIPdroid, that would "hang 
up" the PBXes extension, and ending the call in SIPdroid would dial the number. 
 It made absolutely no effing sense, but that's what the log said.  So, I 
created a new extension in my PBXes account and pointed SIPdroid to that new 
extension, and that fixed it.  I still can't believe this was the root of the 
problem.  It pisses me off, actually.  I mean, how the hell does that even 
happen??  A compatibility conflict with another app seemed like a much more 
probable cause.  It might be a PBXes issue, or maybe it's a SIPdroid issue.  In 
either case, what a pain in the ass.  Hope that helps though..

I sure hope that an almighty dev looks into this. 

Original comment by cousini...@gmail.com on 2 Jul 2012 at 11:02

Attachments:

• Image.jpg

[GoogleCodeExporter]

Mine got fixed too on it's own, I didn't do anything. After the recovery from 
the recent outage at pbxes.org, it seems to have fixed the issue. It seems like 
something was not right between SIP exchange & Google servers. I'm sure 
somebody figured it out on complaint from one of the premium members..:-) 

Original comment by ajay.v...@gmail.com on 2 Jul 2012 at 11:14

[GoogleCodeExporter]

I too have been struggling to get sipdroid to answer calls. It seems to answer 
intermittently, and I can't seem to put settings in place to fix it. Anyone has 
success, post back here, I'll keep tweaking things and see if I can't get it to 
work!

Original comment by william....@gmail.com on 26 Jul 2012 at 10:26

[GoogleCodeExporter]

It sounds to me like you're experiencing a different issue than the one being 
described in this particular thread.  Think methodically about the problem 
you're having.  Establish tangible, quantifiable details about it (what happens 
exactly, and when, where, how does it happen), and then search the database 
here for existing issues that are more pertinent to the symptoms of your 
specific problem.  As a start, I'd recheck your Google Voicemail and forwarding 
settings.  These settings can mess with incoming calls.  Next, check the 
schedule settings in your PBXes account.  If your SIPdroid app isn't using UDP, 
I'd change that too.  TCP is generally not well-suited for time-critical data 
exchanges like voice/SIP conversations.. 

It could be any number of things, so the best thing to do is methodically 
troubleshoot the problem.  Establish the what (exactly), when, where, and how 
of the problem.  That will always lead you in the right direction..

Original comment by cousini...@gmail.com on 26 Jul 2012 at 11:41

[GoogleCodeExporter]

Thanks for the great suggestions cousini! There've been so many variables 
lately that its been tough to isolate an incident, but you're absolutely right, 
I need to start quantifying. Thanks for the tip on UDP as well!

Original comment by william....@gmail.com on 27 Jul 2012 at 2:46

[GoogleCodeExporter]

I started getting this error a few days ago. I have exactly the same pattern as 
cousini  on my PBXes Call Monitor page (see his screen capture, above). 
Unfortunately, creating a new extension did not fix the issue for me, and my 
new extension is also seeing the identical hangup-dial "backwards loop" 
described previously.

Original comment by dasar...@gmail.com on 5 Oct 2012 at 8:57

[GoogleCodeExporter]

It turns out I had to select "Submit and Start" in the Personal Data page on 
PBXes, after I defined my new extension. After that, sipdroid began working 
properly again, with the new extension.

Original comment by dasar...@gmail.com on 5 Oct 2012 at 9:33

[GoogleCodeExporter]

This appears to be a recurring issue with PBXes. I've now confirmed that simply 
selecting "Submit and Start" (after filling the password confirmation field) 
will correct the problem.

Original comment by dasar...@gmail.com on 14 Oct 2012 at 4:17

[GoogleCodeExporter]

Submit and Start on the pbxes Personal Data page fixed this issue for me. I did 
not change anything else or define any new extensions. Just log in to 
pbxes.org, goto the personal data page, confirm your password, and hit "Submit 
and Start" then things started working again.

Original comment by jim.stj...@meltwater.com on 29 Oct 2012 at 12:44

[GoogleCodeExporter]

Start and Submit worked for me as well. I was wondering why I wasn't getting 
any calls after the recent update. It happened once before whenever I first 
started using SIPdroid but I didn't know how to remedy the situation so I just 
deleted my pbx account and made a new one as well as re-installing SIPdroid. At 
least now I know what to do next time it happens. Thanks for pointing this out 
Dasar! 

Original comment by DuckussM...@gmail.com on 27 Apr 2013 at 4:58