Displaying 20 results from an estimated 10000 matches similar to: "E100P - connected to Cisco"
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 Feb 28
2
No Caller ID Name PRI NI2
I there,
I have some trouble to do working caller id name for outgoing calls on
the PRI we just installed. Caller id name work on incoming calls only.
Caller id number work on incoming and outgoing calls.
The provider, Goup Telecom, said that's in what i'm sending. They said
that I send the cid name in ascii code and to do it working, I need to
send it in hex.
So I take some traces
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
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
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
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
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
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 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
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 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]
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
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
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|
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
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
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
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:
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
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