Re: [asterisk-users] Capturing call Reject/Decline events on a PRI line
Hi Richard, There is no event for Asterisk to recognize. The PROGRESS message just says that there is an audio message available for the caller to listen to. Asterisk just passes the indication to the peer channel and opens the audio path. It is the caller who must recognize any audio message that their call has been dropped. Thanks for the explanation. Any suggestion on how to recognise that the call has been dropped? -- Thanks, Ishwar. As far as ISDN is concerned, the call has not been answered yet so Asterisk must keep waiting. Richard -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time frame to fix such bugs?
On 7/30/11 7:39 AM, Bruce B wrote: I think this should be a quick fix since it's rendering the latest stable version useless and making the impression that it was released just to break things and force people onto 1.8x. Just a thought...no blame game. But really something like this should be tackled quickly. No point to break things so badly on the last stable version. Regards, Confirming this issue on 10+ 1.6.2.19 Asterisk servers. This problem makes it difficult to do edits on sip.conf on production systems, as there is ~25% chance that you'll crash the server and cut the established calls. The problem does not exist in 1.6.2.18... I think this problem should be fixed or the 1.6.2.19 should be removed from the digium repo. Regards, Vahan -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] (no subject)
Miki Sent on my BlackBerry® from Vodafone -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] (no subject)
Sent on my BlackBerry® from Vodafone -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Codec translation from gsm to other codecs or from other codecs to gsm
Hi All; The asterisk version is 1.8.4.2 Why codec translation from and to gsm is not possible? I think it was possible in previous versions. I am missing something to have this codec translation possibility? Please advise. Regards Bilal -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Codec translation from gsm to other codecs or from other codecs to gsm
On 07/31/2011 07:48 AM, bilal ghayyad wrote: Hi All; The asterisk version is 1.8.4.2 Why codec translation from and to gsm is not possible? I think it was possible in previous versions. I am missing something to have this codec translation possibility? What gives you the impression that it is not possible? -- Alex Balashov - Principal Evariste Systems LLC 260 Peachtree Street NW Suite 2200 Atlanta, GA 30303 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/ -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] asterisk + sccp-b problem
On 07/31/2011 07:22 AM, Pezhman Lali wrote: Dear, with asterisk 1.6.2.18 and sccp-bv3stable on two servers, we tried to register about 1200 cisco phones, for a company. in out of official hours, all 1200 phones registered and the cpu and ram was below 5%. In my experience, registering a Cisco phone was never an issue with sccp but it is hardly a test to see if it works. H323 is the protocol for incoming calls, and SIP for outgoing ones. I'm not sure what the state of chan_h323 is in Asterisk so you should ask around if there is anyone who uses chan_h323 in production and how reliable it is. Or hire a consultant to fix your problems. As far as I know the original developer of chan_h323 has not touched the code in a long time and no longer maintains it. in official hours, with only 10 calls, the cpu went more than 100% , and crashed. the bt full result of gdb was attached I am not a developer so can't tell you what is going wrong. According to the chan_h323 README you need PWLib 1.10.0 and you are using 1.10.3. I have some questions now, 1-is any problem in the attached report. 2-does asterisk 1.4 more stable than 1.6 in this case? Can't you test Asterisk 1.4 and see if that works? Also did you try the other h.323 channel driver (chan_ooh323) which is part of asterisk add-ons? For Asterisk 1.6 you can find it here: http://downloads.asterisk.org/pub/telephony/asterisk/releases/asterisk-addons-1.6.2.3.tar.gz Should Asterisk not be the proper solution for your customer's situation then maybe get a dedicated h.323 -- sip gateway or have a look at FreeSWITCH or Yate. Even if the h.323 part works flawlessly then make sure you test the sccp part very thoroughly. I have only experience with sccp v2 but have never seen that work reliably. Regards, Patrick -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Codec translation from gsm to other codecs or from other codecs to gsm
Could it be this bug? https://issues.asterisk.org/jira/browse/ASTERISK-17742 -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users- boun...@lists.digium.com] On Behalf Of bilal ghayyad Sent: Sunday, July 31, 2011 7:48 AM To: asterisk-users@lists.digium.com Subject: [asterisk-users] Codec translation from gsm to other codecs or from other codecs to gsm Hi All; The asterisk version is 1.8.4.2 Why codec translation from and to gsm is not possible? I think it was possible in previous versions. I am missing something to have this codec translation possibility? Please advise. Regards Bilal -- ___ __ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] sip attacks
My asterisk server is getting bogged down every 5 minutes. My ping time is going from 60ms to 800 ms and the call quality is bad. I have fail2ban running and I am using iptables. I have two ip connections to the box. How can I tell if the poor performance is due to sip attacks? I don't see any reg attempts in my asterisk cli. I use to get frequent attacks but fail2ban seems to be taking care of that. See how ping time gets worst in a short space of time and server performance at the time: 64 bytes from 4.2.2.1: icmp_seq=6 ttl=55 time=87.8 ms 64 bytes from 4.2.2.1: icmp_seq=7 ttl=55 time=99.8 ms 64 bytes from 4.2.2.1: icmp_seq=8 ttl=55 time=107 ms 64 bytes from 4.2.2.1: icmp_seq=9 ttl=55 time=115 ms 64 bytes from 4.2.2.1: icmp_seq=10 ttl=55 time=120 ms 64 bytes from 4.2.2.1: icmp_seq=11 ttl=55 time=122 ms 64 bytes from 4.2.2.1: icmp_seq=12 ttl=55 time=123 ms 64 bytes from 4.2.2.1: icmp_seq=13 ttl=55 time=126 ms 64 bytes from 4.2.2.1: icmp_seq=14 ttl=55 time=122 ms 64 bytes from 4.2.2.1: icmp_seq=15 ttl=55 time=142 ms 64 bytes from 4.2.2.1: icmp_seq=16 ttl=55 time=142 ms 64 bytes from 4.2.2.1: icmp_seq=17 ttl=55 time=137 ms 64 bytes from 4.2.2.1: icmp_seq=18 ttl=55 time=186 ms 64 bytes from 4.2.2.1: icmp_seq=19 ttl=55 time=255 ms 64 bytes from 4.2.2.1: icmp_seq=20 ttl=55 time=310 ms 64 bytes from 4.2.2.1: icmp_seq=21 ttl=55 time=387 ms 64 bytes from 4.2.2.1: icmp_seq=22 ttl=55 time=445 ms 64 bytes from 4.2.2.1: icmp_seq=23 ttl=55 time=514 ms 64 bytes from 4.2.2.1: icmp_seq=24 ttl=55 time=583 ms 64 bytes from 4.2.2.1: icmp_seq=25 ttl=55 time=650 ms 64 bytes from 4.2.2.1: icmp_seq=26 ttl=55 time=715 ms 64 bytes from 4.2.2.1: icmp_seq=27 ttl=55 time=783 ms 64 bytes from 4.2.2.1: icmp_seq=28 ttl=55 time=821 ms 64 bytes from 4.2.2.1: icmp_seq=29 ttl=55 time=810 ms 64 bytes from 4.2.2.1: icmp_seq=30 ttl=55 time=832 ms 64 bytes from 4.2.2.1: icmp_seq=31 ttl=55 time=812 ms 64 bytes from 4.2.2.1: icmp_seq=32 ttl=55 time=821 ms 64 bytes from 4.2.2.1: icmp_seq=33 ttl=55 time=826 ms 64 bytes from 4.2.2.1: icmp_seq=34 ttl=55 time=815 ms 64 bytes from 4.2.2.1: icmp_seq=35 ttl=55 time=821 ms 64 bytes from 4.2.2.1: icmp_seq=36 ttl=55 time=824 ms top - 19:02:38 up 4 days, 11:26, 4 users, load average: 0.36, 0.75, 0.82 Mem: 4051312k total, 1062964k used, 2988348k free, 167004k buffers Swap: 6094840k total,0k used, 6094840k free, 680144k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 4245 root 15 0 791m 86m 10m S 39.6 2.2 1192:32 asterisk 18280 root 15 0 3812 600 516 S 2.0 0.0 0:59.00 pppoe 2582 root 15 0 5912 628 504 S 0.3 0.0 2:02.19 syslogd 18978 root 15 0 12744 1096 812 R 0.3 0.0 0:00.02 top 1 root 15 0 10352 700 588 S 0.0 0.0 0:01.14 init 2 root RT -5 000 S 0.0 0.0 0:00.01 migration/0 3 root 34 19 000 S 0.0 0.0 0:31.90 ksoftirqd/0 4 root RT -5 000 S 0.0 0.0 0:00.00 watchdog/0 5 root RT -5 000 S 0.0 0.0 0:00.01 migration/1 6 root 34 19 000 S 0.0 0.0 0:08.43 ksoftirqd/1 7 root RT -5 000 S 0.0 0.0 0:00.00 watchdog/1 8 root RT -5 000 S 0.0 0.0 0:00.13 migration/2 9 root 34 19 000 S 0.0 0.0 2:40.56 ksoftirqd/2 10 root RT -5 000 S 0.0 0.0 0:00.00 watchdog/2 11 root RT -5 000 S 0.0 0.0 0:00.05 migration/3 12 root 34 19 000 S 0.0 0.0 0:44.56 ksoftirqd/3 13 root RT -5 000 S 0.0 0.0 0:00.00 watchdog/3 14 root 10 -5 000 S 0.0 0.0 0:00.02 events/0 15 root 10 -5 000 S 0.0 0.0 0:00.00 events/1 16 root 10 -5 000 S 0.0 0.0 0:00.00 events/2 17 root 10 -5 000 S 0.0 0.0 0:00.00 events/3 18 root 10 -5 000 S 0.0 0.0 0:00.00 khelper 55 root 10 -5 000 S 0.0 0.0 0:00.00 kthread 62 root 10 -5 000 S 0.0 0.0 0:00.07 kblockd/0 63 root 10 -5 000 S 0.0 0.0 0:00.01 kblockd/1 64 root 10 -5 000 S 0.0 0.0 0:00.00 kblockd/2 65 root 10 -5 000 S 0.0 0.0 0:00.00 kblockd/3 66 root 17 -5 000 S 0.0 0.0 0:00.00 kacpid 166 root 17 -5 000 S 0.0 0.0 0:00.00 cqueue/0 167 root 18 -5 000 S 0.0 0.0 0:00.00 cqueue/1 Dave -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] sip attacks
hard to equate sip attack to ping performance.. Run mtr for a bit. Also try tcpdump or wireshark or tethereal. If you are really paranoid recycle all your passwords Sent from my iPhone On Jul 31, 2011, at 7:04 PM, Dave George dgeo...@teletoneinc.com wrote: My asterisk server is getting bogged down every 5 minutes. My ping time is going from 60ms to 800 ms and the call quality is bad. I have fail2ban running and I am using iptables. I have two ip connections to the box. How can I tell if the poor performance is due to sip attacks? I don't see any reg attempts in my asterisk cli. I use to get frequent attacks but fail2ban seems to be taking care of that. See how ping time gets worst in a short space of time and server performance at the time: 64 bytes from 4.2.2.1: icmp_seq=6 ttl=55 time=87.8 ms 64 bytes from 4.2.2.1: icmp_seq=7 ttl=55 time=99.8 ms 64 bytes from 4.2.2.1: icmp_seq=8 ttl=55 time=107 ms 64 bytes from 4.2.2.1: icmp_seq=9 ttl=55 time=115 ms 64 bytes from 4.2.2.1: icmp_seq=10 ttl=55 time=120 ms 64 bytes from 4.2.2.1: icmp_seq=11 ttl=55 time=122 ms 64 bytes from 4.2.2.1: icmp_seq=12 ttl=55 time=123 ms 64 bytes from 4.2.2.1: icmp_seq=13 ttl=55 time=126 ms 64 bytes from 4.2.2.1: icmp_seq=14 ttl=55 time=122 ms 64 bytes from 4.2.2.1: icmp_seq=15 ttl=55 time=142 ms 64 bytes from 4.2.2.1: icmp_seq=16 ttl=55 time=142 ms 64 bytes from 4.2.2.1: icmp_seq=17 ttl=55 time=137 ms 64 bytes from 4.2.2.1: icmp_seq=18 ttl=55 time=186 ms 64 bytes from 4.2.2.1: icmp_seq=19 ttl=55 time=255 ms 64 bytes from 4.2.2.1: icmp_seq=20 ttl=55 time=310 ms 64 bytes from 4.2.2.1: icmp_seq=21 ttl=55 time=387 ms 64 bytes from 4.2.2.1: icmp_seq=22 ttl=55 time=445 ms 64 bytes from 4.2.2.1: icmp_seq=23 ttl=55 time=514 ms 64 bytes from 4.2.2.1: icmp_seq=24 ttl=55 time=583 ms 64 bytes from 4.2.2.1: icmp_seq=25 ttl=55 time=650 ms 64 bytes from 4.2.2.1: icmp_seq=26 ttl=55 time=715 ms 64 bytes from 4.2.2.1: icmp_seq=27 ttl=55 time=783 ms 64 bytes from 4.2.2.1: icmp_seq=28 ttl=55 time=821 ms 64 bytes from 4.2.2.1: icmp_seq=29 ttl=55 time=810 ms 64 bytes from 4.2.2.1: icmp_seq=30 ttl=55 time=832 ms 64 bytes from 4.2.2.1: icmp_seq=31 ttl=55 time=812 ms 64 bytes from 4.2.2.1: icmp_seq=32 ttl=55 time=821 ms 64 bytes from 4.2.2.1: icmp_seq=33 ttl=55 time=826 ms 64 bytes from 4.2.2.1: icmp_seq=34 ttl=55 time=815 ms 64 bytes from 4.2.2.1: icmp_seq=35 ttl=55 time=821 ms 64 bytes from 4.2.2.1: icmp_seq=36 ttl=55 time=824 ms top - 19:02:38 up 4 days, 11:26, 4 users, load average: 0.36, 0.75, 0.82 Mem: 4051312k total, 1062964k used, 2988348k free, 167004k buffers Swap: 6094840k total,0k used, 6094840k free, 680144k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 4245 root 15 0 791m 86m 10m S 39.6 2.2 1192:32 asterisk 18280 root 15 0 3812 600 516 S 2.0 0.0 0:59.00 pppoe 2582 root 15 0 5912 628 504 S 0.3 0.0 2:02.19 syslogd 18978 root 15 0 12744 1096 812 R 0.3 0.0 0:00.02 top 1 root 15 0 10352 700 588 S 0.0 0.0 0:01.14 init 2 root RT -5 000 S 0.0 0.0 0:00.01 migration/0 3 root 34 19 000 S 0.0 0.0 0:31.90 ksoftirqd/0 4 root RT -5 000 S 0.0 0.0 0:00.00 watchdog/0 5 root RT -5 000 S 0.0 0.0 0:00.01 migration/1 6 root 34 19 000 S 0.0 0.0 0:08.43 ksoftirqd/1 7 root RT -5 000 S 0.0 0.0 0:00.00 watchdog/1 8 root RT -5 000 S 0.0 0.0 0:00.13 migration/2 9 root 34 19 000 S 0.0 0.0 2:40.56 ksoftirqd/2 10 root RT -5 000 S 0.0 0.0 0:00.00 watchdog/2 11 root RT -5 000 S 0.0 0.0 0:00.05 migration/3 12 root 34 19 000 S 0.0 0.0 0:44.56 ksoftirqd/3 13 root RT -5 000 S 0.0 0.0 0:00.00 watchdog/3 14 root 10 -5 000 S 0.0 0.0 0:00.02 events/0 15 root 10 -5 000 S 0.0 0.0 0:00.00 events/1 16 root 10 -5 000 S 0.0 0.0 0:00.00 events/2 17 root 10 -5 000 S 0.0 0.0 0:00.00 events/3 18 root 10 -5 000 S 0.0 0.0 0:00.00 khelper 55 root 10 -5 000 S 0.0 0.0 0:00.00 kthread 62 root 10 -5 000 S 0.0 0.0 0:00.07 kblockd/0 63 root 10 -5 000 S 0.0 0.0 0:00.01 kblockd/1 64 root 10 -5 000 S 0.0 0.0 0:00.00 kblockd/2 65 root 10 -5 000 S 0.0 0.0 0:00.00 kblockd/3 66 root 17 -5 000 S 0.0 0.0 0:00.00 kacpid 166 root 17 -5 000 S 0.0 0.0 0:00.00 cqueue/0 167 root 18 -5 000 S 0.0 0.0 0:00.00 cqueue/1 Dave -- _ --
Re: [asterisk-users] sip attacks
How long ago was the last block from fail2ban? What could be is that the attacker hasn't yet realized that he has been blocked and is still trying, which although blocked by iptables it is still coming down the line for attempted connections. On Sun, Jul 31, 2011 at 7:04 PM, Dave George dgeo...@teletoneinc.com wrote: My asterisk server is getting bogged down every 5 minutes. My ping time is going from 60ms to 800 ms and the call quality is bad. I have fail2ban running and I am using iptables. I have two ip connections to the box. How can I tell if the poor performance is due to sip attacks? I don't see any reg attempts in my asterisk cli. I use to get frequent attacks but fail2ban seems to be taking care of that. See how ping time gets worst in a short space of time and server performance at the time: 64 bytes from 4.2.2.1: icmp_seq=6 ttl=55 time=87.8 ms 64 bytes from 4.2.2.1: icmp_seq=7 ttl=55 time=99.8 ms 64 bytes from 4.2.2.1: icmp_seq=8 ttl=55 time=107 ms 64 bytes from 4.2.2.1: icmp_seq=9 ttl=55 time=115 ms 64 bytes from 4.2.2.1: icmp_seq=10 ttl=55 time=120 ms 64 bytes from 4.2.2.1: icmp_seq=11 ttl=55 time=122 ms 64 bytes from 4.2.2.1: icmp_seq=12 ttl=55 time=123 ms 64 bytes from 4.2.2.1: icmp_seq=13 ttl=55 time=126 ms 64 bytes from 4.2.2.1: icmp_seq=14 ttl=55 time=122 ms 64 bytes from 4.2.2.1: icmp_seq=15 ttl=55 time=142 ms 64 bytes from 4.2.2.1: icmp_seq=16 ttl=55 time=142 ms 64 bytes from 4.2.2.1: icmp_seq=17 ttl=55 time=137 ms 64 bytes from 4.2.2.1: icmp_seq=18 ttl=55 time=186 ms 64 bytes from 4.2.2.1: icmp_seq=19 ttl=55 time=255 ms 64 bytes from 4.2.2.1: icmp_seq=20 ttl=55 time=310 ms 64 bytes from 4.2.2.1: icmp_seq=21 ttl=55 time=387 ms 64 bytes from 4.2.2.1: icmp_seq=22 ttl=55 time=445 ms 64 bytes from 4.2.2.1: icmp_seq=23 ttl=55 time=514 ms 64 bytes from 4.2.2.1: icmp_seq=24 ttl=55 time=583 ms 64 bytes from 4.2.2.1: icmp_seq=25 ttl=55 time=650 ms 64 bytes from 4.2.2.1: icmp_seq=26 ttl=55 time=715 ms 64 bytes from 4.2.2.1: icmp_seq=27 ttl=55 time=783 ms 64 bytes from 4.2.2.1: icmp_seq=28 ttl=55 time=821 ms 64 bytes from 4.2.2.1: icmp_seq=29 ttl=55 time=810 ms 64 bytes from 4.2.2.1: icmp_seq=30 ttl=55 time=832 ms 64 bytes from 4.2.2.1: icmp_seq=31 ttl=55 time=812 ms 64 bytes from 4.2.2.1: icmp_seq=32 ttl=55 time=821 ms 64 bytes from 4.2.2.1: icmp_seq=33 ttl=55 time=826 ms 64 bytes from 4.2.2.1: icmp_seq=34 ttl=55 time=815 ms 64 bytes from 4.2.2.1: icmp_seq=35 ttl=55 time=821 ms 64 bytes from 4.2.2.1: icmp_seq=36 ttl=55 time=824 ms top - 19:02:38 up 4 days, 11:26, 4 users, load average: 0.36, 0.75, 0.82 Mem: 4051312k total, 1062964k used, 2988348k free, 167004k buffers Swap: 6094840k total, 0k used, 6094840k free, 680144k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4245 root 15 0 791m 86m 10m S 39.6 2.2 1192:32 asterisk 18280 root 15 0 3812 600 516 S 2.0 0.0 0:59.00 pppoe 2582 root 15 0 5912 628 504 S 0.3 0.0 2:02.19 syslogd 18978 root 15 0 12744 1096 812 R 0.3 0.0 0:00.02 top 1 root 15 0 10352 700 588 S 0.0 0.0 0:01.14 init 2 root RT -5 0 0 0 S 0.0 0.0 0:00.01 migration/0 3 root 34 19 0 0 0 S 0.0 0.0 0:31.90 ksoftirqd/0 4 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/0 5 root RT -5 0 0 0 S 0.0 0.0 0:00.01 migration/1 6 root 34 19 0 0 0 S 0.0 0.0 0:08.43 ksoftirqd/1 7 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/1 8 root RT -5 0 0 0 S 0.0 0.0 0:00.13 migration/2 9 root 34 19 0 0 0 S 0.0 0.0 2:40.56 ksoftirqd/2 10 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/2 11 root RT -5 0 0 0 S 0.0 0.0 0:00.05 migration/3 12 root 34 19 0 0 0 S 0.0 0.0 0:44.56 ksoftirqd/3 13 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/3 14 root 10 -5 0 0 0 S 0.0 0.0 0:00.02 events/0 15 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 events/1 16 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 events/2 17 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 events/3 18 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 khelper 55 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 kthread 62 root 10 -5 0 0 0 S 0.0 0.0 0:00.07 kblockd/0 63 root 10 -5 0 0 0 S 0.0 0.0 0:00.01 kblockd/1 64 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 kblockd/2 65 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 kblockd/3 66 root 17 -5 0 0 0 S 0.0 0.0 0:00.00 kacpid 166 root 17 -5 0 0 0 S 0.0 0.0 0:00.00 cqueue/0 167 root 18 -5 0 0 0 S 0.0 0.0 0:00.00 cqueue/1 Dave --
Re: [asterisk-users] sip attacks
How big is the blocklist from fail2ban? - a few thousand entries and the network stack performance degrades. BillK On Sun, 2011-07-31 at 19:54 -0400, C F wrote: How long ago was the last block from fail2ban? What could be is that the attacker hasn't yet realized that he has been blocked and is still trying, which although blocked by iptables it is still coming down the line for attempted connections. On Sun, Jul 31, 2011 at 7:04 PM, Dave George dgeo...@teletoneinc.com wrote: My asterisk server is getting bogged down every 5 minutes. My ping time is going from 60ms to 800 ms and the call quality is bad. I have fail2ban running and I am using iptables. I have two ip connections to the box. How can I tell if the poor performance is due to sip attacks? I don't see any reg attempts in my asterisk cli. I use to get frequent attacks but fail2ban seems to be taking care of that. See how ping time gets worst in a short space of time and server performance at the time: 64 bytes from 4.2.2.1: icmp_seq=6 ttl=55 time=87.8 ms 64 bytes from 4.2.2.1: icmp_seq=7 ttl=55 time=99.8 ms 64 bytes from 4.2.2.1: icmp_seq=8 ttl=55 time=107 ms 64 bytes from 4.2.2.1: icmp_seq=9 ttl=55 time=115 ms 64 bytes from 4.2.2.1: icmp_seq=10 ttl=55 time=120 ms 64 bytes from 4.2.2.1: icmp_seq=11 ttl=55 time=122 ms 64 bytes from 4.2.2.1: icmp_seq=12 ttl=55 time=123 ms 64 bytes from 4.2.2.1: icmp_seq=13 ttl=55 time=126 ms 64 bytes from 4.2.2.1: icmp_seq=14 ttl=55 time=122 ms 64 bytes from 4.2.2.1: icmp_seq=15 ttl=55 time=142 ms 64 bytes from 4.2.2.1: icmp_seq=16 ttl=55 time=142 ms 64 bytes from 4.2.2.1: icmp_seq=17 ttl=55 time=137 ms 64 bytes from 4.2.2.1: icmp_seq=18 ttl=55 time=186 ms 64 bytes from 4.2.2.1: icmp_seq=19 ttl=55 time=255 ms 64 bytes from 4.2.2.1: icmp_seq=20 ttl=55 time=310 ms 64 bytes from 4.2.2.1: icmp_seq=21 ttl=55 time=387 ms 64 bytes from 4.2.2.1: icmp_seq=22 ttl=55 time=445 ms 64 bytes from 4.2.2.1: icmp_seq=23 ttl=55 time=514 ms 64 bytes from 4.2.2.1: icmp_seq=24 ttl=55 time=583 ms 64 bytes from 4.2.2.1: icmp_seq=25 ttl=55 time=650 ms 64 bytes from 4.2.2.1: icmp_seq=26 ttl=55 time=715 ms 64 bytes from 4.2.2.1: icmp_seq=27 ttl=55 time=783 ms 64 bytes from 4.2.2.1: icmp_seq=28 ttl=55 time=821 ms 64 bytes from 4.2.2.1: icmp_seq=29 ttl=55 time=810 ms 64 bytes from 4.2.2.1: icmp_seq=30 ttl=55 time=832 ms 64 bytes from 4.2.2.1: icmp_seq=31 ttl=55 time=812 ms 64 bytes from 4.2.2.1: icmp_seq=32 ttl=55 time=821 ms 64 bytes from 4.2.2.1: icmp_seq=33 ttl=55 time=826 ms 64 bytes from 4.2.2.1: icmp_seq=34 ttl=55 time=815 ms 64 bytes from 4.2.2.1: icmp_seq=35 ttl=55 time=821 ms 64 bytes from 4.2.2.1: icmp_seq=36 ttl=55 time=824 ms top - 19:02:38 up 4 days, 11:26, 4 users, load average: 0.36, 0.75, 0.82 Mem: 4051312k total, 1062964k used, 2988348k free, 167004k buffers Swap: 6094840k total,0k used, 6094840k free, 680144k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 4245 root 15 0 791m 86m 10m S 39.6 2.2 1192:32 asterisk 18280 root 15 0 3812 600 516 S 2.0 0.0 0:59.00 pppoe 2582 root 15 0 5912 628 504 S 0.3 0.0 2:02.19 syslogd 18978 root 15 0 12744 1096 812 R 0.3 0.0 0:00.02 top 1 root 15 0 10352 700 588 S 0.0 0.0 0:01.14 init 2 root RT -5 000 S 0.0 0.0 0:00.01 migration/0 3 root 34 19 000 S 0.0 0.0 0:31.90 ksoftirqd/0 4 root RT -5 000 S 0.0 0.0 0:00.00 watchdog/0 5 root RT -5 000 S 0.0 0.0 0:00.01 migration/1 6 root 34 19 000 S 0.0 0.0 0:08.43 ksoftirqd/1 7 root RT -5 000 S 0.0 0.0 0:00.00 watchdog/1 8 root RT -5 000 S 0.0 0.0 0:00.13 migration/2 9 root 34 19 000 S 0.0 0.0 2:40.56 ksoftirqd/2 10 root RT -5 000 S 0.0 0.0 0:00.00 watchdog/2 11 root RT -5 000 S 0.0 0.0 0:00.05 migration/3 12 root 34 19 000 S 0.0 0.0 0:44.56 ksoftirqd/3 13 root RT -5 000 S 0.0 0.0 0:00.00 watchdog/3 14 root 10 -5 000 S 0.0 0.0 0:00.02 events/0 15 root 10 -5 000 S 0.0 0.0 0:00.00 events/1 16 root 10 -5 000 S 0.0 0.0 0:00.00 events/2 17 root 10 -5 000 S 0.0 0.0 0:00.00 events/3 18 root 10 -5 000 S 0.0 0.0 0:00.00 khelper 55 root 10 -5 000 S 0.0 0.0 0:00.00 kthread 62 root 10 -5 000 S 0.0 0.0 0:00.07 kblockd/0 63 root 10 -5 000 S 0.0 0.0 0:00.01 kblockd/1 64 root 10 -5 000 S 0.0 0.0 0:00.00 kblockd/2 65 root 10 -5 000 S 0.0 0.0 0:00.00 kblockd/3
Re: [asterisk-users] different format in asterisk
Does anyone know about this... On 06/20/2011 04:34 PM, Nikhil wrote: Hi In asterisk channel ,I so number of variable regarding the Codec ,Can anyone explain what are those variable variable means.Below are the variables 1. chan-readformat 2. chan-writeformat 3. chan -rawreadformat 4. chan -rawwriteformat 5. chan-nativeformats Thanks Nikhil -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
