[asterisk-r2] suddenly system has become unstable

[Anton Krall]

w1g1      Link encap:Point-to-Point Protocol
          UP POINTOPOINT RUNNING NOARP  MTU:8  Metric:1
          RX packets:811472099 errors:0 dropped:0 overruns:0 frame:0
          TX packets:811472099 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:2196809496 (2.0 GiB)  TX bytes:2196809496 (2.0 GiB)
          Interrupt:217 Memory:f8b40000-f8b41fff

[root at voip root]# wanpipemon -i w1g1 -c derr

Failed to Enable RBS RX mode.


[root at voip root]# wanpipemon -i w1g1 -c dert

Failed to Enable RBS TX mode.




From: Moises Silva <moises.silva at gmail.com>
Reply-To: <asterisk-r2 at lists.digium.com>
Date: Mon, 24 Aug 2009 10:19:52 -0400
To: <asterisk-r2 at lists.digium.com>
Subject: Re: [asterisk-r2] suddenly system has become unstable

When such thing happens, is time to use wanpipe debugging tools to see what
does the driver sees.

wanpipemon -i w1g1 -c derr
wanpipemon -i w1g1 -c dert

The -i option expects the interface name (depending on the wanpipe port, see
wanpipex.conf interface to know which one to use). The -c option is the
wanpipemon command to execute. 

derr = debug enable rbs receive
dert = debug enable rbs transmit

The debug output will be sent to /var/log/messages

I'd like to see the results by myself, contact me via msn when you see this
situation. If you don't see me online try doing it yourself. Each time you
try to make a call you should see changes in the ABCD tx and rx bits, first
changes in tx bits since we try to use the line, and then changes in the rx
bits when receiving almost immediately a reply from the other end.

If we don't see either bit chnage, either there is a driver, hardware or
connectivity problem.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20090824/954cef46/attachment.htm