Sponsor: VoiceMeUp - Corporate & Wholesale VoIP Services

VoIP Mailing List Archives
Mailing list archives for the VoIP community
 SearchSearch 

[asterisk-users] HFC-S zap channels always busy

Goto page 1, 2  Next
 
Post new topic   Reply to topic    VoIP Mailing List Archives Forum Index -> Asterisk Users
View previous topic :: View next topic  
Author Message
jwinius at umrk.to
Guest





PostPosted: Thu Jan 03, 2008 10:08 am    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

Hi list,

Attempting to get an ISDN-BRI line connected using an HFC-S PCI card
together with Asterisk v1.4.14 and Zaptel 1.4.7 on a Debian etch
system, I find that I can't access the card's resources because the
channels are always be busy. An attempt to call out results in the
following CLI output:

== Primary D-Channel on span 1 down
== Primary D-Channel on span 2 down
-- Executing [0653214647 at phones:1] Dial("SIP/1000-081f3698",
"Zap/g0/0653214647 at channels||r") in new stack
[Jan 3 15:32:06] WARNING[9769]: app_dial.c:1130 dial_exec_full: Unable to
create channel of type 'Zap' (cause 34 - Circuit/channel
congestion)
== Everyone is busy/congested at this time (1:0/1/0)
== Auto fallthrough, channel 'SIP/1000-081f3698' status is 'CONGESTION'
== Primary D-Channel on span 1 down
== Primary D-Channel on span 2 down

Hopefully, someone here with more experience can point me in the
direction of a solution. Here are hopefully some more clues:

# lsmod | grep zap

zaphfc 13660 1
vzaphfc 24984 1
zaptel 185956 9 xpp,zaphfc,vzaphfc
crc_ccitt 2560 1 zaptel

# cat /proc/zaptel/*

Span 1: ZTHFC1 "HFC-S PCI A Zaptel Driver card 0 [TE]" (MASTER) AMI/CCS

1 ZTHFC1/0/1 Clear (In use)
2 ZTHFC1/0/2 Clear (In use)
3 ZTHFC1/0/3 HDLCFCS (In use)
Span 2: ZTHFC1 "HFC-S PCI A ISDN card 1 [TE]" AMI/CCS

4 ZTHFC1/0/1 Clear (In use)
5 ZTHFC1/0/2 Clear (In use)
6 ZTHFC1/0/3 HDLCFCS (In use)

It looks like the vzaphfc module creates a virtual interface. I have
only one HFC-S PCI card installed. Each channel is "(In use)"
immediately after Asterisk is started.

CLI> zap show channels

Chan Extension Context Language MOH Interpret
pseudo default en default
1 from-pstn en default
2 from-pstn en default
4 from-pstn en default
5 from-pstn en default

CLI> zap restart

Destroying channels and reloading zaptel configuration.
== Parsing '/etc/asterisk/zapata.conf': Found
== Parsing '/etc/asterisk/zapata-channels.conf': Found
[Jan 3 15:40:06] WARNING[9797]: chan_zap.c:1081 zt_open: Unable to
specify channel 1: Device or resource busy
[Jan 3 15:40:06] ERROR[9797]: chan_zap.c:7501 mkintf: Unable to
open channel 1: Device or resource busy
here = 0, tmp->channel = 1, channel = 1
[Jan 3 15:40:06] ERROR[9797]: chan_zap.c:12266 build_channels: Unable to
register channel '1-2'
[Jan 3 15:40:06] WARNING[9797]: chan_zap.c:11554 zap_restart: Reload
channels from zap config failed!

Not a good idea, because that results in...

CLI> zap show channels

Chan Extension Context Language MOH Interpret

the channels disappearing altogether. However, I can restore the
situation back to its original, albeit useless, state if I stop and
start Asterisk.

My configuration files are as follows:

/etc/asterisk/zapata-channels.conf (after running "genzaptelconf -sd -c nl"):

group=0,11
context=from-pstn
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel => 1-2
group=
context=default

