This feature is available from 1.0.2.7 and higher.
TNG stores the Epygi Authentication Codes in the Pin Code Field. (A code that is used to allow or prevent an user from using a phone)
From 1.0.4.3 and up, the EpygiDiscarded digits (Field 166) is now also available as the Pin Code.
To find the latest version of the TNGEpygiRadius service see install instructions - refer to forum post:
How to install the Epygi Radius service for TNG
To ensure that valid EPYGI Authentication codes is used, configure the codes in the INI section like the example below.
The section name must be [VALID ACCOUNTS] to have the Pin Code verified properly.
TNGEpygiRadiusService.ini
- Code: Select all
[VALID ACCOUNTS]
231
6808
In the above example
- The INI file must have the same name as the TNGEpygiRadiusService. If the service was renamed, the INI will have to be renamed too to have the same format.
- If 231 or 6808 are given to TNG by the Epygi as the Authentication code, the codes will be accepted. If any other value come through, it will be ignored and the pin code field will be cleared.
To use the EPYGI account code as the account code in TNG,
you need to swop it with the 'TNG' pin code.
- Scroll down to the COMMUNICATION CONFIGURATION section.
Enable the option to 'Swop account code and pin code fields' by clicking in the tick box.
Click on 'Apply changes' before exiting the page. - Configure the same account codes as per '[VALID ACCOUNTS]' section under 'User Configuration' to see user names for the pin code calls. If no user name configured it will show PLEASE ADD USER if a pin code was received. If it shows PLEASE ADD or the extension name, then no pin code was received.