Additional Route
In this Chapter we'll improve basic configuration that is described in Chapter 1 above by adding new Dialpeers that will help to spend less money for calling to the alternative routes.
In our new example the same Vendor (Contractor B from basic configuration) proposed us special price for all calls that will be made to the numbers that start from 38048 (code of Odesa region in Ukraine).
1. Creation of additional Dialpeer
At the first step we'll configure one additional Dialpeer that should be associated with Routing Group, Vendor, Vendor's Account and Vendor's Gateway that were configured in Chapter 1 above. In our example we use 38048 as Prefix and we'll pay 0.5 monetary unit per minute.
| Object to create | Attributes |
|---|---|
| Dialpeer | Prefix: 38048 Enabled: True Routing Group: My RoutingGroup Vendor: Contractor B Account: Account B Initial Rate: 0.5 Next Rate: 0.5 Gateway: Gateway B |
2. Test the call
For the call testing it is necessary to fill 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 | 380487860570 |
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 has Initial and Next Rates of Dialpeer that was newly created. Full log of call processing also will be shown under the resulting records.