group=0,12
context=from-pstn
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel => 4-5
group=
context=default

/etc/asterisk/zapata.conf (supposed to work in the Netherlands):

[trunkgroups]

[channels]
language=en
context=isdn-in
switchtype=euroisdn
pridialplan=dynamic
prilocaldialplan=local
nationalprefix = 0
internationalprefix = 00
overlapdial=yes
signalling=bri_cpe_ptmp
rxwink=300
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=100
rxgain=4.5
txgain=-3
group=1
callgroup=1
pickupgroup=1
immediate=yes
#include zapata-channels.conf

Abbreviated /etc/asterisk/extensions.conf:

[globals]

[general]

[isdn-out]
exten => _X.,1,Dial(Zap/g0/${EXTEN}@channels,,r)

[internal]
exten => 1000,1,Verbose(1|Extension 1000)
exten => 1000,n,Dial(SIP/1000,30)
exten => 1000,n,Hangup()

[phones]
include => internal
include => isdn-out

Any ideas?

TIA,

Jaap
Back to top
tzafrir.cohen at xorco...
Guest





PostPosted: Thu Jan 03, 2008 10:31 am    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

On Thu, Jan 03, 2008 at 04:08:10PM +0100, Jaap Winius wrote:
Quote:
Hi list,

Attempting to get an ISDN-BRI line connected using an HFC-S PCI card
together with Asterisk v1.4.14 and Zaptel 1.4.7 on a Debian etch
system, I find that I can't access the card's resources because the
channels are always be busy. An attempt to call out results in the
following CLI output:

== Primary D-Channel on span 1 down
== Primary D-Channel on span 2 down
-- Executing [0653214647 at phones:1] Dial("SIP/1000-081f3698",
"Zap/g0/0653214647 at channels||r") in new stack
[Jan 3 15:32:06] WARNING[9769]: app_dial.c:1130 dial_exec_full: Unable to
create channel of type 'Zap' (cause 34 - Circuit/channel
congestion)
== Everyone is busy/congested at this time (1:0/1/0)
== Auto fallthrough, channel 'SIP/1000-081f3698' status is 'CONGESTION'
== Primary D-Channel on span 1 down
== Primary D-Channel on span 2 down

What is the output of:

pri show spans

(Yes, it is "pri" and not "bri").

Do incoming calls work?

Quote:

Hopefully, someone here with more experience can point me in the
direction of a solution. Here are hopefully some more clues:

# lsmod | grep zap

zaphfc 13660 1
vzaphfc 24984 1
zaptel 185956 9 xpp,zaphfc,vzaphfc
crc_ccitt 2560 1 zaptel

Interesting... which one of those two is used?

I suspect vzaphfc is loaded automatically by udev, unless you have
zaphfc explicitly in /etc/modules .

Quote:

# cat /proc/zaptel/*

Span 1: ZTHFC1 "HFC-S PCI A Zaptel Driver card 0 [TE]" (MASTER) AMI/CCS

1 ZTHFC1/0/1 Clear (In use)
2 ZTHFC1/0/2 Clear (In use)
3 ZTHFC1/0/3 HDLCFCS (In use)
Span 2: ZTHFC1 "HFC-S PCI A ISDN card 1 [TE]" AMI/CCS

4 ZTHFC1/0/1 Clear (In use)
5 ZTHFC1/0/2 Clear (In use)
6 ZTHFC1/0/3 HDLCFCS (In use)

It looks like the vzaphfc module creates a virtual interface. I have
only one HFC-S PCI card installed. Each channel is "(In use)"
immediately after Asterisk is started.

CLI> zap show channels

Chan Extension Context Language MOH Interpret
pseudo default en default
1 from-pstn en default
2 from-pstn en default
4 from-pstn en default
5 from-pstn en default

CLI> zap restart

This will not work with digital spans. Try restarting asterisk.

e.g:

asterisk -R

restart now

Quote:

