similar to: UK BT ISDN30e PRI Problem

Displaying 20 results from an estimated 400 matches similar to: "UK BT ISDN30e PRI Problem"

2010 Jun 22
3
PRI span problem - no D channel
Hi, I have the following happen to me after the restart of one of my servers: out of my 3 PRIs (all configured with the same technical settings), the last one isn't coming back. It's underutilized (chances it didn't get a call since my reboot), if it makes a difference . The PRI goes from provisioned to unprovisioned, and I get this regularly: [Jun 22 09:03:48]
2007 Jun 06
3
1.4 Zaptel/Sangoma Issues on CentOS
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:
2007 Oct 02
5
PRI Setup problem
Hi everyone, I'm trying to get a Sangoma A101D-X card talking to a Sasktel PRI (Megalink) circuit and having some trouble getting it to handshake. Thanks for any help or suggestions to diagnose this problem. The problem is that Asterisk has trouble bringing up the link. I see the following lines every couple of minutes: == Primary D-Channel on span 1 up == Primary D-Channel on
2009 Mar 26
2
PRI dropping #2
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 == ==
2007 Jul 12
0
No subject
caller can't hear anything. Asterisk CLI shows: =3D=3D Primary D-Channel on span 1 down =3D=3D Primary D-Channel on span 1 up =3D=3D Primary D-Channel on span 1 down =3D=3D Primary D-Channel on span 1 up =3D=3D Primary D-Channel on span 1 down =3D=3D Primary D-Channel on span 1 up all the time. Telecom told us that problem is in our box. Fast running zttest give me: --- Results after 279
2009 Nov 30
1
DAHDI - BRI - Astribank
Hello List, it is a very long time since I wrote here.... It has been still in Zaptel times.... Today I am run into a related problem: I can't get a DAHDI setup to work 100%. I am configuring an Astribank XR00013 (BRI, two ISDN ports). At some degree the installation (latest DAHDI drivers, Asterisk 1.6.0.18 on Centos 5.x) works. I can get incoming calls to the dialplan context that is
2010 Apr 10
2
t200_expire: q921_state now is Q921_LINK_CONNECTION_RELEASED
Hi everyone. We have a problem here... Hope somebody can give us some hints. We have a HP ProLiant DL180 G6 Server with a Debian/Lenny sytem. Asterisk 1.4.21.2 (1.4.21.2~dfsg-3+lenny1) with zaptel (1.4.11) and libpri (1.4.3) is installed. There is a QuadBRI-Card installed: # lspci -vv -s 06:04.0 06:04.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] (rev 01)
2009 Jan 16
0
No subject
"RED: Loss of signal (LOS): The equipment shall assume "loss of signal" when the incoming signal amplitude is, for a time duration of at least 1 ms, more than 20 dB below the nominal amplitude. The equipment shall react within 12 ms by issuing AIS." This sounds like what is happening, and is in order with what one of the technicians said - I was about 20 dB below their
2009 Jan 16
0
No subject
"RED: Loss of signal (LOS): The equipment shall assume "loss of signal" when the incoming signal amplitude is, for a time duration of at least 1 ms, more than 20 dB below the nominal amplitude. The equipment shall react within 12 ms by issuing AIS." This sounds like what is happening, and is in order with what one of the technicians said - I was about 20 dB below their
2009 Apr 03
1
ISDN Timer T309
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> Hi everione,<br> <br> I'm make some test with pri timer T309. I'm using asterisk 1.4.23.1, libpri 1.4.9, dahdi-linux 2.1.0.4 and dahdi-tools 2.1.0.2. But in my tests, the timer fail with a telco
2009 Oct 31
0
PRI line resetting on incoming call
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
2004 Jun 12
2
Sending SABME continuosly. Urgent help needed!
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
2003 Nov 21
3
PRI problems
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
2005 Mar 10
7
Panasonic TDA200 E1 -> E100P negotiation issues
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
2010 May 17
1
PRI down due to chan_zap.c: No more room in scheduler....Got SABME and Sending Unnumbered Acknowledgement...Any thoughts?
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?
2003 Aug 18
8
PRI Question
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
2007 Jun 28
2
E1 not coming up
-----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
2010 May 12
1
Sangoma A101D PRI failing with ERROR - -- Got SABME from network peer. Sending Unnumbered Acknowledgement
Hi Guys, Anyone might know why this error keeps showing up and inbound/outbound is not working on a Bell PRI with Sangoma A101D? -- Got SABME from network peer. Sending Unnumbered Acknowledgement No calls can be made inbound/outbound. Keeps repeating. No alarms ON and no changes been made to the system. Stopped all a sudden. Asterisk CLI doesn't show anything with full verbose for both
2008 Aug 13
1
Sending Set Asynchronous Balanced Mode Extended
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:
2010 Jun 29
21
[Bug 28810] New: Blank consoles (Ctrl+Alt+Fn) after X starts on Arch Linux with FX5200 card.
https://bugs.freedesktop.org/show_bug.cgi?id=28810 Summary: Blank consoles (Ctrl+Alt+Fn) after X starts on Arch Linux with FX5200 card. Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: Driver/nouveau