similar to: BRIstuff/QuadBRI problem: Ring requested on unconfigured channel 255/255 span 5

Hi all, I just posted this question before last week. Meanwhile after upgrading Asterisk 1.0.7-BRIstuffed-0.2.0-RCg to 1.0.8-BRIstuffed-0.2.0-RCh the same problem occurs, but seems to be more seldom. Attached is now the output of "zap show channel" . - I'm running a stable Asterisk on a HP DL380G2 1.4Ghz 0,5GB RAM equipped with 1x TE410P and 2xJunghanns OctoBRI running in NT-mode.

I have a serious problem that repeats very often, after 30 - 50 calls and I can only solve it by stopped and restarting * :-( After a while, * seems to loose track of something. When an ISDN call from PBX needs to go to the Telco, I get 'Ring requested on unconfigured channel 255/255 span 2' It's always channel 255/255 ??, the 'span' number is random Setup: * between Local

Here's one last plea for help from the list before I give up on the totally cool software FAX modem concept in complete despair (for now, at least, until I have more time to dig into it).... I am simply not able to successfully receive a FAX no matter what device I transmit from or how I bring the call into Asterisk. My lastest effort was a call from a Pitney-Bowes FAX machine into an X100P

After working fine for a week or so my new Quad E1 asterisk 1.8 system has started rejecting outbound calls from the Nortel BMC 450 it is connected to. The cli fills up with these: sig_pri.c: Ring requested on unconfigured channel 255/255 span 3 Is this likely to be a 1) config error 2) cable issue (I made them) 3) hardware problem with the Digium card 4) software (lib pri) Any clues?

Hi all, I replaced a TE410P Rev C 1st Generation Firmware with a TE411P without any cfg changes (zaptel/zapata). As a result Asterisk crashes on outbound from PRI4 going to PRI1 calls: Aug 23 18:22:00 WARNING[4693]: chan_zap.c:7545 zt_pri_error: PRI: !! Got a UA, but i'm in state 1 Aug 23 18:22:00 WARNING[4693]: chan_zap.c:7545 zt_pri_error: PRI: !! Got a UA, but i'm in state 1

CentOS-6.2 We have a dedicated CentOS-5.7 host used for fax reception and transmission that we wish to move to a CentOS-6.2 virtual guest instance. The CentOS-6.2 virtual host has a 4-port serial card installed. lspci -v tshows this this: 03:00.0 Serial controller: Oxford Semiconductor Ltd OX16PCI954 (Quad 16950 UART) function 0 (Uart) (prog-if 06 [16950]) Subsystem: Oxford

Folks, (sorry for overlong lines) I have recently configured one port on my QuadBRI card to work in NT mode with NET signalling configured so that I can use an ISDN telephone on it. I have set up a separate group in zapata.conf and can call the phone and place calls from it like a charm. No problems at all. Problems came up when trying to hold a call and get it back. I turned on "pri debug

System have been working great for weeks, using an average 40 of 120 dahdi channels. But today, I suddenly see scary things like this: -- Moving call from channel 5 to channel 7 [Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:10608 pri_fixup_principle: Can't fix up channel from 5 to 7 because 7 is already in use [Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:11535 pri_dchannel: Ringing

Hi guys, I've been trying to get my ISDN-10 line up for the past few days, but its been going up and down. I am using OpenVox D110P card on asterisk version 1.4.21. It seems to me like a cable problem. I tried using Ethernet straight cable (12, 45, 36, 78) and also a "straight" cable where the twisted pairs are on 12, 34, 56 and 78. The problem remains the same.

I am getting: NOTICE[180235]: chan_zap.c:7358 pri_dchannel: PRI got event: 6 on Primary D-channel of span 1 on my asterisk box and it seems to be causing a poping sound in the phones, I am wondering if anyone can shed some light on this. I have scanned the archives and get possibilities ranging form motherboards, to pri, to loaded module problems. Can someone tell me the best way to start

I receive this error on the asterisk console and it is pretty much ALWAYS coming up. Sometimes there will be a break where it does not display. We had our PRI provider test the lines and they claim that there is no signalling problem. It doesn't matter if there are no calls or if there are 10 calls in progress the error is still displayed. I also get an annoying popping or clicking sound

Hi there, I am attempting to set up a simple BRI and SIP based platform using * with the quadbri card (it's not sharing an IRQ). I enclose my zaptel and zapata.conf files. For the inital test I'm simply trying to connect to the * demo menu. The drivers compile (with a few warning that I believe aren't important - see attachments). chan_zap comiles with the warning: chan_zap.c:

Hi all, So, we reverted the LibPRI version and tested it, and then tried with the latest version of everything. Still no changes. The BRI line is in PTMP. If we set the configs to PTMP in the genconf_parameters and try it, we get the following: [Jan 21 17:32:20] ERROR[20341]: chan_dahdi.c:12645 dahdi_pri_error: Unable to receive TEI from network! If we set it to PTP (which it is not) we

Hello everybody I am trying to connect my asterisk to a payment equipment trough PSTN. I have a TDM400P card with an fxs module an the equipment use modem to send data! I was thinking to implement a software data modem in asterisk, but I found out that there is just faxmodem for asterisk, Is anyone here know something about software data modem working with asterisk to help out? Thanks,

Hi, We've exhausted our internal capabilities as well as Sangoma tech support and were hoping someone with some expertise could help us with a pointer. Briefly, our issue is as follows. Periodically (several times an hour), we get either of the following error messages in our asterisk messages log. These correspond with dropped outbound calls on a one-to-one basis when the second error

I have a TDM400 card with 3x FXO and 1x FXS ports on it. At the moment I'd prefer (till I can get it working more reliable with iaxmodem), for a faxmodem to answer one of the lines instead of the linecard. I've tried changing the context of that line so that the exten => s does nothing, but that stops the line from being able to receive calls (get a recorded This number is not

I have a pretty large setup on one of my customers. Digium TE420B (with echo cancelling module), 3 Xorcom Astribanks with 32 FXS each and 1 Xorcom Astribank with 16 FXO. These FXO ports are NOT used for fax/data transmission, as they are connected to cell phones. Not really related to the issue, but there are also 250 SIP phones. The problem is that fax and dial-up connections are really

I also experienced this problem and the first thing that really helped out was changing the timing in the span line of the zaptel.conf. Change it to look like this (see below) and see if it helps out. I got the error much less after doing this and eventually got rid of the error completely by removing my raid drives, installing an IDE drive, enabling DMA mode on the Hard Drive, enabling APCI in

Given all the issues with the fax DSP code and reliability, I'm looking into the option of using an external fax modem instead of trying to shoehorn asterisk into handling faxes properly... I'm thinking of hooking up the faxmodem to the line directly, then hooking the X100P to the modem's Phone port. Can I enable fax detection and use the fax extension to spawn an external command

Usually I used real Digium cards in asterisk systems, so I'm running into this for the first time. dahdi_tool reports that dahdi_dummy is in state UNCONFIGURED. This isn't super surprising, as it seems like the configuration files for DAHDI are really intended only for configuring real physical cards. But that begs the question: Is there any legal DAHDI configuration for dahdi_dummy such