[cisco-voip] [EXT] Expressway cluster algorithm

[Ryan Huff]

Sent from my iPhone

> On Jan 23, 2019, at 15:34, Ryan Huff <ryanhuff at outlook.com> wrote:
> 
> Or, rather than fixed machine resources, could it be application resource logic (node with the most recent, least amount of calls.. etc)?
> 
> Sent from my iPhone
> 
>> On Jan 23, 2019, at 15:29, Ryan Huff <ryanhuff at outlook.com> wrote:
>> 
>> Thanks for responding!
>> 
>> “Lowest resource usage” is the most specific info I’ve ever found. Is that just CPU, or Mem or IOPS or any combo? And which of the “resource” metrics take priority in the decision?
>> 
>> Thanks,
>> 
>> Ryan
>> 
>>> On Jan 23, 2019, at 15:24, Jeffrey McHugh <jmchugh at fidelus.com> wrote:
>>> 
>>> From exp clustering guide: 
>>> 
>>> Neighboring Between Expressway Clusters
>>> You can neighbor your local Expressway (or Expressway cluster) to a remote Expressway cluster; this remote cluster could be a neighbor, traversal client, or traversal server to your local Expressway. In this case, when a call is received on your local Expressway and is passed via the relevant zone to the remote cluster, it will be routed to whichever peer in that neighboring cluster has the lowest resource usage. That peer will then forward the call as appropriate to one of its:
>>> ■
>>> locally registered endpoints (if the endpoint is registered to that peer)
>>> ■
>>> peers (if the endpoint is registered to another peer in that cluster)
>>> ■
>>> external zones (if the endpoint has been located elsewhere)
>>> For Expressway: Lowest resource usage is determined by comparing the number of available media sessions (maximum - current use) on the peers, and choosing the peer with the highest number. Peers that are in maintenance mode are not considered
>>> 
>>> 
>>> Jeffrey McHugh | Sr. Collaboration Consulting Engineer 
>>> 
>>> Fidelus Technologies, LLC
>>> Named Best UC Provider in the USA
>>> 240 West 35th Street, 6th Floor, New York, NY 10001
>>> +1-212-616-7801 office | +1-212-616-7850 fax | https://nam01.safelinks.protection.outlook.com/?url=www.fidelus.com&data=02%7C01%7C%7Ca2cd61d7048d4afb98d608d68170cfe5%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636838718849178018&sdata=IxL%2FSJK83B2mQG545Le3qssuCOftt83%2F0QQolzc8r4A%3D&reserved=0
>>> 
>>> Disclaimer - This email and any files transmitted with it are confidential and intended solely for the person(s) addressed to. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Fidelus Technologies, LLC. Warning: Although Fidelus Technologies, LLC has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
>>> -----Original Message-----
>>> From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Ryan Huff
>>> Sent: Wednesday, January 23, 2019 3:19 PM
>>> To: cisco-voip at puck.nether.net
>>> Subject: [EXT] [cisco-voip] Expressway cluster algorithm
>>> 
>>> 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
>>> https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7Ca2cd61d7048d4afb98d608d68170cfe5%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636838718849178018&sdata=8TCE6Oe71Y8smfXAbH8%2B47evW%2BKbM%2B2uYltLn1cuxFM%3D&reserved=0
>>>