Displaying 20 results from an estimated 1000 matches similar to: "PRI: Call Reference Length not supported"
2009 Oct 25
1
some issue with libpri cant go past 1.4.1
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
2006 Apr 18
0
Problem Using Asterisk Call Files with Zap PRI
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
2005 Sep 09
0
BRI debug, national ISDN speech call problem
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
2007 Nov 06
1
Telus (Alberta) PRI Caller ID NAME, Display IE, Facility ID
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
2004 Dec 23
1
PRI unable to request channel
I wonder if anyone has come across this odd behavour with a T1 PRI using
NI2 signalling from a Nortel switch.
Sometimes, when bringing up a PRI trunk, a channel gets into a state
where asterisk can't request a channel, and gets reason 0, but the
channel is not busy. The only thing so far that clears this state is to
make an incoming call to the channel, which succeeds. After that,
outgoing
2007 Jul 12
0
No subject
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|
2007 Jul 12
0
No subject
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
2004 Jan 10
0
E1 - E100P connected to Cisco - problem - HELP
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
Stephen J. Wilcox wrote:<br>
<blockquote type="cite"
2006 Mar 11
1
FW: I need to set NO CRC4 on zaptel.conf?
Hi all,
Can somebody help me out, to get the call going through to my provider?
I connected my A104D Sangoma card to E1/isdn and each I tried to make call I
get the errors below.
My protocol analyzer can see only setup info and release complete.
WIRELESS2*CLI> set debug 9
Core debug was 0 and is now 9
WIRELESS2*CLI> pri intense debug span 1
Enabled EXTENSIVE debugging on span 1
T203
2009 May 22
2
BT ISDN-30 Pri getting 'stuck' on outgoing calls.
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
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 Jan 12
1
E100P - connected to Cisco
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi,<br>
<br>
have any one sucessfully connected E100P to Cisco? I am
2010 Jun 21
1
DAHDI: Inbound BRI call, DDI not presented
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
2003 Jul 11
0
[Q]: Dialin problems over E1 on a Digium E100P
Hi....
Apologies for the length of this, but any help would be greatly appreciated
;-)...
I have installed and configured a Digium E100P on my Asterisk PBX and I have
connected this to an 8 port E1 VoIP gateway on a Cisco 6509. There is also
an external E1 link from our Telco plugged into one of the other ports on
this gateway and this gateway is in turn registered with a Cisco CallManager
2004 May 25
1
D-Channel on span 1 up/down + frame slips with zaptelBRI
I have installed two HFC PCI A-cards running zaphfc from bristuff-0.0.2,
which seems to work quite fine, but I continously receive the messages
"D-Channel on span 1 up" followed by "D-Channel on span 1 down" with a few
seconds interval. Why is that? Bri intense debug log and configuration
files below.
I don't need ztdummy or zaprtc, do I? I get some frame slips as well,
2010 Feb 18
0
ISDN phone not ringing. ISDN PBX not answering?!
Hi,
I've set up an Asterisk as voip gatway:
VOIP <-> Asterisk <-> hfc-s card <-> NTBA <-> Siemens Gigaset Dect ISDN pbx.
Outgoing calls from dect handset to the world are working. Incoming calls don't even ring the handset.
I'm using the dahdi driver with the zaphfc kernel module. The hfc-s card is in nt mode.
The msn is set at the dect phone/base station
2008 Apr 28
2
PRI hangup certain outgoing calls
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
2006 Feb 16
1
Problem making outbound calls on TE210P using NFAS
Hello,
I'm running Asterisk@home 2.5
asterisk 1.2.4
zapatel 1.2.2
libpri 1.2.2
on a Dell Poweredge 2850 (1 CPU) with a TE210P
I have 2 t1 circuits using NFAS with dchan on 24 and no backup dchan. I am able to receive inbound
calls on all channels and can only make outbound calls on channels 25-48.
Attempting to make an outbound call on channels 1-23 results in congestion.
2010 Sep 16
1
How to Understand a pri intense debug span X
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
2011 Oct 19
1
Problem E1 PRI
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