mailinglists
2004-Dec-03 12:43 UTC
[Asterisk-Users] ZAPHFC, Asterisk does not load with signalling = bri_net_ptmp
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
I am trying to get zaphfc running in nt mode with asterisk. I am using
bri-stuff 0.2.0 rc2b (but tried others) and everything compiles well
against my mandrake 2.4.25-9mdk kernel (tried 2.6.3 also but that was a
disaster). I followed the exact instructions on wiki and both zaptel
and zaphfc load ok When I load zaphfc syslog says:<br>
<br>
<b>Dec 3 20:26:12 asterisk kernel: PCI: Enabling device 00:0a.0
(0000
-> 0003)<br>
Dec 3 20:26:12 asterisk kernel: PCI: Found IRQ 9 for device
00:0a.0<br>
Dec 3 20:26:12 asterisk kernel: zaphfc: CCD/Billion/Asuscom 2BD0
configured at mem 0xc48dc000 fifo 0xc1aa8000(0x1aa8000) IRQ 9 HZ 100<br>
Dec 3 20:26:12 asterisk kernel: zaphfc: Card 0 configured for NT
mode<br>
Dec 3 20:26:12 asterisk kernel: zaphfc: 1 hfc-pci card(s) in this
box.<br>
</b><br>
looks good I think...<br>
<br>
ztcfg -v says:<br>
<br>
<b>Zaptel Configuration<br>
======================<br>
<br>
SPAN 1: CCS/ AMI Build-out: 399-533 feet (DSX-1)<br>
<br>
3 channels configured.</b><br>
<br>
looks good also!<br>
<br>
when I use "<b>signalling = bri_net_ptmp</b>" in
/etc/asterisk/zapata.conf and start asterisk, asterisk stops at the
initializing of chan_zap without errors or warnings... It just
stalls... When I use "<b>signalling = bri_net</b>"
instead, although I
am not sure if that is OK to do, asterisk loads and chan_zap replies:<br>
<br>
<b>[chan_zap.so] => (Zapata Telephony w/PRI)<br>
== Parsing '/etc/asterisk/zapata.conf': Found<br>
-- Registered channel 1, PRI Signalling
signalling<br>
-- Registered channel 2, PRI Signalling
signalling<br>
-- Automatically generated pseudo
channel<br>
== Starting D-Channel on span 1<br>
== Registered channel type 'Zap' (Zapata Telephony Driver
w/PRI)<br>
== Registered channel type 'Tor' (Zapata Telephony Driver
w/PRI)<br>
== Registered application 'CallingPres'<br>
== Manager registered action ZapTransfer<br>
== Manager registered action ZapHangup<br>
== Manager registered action ZapDialOffhook<br>
== Manager registered action ZapDNDon<br>
== Manager registered action ZapDNDoff<br>
== Manager registered action ZapShowChannels<br>
</b><br>
No bad feelings about this either... but it does not work!<br>
<br>
I have a terminal adaptor connected crosswired to the zaphfc board
(e-tech PCTA128) and an analogue phone connected to the terminal
adaptor. The phone is dead, either with or without a NT1 connected in
between. I get no debug information if I load the zaphfc module with
debug=1.<br>
<br>
When I try to call to a zap channel I get this:<br>
<br>
<b>*CLI> -- Executing
Dial("SIP/11-d2ad", "ZAP/1|20") in new
stack<br>
Dec 3 20:34:49 NOTICE[262160]: app_dial.c:727 dial_exec: Unable to
create channel of type 'ZAP'<br>
== Everyone is busy/congested at this time<br>
</b><br>
Another thing that I consider weird is that I was told that with zaphfc
you did not need ztdummy anymore as a timing device for musiconhold.
When zaphfc is loaded musiconhold does not work (without notice of
asterisk)! Not even when ztdummy is loaded aswell.<br>
<br>
Maybe someone has a clue what's wrong, because I am out of ideas.
Everything else works but I would really like this feature...<br>
<br>
I hope someone can help.<br>
<br>
Regards,<br>
<br>
Bart<br>
</body>
</html>
Possibly Parallel Threads
Wisdom of the Ancients
