hudamalmsteen / sipdroid

Automatically exported from code.google.com/p/sipdroid
0 stars 0 forks source link

Reregistration timer is too long (NAT) #72

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Sipdroid 1.0.0 on Rogers HTC Dream (Android 1.5)
2. Using PBXes trunked to CallWithUs (DID trunk)
3. Call DID number after half hour of no use.

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

The phone should ring, and the PBXes Status Monitor (Flash app in the Setup
section) shows that a call is started to the extension Sipdroid is
registered to but it is promptly hung up.

What version of the product are you using? On what operating system?

Sipdroid 1.0.0 on Rogers HTC Dream (Android 1.5)

Please provide any additional information below.

The problem is most likely (by my meager understanding of it) in the fact
that the NAT tables on the routers I use at work and at home (hp and cisco,
respectively) timeout faster than Sipdroid reregisters at PBXes, so when
PBXex calls out to the phone the NAT Translation that it made when it
initially registered is already gone.

I can confirm that restarting Sipdroid (turning WiFi off and on) allows
inbound calls again until a longer stretch of inactivity when it breaks again.

Suggestion: Give the user an option to modify the reregistration timer?

Original issue reported on code.google.com by ivan....@gmail.com on 13 Jul 2009 at 6:33

GoogleCodeExporter commented 9 years ago

Original comment by pmerl...@googlemail.com on 13 Jul 2009 at 6:38

GoogleCodeExporter commented 9 years ago

Original comment by pmerl...@googlemail.com on 4 Sep 2009 at 3:07