Google Code Exporter

``` [deleted comment] ```

``` Jeremy I just started to observe the high CPU consumption issue your indicated. Your script seems to work MUCH better :) THANK YOU! HOWEVER, its still not starting up...

``` Hello Steve, In order for services to start you need to tell them when to start (i.e. in which runlevel). On Ubuntu this is done with the update-rc.d command:...

``` Thanks Jeremy! I will try it now. Also, I wonder if there is some way to enhance the startup script to make sure that there are no left over...

``` Isn't this solved with the 2.5.0 release of webrtc2ip (r85)? That release fixes issue 13: http://code.google.com/p/webrtc2sip/issues/detail?id=13 Or is that a different issue? Jeremy ``` Original comment by `[email protected]` on...

``` I am currently running with 2.5.0. How rapidly should these connections be brought down after termination of webrtc2sip? I still receive these messages and observe connections still waiting to...

``` Jeremy "update-rc.d webrtc2sip defaults" Yes that resolved my statup issue with the init script thanks! ``` Original comment by `[email protected]` on 17 May 2013 at 3:26

``` Hello Steve, If there are no active TCP connections on 10060, immediately. If there are active connections it could take up to minute. I always make sure I kill...

``` You can actually adjust the length of the TIME_WAIT state. By default it's 60 seconds: cat /proc/sys/net/ipv4/tcp_fin_timeout 60 You could try setting tcp_fin_timeout to a lower setting to shorten...

``` An option would be to issue a tcpkill or cutter command before restarting webrtc2sip. I'm going to test this. So basically you terminate the WebSocket connections on the server...