Customer Interface
Customer Signup Module
The sign up pages are located in http://Server-IP/A2Billing_UI/signup/
A link to sign up can inserted on the customer log in screen by entering the URL in a2Billing.conf
All fields must be filled in, and each field is error trapped as far as is possible. When the customer completes sign-up, the next page shows their card number, card alias and password. Additionally, and email is sent to the new customer, the contents of which can be edited via the Admin interface under signup. Captcha has been enabled to reduce the possibility of web robots automatically signing up. Note that there are 6 digits to be entered, and they should be entered in lower case.
How the card is initially created, and how much credit, is defined in a2billing.conf If a card is issued with zero balance, then, the customer will need to logon to their customer interface and top up their account via the E-payment interface, or by some other method before they can make calls. If a SIP or IAX Client is created, then the client can connect their own VoIP device or software to the A2Billing platform. Point the client at the calling card URL, and set the username as the card number, and the password as the password issued by the system
Customer Interface
Introduction – Customer Interface
The A2Billing platform gives a customer interface where the customer can top up their account via the PayPal? gateway, inspect usage on the account, as well as launch call-backs, or even use the supplied web based Java screen phone. The customer pages are located at
http://Server-IP/A2BCustomer_UI/
The customer logs in with the Card Alias or email address, and their password, which were supplied during the signup process.
Note that to allow the customer to sign in, they must be activated. By default a2billing.conf is set to create a customer in a de-activated state.
Modules can be disabled through a2billing.conf if there are certain features that you do not want to offer your customer.
Account Info
Account info screen shows the details of the account and the balance on the card. If the payment gateway is enabled, then the customer can top up their account from this screen. The amount that the customer can top up is set in a2billing.conf.
From this screen, personal information can be updated by the customer.
SIP IAX Info
This shows the SIP and IAX settings that are required for an endpoint to connect to A2Billing. Copying and pasting the settings into FreePBX trunks or into sip or iax.conf makes it easy to configure asterisk. The default settings are set in a2billing.conf
Call History
Call history gives a list of calls that have been made through the system. There is an option to filter the calls, and to analyse them.
Voucher
Vouchers are created in the Admin interface, and can be sold via a retail outlet. The customer can enter the number on the voucher into this screen, and the card will be topped up to the value of the voucher.
There is now an IVR menu so that voucher top-ups can be added via the telephone.
Invoices
The customer can view their invoice, which has a number of graphs and analysis on the invoice. They can either download copy invoices, or see how much they have been charged for each individual call.
invoice Details
Lists unbilled calls
View Invoices
Lists invoice history
Current Invoice
Shows the current invoice
DID
Once DDI have been set up via the admin screens, customers can select their own DDI and point it at a number of their choice, or indeed, point the number at a VoIP client.
Additionally, numbers can be released
Speed Dial
The customer can create short code access numbers for numbers that they dial frequently. The number of speed dials that they can create is limited in a2billing.conf.
Ratecard
The rate-card with the cost of calls to the destinations are listed in this screen.
Simulator
The customer can simulate a call to a destination, so that they can work out the cost. This is sometimes easier that working through the rates in the previous screen.
Call-back
Trigger a call back through this screen. This option must be set up in Asterisk and in a2billing.conf.
The customer puts in the number they are at, and the number they wish to call, then clicks the launch button.
The customer should receive a call at their location and when they pick up the phone, they are connected to the dialled party.
Calls will be charged by adding up the price of the 2 legs of the call, and multiplying by the number of minutes that they are connected to the distant end.
Using this system with a mobile could save money while roaming abroad as it is often cheaper to receive a call on a roaming mobile than to make a call.
Web-Phone
The web phone is a screen phone written in Java which allows the customer to make calls on a computer equipped with a soundcard, microphone and speakers.
Add Caller ID
If an ingress number has been configured on the platform, the customer can dial in using DISA, and the system can recognise the CLI and use that for authentication rather than authenticating using their card number. The number of CallerID that can be added is set in a2billing.conf
Password
Change the password for logging into the customer GUI, This however does not change the password of the SIP/IAX authentication.
Logout
Logout will take the customer back to the login page. This is the recommended way of leaving the system, so that there is no possibility that a future user of the computer, say in an internet café can access the customer details
The Flags
The flags at the bottom of the page allow the system to display the customer screen in different languages.
