I have experienced a situation where SER (0.9.1) has stopped processing all register requests. Note I am also running mediaproxy 1.3.0. TOP shows 8 ser processes running each using between 10-15% CPU. There is one zombie process which is shown as [SER] <defunct> when I do a ps ax. There are only 9 running processes (8 SER + top). This is a test server that is not doing anything else and I am simply trying to register 1 UA against it. The server was running fine for a few days and then suddenly went AWOL. I looked back through the log and found the following although I don't think this is causing the current problem Apr 25 20:36:51 beta mediaproxy[23057]: command request E4CFFBCB-05BF-4204-9F82-3AE0BB64F9F5(a)192.168.0.15 60.234.199.XXX:8000:audio 60.234.199.XXX beta.mydomain.co.nz remote 60.234.199.XXX remote X-Lite=20release=201103m info=from:beattiec@beta.mydomain.co.nz,to:beattiea@beta.mydomain.co.nz,fromtag:274519666,totag: Apr 25 20:36:51 beta mediaproxy[23057]: Traceback (most recent call last): File "/usr/local/bin/mediaproxy/modules/rtphandler.py", line 856, in __findRTPSlot dsock.bind((proxyIP, port)) File "<string>", line 1, in bind error: (99, 'Cannot assign requested address') Apr 25 20:36:51 beta mediaproxy[23057]: error: cannot create session for &#39;E4CFFBCB-05BF-4204-9F82-3AE0BB64F9F5(a)192.168.0.15&#39;.15': cannot find enough free ports for the media streams Any suggestions on what's the best way to try and find out what's causing it? Shouting "Stop" loudly did not work. Killing SER and starting again would probably work but I'd rather try to find out what went wrong. Maybe these are the pleasures of using a non-stable version? Regards Cameron