[asterisk-dev] [Code Review] Channel Redirect CLI command

Tzafrir Cohen tzafrir.cohen at xorcom.com
Sat Dec 13 11:48:22 CST 2008


On Sat, Dec 13, 2008 at 06:18:53PM +0100, Johansson Olle E wrote:
> >
> > (I also don't remember the discussion where we were trying to move  
> > away
> > from this type of functionality; do you have a thread you can direct  
> > me to?)
> >
> I can't point you to a specific message, but we did decide to  
> deprecate the "consise"
> CLI's because we felt that we did want to move API-like stuff to  
> manager and keep
> commands for admin usage in the CLI. I don't see many cases where you  
> have an
> operator or receptionist sitting at the CLI monitoring calls and doing  
> a redirect
> on the cli when they see a bad call. That's just for geeks that test  
> stuff, which might
> be a good reason to have it as an optional module. Normal users would  
> do it
> in a web interface, and the recommendation is that that kind of  
> interfaces use
> the AMI, not the CLI.

There's a big usability difference between the CLI and the manager
interface: the CLI does not require setup. Which is why it is much more
usable in scripts that don't want to assume too much about the installed
system.

> 
> That we have a bunch of these still around is no reason to keep  
> accepting new ones.
> With that way of reasoning, we could add a lot of stuff that no longer  
> makes sense...
> We have to have an idea of where we want to go, some design to follow.  
> To copy
> a manager command in the CLI is just adding to the confusion on where  
> to use
> CLI and where to use AMI.

This can be resolved if you can get astcli to Just Work [tm]

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir



More information about the asterisk-dev mailing list