|Summary:||ASTERISK-14110: [patch] Broadcasting CDR &| Manager Events via UDP|
|Reporter:||Philipp Dunkel (pdunkel)||Labels:|
|Date Opened:||2009-05-12 09:57:45||Date Closed:||2011-06-07 14:00:20|
|Environment:||Attachments:||( 0) cdr_broadcast.c|
( 1) cdr_broadcast.conf.sample
( 2) cdr_broadcast.patch
( 3) cdr_broadcast.trunk.patch
|Description:||For an application of mine I need Manager-Events to be broadcast via UDP-Multicast. In this application the reliability of getting the events is less important than being able to monitor them. This little CDR module sends Manager &| CDR Events via UDP Sockets to the network. There they can easily be monitored by other applications.|
|Comments:||By: Philipp Dunkel (pdunkel) 2009-05-12 10:01:17|
You guys also already have my paper based license on file email@example.com
By: Philipp Dunkel (pdunkel) 2009-05-12 11:28:55
The cdr_broadcast.patch file is a patch to make this work with the 184.108.40.206 tree as well.
By: Sean Bright (seanbright) 2009-05-13 10:21:21
The copyright in your .c file is wrong. Since you wrote it, the copyright is yours.
By: Philipp Dunkel (pdunkel) 2009-05-15 10:07:10
For all I care this could be put into PD. Can we work this through on its merits?
As to the copyright line being wrong: why? Are you saying I can't give away my copyright as a present to digium ;)
Let's just agree that we will put the best suited line at the top of the file when all other potential issues are sorted out.
By: Russell Bryant (russell) 2009-05-15 11:59:02
Please review the coding guidelines in doc/CODING-GUIDELINES.
Also, for your string handling, please use the ast_str dynamic string API.
By: John S. (johnakabean) 2009-05-16 20:09:06
Asside from your module, russel, this should be part of the module snmp that asterisk already has which means it is a duty of digium to incorporate this if they include an snmp protocol as this is one main job/feature of simple network managemnet protocol.
By: Leif Madsen (lmadsen) 2009-09-18 09:44:10
I'm suspending this issue for now since it requires the original reporter to update the patch based on the coding guidelines. If the reporter (or anyone else) is able to move this issue forward, then please reopen the issue.