Destroying channels and reloading zaptel configuration.
== Parsing '/etc/asterisk/zapata.conf': Found
== Parsing '/etc/asterisk/zapata-channels.conf': Found
[Jan 3 15:40:06] WARNING[9797]: chan_zap.c:1081 zt_open: Unable to
specify channel 1: Device or resource busy
[Jan 3 15:40:06] ERROR[9797]: chan_zap.c:7501 mkintf: Unable to
open channel 1: Device or resource busy
here = 0, tmp->channel = 1, channel = 1
[Jan 3 15:40:06] ERROR[9797]: chan_zap.c:12266 build_channels: Unable to
register channel '1-2'
[Jan 3 15:40:06] WARNING[9797]: chan_zap.c:11554 zap_restart: Reload
channels from zap config failed!

Not a good idea, because that results in...

CLI> zap show channels

Chan Extension Context Language MOH Interpret

the channels disappearing altogether. However, I can restore the
situation back to its original, albeit useless, state if I stop and
start Asterisk.

My configuration files are as follows:

/etc/asterisk/zapata-channels.conf (after running "genzaptelconf -sd -c nl"):

group=0,11
context=from-pstn
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel => 1-2
group=
context=default

group=0,12
context=from-pstn
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel => 4-5
group=
context=default

/etc/asterisk/zapata.conf (supposed to work in the Netherlands):

[trunkgroups]

[channels]
language=en
context=isdn-in
switchtype=euroisdn
pridialplan=dynamic
prilocaldialplan=local
nationalprefix = 0
internationalprefix = 00
overlapdial=yes
signalling=bri_cpe_ptmp
rxwink=300
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=100
rxgain=4.5
txgain=-3
group=1
callgroup=1
pickupgroup=1
immediate=yes
#include zapata-channels.conf

Abbreviated /etc/asterisk/extensions.conf:

[globals]

[general]

[isdn-out]
exten => _X.,1,Dial(Zap/g0/${EXTEN}@channels,,r)

[internal]
exten => 1000,1,Verbose(1|Extension 1000)
exten => 1000,n,Dial(SIP/1000,30)
exten => 1000,n,Hangup()

[phones]
include => internal
include => isdn-out

Any ideas?

TIA,

Jaap

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen at xorcom.com
+972-50-7952406 mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
Back to top
jwinius at umrk.to
Guest





PostPosted: Thu Jan 03, 2008 11:28 am    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

Quoting Tzafrir Cohen <tzafrir.cohen at xorcom.com>:

Quote:
What is the output of:

pri show spans

PRI span 1/0: Provisioned, Down, Active
PRI span 2/0: Provisioned, Down, Active

Quote:
Do incoming calls work?

I haven't configured that yet.

Quote:
Interesting... which one of those two is used?

Good question. I've wanted to test that, but they're all the same: in use.

Quote:
I suspect vzaphfc is loaded automatically by udev, unless you have
zaphfc explicitly in /etc/modules .

It's not mentioned in /etc/modules.

Cheers,

Jaap
Back to top
jwinius at umrk.to
Guest





PostPosted: Fri Jan 04, 2008 10:29 am    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

Quoting Tzafrir Cohen <tzafrir.cohen at xorcom.com>:

Quote:
What is the output of:

pri show spans

PRI span 1/0: Provisioned, Down, Active
PRI span 2/0: Provisioned, Down, Active

Quote:
Do incoming calls work?

Negative, and nothing shows up on the CLI. And that's after creating
separate contexts called [default] and [pstn-in] in extensions.conf
for incoming ISDN calls.

Quote:
Interesting... which one of those two is used?

Good question. I've wanted to test that, but they're all the same: in use.

Quote:
I suspect vzaphfc is loaded automatically by udev, unless you have
zaphfc explicitly in /etc/modules .

It's not mentioned in /etc/modules.

I also tried removing only vzaphfc or zaphfc and learned two more things:

1) After modifying zapata-channels.conf accordingly, no zap channels
will show up in either of these configurations, i.e. "pri show spans"
shows nothing.

