<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY>
Have you looked at all into the ACP-XML api? I have an old doc from 4.1 on it but haven't seen much since. Seems like it would be a great way to integrate larger scale Acme provisioning and management with a home grown system. <BR>
<BR>
<BR>
On Sat, 2009-09-12 at 19:10 -0700, David Hiers wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Acme is a victim of their own success on this one. It's so easy to
manage the SDs over the CLI for a handful of boxes, and it plugs into
our overall monitoring strategy so well that I've never thought of
what I'm missing with the EMS. Size matters, so if we had a oodles of
them it might be a different story.
Along these lines, has anyone ever cooked up a decent perl module to
work with the selecting and such needed to modify the config? It'd be
pretty sweet to can some module that can work with their CLI paradigm
as well as expect or net::telnet.
David
On Fri, Sep 11, 2009 at 3:44 PM, Brandon Buckner <<A HREF="mailto:BrandonB@netins.com">BrandonB@netins.com</A>> wrote:
> 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
> <A HREF="mailto:brandonb@netins.com">brandonb@netins.com</A>
>
>
>
>
>
> ________________________________
>
> From: <A HREF="mailto:voiceops-bounces@voiceops.org">voiceops-bounces@voiceops.org</A> [<A HREF="mailto:voiceops-bounces@voiceops.org">mailto:voiceops-bounces@voiceops.org</A>]
> On Behalf Of Scott Berkman
> Sent: Friday, September 11, 2009 5:12 PM
> To: <A HREF="mailto:voiceops@voiceops.org">voiceops@voiceops.org</A>
> 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
>
> _______________________________________________
> VoiceOps mailing list
> <A HREF="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</A>
> <A HREF="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</A>
>
>
_______________________________________________
VoiceOps mailing list
<A HREF="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</A>
<A HREF="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</A>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>