Yeti Switch

Appearance

Gateway groups ​

Gateway group allows the use of multiple gateways for traffic termination to the same vendor. Yeti will load-balance calls between gateways within the same gateway group based on each gateway’s priority and weight.

To terminate calls using a gateway group, you should configure a Dialpeer to point to the gateway group instead of an individual gateway.

WARNING

Gateway group affects only traffic termination (legB).

Attributes ​

Id

Unique identifier.

Name

Unique gateway group name.

Vendor

Gateway group owner.

WARNING

A dialpeer pointing to a Gateway Group, the Gateway Group itself, and all gateways included in the Gateway Group must be linked to the same vendor.

Balancing Mode

Algorithm used for distributing calls between gateways in this gateway group.

Priority/Weigth balancing
Calls are distributed according to gateway priority and weight.
Priority/Weigth balancing. Prefer gateways from same POP
Gateways where POP = call POP are preferred.
Priority/Weigth balancing. Exclude gateways from other POPs
Gateways where POP != call POP are excluded from the routeset.

INFO

The call POP is determined by the location of the Yeti node processing the call.

Max Rerouting Attempts

Limits the maximum number of gateways within this gateway group that may be used for call routing.

Example ​

Yeti uses the DNS SRV algorithm to order gateways based on their Priority and Weight attributes.

Gateway group A contains four Gateways:

  • Gateway 1 (Priority 100, Weight 0, POP UA);
  • Gateway 2 (Priority 101, Weight 40, POP UA);
  • Gateway 3 (Priority 101, Weight 50, POP MD);
  • Gateway 4 (Priority 101, Weight 10, POP UA).

The algorithm of sorting Gateways (within selected Dialpeer) for terminating the call will consist from the following steps:

1. Gateways are sorted by Priority in ascending order ​

Intermediate results after this step:

  • Gateway 1 (Priority 100, Weight 0, POP UA);
  • Gateway 2 (Priority 101, Weight 40, POP UA);
  • Gateway 3 (Priority 101, Weight 50, POP MD);
  • Gateway 4 (Priority 101, Weight 10, POP UA).

WARNING

A lower priority value means a higher position in routing.

2. Random reordering based on Weight ​

Gateways with the same Priority value are reordered randomly according to their Weight. The idea of this step is to provide a different order for each new call, achieving load balancing. Intermediate results after this step:

  • Gateway 1 (Priority 100, Weight 0, POP UA);
  • Gateway 3 (Priority 101, Weight 50, POP MD);
  • Gateway 4 (Priority 101, Weight 10, POP UA);
  • Gateway 2 (Priority 101, Weight 40, POP UA).

3a. Prefer gateways from same POP ​

Imagine a call is processed on a Yeti node located in POP MD. If the gateway group balancing mode is Priority/Weight balancing. Prefer gateways from same POP, gateways with POP MD will be moved to the top of the list:

  • Gateway 3 (Priority 101, Weight 50, POP MD);
  • Gateway 1 (Priority 100, Weight 0, POP UA);
  • Gateway 4 (Priority 101, Weight 10, POP UA);
  • Gateway 2 (Priority 101, Weight 40, POP UA).

3b. Exclude gateways from other POPs ​

Imagine a call is processed on a Yeti node located in POP MD. If the gateway group balancing mode is Priority/Weight balancing. Exclude gateways from other POPs, gateways with other POPs (POP UA in this example) will be excluded from routing results:

  • Gateway 3 (Priority 101, Weight 50, POP MD);