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

[Matthew Huff]

What about in a cluster?

Would it be a good idea to name it:

ny-expc-01.domain.com<http://ny-expc-01.domain.com>
ny-expc-02.domain.com<http://ny-expc-02.domain.com>

ny-expe-01.domain.com<http://ny-expe-01.domain.com>
ny-expe-02.domain.com<http://ny-expe-02.domain.com>

What about public/private names?

On Sep 4, 2017, at 7:58 AM, Bill Talley <btalley at gmail.com<mailto:btalley at gmail.com>> wrote:

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 <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>> wrote:

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, Matthew Huff <mhuff at ox.com<mailto:mhuff at 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 at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
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