2) If I start Asterisk by running "genzaptelconf -sd -c nl", the other
module will first get loaded, zapata-channels.conf will be restored to
its original state* and all the channels will once again be in use.

# cat zapata-channels.conf
; Autogenerated by /usr/sbin/genzaptelconf -- do not hand edit
; Zaptel Channels Configurations (zapata.conf)
;
; This is not intended to be a complete zapata.conf. Rather, it is intended
; to be #include-d by /etc/zapata.conf that will include the
global settings
;

; Span 1: ZTHFC1 "HFC-S PCI A Zaptel Driver card 0 [TE]" (MASTER)
group=0,11
context=from-pstn
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel => 1-2
group=
context=default

; Span 2: ZTHFC1 "HFC-S PCI A ISDN card 1 [TE]"
group=0,12
context=from-pstn
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel => 4-5
group=
context=default

This is what "genzaptelconf -sd -c nl" keeps producing, although it
doesn't look right. But, even if I comment out the first or second
part and restart Asterisk, the remaining channels are always in use,
dialing in doesn't work (number not available), and nor does dialing
out (cause 34 - Circuit/channel congestion).

Cheers,

Jaap
Back to top
tzafrir.cohen at xorco...
Guest





PostPosted: Fri Jan 04, 2008 12:06 pm    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

On Fri, Jan 04, 2008 at 04:29:19PM +0100, Jaap Winius wrote:
Quote:
Quoting Tzafrir Cohen <tzafrir.cohen at xorcom.com>:

Quote:
What is the output of:

pri show spans

PRI span 1/0: Provisioned, Down, Active
PRI span 2/0: Provisioned, Down, Active

Quote:
Do incoming calls work?

Negative, and nothing shows up on the CLI. And that's after creating
separate contexts called [default] and [pstn-in] in extensions.conf
for incoming ISDN calls.

Quote:
Interesting... which one of those two is used?

Good question. I've wanted to test that, but they're all the same: in use.

Quote:
I suspect vzaphfc is loaded automatically by udev, unless you have
zaphfc explicitly in /etc/modules .

It's not mentioned in /etc/modules.

I also tried removing only vzaphfc or zaphfc and learned two more things:

1) After modifying zapata-channels.conf accordingly, no zap channels
will show up in either of these configurations, i.e. "pri show spans"
shows nothing.

2) If I start Asterisk by running "genzaptelconf -sd -c nl", the other
module will first get loaded, zapata-channels.conf will be restored to
its original state* and all the channels will once again be in use.

# cat zapata-channels.conf
; Autogenerated by /usr/sbin/genzaptelconf -- do not hand edit
; Zaptel Channels Configurations (zapata.conf)
;
; This is not intended to be a complete zapata.conf. Rather, it is intended
; to be #include-d by /etc/zapata.conf that will include the
global settings
;

; Span 1: ZTHFC1 "HFC-S PCI A Zaptel Driver card 0 [TE]" (MASTER)
group=0,11
context=from-pstn
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel => 1-2
group=
context=default

; Span 2: ZTHFC1 "HFC-S PCI A ISDN card 1 [TE]"
group=0,12
context=from-pstn
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel => 4-5
group=
context=default

This is what "genzaptelconf -sd -c nl" keeps producing, although it
doesn't look right.

genzaptelconf is used for detection. This is not something you should
run on each startup.

Where does it get the configuration wrong?

(And you don't have to #include that file into zapata.conf. You can put
whatever you want in your zapata.conf. That was the point of generatign
a file that is not zapata.conf)

What do you have in your zapata.conf? Can you post it here?
What is the output of:

asterisk -rx 'zap show chanels'
lszaptel

--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen at xorcom.com
+972-50-7952406 mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
Back to top
ron at wellsted.org.uk
Guest





PostPosted: Fri Jan 04, 2008 3:33 pm    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jaap Winius wrote:
Quote:

