[asterisk-users] Zaptel problems on SUSE 9.3

[Angus Asterisk]

Core show channeltypes:
SIP         Session Initiation Protocol (SIP)        yes          yes
yes
Console     OSS Console Channel Driver               no           yes
no
OOH323      Objective Systems H323 Channel Driver    no           yes
no
Skinny      Skinny Client Control Protocol (Skinny)  no           yes
no
Phone       Standard Linux Telephony API Driver      no           yes
no
Agent       Call Agent Proxy Channel                 yes          yes
no
IAX2        Inter Asterisk eXchange Driver (Ver 2)   yes          yes
yes
Local       Local Proxy Channel Driver               yes          yes
no
MGCP        Media Gateway Control Protocol (MGCP)    yes          yes
no
----------LI>
9 channel drivers registered.

Which one in above signifies the Zaptel channel?

asterisk:~ # cat /proc/zaptel/*
Span 1: WCTDM/0 "Wildcard TDM400P REV I Board 1" (MASTER)

           1 WCTDM/0/0 RED
           2 WCTDM/0/1 RED
           3 WCTDM/0/2 RED
           4 WCTDM/0/3 RED


lspci:
0000:00:14.0 Communication controller: Tiger Jet Network Inc. Tiger3XX
Modem/ISDN interface

I fiddled an it is working now - all green lights on on board.

It seems that the zaptel startup script does not work.  I noticed at startup
the line:
/etc/init.d/zaptel: line 40: /etc/init.d/functions: No such file or
directory

Line 40:
# Source function library.
if [ $system = redhat ]; then
    . $initdir/functions || exit 0
Fi

The . %initdir... is line 40.

Any ideas how to fix this file on suse?

I think if I can fix this everything should be ok.

Angus


Could the system be confusing the Zaptel device for Tiger Jet?  Ie loading
wrong driver?





-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Tzafrir Cohen
Sent: 04 October 2009 22:47
To: asterisk-users at lists.digium.com
Subject: Re: [asterisk-users] Zaptel problems on SUSE 9.3

On Sun, Oct 04, 2009 at 11:28:23AM +0100, Angus Asterisk wrote:
> Hi
> 
>  
> 
> My asterisk output is:
> 
> chan_sip.so => (Session Initiation Protocol (SIP))
> Asterisk Ready.
>     -- Registered SIP '201' at 192.168.0.55 port 33906
>     -- Saved useragent "X-Lite release 1011s stamp 41150" for peer 201
>     -- Executing [907768385144 at default:1] Dial("SIP/201-083e75c0",
> "ZAP/g1/907768385144|60") in new stack
> [Oct  4 11:54:27] WARNING[6255]: channel.c:3388 ast_request: No channel
type
> registered for 'ZAP'

Looks like chan_zap failed to load or something similar.

What is the output of: (in Asterisk)

  core show channeltypes

(In Linux)

  cat /proc/zaptel/*

> [Oct  4 11:54:27] WARNING[6255]: app_dial.c:1275 dial_exec_full: Unable to
> create channel of type 'ZAP' (cause 66 - Channel not implemented)
>   == Everyone is busy/congested at this time (1:0/0/1)
>     -- Executing [907768385144 at default:2] Hangup("SIP/201-083e75c0", "")
in
> new stack
>   == Spawn extension (default, 907768385144, 2) exited non-zero on
> 'SIP/201-083e75c0'
> 
>  
> 
> when I make a call from a sip device to my outbound analog trunk using a
> Digium TDM card.
> 
>  
> 
> My /etc/zaptel.conf file:
> 
> loadzone=uk
> 
> defaultzone=uk
> 
> fxsks=1-4
> 
>  
> 
> I am in the uk by the way.
> 
>  
> 
> Relevant part of /etc/astersk/zapata.conf:
> 
> signalling=v23   ; added for UK CLI detection
> 
> cidstart=polarity   ; added for UK CLI detection
> 
> context=frompstnanalog
> 
> group=1
> 
> callgroup=1
> 
> pickupgroup=1
> 
> signalling=fxs_ks
> 
> channel=>1-4
> 
>  
> 
> part of extensions.conf:
> 
> exten => _X.,1,Dial(ZAP/g1/${EXTEN},60)
> 
> exten => _X.,2,Hangup
> 
>  
> 
> I am running suse 9.3 on via and read article regarding old version of
> zaptel driver and fixed as per script -
> http://www.voip-info.org/wiki/view/Asterisk+Linux+SuSE
> 
>  
> 
> So now running dmesg reveals:
> 
> zaptel: unsupported module, tainting kernel.
> 
> Zapata Telephony Interface Registered on major 196
> 
> Zaptel Version: 1.4.12.1
> 
> Zaptel Echo Canceller: MG2

Have you actually loaded the module wctdm ?

> 
>  
> 
> So that looks encouraging
> 
>  
> 
> But still getting problem dialing out.
> 
>  
> 
> Also quite worrying is that there are no lights on the Digium card.
> 
>  
> 
> This used to work on same box and same operating system.  I just can't
> remember how I got it to work last time.
> 
>  
> 
> Anyone have any suggestions?

-- 
               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

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

AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net

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