Origin based billing
In this Chapter we'll improve configuration that is described in Chapter 3 <quick_start_chapter3> above by adding origin based billing.
In our example Vendor 2(who providing route to 38048705 prefix) also want to accept international calls from France(country core 33) with price $1.5 per minute. We are going to sell such traffic(from France to 38048705 prefix) for $2.5 per minute to customer.
Orange line represent call routing logic for calls with France CLI to destination network 38048705.
1. Adding Areas and Area Prefixes
At the first step it is necessary to configure:
- two
Areas <areas>(one for France and one for Ukraine);
+------------------+---------------------+ | Object to create | Attributes | +==================+=====================+ | Area | > - Name: Ukraine | +------------------+---------------------+ | Area | > - Name: France | +------------------+---------------------+
- two
Area prefixes <area_prefixes>that should be associated withAreas <areas>{.interpreted-text role="ref"} above.
+------------------+---------------------+ | Object to create | Attributes | +==================+=====================+ | Area Prefix | > - Prefix: 380 | | | > - Area: Ukraine | +------------------+---------------------+ | Area Prefix | > - Prefix: 33 | | | > - Name: France | +------------------+---------------------+
2. Adding Routing Tag and Routing Tag Detection Rule
At the second step it is necessary to configure:
Routing Tag <routing_tag>to mark calls from France to Ukraine
+------------------+--------------------------+ | Object to create | Attributes | +==================+==========================+ | Routing Tag | > - Name: France_to_UA | +------------------+--------------------------+
Routing Tag detection Rule <routing_tag_detection_rules>{.interpreted-text role="ref"} to append routing tag to calls from France to Ukraine
+----------------------------+--------------------------------------+ | Object to create | Attributes | +============================+======================================+ | Routing Tag detection Rule | - Src Area: France | | | - Dst Area: Ukraine | | | - Tag Action: Append selected tags | | | - Tag Action value: France_to_UA | +----------------------------+--------------------------------------+
3. Adding Destination
At the third step we'll configure additional Destination <destinations> to charge customer traffic tagged as France_to_UA with different price.
+------------------+--------------------------------+ | Object to create | Attributes | +==================+================================+ | Destination | - Prefix: 38048705 | | | - Enabled: True | | | - Rate Group: My RateGroup | | | - Routing tags: France_to_UA | | | - Routing mode: AND | | | - Initial rate: 2.5 | | | - Next rate: 2.5 | +------------------+--------------------------------+
4. Adding Dialpeer
At the fourth step we'll add Dialpeer <dialpeers>{.interpreted-text role="ref"} to properly calculate price we have to pay to vendor for traffic from France
+------------------+------------------------------------+ | Object to create | Attributes | +==================+====================================+ | Dialpeer | - Prefix: 38048705 | | | - Enabled: True | | | - Routing Group: My RoutingGroup | | | - Routing tags: France_to_UA | | | - Routing mode: AND | | | - Initial rate: 1.5 | | | - Next rate: 1.5 | +------------------+------------------------------------+
5. Test the call
For the call testing it is necessary to fill Routing Simulation <routing_simulation> form and to press Simulate routing button.
+---------------+----------------+ | Field name | Value | +===============+================+ | > Remote ip | > 127.0.0.1 | +---------------+----------------+ | > Remote port | > 10000 | +---------------+----------------+ | > Src number | > 331234567890 | +---------------+----------------+ | > Dst number | > 380487050321 | +---------------+----------------+
As a result two records will be shown, where the first record is an actual record of Call Profile that will be send to the Yeti/SEMS node for making call. This Call Profile uses newly created Destination <destinations> as a basis for Customer's billing. Full log of call processing also will be shown under the resulting records.