EpygiRadius.log:
----------------
- Code: Select all
2010-08-10 14:22:22.006 [1.0.2.11] -> Remote Client Disconnected
2010-08-10 14:22:22.115 [1.0.2.11] -> Connected from : 10.10.10.35:52561
2010-08-10 14:22:22.209 [1.0.2.11] -> Remote Client Disconnected
2010-08-10 14:22:22.318 [1.0.2.11] -> Connected from : 10.10.10.35:52562
2010-08-10 14:22:22.412 [1.0.2.11] -> Remote Client Disconnected
TNG.log:
---------
- Code: Select all
2010-08-10 14:22:22:013 [1.0.7.0] - Disconnected from Network PBX
2010-08-10 14:22:22:115 [1.0.7.0] - TCPClient Connected to Network PBX 10.10.10.35:25001
2010-08-10 14:22:22:216 [1.0.7.0] - Disconnected from Network PBX
2010-08-10 14:22:22:317 [1.0.7.0] - TCPClient Connected to Network PBX 10.10.10.35:25001
2010-08-10 14:22:22:419 [1.0.7.0] - Disconnected from Network PBX
Try the following:
Run a 'netstat -nba' from the command line to see if any other applications is using the 25001 port. It must list the IP (not zeroes), else it can connect from any IP to port 25001
Run a 'telnet' to the Epygi service IP en port 25001.
If you receive a blank line and the cursor moves to the next line, it is because there is no data from the PABX. Telnet will check every second.
Please double-check that all your settings is correct on the PABX side,
see :How to install the Epygi Radius service for TNG
Check if the 'keep alive' options is ticked under 'Communication Configuration' on the 'Settings' page. Disable the current option and APPLY. Check if you now receive data in the TNGEpygiRadius log when making a test call.
EPYGI Radius was tested using the LAN option, WAN might give a different output.