switchtype = euroisdn
signalling = bri_cpe_ptmp

I don't know about NL but in the UK, multiple ISDN2e lines have to be
configured as bri_cpe_ptp not bri_cpe_ptmp. Have you tried this mode?

HTH

- --
Ron Wellsted
ron at wellsted.org.uk http://www.wellsted.org.uk
N 52.567623, W 2.136111 Linux Counter No. 202120
Ekiga: 645022
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEVAwUBR36YHUtP/KMNOfRbAQJqBwf/b/lJbbF4EJo8f6ogj6td85YXL+V9uO1A
jrn2Ecqa2hKSa7C8VQcmKVaTROdRAqITPb3kYbXNOWXc5r25d87WmJNYrvuEtEPd
5JifulE+LrWiw1doXXNJXeIovSepmT7arUy3/25Sv640WlxRWk0CptkvQQCzRQ/A
Vv5BzHYOXD1uaieD8ir3A3QyI6qSoUeMABjOBfKfrNVPIIy50KnnVkLDGjZacQ6f
B5xp93LLrw3OPiGorij6QlWjEeK3IEtd+7wKnh+4jH0QeiWaUBlgL6MqdeNFZhNX
v471guV/Kj5i6Oo+0jpLJGwFPGk46NGS21ETiKwL2QSkaxMms5yHpw==
=nlcm
-----END PGP SIGNATURE-----
Back to top
michiel at vanbaak.info
Guest





PostPosted: Fri Jan 04, 2008 5:49 pm    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

On 20:33, Fri 04 Jan 08, Ron Wellsted wrote:
Quote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jaap Winius wrote:
Quote:

switchtype = euroisdn
signalling = bri_cpe_ptmp

I don't know about NL but in the UK, multiple ISDN2e lines have to be
configured as bri_cpe_ptp not bri_cpe_ptmp. Have you tried this mode?

It's the same here in .nl

--

Michiel van Baak
michiel at vanbaak.eu
http://michiel.vanbaak.eu
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x71C946BD

"Why is it drug addicts and computer afficionados are both called users?"
Back to top
jwinius at umrk.to
Guest





PostPosted: Fri Jan 04, 2008 7:18 pm    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

Quoting Michiel van Baak <michiel at vanbaak.info>:

Quote:
Quote:
I don't know about NL but in the UK, multiple ISDN2e lines have to be
configured as bri_cpe_ptp not bri_cpe_ptmp. Have you tried this mode?

It's the same here in .nl

Interesting, but I would think this to be unnecessary in my case,
since I have only one ISDN-BRI line. It's just that for some reason
the software keeps loading both the zaphfc and vzaphfc modules, which
makes it look like I have two lines. But even if I do configure the
system with " signalling = bri_cpe_ptp", it makes no difference: all
of the channels are still busy.

Thanks anyway, though.

Cheers,

Jaap
Back to top
tzafrir.cohen at xorco...
Guest





PostPosted: Fri Jan 04, 2008 7:27 pm    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

On Sat, Jan 05, 2008 at 01:18:18AM +0100, Jaap Winius wrote:
Quote:
Quoting Michiel van Baak <michiel at vanbaak.info>:

Quote:
Quote:
I don't know about NL but in the UK, multiple ISDN2e lines have to be
configured as bri_cpe_ptp not bri_cpe_ptmp. Have you tried this mode?

It's the same here in .nl

Interesting, but I would think this to be unnecessary in my case,
since I have only one ISDN-BRI line. It's just that for some reason
the software keeps loading both the zaphfc and vzaphfc modules, which
makes it look like I have two lines. But even if I do configure the
system with " signalling = bri_cpe_ptp", it makes no difference: all
of the channels are still busy.

signalling = bri_cpe

