What I had wished I known before coming up with a naming scheme was a couple of things. If using the two interface approach, the only way to distinguish between inside ip and outside IP is split view DNS entries.
Also, your expressway hostname and domain must match the SRV records. You might be able to get away with aliases in the responses, but we weren't ready to risk it. We were on a tight timeline. https://www.cisco.com/c/en/us/support/docs/unified-communications/expressway-series/117811-configure-vcs-00.html HTH Sent from my iPhone On Sep 4, 2017, at 6:17 AM, Matthew Huff <mh...@ox.com<mailto:mh...@ox.com>> wrote: I’m about to deploy our first expressway cluster, what names do people use form expressway DNS names? _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
