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 str
ngs
persistent. When the mailing list post you linked was first written, there was
only a single /etc/modules.conf file. That single file has been split up into
multiple files in /etc/modprobe.d now.
I hope this helps,
Shaun
--
_
c parts on the
machines where you want to load DAHDI modules you sign with the private
part.
See:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Kernel_Administration_Guide/sect-signing-kernel-modules-for-secure-boot.html
Regards,
Shaun
--
__
hat would allow me to
answer this question.
Cheers,
Shaun
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
Check out the new Asterisk community forum at: https://community.asterisk.org/
New to As
0-rc1.tar.gz
[2]
http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commit;h=8c8b9b6df0d5757cad25b40efeb15ba1a7c95bdf
(although it looks like the dahdi-linux-complete tarball has not been
updated since the final 3.1.0 was released)
Cheers,
Shaun
--
__
"
>
> If you have a link, please share.
http://blog.krisk.org/2012/06/everything-you-wish-you-didnt-need-to.html
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at
products, including the
phones.
If you have an issue you can open up support tickets through that
site as well.
Cheers,
Shaun
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL
the cable is disconnected from the
card, there is something flaky in the connection with the central
office, a filter is causing a voltage drop, etc..
One thing to check is that the 'opermode' module parameter is set
for the country that you&#x
On Mon, Jun 01, 2015 at 05:09:59PM -0400, sean darcy wrote:
> On 06/01/2015 04:49 PM, Shaun Ruffell wrote:
> >On Mon, Jun 01, 2015 at 04:24:31PM -0400, sean darcy wrote:
> >>On fedora 21, trying to build dahdi for kernel 4.0.4.
> >>
> >>gcc-4.9.2-6.fc21.x86_64
rce while waiting for the next release of
dahdi-linux.
[1]
http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commitdiff;h=1cc0ad510acd404e63923ed3062b93
[2] https://issues.asterisk.org/jira/browse/DAHLIN-346
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Dav
onse to receiving one of these frames.
I think it's safe to ignore them. Alternatively, if the comfort
noise packets are generated from SIP endpoints that you have control
over, you could see if there are any options to disable generation
of those frames.
--
Shaun Ruffell
Digium, Inc. |
otocol. I don't
know if it is the *best* way, but I use:
$ asterisk -rx 'pri show spans'
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check
ate firmware for TE133/TE131 to 780019") [1]
[1]
http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commit;h=45b4937a350ec4221ade0bc6c58c66cab
This change was first relesed in DAHDI-Linux 2.9.1.
Cheers,
Shaun
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis
ixed in 2.9.2-rc2 in commit (a1ff3cb0
"dahdi: Stop tones on channel when updating tone zone.") [1]
[1]
http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commit;h=a1ff3cb0c0f3f4e65d734f4a71a090f5484505b4
The bug in dahdi was hit in this case since dahdi_cfg was called
while asterisk had ch
te12xp
> dahdi 224134 11
> dahdi_transcode,wcb4xxp,wctdm,wcfxo,wctdm24xxp,wcte11xp,wct1xxp,wcte12xp,dahdi_voicebus,wct4xxp,oct612x
> crc_ccitt 1717 2 wctdm24xxp,dahdi
Looking at the above, it appears you do not have the wcte13xp driver
loaded.
Check your /et
to the system core and is no longer a loadable module.
--
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
--
_
-- Ban
inux-2.6.2 install' failed with 512.
This was fixed in the DAHDI sources in "dahdi: Replace
create_proc_entry() with proc_create_data()" [1]
You will need to update to at least dahdi-linux 2.8.0 if you would
like to run against kernels newer than 3.10.
[1] http://git.aster
ago
> His issue was obvious and well stated until another poster confused the issue!
Just to keep it clear for anyone who stumbles on this thread in the
future, this can sometimes work if you set the callprogress=yes
opt
]
https://github.com/sruffell/asterisk-working/blob/svn_trunk/configs/chan_dahdi.conf.sample#L1038-L1059
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www
== Incoming call from 059332640
>
> -- Executing [s@from-pstn:2] *Dial*("*DAHDI/5-1*", "") in new stack
Looking at the above, are you trying to dial out on the same channel
with the inbound call?
--
Shaun Ruffell
Digium, Inc. | Linux Ke
plication, but I have
> plenty of CPU headroom.
>
> Coincidentally, 512 is my target. Any clues on how to get 200 more?
Steve,
If you're looking to reduce the CPU overhead of processing meetme
conferences, this email from awhile ago may be of some help:
http://thread.gmane.org/gman
On Mon, Mar 03, 2014 at 08:53:16AM -0800, Justin Killen wrote:
> Plus, some traffic got split off into the app-dev list (and there's the dev
> list).
PlusPlus, the forums [1] have siphoned a bit of the traffic.
[1] http://forums.digium.com/viewforum.php?f=42
--
Shaun Ruffell
ny
calls to the drivers. My guess is this has more to do with the state
/ configuration of Asterisk.
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us
> > card. Then I enter asterisk console, and once I do a "pri show channels",
> > the console no longer works correctly. There's no output for any command
> > after that. If I type "pri show" and hit tab for completion, console
> > freezes there,
kernel.h.
Something like:
diff --git a/include/dahdi/kernel.h b/include/dahdi/kernel.h
index f2f9ec5..c19aec5 100644
--- a/include/dahdi/kernel.h
+++ b/include/dahdi/kernel.h
@@ -43,6 +43,7 @@
#include
#include
#include
+#include
#ifdef CONFIG_DAHDI_NET
#include
Doe
nstalling newer versions of DAHDI.
Although, dahdi-tools should probably have a configure script test
for a working implementation of sem_open and use another mechanism
if it is not available.
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 -
-se, but it's how most POSIX libraries
on linux (including the one installed on your system) implement the
named semaphores.
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at:
On Wed, Feb 12, 2014 at 05:49:49PM +, Rodrigo Borges Pereira wrote:
> Hello Shaun,
>
> This system is a custom distro, based on debian and currently built around
> kernel 2.6.35.8. Is sem_open introduced only in DAHDI 2.9 ?
Yes. It was added in [1] in order to prevent errors w
onfigure.
>
> Notice: Configuration file is /etc/dahdi/system.conf
> *line 15: Unable to create 'dahdi_cfg' mutex.*
Which distro / version are you running? It appears that the sem_open
call has failed on this platform.
There does appear to be a mistake in the code though with
0/28 Clear (In use) (EC: VPMOCT032 - INACTIVE)
> 29 WCT13x/0/29 Clear (In use) (EC: VPMOCT032 - INACTIVE)
> 30 WCT13x/0/30 Clear (In use) (EC: VPMOCT032 - INACTIVE)
> 31 WCT13x/0/31 Clear (In use) (EC: VPMOCT032 - INACTIVE)
>
>
>
>
>
dahdi devices loaded? What is the output of
dahdi_scan or "cat /proc/dahdi/1"?
--
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
--
_
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? H
D
> 23 TE2/0/1/23 Clear RED
> 24 TE2/0/1/24 Clear RED
That explains it. Your channels are bound together in one clear
channel on span 1. When configured this way, you can only open the
"master" channels. All the data from the other channels (timeslots)
are then added to this ma
CTDM/0/5 FXSKS RED (EC: VPMOCT032 - INACTIVE)
7 WCTDM/0/6 Reserved
8 WCTDM/0/7 Reserved
--
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
--
___
e to open channels via
/dev/dahdi/. In fact, they generally open
/dev/dahdi/channel and then use the SPECIFY ioctl to bind that
particular file descriptor to a specific dahdi channel.
So try 'lsof /dev/dahdi/channel' and see what you see.
Cheers,
Shaun
--
Shaun Ruffell
Digium, Inc.
pposedly good card.
>
> appreciate any input, thx.
Those events (29 and 30) indicate that patlooptest isn't able to
keep up with the hardware.
Do you get the same thing when you run patloop test with elevated
permissions?
$ chrt -f 99 patlooptest
Cheers,
Shaun
--
Shaun Ruffell
Digi
e software.
>
> All that to say, try upgrading DAHDI and see what happens.
As far as Olivier's concern, I still vote there is some physical
cabling issue that is causing problems.
However, just for posterity, in my experience if HDLC aborts are
occuring and there are timing slips, it d
On Mon, Jan 13, 2014 at 04:13:49PM +0100, Olivier wrote:
> 2014/1/10 Shaun Ruffell
>
> > On Fri, Jan 10, 2014 at 08:34:57PM +0100, Olivier wrote:
> > > 2014/1/10 Shaun Ruffell
> > > >
> > > > You've configured the card to recover timing from
On Fri, Jan 10, 2014 at 08:34:57PM +0100, Olivier wrote:
> 2014/1/10 Shaun Ruffell
> >
> > You've configured the card to recover timing from the provider?
>
> I'm not sure but I don't think so as I've just configured the card with:
>
> sp
ming from the provider? If
so, do your slips follow the actual cable that you were using to
connect to provider or PBX?
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
iPath
> and compare two /pro/dahddi/1 outputs.
> Thoughts ?
Yes, You can monitor the timing slips to see the rate at which they
occur, then connect just one span direct and make sure you don't
have slips, then one span directly to the HiPath and make sure you
don't ha
d definition of PDE_DATA [1] in kernel
2.6.32-431.
2.8.0.1 [2] or 2.7.0.2 [3] should work for you.
[1] https://issues.asterisk.org/jira/browse/DAHLIN-330
[2]
http://downloads.asterisk.org/pub/telephony/dahdi-linux/dahdi-linux-2.8.0.1.tar.gz
[3]
http://downloads.asterisk.org/pub/telephony/da
On Tue, Dec 03, 2013 at 10:18:54PM -0800, Ira wrote:
> Hello Shaun,
>
> Tuesday, December 3, 2013, 7:20:34 PM, you wrote:
>
> > Based on some direct replies that you sent, my current belief is
> > that you are not recompiling dahdi_echocan_hpec for the new versions
> &
steps 4 and 6 from the HPEC readme [1], do you still
have problems when you try the new versions of the drivers?
[1] http://downloads.digium.com/pub/telephony/hpec/README
Cheers,
Shaun
--
Shaun Ruffell
Digium, Inc. | Li
dahdi
# modinfo -F version dahdi
2.8.0-rc4
# dahdihpec_enable
Digium High-Performance Echo Canceller Enabler
Copyright (C) 2006-2009 Digium, Inc.
Version
Found valid HPEC licenses for 128 channels.
Successfully enabled 128 channels.
Thanks,
Shaun
--
Shaun Ruffell
Digium, Inc.
/sync'
Hi, it's safe to ignore this message, but for future reference I
just committed a change [1] that will now prevent it from showing,
which will be in the final v2.8.0 release of DAHDI-tools.
[1] http://git.asterisk.org/gitweb/?p=dahdi/tools.git;a=commit;h=c27664dc1b3
Cheers
On Tue, Nov 19, 2013 at 01:54:16PM +0400, Dmitry Melekhov wrote:
> Hello!
>
> Could somebody at least tell me is such data link still supported?
>
> Thank you!
Yes, but you will need to edit include/dahdi/dahdi_config.h and
ensure that CONFIG_DAHDI_NET is defined.
Cheers,
S
On Tue, Nov 05, 2013 at 05:02:13PM +, Rodrigo Borges Pereira wrote:
> Hello,
>
> Can someone confirm to me if Asterisk 1.4 can be used with DAHDI 2.7 ?
>
> Thanks in advance.
2.7 is not tested against the head of the Asterisk 1.4 branch, but
it *should* work.
Cheers,
S
e else run into this? How did you get around it?
libuuid-devel is what I think you need.
As an aside, in the asterisk source there is an install_prereq
script that can be used to install all the necessary packages for
your platform:
$ sudo contrib/scripts/install_prereq install
Cheers,
Shaun
the overhead of processing another
interrupt.
[snip]
So I guess I would be interested to hear if a kernel update is all
you need to have good results with the core timer.
If not...it might be worth investigating and measuring adding
hrtimer support into the core timer.
Cheers,
Shaun
--
Shaun
ean. It's most likely either a)
misconfiguration between the card settings and the provider b)
cabling between the card and the smart jack or c) Just something bad
on the provider's end. The probability of it being system / hardware
related is low IMO.
I take it though your old install still w
ing isn't perhaps
running dahdi_cfg in the background (or did you run it multiple
times after loading the card?) Normally I only see one "Calling
startup" line.
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out
On Tue, Jul 30, 2013 at 11:13:55AM -0400, Andre Goree wrote:
> On Tue, Jul 30, 2013 at 10:56 AM, Shaun Ruffell wrote:
> > On Tue, Jul 30, 2013 at 10:36:58AM -0400, Andre Goree wrote:
> >
> > > I've posted the configs and the output of a 'pri debug' below
more or contacting customer support, it
might be easy to change that one line and see if the behavior is
different.
--
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
--
ations for each audio packet. Keeping the
kernel tickless should also work fine here when using a software
timer to mix your audio since the kernel will set the timer to fire
at the next timer expiration (whatever that was set to).
So, in summary...I've not seen any problems related to the t
, those cards do support adding a hardware
echocancelation module. But I would recommend trying the software
solutions first.
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digiu
git.asterisk.org/gitweb/?p=team/sruffell/dahdi-linux.git;a=patch;h=e4d89ffa7485";
| patch -p1
[1]
http://git.asterisk.org/gitweb/?p=team/sruffell/dahdi-linux.git;a=commitdiff;h=e4d89ffa7485
Cheers,
Shaun
--
pmadt032_x86_64.o.cmd
> for
> /home/mclaborn/asterisk/dahdi-2.6.y-snapshot-20130528-linux-20a479b/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_64.o
No, that's normal. It's a side effect that the compiler doesn't
know all the options that were used to produce the precompile
VPMADT0
ux.git;a=commit;h=160edc8c9db
If you don't have git installed on the machine you would like to
install this on, you can use the 'snapshot' link when looking at the
shortlog of the 2.6.y branch at git.asterisk.org [3] which will
allow you to download a tar.gz file.
[3]
http://git.as
; What is wrong ?
>
This was resolved in commit "xpp: Do not typedef bool on RHEL 5.2 or
later" [1] which was released in DAHDI-Linux 2.6.2.
Cheers,
Shaun
[1]
http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commit;h=179a48862daf35d022f6fecaf7e5c8195f9d4921
--
Shaun Ruffe
anscoders from g723 to anything else in
> > Asterisk 10.7.1. Does anybody know how to fix that?
If you do not want to arrange to pay your own royalties, a
transcoding card like the TCE400B [1] can also handle transcoding to
and from G.723.1.
[1]
http://www1.digium.com/en/products/telephony-cards/voi
wcte11xp-e159:0001 Digium Wildcard TE110P T1/E1 Board
>
> run 'dahdi_genconf modules' to load support for only
> the DAHDI hardware installed in this system. By
> default support for all DAHDI hardware is loaded at
> DAHDI start.
>
>
>
> any idea
are other good sources of documentation. Also,
there are active forums [1] for those who do not want to be bothered
by top vs bottom posting and want a more tighly controlled
presentation of any discussions.
[1] http://forums.asterisk.org.
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Da
lk down memory lane on top vs bottom posting on the Asterisk
mailing lists:
http://thread.gmane.org/gmane.comp.telephony.pbx.asterisk.user/254997
--
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
--
_
posted you had #include
dahdi-channels.conf. Would it be possible to send that configuration
options you have attached in that file as well?
Cheers,
Shaun
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - U
have the disclaimer removed? They may be interested in:
http://www.goldmark.org/jeff/stupid-disclaimers
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us
t;.
In practice, I've found that it's generally better to fix what on
the system is causing latency to grow so large instead of enabling
that option.
Cheers,
Shaun
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville,
at DAHDI is installed before
compiling libpri.
[1] http://svnview.digium.com/svn/libpri?view=revision&revision=2294
Cheers,
Shaun
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digi
e
There isn't a 1.4 version of DAHDI. However version v2.6.0 will not
build any PCI drivers if the Kernel does not have the PCI bus
configured.
[1] http://svnview.digium.com/svn/dahdi?view=revision&revision=10397
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davi
d
Hmm... it looks like commit 10682 "dahdi_hardware: Detect the Digium
TE820 card" [1] is on the 2.6 branch in subversion but is not in the
2.6.1 release. If you need dahdi_hardware to work, you can install
DAHDI-Tools from trunk or you can wait until the next release of
DAHDI.
[1] htt
On Thu, Nov 08, 2012 at 07:41:45AM +0100, martin f krafft wrote:
>
> My systems are already managed automatically, thankfully no longer
> with Puppet. ;)
Just out of curiosity why do you say this?
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Hunts
working fine. Is there some kernel module that I'm
> missing?
Support for the TE820 was added to the wct4xxp driver in DAHDI-Linux
v2.6.0. DAHDI-Linux 2.6.1 is the latest version. I bet updating
DAHDI-Linux and DAHDI-Tools is all you need to do.
Cheers,
Shaun
--
Shaun Ruffell
Digium, Inc.
nalling=fxo_ks
> context=dummy
> group=63
> channel=>5
>
>
> I can now dial out on group 63 and it rings in the simulation
> context, which I forward to a SIP phone for testing.
>
> Is that what you expected to see?
Basically yes. That should allow you to try things out
Minor correction below:
On Tue, Oct 09, 2012 at 12:32:44PM -0500, Shaun Ruffell wrote:
> On Tue, Oct 09, 2012 at 11:46:04AM -0500, Mitch Claborn wrote:
> >
> > (Now if I just didn't have to wait to get on-site where those lines
> > are to try it. Too bad there isn&
lation" context.
Dynamic local spans have been around for awhile but I've only used them
on a regular basis since 2.6.0+.
Cheers,
Shaun
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsvill
On Tue, Oct 02, 2012 at 11:22:31PM -0400, Pat Collins wrote:
> Shaun,
> To make more sense of the code, I changed
> #define DAHDI_XBIT(3 >> 2) to
> #define DAHDI_XBIT(0)
>
> Sadly, incoming calls do not work. Not sure exactly how to START or RI
and seized
Perhaps you could edit dahdi_rbs_sethook() and dahdi_q_sig()? Those
function map state to RBS states.
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digi
ased on the locale information on the server.
--
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
On Fri, Sep 21, 2012 at 01:59:28PM -0300, equis software wrote:
> Shaun, here is the last test that I made.
>
>
> Time 0:
> IVR1 (with digiumA) have erros (Master changed to TE2/0/1)
> IVR2 (with digiumB) OK
>
> Time 1: (just swap spams)
> IVR1 (with digiumB) OK
>
the debug module parameter
[1]
[1] http://svnview.digium.com/svn/dahdi?view=revision&revision=9299
You can enable this flag without reloading like:
$ echo 1 > /sys/module/dahdi/parameters/debug
Cheers,
Shaun
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Driv
directly from the kernel.
Cheers,
Shaun
[1] http://linux.die.net/man/2/poll
[2] http://svnview.digium.com/svn/asterisk?view=revision&revision=122928
[3] http://linux.die.net/man/2/pipe
[4] http://linux.die.net/man/2/timerfd_create
[5] http://svnview.digium.com/svn/asterisk?view=revis
rrors)
And your problem follows the server not the card or the cable? Have
you tried other slots? Are you screwing the cards down?
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL
On Fri, Sep 14, 2012 at 11:27:14AM -0300, equis software wrote:
> Shaun, could it be related to
> http://lists.digium.com/pipermail/asterisk-users/2012-March/271304.html ??
> I'm using DAHDI Version: 2.4.1.2
No, those committs were to address an issue that only existed
between 2
7;t quite understand this comment. Is it possible to reword it?
Is the LTG the line interface card? Are both these test servers
using the same provider drop?
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.co
On Thu, Sep 13, 2012 at 09:35:55AM -0500, Shaun Ruffell wrote:
> On Thu, Sep 13, 2012 at 09:49:37AM +0200, Olivier wrote:
> > 2012/9/13 Shaun Ruffell
> >
> > > On Wed, Sep 12, 2012 at 11:52:40PM -0400, Mark Robinson wrote:
> > > > I know that asterisk on vir
On Thu, Sep 13, 2012 at 09:49:37AM +0200, Olivier wrote:
> 2012/9/13 Shaun Ruffell
>
> > On Wed, Sep 12, 2012 at 11:52:40PM -0400, Mark Robinson wrote:
> > > I know that asterisk on virtual machine require a timing source.
> > > What would you suggest to use for ti
livered to the kernel modules in
20ms chunks. This can have a big impact on reducing the load on the
CPU.
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.
alarm.
Each time it goes into alarm the core of DAHDI will look for a new
span to use as a timing source for asterisk. If TE2/0/1 is the
"preferred" timing source, when it comes out of alarm, DAHDI will
switch the timing back to it.
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445
ogd@ at Tue Sep 4 11:46:57 2012 ...
Assuming you're using a telephony card, I would contact your card
vendor for support.
Normally when I see messages just appear on an otherwise working
system it is due to the card being slightly unseated from the slot.
Cheers,
Shaun
--
Shaun Ruffel
d b)
Rework how conferencing / bridging is done in the drivers so that
only channels in conference with one another are checked for audio
mixing. I believe the limiting factor would be CPU cycles and not
memory.
As an aside, the most I've run in a single server are 24 T1s. But I
was not o
ephony Interface Registered on major 196
> dahdi: Version: 2.5.0.2
[snip]
> Can you fix that?
>
> Thanks in advanced.
I think your best bet will be to contact OpenVox. My guess is that
there is an an incompatibility between the firmware on the D210E and
2.6.1 that they are in the bes
e commands as root and send the output:
# dmesg -c > /dev/null
# /etc/init.d/dahdi stop
# modprobe wte11xp
# dmesg
> I try to confirm my thought by using
> root@ubuntu:~# dahdi_tool
>
> There is no interface listed on the table.
>
> I am wondering if anyone got idea ab
actly what you're trying to do.
Cheers,
Shaun
--
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
--
_
-- Bandwid
you intende the KVM
guest to handle all the card communication.
You could get an analog gateway, or setup another small system to
host any cards you get to act as a gateway, and keep most of your
logic on the KVM.
Cheers,
Shaun
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
44
"
communicate with the back-end process that is doing the work.
Cheers,
Shaun
--
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
--
__
;ve seen "clipped"
DTMF in the past it was due to imperfect muting at the PSTN -> SIP
interface.
You should be able to take a packet trace on the interface of the
Asterisk server communicating with the Metaswitch to determine
whether the problem first appears at the switch or in your Aster
not any indications in dmesg of
latency bumps, which would be case if something else was preventing
the wcte12xp interrupt service routine from running. The patlooptest
errors would explain the bad audio you recorded with dahdi_monitor
and the DTMF
detection problems.
Cheers,
Shaun
--
Shaun Ruffell
Dig
s now for the error counters to
flag that the driver does not actually collect them versus returning
0 which was leading users to believe no errors existed. This change
was made in r10212 "wcte12xp: Set uncollected performance counters
to -1" [1].
[1] http://svnview.digium.com/svn/dahdi?view
you're running on a system with limited memory and the asterisk
process is dropping audio while paging in code. (See DAHLIN-241 [1])
[1] https://issues.asterisk.org/jira/browse/DAHLIN-241
Cheers,
Shaun
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Hu
ail/asterisk-dev/2008-December/035673.html
--
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 Col
1 - 100 of 672 matches
Mail list logo
