similar to: Problem with integrating ISDN PBX using NT mode

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

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

Hi all, We're trying to hook up our Asterisk config (Card: TE410P) with a Siemens EWSD switch. The link is ok on both ends (green), with no errors. The problem is when we try to make a call from our side (via call files), we get the pri/E1 error Ext: 1 Cause: Temporary failure (41), class = Network Congestion (2) Our Telecom partner (they checked with Siemens) mentioned that we need to

*This message was transferred with a trial version of CommuniGate(tm) Pro* In setting up Asterisk, I'm looking to dump my current phone system (Nortel Venture). I presently have three POTS lines. I would use a VOIP provider, but now are presently available in the Toronto, ON, CANADA area that support user owned hardware/software. I need a 416/647 area code number. In looking at FXO cards

Hi all, I just configures my PRI and incoming calls are working fine but outside calling giving error PRI is BUSY :( any idea ? I have same setup on other box and that boxes works perfect. -- DAHDI/i1/6463279153-2 is proceeding passing it to SIP/7328-00000002 -- DAHDI/i1/6463279153-2 is making progress passing it to SIP/7328-00000002 -- DAHDI/i1/6463279153-2 is busy -- Hungup

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

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 2 ISDN BRI boxes, each with 4 spans, where the first one is configured as CPE, the second one as NET(so I don't need real lines for developing and testing). Once in a while I do see the following libpri error messages simultaneously on both boxes: PRI Span: 1 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 7(Multi-frame established) PRI Span: 2 TEI=0 MDL-ERROR (A): Got

Hi list! We currently have a PRI gateway composed by a box with two Digium quad-span PRI cards (a TE420 and a ). One of the cards is filled with TELCO1, while the other has first two slots filled with TELCO2, and 3rd slot with TELCO3. I am currently having (timer ?) issues on TELCO3 (span 7) D-Chan (202 as determined by dahdi_genconf ) is constantly failing causing on-going calls to terminate.

PRI debug of the entire call would be great, also, switchtype would be awesome as well. Thanks! Matthew Fredrickson On Thu, Mar 24, 2016 at 4:07 PM, Carlos Rojas <crt.rojas at gmail.com> wrote: > Hi > > Did you activate the pri debug on the cli asterisk? > > On Thu, Mar 24, 2016 at 12:59 PM, Carlos Chavez <cursor at telecomabmex.com> > wrote: >> >>

Dear; Thanks a lot for guiding me. Is it possible that the installation libpri-1.4.11.5 newer than the libpri-1.4.11.5-patch? Well, when I typed (note: I am trying to apply the libpri-1.4.11.5-patch for the libpri-1.4.11.5): libpri-1.4.11.5# patch -p0 -i libpri-1.4.11.5-patch It gave me that patched detected as shown below (example of one file, and I got same for other files): patching file

Hi all, I really hope that you guys can help, because I've been tearing my hair out for the past 5 hours on this one. I have a Zaphfc (BRI) card in TE mode connected to the S-Bus of a Nortel Meridian phone system. Phone calls from the Nortel to say MSN 510 are correctly being sent to the right SIP phone. When asterisk dials say Zap/g2/224 (a Nortel internal extension) the call goes

I have an asterisk with a TE110P configured as T1 which is behind a PSTN gateway. This gateway has an E1 to PSTN and a T1 to asterisk. This T1 is configured as Network and * as CPE. Every call I receive in E1 gateway is directly switched to asterisk using T1. Remember E1 is alaw. Both E1 and T1 have Natural Microsystems boards with a very simple software. When I call to E1 asterisk signalling

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:

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

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

I've this error How i can find the problem? Apr 23 12:24:43 WARNING[131081]: PRI: received TEI check request for TEI = 89 Apr 23 12:24:47 WARNING[131081]: PRI: received TEI check request for TEI = 89 Apr 23 12:24:48 WARNING[131081]: PRI: !! Got a UA, but i'm in state 1 Apr 23 12:24:53 WARNING[131081]: PRI: received TEI check request for TEI = 89 Apr 23 12:25:02 WARNING[131081]: PRI:

Hi, I'm experiencing difficulties to get a B410P running with Asterisk 10.3.1 and DAHDI 2.6.1. Am I supposed to use DAHDI for this card and ISDN BRI for my country (Belgium)? thx, BC

I've been working on an asterisk box at work for a few weeks now, things were finally starting to sail smoothly until I hit this head scratcher this morning. It's a rather intricate problem, so bear with me. Heres the scenario. What works: If I call from my sip phone -> sip phone everythings ok If I call from sip phone -> external pots number ok as well If I map one of our

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