[asterisk-r2] MFCR2 With Unicall - can unicall affect zaptel commands?
Juan Carlos Huerta
juancarloshuerta at gmail.com
Tue Apr 7 12:51:57 CDT 2009
And what is the result? still with zap commands problem?
Juan Carlos
~ Lo que no te mata te fortalece ~
On Tue, Apr 7, 2009 at 12:49 PM, Giovanny Magallanes
<gmagallanes at gmail.com> wrote:
> I did it:
>
> elastix*CLI> load chan_zap.so
> The 'load' command is deprecated and will be removed in a future release.
> Please use 'module load' instead.
> == 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
> -- Registered channel 67, FXO Kewlstart signalling
> -- Registered channel 68, FXO Kewlstart signalling
> -- Registered channel 68, FXO Kewlstart signalling
> -- Registered channel 69, FXO Kewlstart signalling
> -- Registered channel 70, FXO Kewlstart signalling
> -- Registered channel 71, FXO Kewlstart signalling
> -- Registered channel 72, FXO Kewlstart signalling
> -- Registered channel 73, FXO Kewlstart signalling
> -- Registered channel 74, FXO Kewlstart signalling
> -- Registered channel 75, FXO Kewlstart signalling
> -- Registered channel 76, FXO Kewlstart signalling
> -- Registered channel 77, FXO Kewlstart signalling
> -- Registered channel 78, FXO Kewlstart signalling
> elastix*CLI>
>
> Thank you Juan
>
> Giovanni
>
>
> 2009/4/7, Juan Carlos Huerta <juancarloshuerta at gmail.com>:
>>
>> Try to load the chan_zap.so module manually to see if you get some error.
>>
>> Juan Carlos
>> ~ Lo que no te mata te fortalece ~
>>
>>
>>
>> On Tue, Apr 7, 2009 at 12:44 PM, Giovanny Magallanes
>> <gmagallanes at gmail.com> wrote:
>> > I'm using Elastix 1.1-8 with:
>> >
>> > asterisk-1.4.19
>> > spandsp-0.0.4
>> > unicall-0.0.5pre1
>> > zaptel-1.4.9.2
>> > unicall-0.0.5pre1
>> > libmfcr2-0.0.3
>> > libsupertone-0.0.2
>> > libunicall-0.0.3
>> >
>> > Regards,
>> >
>> > Giovanni
>> >
>> > 2009/4/7, Giovanny Magallanes <gmagallanes at gmail.com>:
>> >>
>> >> Ok, Thanks. The chan_zap commands are unavailable, but unicall commands
>> >> and my E1 MFC/R2 are OK.
>> >>
>> >> Giovanni
>> >>
>> >>
>> >> 2009/4/7, Moises Silva <moises.silva at gmail.com>:
>> >>>
>> >>> I don't understand your problem. And no, unicall has nothing to do
>> >>> with chan_zap.so commands.
>> >>>
>> >>> Please, in the future, don't hijack threads, open a new thread for
>> >>> your discussion. This time I changed the subject already.
>> >>>
>> >>> Moy
>> >>>
>> >>> On Tue, Apr 7, 2009 at 1:08 AM, Giovanny Magallanes
>> >>> <gmagallanes at gmail.com> wrote:
>> >>> > 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
>> >>> >
>> >>> >
>> >>> > _______________________________________________
>> >>> > --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
>> >>> >
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> "I do not agree with what you have to say, but I’ll defend to the
>> >>> death your right to say it." Voltaire
>> >>>
>> >>> _______________________________________________
>> >>> --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
>> >
>> >
>> > _______________________________________________
>> > --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
>> >
>>
>> _______________________________________________
>> --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
>
>
> _______________________________________________
> --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
>
More information about the asterisk-r2
mailing list