similar to: Handling message for SAPI/TEI=0/0 Repeated Quickly

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 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

I have a working system with asterisk 1.4.26.2 libpri 1.4.1 and zaptel 1.4.12.1 With a digium TE205p. I am trying to update to libpri 1.4.10.2. When I do, incoming calls work but outgoing does not. When I do this I "rm /usr/lib/libpri*" then just install libpri-1.4.10.2 as normal. I then do a make clean in asterisk and make distclean ,then configure, make and make install. I do

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

I have a user who's system crashes on pri hangup request. Tried 1.4.19.1 and 1.4.20 as well as the latest libpri no change Progress is as follows...... < Supervisory frame: < SAPI: 00 C/R: 0 EA: 0 < TEI: 000 EA: 1 < Zero: 0 S: 0 01: 1 [ RR (receive ready) ] < N(R): 025 P/F: 1 < 0 bytes of data -- ACKing all packets from 24 to (but not including) 25 -- Since

I have a problem calling a certain number from our PRI line. Calling the number from a separate PSTN phone works fine. The remote number seems to have some funny call redivert setup, when you call it, it answers immediately, makes some kind of beep and then starts to ring. Our PRI is in the UK from Telewest/NTL/Virgin Media and most outgoing calls work without a problem. The server is

I'm not a PRI expert and therefore don't know what this debug stuff means for PRI, so if anyone can help me here... I'm running the latest libpri and zaptel from CVS. Keep in mind that everything works fine when using the STABLE libpri and zaptel. I am NOT running CVS asterisk. I am running 1.0.6. asterisk*CLI> pri intense debug span 1 Enabled EXTENSIVE debugging on span 1 T203

Hi I have a small ISDN PABX , (BRI) at home - Siemens Gigaset 4175 which has cordless DECT extensions. I have set up asterisk on FC3 with two HFC cards and I am using the latest bristuff. I am trying to use * between my ISDN line and my PABX. One card is in TE mode and can receive and make calls OK. I can make and receive external calls to a SIP phone. I cannot get the other card to talk to my

picture. I know the firmware on the Nortel is old, so I'm guessing that libpri is sending something that the Nortel does not know how to handle. Is there a way to dumb down what libpri sends? From everything I've read PRI is an evolving standard - and older devices may struggle with newer extensions/developments. (This might be very handy for users trying to talk to old pbx's.) Is

I have an application where I need to send outbound prerecorded messages. The Asterisk "call file" process works fine if I am sending the call via SIP or IAX, but not via ZAP over a PRI channel. The destination device (my cell phone) never rings. The only unusual thing I see is on the fifth line of the "full" log, below, "channel.c: Don't know what to do with

Hello, I'm experiencing some weird problems on my server: - 1) The following messages are filling up my logs: [Sep 29 08:24:59] WARNING[7077]: chan_dahdi.c:2789 pri_find_dchan: No D-channels available! Using Primary channel 140 as D-channel anyway! [Sep 29 08:24:59] WARNING[7078]: chan_dahdi.c:2789 pri_find_dchan: No D-channels available! Using Primary channel 171 as D-channel anyway!

Hi All, I've a BT Versatility PBX that I want to connect to my asterisk 11.9.0 box via BRI port in NT mode but actually I wasn't able to get it working. I've another standalone PBX, it's a Panasonic model, which works fine connected to the same port. The BT connected to a UK BT BRI line works quite fine after roughly a minute once connected. The PBX can be seen at

hello, I have a Junghanns QuadBRI card in my asterisk server. I'm able to dial & connect to local numbers through the ZAP interfaces however when I try to dial national numbers with the according area code the connection fails, an intense BRI debug is shown below. The error being Ext: 1 Cause: Unallocated (unassigned) number (1), class = Normal Event (0) about half way through the

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

Was'nt sure if this mail got through earlier: I have been having a weird issue with my telco's ISDN PRI occasionally resetting on a incoming call, i suspect it to possibly be a timing issue since some of the incoming call work. This problem happens very frequently. I am using asterisk-1.6.0.1 with libpri-1.4.9, the asterisk server is connected viw TDMoE to a Redfone Fonebridge into

I've having problems with a BT 2 span ISDN-30/Digium TE205P asterisk setup with outgoing calls not completing and requiring an Asterisk reset to 'unstick' span 1. Sorry this is a bit long but I'm completely out of my depth :-( This system has been in use for some while and I recently upgraded it to asterisk 1.4.24, zaptel 1.4.11 and libpri 1.4.9. I didn't change

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?

Can anyone work out why my callerid doesn't work on my isdn4Linux with asterisk (or without asterisk for that matter)... This used to work fine, and I am quite confident that the telco is sending callerid information (because they always do on all ISDN lines standard, only extra cost on POTS lines). This is the information from dmesg, whether asterisk is running or not: isdn_net: Incoming

handled. So....what do I do? Thanks, MD =1=================================================== !! Invalid Protocol Profile field 0x11 -- Accepting call from '2004000' to '111' on channel 0/23, span 1 -- Executing NoOp("Zap/23-1", "Incoming call from Meridian1") in new stack -- Executing NoOp("Zap/23-1", " From number: 2004000|

We are trying to send caller ID NAME information over a Telus PRI in Alberta. The PRI tech says that he sees the NAME information, and for calls over the same network, that NAME info should be reaching the receiving station, but it is not. The technician was stumped. I suspect there's something specific that I need to do to make it work, since many PBXs can do this. The switch is a