# Zap channel issue **URL:** \ **Category:** Asterisk Support\ **Created:** [March 9, 2008, 5:41am UTC](https://community.asterisk.org/t/zap-channel-issue/19649 "2008-03-09T05:41:49Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![ddougan](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/ddougan/32/579_2.png) [@ddougan](https://community.asterisk.org/u/ddougan)\ **Post date:** [March 9, 2008, 5:41am UTC](https://community.asterisk.org/t/zap-channel-issue/19649/1 "2008-03-09T05:41:49Z")
I moved my Asterisk server, as well as my other boxes, to a new location. After I started the server, Asterisk came up and I see both channels (I have a TDM11B card, 1 inbound and 1 outbound channel); however, I am not getting dialtone on the phone connected to the card. It was working fine prior to the move. If I dial in, Zap says the line is ringing, and it will then go to voicemail, but without anything happening on the handset. Can anyone shed any light on what might be happening here? Thanks, Des ---
**Author:** ![afried](https://avatars.discourse-cdn.com/v4/letter/a/7bcc69/32.png) [@afried](https://community.asterisk.org/u/afried)\ **Post date:** [March 10, 2008, 3:35am UTC](https://community.asterisk.org/t/zap-channel-issue/19649/2 "2008-03-10T03:35:44Z")
I’m having “issues” with my TDM400P card as well. I’m running zaptel 1.4.9.2 and asterisk 1.4.18. I can receive inbound calls on the port, but when outgoing calls are made I receive the following error: WARNING[6639]: chan\_zap.c:3835 zt\_handle\_event: Detected alarm on channel 3: No Alarm I’ve rebuilt everything, same problem. ---
**Author:** ![ManChicken](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@ManChicken](https://community.asterisk.org/u/ManChicken)\ **Post date:** [March 10, 2008, 10:03pm UTC](https://community.asterisk.org/t/zap-channel-issue/19649/3 "2008-03-10T22:03:16Z")
I updated to Zaptel 1.4.9.2 and Asterisk 1.4.18 this weekend and am now seeing the same thing; usually when a call hangs up: ` [Mar 10 16:01:41] WARNING[23790]: chan_zap.c:6685 handle_init_event: Detected alarm on channel 1: No Alarm [Mar 10 16:01:42] NOTICE[23790]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 1` TDM800P The system is otherwise behaving normally, everything seems to be working (I have 4 FXO ports and 1 FXS; The local phones are all VoIP phones). ---
**Author:** ![bwilks](https://avatars.discourse-cdn.com/v4/letter/b/e274bd/32.png) [@bwilks](https://community.asterisk.org/u/bwilks)\ **Post date:** [March 11, 2008, 11:00am UTC](https://community.asterisk.org/t/zap-channel-issue/19649/4 "2008-03-11T11:00:05Z")
Hi, I see you are running recent releases have you looked at [bugs.digium.com](http://bugs.digium.com) or read the change log? ddougan Could you have changed a conf before you shut the Asterisk box down? ---
**Author:** ![dufus](https://avatars.discourse-cdn.com/v4/letter/d/c77e96/32.png) [@dufus](https://community.asterisk.org/u/dufus)\ **Post date:** [March 11, 2008, 12:26pm UTC](https://community.asterisk.org/t/zap-channel-issue/19649/5 "2008-03-11T12:26:19Z")
Since you moved the box, I’d guess this might be something either in the wiring, or the card itself. First off, make sure you’re plugged into the correct port on the card. Second, try a different line cord to the analog phone. Third, check the daughter card on the board. Perhaps it came loose in the move. Fourth, check the power cable to the card. Perhaps it came loose in the move. Problems like this are usually not software related. ---
**Author:** ![christsis](https://avatars.discourse-cdn.com/v4/letter/c/f07891/32.png) [@christsis](https://community.asterisk.org/u/christsis)\ **Post date:** [March 11, 2008, 6:46pm UTC](https://community.asterisk.org/t/zap-channel-issue/19649/6 "2008-03-11T18:46:36Z")
I’m going to add a “me too” on this. I just setup a new box with a TDM800P with 2 quad FXO and the echo cancel on it. I’ve tried multiple cables, different ports, etc. This is definately an odd software issue as I can single out the ports in various ways and it dials properly. I’ve seen other postings saying this is something that started with zaptel 1.4.8. I was going to try downgrading and see what happens. ---
**Author:** ![ManChicken](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@ManChicken](https://community.asterisk.org/u/ManChicken)\ **Post date:** [March 11, 2008, 8:17pm UTC](https://community.asterisk.org/t/zap-channel-issue/19649/7 "2008-03-11T20:17:51Z")
> [@christsis](#): > > This is definately an odd software issue as I can single out the ports in various ways and it dials properly. I’ve seen other postings saying this is something that started with zaptel 1.4.8. I was going to try downgrading and see what happens. Could be; I was running zaptel-1.4.7.1 prior to upgrading to 1.4.9.2 and everything was fine (although again for me, so far, I have not been having problems making/receiving calls, just getting the errors in the console I pasted in my previous reply.) I upgraded to 1.4.9.2 because I’d read about the enhancements in the changelogs to fxotune but I might downgrade until something definitive is determined on this issue - while my system is working for now who knows what little ‘isms’ could be occurring I’m not aware of. ---
**Author:** ![christsis](https://avatars.discourse-cdn.com/v4/letter/c/f07891/32.png) [@christsis](https://community.asterisk.org/u/christsis)\ **Post date:** [March 11, 2008, 8:49pm UTC](https://community.asterisk.org/t/zap-channel-issue/19649/8 "2008-03-11T20:49:01Z")
I backed off to 1.4.7.1 and even tried the latest SVN. I’m still getting the same results. Definately something weird going on with the zaptel drivers now. ---
**Author:** ![ManChicken](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@ManChicken](https://community.asterisk.org/u/ManChicken)\ **Post date:** [March 12, 2008, 4:03pm UTC](https://community.asterisk.org/t/zap-channel-issue/19649/9 "2008-03-12T16:03:21Z")
Wait-- you’re still getting the alarms when you downgraded to 1.4.7.1? ---
**Author:** ![christsis](https://avatars.discourse-cdn.com/v4/letter/c/f07891/32.png) [@christsis](https://community.asterisk.org/u/christsis)\ **Post date:** [March 12, 2008, 5:11pm UTC](https://community.asterisk.org/t/zap-channel-issue/19649/10 "2008-03-12T17:11:42Z")
Yes, mine’s a little different I’m getting the alarm on 2 specific lines dialing out. But it’s still the exact same zaptel error. I’ve tried 1.4.7.1, I’ve tried latest svn, I’ve tried the special battery\_alarm branch from the SVN. I can’t seem to figure out what’s going on. Since it’s new digium hardware I think I’ll just try putting in a support ticket and see if they’ll help. ---
**Author:** ![ManChicken](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@ManChicken](https://community.asterisk.org/u/ManChicken)\ **Post date:** [March 12, 2008, 5:14pm UTC](https://community.asterisk.org/t/zap-channel-issue/19649/11 "2008-03-12T17:14:56Z")
Ah. Yeah sounds like something could be awry with your hardware if it’s been doing this all along - I was under the impression you were just now getting these errors after upgrading zaptel from a previously working install (which is my particular issue). I downgraded last night back to zaptel 1.4.7.1 and my ‘no alarm’ alarms have gone away. And I compared my fxotune values from the old version to the new one and they were the same, so I guess it’s no big loss for now 😄 ---
**Author:** ![afried](https://avatars.discourse-cdn.com/v4/letter/a/7bcc69/32.png) [@afried](https://community.asterisk.org/u/afried)\ **Post date:** [March 18, 2008, 3:50am UTC](https://community.asterisk.org/t/zap-channel-issue/19649/12 "2008-03-18T03:50:36Z")
I finally reverted back to zaptel 1.4.7.1 and the alarm errors went away. I’m now able to dial OUT on the TDM card - before downgrading, I could receive calls but not place them. ---
**Author:** ![alicat](https://avatars.discourse-cdn.com/v4/letter/a/a5b964/32.png) [@alicat](https://community.asterisk.org/u/alicat)\ **Post date:** [March 21, 2008, 3:06am UTC](https://community.asterisk.org/t/zap-channel-issue/19649/13 "2008-03-21T03:06:39Z")
I am having the same problem also. Clean install of AsteriskNow 1.0.2 gives me this… ```auto -- Executing [91234567@numberplan-custom-1:1] Macro("SIP/26-081f82c8", "trunkdial|Zap/g1/w1234567|asreceived") in new stack -- Executing [s@macro-trunkdial:1] Set("SIP/26-081f82c8", "CALLERID(all)=asreceived") in new stack -- Executing [s@macro-trunkdial:2] Dial("SIP/26-081f82c8", "Zap/g1/w1234567") in new stack -- Called g1/w1234567 [Mar 20 20:09:16] WARNING[3688]: chan_zap.c:3835 zt_handle_event: Detected alarm on channel 3: No Alarm -- Hungup 'Zap/3-1' == Everyone is busy/congested at this time (1:0/0/1) -- Executing [s@macro-trunkdial:3] Goto("SIP/26-081f82c8", "s-CHANUNAVAIL|1") in new stack -- Goto (macro-trunkdial,s-CHANUNAVAIL,1) -- Executing [s-CHANUNAVAIL@macro-trunkdial:1] NoOp("SIP/26-081f82c8", "") in new stack == Auto fallthrough, channel 'SIP/26-081f82c8' status is 'CHANUNAVAIL' [Mar 20 20:09:16] NOTICE[3510]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 3 ``` anybody have a solution? ---
**Author:** ![alicat](https://avatars.discourse-cdn.com/v4/letter/a/a5b964/32.png) [@alicat](https://community.asterisk.org/u/alicat)\ **Post date:** [March 21, 2008, 3:07am UTC](https://community.asterisk.org/t/zap-channel-issue/19649/14 "2008-03-21T03:07:52Z")
-duplicate post- ---
**Author:** ![christsis](https://avatars.discourse-cdn.com/v4/letter/c/f07891/32.png) [@christsis](https://community.asterisk.org/u/christsis)\ **Post date:** [March 24, 2008, 7:20pm UTC](https://community.asterisk.org/t/zap-channel-issue/19649/15 "2008-03-24T19:20:49Z")
I actually backed off to 1.4.7.1 but had to recompile asterisk as well after installing the older version. After that I was able to dial out all channels. So clearly something after 1.4.7.1 has had a serious impact on it. I have not tried to use the zaptel SVN and then recompile Asterisk as well to see if that functions. ---
**Author:** ![jafo8](https://avatars.discourse-cdn.com/v4/letter/j/bc79bd/32.png) [@jafo8](https://community.asterisk.org/u/jafo8)\ **Post date:** [April 1, 2008, 2:23am UTC](https://community.asterisk.org/t/zap-channel-issue/19649/16 "2008-04-01T02:23:56Z")
I was able to resolve this by adding ```auto ``` to the /etc/modprobe.conf file. I am currently running asterisk on an Centos5.1 (rhel5.1) box with rpms from [http://atrpms.net/dist/el5/](http://atrpms.net/dist/el5/) asterisk-1.4.18 zaptel-1.4.9.2 My hardware: TDM422B Wildcard TDM400P REV I Board 1 1 WCTDM/0/0 FXOKS 2 WCTDM/0/1 FXOKS 3 WCTDM/0/2 FXSKS 4 WCTDM/0/3 FXSKS My symptoms were calls being dropped. Regardless of incoming or outgoing. ---
**Author:** ![jafo8](https://avatars.discourse-cdn.com/v4/letter/j/bc79bd/32.png) [@jafo8](https://community.asterisk.org/u/jafo8)\ **Post date:** [April 1, 2008, 2:24am UTC](https://community.asterisk.org/t/zap-channel-issue/19649/17 "2008-04-01T02:24:36Z")
I was able to resolve this by adding ```auto ``` to the /etc/modprobe.conf file. I am currently running asterisk on an Centos5.1 (rhel5.1) box with rpms from [http://atrpms.net/dist/el5/](http://atrpms.net/dist/el5/) asterisk-1.4.18 zaptel-1.4.9.2 My hardware: TDM422B Wildcard TDM400P REV I Board 1 1 WCTDM/0/0 FXOKS 2 WCTDM/0/1 FXOKS 3 WCTDM/0/2 FXSKS 4 WCTDM/0/3 FXSKS My symptoms were calls being dropped. Regardless of incoming or outgoing. I hope this helps someone else.