w4a do not detect the closed server connection

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Connect with w4a to SIP server
2. Restart the SIP server
3. See the w4a still in "Connected" state

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

The expected is to catch the closed socket connection and move to Disconnected 
state

What version of the product are you using? On what operating system?
w4a v756
win7 64bit
firefox 16.x

Can provide any additional information upon request.

Original issue reported on code.google.com by sfinx.so...@gmail.com on 12 Nov 2012 at 10:04

• Merged into: w4a do not support OPTIONS (used for keepalive) #4

[GoogleCodeExporter]

This is expected for any VoIP client using unreliable connection (e.g UDP). 
It's possible to send keepAlive messages but I don't think it worth it

Original comment by boss...@yahoo.fr on 12 Nov 2012 at 10:10

[GoogleCodeExporter]

It is not related to keepalive at all - it is related to socket close event 
that is missed by w4a. The keepalive problem is separated w4a issue that will 
be posted in a few minutes.

Original comment by sfinx.so...@gmail.com on 12 Nov 2012 at 10:12

[GoogleCodeExporter]

Original comment by boss...@yahoo.fr on 12 Nov 2012 at 10:19

• Changed state: Duplicate

[GoogleCodeExporter]

"it is related to socket close event" -> UDP socket close at server side for 
signaling?

Original comment by boss...@yahoo.fr on 12 Nov 2012 at 10:20

[GoogleCodeExporter]

Don't forget that w4a use UDP instead of websocket transport which means no 
"close event" will be triggered.

Original comment by boss...@yahoo.fr on 12 Nov 2012 at 10:27

[GoogleCodeExporter]

This w4a bug is not related to signaling, more to keepalive one. Please see, 
for example :

http://stackoverflow.com/questions/4956940/how-to-know-socket-client-got-disconn
ected

Original comment by sfinx.so...@gmail.com on 12 Nov 2012 at 10:34

[GoogleCodeExporter]

Sorry but I don't understand what you are trying to demonstrate. Do you mean 
it's possible to now that the server is down when using UDP without sending any 
packet? Sorry to ask such trivial question but I'm a bit lost with the link 
you're providing which is about TCP.

Original comment by boss...@yahoo.fr on 12 Nov 2012 at 10:42

[GoogleCodeExporter]

Sure it is not existed for UDP - this "close" event need to be detected somehow.

Original comment by sfinx.so...@gmail.com on 12 Nov 2012 at 10:42

[GoogleCodeExporter]

Ok, seems like OPTIONS support from the server is sufficient here.

Original comment by sfinx.so...@gmail.com on 12 Nov 2012 at 10:53