Displaying 20 results from an estimated 9000 matches similar to: "Strange problem with PRI on 64-bit?"
2018 Apr 03
3
Strange problem with PRI on 64-bit?
In article <CAHZ_z=w5DMg93gShtC93kuC+fnmraPgV46BS956U5BQXVgyhxg at mail.gmail.com>,
Matt Fredrickson <creslin at digium.com> wrote:
> On Tue, Apr 3, 2018 at 5:44 AM, Tony Mountifield <tony at softins.co.uk> wrote:
> > I have some more investigation to do on this, but I wanted to see if anyone
> > here had any insight into the issue I've run into.
> >
>
2018 Apr 03
3
Strange problem with PRI on 64-bit?
On Tue, Apr 3, 2018 at 4:57 PM, Matt Fredrickson <creslin at digium.com> wrote:
> On Tue, Apr 3, 2018 at 4:38 PM, Tony Mountifield <tony at softins.co.uk>
> wrote:
> > In article <CAHZ_z=w5DMg93gShtC93kuC+fnmraPgV46BS956U5BQXVgyhxg@
> mail.gmail.com>,
> > Matt Fredrickson <creslin at digium.com> wrote:
> >> On Tue, Apr 3, 2018 at 5:44 AM, Tony
2013 Sep 05
1
MDL-ERROR
I have 2 ISDN BRI boxes, each with 4 spans, where the first one is configured as CPE, the second
one as NET(so I don't need real lines for developing and testing).
Once in a while I do see the following libpri error messages simultaneously on both boxes:
PRI Span: 1 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 7(Multi-frame established)
PRI Span: 2 TEI=0 MDL-ERROR (A): Got
2010 Dec 16
1
PTMP BRI Unable to receive TEI from network in state 2(Assign awaiting TEI) - Asterisk 1.6.2, Latest DAHDI, LibPRI
Hi all,
Last night I went to replace an Asterisk 1.4 + mISDN + b410p box with
Asterisk 1.6.2 and DAHDI BRI - to no avail.
I had two servers so copied network setting etc from the working one,
moved the card across, ran dahdi_genconf etc and it didn't work.
Here's the console output with notices disabled:
lucas*CLI> pri intense debug span 1
Enabled debugging on span 1
[Dec 16
2011 Mar 18
7
One PRI card with 2 (or more) Telcos
Hi list!
We currently have a PRI gateway composed by a box with two Digium quad-span
PRI cards (a TE420 and a ).
One of the cards is filled with TELCO1, while the other has first two slots
filled with TELCO2, and 3rd slot with TELCO3.
I am currently having (timer ?) issues on TELCO3 (span 7)
D-Chan (202 as determined by dahdi_genconf ) is constantly failing causing
on-going calls to terminate.
2010 Sep 29
1
Weird Behavior with DAHDI
Hello,
I'm experiencing some weird problems on my server:
- 1) The following messages are filling up my logs:
[Sep 29 08:24:59] WARNING[7077]: chan_dahdi.c:2789 pri_find_dchan: No
D-channels available! Using Primary channel 140 as D-channel anyway!
[Sep 29 08:24:59] WARNING[7078]: chan_dahdi.c:2789 pri_find_dchan: No
D-channels available! Using Primary channel 171 as D-channel anyway!
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
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
2011 Jan 24
1
B410P: DAHDI BRI PTMP HDLC Abort (6) on Primary D-channel of span 1 (TEI Errors)
Hi all,
So, we reverted the LibPRI version and tested it, and then tried with
the latest version of everything. Still no changes.
The BRI line is in PTMP. If we set the configs to PTMP in the
genconf_parameters and try it, we get the following:
[Jan 21 17:32:20] ERROR[20341]: chan_dahdi.c:12645 dahdi_pri_error:
Unable to receive TEI from network!
If we set it to PTP (which it is not) we
2014 Feb 18
1
PRI Error on span 1: Received MDL/TEI management message, but configured for mode other than PTMP
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
2012 May 09
5
Belgian BRI (euroisdn): what to use for a B410P
Hi,
I'm experiencing difficulties to get a B410P running with Asterisk
10.3.1 and DAHDI 2.6.1.
Am I supposed to use DAHDI for this card and ISDN BRI for my country
(Belgium)?
thx,
BC
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
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
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.
2011 Oct 16
0
PRI E1 call termination issue
Hi List,
I have configured TE121PF card in E1 mode. I am using asterisk
1.6 and freepbx 2.7. My card staus turn in to green and looks like sync with
the service provider. My service provider is BSNL - India. I have one toll
free number for incoming and one land line number for out going calls.
Problem :
If i am calling to the toll free number, i am getting the ring but that call
is
2013 Oct 31
2
issue with dahdi_channels.conf
Hello list
i have an issue with my dahdi_channels.conf
in span 1 when i use it like below i can do my outband calls without issue
; Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" (MASTER)
group=0,11
context=from-pstn
switchtype = euroisdn
signalling = pri_cpe
channel => 17-31
context = default
group = 63
but when i add in channel 1-15 like: channel => 1-15,17-31
i receive all
2014 Jan 20
1
ISDN Cause Code 47 Errors
We fairly recently switched service providers for our 4 PRI circuits. Since
that time, we started to notice some failed inbound calls. These calls
terminate with an ISDN cause code 47 'resource unavailble'. Most of the
time I see this error on the first or second channel on the second span in
a trunk group (This is the providers trunk group for hunting, not an
Asterisk trunk group). All
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