[asterisk-users] Realtime peers and sendrpid

2014-05-13 Thread Ishfaq Malik
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 discrepancy an oversight? Is it possible to set the system default
to pai but an individual peer to rpid via a realtime table?

I have tried setting the system value to pai and a single peer value to yes
but it still sent pai rather than rpid.

Thanks in Advance

Ish
-- 

Ishfaq Malik
Department: VOIP Support
Company: Packnet Limited
t: +44 (0)845 004 4994
f: +44 (0)161 660 9825
e: i...@pack-net.co.uk
w: http://www.pack-net.co.uk

Registered Address: PACKNET LIMITED, Duplex 2, Ducie House
37 Ducie Street
Manchester, M1 2JW
COMPANY REG NO. 04920552
-- 
_
-- 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] Ringing issue

2014-05-13 Thread D'Arcy J.M. Cain
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 one origination provider.  As far as I can tell the issue is
related to the remote user's provider.  My sister does not hear ringing
when she calls from her Roger's cell phone but she does from her Vonage
phone.  I hear ringing when calling in from my Koodo cell phone.  Some
land lines work and others do not.

The server is not behind a NAT and neither is the origination
provider.  There is a firewall but port 5060 is open (UDP and, just in
case, TCP) as well as the RTP ports mentioned above.

I am not sure where to look next.  I assume that there is some sort of
signaling that I am not doing but I can't figure out where.  Can anyone
suggest what area I should be looking?

Thanks.

-- 
D'Arcy J.M. Cain
System Administrator, Vex.Net
http://www.Vex.Net/ IM:da...@vex.net
VoIP: sip:da...@vex.net

-- 
_
-- 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] Terrible dahdi_test results

2014-05-13 Thread Mike Leddy
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% 91.939% 71.877% 90.648% 88.163% 
77.173% 97.651% 77.932% 77.942% 77.929% 76.548% 80.922% 90.292% 
81.977% 89.354% 79.203% 76.665% 77.935% 91.000% 68.182% 95.018%
--- Results after 40 passes ---
Best: 97.654% -- Worst: 68.182% -- Average: 84.673880%
Cummulative Accuracy (not per pass): 86.629

But on examination the /etc/init.d/dahdi start was only loading 
the dahdi module. 

# lsmod | egrep 'wc|dahdi'
dahdi 192295  0 
crc_ccitt  12347  1 dahdi

After a modprobe wcte11xp the situation is:

# lsmod | egrep 'wc|dahdi'
dahdi_echocan_oslec12578  30 
echo   12652  1 dahdi_echocan_oslec
wcte11xp   21535  0 
dahdi 192295  2 wcte11xp,dahdi_echocan_oslec
crc_ccitt  12347  1 dahdi

The test returns to as it was before:

# dahdi_test 
Opened pseudo dahdi interface, measuring accuracy...
89.100% 89.212% 88.871% 89.078% 89.286% 89.559% 89.358% 89.423% 
89.184% 89.083% 88.931% 89.070% 89.110% 88.818% 88.573% 89.091% 
89.006% 88.978% 89.157% 89.069% 89.112% 88.890% 89.374% 88.900% 
89.042% 89.043% 88.946% 88.786% 88.865% 89.259% 88.951% 88.763% 
88.944% 89.123% 88.956% 88.976% 89.044% 89.040% 88.970% 89.148%
--- Results after 40 passes ---
Best: 89.559% -- Worst: 88.573% -- Average: 89.052215%
Cummulative Accuracy (not per pass): 89.052

Still experimenting. 

Best regards,

Mike


On Mon, 2014-05-12 at 17:23 -0500, Russ Meyerriecks wrote:
 On Mon, May 12, 2014 at 4:57 PM, Mike Leddy m...@loop.com.br wrote:
 [   39.223031] wcopenpci: Module loaded
 [   39.751770] wcte1xxp: Setting yellow alarm
 
 # dahdi_hardware
 pci::06:00.0 wcte11xp+e159:0001 Digium Wildcard
 TE110P T1/E1 Board
 
 
 Mike,
   This stuff predates my time on this project, but it looks like
 wcopenpci and wcte1xxp might be conflicting on your system because
 they register against the same hardware. I might try blacklisting the
 wcopenpci driver in /etc/modprobe.d/dahdi.blacklist.conf and rebooting
 or reloading dahdi.
 
 
 -- 
 Russ Meyerriecks
 Digium, Inc. | Linux Kernel Developer
 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
 direct: +1 256-428-6025
 Check us out at: www.digium.com  www.asterisk.org



-- 
_
-- 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] Ringing issue

2014-05-13 Thread Gareth Blades
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 ringing but the other end is 
misconfiguration and not generating its own ring tone. This is possible 
if you have multiple providers sending you calls or one provider using 
different kit for different geographic areas.


