Ah. Yes. That part from the conversation is coming back to me. Geeez. No real
way then, I’d there?
-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
SRV weights and priorities do influence the selection, but do not guarantee.
The accepting peer can pass to the other peer if the other peer is less
utilized.
Sent from my iPhone
On Jan 23, 2019, at 16:35, Lelio Fulgenzi
mailto:le...@uoguelph.ca>> wrote:
Gotcha. IIRC, you can’t put weight on
Well, ideally each inbound caller’s endpoint uses the same implementation of
DNS SRV as defined in RFC2782 and respects priorities and weights (my SIP SRV
targets the edge cluster FQDN).
And to your point, I can reliably control the edge that accepts the initial
inbound INVITE with SRV
Gotcha. IIRC, you can’t put weight on traversal neighbours.
So you can use dns srv record weights to pick the C out or the E in, but once
inside the cluster picking the next hop E (or C) is round robin.
Interested to hear comments.
-sent from mobile device-
Lelio Fulgenzi, B.A. | Senior
Is this for inbound B2B or for MRA?
If inbound B2B, it's more up to the caller's implementation of DNS. If the
caller is Webex, their may be some documented behavior out there somewhere.
On Wed, Jan 23, 2019 at 4:17 PM Ryan Huff wrote:
> I’m trying to guarantee an active/passive use case; so
I’m trying to guarantee an active/passive use case; so maintenance mode would
achieve that (or shutting one side down), but would require manual
intervention, and be as clunky of a work-a-round as it gets for a runtime
solution.
-Ryan
On Jan 23, 2019, at 16:00, Lelio Fulgenzi
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
I am also curious if there is any documentation for this. When I asked Cisco
HTTS support recently they said it is round robin. In my environment though I
see inbound B2B calls from Webex hitting the same CUCM Sub.
-Original Message-
From: cisco-voip On Behalf Of Ryan Huff
Sent:
