Difference between revisions of "VOIP Billing"
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | Click Here to return to the main Screen: '''[[Main Page |Back]]''' | |
| + | |||
| − | + | Sky DANCE Billing is a fully integrated Billing Solution for Sky DANCE based on the ASTPP project. It supports pre-paid and post-paid billing with call rating and credit control. It also provides many other features such as calling cards, least cost routing (LCR), did management, resellers management etc. | |
| + | |||
| + | |||
| + | General Theory: | ||
| + | You will be considered the admin and will be working with providers, resellers and customers. Customers who don't have a reseller are considered your direct customers. - reseller ID - 0 | ||
| + | |||
| + | 1. You will need to setup different accounts: | ||
| + | a) Provider - that is to track your costs | ||
| + | b) Customer or Reseller or both - that is to track your income. | ||
| + | |||
| + | 2. You will need to setup rates for termination - these are the rates your providers charge you. These will be attached to a RG_xx where xx is the Sky DANCE resource group. | ||
| + | 3. You will need to setup rates for origination - these are the rates you will charge your customers or resellers. These will be attached to a rate group which is attached to the outbound resource groups you setup in #2. | ||
| + | 4. Account codes can be set at the resource group level, attached to a specific ANI or attached to a specific extension. The priority is extension, ANI, resource group if there is overlap. | ||
| + | |||
| + | The sky_prepaid.lua script is used to integrate billing into the dialplan and should be integrated into the create_b_leg in the skydance.xml dialplan and also whenever you dial outbound from an extension. | ||
| + | |||
| + | If you don't provide an account number to sky_prepaid.lua, it will try to determine it based on either the ANI or if not from that it will get it from the inbound resource group associated with that call. | ||
| + | |||
| + | You will need to setup a RG_xx entry for each resource group you will be tracking. Outbound resource groups will have the provider account code and inbound resource groups will have the customer/reseller account code. | ||
| + | |||
| + | Note: You will actually need to login as a given reseller to create customer accounts for that reseller. The only accounts you see are ones that belong to you - provider, customer, reseller for the admin user or just reseller and customer for the reseller user. | ||
| + | |||
| Line 13: | Line 35: | ||
[[Reports]] | [[Reports]] | ||
| − | [https://astpp.readthedocs.io/en/v3.6/Modules/modules.html ASTPP docs] | + | [https://web.archive.org/web/20190603115610/https://astpp.readthedocs.io/en/v3.6/Modules/modules.html See complete ASTPP docs] |
Latest revision as of 10:01, 17 January 2023
Click Here to return to the main Screen: Back
Sky DANCE Billing is a fully integrated Billing Solution for Sky DANCE based on the ASTPP project. It supports pre-paid and post-paid billing with call rating and credit control. It also provides many other features such as calling cards, least cost routing (LCR), did management, resellers management etc.
General Theory:
You will be considered the admin and will be working with providers, resellers and customers. Customers who don't have a reseller are considered your direct customers. - reseller ID - 0
1. You will need to setup different accounts: a) Provider - that is to track your costs b) Customer or Reseller or both - that is to track your income.
2. You will need to setup rates for termination - these are the rates your providers charge you. These will be attached to a RG_xx where xx is the Sky DANCE resource group. 3. You will need to setup rates for origination - these are the rates you will charge your customers or resellers. These will be attached to a rate group which is attached to the outbound resource groups you setup in #2. 4. Account codes can be set at the resource group level, attached to a specific ANI or attached to a specific extension. The priority is extension, ANI, resource group if there is overlap.
The sky_prepaid.lua script is used to integrate billing into the dialplan and should be integrated into the create_b_leg in the skydance.xml dialplan and also whenever you dial outbound from an extension.
If you don't provide an account number to sky_prepaid.lua, it will try to determine it based on either the ANI or if not from that it will get it from the inbound resource group associated with that call.
You will need to setup a RG_xx entry for each resource group you will be tracking. Outbound resource groups will have the provider account code and inbound resource groups will have the customer/reseller account code.
Note: You will actually need to login as a given reseller to create customer accounts for that reseller. The only accounts you see are ones that belong to you - provider, customer, reseller for the admin user or just reseller and customer for the reseller user.
Calling cards Least cost routing (LCR) DID management Multi level Reseller management Customer management Invoices and Billing Rates management Reports
See complete ASTPP docs
