similar to: BRI Error with zaphfc

Any ideas? Sangoma support is closed for the evening. I have the latest Sangoma drivers and Asterisk 1.4 everything installed. When I fire up asterisk, I keep getting "Primary D-Channel on span 1 up" repeated over and over. The B channels never come up. There are no errors in any of the logs, zttool, or the wanpipe tools. Intense pri debug output: < Unnumbered frame: < SAPI:

Hi, I'm pulling my hair out, cause cannot connect to EuroISDN BRI in Italy with octobri card from Beronet. I use bristuff and have following zaptel.conf... # # This file is parsed by the Zaptel Configurator, ztcfg # # # First come the span definitions, in the format # span=<span num>,<timing>,<line build out (LBO)>,<framing>,<coding>[,yellow] # # The timing

Hello- I have a system with one D410P and one B200P (both OpenVox). All is well with the D410P, inbound and outbound, and I can initiate calls on the B200P BRI span, but there may be something wrong with my inbound BRI setup: there is no indication of an inbound call when I dial in to it from the PSTN. When I run "pri intense debug" and make a call to the BRI span, I can see a

Hi all, Last night I went to replace an Asterisk 1.4 + mISDN + b410p box with Asterisk 1.6.2 and DAHDI BRI - to no avail. I had two servers so copied network setting etc from the working one, moved the card across, ran dahdi_genconf etc and it didn't work. Here's the console output with notices disabled: lucas*CLI> pri intense debug span 1 Enabled debugging on span 1 [Dec 16

Hi Guys, Running the following with a Sangoma A101D PRI card: *Asterisk 1.4.21.2* *LibPRI version: 1.4.10* No inbound or outbound calls can be made. In fact Asterisk CLI doesn't show any activity. Problem goes away on restart of the system or maybe asterisk. I see post about upgrading Libpri to 1.4.10.2 and then I see posts that even that didn't work. Anyone can weigh in this please?

Hi guys, We are experiencing a problem with a T1 PRI connection. After trying a number of variations in the configuration files, the behavior is always the same: no B channels come up and the D channel doesn't appear to be working well. We can see there are AT&T Maintenance messages being exchanged by asterisk and the provider, CONNECT and CONNECT ACKNOWLEDGE, but that doesn't

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello List, since some days i run into the problem that one span on a TE407P is not comming up correctly. With intense debug on that span i get: < [ 02 01 7f ] < Unnumbered frame: < SAPI: 00 C/R: 1 EA: 0 < TEI: 000 EA: 1 < M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ] < 0 bytes of data

Hi. I'm running some asterisk boxes on different sites, some equipped with a couple of ZapHFC cards, others with Junghanns quadBRI cards. All boxes were compiled with Asterisk 1.2.10 (libpri 1.2.3 zaptel 1.2.6) and bristuff 0.3.0 pre 1s, distribution is Fedora Core 4 with kernel 2.6.17.3 The cards are connected to Telecom Italia's NT1/NT1+ S/T lines; some of them are point-to-point,

Hi, I'm trying to install an E1 PRI, and I need it working by Monday, but although everything seems ok, I get no response to calls. When I make a pri extense debug on span 1, I repeatedly get the following: Sending Set Asynchronous Balanced Mode Extended [ 00 01 7f ] Unnumbered frame: SAPI: 00 C/R: 0 EA: 0 TEI: 999 EA: 1 M3: 3

I have installed two HFC PCI A-cards running zaphfc from bristuff-0.0.2, which seems to work quite fine, but I continously receive the messages "D-Channel on span 1 up" followed by "D-Channel on span 1 down" with a few seconds interval. Why is that? Bri intense debug log and configuration files below. I don't need ztdummy or zaprtc, do I? I get some frame slips as well,

I've got a couple of PRIs coming in from a SUMA 4 switch with some 800 numbers routed through it. When the calls come in, I get the following message on the console and the call never makes it through: (800 number is fake) Extension '8005551212' in context 'nonauthenticated' from '232102749585' does not exist. Rejecting the call on span 4, channel 1. I do have the

Hello list, i've got some problems getting a E1 line with a E100P up and running (germany). # cat /proc/zaptel/1 Span 1: WCT1/0 "Digium Wildcard E100P E1/PRA Card 0" HDB3/CCS/CRC4 YELLOW RED "YELLOW RED" sounds not so good. When launching asterisk, enabling pri debug on that span, i see outgoing attempts: ;---------- snip -------- > [00 01 7f ] > Unnumbered

Hi, I hope someone can help me with this.... Asterisk 1.0.6 Zaptel 1.0.6 Libpri 1.0.6, 1 Digium E100P card installed Panasonic TDA200 firmware v2.0.6 E1 Card Firmware 1.0.2 System is located in Australia, so as technologies go, I believe it is twist on the euro standard for the E1 signalling. Here is the situation. The TDA E1 card is set in cross over mode and I am using a functional

Hello all, if I try to call from one phone on the internal S0 to another on the same S0 using zaphfc, the bus is hung up. The called phone is ringing, but I can't talk from one phone to the other. The error I get is: -- Executing Dial("Zap/2-1", "ZAP/1/55|15|tr") in new stack -- Requested transfer capability: 0x00 - SPEECH -- Called 1/55 -- Channel 0/1,

I managed to get Asterisk working with my PBX using T1, now I am moving on to trying to make PRI work. I have my zaptel.conf and zapata.conf configured as follows: Zaptel.conf: span=1,1,0,esf,b8zs bchan=1-23 dchan=24 loadzone=us defaultzone=us Zapata.conf: [channels] transfer=yes immediate=yes callprogress=yes language=en context=default switchtype=national signalling=pri_net group=1

So we've got a TE410P configured as E-1. The PRI is showing up as normal, I have green lights, but d channel doesnt seem to come up and i keep getting this error if i do a "pri intense debug" The carrier swears up and down that there are no issues on their end. Any thoughts? localhost*CLI> > Unnumbered frame: > SAPI: 00 C/R: 0 EA: 0 > TEI: 000 EA: 1 > M3:

My comment, (forwarded from Bristuff list) - A few people are seeing a Cause 34 (congestion) from ISDN installs, where there clearly is an available channel. This was originally related to Bristuff as it happens to ISDN2 users, but there is at least one report of an unpatched 1.6.x user seeing the same issue. 2009/4/23 Steve Davies <davies147 at gmail.com>: > I think I have a site where

Hi, I'm having problems with a new ISDN PRI in a new server. The cable is connected and the E1 modem seems to have issues with syncing (blinking light on the modem). versions: CentOS 6, asterisk 1.6.2.20, dahdi 2.5.0.1, libpri 1.4.12 ------------------------------------------------------------------------------------ dahdi show status T4XXP (PCI) Card 0 Span 1 RED 0

Hello, I got a Problem with my HFC Card, I start my "asterisk -vvvvvvvvvvvvc" The console comes up: ---------------snip---------- Asterisk Ready. *CLI> ---------------snip---------- Setting up debuglevel for span 1 ---------------snip---------- *CLI> pri intense debug span 1 Enabled EXTENSIVE debugging on span 1 ---------------snip---------- Console output:

Hi I've been running into a weird issue, which its hard to get any information on. We successfully setup a R710 system with Asterisk 1.4.22 / libpri 1.4.7, utilizing a Digium TE121B Pci express card. However we are having some stability issues and can't seem to trace it down to if it is a card/system issue or our PRI vendor having a dirty line. I know some will say it is a old version of