Hey Team,
We have 2 yeti sems servers as well as 3 Kamailio servers acting as load balancers. These Kamailio servers have been set up to proxy outbound calls in addition to inbound calls, using the “Term outbound proxy” option on the gateway.
Since we have 3 Kamailio servers to use as an outbound proxy but you can only specify a single term outbound proxy on a gateway, we have been setting up multiple copies of the same gateway just with different term outbound proxy inside a gateway group, then using the gateway priorities to choose the proxy server closest geographically to the other carrier using POP preference.
Just checking in case I’ve missed it somewhere, is there a better way of doing this with just a single gateway but multiple proxy server options? Or perhaps we have already found the best way of doing it.
Thanks!
There is no better way. What idea of having 3 proxies there?
Actually you can create DNS SRV record for your proxies and use it in yeti
Interesting suggestion, will try that out NAPTR/SRV records and see how it works. Thanks.
We have kamailio proxies in different countries/cities so would want to prefer the proxy closest to the other carrier’s servers but then fall back to other proxies in case the primary one we want to use is down.
It is not clear what problem you solving by this setup - it will not improve e2e latency.
Let’s say we have a kamailio proxy and a yeti node in Country A and another proxy + yeti node in Country B.
If there is call from Country A also going to a number in Country A, we can keep the call within the same country by using kamailio proxy dispatcher to select the local yeti node as first priority and then for the outbound leg use yeti gateway groups with POP preference or priority order to use the local proxy again which keeps the network path short and latency low. But, still good to have the proxy in Country B as a secondary option in the gateway group for high availability. Hope that makes sense.