search

zjzhang-cn / imsdroid

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

keeps losing asterisk server #87

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.register with asterisk on local network
2.From asterisk log:
Oct 29 19:03:12] NOTICE[1674]: chan_sip.c:24694 sip_poke_noanswer: Peer 'droid' 
is now UNREACHABLE!  Last qualify: 194
[Oct 29 19:03:22] NOTICE[1674]: chan_sip.c:19523 handle_response_peerpoke: Peer 
'droid' is now Reachable. (148ms / 2000ms)
[Oct 29 19:04:26] NOTICE[1674]: chan_sip.c:24694 sip_poke_noanswer: Peer 
'droid' is now UNREACHABLE!  Last qualify: 148
[Oct 29 19:04:36] NOTICE[1674]: chan_sip.c:19523 handle_response_peerpoke: Peer 
'droid' is now Reachable. (13ms / 2000ms)
[Oct 29 19:05:40] NOTICE[1674]: chan_sip.c:24694 sip_poke_noanswer: Peer 
'droid' is now UNREACHABLE!  Last qualify: 13
[Oct 29 19:05:51] NOTICE[1674]: chan_sip.c:19523 handle_response_peerpoke: Peer 
'droid' is now Reachable. (153ms / 2000ms)

And imsdroid keeps registering and unregistering

3.But ping is <5ms. From the asterisk box:

ping droid
PING droid (10.10.11.5) 56(84) bytes of data.
64 bytes from droid (10.10.11.5): icmp_seq=1 ttl=64 time=3.29 ms
64 bytes from droid (10.10.11.5): icmp_seq=2 ttl=64 time=3.81 ms
64 bytes from droid (10.10.11.5): icmp_seq=3 ttl=64 time=2.38 ms
64 bytes from droid (10.10.11.5): icmp_seq=5 ttl=64 time=2.21 ms
64 bytes from droid (10.10.11.5): icmp_seq=6 ttl=64 time=2.50 ms

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

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

imsdroid-1.0.311-g729.apk

Please provide any additional information below.

Because it keeps losing the connection, calls keep getting dropped.

Maybe related, the first ping to the droid is sometimes > 100ms:

ping droid
PING droid (10.10.11.5) 56(84) bytes of data.
64 bytes from droid (10.10.11.5): icmp_seq=1 ttl=64 time=155 ms
64 bytes from droid (10.10.11.5): icmp_seq=2 ttl=64 time=2.40 ms
64 bytes from droid (10.10.11.5): icmp_seq=3 ttl=64 time=2.56 ms

Original issue reported on code.google.com by seandar...@gmail.com on 30 Oct 2010 at 12:18

GoogleCodeExporter commented 9 years ago 
So as I understand, Issue 85 can be closed?

Original comment by volkov.r...@gmail.com on 1 Nov 2010 at 9:48

GoogleCodeExporter commented 9 years ago 
I don't think it's related to imsdroid itself.
Is it possible to have network capture?

Original comment by boss...@yahoo.fr on 1 Nov 2010 at 6:49