Re: [cisco-voip] Naming conventions for Expressway-C / E

I try to stay away from uppercase, numbers and hyphens /special chars in hostnames (just superstitious like that). Example Edge: expedgea.domain.tld expedgeb.domain.tld This is the FQDN that will resolve to LAN2 on the inside with internal DNS and then the outside public address in external

Re: [cisco-voip] Naming conventions for Expressway-C / E

What about in a cluster? Would it be a good idea to name it: ny-expc-01.domain.com ny-expc-02.domain.com ny-expe-01.domain.com ny-expe-02.domain.com What about public/private

Re: [cisco-voip] Naming conventions for Expressway-C / E

Similar to Ryan, I usually try to include "expe" or "expc" as well when the longer name isn't allowed, depending on customers naming standards. Sent from a mobile device with very tiny touchscreen input keys. Please excude my typtos. > On Sep 4, 2017, at 7:05 AM, Ryan Huff

Re: [cisco-voip] Naming conventions for Expressway-C / E

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

Re: [cisco-voip] Naming conventions for Expressway-C / E

I usually keep the names, "edge" and "control" incorporated in them somehow. If I'm trying to save on typing and it's a single pair I might do, "expcontrol" and "expedge". With clusters, I'll add more to the name that denote its purpose or location. Thanks, Ryan On Sep 4, 2017, at 6:17 AM,

[cisco-voip] Naming conventions for Expressway-C / E

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 https://puck.nether.net/mailman/listinfo/cisco-voip