* You are viewing Posts Tagged ‘module’

Load testing SFA

Hello,
does anyone know a way to load test the SkypeForAsterisk module without
actually generating calls to Skype Network? (only inside test environment).
I mean, is there any way to simulate the endpoint SFA talks to?

regards,
takeshi

codec_g729a implicated in file descriptor buildup

Hello,

I wonder if anyone else has noticed this.

I see a pair of calls to pipe() within the codec_g729a, and suddenly, I have
a leaked file descriptor that remains until asterisk dies.

Now, maybe no-one sees this, mainly because I have no g729 licenses on the
machines where this happens. And conversely,
I haven’t yet studied servers that do have licenses. Why have
codec_g729a.so loaded if I don’t have licenses? Well, I can
install licenses on the run as needed this way, and not worry about having
to install anything, or
muck things up if there is a mistake. I can mod the phones and get g729 used
without restarting asterisk
or loading modules.

On completely quiet machines, with no calls in or out, I get one descriptor
per day, maybe of a daily reload or something. I
haven’t gotten that far in my investigations yet.

Since the module isn’t compiled with debug info, the best stack trace I can
get is:

#0 0x4d5544a0 in pipe () from /lib/libc.so.6
#1 0xb69384ce in __cxa_finalize () from
/usr/lib/asterisk/modules/codec_g729a.so
#2 0xae7fdae4 in ?? ()
#3 0xae7fcae4 in ?? ()
#4 0×00001000 in ?? ()
#5 0×00000000 in ?? ()

The version of the g279 module is: Digium G.729A Module Version
1.6.2.0_3.1.4 (optimized for generic_32)

Just now, on a very low-volume asterisk server I am monitoring, two calls
just got processed. The
g729a codec did a pair of pipe() calls, and voila! I have one more open file
descriptor as reported by lsof.

Some of my servers (which are busy, but nowhere near capacity!) will build
up 100 such leaked descriptors per day, and unless I jack up the
maximum number of file descriptors, those servers will have to be restarted
about every 10 days, or they will eventually stop accepting
calls (or making them, for that matter). Not nice.

So, since there is no list of problems fixed with the current g729a module
distribution, (at least, no in the README in the dist,
is this a problem that is known? Is this a new problem? Should I call
support?

Anybody else see this?

murf

Dahdi 2.4.0 and unplugged spans

Hi,

I’m facing an issue with which loading wctdm24xxp module fails.

Here is relevant dmesg’s output :

[ 13.455729] dahdi: Telephony Interface Registered on major 196
[ 13.455729] dahdi: Version: 2.4.0
[ 13.510847] ACPI: PCI Interrupt 0000:01:0b.0[A] -> GSI 22 (level, low) ->
IRQ 22
[ 15.527788] wctdm24xxp 0000:01:0b.0: Timeout waiting for receive frame.
[ 17.527787] wctdm24xxp 0000:01:0b.0: Timeout waiting for receive frame.
[ 19.527787] wctdm24xxp 0000:01:0b.0: Timeout waiting for receive frame.
[ 21.527785] wctdm24xxp 0000:01:0b.0: Timeout waiting for receive frame.
[ 23.527784] wctdm24xxp 0000:01:0b.0: Timeout waiting for receive frame.
[ 25.527785] wctdm24xxp 0000:01:0b.0: Timeout waiting for receive frame.
[ 27.527785] wctdm24xxp 0000:01:0b.0: Timeout waiting for receive frame.
[ 29.527785] wctdm24xxp 0000:01:0b.0: Timeout waiting for receive frame.
[ 31.527785] wctdm24xxp 0000:01:0b.0: Timeout waiting for receive frame.
[ 33.527942] wctdm24xxp 0000:01:0b.0: Timeout waiting for receive frame.
[ 33.527995] wctdm24xxp 0000:01:0b.0: The firmware may be corrupted.
Please completely power off your system, power on, and then reload th
e driver with the ‘forceload’ module parameter set to 1 to attempt recovery.
[ 33.544741] ACPI: PCI interrupt for device 0000:01:0b.0 disabled
[ 33.544757] wctdm24xxp: probe of 0000:01:0b.0 failed with error -5
[ 34.157817] dahdi: Registered tone zone 2 (France)
[ 38.873158] warning: `ntpd’ uses 32-bit capabilities (legacy support in
use)
[ 47.462040] dahdi: Detected time shift.

My setup is :
Asterisk box with HA8+B400M <---ISDN/BRI----> Patton SN4638 <----SIP--->
Asterisk

Patton SN4638 is configured to behave as telco node (ie NT/PtmP).

To narrow my research scope, I’m wondering if the followin sentence is true
:
“if you load a dahdi module with a modprobe command (like modprobe
wctdm24xxp) disconnect any cable of any kind connected to the corresponding
PCI board, should this command succeed or fail”

In other words, do you need to connect board to a public network when
configuring it ?

Regards

Asteris 1.8 and mISDN – ‘mISDN’ (cause 66 - Channel not implemented)

HI!

Quoting Michael Nausch :

>> You installed the module, but did you load it in modules.conf?
>
> No, ’cause the modul should be autoloaded, as on Asterisk 1.6 it has
> done.

I know a little bit more, after testing this/last night!

If I start asterisk 1.8 with “service asterisk start” or
“/etc/init.d/asterisk start”, I can’t load chan_misdn.so

If I run asterisk 1.8 as root via “asterisk -vvvc” I can access my
ISDN-card and I be able to dial out to my PSTN provider! ;)

Example:
*CLI> == Using SIP RTP CoS mark 5
[Dec 1 10:49:47] ERROR[16779]: chan_sip.c:27876 setup_srtp: No SRTP
module loaded, can’t setup SRTP session.

Newbie question on GSM adapter

Hi,

I’ve recently installed Asterisk 1.6.2.13. I’d like to connect GSM Trunk to
it. I purchased a few Mobigater ProOpen gateways. It states that I should
use chan_celliax module to it. On the gsmopen site I see a comment in the
documentation that I can install the module on Asterisk 1.2.x, 1.4.x,
1.6.0.x but not on the 1.6.1.x. Could somebody tell me if I can install it
on my 1.6.2.13 version or I need to go back to 1.6.0.28 or the 1.4 line. If
it works on my installation what should I change in the makefile.

Thank you,

Zoltán

http://www.clamagent.org – Free Antivirus for Exchange

http://www.it-pro.hu

http://emaildetektiv.hu