Hello all
If I look at the sip peers table definition as provided with the source
of asterisk-1.8.23.0/ (looking at
contrib/realtime/mysql/sippeers.sql) for the sendrpid column it's an enum
with 2 possible values, yes and no.
However, the sip.conf allows 4 values, no, yes, rpid and pai.
Is this
I have an issue with ringing. Some users who call my switch hear
ringing and others don't. I have researched this and understand the
issue of firewalling and RTP. My switch has UDP ports 1 to 2
open. In any case I think that blocked RTP would block all ringing,
not just some.
I have
Thanks Russ,
I blacklisted wcopenpci, and i noticed an improvement:
# dahdi_test
Opened pseudo dahdi interface, measuring accuracy...
91.973% 96.242% 94.423% 77.932% 97.654% 87.114% 68.750% 87.417%
75.768% 95.693% 93.086% 77.936% 87.283% 92.996% 77.942% 77.926%
77.943% 89.545% 93.949% 87.032%
You would need to provide more information. Mobiles and landlines are
not SIP and yet you say calls are coming into your asterisk over SIP. So
what or who is doing the translation?
Initial thoughts are that it could be you are sending back SIP/180 with
no session progress and indicating
Another alternative is SecAst (Asterisk intrusion detection system). Grab the
free version from www.generationd.comhttp://www.generationd.com/?
It does everything fail2ban does, plus you have the option of blocking IP's
based on geograhic origin, detecting suspicious call patterns, etc.
Thanks for your support, I will try your suggestions,
will let you know how it goes,
Thanks,
On Tue, May 13, 2014 at 7:28 AM, Michelle Dupuis mdup...@ocg.ca wrote:
Another alternative is SecAst (Asterisk intrusion detection system).
Grab the free version from www.generationd.com​
It
On Tue, May 13, 2014 at 7:28 AM, Mike Leddy m...@loop.com.br wrote:
But on examination the /etc/init.d/dahdi start was only loading
the dahdi module.
With this in mind I might start looking around the system for things which
might cause jitter in the servicing of system timer interrupts:
Are
Thanks again Russ,
Just a quick reply for now.
No virtualization, but yes I am running a tickless kernel:
#
# Processor type and features
#
CONFIG_NO_HZ=y
Standard for debian kernels. I booted with nohz=off and the behaviour
changed. Unfortunately for the worse:
# dahdi_test
Opened pseudo
