Yes this is normal with TCP socket connections.
FreePBX makes hundreds of calls to the Asterisk Manager Interface each
time you browse the web interface in order to get the extension's status,...
Once it disconnects the TCP socket, the socket goes into a waiting
period before being removed and this is what you see on your netstat report.
You may browse the web to see if you can reduce the time to wait, but I
wouldn't worry about it.
Cheers.
Stephan Monette
Unlimitel Inc.
Tel.: 613-688-6212. x221
TF : 1-877-464-6638, x221
FAX : 613-482-1077
Andre Courchesne wrote:
Hi,
Anyone has any ideas why I would have MANY such TIME_WAIT pilling up
when doing netstat -a ?
tcp 0 0 localhost.localdomain:5038
localhost.localdomain:46965 TIME_WAIT
tcp 0 0 localhost.localdomain:46967
localhost.localdomain:5038 TIME_WAIT
tcp 0 0 localhost.localdomain:5038
localhost.localdomain:46963 TIME_WAIT
tcp 0 0 localhost.localdomain:46966
localhost.localdomain:5038 TIME_WAIT
tcp 0 0 localhost.localdomain:5038
localhost.localdomain:46964 TIME_WAIT
tcp 0 0 localhost.localdomain:5038
localhost.localdomain:46962 TIME_WAIT
tcp 0 0 localhost.localdomain:46961
localhost.localdomain:5038 TIME_WAIT
The only AMI application running is when freePBX is used.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
