Re: Dispatcher failover to the next least loaded destination

Henning Westerholt via sr-users <[email protected]>
Newsgroups gmane.comp.voip.ser
Message-ID <DB5PR07MB9453DC04456257FC8FECF79CBF24A@DB5PR07MB9453.eurprd07.prod.outlook.com>
Hello,

I haven't looked to the code, but I think it will just take the next entry from the XAVP. Maybe you can test it and report back.

Cheers,

Henning

> -----Original Message-----
> From: Ivan Ribakov via sr-users <[email protected]>
> Sent: Freitag, 25. Juli 2025 17:05
> To: [email protected]
> Cc: [email protected]
> Subject: [SR-Users] Dispatcher failover to the next least loaded destination
> 
> Hi all, I'm wondering if it is currently supported to perform failover while
> respecting the call load distribution algorithm.
> 
> What makes me doubt this is possible is the following wording in the
> documentation:
> 
> > The rest of the destination list is taken in order of the entries in set - anyhow,
> until a re-route to next destination happens, the load on each address can
> change.
> 
> >From it it's not clear if ds_next_dst() will simplify use next entry from the AVP
> list or if it will attempt to intelligently choose next entry from the AVP list
> taking into the account updated call load of the remaining entries.
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions -- sr-
> [email protected] To unsubscribe send an email to sr-users-
> [email protected]
> Important: keep the mailing list in the recipients, do not reply only to the
> sender!
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.