similar to: Junghanns douBRI miniPCI (b559) DAHDI drivers

Kapejod is working on a fix for the CDR problem in bristuff. See below ----- Forwarded message from kpj@junghanns.net ----- Resent-From: tzafrir.cohen@xorcom.com Resent-Date: Fri, 10 Feb 2006 13:01:25 +0200 Resent-Message-ID: <20060210110125.GU16880@xorcom.com> Resent-To: tzafrir@cohens.org.il Envelope-to: tzafrir.cohen@xorcom.com Delivery-date: Fri, 10 Feb 2006 05:19:50 -0500 Date: Fri,

Hi, I'm very new to asterisk and managed to set one up in debian, I installed via apt-get the asterisk and asterisk-bristuff packages. I downloaded the bristuff source as well. I managed to get as far as loading the following modules: zaptel 199144 4 cwain,zaphfc,zttranscode,ztdummy But the problem now is that all channels that I try to configure gives me an error that

Hi to all, we are searching for a hardware based DSP solution for use with Asterisk based on PCI or MiniPCI to reduce main processor load and to use embedded boards with Digium E1/T1 cards like TE410P. does anyone know about any manufactorer of those cards or someone who is able to develop/build such cards? Specifications: PCI or MiniPCI up to 120 concurrent transcodings Codecs: G.729/G.729A or

Same question for asterisk-users as well: ----- Forwarded message from Tzafrir Cohen <tzafrir.cohen at xorcom.com> ----- Date: Wed, 7 Mar 2012 21:14:04 +0200 From: Tzafrir Cohen <tzafrir.cohen at xorcom.com> To: asterisk-dev at lists.digium.com Short version: it's now time to remove. Anybody actually uses latest DAHDI with RHEL4? See inline, On Thu, Dec 29, 2011 at 07:42:39PM