(if you set in /etc/default/zaptel: ZAPBRI_SIGNALLING="bri"
you'll get that from genzaptelconf.

Anyway, either you use zaphfc or vzaphfc. The first one that loads takes
everything.

What do you see on /proc/interrupts ?

Which of those two modules you can't unload when Asterisk is running?

--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen at xorcom.com
+972-50-7952406 mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
Back to top
asterisk-list at puzzl...
Guest





PostPosted: Sat Jan 05, 2008 10:27 am    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

On Sat, 2008-01-05 at 01:18 +0100, Jaap Winius wrote:
Quote:
Quoting Michiel van Baak <michiel at vanbaak.info>:

Quote:
Quote:
I don't know about NL but in the UK, multiple ISDN2e lines have to be
configured as bri_cpe_ptp not bri_cpe_ptmp. Have you tried this mode?

It's the same here in .nl

Interesting, but I would think this to be unnecessary in my case,
since I have only one ISDN-BRI line. It's just that for some reason
the software keeps loading both the zaphfc and vzaphfc modules

Why not remove or disable the module you don't need just to make sure it
is not interfering?

Regards,
Patrick
Back to top
jwinius at umrk.to
Guest





PostPosted: Mon Jan 07, 2008 7:26 am    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

Quoting Tzafrir Cohen <tzafrir.cohen at xorcom.com>:

Quote:
(if you set in /etc/default/zaptel: ZAPBRI_SIGNALLING="bri"
you'll get that from genzaptelconf.

If I create a file like this, I end up with "signalling=bri_cpe" instead of
"signalling=bri_cpe_ptmp".

Quote:
Anyway, either you use zaphfc or vzaphfc. The first one that loads takes
everything.

So far I have succeeded in starting up Asterisk without the zaphfc
module (if channels 4-5 aren't defined in zapata.conf), but not
without vzaphfc. Not having vzaphfc loaded always results in Asterisk
starting up without Zaptel support. However, whether I run it with or
without zaphfc, all of the available ISDN channels are always busy and
the CLI still frequently shows "Primary D-Channel on span 1 down"
messages.

Quote:
What do you see on /proc/interrupts ?

CPU0
0: 25025934 IO-APIC-edge timer
6: 3 IO-APIC-edge floppy
8: 1 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
15: 129 IO-APIC-edge ide1
169: 286747 IO-APIC-level skge
177: 1014894 IO-APIC-level libata
185: 0 IO-APIC-level uhci_hcd:usb1, uhci_hcd:usb2, ...
193: 114700219 IO-APIC-level vzaphfc, zaphfc
201: 0 IO-APIC-level via82cxxx
NMI: 0
LOC: 25024942
ERR: 0
MIS: 0

Quote:
Which of those two modules you can't unload when Asterisk is running?

If I declare all of the channels in zapata.conf, like this...

channel => 1-2
channel => 4-5

then neither of the modules can be unloaded while Asterisk is running.
If I comment out the first line then I can unload vzaphfc, while if I
comment out the second I can unload zaphfc, so I guess this is how the
channels are related to the modules. This makes sense, because when
the zaptel modules are loaded with "genzaptelconf -d" (-d = hardware
detection), vzaphfc is always loaded first.

Regarding "genzaptelconf -d", I've found that it is essential for me
to run this command first before starting Asterisk. If not, Asterisk
will start, but without Zaptel support. During system bootup, only the
zaptel van vzaphfc modules are loaded by the kernel, which is not
enough. Instead, genzaptelconf's hardware detection loads these
modules in the following order:

Module Size Used by
xpp 88512 0
zaphfc 12956 0
vzaphfc 24312 0
firmware_class 9600 0
zaptel 184740 3 xpp,zaphfc,vzaphfc

This works. However, if I try to load these modules manually in the
same order, Asterisk will start without Zaptel support. I don't know
yet how genzaptelconf accomplishes this, but I suspect that it passes
certain parameters to the zaptel and/or vzaphfc modules as it loads
them.

I say that because, after running "genzaptelconf -d", it's possible to
remove the xpp, zaphfc (if channels 4-5 are not declared) and
firmware_class modules before starting up Asterisk and still have
Zaptel support, although all of the Zaptel channels will still be
busy. Furthermore, it is therefore not my impression that zaphfc is
interfering with vzaphfc to cause all the zap channels to be busy.

FYI, my current /etc/asterisk/zapata.conf is as follows:

-----------------------------------------

[trunkgroups]

[channels]
language=en
context=isdn-in
switchtype=euroisdn
pridialplan=dynamic
prilocaldialplan=local
nationalprefix = 0
internationalprefix = 00
overlapdial=yes
signalling=bri_cpe_ptmp
rxwink=300
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=100
rxgain=4.5
txgain=-3
callgroup=1
pickupgroup=1
immediate=yes
group=1
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel => 1-2
channel => 4-5

-----------------------------------------

More information can be found in my previous posts in this thread.

By the way, I've now duplicated my results on a new system with a
different motherboard, a new HFC-S card and a fresh Debian etch
install, etc., but unfortunately the results were exactly the same:
all zap channels busy as soon as Asterisk starts.

If anybody has a working Asterisk v1.4 configuration for ISDN-BRI
using an HFC-S card and Zaptel software, I'd love to see it.

Thanks,

Jaap
Back to top
tzafrir.cohen at xorco...
Guest





PostPosted: Thu Jan 10, 2008 2:29 am    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

On Sat, Jan 05, 2008 at 04:27:25PM +0100, Patrick wrote:
Quote:

On Sat, 2008-01-05 at 01:18 +0100, Jaap Winius wrote:
Quote:
Quoting Michiel van Baak <michiel at vanbaak.info>:

Quote:
Quote:
I don't know about NL but in the UK, multiple ISDN2e lines have to be
configured as bri_cpe_ptp not bri_cpe_ptmp. Have you tried this mode?

It's the same here in .nl

Interesting, but I would think this to be unnecessary in my case,
since I have only one ISDN-BRI line. It's just that for some reason
the software keeps loading both the zaphfc and vzaphfc modules

Why not remove or disable the module you don't need just to make sure it
is not interfering?

To be more specific: I get the wierd impression that either both modules
somehow get interrupts from the two cards, or each module handles a
different card. This hsouldn't happen.

So try blacklisting one of them:

echo 'blacklist vzaphfc' >/etc/modprobe.d/blacklist_hfc

/etc/init.d/asterisk zaptel-fix

Or maybe blacklist zaphfc instead.

--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen at xorcom.com
+972-50-7952406 mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
Back to top
jwinius at umrk.to
Guest





PostPosted: Thu Jan 10, 2008 8:31 am    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

Quoting Tzafrir Cohen <tzafrir.cohen at xorcom.com>:

Quote:
... I get the wierd impression that either both modules somehow
get interrupts from the two cards, or each module handles a
different card. This hsouldn't happen.

So try blacklisting one of them:

I've already done something like that: removing the vzaphfc directory
from /lib/modules/2.6.18-5-k7/misc/, running depmod, and then
"genzaptelconf -sdc nl". The rest of the modules loaded fine, but
again all (3) channels were in use. Of course, I also tried putting
vzaphfc back and removing zaphfc instead, but the results were the same.

In both cases, I also tried running Asterisk with a minimal zapata.conf:

switchtype=euroisdn
signalling=bri_cpe_ptmp
channel=>1-2

Just for fun, I even tried this with "signalling=bri_cpe_ptp", but
then Asterisk starts without any Zaptel support.

I'm running out of options here. It looks to me like the current
versions of the software I'm using (Asterisk 1.4.14, Zaptel 1.4.7)
just don't include working support HFC-S PCI cards. Yet, I've read
that it has apparently worked in the past, so maybe I should try to
downgrade to Asterisk 1.2.13 and Zaptel 1.2.11 (the versions that come
with Debian stable).

Thanks,

Jaap
Back to top
tzafrir.cohen at xorco...
Guest





PostPosted: Thu Jan 10, 2008 9:01 am    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

On Thu, Jan 10, 2008 at 02:31:53PM +0100, Jaap Winius wrote:
Quote:
Quoting Tzafrir Cohen <tzafrir.cohen at xorcom.com>:

Quote:
... I get the wierd impression that either both modules somehow
get interrupts from the two cards, or each module handles a
different card. This hsouldn't happen.

So try blacklisting one of them:

I've already done something like that: removing the vzaphfc directory
from /lib/modules/2.6.18-5-k7/misc/, running depmod, and then
"genzaptelconf -sdc nl". The rest of the modules loaded fine, but
again all (3) channels were in use. Of course, I also tried putting
vzaphfc back and removing zaphfc instead, but the results were the same.

What do you mean by "In Use"?

When Asterisk runs, they are "(In use)" - by Asterisk.

Quote:

In both cases, I also tried running Asterisk with a minimal zapata.conf:

switchtype=euroisdn
signalling=bri_cpe_ptmp
channel=>1-2

Just for fun, I even tried this with "signalling=bri_cpe_ptp", but
then Asterisk starts without any Zaptel support.

It is:

signalling=bri_cpe

Quote:

I'm running out of options here. It looks to me like the current
versions of the software I'm using (Asterisk 1.4.14, Zaptel 1.4.7)
just don't include working support HFC-S PCI cards. Yet, I've read
that it has apparently worked in the past, so maybe I should try to
downgrade to Asterisk 1.2.13 and Zaptel 1.2.11 (the versions that come
with Debian stable).

Thanks,

Jaap

_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen at xorcom.com
+972-50-7952406 mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
Back to top
jwinius at umrk.to
Guest





PostPosted: Thu Jan 10, 2008 6:45 pm    Post subject: [asterisk-users] HFC-S zap channels always busy Reply with quote

Quoting Tzafrir Cohen <tzafrir.cohen at xorcom.com>:

Quote:
What do you mean by "In Use"?

# cat /proc/zaptel/*
Span 1: ZTHFC1 "HFC-S PCI A Zaptel Driver card 0 [TE]" (MASTER) AMI/CCS

1 ZTHFC1/0/1 Clear (In use)
2 ZTHFC1/0/2 Clear (In use)
3 ZTHFC1/0/3 HDLCFCS (In use)

Quote:
When Asterisk runs, they are "(In use)" - by Asterisk.

I would hope so. I do see:

# asterisk -rx 'pri show spans'
PRI span 1/0: Provisioned, Up, Active

and

# asterisk -rx 'zap show channels'
Chan Extension Context Language MOH Interpret
pseudo isdn-in en default
1 isdn-in en default
2 isdn-in en default

This is when I use the vzaphfc modules. However, any attempt to dial
out via ISDN results in errors like:

-- Executing [0654314647 at phones:1] Dial("SIP/1000-081f3220",
"Zap/g0/0654314647 at channels||r") in new stack
[Jan 11 00:12:15] WARNING[1354]: app_dial.c:1130 dial_exec_full:
Unable to create channel of type 'Zap' (cause 34 - Circuit/channel
congestion)
== Everyone is busy/congested at this time (1:0/1/0)
== Auto fallthrough, channel 'SIP/1000-081f3220' status is 'CONGESTION'
[Jan 11 00:12:15] NOTICE[1354]: cdr.c:434 ast_cdr_free: CDR on channel
'SIP/1000-081f3220' not posted

In this case, the rule that I use in extensions.conf for dialing out is:

exten => _X.,1,Dial(Zap/g0/${EXTEN}@channels,,r)

Quote:
signalling=bri_cpe

I've tried that, but unless I'm doing something else wrong
(hopefully), using "signalling=bri_cpe" instead of
"signalling=bri_cpe_ptmp" makes no difference.

Thanks,

Jaap
Back to top
Display posts from previous:   
Post new topic   Reply to topic    VoIP Mailing List Archives Forum Index -> Asterisk Users All times are GMT - 5 Hours
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group

VoiceMeUp - Corporate & Wholesale VoIP Services