[asterisk-dev] What to do with RTCP ????
The RTCP branch includes improved support of RTCP, but also a reporting facility we do not use currently. Would it be useful to add this to a channel variable - or even better a CDR variable - so you can add it to CDRs and make reports based on it? /Olle ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
RE: [asterisk-dev] What to do with RTCP ????
The RTCP branch includes improved support of RTCP, but also a reporting facility we do not use currently. Would it be useful to add this to a channel variable - or even better a CDR variable - so you can add it to CDRs and make reports based on it? I don't mind how it's reports, als long as it's relatively easy to correlate RTCP data to users. So adding some information to a CDR is fine. -- Andreas Sikkema BBned NV Software EngineerPlaneetbaan 4 +31 (0)23 70743422132 HZ Hoofddorp ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] What to do with RTCP ????
On 2/27/06, Andreas Sikkema [EMAIL PROTECTED] wrote: The RTCP branch includes improved support of RTCP, but also a reporting facility we do not use currently. Would it be useful to add this to a channel variable - or even better a CDR variable - so you can add it to CDRs and make reports based on it? I don't mind how it's reports, als long as it's relatively easy to correlate RTCP data to users. So adding some information to a CDR is fine. Some integration with the CDR is fine, but I'd rather we make it available via a function so people can grab the data and do what they want with it. To have an RTCP logging channel via the existing logger facility might be an interesting thing too. I'd proably use that to throw it to some facility that throws up mrtg type graphs,etc. -- Bird's The Word Technologies, Inc. http://www.btwtech.com/ ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] What to do with RTCP ????
27 feb 2006 kl. 13.00 skrev BJ Weschke: On 2/27/06, Andreas Sikkema [EMAIL PROTECTED] wrote: The RTCP branch includes improved support of RTCP, but also a reporting facility we do not use currently. Would it be useful to add this to a channel variable - or even better a CDR variable - so you can add it to CDRs and make reports based on it? I don't mind how it's reports, als long as it's relatively easy to correlate RTCP data to users. So adding some information to a CDR is fine. Some integration with the CDR is fine, but I'd rather we make it available via a function so people can grab the data and do what they want with it. A function is a good idea, but not a replacement for variables. We can do a function too, but the end report is only available at the end of the call, so a function would be of no use. The function can deliver the current data mid-call, but would be of limited use. To have an RTCP logging channel via the existing logger facility might be an interesting thing too. I'd proably use that to throw it to some facility that throws up mrtg type graphs,etc. -- Well, that would imply that we can log quality for other channels as well, so we need to come up with generic stuff to have a log that can handle both IAX2 and rtp-based channels. /O ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] What to do with RTCP ????
On Mon, Feb 27, 2006 at 10:48:06AM +0100, Olle E Johansson wrote: The RTCP branch includes improved support of RTCP, but also a reporting facility we do not use currently. Would it be useful to add this to a channel variable - or even better a CDR variable - so you can add it to CDRs and make reports based on it? /Olle Would love to see RTCP stats in a CDR. Currently have SER parsing RTCP reports out and doing things with them instead. Ray ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] What to do with RTCP ????
On Mon, Feb 27, 2006 at 10:48:06AM +0100, Olle E Johansson wrote: The RTCP branch includes improved support of RTCP, but also a reporting facility we do not use currently. Would it be useful to add this to a channel variable - or even better a CDR variable - so you can add it to CDRs and make reports based on it? /Olle Would love to see RTCP stats in a CDR. Currently have SER parsing RTCP reports out and doing things with them instead. Ray 1) As far as how Asterisk presents information (regardless of this SIP-specific method) I would suggest that the data is available via channel variables. Functions and variables are equally useful as far as I'm concerned - is there a reason why one method would be preferred over another? 2) How difficult would it be to put the RTCP stats into the new SNMP structure? I'm not sure how useful this would be, since whatever SNMP query system existed would have to walk the tree (or be notified via a Manager link of some type) to obtain call lists and then monitor the calls. 3) Would a Manager-accessible method make sense here? I think that having the call quality data available to external Asterisk-compatible tools would be pretty interesting, and ultimately the most useful method to obtain real-time quality information for a NOC. (sorry if this is already in place; I've tested this patch a few times, but never tried to see what happens on the manager interface.) 4) If the variables were accessible in the dialplan at hangup, then something like my CQDR log could be created by a System call within the dialplan... http://lists.digium.com/pipermail/asterisk-dev/2004-May/004180.html 5) While not directly relevant to how Asterisk implements RTCP stats, this may be of interest as a method for many devices in a SIP call chain to monitor RTP quality of a particular call: http://www.ietf.org/internet-drafts/draft-ietf-sipping-rtcp-summary-00.txt JT ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] What to do with RTCP ????
Paul Cadach wrote: Hello, Olle E Johansson wrote: The RTCP branch includes improved support of RTCP, but also a reporting facility we do not use currently. Would it be useful to add this to a channel variable - or even better a CDR variable - so you can add it to CDRs and make reports based on it? Mostly RTCP information can be used to adjust jitter buffering algorithms, arrange clocks when peer stopped transmission, etc. ..and be used to make decisions about in-call codec changes, but that something we can do later. I will try to create some data for CDR variables in the meantime, and a dial plan function. I also want to add a special thank you to folsson and john martin that has done the development on this patch. I still look froward to more test reports in the bug tracker :-) /O ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