After a reboot, I can't reproduce the problem anymore which is quite frustating. 2011/6/14 Tzafrir Cohen <tzafrir.cohen at xorcom.com> > On Tue, Jun 14, 2011 at 03:44:32PM +0200, Olivier wrote: > > Hi, > > > > I'm using a two-years old installation script for the first time on a > > Squeeze (linux 2.6.32) platform. > > For an unknown reason (might

Hi, In my 1.6.1.18 with dahdi 2.2.1.1, I've got : # dahdi_hardware pci:0000:01:0a.0 qozap- 1397:16b8 Junghanns OctoBRI ISDN card Does it mean I should download and use qozap or is it a bug in Dahdi ? Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100412/de87e46e/attachment.htm

Hi, I'm using a revision 6822-enabled Dahdi-Tools (see https://issues.asterisk.org/view.php?id=13897) with a Junghanns QuadBRI. 1. Do I still need qozap driver ? If positive, how is it recommended to get it ? 2. Which line should be included in /etc/dahdi/modules to have the appropriate driver loaded ? 3. The process I'm planning to use is : A- Hand edit /etc/dadhi/modules,

2017-03-14 13:08 GMT+01:00 Tzafrir Cohen <tzafrir.cohen at xorcom.com>: > On Tue, Mar 14, 2017 at 11:10:57AM +0100, Olivier wrote: > > Hello, > > > > After all these years installing from source, I'm giving Dahdi package > > installation a try on a recent Stretch box. > > > > Google over the web, I didn't find too many doc on this topic. >

such file or directory" on pure-IP platform in which I installed asterisk-libpri-dahdi trilogy. Maybe, it's me while following README instructions, maybe README instructions could be improved or maybe it's wrongly labeled messages ? That's why I told myself : I'm waiting too much from doc ? is a pure-IP platform too specific ? what is the official policy ? README starts with

Hi folks Xorcom Rapid 1.0 is avilable for download Q: 1.0? A: Sure, better than 0.9.1: * Asterisk 1.0.5 * Base packages upgraded * Built with SpanDSP support * Improved Zaptel detection * ast-cmd with some useful command-line abilities provided * ssh installed by default * putty.exe is included on the CD * music-on-hold files removed due to potential licensing issues

On Tue, Mar 21, 2017 at 09:36:21AM +0100, Olivier wrote: > Thanks to Tzafrir help, Now I have an Asterisk-Dahdi system installed from > Stretch repository. > This system has a Digium HX8 card with BRI modules, Asterisk 13.14.0, Dahdi > 2.11.1. > BRI spans appears as up and active but I've not tested them yet: > CLI> pri show spans > PRI span 1/0: Up, Active > PRI

static void senddialevent(struct ast_channel *src, struct ast_channel *dst) { manager_event(EVENT_FLAG_CALL, "Dial", "Source: %s\r\n" "Destination: %s\r\n" "CallerID: %s\r\n" "CallerIDName: %s\r\n" "SrcUniqueID: %s\r\n" "DestUniqueID: %s\r\n" "CDRUserfield: %s\r\n", src->name,

About the IVR, are u using Asterisk? Regards Bilal > ------------------------------ > > Message: 17 > Date: Wed, 18 Feb 2009 12:23:41 +0200 > From: Tzafrir Cohen <tzafrir.cohen at xorcom.com> > Subject: Re: [asterisk-users] Credit Card processing > machines > To: asterisk-users at lists.digium.com > Message-ID: <20090218102341.GD21440 at xorcom.com> >

Dear List; Thanks alot for the help. But how can I let the second dial tone (after pressing the extension to select that FXO port) to be difference than normal dial tone? Regards Bilal Ghayad -------------------------- Correction, on FXO port not FXS, second, read his email first: "Also, how it will be possible to assign an dedicated line (connected to FXO) to an button on the Polycom IP

---------- Forwarded message ---------- From: Tzafrir Cohen <tzafrir.cohen at xorcom.com> Date: Oct 4, 2007 12:56 PM Subject: Re: [asterisk-dev] chan_h323 and chan_oh323 compatibilities To: asterisk-dev at lists.digium.com Hi On Thu, Oct 04, 2007 at 11:46:30AM -0300, Caciano Machado wrote: > I'm receiving a lot of warning messages from my Asterisk > 1.2.5/chan_oh323 every time

I really need help. We have a Junghanns DuoBRI and we plugged it into an Asterisk 1.4 box. We keep on getting the error "layer 1 deactivated (F3)"! We then contacted Junghanns, who told us that there is no driver for the card for 1.4 and that we should try 1.2. We tried 1.2 with their driver but ALAS we get even more error messages! I don't understand how Junghanns puts an

Okay, i'll move my discuss to asterisk-users. Thank you. On 1/17/07, Tzafrir Cohen <tzafrir.cohen@xorcom.com> wrote: > > > On Wed, Jan 17, 2007 at 04:39:03PM +0800, ??? wrote: > > Jonson Player wrote: > > > Hello, I intend to buy a FXO/FXS device from Linksys. > > > I'm thinking about SPA3102. What you guys thik about it. > > > Is ok, is

What is dahdi.auto_assign_spans and why should you care? In later versions the kernel module dahdi[Q] includes a new parameter: auto_assign_spans. It defaults to 1, and if you set it to 0, DAHDI can start behaving in strange and completely expected ways. Chances are the default will be set to 1 in a future version. Here is why you'll want to set it yourself. Up until DAHDI 2.5, hardware

Hi, I have a Junghanns QuadBri installed and seems to be detected and working correctly using the wcb4xxp driver All ports are configured as TE The problem is when I connect an ISDN line - the LED turns green and Dahdi status shows Alarm OK But when I try to make a call I get "All circuits are busy" cause 27 I have searched and web and tried numerous configs but it doesn't want to

Hi I put a snapshot of our current packages updates.xorcom.com . They are available from the deb source deb http://updates.xorcom.com/test sarge main (this is s/rapid/test/ of the name of the source of the stable version) Changes include: * Fixed and simplified zaptel detection * Support for spandsp: compiled but not yet tested * IAX extensions * Mail server configuration * The script