similar to: Bristuff and incoming call problems

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

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'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! I'm still trying to figure out about the groups in asterisk. If I understand correctly, if you assign a certain group number and you assign the same call group number to a sip device the device will reing even though you did not specifically specify it in extension.conf? How will this work for ISDN BRI/PRI? I don't want some extensions to get all calls from the BRI/PRI, just

Caller id is not in the configs that are supplied with zaphfc from bristuff, and it's not mentioned in the wiki. Is it possible to use callerid with zaphfc/bristuff? Thanks!!

I tried to get callerid working the normal way but the cid is never passed to the phone. It doesn't work untill I set SetCIDNum(0${PRI_NETWORK_CID}) in extensions.conf which I found in the wiki: http://www.voip-info.org/tiki-print.php?page=Asterisk+zaphfc Is this intended behaviour, or still a bug? It does work but it only shows one zero even though I have nationalprefix = 0

Hi list! On a newly installed RHEL 4 box I'm trying to install bristuff-0.2.0-RC8n. Everything did compile but I am running into some problems with the zaphfc driver. First of all when I load zaphfc *before* zaptel (yes I know I shouldn't do that) I get a kernel panic and the box hangs. Not so nice, especially when you are trying to fix stuff from remote locations. But ok. Now for

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

Hi list! I'm trying to install bristuff on a newly installed box. The box is running a rebuild of RedHat Enterprise linux with the latest kernel. The architecture of the box is x86_64 (Athlon 64), the os is 64 bit with 32 bit compat libs installed. Also the kernel source is installed as well as the (kernel) development tools. The bristuff install.sh script downloads asterisk+zaptel 1.0.2

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 list! I am installing an * box that will be installed on a site with KPN BRI ISDN in The Netherlands. I am using bristuff fron Junghanns. Does anybody know the correct settings for this? I will not have internet access there which makes it harder to google around on location. switchtype = euroisdn is pretty obvious but what about these settings: signalling = bri_cpe_ptmp ; p2p TE mode

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

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 have newly installed a RedHat 4.0 EL rebuild. The install was done without the ISDN card present. After disabling kudzu and haldaemon I inserted the card. Stil that *(&$^&%$(&$^!!!!!! kudzu shit modified my config and is loading hisax, crc_ccit and isn modules. Even worse, they do not appear in /etc/modprobe.conf which means that that f*cking kudzu added the modules to initrd.

Hi! I'm trying to setup a Wildcard TE110P with a PRI in The Netherlands. I get a Red Alarm on the line. Is there any way of debugging this? I've tried some configs that should work but without success. Is there any way of telling if the cabling is correct or what else the problem could be? Thanks!! Remco

I hva ean HFC-S card in a box that I'm trying to get to work with bristuffed Asterisk 1.0.3. The box is an Athlon64 running a RHEL rebuild with a plain vanilla 2.6.10 kernel. I tried both APIC and NOAPIC mode. The installation went ok and does give output that seems correct SPAN 1: CCS/ AMI Buil-out: 399-533 feet (DSX-1) 2 channels and one D-channel Even though I've configured * to

Hi list! While looking for the Snom 190 I found another phone, the Elmeg IP 290 (www.elmeg.de). Looking at the pictures & the specs they seem to be very similar beasts but the firmware is supposedly not interchangeable. Does anyone know the difference between the 2, do they work with Asterisk? The weird thing is that Elmeg has similar phones with the Snom look but they are ISDN only (no

I'm using bristuffed Asterisk with ISDN/ZAPHFC I have VERY ugly (outgoing) sound through ISDN/HFC if echocancel=yes in zapata.conf, but without echocancel I have bad (incoming) echo Through PSTN/FXO sound is ok with or without echocancel. I tried other echo cancellers (in zconfig.h) two times: ECHO_CAN_KB1 (this was default) ECHO_CAN_MARK2 ECHO_CAN_MG2 after any change I compiled (make

Most people seem quite positive about Snom phones, I cannot share this opinion. The displays are dying quite often, and firmware is buggy. I have tried every firmware from 4.5 up to 5.x and 6.04 but keep having problems with phones locking up or rebooting during an ongoing conversation. REALLY annoying for a phone that is advertised / targeted as a business class phone

Hi list! I'm totally fed up with bristuff (or it's instability with a simple HFC-S card), 2 out of 3 times when people try to call they get the information tone that the number is not connected. I would like to try vzaphfc and I am looking for information on it. >From previous posts I found that the only place where the sources seem to be maintained and available is at the debian