[asterisk-dev] Manager "sipchannel" command

[Olle E. Johansson]

19 jan 2010 kl. 21.47 skrev Eduardo Ferro:

> Hi Olle!
> 
> There are my 2 cents...
> 
> I like the proposed sintax :), but I think it can be better if there is another manager command (or other method) to get the information related with the valid indexes, and the valid Metric's names... 
THat's good input for a new generation of manager - discovery.

> 
> So, even without knowing (initially) the meaning  of the Qos data, I can define a recollector, dispatcher and storage system...
> I am think in something like "metainfo" for the Qos metrics... (an for other kinds of datatypes), so I can programmatically know all the info and autogenerate some related tools...
> 
> When we are talking about snmp metric we can get this info from the mib, so a lot of tools can be very generic, so I think that in that case this metainfo can be very usefull also...
> 
> But that’s just my two cents...
Thank you - very valuable feedback!

/O
> Best regards.
> 
>     Eduardo
> 
> On Mon, Jan 18, 2010 at 1:15 PM, Olle E. Johansson <oej at edvina.net> wrote:
> I am implementing a manager command that can report properties on a SIP channel. Right now, I'm only interested in QoS.
> (for obvious reasons).
> 
> -------------------------------------------------------------------------------
> *CLI> manager show command SIPchannel
> Action: SIPchannel
> Synopsis: Show information about SIP channel
> Privilege: call,all
> Description: Show one SIP channel with details on current status.
> Variables:
>  Channel: <name>        The channel name (AST) you want to check.
>  ActionID: <id>          Optional action ID for this AMI transaction.
>  Datatype: <name>        Optional parameter name required. If not specified, all data will be sent
> 
>  Datatype      Description
>        qos     Current QoS value for this channel (sender and receiver)
> 
> -------------------------------------------------------------------------------
> 
> This should be extensible with other datatypes in the future.
> 
> Now, for QoS we have to report data for all RTP streams. I was wondering how to label the manager headers. I don't want LocalJitterAudio and LocalJitterVideo - so I started experimenting with parentesis. Meanwhile, we decided to use that for channel identifiers in events/responses including multiple channels. So the question is what kind of syntax I could use here.
> 
> Current output:
> 
> -------------------------------------------------------------------------------
> action: sipchannel
> datatype: qos
> channel: SIP/pinefrog6-00000000
> 
> Response: Success
> LocalSSRC(audio): 593163852
> RemoteSSRC(audio): 0
> LocalJitter(audio): 0
> LocalPacketCount(audio): 0
> RemotePacketCount(audio): 0
> LocalLostPackets(audio): 0
> RemoteLostPackets(audio): 0
> RemoteJitter(audio): 1
> MediaRtt(audio): 25889302
> 
> -------------------------------------------------------------------------------
> 
> Should I move to
> 
> MediaRtt[Audio]
> 
> using square brackets. In the future, one could come up with
> 
> label[index](channel)
> 
> headers for events.
> 
> What do you think?
> 
> /O
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
> 
> 
> 
> -- 
> Hasta otra!!!
>    Eduardo Ferro Aldama
>    Alea Soluciones
>    
>    http://www.alea-soluciones.com    
>    http://oss.alea-soluciones.com
>    http://doc.alea-soluciones.com
> 
> -- 
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev

---
* Olle E Johansson - oej at edvina.net
* Cell phone +46 70 593 68 51, Office +46 8 96 40 20, Sweden