receive STUN ping error

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Use two gmail accounts. Login using the "call" example with different PC. Use 
the rtpdump samples included with libjingle as video/voice inputs.
2. Initiate a voice call
What is the expected output? What do you see instead?
always stun, like:
Jingle:Conn[rtp:0:stun:udp:60.209.248.166:5200->rtp:0:stun:udp:192.168.1.230:152
2|CR-|-]: UpdateState(): pings_since_last_response_=, rtt=3000, now=24760406
Jingle:Conn[rtp:0:local:udp:192.168.1.28:5199->rtp:0:local:udp:192.168.1.230:152
1|CRW|0]: Sending STUN ping HyVWLDDd44v7 at 24760406
Jingle:Conn[rtp:0:local:udp:192.168.1.28:5199->rtp:0:local:udp:192.168.1.230:152
1|CRW|0]: Received STUN ping response HyVWLDDd44v7, pings_since_last_response_=2
4760406 , rtt=0

What version of the product are you using? On what operating system?
libjingle-0.6.3  windows xp

Please provide any additional information below.

Original issue reported on code.google.com by zhengxue...@gmail.com on 12 Dec 2011 at 7:29

Attachments:

• error.txt

[GoogleCodeExporter]

This is not a typical stun ping error. From the error code it looks like a 
winsocket error. Error=10054 normally means an existing connection was forcibly 
closed by the remote host. This normally results if the peer application on the 
remote host is suddenly stopped, the host is rebooted, the host or remote 
network interface is disabled, or the remote host uses a hard close (see 
setsockopt for more information on the SO_LINGER option on the remote socket). 
This error may also result if a connection was broken due to keep-alive 
activity detecting a failure while one or more operations are in progress.

Original comment by jun...@google.com on 9 Feb 2012 at 5:24

• Changed state: Done