TNG & EPYGI: TNGEpygi service error Could not bind socket

[Belinda Frick]

TNGEpygiRadius.log:
2010-05-13 09:07:13.125 [1.0.2.11] -> StartupTCPServer : Set Default Port
2010-05-13 09:07:13.218 [1.0.2.11] -> StartupTCPServer : Create Bindings
2010-05-13 09:07:13.234 [1.0.2.11] -> StartupTCPServer : Set Functions
2010-05-13 09:07:13.234 [1.0.2.11] -> StartupTCPServer : Start Server :
2010-05-13 09:07:13.234 [1.0.2.11] -> StartupTCPServer : Started TCP Listen on port : 25001
2010-05-13 09:07:13.234 [1.0.2.11] -> StartupUDPServer : Set Default port
2010-05-13 09:07:13.234 [1.0.2.11] -> StartupUDPServer : Create Bindings
2010-05-13 09:07:13.234 [1.0.2.11] -> StartupUDPServer : Set Functions
2010-05-13 09:07:13.234 [1.0.2.11] -> StartupUDPServer : Start Server
2010-05-13 09:07:13.234 [1.0.2.11] -> StartupUDPServer : ERROR : Could not bind socket. Address and port are already in use.
2010-05-13 09:08:59.625 [1.0.2.11] -> Connected from : 192.168.4.1:1308

There is a Radius server that is used to give information
like start and stop of recordings, etc. It runs on UDP port
16014/16015.

You cannot run TNGEpygiRadius and this Radius server (standard protocol)
on the same server as they use the same UDP port:

2010-05-13 09:07:13.234 [1.0.2.11] -> StartupUDPServer : ERROR : Could not bind socket. Address and port are already in use.