Got it! It's working fine with 25. Actually, I just revisited your KB
article and it does clearly instruct to test 1, 25, and so forth... But I
was still thinking spans, not channels. So my apologies for this RTFM
moment.
Thanks!
On Wed, Jan 15, 2014 at 5:43 PM, Shaun Ruffell wrote:
> On Wed
On Wed, Jan 15, 2014 at 05:29:44PM +, Rodrigo Borges Pereira wrote:
> Shaun, sorry to insist on this, but this kind of diagnostic is new for me
> and extremely valuable for my support operations.
>
> You say "when configured this way".. do you mean regarding dahdi? Here's my
> system conf, bas
Shaun, sorry to insist on this, but this kind of diagnostic is new for me
and extremely valuable for my support operations.
You say "when configured this way".. do you mean regarding dahdi? Here's my
system conf, based on your KB article for loop testing:
shell> cat system.conf
loadzone=us
defaul
On Wed, Jan 15, 2014 at 05:02:10PM +, Rodrigo Borges Pereira wrote:
> No, I see this:
>
[snip]
> shell> cat /proc/dahdi/1
> Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" B8ZS/ESF LOOP
>
>1 TE2/0/1/1 Clear Master RED
>2 TE2/0/1/2 Clear RED
>3 TE2/0/1/3 Clear RED
>4 TE2/0/1/4 Cl
No, I see this:
shell> cat /proc/dahdi/2
Span 2: TE2/0/2 "T2XXP (PCI) Card 0 Span 2" (MASTER) B8ZS/ESF LOOP
CRC4 error count: 1
E-bit error count: 1
25 TE2/0/2/1 Clear Master LOOP
26 TE2/0/2/2 Clear LOOP
27 TE2/0/2/3 Clear LOOP
28 TE2/0/2/4 Clear LOOP
29 TE2/0/2/5 Clear LOOP
30 TE2/0/
On Wed, Jan 15, 2014 at 04:18:55PM +, Rodrigo Borges Pereira wrote:
> Still no luck:
>
> shell> pgrep asterisk
> shell> ps -ef | grep asterisk
> shell> lsof /dev/dahdi/channel
> shell> lsof /dev/dahdi/1
> shell> lsof /dev/dahdi/2
> shell> chrt -f 99 patlooptest /dev/dahdi/2 -t 300 -v
> /de
I tried it on 123. Those user and PW did not work :-(
Sent from my Verizon Wireless 4G LTE DROID
Shaun Ruffell wrote:
>On Wed, Jan 15, 2014 at 04:00:19AM +, Rodrigo Borges Pereira wrote:
>> Ok, I'm a believer now:
>>
>>
>> shell> chrt -f 99 patlooptest /dev/dahdi/1 -t 300 -v
>> Using
Still no luck:
shell> pgrep asterisk
shell> ps -ef | grep asterisk
shell> lsof /dev/dahdi/channel
shell> lsof /dev/dahdi/1
shell> lsof /dev/dahdi/2
shell> chrt -f 99 patlooptest /dev/dahdi/2 -t 300 -v
/dev/dahdi/2: Device or resource busy
I can assure no PBX related process is running.
On
On Wed, Jan 15, 2014 at 04:00:19AM +, Rodrigo Borges Pereira wrote:
> Ok, I'm a believer now:
>
>
> shell> chrt -f 99 patlooptest /dev/dahdi/1 -t 300 -v
> Using Timeout of 300 Seconds
> Going for it...
> Timeout achieved Ending Program
> Test ran 28295 loops of 2039 bytes/loop with 0 erro
Ok, I'm a believer now:
shell> chrt -f 99 patlooptest /dev/dahdi/1 -t 300 -v
Using Timeout of 300 Seconds
Going for it...
Timeout achieved Ending Program
Test ran 28295 loops of 2039 bytes/loop with 0 errors
Still, any hint about this?
shell> lsof /dev/dahdi/2
shell>
shell> chrt -f 99 patl
On Tue, Jan 14, 2014 at 05:58:57PM +, Rodrigo Borges Pereira wrote:
>
> Running patlooptest following instructions on Digium KB, using dahdi 2.5.1
> with a TE205P. I'm getting this kind of output (not full output). Note, I'm
> using a standard cat5 ethernet cable (30cm), with a Digium T10i cro
Thanks for the tips. I forgot to mention, i did try lsof, and it comes out
with no result.
There is one thing I see different between the spans:
shell> head /proc/dahdi/1
Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" B8ZS/ESF LOOP
1 TE2/0/1/1 Clear Master RED
2 TE2/0/1/2 Clear RED
3 TE2/0
On Tue, Jan 14, 2014 at 12:54 PM, Rodrigo Borges Pereira
wrote:
> Interestingly, span 2 goes into loop mode, but patlooptest can't access it:
>
>> patlooptest /dev/dahdi/2 -t 300 -v
> /dev/dahdi/2: Device or resource busy
>
> And I do not have Asterisk running.
You should be able to use "lsof
Thanks.
The cable is straight, and I was using it together with dahdi:maint. Both
spans are set to provide (0). I've now tested span 1 again without cable,
and still same kind of result:
Timeout achieved Ending Program
Test ran 28309 loops of 2039 bytes/loop with 3692 errors
Interestingly, span
On Tue, Jan 14, 2014 at 11:58 AM, Rodrigo Borges Pereira
wrote:
> Cause for concern?
For patlooptest ensure that:
- Your ethernet cable is straight through and not crossover
- The span you're testing is set to "provide" timing, not recover
- In dahdi_tools you can "make utils" and just use dahdi
Hi there,
Running patlooptest following instructions on Digium KB, using dahdi 2.5.1
with a TE205P. I'm getting this kind of output (not full output). Note, I'm
using a standard cat5 ethernet cable (30cm), with a Digium T10i crossover.
Error 4985 (loop 19898, offset 425, error 214): Unexpected r
16 matches
Mail list logo
