[asterisk-ss7] chan_ss7 statistics (Was: Zaptel Buffer problems with chan_ss7)

[Anders Baekgaard]

Hello,

This "Excessive poll delay" warning is a known and yet mysterious problem. We 
see it on some machines, but not on others, and we have not gathered 
sufficient statistics to narrow down the cause for it.

It would be very useful to gather that statistics in the form of output from 
the shell commands:

uname -a
/sbin/lspci
cat /proc/cpuinfo
cat /proc/meminfo
cat /proc/interrupts
grep "Excessive poll delay" /var/log/asterisk/messages | tail -10

(If your asterisk messages file is located elsewhere, please change the grep 
command).

Please mail it directly to me with the Subject "chan_ss7 statistics".

I kindly request everybody reading this post to help solving the problem, 
regardless you experience it your self.

Thank you in advance.

Best regards
Anders Baekgaard


On Wednesday 17 May 2006 11:14, Kai Militzer wrote:
> Hello everyone,
>
> I have two machines running chan_ss7. Both use a TE205P with the same
> zaptel version and configuration file, both have the same Kernel-Version
> (debian 2.6.8-3, only differ in CPU type) and except the PCs the same
> SS7 config. What differs are the Mainboards and CPUs. One is a AMD
> Duron, the other a P4 with 3Ghz.
>
> On the seconds machine (the P4) I get error like that all the time:
>
> May 17 11:12:36 WARNING[29307]: mtp.c:1539 mtp_thread_main: Empty Zaptel
> output buffer detected, outgoing packets may have been lost on link 'l1'.
> May 17 11:12:36 NOTICE[29307]: mtp.c:1217 mtp2_read_su: Short MTP2 frame
> len 3 < 5 on link 'l1'.
> May 17 11:12:36 WARNING[29307]: mtp.c:1492 mtp_thread_main: Full Zaptel
> input buffer detected, incoming packets may have been lost on link 'l1'.
> May 17 11:12:36 WARNING[29307]: mtp.c:1539 mtp_thread_main: Empty Zaptel
> output buffer detected, outgoing packets may have been lost on link 'l1'.
> May 17 11:12:36 WARNING[29307]: mtp.c:1438 mtp_thread_main: Excessive
> poll delay 6737!
>
> It seems not to influence the performance of the channel, calls in both
> directions are possible and the sound is good. I have no real
> explanation where these error come from. Maybe one of you can shed some
> light on it.
>
> Regards,
> Kai