[asterisk-users] What's up with the Manager Interface?!?!

[Richard Lyman]

TP'n to follow flow..

yes i understand the out is similar/same.
i was attempting to get james to note that there already are manager 
commands.

as a note for parsing the manager interface..

you will probably find it easier if you parse as a block, meaning *till* 
a blank line.
then parse the block for all it's little tweaks <G>

Douglas Garstang wrote:
> That data is no easier to parse than the output generated from:
>
> Action: Command
> Command: sip show peer <peer>
>
> Note the colons used both as a field delimiter AND stuck in the regcontact.
>
> CodecOrder: ulaw,g729,gsm
> Status: UNKNOWN
> SIP-Useragent: PolycomSoundPointIP-SPIP_601-UA/1.6.7.0098
> Reg-Contact : sip:2944093 at 216.187.128.77
> ChanVariable:
>  parkstart,10
>
> Doug.
>
>   
>> -----Original Message-----
>> From: Richard Lyman [mailto:pchammer at dynx.net]
>> Sent: Wednesday, November 29, 2006 3:30 PM
>> To: Asterisk Users Mailing List - Non-Commercial Discussion
>> Subject: Re: [asterisk-users] What's up with the Manager Interface?!?!
>>
>>
>> James Texter wrote:
>>     
>>> Doug,
>>>     Your issue isn't with the manager.  It's with the CLI 
>>>       
>> output you are
>>     
>>> trying to hijack via manager :D  If you run "sip show peer 
>>>       
>> 2944093" in the
>>     
>>> CLI, you'll see a blank line, followed by a line that is "* 
>>>       
>> Name".  It
>>     
>>> appears what you really want is a manager Action to show a 
>>>       
>> sip peer, in
>>     
>>> which case I would recommend adding a new manager command 
>>>       
>> that returns a
>>     
>>> string which is much more machine readable.  Remember, CLI output is
>>> designed to be human readable.
>>>
>>> Just my $0.02.
>>>
>>>   
>>>       
>> action: sippeers
>>
>> or
>>
>> action: sipshowpeer
>> peer: name
>>
>> maybe you should do the below to refresh  your memory
>>
>> action: command
>> command: show manager commands
>>
>>