Question : d channnel is down solved


#1

I have installed hfc bri isdn card, but by starting asterisk it says no d channel is available
my zaptel.conf

span=1,0,3,d4,ami
span=2,2,3,d4,ami
span=3,0,3,d4,ami
span=4,0,3,d4,ami

bchan=1,2
dchan=3
bchan=4,5
dchan=6
bchan=7,8
dchan=9
bchan=10,11
dchan=12

zapata.conf

pridialplan = local
prilocaldialplan = local
nationalprefix = 0
internationalprefix = 00

echocancel = yes
 context=internal

signalling = bri_cpe
group = 1
; S/T port 1-2
channel => 1-2
channel => 4-5
context=internal
signalling = bri_net

group = 2
; S/T port 3-4
channel => 7-8
channel => 10-11

can anyone help?


#2

I don’t have any experiences with bri, but first you should check if this is happening on all d channels, or just a specific one. It might be that the clock source is not set properly. But that’s just my guess.


#3

Thanks for your quickly reply
here is some of the warnings

Apr 20 12:53:11 WARNING[11106]: chan_zap.c:2464 pri_find_dchan: No D-channels available!  Using Primary channel 6 as D-channel anyway!
Apr 20 12:53:11 NOTICE[11106]: chan_zap.c:8518 pri_dchannel: pri_shutdown
Apr 20 12:53:11 NOTICE[11106]: chan_zap.c:8511 pri_dchannel: PRI got event: No more alarm (5) on Primary D-channel of span 2
Apr 20 12:53:11 NOTICE[11105]: chan_zap.c:8511 pri_dchannel: PRI got event: No more alarm (5) on Primary D-channel of span 1
Apr 20 12:53:11 NOTICE[11109]: chan_zap.c:6565 handle_init_event: Alarm cleared on channel 1
Apr 20 12:53:11 NOTICE[11109]: chan_zap.c:6565 handle_init_event: Alarm cleared on channel 2
Apr 20 12:53:11 NOTICE[11109]: chan_zap.c:6565 handle_init_event: Alarm cleared on channel 4
Apr 20 12:53:11 NOTICE[11109]: chan_zap.c:6565 handle_init_event: Alarm cleared on channel 5
  == Primary D-Channel on span 3 down
Apr 20 12:53:11 WARNING[11107]: chan_zap.c:2464 pri_find_dchan: No D-channels available!  Using Primary channel 9 as D-channel anyway!
  == Primary D-Channel on span 4 down
Apr 20 12:53:11 WARNING[11108]: chan_zap.c:2464 pri_find_dchan: No D-channels available!  Using Primary channel 12 as D-channel anyway!

I want to test the card, i mean the card is not connecting with the real PBX, i just connect the card with a isdn phone,
after reading your reply, i guess without connecting to the real PBX, the timing resource can not work well and that make d channel down. is this guess right?


#4

I had similar problems with PRI long time ago though - so hopefully I will remember the right check list, but you should verify these:

  • Clock must be set to MASTER, if you’re connecting card to the ISDN phone, and to NORMAL (or however terminology for your card is) if you’re connecting to the telco.

  • Signaling must be bri_cpe when talking to the telco, and bri_net if you’re talking to the ISDN phone

I’m guessing that you cannot receive time source from the ISDN phone (which is logical), so try to simulate as if you were the telco … meaning that you should configure your card (and zaptel.conf) to dictate clock to the ISDN phone.

Hope, this will bring you bit closer to the solution.


#5

so far as my understanding, if want to set clock as MASTER, the parameter should be 1,2,…, if want to set clock as SLAVE it should be 0. If this is correct , then I have done nothing wrong.
is there other possible reason for this problem?


#6

Which country you are located ?


#7

[quote=“bxjy”][quote]

  • Clock must be set to MASTER, if you’re connecting card to the ISDN phone, and to NORMAL (or however terminology for your card is) if you’re connecting to the telco
    [/quote]
    so far as my understanding, if want to set clock as MASTER, the parameter should be 1,2,…, if want to set clock as SLAVE it should be 0. If this is correct , then I have done nothing wrong.
    is there other possible reason for this problem?[/quote]

Hmmm…can’t think of any other reason at this point. :frowning:


#8

hi RichardHH
I m in Germany.

and another question:
how can I bind a isdn phone to a given phone number? Because I m going to use the * box as a gateway ,which sit before a traditional PBX.


#9

Dann wechsel mal Deine Config, mit dem Signalling kann sie nämlich nicht klappen :wink:

Zaptel.conf:

Zapata.conf:

ggfls. den letzten Block austauschen:
signalling = bri_net_ptmp
context=default
group=1
channel => 1-2

Musst Du ausprobieren, welcher der letzten beiden Blöcke.

English:
The zaptel.conf and zapata.conf are wrong for germany.
The posted conf’s should work - out of mind tho since its a HCF 2-channel card and we are using a PMX Pri E1 here.


#10

[quote]
how can I bind a isdn phone to a given phone number? Because I m going to use the * box as a gateway ,which sit before a traditional PBX.[/quote]

