Shaun,
Thank you. It seems like it is:
Span 1: WCT13x/0 "Wildcard TE131/TE133 Card 0" (MASTER) ESF/B8ZS RED
ClockSource
On Tue, Jan 12, 2021 at 6:32 AM Shaun Ruffell wrote:
> On Tue, Jan 12, 2021 at 05:31:31AM -0500, Dovid Bender wrote:
> > Yes but it does not tell me if the actual hardware
On Tue, Jan 12, 2021 at 05:31:31AM -0500, Dovid Bender wrote:
> Yes but it does not tell me if the actual hardware is being used or if its
> using the kernel (in place of hardware).
You should be able to get this information from the /proc/dahdi/ file. If
it is the timing master you will see a
Yes but it does not tell me if the actual hardware is being used or if its
using the kernel (in place of hardware).
On Wed, Jan 6, 2021 at 4:50 PM Steve Edwards
wrote:
> On Wed, 6 Jan 2021, Dovid Bender wrote:
>
> > The question is if it's using the card or the card or dahdi dummy (or
> >
On Wed, 6 Jan 2021, Dovid Bender wrote:
The question is if it's using the card or the card or dahdi dummy (or
whatever it's called) or if the card itself is being used.
Does this yield a clue?
pbx10:newline:13:47:53> module show like tim
Module Description
>
>
> pbx10:newline:13:25:02> timing test
> Attempting to test a timer with 50 ticks per second.
> Using the 'timerfd' timing module for this test.
> It has been 1000 milliseconds, and we got 50 timer ticks
>
>
I get:
as2-c3-njr2*CLI> timing test
Attempting to test a timer with 50 ticks per
On Wed, 6 Jan 2021, Dovid Bender wrote:
I have a box that I suspect had timing issues. I added a TE131 to see if
that would help. Is there any way for me to verify that Dahdi is using
the card for timing and not the kernel?
Does this yield a clue:
pbx10:newline:13:25:02> timing test
Hi,
I have a box that I suspect had timing issues. I added a TE131 to see if
that would help. Is there any way for me to verify that Dahdi is using the
card for timing and not the kernel?
--
_
-- Bandwidth and Colocation
Thanks Matt. The suggestion helped. No more slip erros.
Dave
Original Message
Subject: Re: [asterisk-users] dahdi timing source multiple cards
From: Matthew Fredrickson cres...@digium.com
Date: Fri, December 21, 2012 3:41 pm
To: asterisk-users@lists.digium.com
You
You must make sure that for each card, the timing parameter does not
exceed the number of spans on the card (unless you're using a timing
cable between cards). So you probably don't want to have anything above
a 4 for the timing parameter... I see below that you have 5-12 listed in
the timing
I have a box with 12 T1s (4 Te410P cards). The PSTN provider is reporting
slips and ask me to update the clock source. I have my system.conf set as
the following but when I run dahdi_scan only the ports on Card 1 are showing
up with syncsrc=1
system.conf :
span=1,1,0,esf,b8zs
bchan=2-24
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
11 matches
Mail list logo