In order to manage rates for destinations more easily, destinations are grouped, so that one rate applies for a group of destinations, not for one destination separately. (A Group can contain only one destination if necessary.) Destinations groups are for users, not providers, because providers need to have very exact rates for every destination.
Each group of destinations consists of several destinations described by prefixes. As an example, let's take Albania MOB. Here we have three destinations described by prefixes: 35538, 35568 and 35569. Each of these destinations is Albania MOB. Usually users do not care which MOB network they are calling, and for the less popular countries providers usually put one price on all destinations in that direction. It's the same here: We can put one price on all these three destinations grouped as "group Albania MOB".
Each rate for a destination group may have many rate details. This means: a destination group may have one rate, but this rate has many rate details (sub-rates). Each rate detail describes one interval of the call. If the first rate detail is RD1, the second is RD2, and so on, all calls can be expressed as RD1 + RD2 + .. + RDn. The number is finite. The rate detail can be seen as the time intervals for all call durations. The time interval could also be zero length. It is explained further below.
Each rate detail consists of the following parts:
- FROM – from which second the rate detail starts.
- DURATION – the length of this rate detail (interval).
- TYPE - minute or event.
- ROUND BY – in what intervals to round the time.
- RATE – the price per minute in this rate interval.
The type 'minute' describes an interval that lasts some time. This time is billed by rate and rounded accordingly. An Interval starts at FROM and lasts for DURATION seconds. The type 'event' describes a zero-length interval, which we call EVENT. This might, for example, be a connection fee. If the type is 'event', the rate detail has no DURATION (it's always zero) or ROUND BY fields.
NOTE: The same rules apply to Custom Rates for users.
The call should have 0.2 connection fee (regardless of the currency) and all other time must be billed by 6-second intervals with a rate of 0.1 per minute. Such a rate should be described like this:
The first 30 seconds of the call cost 0.1, the next time till 5 minutes is billed at rate 0.05 rounded by 30 seconds, and the remaining time is billed by rate 0.02 and rounded by 1 second.
The same example can also be described like this:
The rate for the call is 0.01 per minute rounded by 1s. The maximum price for call is 0.1.
The rate for the call is 0.01 per minute rounded by 1s. The first 15 seconds of the call are not billed.
When call duration is between 10 and 30 seconds, following formula is used to calculate price:
Period 1: 3/60*2=0.1
Period 2: 2/60*10=0.333
Period 3: 1/60*30=0.5
Total call price: 0.933
Charge call only longer then 8 seconds, with rate 0.1, increment 1s :
NOTE: Same can be done with Grace time
Import from CSV file
It is not possible to import (upload) Advanced rates from the CSV file directly.
But if you need to upload Rates for which you are planning to apply Advanced Rates:
- Create Wholesale Tariff.
- Import Wholesale rates to the newly created Wholesale Tariff.
- Transform Wholesale Tariff to Retail Tariff.
- Delete Wholesale Tariff.
- Apply Advanced Rates for Retail Rates
Where to find advanced rates
Allow users to see advanced rates