a2billing has three basic ways to authenticate users when they reach the platform. CallerID, accountcode and PIN/Card Number.
By the default, the system will not prompt for the Card ID Number if:
- The call comes from a SIP or IAX device that can authenticate to the system (VoIP authentication). a2billing knows that the call comes from a legitimate device because it can find in the customer database the correspondent accountcode.
- The call comes from a VoIP terminal or other type of trunk technology that sends a customer associated CallerID. The usage of CallerID is necessary to provide automatic identification/authentication for users coming from PSTN/ISDN lines.
If CallerID or accountcode authentication does not take place, the user is requested to introduce the PIN number (Card Number/Account Number). It is important to notice that CallerID based-authentication is more insecure that a SIP or IAX2 challenge-response authentication.
The CID can be added to the system in a number of ways.
1. Manually via the Edit Customer's screen.
2. Manually via the this screen
3. Automatically added by the system depending on how you have set up the agi-conf in system settings.
An account can be created when a potential customer calls the access number for the first time, and the CID attached to that customer or the CID can be attached the first time that an existing customer calls in and enters their card number for authentication.
There are links on the far right of the page to: -
Edit the CID, activate it and de-activate the number
Delete the CID
Card to take you to the customer that has that callerID
To find a CID, the first few digits of the CID can be entered, and the syustem will return all CID that match the first few digits.
Note: In a2billing, Customer, User, Account Number, Card Number or PIN number are the same thing