Incoming calls routed through - pbxes.org do not work properly

[GoogleCodeExporter]

NOTE: This form is only for reporting bugs. For problems, questions, or
comments, please visit:  http://groups.google.com/group/sipdroid-users

*************************************************
* Read the FAQ                                  *
*    Check if the bug has already been reported *
*        No doubles please                      *
*************************************************

Did you carefully read above and decide this means of communication is the
right for your notice? Don't just list an incompatible SIP server or
device, please. Try to look behind the scenes if you like to
contribute here. Thanks!

--
What steps will reproduce the problem?
1. Using PBXES.org for incoming calls
2.
3.

What is the expected output? What do you see instead?

When my number is dialed and I am routed through PBXES my calls should 
come through. They do not. If I make a call, hang up, I can receive a call 
if it is within a few minutes of making a call or forcing sipdroid to re-
register. If I change a setting in Sipdroid and it has to re-register with 
pbxes I can get a call but after a few minutes unless I change a setting 
in Sipdroid again, I cannot receive calls. all the while pbxes and 
sipdroid status show as connected. This is with 3G, WLAN over UDP or TCP 
doesn't matter. If the software isn't forced to re-register it does not 
send a signal to my phone for incoming calls.

What version of the product are you using? On what operating system?
this has been a problem from at least the last 4 builds. I am using 1.1.3 
of Sipdroid and Cyanogen Mod 4.1.999 but this has been on other mods and 
stock t-mo builds as well.

Which SIP server are you using? What happens with PBXes?
Sipgate trunks are setup with pbxes.

Please provide any additional information below.

For some reason pbxes does not keep the connection to sipdroid alive for a 
very long time. I can login to pbxes and watch the call process and see 
that everything is visually running as it should but the alert to sipdroid 
never gets through from pbxes even though the visual on the status page is 
showing that it is trying to ring the phone. If I change a setting in 
sipdroid such as changing from UPD to TCP sipdroid is forced to re-
register, the call will come through. Again, calls will only come through 
for a few minutes after a change is made in sipdroid causing it to "Wake 
UP" the connection to pbxes.
Right now I have pbxes bound to my own SIP server and login to my own 
server. This setup keeps the connection alive so the problem has to be 
between pbxes & sipdroid. I would consider purchasing a pbxes subscription 
but not if it can't keep my connections alive to sipdroid. I cannot be the 
only person having this problem. The fact that I have to run my own server 
to keep the connection alive is kind of silly. I wish this issue would be 
fixed once and for all. Thanks :-)

Original issue reported on code.google.com by BrianG...@gmail.com on 14 Oct 2009 at 11:12

[GoogleCodeExporter]

I'm having a similar problem: wether using PBXes or another proxy sip calls 
doesn't ring. I can correctly make 
calls but cannot receive. It's curious that both sipdroid and proxy status show 
as registered ok, but if I test I 
listen a ringing tone on the caller peer but it doesn't ring.

Original comment by nlagal...@googlemail.com on 5 Dec 2009 at 10:58

[GoogleCodeExporter]

Just a suggestion. It may be a NAT problem. I had the same problem using 
SipAgent instead of sipdroid and it 
ceased when I configured a STUN server.

Original comment by nlagal...@googlemail.com on 9 Dec 2009 at 5:34

[GoogleCodeExporter]

I had similar issues with pbxes not beeing able to receive incoming calls. 
(Probably
more like nlagalaye issue).

I tried SipAgent as well, but could still not receive calls.

Just now I read
http://pbx.i-p-tel.com/wiki/index.php/FAQ#Outgoing_calls_work_but_incoming_calls
_are_always_busy_or_answered_by_voicemail.
suggesting to save the extension again. Now I was able to receive with both 
sipdroid
and sipagent.

