similar to: Possible PRI fault?

Hi, I' ve just connected a carte X100M to my asterisk server running zaptel-1.2.5, libpri-1.2.2 and asterisk-1.2.6 on SUSE 10.0. When I make modprobe wcfxo and modprobe zaptel I haven't any error, I have also chan_zap.so module existing in /usr/lib/asterisk/modules. But, when i run ztcfg, it shows me this: Zaptel Configuration ====================== Channel map: 0 channels configured.

I am running Asterisk 1.2.14 and Zaptel 1.2.12 and using a Digium TE110P card in E1 mode. I've recently noticed in my logs the following Jan 5 01:27:11 VERBOSE[22490] logger.c: [chan_zap.so]Jan 5 01:27:11 VERBOSE[22490] logger.c: [chan_zap.so] => (Zapata Telephony w/PRI) Jan 5 01:27:11 VERBOSE[22490] logger.c: == Parsing '/etc/asterisk/zapata.conf': Jan 5 01:27:11

Sorry I should have stated that I've tried +x, -x, x.y and x and I still get the same. Regards Lee -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Eric "ManxPower" Wieling Sent: 05 January 2007 08:10 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users]

Hi everyone, I have been having some problems lately with our PRI and Asterisk, or maybe it is just me. It happens once maybe twice a day, but when some of our customers are calling in, the phone just drops on them. I pulled the information below from the log from one that happened. I notice why it is happening, but I can't seem to figure out a way to stop it from happening. I also

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.

hello all, i'm using TE110P and all configuration prosess is done. but after i do the 'modprobe' for zaptel and wcte11xp, follow by ztcfg -vv and asterisk -vvvgc i have this error. *CLI> May 27 14:44:33 WARNING[3059]: chan_zap.c:8534 pri_dchannel: PRI Error: We think we're the network, but they think they're the network, too. May 27 14:44:34 WARNING[3059]: chan_zap.c:8534

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 all, I've done this a few times with other PBX's but swyx has stumped me! I'm having some trouble getting Asterisk connected to a Swyx system using a sangoma A104dx... currently the setup is: BT <-> Swyx The above setup works fine... what i'm trying to achieve is BT & SIP Trunks <-> Asterisk <-> Swyx I have connected to our BT (2 x ISDN30 UK) with

Here is the scenario: Asterisk 1.14.13; zaptel 1.4.6; Digium TE120P (same problem with various previous versions; same problem with different TE120P cards). The customer has a partial (10 B-Channel) PRI that when it is busy (eight or more B channels in use), tends to fail as shown below... [Jan 26 23:00:31] ERROR[31893] chan_zap.c: Write to 28 failed: Unknown error 500 [Jan 26 23:00:31]

Hi, I am getting this message on the * console on my first pri span. Pri show span show it is down, and I can't make any calls from the span. Apr 27 07:40:23 NOTICE[23988]: chan_zap.c:8202 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 27 07:40:23 NOTICE[23988]: chan_zap.c:8202 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 27

Hi everyone, I have a PRI conection on an * system running Asterisk 1.0.9, libpri 1.0.9 and zaptel 1.0.9.2 connected to an AXE 10 (APZ 21220 System 64) in the network side. I know the system and the wildcard I´m using are ok because I´ve used them before with other PRI connections (to a Siemens EWSD) without any problem. First the PRI didn´t work (I got the TE110P alarmed with red). After

Hi all, can somebody help me with pri configuration? Here my zapata.conf: ; Zapata telephony interface ; ; Configuration file [channels] switchtype=euroisdn signalling=pri_cpe ;group=1 channel => 1-15,17-31 ;group=2 channel =>32-46,48-62 ;group=3 channel => 63-77,79-93 ;group=4 channel => 94-108,110-124 And here my zaptel.conf: zaptel.conf [----] 0 L:[ 1+ 0

Hey, I wrote yesterday about PRI dropping, which turned out to just be a regular reset of unused B-channels. This time there's a real issue. As noted earlier I have an ISDN-30 connection, a Digium TE-121 with VPMADT032 echo cancellation. These are my configurations files: == /etc/zaptel.conf loadzone=dk defaultzone=dk span=1,1,0,css,hdb3,crc4 bchan=1-15 dchan=16 bchan=17-31 == ==

Hi again, I'm trying to setup our non pri T1 (they call it a Long Distance T1), our current pbx has the signaling set to E&M, I can set em in zapata.conf, but I'm trying to track down the proper entries for the zaptel.conf file. The digium docs only show a PRI example. Our current system has these settings: Signalling: E&M Framing mode: ESF Line Coding: B8SZ here's my

Hey everybody, I've, within the last 3 weeks, moved over to a PRI from SBC/AT&T. I've received several complaints about dropped calls. Reviewing the archives on PRI and dropped calls shows that I should set the resetinterval=never in the zapata.conf and restart. This hasn't helped. The dropped calls have to date only been on outbound calls. Usually within 2 to 3 minutes

Hello... Does anybody knows what is the meaning of thoose messages ? What i'm doing wrong here ? The * works fine , both incoming and outgoing services.. WARNING[163851]: File chan_zap.c, Line 5683 (zt_pri_error): PRI: Read on 47 failed: Unknown error 500 PRI got event: 8 WARNING[163851]: File chan_zap.c, Line 5683 (zt_pri_error): PRI: Read on 47 failed: Unknown error 500 PRI got event: 6

Hi, I'm installing E100P for isdn pri line. My configuration are like this. zaptel.conf ======================================= span=1,0,0,ccs,hdb3,crc4 loadzone = us defaultzone=us bchan=1-15 dchan=16 bchan=17-31 zapata.conf ================================================= [channels] context=default switchtype=euroisdn context=default signalling=pri_net usecallerid=yes

I am trying to test out my PRI configuration on a server by conection another asterisk server to it. I have the T-1 cards up and both set to bchan=1-23 and dchan=24 in zaptel.conf I am getting lost on the signalling in zapata.conf. using pri_cpe makes sense for my target box, but I am getting the following errors on my source box if I use pri_net or pri_cpe signalling. May 31 17:15:06

Hi all, I have 1 Card Digium TE412P and 2PRI E1. I have more problems with drops lines. The asterisk log is this: May 16 10:52:26 NOTICE[4465]: chan_zap.c:8194 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 1 May 16 10:52:26 WARNING[4465]: chan_zap.c:2287 pri_find_dchan: No D-channels available! Using Primary channel 16 as D-channel anyway! May 16 10:52:26 NOTICE[4465]:

I have not been able to get two B-channel transfer to work on DMS100 PRI. I consistently get the following errors: [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: ROSE RETURN ERROR: [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: OPERATION: RLT_OPERATION_IND [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: ERROR: RLT Not Allowed I have tried on two