A2BILLING DOCUMENTATION PDF
- December 24, 2020
A2Billing Flask API. Docs»; Welcome to A2Billing Flask API’s documentation! APIs Detailed Documentation · Usage API – Card Deploy A2Billing-Flask-API. Source Keywords a2billing, api, flask . Flexible & Fast Restful APIs framework for A2Billing powered. A guide to the basics of using A2Billing. This document may be distributed subject to the terms and conditions set forth in the Open Publication License, v or.
| Author: | Kagabei Dulkis |
| Country: | Laos |
| Language: | English (Spanish) |
| Genre: | Life |
| Published (Last): | 5 November 2010 |
| Pages: | 487 |
| PDF File Size: | 17.19 Mb |
| ePub File Size: | 3.47 Mb |
| ISBN: | 788-4-43142-337-6 |
| Downloads: | 66981 |
| Price: | Free* [*Free Regsitration Required] |
| Uploader: | Toll |
For each ratecard you will be able to create as many rates you want. For instance you can define that you can to bill the customer 0.
Welcome to A2Billing Flask API’s documentation! — A2Billing Flask API documentation
Standard process should be: This is similar to a account number webui pass: Tariffgroup is a set of ratecards hooked up together. Ratecards contain all the information about one or more destinations and the rates to those destinations to which you would like to provide a termination.
Ratecard A ratecard is set of rates rates are defined according to a dialing prefix, for instance Define if more that one call can be accept at the same time on this card currency: In that case, reset the flag to 0. Date when the first call has been make on this card enable expire: This chapter aims to help using the software. Define the date for the expiration, it works only if “enable expire” is set to “date expire” expiration days: We will try to describe interactions between entities and the different features available through the web interface.
A ratecard can have a “starting date” and an “expiration date”, you can also define a trunk by default and if no trunk is defined for a trunk, the ratecard default trunk will be used[[BR]].
This allow to a third party to use your service without having to authenticate each time. If you know something about administrators you will get an idea and that is enough.
There is an ACL admin which has limited access to the buttons on the right. Progressive rate aims to bill the customer at various rates according the duration of the call.
If you are defining a SIP trunk and the carrier needs authentication, remember to add the following configuration in sip. User Guide This chapter aims to help using the software. Here you define the different roles for different administrators.
If you dont know anything about administrators then Least Cost Routing – search the best termination with the cheaper cost for you buying rate. You can also specify the buying rate, i.
Least Cost Dialing – search the best termination with the cheaper cost for end-user selling rate Import Ratecard This module will allow you to import ratecard from a csv file! A ratecard is set of rates rates are defined according to a dialing prefix, for instance Finally select the csv files and click on the “Import Ratecard” button. This module will allow you to import ratecard documentatio a csv file! When defining your trunk configuration, you can take asterisk trunk configuration.
Documentation | A2Billing
Least Cost Dialing – search the best termination with the cheaper cost for end-user selling rate. If the system stops abnormally, it can happen that some customers won’t be able to use their cardnumber again. Simply put a card is a customer in your system. Then there is a daddy administrator, which has all the options, and can create acl administrators. You will have to define the ratecard name, the trunk to use and the different fields that you want to specify from your csv files.
Most of common integration would follow the next schema: Customers Billing Ratecard Trunk Call report Cront service oh i have to document this one too Administrator File manager Signup DID Then there is a daddy administrator, which has all the options, and can create acl administrators. The permissions can be granted for: Card properties Let’s try to make an non-exhaustive list of the card properties. The most basic entity is the trunk. Define the numbers of days for the expiration if if “enable expire” is set to “amount of days since first use” or “amount of days since creation” the following is information about the card holder: You have to insert the same name you use to define the trunk in asterisk.
A credit limit needs to be specified. Define how you want to enable the expiration of the card date, amount of days since first use, amount of days since creation. The CallerID Authentication is well-know in the callingcard business.
A2Billing Documentation
Entities interaction in the callingcard platform The graph above illustrates how the main entities interact together. Providers will be used to classify the trunk and to help with reporting. Cards have different properties but the main is the tariffgroup to which it is linked. As you probably discover, when you browse the card you have 2 particulars button at your disposal: If you are familiar with A2biling, it is the string that you give in the Dial application.
A ratecard can have a “starting date” and an “expiration date”, you can also define a trunk by default and if no trunk is defined for a trunk, the ratecard default trunk will be used[[BR]] TariffGroup?
Now you also have to assign it to a ratecard and a dial prefix. For ease of use, a trunk can be associated with a provider, Or as Areski would say:
/imgs.jusbr.com/publications/images/702f000ef23e43983b20dda089ba7cd9 "fotos marcos kitano matsunaga")