(I'm using 3g with danish 3 operator).

Original comment by baard.ma...@gmail.com on 9 Dec 2009 at 8:27

[GoogleCodeExporter]

I have exactly the same problem. pbxex.org/status shows my incomming call but 
it just
not triggers my sipdroid (1.2.4)on my Hero. No matter what i do and it is NOT a 
NAT
problem. It's keeping me busy for the last week and the strange thing is that 
it has
worked two times !? outbound is working great. 
Is this maybe indeed a pbxes free issue or just a sipdroid bug ?
Any help welcome, Thanks.

Original comment by hero.hol...@gmail.com on 3 Jan 2010 at 7:14

[GoogleCodeExporter]

I switched over to Voxalot.com and the problem is now gone! Has to be PBXES as 
far 
as I am concerned. Since signing up with Voxalot, all my calls ring through 
with no 
problems whatsoever! They allow TCP port 80 connections same as PBXES to save 
on 
battery power too. So far so good with them but I did have to pay $15.00 to be 
able 
to get what I needed though. I guess you get what you pay for.

Original comment by BrianG...@gmail.com on 5 Jan 2010 at 12:56

[GoogleCodeExporter]

Ok tanx BrianGNYC, have similar problems with the free VOX Basic. I will 
upgrade to
VOX Lite...

Original comment by hero.hol...@gmail.com on 12 Jan 2010 at 10:35

[GoogleCodeExporter]

i've got the same problem. is VOX Lite reliable?

Original comment by GLev...@gmail.com on 8 Apr 2010 at 10:02

[GoogleCodeExporter]

Issue 447 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 5 May 2010 at 7:28

[GoogleCodeExporter]

I really don't think the problem is from pbxes : i have the same without using 
pbxes
(with my SIP accounts, which btw work great on my laptop)

The only way i've found to make it work (before it's resolved in sipdroid), is 
to use
fring. The SIP add-on works well and I can receive calls. I honnestly don't 
like this
application (I have to open it each time i wanna dial a number without using my
cell), but it's working...

Hope this helped :)

Original comment by jeromecouzy on 7 May 2010 at 5:46

[GoogleCodeExporter]

I'm experiencing this problem quite consistently, so I think I can provide a 
lot of info.

I am using a Sprint Hero with Android 1.5 (stock) on Sprint/Boost.  The problem
happens in Siprdoid 1.4.7 beta and 1.3.7 beta.  The problem only happens over 
3G - I
have been unable to duplicate it over WiFi.  Sipdroid gets stuck in a mode in 
which
incoming calls fail to ring.  It happens most often when the incoming call 
comes into
a DID from the POTS network, though I have observed some instances of the 
problem
when receiving calls that were end-to-end VoIP.  Usually it's the second call 
since
Sipdroid was started that is the first to not ring, but I have also observed it 
not
ringing starting on the third through eighth incoming calls.  I can fix the 
problem
by forcing Sipdroid to re-register (by disabling and re-enabling the mobile 
network,
for example), or by restarting Sipdroid.  The problem happens using TCP and 
UDP.  The
problem happens with different SIP providers:  I've tried Gizmo5 without 
pbxes.org,
and Sipgate One via pbxes.org.  The problem happens with and without STUN.  The
problem happens with Sipdroid in the foreground and the background.

I can recreate the problem fairly consistently with this sequence:
* launch Sipdroid
* call my Sipgate One number from a POTS phone
* cancel the call from the calling phone after a few seconds (though the problem
occurs even if I answer it in Sipdroid)
* call my Sipgate One number again, from a different POTS phone (though calling 
from
the same POTS phone yields the same result)

The second call doesn't ring in Sipdroid.

Here's the weird part:  if I follow the above sequence, cancel the second call, 
wait
a few seconds, and then exit Sipdroid, I hear a couple seconds of Sipdroid 
ringing,
and the Sipdroid call-ended screen is displayed, showing the number of the 
second
caller.  So Sipdroid *did* know about that second incoming call.  It seems that 
the
call is getting stuck somewhere in the pipe, so to speak, but I don't know 
where.

I am providing a logcat log showing the entire sequence: launching Sipdroid; the
first call coming in; the second call coming in and failing to ring; and then 
exiting
Sipdroid and hearing a bit of ringing and seeing the call-ended screen briefly.

The logcat log is using the default logging level and queue.  I can easily 
provide
more detailed logging, if requested.

http://www-personal.umich.edu/~balazer/files/Sipdroid_Hero_problem/

Original comment by bala...@gmail.com on 10 May 2010 at 7:40

[GoogleCodeExporter]

I also have problems with receiving calls with Sipdroid on Samsung GT-I5700. 
I've 
setted up two extentions one for good old n800 and another for Sipdroid. Other 
side is 
gtalk running on PC with gtalk2voip enabled. So n800 can receive and send 
calls, but 
Sipdroid can only call. When i calling my account @pbxes.com from gtalk2voip 
n800 
start ringing, Sipdroid if unblocked silently shows the call. If i receive call 
with 
Sipdroid, n800 stop ringing, and it seems like Sipdroid is in call, but it 
isn't. No 
sound going in any direction and after 60 second gtalk2voip service drops 
connection 
with error - Reason = EndedByTransportFail.

Original comment by laplande...@gmail.com on 4 Jun 2010 at 8:38

[GoogleCodeExporter]

I have the same problem on Spica (I5700), can't answer incoming calls (sipdroid 
doesn't ring, but activating sipdroid i can see incoming call but after 
answering there is no voice in any direction), but after setting auto answer it 
works  fine when phone screen is activated.  

Original comment by m.k.szcz...@gmail.com on 8 Jun 2010 at 7:13

