Hi Olle!<br><br><div>There are my 2 cents...</div><div><br><div>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... <div>
<br></div><div>So, even without knowing (initially) the meaning of the Qos data, I can define a recollector, dispatcher and storage system...</div><div>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...</div>
<div><br></div><div>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...</div><div><br></div>
<div>But that’s just my two cents...</div><div>Best regards.</div><div><br></div><div> Eduardo</div><div><br></div><div><div><div><div><div class="gmail_quote">On Mon, Jan 18, 2010 at 1:15 PM, Olle E. Johansson <span dir="ltr"><<a href="mailto:oej@edvina.net">oej@edvina.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I am implementing a manager command that can report properties on a SIP channel. Right now, I'm only interested in QoS.<br>
(for obvious reasons).<br>
<br>
-------------------------------------------------------------------------------<br>
*CLI> manager show command SIPchannel<br>
Action: SIPchannel<br>
Synopsis: Show information about SIP channel<br>
Privilege: call,all<br>
Description: Show one SIP channel with details on current status.<br>
Variables:<br>
Channel: <name> The channel name (AST) you want to check.<br>
ActionID: <id> Optional action ID for this AMI transaction.<br>
Datatype: <name> Optional parameter name required. If not specified, all data will be sent<br>
<br>
Datatype Description<br>
qos Current QoS value for this channel (sender and receiver)<br>
<br>
-------------------------------------------------------------------------------<br>
<br>
This should be extensible with other datatypes in the future.<br>
<br>
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.<br>
<br>
Current output:<br>
<br>
-------------------------------------------------------------------------------<br>
action: sipchannel<br>
datatype: qos<br>
channel: SIP/pinefrog6-00000000<br>
<br>
Response: Success<br>
LocalSSRC(audio): 593163852<br>
RemoteSSRC(audio): 0<br>
LocalJitter(audio): 0<br>
LocalPacketCount(audio): 0<br>
RemotePacketCount(audio): 0<br>
LocalLostPackets(audio): 0<br>
RemoteLostPackets(audio): 0<br>
RemoteJitter(audio): 1<br>
MediaRtt(audio): 25889302<br>
<br>
-------------------------------------------------------------------------------<br>
<br>
Should I move to<br>
<br>
MediaRtt[Audio]<br>
<br>
using square brackets. In the future, one could come up with<br>
<br>
label[index](channel)<br>
<br>
headers for events.<br>
<br>
What do you think?<br>
<br>
/O<br>
<font color="#888888">--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Hasta otra!!!<br> Eduardo Ferro Aldama<br> Alea Soluciones<br> <br> <a href="http://www.alea-soluciones.com">http://www.alea-soluciones.com</a> <br>
<a href="http://oss.alea-soluciones.com">http://oss.alea-soluciones.com</a><br> <a href="http://doc.alea-soluciones.com">http://doc.alea-soluciones.com</a><br><br>
</div></div></div></div></div></div>