Displaying 20 results from an estimated 2000 matches similar to: "serios problem with zaptel or asterisk"
2005 Jan 09
5
Help in E1-T1 encoding
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
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 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
2005 Mar 15
1
PRI: Call Reference Length not supported
I'm not a PRI expert and therefore don't know what this debug stuff means
for PRI, so if anyone can help me here...
I'm running the latest libpri and zaptel from CVS.
Keep in mind that everything works fine when using the STABLE libpri and
zaptel.
I am NOT running CVS asterisk. I am running 1.0.6.
asterisk*CLI> pri intense debug span 1
Enabled EXTENSIVE debugging on span 1
T203
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
2004 Oct 07
1
T100P Pri Audio
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
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
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
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
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
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
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
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|
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
2004 Mar 18
4
zaphfc problem
Hi,
I have a partial working installation with zaphfc.
Incoming call :
For incoming call, seems work fine. But the sound is very bad with bounce
short crashing sound. Same sound with echo cancel off or on.
SDA work fine.
Another problem, it's seems that's zaphfc don't reset correctly the line. I
have one of my D channel how was busy even after stop communication.
Outgoing call :
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"
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
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
2007 Oct 31
4
PRI over T1 calls dropping, cause 100
I have a T1 link from asterisk 1.2.23 (also tried with 1.4.13) to a Meridian
Option 61C. Calls either way drop with error "Channel 0/23, span 1 got
hangup, cause 100". Can anyone offer insight into the cause and
solution/workaround? (I tried upgrading to Ast 1.4.13, and upgrading
matching zaptel & libpri, put the problem is identical).
For testing, I tried a call from the
2014 Aug 01
1
Connecting Asterisk and BT Versatility PBX via NT BRI port
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