* You are viewing the archive for February 27th, 2012

TCE400P diagnostic messages

Hello,

I’m running Asterisk C.3.7.2 and DAHDI 2.4.1.2
No changes in hardware since last April and asterisk version since last summer.

Since last Friday one of the call centers I support has been complaining of lagged audio, dropped calls, and “two calls at once”. Now I run 5 call centers off a single ABE installation and have never had only a single site have isolated problems like this. The only piece of the equation which is different from the other sites is the use of Digium TCE400P transcoder cards.

Since last Friday, these two diagnostic messages came over the kernel console message logger:

wctc4xxp: tce4001: Received diagnostic message:
wctc4xxp: tce4001: opcode: 0001 seq: 07 control: 41 channel: ffff length: e8 index: 00 type: 75 class: c1 function: 0000 0001 0000 0029 0212 51d4 00f7 ffff ffff 8f40 0002 16e0 0035 0001 0000 6574 00a0 6c8c 00a5 0212 0000 0001 0000 0000 0000 0029 0000 16e0 0035 ffff ffff 51d4 00f7 0001 0000 cccc cccc 0f90 0a00 8f40 0002 01d4 0000 0000 0000 0029 0000 16e0 0035 ffff ffff 51d4 00f7 0001 0000 5b4c 0001 8f40 0002 51d4 00f7 ffff ffff 0000 0000 8f44 0002 b220 0036 0060 0a01 5520 0059 5018 00f7 0000 0000 0980 0059 51d4 00f7 8f44 0002 51d4 00f7 ffff ffff 5018 00f7 0128 0000 075c 0900 aaaa aaaa aaaa aaaa 5555 5555 5555 5555 0000 0000 0000 0000 3794 0000 5555 5555 5555 5555 5555 5555
wctc4xxp: tce4001: Received diagnostic message:
wctc4xxp: tce4001: opcode: 0001 seq: 03 control: 41 channel: ffff length: d8 index: 01 type: 75 class: c1 function: 0000 0001 0001 0001 0212 f53c 00f6 ffff ffff 8f40 0002 1720 0035 0001 0000 6574 00a0 6e6c 00a5 0212 0000 0001 0000 0000 0000 0001 0000 1720 0035 ffff ffff f53c 00f6 0000 0000 cccc cccc 5390 0a00 8f40 0002 01d4 0000 f53c 00f6 0000 0000 5b4c 0001 8f40 0002 f53c 00f6 ffff ffff 0001 0000 8f44 0002 cc00 0036 b060 0a00 a9e0 0051 f380 00f6 0000 0000 5e40 0051 f53c 00f6 8f44 0002 f53c 00f6 ffff ffff f380 00f6 014d 0000 076c 0900 aaaa aaaa aaaa aaaa 5555 5555 5555 5555 0000 0000 0000 0000 3794 0000 5555 5555 5555 5555 5555 5555

I’ve searched high and low for the various key words and have absolutely nothing. Shy of digging through source, I’m curious if anyone else has seen this before.

Capture sip Response

Hello,
I am using a mix of Call files and AMI telnet from a perl app to place
calls. I sometimes get this in the CLI:

CDR Analyzer/Queue stats reporting

I’ve been tasked with finding and implementing a CDR/Queue analyzer to provide information to management about the call center’s performance. My Google-fu seems to be returning a lot of things that are more or less abandoned projects. Does anyone have any recommended solutions for a CentOS 6 / Asterisk 10 “vanilla” server? Not opposed to something commercial, provided it actually works and isn’t a disaster to set up.

Thank you,

Noah Engelberth
MetaLINK Technologies
System Administration
nengelberth@team-meta.net
419-636-0999 ext 100

The message does not contain any threats
AVG for MS Exchange Server (2012.0.1913 – 2114/4835)

AstLinux 1.0.2 Release

The AstLinux team is happy to announce the release of version 1.0.2. This release features several security updates. All current users are encouraged to upgrade as soon as possible. Please see the documentation at http://doc.astlinux.org for upgrade details or the official release pages.

Updates:
Asterisk (1.8.9.2)
DAHDI (2.5.0.2)
Rhino(0.99.5b1)
Wanpipe (3.5.24)
The Sangoma BRI/Hybrid cards (A500 + B700) are now supported via DAHDI

Security Fixes:
PHP(5.3.10)
OpenSSL(0.9.8t)

New Features:
A “Test SMTP Mail Relay” feature was added to verify msmtp configuration

See the change log on either of these release pages for more details

http://www.astlinux.org/release/102-asterisk-1892
http://www.astlinux.org/release/102-asterisk-1443

Enjoy,
The AstLinux Team

dahdi timing

Hi,

We heavily use meetme/SLA functionality in Asterisk, and continuously run into issues with dahdi timing. The two errors we get are:

ERROR[6518] res_timing_dahdi.c: Failed to configure DAHDI timing fd for 0 sample timer ticks

WARNING[22024] app_meetme.c: Unable to write frame to channel

Right now, dahdi in our setup uses the software timer (with res_timing_dahdi.so which gives much better results compared to res_timing_timerfd.so). On an idle system (Centos 6, Asterisk 1.8.7, dahdi 2.5), dahdi_test results are pretty good at about %99.99. However, when loaded, the numbers fluctuate between %99.90 and %99.99 which seem to cause the above errors.

We tried Sangoma UT50 as a timing device (it’s USB based), but the test results were worse (between 99.98 – 99.97 when idle, and had big dips when loaded and there is no IRQ sharing).

We are planning to order Digium AEX410 cards hoping they will be an improvement over dahdi_dummy and Sangoma. Does anyone have experience with these cards? Can we get a stable performance from them even under load?

Also (for Digium developers who might be reading this list), any plans for decoupling SLA from dahdi timing in future releases of Asterisk?

Thanks,
Mert

Correct call duration when transfer a call

Hi.
I am new to asterisk.
I have an ivr application with asterisk and voiceglue. I make a call from
asterisk (say to A) and when callee press a button voiceglue transfer the
callee to another number (say to B). When I look cdr records the billsec
between A and B always 0 and billsec with A shows the billsec for A and B.
I am confused. Is there a reliable way to get the real call durations?
Best regards.