[asterisk-r2] Fwd: Unicall and zaptel commands

[Giovanny Magallanes]

This is one part of /var/log/asterisk/full.

[Apr  7 00:47:18] VERBOSE[22420] logger.c:     -- Executing [s at macro-dial:7]
Dial("SIP/400-b7c066e0", "ZAP/64||tr") in new stack
[Apr  7 00:47:18] WARNING[22420] channel.c: No channel type registered for
'ZAP'
[Apr  7 00:47:18] WARNING[22420] app_dial.c: Unable to create channel of
type 'ZAP' (cause 66 - Channel not implemented)
[Apr  7 00:47:18] VERBOSE[22420] logger.c:   == Everyone is busy/congested
at this time (1:0/0/1)
[Apr  7 00:47:18] DEBUG[22420] app_macro.c: Executed application: Dial

regards


---------- Forwarded message ----------
From: Giovanny Magallanes <gmagallanes at gmail.com>
Date: 07-abr-2009 0:08
Subject: Re: [asterisk-r2] Unicall and zaptel commands
To: asterisk-r2 at lists.digium.com


Hi, Guys.

I did not type any zaptel commands in asterisk console. I have installed
Elastix 1.1-8 with unicall and it is working fine with a Digium TE212-P.

[root at elastix asterisk]# find -P / -name chan_zap.so
/usr/lib/asterisk/modules/chan_zap.so
/usr/src/astunicall-1.4.19-0.1/asterisk-1.4.19/channels/chan_zap.so
[root at elastix asterisk]#
elastix*CLI> load chan_zap.so
  == Parsing '/etc/asterisk/zapata.conf': Found
  == Parsing '/etc/asterisk/zapata_additional.conf': Found
  == Parsing '/etc/asterisk/zapata-channels.conf': Found
    -- Registered channel 63, FXO Kewlstart signalling
    -- Registered channel 64, FXO Kewlstart signalling
    -- Registered channel 65, FXO Kewlstart signalling
    -- Registered channel 66, FXO Kewlstart signalling

* *
*Can unicall affect zaptel commands in asterisk??*

Thanks

Giovanni Magallanes



2009/4/6, Fernando Berretta <fernando.berretta at gmail.com>:
>
> Hi,
>
> I've installed Asterisk 1.4 and Openr2 1.1 all is working well. I've
> connected a crossover cable to TE122 board and board lite has went
> green. But when I've  tried to make a call, I've got the following trace:
>
> [15:35:00:218] [Thread: 3078437776] [Chan 1] - Call started at Mon Apr
> 6 15:35:00 2009 on chan 1
> [15:35:00:218] [Thread: 3078437776] [Chan 1] - CAS Tx >> [SEIZE] 0x00
> [15:35:00:218] [Thread: 3078437776] [Chan 1] - CAS Raw Tx >> 0x01
> [15:35:00:242] [Thread: 3078437776] [Chan 1] - Bits changed from 0x08 to
> 0x00
> [15:35:00:242] [Thread: 3078437776] [Chan 1] - CAS Rx << [FORCED
> RELEASE] 0x00
> [15:35:00:242] [Thread: 3078437776] [Chan 1] - Disconnection before
> seize ack detected![15:35:00:242] [Thread: 3078437776] [Chan 1] - Far
> end disconnected. Reason: Forced Release
> [15:35:00:245] [Thread: 3078437776] [Chan 1] - Attempting to cancel
> timer timer 0
> [15:35:00:245] [Thread: 3078437776] [Chan 1] - Cannot cancel timer 0
> [15:35:00:245] [Thread: 3078437776] [Chan 1] - CAS Tx >> [CLEAR FORWARD]
> 0x08
> [15:35:00:245] [Thread: 3078437776] [Chan 1] - CAS Raw Tx >> 0x09
> [15:35:00:306] [Thread: 3081632656] [Chan 1] - Bits changed from 0x00 to
> 0x08
> [15:35:00:306] [Thread: 3081632656] [Chan 1] - CAS Rx << [IDLE] 0x08
> [15:35:00:306] [Thread: 3081632656] [Chan 1] - Call ended
> [15:35:00:306] [Thread: 3081632656] [Chan 1] - Attempting to cancel
> timer timer 0
> [15:35:00:306] [Thread: 3081632656] [Chan 1] - Cannot cancel timer 0
>
> Is there some way to complete a call through crossover cable with R2 ?
> How should I configure dahdi ?
>
> Best Regards,
> Fernando
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20090407/a7873fb1/attachment.htm