Displaying 20 results from an estimated 3000 matches similar to: "No Caller ID Name PRI NI2"
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
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
2008 Oct 20
2
ISDN PRI Caller ID problem
Dear All,
I am trying to setup an ISDN line from local telco on a digium card. The
problem I am facing is that I am not getting any caller id from the
telco. They say that they have enabled caller id.
Please help me out.
My zapata.conf
--------------------------------------------------------------------------------------------------------------------
[trunkgroups]
[channels]
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
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|
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
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
2014 Apr 29
1
Inbound DAHDI Error
Hello,
I am trying to diagnose an intermittent error when a call comes in over our
PRI lines.
The problem appears random, however I have feeling it has something to do
with the call volume, as the frequency increases with more calls on the
system.
I am not an expert when it comes to reading the PRI Span Debug statements
but here is a call that had a problem and I bolded, italicized, and
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
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 :
2007 Mar 20
2
Problem with "AT&T Maintenance" protocol in PRI connection, no B+D channels available
Hi guys,
We are experiencing a problem with a T1 PRI connection. After trying a number of variations in the configuration files, the behavior is always the same: no B channels come up and the D channel doesn't appear to be working well. We can see there are AT&T Maintenance messages being exchanged by asterisk and the provider, CONNECT and CONNECT ACKNOWLEDGE, but that doesn't
2008 Jun 13
1
PRI crashing Asterisk
I have a user who's system crashes on pri hangup request. Tried 1.4.19.1 and
1.4.20 as well as the latest libpri no change
Progress is as follows......
< Supervisory frame:
< SAPI: 00 C/R: 0 EA: 0
< TEI: 000 EA: 1
< Zero: 0 S: 0 01: 1 [ RR (receive ready) ]
< N(R): 025 P/F: 1
< 0 bytes of data
-- ACKing all packets from 24 to (but not including) 25
-- Since
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
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.
2008 Mar 11
1
WARNING[4294]: chan_zap.c:8851 zt_pri_error: 1 copying 5 bytes LLC
Hi
I have recently upgraded my Asterisk system (from 1.2 to 1.4) and I have started to
notice the following messages when I recieve a call on my Zap channel
:-
[Mar 11 09:20:17] WARNING[4294]: chan_zap.c:8851 zt_pri_error: 1 copying 5 bytes LLC
I have a single PRI ISDN 30 link to a Siemens Realitis DX. Here is my
zapata.conf :-
[channels]
echocancel=no
echocancelwhenbridged=no
rxgain=-5.0
2011 Jun 07
2
PRI issue its BUSY
Hi all,
I just configures my PRI and incoming calls are working fine but outside calling giving error PRI is BUSY :( any idea ? I have same setup on other box and that boxes works perfect.
-- DAHDI/i1/6463279153-2 is proceeding passing it to SIP/7328-00000002
-- DAHDI/i1/6463279153-2 is making progress passing it to SIP/7328-00000002
-- DAHDI/i1/6463279153-2 is busy
-- Hungup
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
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
2010 Sep 03
1
not succeeding to hide callerid with outbound calls
Hi All,
In my dialplan and standard asterisk CLI logging i see that i am able to restrict the callerid when dialing out with asterisk.
however, on the receiving phone, the callerid is still displayed.
When i increment the logging of the pri with "pri set debug on span 1" on the CLI i also get the lower level debugging info from the pri.
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