On Wed, Jan 15, 2014 at 05:29:44PM +0000, 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, based on your KB article for loop testing: > > shell> cat system.conf > loadzone=us > defaultzone=us > span=1,0,0,esf,b8zs > clear=1-24 > span=2,0,0,esf,b8zs > clear=25-48 > > How could I configure now so I can get conclusive readings for span2?
No problem. So given the above configuration, there are only two channels that can be opened from user space, channels 1 and 25. So if you would like to keep things configured this way and check span 2, you would then just run patlooptest on channel 25. If you want to run patlooptest on individual channels in the span, configure like a PRI is normally: loadzone=us defaultzone=us span=1,0,0,esf,b8zs bchan=1-23 dchan=24 span=2,0,0,esf,b8zs bchan=25-47 dchan=48 Then you will be able to run patlooptest on all channels expcept 24 and 48 (which now have HDLC framing enabled on them). -- Shaun Ruffell Digium, Inc. | Linux Kernel Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
