Displaying 20 results from an estimated 4000 matches similar to: "pri "call by call" trunking?"
2007 Aug 06
4
low-level dump for PRI dchan debugging
I've been going back and forth with my telco for several days, trying
different configurations to get a new PRI to come up. The bchannels
are all up and the T1 is not in alarm status. The dchannel refuses to
come up however. We've tried ni2, qsig, and now dms100 for the
switchtype. The telco tech I've been working with says that he's been
sending "reset all channels"
2005 Aug 10
2
ZAP bchan and dchan HELP!!
We have install a DS3 with 28 DS1's we have an Adtran MUX breaking out
the DS1's, we are trying to setup the system with 2 dchannels for each 4
DS1's.
Everything looks fine when modprobe zaptel and wct4xxp and ztcfg -vvvvvv
but when I asterisk asterisk it says:
Aug 10 16:33:32 ERROR[8954]: chan_zap.c:6750 mkintf: Channel 24 is
reserved for D-channel.
Aug 10 16:33:32 ERROR[8954]:
2006 Apr 18
6
T1 to cross connect remote PBX and asterisk
Looking for someone with a successful experience similar to this;
I have a need to cross connect a 3COM NBX PBX PRI interface to asterisk,
but over a long distance. We do not need any IP connectivity and the
solution requires G.711u audio so there is no benefit to using IP.
Has anyone here successfully cross connected any PBX PRI interface
expecting NI2 PRI signaling B8ZS/ESF with an
2010 Aug 27
7
ASterisk CDR file Master.csv
How can we set the CDR Master file to rollover at say 30 Meg and create a new one
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100827/2e98385f/attachment.htm
2007 Jan 03
2
Sangoma A102 w/ EC module gets intermittent echo /audio artifacts
I've replaced 2XTE110 with an A102 with echo cancellation specifically to
deal with echo problems. However, user feedback has indicated to me that on
some calls (not a lot, but some) the call is unusable, with audio
artifiacts, described by one user, as: "very bad phasing reverb & feedback
(from my rock & roll days)". This is quite intermittent, as in most cases,
the user
2004 May 31
5
D-Channel Problems
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Good day eveyone,
I'm hoping that someone can help me. Perhapps i'm overlooking the obvious,
in truth, I hope that I am. I've scoured the mailing list and google,
and haven't come up with much.
I have a Digium T400P thats been connected to a channel bank for testing
for some time now. all has been well.
I've now just had
2005 Mar 01
3
Ordering a Voice PRI for Asterisk
We are in the process of ordering a Voice PRI to plug into Asterisk. Of
course we will be buying a card from Digium for this.
Question is this, there seem to be MANY options technically when ordering
this PRI (in the US) but since this is the first time ordering a voice
circuit I am clueless as to what options we need.
Any clues would be helpful or maybe something has already been written
2007 Feb 13
4
Nortel 81C MSDL Trunking to Asterisk TE110P, Nortel Resetting PRI Channels
We are currently working to trunk from a Nortel 81C to an Asterisk
Server 1.4 running on Red Hat Linux. We have two PRI trunks which work
with the exception of the clock slips, which is causing the Nortel to
reset the PRIs once a hour. Thanks for any suggestions.
81C MSDL Asterisk Digium
TE110P
REQ prt
TYPE adan dch 10
2006 Jan 24
13
Nortel Meridian Opt 81C and PRI
We've been trying unsuccessfully to connect our Meridian Option 81C to a
TE110P via PRI. We've followed the directions in
asterisk-meridian-a1.pdf (link on
http://www.voip-info.org/wiki/view/Asterisk+legacy+integration), but it
doesn't seem to work on our 81C (even though many, many users report it
works very well on Option 11's).
Has anyone had any success in getting the above
2004 Aug 05
2
PRI protocol question...
I'm having difficulty getting a PRI working between asterisk and a Merlin
Legend. I have been attempting to get it going as esf, b8zs & 5ess (although
I have tried other switchtypes...). I found the following info in the Legend
docs:
If the switch type is 5ESS, the protocol MUST be set for ATT Custom.
If switch type is DMS-100, the protocol MUST be set for NTNAPRI
The README in
2003 Jun 08
2
zapata.conf and zaptel.conf
Can anyone explain to me the difference in zaptel.conf and zapata.conf?
I'm trying to get a real clear understanding of them but its getting a
little murky in places. I will be setting up a PBX running asterisk with
2 T100P cards. I will be bringing a 23 channel PRI into one card and
connecting the other card to a Nortell 24 channel FXS channel bank. As I
understand it zapata.conf is
2004 Nov 29
1
New T100P Pri install suggestions?
In the next week or so, we'll be turning up a new T1 Pri from Cox Cable
in Omaha using a T100P (installed but not yet configured). While discussing
the interface parameters with a very knowledgable Cox engineer, we decided
on some of the basics including b8zs, esf, dchan=24, callerid, 5 digits
of called number forwarded to *, and switchtype=national (NI2). They
indicated their CO switch is a
2010 Aug 11
1
DAHDI config file system.conf
I have DAHDI 2.2.1
my system.conf file is :
span=1,0,0,esf,b8zs
bchan=1-23
dchan=24
echocanceller=mg2,1-23
loadzone = us
defaultzone = us
Its telling me:
Running dahdi_cfg: DAHDI_SPANCONFIG failed on span 1: Invalid argument (22)
[FAILED]
What am I missing. Its straight PRI NI2.
2007 Apr 16
4
New T1 Asterisk installation
Hi List,
I need to change my provider, at this time Asterisk box is on VOIP trunk.
I have two options, T1 or 15 analog lines.
I have some experience with analog and I have had two main issues with it.
first is echo (I have not tried HPEC yet) and second unpredictable volume.
The question is, if I use TE100 with PRI , will I have same issues?
I would appreciate any comments and sample zaptel.conf
2006 Mar 22
3
PRI DMS100 -> Nortel Meridian Option 81
Hello all,
I have Asterisk 1.2.1 and a TE110P connected to a Nortel Meridian Option
81C system. The PRI line is currently setup as DMS100. Here are the
relevant lines from zaptel.conf and zapata.conf:
zaptel.conf:
span=1,1,0,esf,b8zs
bchan=1-23
dchan=24
loadzone = us
defaultzone = us
zapata.conf:
[channels]
language=en
context=from-internal
musiconhold=default
switchtype=dms100
2012 Dec 21
2
dahdi timing source multiple cards
I have a box with 12 T1s (4 Te410P cards). The PSTN provider is reporting
slips and ask me to update the clock source. I have my system.conf set as
the following but when I run dahdi_scan only the ports on Card 1 are showing
up with syncsrc=1
system.conf :
span=1,1,0,esf,b8zs
bchan=2-24
mtp2=1
span=2,2,0,esf,b8zs
bchan=26-48
mtp2=25
span=3,3,0,esf,b8zs
bchan=49-72
2007 Nov 02
3
Two PRI setup questions
I am in the process of implementing a new ISDN pri and have a couple of questions. This is a full 24 channels (23 B and 1 D) delivered over a T1 interface. The interface looks good and is not showing any errors. Any help that you can provide would be greatly appreciated.
1) What switchtype should be configured in the zapata.conf file when AT&T is using CUSTOM? My understanding is that
2006 Apr 27
12
PRIs from two different telco
My TE411p does not seem to like to have two PRIs from different telcos
(span 1 and span 2). I can get one working, but not the other. However,
if I use vpmsupport=0 when loading the wct4xxp module, they both work.
But here is the problem, vpmsupport=0 disables the on board echo
cancellation. Any ideas?
BTW, here is zaptel.conf
span=1,1,0,esf,b8zs
span=2,2,0,esf,b8zs
bchan=1-23
dchan=24
2011 Aug 03
1
TE410P hardware problems
TE410P card down.
I have three (3) TE410P in one machine running asterisk with SS7.
My problems started last week when one of my cards started switching to E1
every time after reboot. I set the following in dahdi.conf and that solve
the problem.
/etc/modprobe.d/
options wct4xxp t1e1override=0x00
Now all 4 ports on that card is down with Red Alarm. I tried rebooting the
machine and
2005 Jun 11
4
PRI Trouble
Out of the blue i started receiving the following error on my PRI line
which connects my asterisk server to a Norstar 0x32 key system.
The asterisk zaptel.conf file was configure as follows and this config
worked for 6 months until friday. Nothing was changed on either system
prior to friday. here is teh zaptel.conf
span=1,0,0,esf,b8zs
bchan=1-23
dchan=24
span=2,0,0,esf,b8zs
bchan=25-47
dchan=48