Hello,
the documentation doesn't clearly state if a larger value for the priority field means that it gets used first before entries with smaller priority values are used - or vice versa.
It currently states:
“8” - select destination sorted by priority attribute value (serial forking ordered by priority).
and
priority: sets the priority in destination list (based on it is done the initial ordering inside the set)
This is just ambiguous. It should clearly say wether the list is processed in ascending or descending order for the priority value when using algorithm 8 (serial forking aka failover).
Regards, -Sven Neuhaus
Hello,
if you do:
kamctl dispatcher dump
the output shows the destinations in the order they are going to be used (first printed is going to be the first used).
Afterwards, making a pull request to clarify the priority order rule would be appreciated ;-)
Cheers, Daniel
On 16/07/15 11:13, Sven Neuhaus wrote:
Hello,
the documentation doesn't clearly state if a larger value for the priority field means that it gets used first before entries with smaller priority values are used - or vice versa.
It currently states:
“8” - select destination sorted by priority attribute value (serial forking ordered by priority).
and
priority: sets the priority in destination list (based on it is done the initial ordering inside the set)
This is just ambiguous. It should clearly say wether the list is processed in ascending or descending order for the priority value when using algorithm 8 (serial forking aka failover).
Regards, -Sven Neuhaus
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-
Daniel-Constantin Mierla -
Sven Neuhaus