On 13/05/14 12:01, D'Arcy J.M. Cain wrote:

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 one origination provider.  As far as I can tell the issue is
related to the remote user's provider.  My sister does not hear ringing
when she calls from her Roger's cell phone but she does from her Vonage
phone.  I hear ringing when calling in from my Koodo cell phone.  Some
land lines work and others do not.

The server is not behind a NAT and neither is the origination
provider.  There is a firewall but port 5060 is open (UDP and, just in
case, TCP) as well as the RTP ports mentioned above.

I am not sure where to look next.  I assume that there is some sort of
signaling that I am not doing but I can't figure out where.  Can anyone
suggest what area I should be looking?

Thanks.



--
_
-- 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 1.8.22

2014-05-13 Thread Michelle Dupuis
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.


-=M=-

All opinions posted are my own. But as an employee of GenerationD System my 
views are undoubtedly biased :)



From: asterisk-users-boun...@lists.digium.com 
asterisk-users-boun...@lists.digium.com on behalf of motty cruz 
motty.c...@gmail.com
Sent: Monday, May 12, 2014 5:43 PM
To: Asterisk Users List
Subject: [asterisk-users] Asterisk 1.8.22

Hello,
recently I have seen spike in attacks on my asterisk server, this is what I get 
on the LCD of my phone: 201@76.220.5.205mailto:201@76.220.5.205

or calls from 1000 sip1000@76.2230.5.205mailto:1000@76.2230.5.205,

have any idea on how to stop this calls?

Thanks,
-- 
_
-- 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 1.8.22

2014-05-13 Thread motty cruz
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 does everything fail2ban does, plus you have the option of blocking
 IP's based on geograhic origin, detecting suspicious call patterns, etc.


  -=M=-

 All opinions posted are my own. But as an employee of GenerationD System
 my views are undoubtedly biased :)


  --
 *From:* asterisk-users-boun...@lists.digium.com 
 asterisk-users-boun...@lists.digium.com on behalf of motty cruz 
 motty.c...@gmail.com
 *Sent:* Monday, May 12, 2014 5:43 PM
 *To:* Asterisk Users List
 *Subject:* [asterisk-users] Asterisk 1.8.22

  Hello,
 recently I have seen spike in attacks on my asterisk server, this is what
 I get on the LCD of my phone: 201@76.220.5.205

 or calls from 1000 sip1000@76.2230.5.205,

  have any idea on how to stop this calls?

  Thanks,

 --
 _
 -- 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] Terrible dahdi_test results

2014-05-13 Thread Russ Meyerriecks
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 you running under a virtualized environment?
Are you running a tickless kernel? (maybe try adding nohz=off to your
kernel boot parameters)
Is there some sort of processor power saving or frequency scaling going on
that interrupts the system timer?

-- 
Russ Meyerriecks
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
direct: +1 256-428-6025
Check us out at: www.digium.com  www.asterisk.org
-- 
_
-- 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] Terrible dahdi_test results

2014-05-13 Thread Mike Leddy
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 dahdi interface, measuring accuracy...
66.653% 66.683% 66.683% 66.807% 67.705% 66.666% 66.651% 66.679% 
67.516% 66.882% 66.649% 66.657% 66.678% 66.668% 66.672% 66.664% 
66.675% 66.675% 66.659% 66.692% 66.631% 66.187% 66.650% 66.710% 
66.648% 66.633% 66.714% 66.638% 66.688% 66.794% 66.645% 66.696%
--- Results after 32 passes ---
Best: 67.705% -- Worst: 66.187% -- Average: 66.726523%

Comparing the boot messages without nohz=off:

[0.00] hpet clockevent registered
[0.00] Fast TSC calibration failed
[0.00] TSC: Unable to calibrate against PIT
[0.00] TSC: using HPET reference calibration
[0.00] Detected 2593.456 MHz processor.

and with nohz=off:

[0.00] hpet clockevent registered
[0.00] Fast TSC calibration using PIT
[0.00] Detected 2593.225 MHz processor.

I am encouraged that we seem to be homing in on the problem. I need to
read up a bit more on the subject and look at possible power 
saving issues on this machine.

Best regards,

Mike


On Tue, 2014-05-13 at 15:26 -0500, Russ Meyerriecks wrote:
 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 you running under a virtualized environment?
 Are you running a tickless kernel? (maybe try adding nohz=off to your
 kernel boot parameters)
 Is there some sort of processor power saving or frequency scaling
 going on that interrupts the system timer?
 
 
 -- 
 Russ Meyerriecks
 Digium, Inc. | Linux Kernel Developer
 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
 direct: +1 256-428-6025
 Check us out at: www.digium.com  www.asterisk.org



-- 
_
-- 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