System information

The server can authenticate the user based on the following methods:
 ANI/CLI authentication: if the CLI is known and this method is allowed.
A number authentication can be used to try user authentication for a call coming from a traffic sender. If user is found with the actual A number then the
caller will be authenticated as the enduser, otherwise will be authenticated as traffic sender. In this case you can require a PIN number from the user.
Configuration options:
anumberhandling global configuration
• 0=disabled
• 1=only add
• 2= only accept
• 3=add and accept (default)
• 4=only a number access (no pincode request)
enableanumberlookup per user configuration. You need to set it to 1 for traffic senders.
A numbers can be also registered by the users on a web interface or by sending an SMS in the proper predefined format.
 PIN (calling-card) based authentification:
When the A number is not known or the A number based authentication is disabled, the IVR have to ask the user for a valid PIN code.
This can be done by the CallingCardAuthentication IVR action.
After the server collects the DTMF digits it will lookup the database for a valid user entry. The authentication can be based on username, password or
username+password or depending on the “callingcardauth” global config option which can have the following values:
• 0=pin field (default)
• 1=callingcard username
• 2= callingcard password
• 3= callingcard username+password
• 4=any username
• 5=any password
• 6=any username+password
• 7=any username+password or username+pin
• 8=username for callingcard and username+password or username+pin for other users (default)
• 9=pin
• 10=password or pin
• 11=all combinations
• 12=calling card username or any user username + password or username + pin (default)