YOu cant bind a “pure” ISDN phone with asterisk.
Asterisk is using:

  1. SIP
  2. IAX
  3. FXS/FXO

via network and/or ATA devices.

An ISDN phone is using the ISDN protocol, but there is no “adapter” so you cant (physically) connet the phone to asterisk.

Was that the question ?


#11

PS.:

If you want to use asterisk as a “gateway”, you need the so called
"NTBA/Crossover" Setup.

In short:
You use an old NTBA to terminate the line and connect asterisk via HCF card and crossover cable.

That way asterisk listens to the lines (yep…you see already:2 X HCF card…) and accesses the dialplan. Then it can route the call to a direct connected device (sipphone for instance) or via the second HCF card (Zap) to the phones connected to that card (or PBX conn. to that card).

But thats a trickey setup…i would rather go with pure SIP phones, much more handy !


#12

Hi RichardHH
Danke zuerst für deine Hilfe ,sofort probiere die CONF Datei.
as to the NTBA/Crossover sever: what we have planed is to combine the ip telephone with the traditoinal ones, so I think two cards , as you said , will be enough to take the job, one card listen to the pstn, and the other connect to the traditional pbx. What I have now is a 4 ports hfc isdn card, and I set 2 of them on nt mode and the others on te mode.
What I m going to test first is that without conecting with pstn if the soft phone and ip hard phone can communicate with the isdn phone, which connects with the nt mode port .
anyway, I ll try first, and paste the result here.

regards


#13

I think your conf file is right, the warnings are only about the port 1 and 2, which I use them to listen to pstn. I think if I connect the ports with PSTN then the warnings will be gone.

I m not sure if I have totally understood what you said.

will it not work ,
even if I connect the isdn phone with * box through the hfc-isdn card?


#14

Yellow alarm=Mostly on your side
Red alert=mostly the telco side

A red alert says "Help me, i have no communication with the telco at all"
which is pretty correct considering this:

I think if I connect the ports with PSTN then the warnings will be gone

LMAO, sure you need to connect a line to USE that line…hehehehe :smiling_imp:

If you find a way using a line WITHOUT connecting it, let me know, we all want to safe money… :smiley: :smiley:

Seriously:
Yep, you can connext an ISDN phone via HCF/Crossover/NTBA setup.

What i was saying is, not “directly” like via ATA or native protocol.
ISDN phones only with this “hack”.


#15

when I connect the incoming isdn line with the isdn card,the led turned from red to green, but when I attched the isdn phone on the isdn card ,there is no reaction ,the led is still red,and I can not hear the normal tone. where is the problem?


#16

Green on the HCF connected to your telco=Good ! Yummy !!

For the internal HCF setup:

pro-linux.de/work/asterisk/asterisk-1.html

But take a seat bro, its german… LMAO :smiling_imp:
Well, there are pictures :stuck_out_tongue:


#17

thanks RichardHH
I have read it , it is a little bit tricky. I did not know that I need a crossover isdn line. I can have a try, but I don’t understand why it should be like that. I mean, why the telephone can not connect directly an the hfc-isdn-card. Can you pl explain how the incoming calls through *box to reach the isdn phones?


#18

THe NTBA is not used as a nettermination here, its used as a BRIDGE.

Its “mis”-used to supply our enddevice with power and to do the linetermination (100 ohm) which we need.

If your phones dont need power from the ISDN line, you COULD miss the NTBA but still need to terminate the lines and cross the cable (receive and send line).

Thats why the use of an NTBA is the most easy thing, it comes with termination and linepower already… (in germany that is, dunno how it is at your place).

This is how the cable is crossed:

– 3–X--4–
– 4–X--3–

– 5–X--6–
– 6–X--3–

Note, that is no RJ-45/Ethernet TP cable, this is the standard 4-pin ISDN cable.


#19

PS.:
Just found an english one…:

isdn.jolly.de/download/v3.0/PBX4Linux-3.0.pdf

(PDF)


#20

Can you pl explain how the incoming calls through *box to reach the
isdn phones?

The phones are used via ZAP.

Imagine, card 1 is spawn 1, group 1 (zap…conf’s)
Line to telco

Imagine, card 2 is spawn 2, group 2 (zap…conf’s)
Line to phones

Dialplan to ring a phone:

exten=> 12345,1, Dial(Zap/g2/MSN-OF-NTBA-CONNECTED-PHONES,45,wW)

So, we could set the MSN of Phone 1 to “12345”, the second phone to “6789”.

If you use
exten=> 12345,1, Dial(Zap/g2/12345,45,wW)
Phone 1 should ring.

exten=> 6789,1, Dial(Zap/g2/6789,45,wW)
Phone 2 should ring.

I say “should” cause i never tested it for real, we use a PMX PRI E1 card.

One phone is working for sure with a dialstring without number:
exten=> 12345,1, Dial(Zap/g2,45,wW)

(Note, no number after “g2”)

The “45” is 45s timeout, “wW” means "callmonitoring incoming and outgoing allowed.