search

chitranshmathur01 / imsdroid

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

Connection Timeout #203

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Sign In to the IMS Core
2. wait 5 minutes
3. Sign Out from the IMS Core

What is the expected output? What do you see instead?
If I Sign In and after a few seconds Out everything is fine (checked with 
wireshark) and also communication is not a problem at the beginning.
But if I just sign In and do nothing, I could get no messages from the UE after 
5 minutes of just signed in. The trace has no more SIP messages.
Therefore on a sign Out the old binding is not deleted and you get a new one 
after a second sign in (now the account has 2 bindings) and so on.

What version of the product are you using? On what operating system?
actual version of IMS-Droid (imsdroid-1.2.366.apk) on Samsung Galaxy S I9000 
(andoid 2.2)
openIMS-core on openSuse

Please provide any additional information below.
It seems to me that doubango lost some connection information after a while. 
There is no NAT, the UE is connected over WLAN and in the same subnet of the 
core.

Original issue reported on code.google.com by arne.fel...@googlemail.com on 22 Mar 2011 at 2:41

GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 23 Mar 2011 at 8:34

GoogleCodeExporter commented 9 years ago 
Fixed by IMSDroid 2.0.431

Original comment by boss...@yahoo.fr on 13 Jul 2011 at 11:52