Google Voice incoming calls through Pbxes work only once via WiFi, then re-registering is needed

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install sipdroid 1.5.7 beta on Android 2.2 and connect it to a Pbxes account 
that is configured to receive incoming calls via a phone number
2. Make sure your phone is connected via WiFi
3. Initiate a Google Voice callback (via either an app on your phone or the 
Google Voice web site on your PC) between the Pbxes phone number and some other 
US phone number as a test
4. Sipdroid will ring and connect the call successfully
5. Hang up the call in Sipdroid
6. Try to initiate another Google Voice Callback
7. Sipdroid will not ring

What is the expected output? What do you see instead?
- The expected output is that sipdroid would ring and be able to connect calls 
after the first one

What version of the product are you using? On what device/operating system?
- 1.5.7 beta, HTC Dream w/Android 2.2

Which SIP server are you using? What happens with PBXes?
- Pbxes

Which type of network are you using?
- WiFi

Please provide any additional information below.
- It is important to note that this problem only occurs with both:
a) Google Voice callback incoming calls
b) Via WiFi

If I call my Pbxes number from another phone, I can call any number of times, 
and each time it will ring in Sipdroid successfully, even over WiFi.

If I shut off WiFi and use 3G, I can initiate a Google Voice callback any 
number of times, and it will ring in Sipdroid successfully.

The only workaround is to cause sipdroid to re-register with pbxes by either 
restarting it or changing a setting that causes it to re-register.

I have also noticed by monitoring the pbxes status page that when this problem 
occurs, pbxes does not show the call as ending when the sipdroid client ends 
the call.  Pbxes still shows it as in progress for about 1.5 minutes after 
sipdroid ends the call, but even after this point, a new call cannot be 
initiated.

Via 3G, or when not using Google Voice, pbxes shows the call as terminating 
immediately upon it being ended from sipdroid.

Original issue reported on code.google.com by clo...@gmail.com on 6 Sep 2010 at 8:58

[GoogleCodeExporter]

Some additional notes:
- it does not actually have to be a Google Voice *callback* for this problem to 
occur.  Using the newly-available Gmail "call phone" service, I can directly 
call the pbxes number from within Gmail, and the same problem occurs.

- as I said above, when this problem occurs, the pbxes status page indicates 
that the call does not end until about 1.5 minutes after sipdroid ends it.  I 
think what is going on is that the number that I am connected to is an 
automated system that terminates the call after 1.5 minutes of inactivity.  If 
I directly call my pbxes number from Gmail, I can see that sipdroid ending the 
call will not cause pbxes to show it as ended, but if I terminate the call from 
the other end (gmail), then it shows as terminated in pbxes

Original comment by clo...@gmail.com on 6 Sep 2010 at 9:15

[GoogleCodeExporter]

Other SIP clients do not present this problem, either on the phone or on a PC.
For example, performing the same test with fring as a client on the same phone 
will allow multiple calls to connect without issue.  Performing the same test 
with Linphone as a client on a PC will allow multiple calls to connect without 
issue.

Original comment by clo...@gmail.com on 6 Sep 2010 at 9:17

[GoogleCodeExporter]

I have also tried using the Gmail "call phone" service from an account other 
than my own.  Same problem.

To elaborate on the sequence events some more:
- It is only after the first incoming call from Google Voice (callback or Gmail 
"call phone") that the problem occurs
- I could call into sipdroid many times successfully, but then after the first 
Google Voice incoming call, no other incoming calls will ring, whether they are 
from Google Voice or not

Original comment by clo...@gmail.com on 6 Sep 2010 at 9:39

[GoogleCodeExporter]

Try a different port number. This might be related to a SIP ALG in your Wifi 
router.

Original comment by pmerl...@googlemail.com on 17 Sep 2010 at 7:48

[GoogleCodeExporter]

Original comment by pmerl...@googlemail.com on 19 Mar 2011 at 2:51

• Changed state: FutureRelease

[GoogleCodeExporter]

Original comment by pmerl...@googlemail.com on 25 Mar 2011 at 11:23

• Changed state: Fixed