[GoogleCodeExporter]

After more testing with the CDMA Hero, the pattern is very clear:  ringing for 
incoming calls is delayed anywhere from 5 to 25 second, and sometimes it fails 
to ring altogether.  I've tried bunches of different SIP providers, with and 
without pbxes.org and Voxalot.  Also, I tried Linphone and got exactly the same 
results.  The problem is more likely to occur when the screen is off and when I 
haven't interacted with the phone for a while. If I am doing any kind of 
network streaming (playing a Youtube video, for example), the calls ring 
through instantly.

On the Samsung Moment, calls ring within 5 seconds every time.

I believe this is a problem with the CDMA Hero.  It seems like some portion of 
the phone gets put to sleep when data is not being sent, and nothing on 
Sprint's end can wake it up.  I speculate that this problem extends to other 
kinds of network applications on the Hero, but I haven't verified that. (delays 
of ~30 seconds would hardly be noticeable in Gmail, for example)

If there's a setting to change this behavior, I haven't found it.  I'm done 
with the Hero.

BTW the problems people are having with the Spica are unrelated.

Original comment by bala...@gmail.com on 18 Jun 2010 at 9:48

[GoogleCodeExporter]

i had the same problem as described in posts #10, #1 and #4.

Now after updating Sipdroid and Android-OS (and without altering the 
sip-setup), everything works flawlessly. incoming calls immediately ring.

Current setup: Nexus One with Android Froyo FRF72 and Sipdroid 1.5.2

Maybe this should be changed to fixed..

Original comment by Roderich...@gmail.com on 22 Jun 2010 at 3:55

[GoogleCodeExporter]

@Roderich...@gmail.com

Are use using TCP or UDP? I have noticed I have better reliability with 
incoming calls with a TCP connection to PBXes but have way better call quality 
on a UDP connection.

Original comment by tiber...@gmail.com on 24 Jun 2010 at 9:16

[GoogleCodeExporter]

@tibere86: I am using UDP over 3G without pbxes as proxy. Using a Nexus One now 
with Froyo FRF91 and sipgate. From my point of view the problem is solved.

Original comment by Roderich...@gmail.com on 4 Jul 2010 at 2:59

[GoogleCodeExporter]

I also have this problem. If I make an incoming call addressing it as follows; 
username@pbxes.org nothing happens.

If I make the same call but this time addressing it as: 
username@88.69.237:29881 the call is successful ?

Original comment by David.To...@gmail.com on 13 Jul 2010 at 4:05

[GoogleCodeExporter]

Issue 686 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 15 Oct 2010 at 9:29

[GoogleCodeExporter]

I've got the exact same problem :

Phone : Samsung Galaxy (GT-I7500)
Android : 1.6 (Galaxo 1.6.3.4)
SipDroid : 1.6.1 beta
SIP provider : OVH / pbxes.org
Network : WLAN (through Belgacom Bbox2)

All incoming calls fail.

I've tried the following configurations :
- direct connexion to my SIP provider using UDP
- connection through pbxes using UDP
- connection through pbxes using TCP

All these configurations works perfectly if I use Ekiga softphone on my laptop 
(which apparently always make a STUN call to detect public IP before 
registering).

Is there a way to put SIPdroid into debug mode to dump the SIP messages and see 
what goes wrong ?

Original comment by greens...@gmail.com on 26 Oct 2010 at 7:22

[GoogleCodeExporter]

Thankx, got this working by just re-saving my extensions

Original comment by Imperial...@gmail.com on 27 Oct 2010 at 7:43

[GoogleCodeExporter]

Hi,

I guess all of the above posts mention the SIPDRIOD working perfectly but later 
it dies.

The issue is that when SIPDRIOD registers with the SIP provider it uses UDP for 
the connection protocol. Which is connectionless. So it provides less standby 
time, or you can say network register time. Although the Client is connected to 
the network. But its not keeping a keep alive. Mostly the 3G network would 
suffer most as your device get a temporary keep alive (registered time) from 
the sip provider. So after that the trunk made earlier is finished. But as you 
already had registered you would show on the network.

So main issue being the UDP connection standby time drops and the device gets 
hung up. Mostly if it works, its good. But theoretically speaking there is no 
keep alive packets, so you would receive latency and dead connection issue.

Regards,

Original comment by etw...@gmail.com on 4 Jan 2011 at 9:20

[GoogleCodeExporter]

Can Someone advise me on how to get incoming calls to work, out going is 
working fine. Thanks for the help.

Original comment by gorham.c...@gmail.com on 12 Jan 2011 at 11:01

[GoogleCodeExporter]

Enabling the STUN server worked for me. Must have been a NAT issue.

Original comment by j...@jphein.com on 7 Feb 2012 at 4:21