[cisco-voip] Expressway cluster algorithm

Lelio Fulgenzi lelio at uoguelph.ca
Wed Jan 23 16:00:27 EST 2019


I’m going to read the responses, but when I opened a TAC case, the engineer explained that there were at least two selection processes in play, which C (or E) to pick, then which neighbour to pick for the traversal.

She said, if you want to be 100% sure during troubleshooting, that you are testing a particular path, you want to put the nodes you don’t want to use into maintenance mode.

Made sense to me at the time.

-sent from mobile device-

Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1<x-apple-data-detectors://1/0>
519-824-4120 Ext. 56354<tel:519-824-4120;56354> | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Jan 23, 2019, at 3:19 PM, Ryan Huff <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>> wrote:

Can anyone explain or cite the documents that define the algorithm used to determine which Expressway node in a given cluster is selected to process a call.

You can influence the selection with DNS SRV priority and weight, but does not appear to guarantee which cluster node is selected each time.

Thanks,

Ryan
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190123/c719f5b3/attachment.html>


More information about the cisco-voip mailing list