similar to: is there a reference guide to "pri debug span" messages?

I have attached my PRI debug out put when making an international call - hopefully it can shed some light on the situation. I am sorry if this attachment gets to the list twice, I sent one early this morning, but it has yet to appear - i may have sent that one in error. Kind Regards: Gabriel -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello, I have an ISDN-30 connection and a Digium TE-121 with VPMADT032 echo cancellation. Every 30-60 minutes I experience PRI dropping. @@@ /etc/zaptel.conf: loadzone=dk defaultzone=dk span=2,1,0,ccs,hdb3,crc4 bchan=32-46 dchan=47 bchan=48-62 @@@ @@@ /etc/asterisk/zapata.conf [channels] switchtype=euroisdn usecallerid=yes group=2 signalling=pri_cpe context=incoming channel => 32-46

Hello my friends, I would like to understand the output from "pri intense debug span X", the Telco always says that their side is OK, but i always receive alarms, loosing connection, take a look: [Sep 16 13:18:19] WARNING[30364] chan_zap.c: Detected alarm on channel 1: Recovering [Sep 16 13:18:19] WARNING[30364] chan_zap.c: Unable to disable echo cancellation on channel 1 [...] [Sep 16

Hi, I am lost trying to figure out how to enable overlap dialing for calls coming in and coing out on a pri span. DISA looked promising at first, but does not seem to support overlap dialing. Just picking up a call by and trying to dial out does not seem the way to do it either. I tried: [dialincontext] exten => 12341234,1,Goto(dialoutcontext,s,1) [dialoutcontext] exten => s,1,Wait,1

We are seeing the message " PRI Error on span 1: Received MDL/TEI management message, but configured for mode other than PTMP" on one of our Asterisk boxes on a PRI. A Google search turns up a number of hits for this error, but they are all for BRI not PRI. I'm reasonably sure there are no recent updates or config changes. Running Asterisk 1.4.37. We can update to 1.4.44 if it

Dear R users, Has anyone implemented a "matrix log" function in R similar to the function logm() in Matlab? I did a quick R site search and browsed the contributed packages to no avail. The octave function is far too simplistic and fails for the Matlab test matrix. Ideally, the code of Cheng, Higham, and Laub (2001) or something similar could be utilized. Just checking before I

anyone? -a -- =============================================================================== | EMAIL :: Ara [dot] T [dot] Howard [at] noaa [dot] gov | PHONE :: 303.497.6469 | When you do something, you should burn yourself completely, like a good | bonfire, leaving no trace of yourself. --Shunryu Suzuki ===============================================================================

Hi, Hey people, i have a TE210P with a ISDN PRI in M?xico. It is working just fine with Asterisk, I just have a minor glinch. When I dial a number that doesn't exists the Zap channel is imediatly hungup, instead of putting my trougth the providers message: "Sorry, the number that you dialed does not exists, etc". I have a call center and the people there really need to be able to

Hi, I'm trying to connect to Telewest/Virgin Media with a TE110P using asterisk 1.4.13/zaptel 1.4.6. No matter what I try, my span always appears as PRI span 1/0: Provisioned, Down, Active My zapata.conf is currently ----------------------------------- [channels] echocancel=yes echocancelwhenbridged=no echotraining=yes switchtype=euroisdn contect=from-pri signalling=pri_cpe group=1 channel

Hi all, I'm debugging a PRI problem, i can see the calling number but i get a busy all the time. From the output below, I guess asterisk hangs up immediately. Can anyone point out what the problem is? Thanks in advance. *CLI> < Protocol Discriminator: Q.931 (8) len=32 < Call Ref: len= 2 (reference 4865/0x1301) (Originator) < Message type: SETUP (5) < [04 03 80 90 a3] <

Hello list We're trying to get a HFC card running in NT mode. Zaphfc loads fine as module and ztcfg -v is run only once per reboot. Cabling is ok, the ISDN-TE gets ist power fine. The HFC card does not share any interupts. After the TE picks up the console (pri debug enabled) shows: Nov 21 18:42:20 NOTICE[13326]: chan_zap.c:7169 pri_dchannel: PRI got event: 6 on Primary D-channel of span 1

Hello, I get an Error every minute on the second card of two installed TE410P Cards in our System. The error is: PRI got event. HDLC Abort (6) on Primary D-channel of span 5(-8) PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 5(-8) Is it possible that there are known problems with 2 cards in one system? I'm running Asterisk/Libpri/zaptel from SVN branch-1.2-16008 I was

Hi Guys, I have been checking logs and noticed this over the last night. Should I be concerned? and where to look for further details? Sample: [2010-04-13 04:31:27] VERBOSE[3844] logger.c: -- B-channel 0/1 successfully restarted on span 1 [2010-04-13 04:31:27] VERBOSE[3844] logger.c: -- B-channel 0/2 successfully restarted on span 1 [2010-04-13 04:31:27] VERBOSE[3844] logger.c: --

Hi, In BRI/TE/PtmP mode, pri show span 1 used to display "Type: CPE (PtMP)" (setup is bristuffed 1.2 asterisk) It seems, it displays now "Type: CPE" without any mention to PtMP (with asterisk 1.6). I'm far from 100% sure it used to include the PtMP word but do you think it should display it ? Does it make sense ? Regards -------------- next part -------------- An HTML

Hi all, has anybody ever encountered this ERROR before? It happens frequently on my debian6-based pbx. I'm using Asterisk 1.8.11 with dahdi-linux-2.4.1 and a quadBRI card. ERROR: chan_dahdi.c: PRI Span: 3 PROBLEM: General: Badly Structured Component I tried to google but without success. Do you know what it means? Should I worry? Thank You Giorgio

This indicate that the connection with the local provider PTSN it is ok? : -- Attempting call on Zap/10 for s@inbound:1 (Retry 2) -- Making new call for cr 32781 > Protocol Discriminator: Q.931 (8) len=28 > Call Ref: len= 2 (reference 13/0xD) (Originator) > Message type: SETUP (5) > Bearer Capability (len= 3) [ Ext: 1 Q.931 Std: 0 Info transfer capability: Speech (0) >

Now that's quite interesting - yes, this is a two way span. I thought that the D-channel negotiation that happens before the B-channel is set up would have implicitly avoid the glare condition through signalling the intent-to-use to the resource to the remote end (a-la E&M wink start). So what seems to be happening in my case is my CPE is set for a 'Descending' b channel sequence

I upgraded from Tormenta2 to Sangoma A101. I followed the instructions, and installation was successful. zttool, ztcfg, all show card is installed properly. I copied the parameters from my old working zaptel.conf, zapata.conf and zapata-auto.conf. Verified on Sangoma website that these files are correct. Also configured wanpipe1.conf. But doing all this didn't start the PRI channels. It says

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

Hello everyone, Today is exactly 10 years ago that tinc 1.0 was released. I would have hoped to celebrate this by releasing 1.0.22 and 1.1pre8 today, but this will instead happen in one week. Tinc 1.1 is close to becoming stable, and I hope to release 1.1.0 before the end of the year. The main features of tinc 1.1 are the improved security over tinc 1.0, and a much nicer interface that makes it