What steps will reproduce the problem?
1. Boot up sip stack to asterisk
2. Take internet connection off line
3. Call stack.stop()
What is the expected output?
ws connection should be terminated and see the __tsip_transport_ws_onclose
event from sipml5.
What do you see instead?
ws continues to exist until some timeout period (unknown, seems random)
What version of the product are you using? On what operating system?
Mac OSX v10.9
Google Chrome v32
SIPML5 v1.3.203
Please provide any additional information below.
When the client loses internet connection, we want to teardown the stack. When
we do that, the ws continues to stay connected, and we fail to see the
__tsip_transport_ws_onclose until much later. If the internet connection comes
back before the ws_onclose fires, then when trying to boot the stack again, it
will fail to connect trying to use a new ws connection.
Original issue reported on code.google.com by jnichol...@fluentstream.com on 23 Jan 2014 at 8:25
Original issue reported on code.google.com by
jnichol...@fluentstream.comon 23 Jan 2014 at 8:25