In  VMukti CallShop you may define the different roles for different administrators. There is an ACL admin which has limited access to the buttons on the right. for example, i will create an admin incharge of creating trunks, another for setting rates on that trunk and so on and not all administrators need all of the options so might as well restrict them from poking around.

The permission can be granted for :

Then there is a daddy administrator, which has all the options, and can create acl administrators. If you know something about administrators you will get an idea and that is enough. If you dont know anything about administrators.

Create Customer:

Create Card:

Cards are the main element of the Calling Card Softwar, and may contain all the info about the customers (name, email, phone, etc. ) Simply put a card is a customer in your system.

Card Properties:
Let's try to make an non-exhaustive list of the Card properties.

 CallerID Authentication:

The CallerID Authentication is well-know in the callingcard business. This allow to a third party to use your service without having to authenticate each time. 

View Payment Methods :

Billing supports Paypal, Authorize.net and Moneybookers payment gateways.

Billing has a payment gateway integrated with PayPal. The settings for the payment gateway are configured within billing.conf text file and within this screen. Cards can be topped up via the customer web interface by pre-defined amounts, in virtually any currency In order to use PayPal, a business account has to be created in PayPal, who will then give you the appropriate settings to put into the system.

View Transactions : 

This screen shows the list of transactions made through the various epayment systems.

View Payment:

Viewing payments give a list of all payments received, and which card the payments were set against. Once the payment has been entered, there is no way to delete the payment, or to correct it, without editing the back end database. Therefore if a mistake has been made, a balancing payment must be made to correct the mistake.

Add New Payment:

As the title suggests, this screen gives the ability to add a new payment against a customer. The payments must be entered in the chosen base currency.

List Voucher:

Vouchers are a mechanism whereby customers can top up their cards by purchasing a voucher from a retail outlet. Vouchers are created with unique randomly generated numbers on them. The customer enters the voucher number into the customer graphical user interface, and the card is topped up by the value of the voucher. There is a link on the screen to export vouchers to a CSV file, which could be sent to a commercial printer to create scratch-off top-up vouchers.

Additionally, Billing can be configured to present an IVR menu, through which the customer can top up their card.  

Generate Voucher:

Generate vouchers is to bulk create a number of vouchers, which may be printed and sold to customers.

As you can see from the HIGHLY interactive diagram above, rate is the next most basic entity in the billing engine. primarily, with every trunk theres a rate associated. You can also specify the buying rate, i.e. : "your purchase cost that you need to pay to your voip-provider to let your platform call this destination..." Then we have a selling rate, which is how to bill the user. Progressive rate aims to bill the customer at various rates according the duration of the call. For instance you can define that you can to bill the customer 0.33dollars for the first 2 minutes and then you want to bill him 0.45dollars for the rest of the call.

Now you also have to assign it to a ratecard and a dial prefix.

RateCard:

A ratecard is set of rates (rates are defined according to a dialing prefix, for instance 44 : UK). For each ratecard you will be able to create as many rates you want. 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]]  

List RateCard:

Previously created rate cards can be listed and edited through this screen

Create New RateCard:

Create a new rate card, that is listed in the screen above. A descriptive name, a start date and an expiry date can be set, as well as the trunk to use. If no trunk is specifically defined, then the default trunk will be used. The DNID (Dialled Number Identifier) Prefix allows the definition of a rule to choose this particular rate card. DNID by default is set to all, to match every DNID. The DNID can be set to an individual number to always choose this rate card when the number matches.

Tariff Group:

Tariffgroup is a set of ratecards hooked up together. The calling card system will choose the appropriate rates according to the Tariffgroup settings (LCR or LCD).

LCR:

Least Cost Routing - search the best termination with the cheaper cost for you (buying rate)

LCD:

Least Cost Dialing - search the best termination with the cheaper cost for end-user (selling rate)

A rate-card has to be created first. A group can contain many rate-cards. Give the Group a descriptive name, and then select whether the rate should be chosen on the basis of LCR (Least Cost Routing) or LCD (Least Cost Dialling)

LCR will select a rate based on the cheapest carrier cost, whereas LCD will select the cost on the basis of the cheapest charge to the customer. There is an option to remove the international dialling prefix as some VoIP carriers do not require the leading 00 (0011 in the USA). If the prefix is removed, then the rate card dialling codes must be in the same format, for instance 441 for UK National calls rather than 00441 (0011441 for the USA).

This screen also allows the possibility of applying a Package Offer for a certain number of minutes to a destination.

List Call Plan:

Having created the Call Plan above, edit the Call Plan through this screen, and add in the rate card. That is to say, select individual previously created rate-cards and add them to the group.

Trunk and Provider:

The most basic entity is the trunk. If you are familiar with VMukti PBX, it is the string that you give in the Dial application. it can be IAX2, SIP, ZAP, or any other, according to the dial application format in VMukti PBX. if you arent familiar with VMukti PBX you are probably lost here.

For ease of use, a trunk can be associated with a provider, Or as Areski would say: "A provider is the company/person that provides you the termination. Providers will be used to classify the trunk and to help with reporting."

NOTE:When defining your trunk configuration, you can take VMukti PBX trunk configuration. You have to insert the same name you use to define the trunk in VMukti PBX. If you are defining a SIP trunk and the carrier needs authentication, remember to add the following configuration in sip.conf (or where you have defined the trunk, maybe sip_additional.conf if you are using AMP/FreePBX):