Re: [asterisk-users] tired of midget packet received warnings
On Nov 8, 2008, at 1:30 PM, Atis Lezdins wrote:
Asterisk offers very much the same flexibility. You can disable
specific log levels (for example warnings) in logger.conf or you can
log everything to syslog, where filter out this specific message.
Of course, there is always this method, which is an even easier way to
disable this specific message:
Index: channels/chan_iax2.c
===
--- channels/chan_iax2.c(revision 155670)
+++ channels/chan_iax2.c(working copy)
@@ -7058,7 +7058,6 @@
memcpy(sin, thread-iosin, sizeof(sin));
if (res sizeof(*mh)) {
- ast_log(LOG_WARNING, midget packet received (%d of %zd
min)\n,
res, sizeof(*mh));
return 1;
}
if ((vh-zeros == 0) (ntohs(vh-callno) 0x8000)) {
--
Russell Bryant
Senior Software Engineer
Open Source Team Lead
Digium, Inc.
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
Russell Bryant wrote: On Nov 8, 2008, at 1:30 PM, Atis Lezdins wrote: Asterisk offers very much the same flexibility. You can disable specific log levels (for example warnings) in logger.conf or you can log everything to syslog, where filter out this specific message. Of course, there is always this method, which is an even easier way to disable this specific message: I would have thought logging to syslog and using the filter functions there would have been considerably easier than recompiling a patched version of Asterisk - particularly if precompiled versions are in use. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote: Tzafrir Cohen wrote: On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote: I'd take this warning seriously. It means that your monitoring app isn't monitoring what you think it is. I always want to know when I get malformed protocol packets in. It is always bad news, mostly either a misconfiguration (your case), an attack, (ie my firewall is not protecting this service) or a sign of a switch port going bad. Fix the cause not the symptom. Maybe it's me, but I think that warning should be regarding a problem I can fix. Malformed network content does not neceserily fall under that definition. notice? Absolutely it does. Warnings of malformed packets are often (as mentioned above) symptomatic of network problems. Fix the network problem, fix the warning. As you saw in this case, this is a monitoring program that checks if somebody still listens on the UDP port. Would you teach nmap to try a valid IAX packet on every UDP port? How can you tell in advance that the port is IAX and not SIP? Or whatever UDP protocol? Why should the monitoring program care? -- Tzafrir Cohen icq#16849755 jabber:[EMAIL PROTECTED] +972-50-7952406 mailto:[EMAIL PROTECTED] http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
Tzafrir Cohen wrote: On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote: Maybe it's me, but I think that warning should be regarding a problem I can fix. Malformed network content does not neceserily fall under that definition. notice? Absolutely it does. Warnings of malformed packets are often (as mentioned above) symptomatic of network problems. Fix the network problem, fix the warning. As you saw in this case, this is a monitoring program that checks if somebody still listens on the UDP port. Would you teach nmap to try a valid IAX packet on every UDP port? How can you tell in advance that the port is IAX and not SIP? Or whatever UDP protocol? Why should the monitoring program care? Depends on how thorough you want the monitoring program to be. Personally if I were monitoring a service, I'd want to know that the service was responding the way you were expecting it to rather than blindly checking whether the port was open. However, one of my previous job was to monitor a large network that was running software that I would consider to be pretty badly broken and the fact that a port was open meant nothing more than the executable was still running - it was quite common for the software behind it to have gone into an infinite loop that promptly ignored all other data. I learnt to be incredibly paranoid if I wanted to be sure that everything was working the way it was supposed to be. UDP presents it's own challenges when it comes to monitoring anyway since there's no guarantee you'll get a reply from the other end. However, in the case of a program such as nmap, I take your point. Nmap is more interested in whether a port is open than whether the software is fully functional or not. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
On Sat, Nov 8, 2008 at 9:20 AM, Louis-David Mitterrand [EMAIL PROTECTED] wrote: On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote: Tzafrir Cohen wrote: On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote: I'd take this warning seriously. It means that your monitoring app isn't monitoring what you think it is. I always want to know when I get malformed protocol packets in. It is always bad news, mostly either a misconfiguration (your case), an attack, (ie my firewall is not protecting this service) or a sign of a switch port going bad. Fix the cause not the symptom. Maybe it's me, but I think that warning should be regarding a problem I can fix. Malformed network content does not neceserily fall under that definition. notice? Absolutely it does. Warnings of malformed packets are often (as mentioned above) symptomatic of network problems. Fix the network problem, fix the warning. C'mon, even firewalls give you the option of _not_ logging malformed packets! fiaif does. Else your logfile would be the weak point of your system. And what if you can't fix the source of these packets? And what if friendly peers outside of your realm (likely to iax-call you, so can't block them) sends these packets? There are holes in your logic. So asterisk has to be puritan of the lot? Holier than thou? Pro-life with malformed packets? I see where this is going and I don't like it one bit. Asterisk offers very much the same flexibility. You can disable specific log levels (for example warnings) in logger.conf or you can log everything to syslog, where filter out this specific message. Regards, Atis -- Atis Lezdins, VoIP Project Manager / Developer, [EMAIL PROTECTED] Skype: atis.lezdins Cell Phone: +371 28806004 Cell Phone: +1 800 7300689 Work phone: +1 800 7502835 ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
On Sat, Nov 08, 2008 at 09:30:59PM +0200, Atis Lezdins wrote: On Sat, Nov 8, 2008 at 9:20 AM, Louis-David Mitterrand [EMAIL PROTECTED] wrote: On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote: Tzafrir Cohen wrote: On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote: I'd take this warning seriously. It means that your monitoring app isn't monitoring what you think it is. I always want to know when I get malformed protocol packets in. It is always bad news, mostly either a misconfiguration (your case), an attack, (ie my firewall is not protecting this service) or a sign of a switch port going bad. Fix the cause not the symptom. Maybe it's me, but I think that warning should be regarding a problem I can fix. Malformed network content does not neceserily fall under that definition. notice? Absolutely it does. Warnings of malformed packets are often (as mentioned above) symptomatic of network problems. Fix the network problem, fix the warning. C'mon, even firewalls give you the option of _not_ logging malformed packets! fiaif does. Else your logfile would be the weak point of your system. And what if you can't fix the source of these packets? And what if friendly peers outside of your realm (likely to iax-call you, so can't block them) sends these packets? There are holes in your logic. So asterisk has to be puritan of the lot? Holier than thou? Pro-life with malformed packets? I see where this is going and I don't like it one bit. Asterisk offers very much the same flexibility. You can disable specific log levels (for example warnings) in logger.conf Sure. And I can always run '2/dev/null' . But this means I won't see useful warnings. And I will ignore other imporant warnings. or you can log everything to syslog, where filter out this specific message. Who needs log levels, then? -- Tzafrir Cohen icq#16849755 jabber:[EMAIL PROTECTED] +972-50-7952406 mailto:[EMAIL PROTECTED] http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote: Louis-David Mitterrand wrote: When monitoring an asterisk through its iax2 port I get these warnings at the console: [Nov 6 13:15:15] WARNING[2209]: chan_iax2.c:7000 socket_process: midget packet received (1 of 4 min) This is triggered by the monitoring app sending a POKE to the iax port. The warning appears even without any '-v'. Your monitoring app is not sending valid IAX2 packets to the server. If it was sending a true IAX2 POKE, it would be a valid packet and wouldn't generate this warning. Could asterisk at least _not_ report this harmless, below-warning event when using a zero-verbose (asterisk -r) level? That would be nice and logical. -- http://www.lesculturelles.net ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
Louis-David Mitterrand wrote: On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote: Your monitoring app is not sending valid IAX2 packets to the server. If it was sending a true IAX2 POKE, it would be a valid packet and wouldn't generate this warning. Could asterisk at least _not_ report this harmless, below-warning event when using a zero-verbose (asterisk -r) level? That would be nice and logical. Actually, I would have said that corrupt/bad IAX packsets *should* be reported and are *not* harmless. They're harmless in your instance because your monitoring application isn't functioning properly, but to anyone else they're likely to indicate either (a) a hacking attempt or (b) a fairly serious network problem. How about you fix your monitoring application to send a correct IAX2 POKE request? ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
On 7 Nov 2008, at 08:49, Louis-David Mitterrand wrote: On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote: Louis-David Mitterrand wrote: When monitoring an asterisk through its iax2 port I get these warnings at the console: [Nov 6 13:15:15] WARNING[2209]: chan_iax2.c:7000 socket_process: midget packet received (1 of 4 min) This is triggered by the monitoring app sending a POKE to the iax port. The warning appears even without any '-v'. Your monitoring app is not sending valid IAX2 packets to the server. If it was sending a true IAX2 POKE, it would be a valid packet and wouldn't generate this warning. Could asterisk at least _not_ report this harmless, below-warning event when using a zero-verbose (asterisk -r) level? That would be nice and logical. I'd take this warning seriously. It means that your monitoring app isn't monitoring what you think it is. I always want to know when I get malformed protocol packets in. It is always bad news, mostly either a misconfiguration (your case), an attack, (ie my firewall is not protecting this service) or a sign of a switch port going bad. Fix the cause not the symptom. T. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
On 7 Nov 2008, at 09:57, Louis-David Mitterrand wrote: On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote: Your monitoring app is not sending valid IAX2 packets to the server. If it was sending a true IAX2 POKE, it would be a valid packet and wouldn't generate this warning. Could asterisk at least _not_ report this harmless, below-warning event when using a zero-verbose (asterisk -r) level? That would be nice and logical. I'd take this warning seriously. It means that your monitoring app isn't monitoring what you think it is. Granted, the monitoring app is simple minded: it only checks if a port is open. In that respect is does a hell of a good job: I hear a beeping alarm as soon as an asterisk instance goes south. Yep, but it won't tell you that the single IAX thread is blocked in a database access, so asterisk is ignoring your packets, it just hasn't closed the port. So what you are saying is that all monitoring apps should speak native iax, else they are bad? Simply checking if a port is open means it's misconfigured or badly written? I wouldn't go so far. Small generic port-monitoring apps should be allowed to check on asterisk without raising such spurious warnings. You know what happens when crying wolf to often, no one listens after a while. A midget packet is not corrupted, I do have a stateful firewall (fiaif) to intercept those. Kinda, certainly I'd be inclined to write a little plug-in that sends a valid POKE packet. Tell me what your monitor supports and I'll help you craft a valid packet. rant AFAIK the onus is on asterisk to adapat: I've suffered too long of the infamous iax2 port-clogging bug that would and render a server 'unreachable' for no good reason. So much so that I went off iax2 entirely and use SIP exclusively for inter-asterisk communication. So much for the muched touted new and advanced pbx communication protocol the iax2 was sold for! This deal-breaker bug went unfixed for years until recently, despite numerous asterisk users reporting iax2 anomalies month after month. A I bitter? yes. Do I trust Digium folks to know their stuff about what is correct or not in networking protocols? I'll let you guess the answer. /rant Yeah, that one took _way_ too long to fix, I think the problem was that IAX was undocumented so not many people could fix it, that and the fact that it required a major re-code to get chan_iax2 multithreaded. Ed Guy et al have done loads of work on the RFC, to the point where it is actually possible to implement IAX without looking at the asterisk code :-) so the situation is better now. I always want to know when I get malformed protocol packets in. It is always bad news, mostly either a misconfiguration (your case), an attack, (ie my firewall is not protecting this service) or a sign of a switch port going bad. Fix the cause not the symptom. 'fraid I stand by that bit Tim. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote: Your monitoring app is not sending valid IAX2 packets to the server. If it was sending a true IAX2 POKE, it would be a valid packet and wouldn't generate this warning. Could asterisk at least _not_ report this harmless, below-warning event when using a zero-verbose (asterisk -r) level? That would be nice and logical. I'd take this warning seriously. It means that your monitoring app isn't monitoring what you think it is. Granted, the monitoring app is simple minded: it only checks if a port is open. In that respect is does a hell of a good job: I hear a beeping alarm as soon as an asterisk instance goes south. So what you are saying is that all monitoring apps should speak native iax, else they are bad? Simply checking if a port is open means it's misconfigured or badly written? I wouldn't go so far. Small generic port-monitoring apps should be allowed to check on asterisk without raising such spurious warnings. You know what happens when crying wolf to often, no one listens after a while. A midget packet is not corrupted, I do have a stateful firewall (fiaif) to intercept those. rant AFAIK the onus is on asterisk to adapat: I've suffered too long of the infamous iax2 port-clogging bug that would and render a server 'unreachable' for no good reason. So much so that I went off iax2 entirely and use SIP exclusively for inter-asterisk communication. So much for the muched touted new and advanced pbx communication protocol the iax2 was sold for! This deal-breaker bug went unfixed for years until recently, despite numerous asterisk users reporting iax2 anomalies month after month. A I bitter? yes. Do I trust Digium folks to know their stuff about what is correct or not in networking protocols? I'll let you guess the answer. /rant I always want to know when I get malformed protocol packets in. It is always bad news, mostly either a misconfiguration (your case), an attack, (ie my firewall is not protecting this service) or a sign of a switch port going bad. Fix the cause not the symptom. T. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- http://www.lesculturelles.net ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
Tim Panton [EMAIL PROTECTED] writes: I always want to know when I get malformed protocol packets in. It's easy for an attacker to fill your log drive then. /Benny ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote: I'd take this warning seriously. It means that your monitoring app isn't monitoring what you think it is. I always want to know when I get malformed protocol packets in. It is always bad news, mostly either a misconfiguration (your case), an attack, (ie my firewall is not protecting this service) or a sign of a switch port going bad. Fix the cause not the symptom. Maybe it's me, but I think that warning should be regarding a problem I can fix. Malformed network content does not neceserily fall under that definition. notice? -- Tzafrir Cohen icq#16849755 jabber:[EMAIL PROTECTED] +972-50-7952406 mailto:[EMAIL PROTECTED] http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
Rob Hillis wrote: Louis-David Mitterrand wrote: On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote: Your monitoring app is not sending valid IAX2 packets to the server. If it was sending a true IAX2 POKE, it would be a valid packet and wouldn't generate this warning. Could asterisk at least _not_ report this harmless, below-warning event when using a zero-verbose (asterisk -r) level? That would be nice and logical. Actually, I would have said that corrupt/bad IAX packsets *should* be reported and are *not* harmless. They're harmless in your instance because your monitoring application isn't functioning properly, but to anyone else they're likely to indicate either (a) a hacking attempt or (b) a fairly serious network problem. How about you fix your monitoring application to send a correct IAX2 POKE request? Personally, I just like reading the word 'midget' . It makes me smile. PaulH ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
Tzafrir Cohen wrote: On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote: I'd take this warning seriously. It means that your monitoring app isn't monitoring what you think it is. I always want to know when I get malformed protocol packets in. It is always bad news, mostly either a misconfiguration (your case), an attack, (ie my firewall is not protecting this service) or a sign of a switch port going bad. Fix the cause not the symptom. Maybe it's me, but I think that warning should be regarding a problem I can fix. Malformed network content does not neceserily fall under that definition. notice? Absolutely it does. Warnings of malformed packets are often (as mentioned above) symptomatic of network problems. Fix the network problem, fix the warning. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote: Tzafrir Cohen wrote: On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote: I'd take this warning seriously. It means that your monitoring app isn't monitoring what you think it is. I always want to know when I get malformed protocol packets in. It is always bad news, mostly either a misconfiguration (your case), an attack, (ie my firewall is not protecting this service) or a sign of a switch port going bad. Fix the cause not the symptom. Maybe it's me, but I think that warning should be regarding a problem I can fix. Malformed network content does not neceserily fall under that definition. notice? Absolutely it does. Warnings of malformed packets are often (as mentioned above) symptomatic of network problems. Fix the network problem, fix the warning. C'mon, even firewalls give you the option of _not_ logging malformed packets! fiaif does. Else your logfile would be the weak point of your system. And what if you can't fix the source of these packets? And what if friendly peers outside of your realm (likely to iax-call you, so can't block them) sends these packets? There are holes in your logic. So asterisk has to be puritan of the lot? Holier than thou? Pro-life with malformed packets? I see where this is going and I don't like it one bit. -- http://www.lesculturelles.net ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
Louis-David Mitterrand wrote: When monitoring an asterisk through its iax2 port I get these warnings at the console: [Nov 6 13:15:15] WARNING[2209]: chan_iax2.c:7000 socket_process: midget packet received (1 of 4 min) This is triggered by the monitoring app sending a POKE to the iax port. The warning appears even without any '-v'. Your monitoring app is not sending valid IAX2 packets to the server. If it was sending a true IAX2 POKE, it would be a valid packet and wouldn't generate this warning. -- Kevin P. Fleming Director of Software Technologies Digium, Inc. - The Genuine Asterisk Experience (TM) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote: Louis-David Mitterrand wrote: When monitoring an asterisk through its iax2 port I get these warnings at the console: [Nov 6 13:15:15] WARNING[2209]: chan_iax2.c:7000 socket_process: midget packet received (1 of 4 min) This is triggered by the monitoring app sending a POKE to the iax port. The warning appears even without any '-v'. Your monitoring app is not sending valid IAX2 packets to the server. If it was sending a true IAX2 POKE, it would be a valid packet and wouldn't generate this warning. Hi, Is POKE a generic udp thing or specific to iax? In the former case I'll probably be able to submit a patch to wmnetmon (great dockable applet I'm using). Thanks, -- http://www.lesculturelles.net ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] tired of midget packet received warnings
On Thursday 06 November 2008 08:53:40 Louis-David Mitterrand wrote: On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote: Louis-David Mitterrand wrote: When monitoring an asterisk through its iax2 port I get these warnings at the console: [Nov 6 13:15:15] WARNING[2209]: chan_iax2.c:7000 socket_process: midget packet received (1 of 4 min) This is triggered by the monitoring app sending a POKE to the iax port. The warning appears even without any '-v'. Your monitoring app is not sending valid IAX2 packets to the server. If it was sending a true IAX2 POKE, it would be a valid packet and wouldn't generate this warning. Is POKE a generic udp thing or specific to iax? In the former case I'll probably be able to submit a patch to wmnetmon (great dockable applet I'm using). It's specific to IAX. -- Tilghman ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
