Topic: Unable to create 'Zap' Channel

[David Harper]

I am trying to configure a Digium TDM410P with the following components:

zaptel-1.4.12.1-54.99.el4
zaptel-kmdl-2.6.9-78.0.8.ELsmp-1.4.12.1-54.99.el4
asterisk-1.4.23.1-72.el4
asterisk-addons-1.4.7-21.el4
libpri-1.4.9-22.el4
sail-2.2.1-688

Internal calls work, provisioning works, but unfortunately attempting to call externally does not:

Code: [Select]

-- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script Executing Application: (NoOp) Options: (test-group)
    -- AGI Script Executing Application: (NoOp) Options: (Found-group)
    -- AGI Script Executing Application: (Dial) Options: (Zap/g2/8421550063)
[Feb  8 23:03:49] WARNING[7520]: app_dial.c:1286 dial_exec_full: Unable to create channel of type 'Zap' (cause 0 - Unknown)
  == Everyone is busy/congested at this time (1:0/0/1)
    -- AGI Script Executing Application: (Playback) Options: (beep)
    -- <SIP/5000-b761d628> Playing 'beep' (language 'en')
    -- AGI Script Executing Application: (NoOp) Options: (test-group)
    -- AGI Script Executing Application: (NoOp) Options: (test-group)
    -- AGI Script Executing Application: (Background) Options: (were-sorry)
    -- <SIP/5000-b761d628> Playing 'were-sorry' (language 'en'

I got this far by enabling the dahdi compatibility option. Previously we had a Cause 66 error.

[David Harper]

Jeff, will updating to 715 fix this?

[SARK devs]

AS far as we know it isn't broken.

What does zap show channels or zap show status give you?

Best

S

[David Harper]

Thanks for the response.

zap show channels shows the pseudo channel only.

When I ran ztcfg -v, it said there were 3 channels to configure, so I ran perl /etc/selintra/selautosniff. It then detects & configures the TDM card's three FXO channels, but as far as I can tell only pseudo shows up in Asterisk.

[SARK devs]

selautosniff was obsoleted in 2.1.12 - it is only there as a legacy item.  It won't function correctly in 2.2.

Instead, you should use the PCI cards panel in the server-manager to configure your card layout.

The installation guide quicknotes (http://aelintra.com/docs/cgi-bin/view/Main/DocChapter03b) will show you the correct procedure in the section entitled PCI Setup.  Firstly though, you should go to PCI cards panel and do an Initialise to clean out any decisions made by autosniff.  If the initialise button is not exposed then you
should continue as decribed in the guide.

S

[ldkeen]

Yeah, I've got the same problem here. Couldn't get the TDM card going for love nor money under asterisk 1.4.23 (from ATRPMS). "zap show channels" gives me:
No DAHDI interface found
Unable to open /dev/dahdi/ctl: No such file or directory
I ended up dropping back to asterisk 1.4.21 and it came straight up. Would "dahdichanname=no" in asterisk.conf fix the problem do you think? I'm not sure where to look. I thought about installing Dahdi but ATRPMS doesn't have the correct kernel module.
Lloyd

[David Harper]

Yeah, I've got the same problem here. Couldn't get the TDM card going for love nor money under asterisk 1.4.23 (from ATRPMS). "zap show channels" gives me:
No DAHDI interface found
Unable to open /dev/dahdi/ctl: No such file or directory

Exactly what I got!

I ended up dropping back to asterisk 1.4.21 and it came straight up.

Where did you get this RPM package from?

Would "dahdichanname=no" in asterisk.conf fix the problem do you think? I'm not sure where to look.

No, I tried this and the Error 66 became Error 0 (unknown).

I thought about installing Dahdi but ATRPMS doesn't have the correct kernel module.

SAIL does not support the Dahdi configuration files anyway -- this wouldn't work.

[ldkeen]

Where did you get this RPM package from?

I got it from my yum cache but if you'd like a copy I've dumped it on the webserver for you: comnetel.com/asterisk-1.4.21.1-65.el4.i386.rpm

SAIL does not support the Dahdi configuration files anyway -- this wouldn't work.

I suspected that might be the case and was the main reason for dropping back to 1.4.21.
Regards, Lloyd

[David Harper]

FANTASTIC! Thanks for this. I have uploaded a bunch of useful RPMS (most of them already mirrored by Selintra at http://sarkpbx.com/sail/) on my website - http://sme.david-harper.com/data/sark/

Much appreciated.

Selintra, I think for the time being you will need to mirror all of the necessary components yourself, rather than rely on atrpms. Until SAIL supports Dahdi, and until SME upgrades to a newer kernel release (2.6.9-68.0.13 at a minimum), atrpms is pretty much useless except for asterisk-addons and sounds etc. The core stuff is now all incompatible with either SME and/or SAIL.

[SARK devs]

http://forums.contribs.org/index.php/topic,43196.0.html

[David Harper]

Asterisk as well

[SARK devs]

Asterisk is not zap or kernel release dependant (at least at the point release level).
In any event we just don't have the bandwidth to host large download files on our FTP site.


Best

S

[David Harper]

The version in atrpms is incompatible with SAIL, as it breaks Zaptel.

[David Harper]

Ok, have downgraded Asterisk to the RPM provided above. Reprobed the card from the web interface; restarted Asterisk with:

Code: [Select]

/etc/init.d/sark stop
/etc/init.d/sark start

zap show channels now correctly displays all 3 available channels, rather than just pseudo. Will test actual calling in a few hours when I am physically at the office.

[David Harper]

Okay, that works.

Selintra: I can confirm that the ATRPMS version of Asterisk breaks Zaptel. Until you update SAIL for DAHDI, only the previous 1.4.21.1-65 version will work with TDM cards.

ldkeen: I owe you a drink! Do you live in Sydney? EDIT: I see from your profile that you are -- give me a call (contact details).

[SARK devs]

I can confirm that the ATRPMS version of Asterisk breaks Zaptel.

Well, yes & no.  We have Asterisk 1.4.22 running quite happily with Dahdi/zaptel on one of our machines here.  However, we did have to make a few changes.  so...  for a very short period (and we mean very short) you can pull the 1.4.21 rpms from here...

http://sarkpbx.com/sail/kmdls/asterisk-1.4.21-Kernel-2.6.9-78.0.8

Now, we really are quite limited on bandwidth so down't download this stuff 'just because you can'.  If it gets overloaded we will just shut it down.  If you have some spare bandwidth then by all means grab the lot and post on here where people can download from.

-715 will be the last planned zaptel release of sail (there may be a few bugfixes, but that's all).  We have loosely scheduled -720 as the first DAHDI release.  It will run with 2.6.9-78.0.13 kernel (which you can yum update to now - although you may get shouted at by the SME elders - we don't know what the official update line is).  The SARK .iso will be zaptel/asterisk 1.4.21 as planned.

S







 

[David Harper]

so...  for a very short period (and we mean very short) you can pull the 1.4.21 rpms from here...

http://sarkpbx.com/sail/kmdls/asterisk-1.4.21-Kernel-2.6.9-78.0.8

Thanks Selintra. I will mirror these later today on my website. I have 2.5TB of transfer per month, so there is plenty of spare bandwidth

-715 will be the last planned zaptel release of sail (there may be a few bugfixes, but that's all).

Okay, that sounds reasonable

We have loosely scheduled -720 as the first DAHDI release.  It will run with 2.6.9-78.0.13 kernel (which you can yum update to now - although you may get shouted at by the SME elders - we don't know what the official update line is).

This kernel is already in smeupdates-testing, so it's not a huge issue to upgrade.

The SARK .iso will be zaptel/asterisk 1.4.21 as planned.

Fantastic. Thanks for all your work on this Selintra. I realise that there are a wide variety of things outside your control (Digium, ATrpms), so putting all this together must be quite a nightmare at times.

[David Harper]

Okay, all of the necessary RPMs except SAIL itself are now online at http://sme.david-harper.com/data/sark/ for your convenience.

[SARK devs]

Thank you - it's very much appreciated.

Please let us know if you have to close it down for any reason.

S