> -----Original Message----- > From: Ken Diliberto [mailto:[EMAIL PROTECTED]
> On the surface, naming may sound trivial. When you're > dealing with users > and people paying your salary/consulting fees, it's not. > Offending the > wrong person because you named the server "Nag", "Chatterbox", > "ETPhoneHome", etc. can be very costly. > > You could use some of the following: > > PhoneSystem > PhoneManager > PhoneVoiceMail > CompanyPhone I named mine "dialtone". I try to give machines here names that relate to their purpose, but ones that aren't *too* software-specific, because renaming machines can be a pain. (For example, I'm reluctant to give names like "asterisk" or "squid" to machines, because what if I switch to some other package later?) I also came in when some machine names had already been established, so I didn't really have the option of using a cute, consistent scheme like some places do. So, for example, we have a proxy server named "gatekeeper", firewalls named "drawbridge" and "portcullis", and an AutoDesk Inventor Vault server named "edison". My users seem to be able to remember the names when they need to, which is the important thing. _______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
