<div>Hi, Guys.</div>
<div> </div>
<div>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.</div>
<div> </div>
<div>[root@elastix asterisk]# find -P / -name chan_zap.so<br>/usr/lib/asterisk/modules/chan_zap.so<br>/usr/src/astunicall-1.4.19-0.1/asterisk-1.4.19/channels/chan_zap.so<br>[root@elastix asterisk]#<br>elastix*CLI> load chan_zap.so<br>
== Parsing '/etc/asterisk/zapata.conf': Found<br> == Parsing '/etc/asterisk/zapata_additional.conf': Found<br> == Parsing '/etc/asterisk/zapata-channels.conf': Found<br> -- Registered channel 63, FXO Kewlstart signalling<br>
-- Registered channel 64, FXO Kewlstart signalling<br> -- Registered channel 65, FXO Kewlstart signalling<br> -- Registered channel 66, FXO Kewlstart signalling<br> </div>
<div> </div>
<div>Can unicall affect zaptel commands in asterisk??</div>
<div> </div>
<div>Thanks</div>
<div> </div>
<div>Giovanni Magallanes </div>
<div> <br><br> </div>
<div><span class="gmail_quote">2009/4/6, Fernando Berretta <<a href="mailto:fernando.berretta@gmail.com">fernando.berretta@gmail.com</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>I've installed Asterisk 1.4 and Openr2 1.1 all is working well. I've<br>connected a crossover cable to TE122 board and board lite has went<br>
green. But when I've tried to make a call, I've got the following trace:<br><br>[15:35:00:218] [Thread: 3078437776] [Chan 1] - Call started at Mon Apr<br>6 15:35:00 2009 on chan 1<br>[15:35:00:218] [Thread: 3078437776] [Chan 1] - CAS Tx >> [SEIZE] 0x00<br>
[15:35:00:218] [Thread: 3078437776] [Chan 1] - CAS Raw Tx >> 0x01<br>[15:35:00:242] [Thread: 3078437776] [Chan 1] - Bits changed from 0x08 to<br>0x00<br>[15:35:00:242] [Thread: 3078437776] [Chan 1] - CAS Rx << [FORCED<br>
RELEASE] 0x00<br>[15:35:00:242] [Thread: 3078437776] [Chan 1] - Disconnection before<br>seize ack detected![15:35:00:242] [Thread: 3078437776] [Chan 1] - Far<br>end disconnected. Reason: Forced Release<br>[15:35:00:245] [Thread: 3078437776] [Chan 1] - Attempting to cancel<br>
timer timer 0<br>[15:35:00:245] [Thread: 3078437776] [Chan 1] - Cannot cancel timer 0<br>[15:35:00:245] [Thread: 3078437776] [Chan 1] - CAS Tx >> [CLEAR FORWARD]<br>0x08<br>[15:35:00:245] [Thread: 3078437776] [Chan 1] - CAS Raw Tx >> 0x09<br>
[15:35:00:306] [Thread: 3081632656] [Chan 1] - Bits changed from 0x00 to<br>0x08<br>[15:35:00:306] [Thread: 3081632656] [Chan 1] - CAS Rx << [IDLE] 0x08<br>[15:35:00:306] [Thread: 3081632656] [Chan 1] - Call ended<br>
[15:35:00:306] [Thread: 3081632656] [Chan 1] - Attempting to cancel<br>timer timer 0<br>[15:35:00:306] [Thread: 3081632656] [Chan 1] - Cannot cancel timer 0<br><br>Is there some way to complete a call through crossover cable with R2 ?<br>
How should I configure dahdi ?<br><br>Best Regards,<br>Fernando<br><br>_______________________________________________<br>--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--">http://www.api-digital.com--</a><br>
<br>asterisk-r2 mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-r2">http://lists.digium.com/mailman/listinfo/asterisk-r2</a><br></blockquote></div><br>