Additional termination provider
In this Chapter we'll add additional local termination partner(Vendor 2) who providing route to 38048705 prefix with price $0.2 per minute. We also will provide better price to this destination for customer. Configuration based on Chapter 2 <quick_start_chapter2>
1. Creation of new Vendor and Account
At the first step we'll configure one additional Contractor <contractors> and Account <accounts> for it
+------------------+--------------------------+ | Object to create | Attributes | +==================+==========================+ | Contractor | - Name: Vendor2 | | | - Enabled: True | | | - Vendor: True | | | - Customer: False | +------------------+--------------------------+ | Account | - Name Vendor2 Account | | | - Contractor: Vendor2 | | | - Max Balance: 100 | +------------------+--------------------------+
2. Creation of new termination Gateway
At the second step we'll configure one additional termination Gateway <gateways> that will be linked to Vendor2
+------------------+------------------------------+ | Object to create | Attributes | +==================+==============================+ | Gateway | - Name: Vendor2 Gateway | | | - Contractor: Vendor2 | | | - Enabled: True | | | - Allow origination: False | | | - Allow termination: True | | | - Host: 129.0.0.1 | +------------------+------------------------------+
3. Creation of additional Dialpeer
At the third step we'll configure one additional Dialpeer <dialpeers> to route calls to prefix 38048705 via new termination gateway with price $0.2 per minute.
+------------------+------------------------------------+ | Object to create | Attributes | +==================+====================================+ | Dialpeer | - Prefix: 38048705 | | | - Enabled: True | | | - Routing Group: My RoutingGroup | | | - Vendor: Vendor2 | | | - Account: Vendor2 Account | | | - Initial Rate: 0.2 | | | - Next Rate: 0.2 | | | - Gateway: Vendor2 Gateway | +------------------+------------------------------------+
4. 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 | > 001234567890 | +---------------+----------------+ | > 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 Gateway C for termination the call. Full log of call processing also will be shown under the resulting records.
::: note ::: title Note :::
If you don't see necessary results, please, make sure that you enter everything correctly. :::