[asterisk-dev] bug 0016466: cidname and cidnum in output of "sip show peers"

[Olle E. Johansson]

22 mar 2010 kl. 16.35 skrev Ron Arts:

> Op 22-03-10 16:10, Leif Madsen schreef:
>> Ron Arts wrote:
>>> Allright. Fair enough. I personally feel things are being overengineered here,
>>> for a small new feature that is very helpful for support engineers, but I
>>> guess the decision has been made.
>>> 
>>> If I want to discuss the other proposal, should we do that in a new thread?
>>> You know, adding callerid to all 'ringing', 'answered', 'busy'  etc messages
>>> in the log output?
>> 
>> I think the issue here is not that this is a small feature that is useful for
>> you, but rather that we have existing implementations that may expect the output
>> to be of a certain format (i.e. the way it is now), and that changing that
>> output formatting would break an existing implementation (even if the use of the
>> output in a script is not recommended).
>> 
> 
> That sounds a bit patronizing. I only suggested it for trunk.
Which is the only place we change things. I kindly ask you to respect that 
we want to build a product that fit many needs and is highly configurable
to fit any one.

> And I honestly
> believe this feature isn't only useful to me, but to a lot of people out there.
> Too bad nobody is stepping up to confirm that :-(
I honestly believe that the change is important. I believe the other requests 
I have seen for additional information in various lists are also important.
How we can fit everything in 80 character lines is the problem we have to solve.
With the solution we outlined, we don't solve the problem, but hand a tool over
to the Asterisk admin to make his priorities implemented by a simple configuration
option. I think that's a good way forward for everyone.

> 
> Anyway, what about the other suggestion? Should I spare myself the trouble?
> Are there people depending on parsing logfile output?
I have a solution where I take manager output and log to MySQL so that support
staff have all the information and don't have to try to parse output from the CLI
or even use the CLI, as it in the case of servers with high load can affect the 
performance of the Asterisk process when you run it over TCP connections (like SSH).

/O