We only use CLI. The only thing I can see that may be useful is the Fault and Performance management. And that is if you don't already have something in place that reads SNMP traps, syslog, or something like MRTG. What I've found is that we have to do very little tweaking of the default settings for the various configuration elements. Once you create it and get it working, you generally leave it be and just add new and nearly identical items every so often. For instance: new SIP trunking customers. The "core" side pretty much never changes unless we're demoing equipment adding new equipment. I've never felt like I'm missing out and all our other equipment runs largely off GUI. ---- Brandon Buckner Switching Technician / VoIP Admin Iowa Network Services brandonb at netins.com<mailto:brandonb at netins.com> ________________________________ From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Scott Berkman Sent: Friday, September 11, 2009 5:12 PM To: voiceops at voiceops.org Subject: [LIKELY JUNK][VoiceOps] Acme: EMS or CLI? So for all the Acme users out there, is the huge cost for the EMS worth it to you? How many people use CLI vs EMS for their day to day actions? Some things lend more towards CLI (linux, cisco, asterisk) and some things just lend more towards GUI (Metaswitch, Broadsoft, Sonus Insight). -Scott