similar to: vzaphfc?

Again trouble compiling bristuff-0.3.0-PRE-1q with the florz patch on a x86_64 box (I guess nobody is using x86_64 platform or is able to fix this themselves?) First of all when bristuff is downloaded and compile is started it appears that the bristuff Makefiles are badly broken. The asterisk Makefiles all do see to find the kernel sources on a RHEL4 box in the proper directory, the pure

I installed bristuff0.20-RC3 (which includes * 1.0.3 stable) It works fine until I disconnect the phone jack for the ISDN line. Even after plug it back in asterisk still reports that it could not create a zap channel when I try to dial out and the line gives an engaged tone when I try to dial. Re-starting asterisk doesn't solve this, I have to stop asterisk, unload the modules, reload

Hi list! I have to do a new bare metal installation of a box running Asterisk with bristuff or vzaphfc. The box will be used as a really lightly loaded file server and pbx. Any advise on which architecture I should use? The cpu is a 64 bit capable AMD (the box is running x86_64 now) but is still suffering from echo on the BRI lines. Should I go with the normal x86 or the 64 bit x86_64

Hi list! I'm currently using a HFC-S card for my ISDN BRI line with bristuff. The instability is driving me crazy however. I'm having continuous problems where inbound calls will not work after some time of operation (the number then appears as not in use to the caller) or also outbound calls do not work. The solution is to unload the modules, stop asterisk, re-load the modules and

Hi list, Has anyone been able to get ISDN-BRI support to work reliably on Asterisk 1.4? If so, I'd love to know how you did it (hardware, distro, kernel, modules, versions, config files). I've tried to get it to work on a Debian etch system with an HFC-PCI card and the zaptel package (v1.4.7, also from xorcom.com), but with no luck: all three channels that are created when the

Hello, I've added a ZAPHFC card to my CAPI based system. Calls coming in via ZAPHFC do not forward the caller id to the SIP phones. Calls coming in via CAPI do forward the caller id to the SIP phones. Any and all help is greatly appreciated. The (hopefully relevant) conf file excerpts are: extensions.conf =============== exten => 807440,1,Answer exten => 807440,2,Noop exten =>

Hi, Has anyone information about BRI hardware supported by 1.6 libpri ? In another thread, I was told a basic BRI card with HFC chipset (Bewan Gazel 128) was supported but I would delighted to lear about other harwarde (and specifically about Digium B410P). Regards -------------- next part -------------- An HTML attachment was scrubbed... URL:

I have an analog GSM Gateway that is connected to a normal SIP ATA device. Basically what it does is this : when you call the extension nr. of the SIP ATA port, the GSM Gateway will pick up the phone and presents a (new) dial tone, and then dials whichever DTMF tones it received. The SIP ATA ia a Grandstream HT286. I would like to use the GSM Gateway to route my outbound cellular calls, how

Hi list, Attempting to get an ISDN-BRI line connected using an HFC-S PCI card together with Asterisk v1.4.14 and Zaptel 1.4.7 on a Debian etch system, I find that I can't access the card's resources because the channels are always be busy. An attempt to call out results in the following CLI output: == Primary D-Channel on span 1 down == Primary D-Channel on span 2 down

Hi list! I read the trixbox anouncement that they downgraded to kernel version 34 to get rid of some audio problems I'm not running trixbox but normal Centos 4 with asterisk installed. I tried to find some further info on this but couldn't find any. Do audio problems occur with normal Centos and the latest kernel version too? (In other words, should every centos user downgrade??)

Hello all. Since half december we are trying to implement * as our primary PBX. We had a test machine running with 2 sip phones and a single ISDN card. Since this was working ok, we installed * on our main Debian server. Some specs: P4 2.8 Ghz HyperThreading 512 MB RAM Debian Sid updated every week. Linux 2.6.9 vanilla kernel (not the debian package) 1 Intel Pro 100 nic for internal network 2

Hi, Reading from www.voip-info.org, i can see that "Junghann's chan_capi is now part of bristuff <http://www.voip-info.org/wiki/view/Bristuff> , as of version 0.3.0-pre". What does that really mean ? Shall I understand I can share a Junghanns QuadBRI board between 2 CAPI-enabled software (like a 0.3.0-pre bristuffed Asterisk for instance) ? If positive, what are the pros and

I am trying to reconfigure an asterisk box that was using an HFC-S card with bristuff but is now using 2 analog lines therefore I want to use the TDM02B to connect to two POTS lines. The TDM02B has 2 red modules. I have this in /etc/zaptel.conf loadzone=nl defaultzone=nl fxsks=1-2 I have /etc/asterisk/zapata.conf signalling=fxs_ks echocancel=yes echocancelwhenbridged=yes echotraining=400

Hi, I read a lot about US providers that can terminate a PSTN number for you and offer IAX or SIP connectivity. Does anyone know such a company in The Netherlands ? I read about Unet. Anyone with experience with them ? Any information is welcome. -- Michiel van Baak http://lunteren.vanbaak.info michiel@vanbaak.info GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7E0B9A2D

After upgrading from 1.2.25 to 1.2.26 i noticed that IAX -> IAX calls always result in Asterisk just exiting without any message. Asterisk also seems to die when using a TDM400 with 2 FXO modules, placing 2 outgoing calls on both lines as Zap/g2 and then trying to make a 3rd call. Went back to 1.2.25 for the moment

I applied the florz patch but my problems remain. Now I get all sorts of weird errors on the console and I cannot make outgoing calls. Incoming calls work as expected. I am using a single HFC-S card with BRI. Any clue what these errors below are? Ri = 44651 TEI msg = 3 TEI = 7f Ri = 3800 TEI msg = 3 TEI = 7f Ri = 42399 TEI msg = 3 TEI = 7f Ri = 42409 TEI msg = 3 TEI = 7f Ri = 22078 TEI msg = 3

After upgrading a CentOS 3.x box to CentOS 4.1 (both x86_64 with an Athlon64) I also wanted to get the latest bristuff. Unfortunately bristuff without florz causes the box to kernel panic within hours (console will complain about bad frame received something). It seems however that the florz patch will not work for x86_64 arch. Bristuff -0.2.0-RC8j compiles fine without the florz patch, but

Hi, Greetings to All, Im looking for some help on configuring VPN on the Asterisk PBX that I have hosted in US. Im currently in Middle East and as everyone knows some countries here has taboo to VOIP. Im not able to get phy phones registered to my PBX as they are blocking SIP and IAX2. Hence im looking for a VPN solution. For this first i need to setup VPN on my server .. Am i right? Well if

Ive installed asterisk and freepbx. Through the interface ive configured 2 extensions, 6000 and 6001. My problem is that when i try to call from extension 6000 to 6001, i hear this msg "Im-sorry&an-error-has-occured" and the call is terminated. As expected if i call to another number i get an error. i thought the problem might been related with the NAT but if checked and changed some

Using the latest(?) bristuff (Asterisk 1.0.4-BRIstuffed-0.2.0-RC3a) I have problems with loosing the D-channel. Most of the time, after the message "PRI D-channel down" it only takes a second or so to come back up, noted by the message "PRI D-channel up" However, today most of the time the D-channel stays down. Calls come in, but can't be answered. Does anyone know