Dialpeers
Dialpeer is route, it defines where to send call(to which termination gateway and contractor) and how much system owner have to pay for such terminated call.
- Id
Unique identifier.
- Prefix
This field is used for setting prefix for filtering dialpeers by destination number (number B). Dialpeer will be selected to the list of possible dialpeers for call routing only in case of matching this Prefix with first symbols of destination number.
Under bottom of this field information about according Network Prefix record (if any) is shown.
In case if two or more dialpeers from one Vendor will match the destination number by this parameter (prefix) only one Dialpeer will be selected for call routing on the basis longest prefix match algorithm.
TIP
You can enter two or more Prefixes that are separated by comma in this field. In this case Yeti will create two or more independent Dialpeers that are had same parameters.
INFO
Principles of matching Prefix field of Dialpeer and destination number (number B) could be found
here <prefix_truth_table.- Dst number min length
Minimum length of number for this Dialpeer. Dialpeer won't be chosen to the list of routing for the call where destination number (number B) length is less than value of this field.
- Dst number max length
Maximum length of number for this Dialpeer. Dialpeer won't be chosen to the list of routing for the call where destination number (number B) length is more than value of this field.
- Enabled
Calls are terminated only via enabled Dialpeers. A disabled Dialpeer is never used to send a call.
WARNING
Disabling a Dialpeer means "do not send this traffic to this Vendor", not "route calls as if this Dialpeer did not exist". The flag is checked after dialpeer selection, so a disabled Dialpeer still takes part in longest-prefix match and Exclusive Route processing, and it can hide other Dialpeers that match the same call. See Disabled Dialpeers in routing.
- Locked
Marks the Dialpeer as temporarily locked by the quality control mechanism (e.g. when ACD or ASR limits are exceeded). Whether a locked Dialpeer is excluded from routing depends on the Routing Plan sorting method: locked Dialpeers are skipped only in sorting modes that include ACD&ASR control. In sorting modes without ACD&ASR control (e.g. LCR, No ACD&ASR control), the Locked flag is ignored and the Dialpeer is still used. Like Enabled, this flag is checked after dialpeer selection, so a skipped locked Dialpeer is not replaced by a less specific Dialpeer of the same Vendor.
- Scheduler
Optional Scheduler that automatically enables or disables this Dialpeer based on configured time ranges. The Scheduler changes the same Enabled flag, so a Dialpeer disabled by schedule behaves exactly as a manually disabled one.
- Routing Group
Routing Group dialpeer belongs to.
Routing Tags can be selected from the list for adding additional routing issue to this Dialpeer.
- Routing tag mode
Routing tag comparison mode.
TIP
Read more about Routing Tags at Using Routing tags documenation
- Vendor
Contractor that acts as call termination provider(where call will be sent). Only Contractor that was marked as
Vendorcan be chosen in this field.- Account
Account of Contractor which will be used for billing.
- Priority
Value of this field (numeric) is used during building of Dialpeers rating (sorting of Dialpeers) for routing call.
WARNING
Dialpeers with biggest value of Priority will be put into top of rating and will be used first in routing set.
- Force Hit Rate
Value of this field (numeric between 0 and 1) is used during building of Dialpeers rating for routing call. It represents probability of putting this Dialpeer at the top of suitable routes.
- Exclusive Route
If during the routing process it turned out that there are entries in the set of suitable routes with the Exclusive route set - all routes without such flag will be discarded. This behavior allows to disable call re-routing for any direction, if there is an exclusive route for it.
WARNING
A disabled Dialpeer with this flag still discards all non-exclusive routes. If every matching exclusive Dialpeer is disabled, the call is left without routes. See Disabled Dialpeers in routing.
- Initial Interval
The starting interval from the start of the call in seconds (default 1). Allows to set another tariffication policy for starting a call (example: The first 5 seconds are free).
- Initial Rate
Rate (in currency units per minute) for tariffication during Initial Billing Interval.
- Next Interval
The subsequent interval of tariffication in seconds. With this interval, the charging step is defined (example Minute (60 seconds), Per second (1 second)).
- Next Rate
Rate (in currency units per minute) for tariffication during Next billing Intervals
- Lcr Rate Multiplier
Value of this field (numeric) is used during building of Dialpeers rating (sorting of Dialpeers) for routing call on the basis of least-cost routing (LCR). This value is used for multiplying Next rate value only during Dialpeers sorting and doesn't effect on final cost of call.
- Connect Fee
Fee (in currency units) for connection (it charges once per call) for this Dialpeer.
- Reverse billing
In case of enabling this flag call termination price will be subtracted from account balance. In normal mode (when this flag is disabled) money will be added to the account balance. See Billing documentation.
- Routeset Discriminator
Groups this Dialpeer with others that share the same Vendor and Routeset Discriminator for independent longest-prefix match during routing. See Routeset Discriminators for details.
- Gateway
Gateway that will be used for termination of the calls. Only gateways with enabled allow termination flag should be used there.
- Gateway Group
Gateway Group that will be used for call termination in case of using multiple gateways for traffic termination to the same Vendor.
- Valid From
Date and time from that this Dialpeer will be active and can be used for routing call.
- Valid Till
Date and time up to that this Dialpeer will be active and can be used for routing call.
- Acd Limit
The average call duration (ACD) limit for this Dialpeer (in seconds). Lower limit of the average length of telephone calls on this Dialpeer. If ACD for this Dialpeer will stay less than Acd Limit this Dialpeer will be excluding from call routing process.
- Asr Limit
The answer-seizure ratio (ASR) limit for this Dialpeer (in percents, where 1.0 = 100%, 0.5 = 50% etc). Lower limit of the percentage of answered telephone calls with respect to the total call volume on this Dialpeer. If ASR for this Destination will stay less than Asr Limit this Dialpeer will be excluding from call routing process.
- Short Calls Limit
The Short Calls ratio limit for this Dialpeer (in percents, where 1.0 = 100%, 0.5 = 50% etc). Lower limit of the percentage of answered telephone calls with length less than Short Call Length with respect to the total call volume on this Dialpeer. If this ratio for this Dialpeer will stay less than Short Calls Limit this Dialpeer will be excluding from call routing process.
- Capacity
Termination capacity limit for this Dialpeer. This value regulates maximum amount of concurrent calls that are allowed via this Dialpeer at same time.
- Src name rewrite rule/Src name rewrite result
Rewrite rules for SRC Name. See how to use POSIX Regular Expressions in Yeti. Both rule and result support call variables using
{{vars.name}}.- Src rewrite rule/Src rewrite result
Rewrite rules for SRC Number. See how to use POSIX Regular Expressions in Yeti. Both rule and result support call variables using
{{vars.name}}.- Dst rewrite rule/Dst rewrite result
Rewrite rules for Destination number. See how to use POSIX Regular Expressions in Yeti. Both rule and result support call variables using
{{vars.name}}.- External ID
Optional identifier used to reference this Dialpeer from an external system (e.g. rate management platform).
- Current Rate ID
Identifier of the currently active Dialpeer New Rate record, if a scheduled rate change is in effect.
- Created At
Date and time creation of this Dialpeer.
Disabled Dialpeers in routing
Yeti checks the Enabled flag at the end of dialpeer selection, not at the beginning. For every call the routing engine works in this order:
A disabled Dialpeer passes steps 1 and 2 like any other Dialpeer and is removed only at step 3. If it wins the selection, the Dialpeers it has displaced are not brought back — they were already discarded at step 2.
This is intentional. It allows to stop sending some traffic to a Vendor without deleting anything, and it guarantees that disabling a specific route never silently moves its traffic to a broader route of the same Vendor, which usually has a different rate.
Blocking a direction for one Vendor
Consider a call to 380441234567:
| Dialpeer | Vendor | Prefix | Enabled | Result |
|---|---|---|---|---|
| DP-1 | Vendor A | 380 | yes | shorter match, discarded |
| DP-2 | Vendor A | 38044 | no | longest match, then removed as disabled |
| DP-3 | Vendor B | 380 | yes | used |
DP-2 wins the longest-prefix match among Vendor A Dialpeers, so DP-1 is discarded. Then DP-2 is removed because it is disabled. Vendor A receives no calls to 38044, although DP-1 is enabled and matches the number. Calls to other 380 numbers are still sent to Vendor A via DP-1.
Longest-prefix match is performed per Vendor + Routeset Discriminator, so a disabled Dialpeer hides only Dialpeers of the same Vendor with the same Routeset Discriminator. Dialpeers of other Vendors are not affected.
Disabled exclusive route
The same call, but the disabled Dialpeer has the Exclusive Route flag:
| Dialpeer | Vendor | Prefix | Exclusive Route | Enabled | Result |
|---|---|---|---|---|---|
| DP-1 | Vendor A | 38044 | yes | no | removed as disabled |
| DP-2 | Vendor B | 38044 | no | yes | discarded as non-exclusive route |
Exclusive Route is evaluated across all matching Dialpeers of all Vendors, so DP-1 discards DP-2 and then is removed itself. No routes are left and the call is rejected with the No routes disconnect code (SIP code 404 by default), although Vendor B has an enabled Dialpeer for this number.
Removing a Dialpeer from routing completely
If other Dialpeers should take over the traffic, the Dialpeer has to stop matching calls at step 1. Disabling it is not enough:
- delete the Dialpeer, or
- set Valid Till to a date in the past — the validity period, unlike the Enabled flag, is checked before selection.
For a disabled exclusive route it is enough to clear the Exclusive Route flag: non-exclusive routes of other Vendors are used again, while the disabled Dialpeer keeps blocking less specific Dialpeers of its own Vendor.
TIP
Use Routing Simulation to check which Dialpeers are actually used for a call after changing the Enabled flag.
Dialpeer New Rates
New Rates are used for setting rates that will be applied for this Dialpeer via some period of time. You can set following parameters: Initial interval, Next interval, Initial rate, Next rate, Connect fee and choose time of applying of these New Rates. To create New Rates object for Dialpeer you should press New Rate button in the Dialpeer's view mode.