Hi,
A telco has recently installed a new line in our building and I need to connect
it to my Asterisk server with a Digium PRI card.
It's not the first time I set up and configure a PRI link but I'm
failing to make this one work.
The only information I got from the telco is:
"
Line Coding [HDB3]
Framing [CRC4]
Encapsultation [hdlc
Isdn switch-type primary-[net5]
"
Is "crc4" actually a "framing" parameter as stated by the
telco, or is it just an "optional line coding parameter"?
I searched the web and not knowing exactly which parameters to use, I tried the
following zaptel/dahdi config:
# TE120P (PRI):
span=1,1,0,ccs,hdb3,crc4
# as E1
bchan=1-15
dchan=16
bchan=17-31
switchtype = euroisdn
signalling = pri_cpe
However, the link doesn't work and I get this:
*CLI show status:
Description Alarms IRQ bpviol CRC4
Wildcard TE120P Card 0 RED 1 0 0
# cat /proc/zaptel/1
Span 1: WCT1/0 "Wildcard TE120P Card 0" (MASTER) HDB3/CCS/CRC4 RED
IRQ misses: 1
1 WCT1/0/1 Clear (In use) RED
2 WCT1/0/2 Clear (In use) RED
3 WCT1/0/3 Clear (In use) RED
4 WCT1/0/4 Clear (In use) RED
5 WCT1/0/5 Clear (In use) RED
6 WCT1/0/6 Clear (In use) RED
7 WCT1/0/7 Clear (In use) RED
8 WCT1/0/8 Clear (In use) RED
9 WCT1/0/9 Clear (In use) RED
10 WCT1/0/10 Clear (In use) RED
11 WCT1/0/11 Clear (In use) RED
12 WCT1/0/12 Clear (In use) RED
13 WCT1/0/13 Clear (In use) RED
14 WCT1/0/14 Clear (In use) RED
15 WCT1/0/15 Clear (In use) RED
16 WCT1/0/16 HDLCFCS (In use) RED
17 WCT1/0/17 Clear (In use) RED
18 WCT1/0/18 Clear (In use) RED
19 WCT1/0/19 Clear (In use) RED
20 WCT1/0/20 Clear (In use) RED
21 WCT1/0/21 Clear (In use) RED
22 WCT1/0/22 Clear (In use) RED
23 WCT1/0/23 Clear (In use) RED
24 WCT1/0/24 Clear (In use) RED
25 WCT1/0/25 Clear (In use) RED
26 WCT1/0/26 Clear (In use) RED
27 WCT1/0/27 Clear (In use) RED
28 WCT1/0/28 Clear (In use) RED
29 WCT1/0/29 Clear (In use) RED
30 WCT1/0/30 Clear (In use) RED
31 WCT1/0/31 Clear (In use) RED
Placing a call through the Zap/Dahdi trunk in Asterisk doesn't work and I
get the following message in the log:
chan_dahdi.c: No D-channels available! Using Primary channel 16 as D-channel
anyway!
logger.c: -- Attempting call on Zap/g1/999xxxxxx for 999xxxxxx at
custom-TESTCALL:1 (Retry 1)
channel.c: Unable to request channel Zap/g1/999xxxxxx
pbx_spool.c: Call failed to go through, reason (8) Congestion (circuits busy)
chan_dahdi.c: No D-channels available! Using Primary channel 16 as D-channel
anyway!
Am I missing some information here?
I'm *supposing* it should be E1 (and that I can use 16 as dchan), euroisdn
(not "national"), but my telco states "hdlc Isdn switch-type
primary-[net5]" and I don't know how to translate it to zaptel/dahdi...
Also, my telco hasn't mentioned anything about ccs but I tried it anyway
because I wouldn't know what else to use.
I also tried
signalling = pri_net
but still got the same RED alerts.
Any suggestions?
Thanks
Vieri
On Wed, 7 Dec 2011, Vieri wrote:> A telco has recently installed a new line in our building and I need to > connect it to my Asterisk server with a Digium PRI card. > > It's not the first time I set up and configure a PRI link but I'm > failing to make this one work. > > chan_dahdi.c: No D-channels available! Using Primary channel 16 as D-channel anyway!We usually get D channels on the first channel of the first T1 in an NFAS group and the last channel of the last t1. However, telcos don't always get the order right. I've spent hours trying configurations and varying the D channel. Sometimes it's just that they number things in a different order than we were expecting. Sometimes, it almost appears that they use a dartboard :) -- Thanks in advance, ------------------------------------------------------------------------- Steve Edwards sedwards at sedwards.com Voice: +1-760-468-3867 PST Newline Fax: +1-760-731-3000
On Thu, Dec 8, 2011 at 10:14 AM, Olivier <oza_4h07 at yahoo.fr> wrote:> In fact I was rather referring to the previous example in which a > cable did run OK for years and suddenly stopped to. >My THEORY is that the driver chips on either end were wearing out and no longer able to send or receive as well as they once did. When you run the correct pairs, the wires are twisted together. This is important for a variety of electrical reasons, too lengthy to cover here, but a quick google search will give you a lot of info if you care. If you use an ethernet cable, you are using a pair of wires that is not twisted together, removing the electrical advantage of twisted-pair cable.> Obviously, the connector pins were still correctly set. > If it stopped to work, then it must come from the electric signals and > should explained through cable impedance or things like that. >Yes, exactly. -- Carlos Alvarez TelEvolve 602-889-3003 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20111208/13d1cb6c/attachment.htm>
Il 08/12/2011 18.17, Carlos Alvarez ha scritto:> If you use an ethernet cable, you are using a pair of wires that is > not twisted together, removing the electrical advantage of twisted-pair > cable.This is wrong, in both T568A or T568B ethernet pins 1/2 and 4/5 runs on a properly twisted pair. Also 120 Ohm impedance is matching the ISDN pri specification. If a straight pri cable is needed then a straight ethernet cable fits the job (not the same for a pri cross cable vs an eth cross cable).
On Thu, Dec 8, 2011 at 10:48 AM, giovanni.v <iax at keybits.org> wrote:> > This is wrong, in both T568A or T568B ethernet pins 1/2 and 4/5 runs on a > properly twisted pair. Also 120 Ohm impedance is matching the ISDN pri > specification. > If a straight pri cable is needed then a straight ethernet cable fits the > job (not the same for a pri cross cable vs an eth cross cable). > >It was probably the crossover I was thinking of, which is what I almost always end up needing. I stopped analyzing the situation when I found myself simply replacing them with the right cable and being successful. -- Carlos Alvarez TelEvolve 602-889-3003 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20111208/88c3e389/attachment.htm>