<DIV>Dear Steve, I thank you for your extensive support on R2 so far.</DIV>
<DIV> </DIV>
<DIV>I am implementing it for Brazil, while I remotely do so. It seems from the list, Daniel Bichara on Fri Oct 1 09:30:29 CDT 2004 and recent Leonardo Gomes Figueira on Fri, 19 Nov 2004 12:28:18 -0200 seem to have succeeded in implementation itself, though having another trouble each. Also I noted your comments about Brazil's auto collect-call.<BR></DIV>
<DIV> </DIV>
<DIV>
<DIV>Here is a verbose log of asterisk when startup, among which I extracted part of unicall-related:</DIV>
<DIV> </DIV>
<DIV> [chan_unicall.so] => (Unified call processing (UniCall))<BR> == Parsing '/etc/asterisk/unicall.conf': Found<BR>Loading protocol mfcr2<BR>Nov 26 17:20:23 WARNING[16384]: chan_unicall.c:634 unicall_error: UniCall: mfcr2 mfcr2_Unblock()<BR>Nov 26 17:20:23 WARNING[16384]: chan_unicall.c:634 unicall_error: UniCall: mfcr2 Tx bits 0x9 [1/40000000/ 0/ 0]<BR> -- Registered channel 1, mfcr2 signalling</DIV>
<DIV> </DIV>
<DIV> [snipping]</DIV>
<DIV> </DIV>
<DIV>Nov 26 17:20:23 WARNING[16384]: chan_unicall.c:634 unicall_error: UniCall: mfcr2 mfcr2_Unblock()<BR>Nov 26 17:20:23 WARNING[16384]: chan_unicall.c:634 unicall_error: UniCall: mfcr2 Tx bits 0x9 [1/40000000/ 0/ 0]<BR> -- Registered channel 15, mfcr2 signalling<BR>Nov 26 17:20:23 WARNING[16384]: chan_unicall.c:634 unicall_error: UniCall: mfcr2 mfcr2_Unblock()<BR>Nov 26 17:20:23 WARNING[16384]: chan_unicall.c:634 unicall_error: UniCall: mfcr2 Tx bits 0x9 [1/40000000/ 0/ 0]<BR> -- Registered channel 17, mfcr2 signalling</DIV>
<DIV> </DIV>
<DIV> [snipping]</DIV>
<DIV> </DIV>
<DIV>Nov 26 17:20:24 WARNING[16384]: chan_unicall.c:634 unicall_error: UniCall: mfcr2 mfcr2_Unblock()<BR>Nov 26 17:20:24 WARNING[16384]: chan_unicall.c:634 unicall_error: UniCall: mfcr2 Tx bits 0x9 [1/40000000/ 0/ 0]<BR> -- Registered channel 62, mfcr2 signalling<BR> == Registered channel type 'UniCall' (Unified call processing (UniCall) driver)<BR> == Registered channel type 'roT' (Unified call processing (UniCall) driver)<BR>Nov 26 17:20:24 WARNING[16384]: chan_unicall.c:3141 restart_monitor: XXX creating monitor thread<BR>Nov 26 17:20:24 WARNING[213005]: chan_unicall.c:2548 handle_uc_event: UC event Protocol failure<BR> -- UC channel 1 protocol error. Cause 32773</DIV>
<DIV> </DIV>
<DIV> [snipping]</DIV>
<DIV> </DIV>
<DIV>Nov 26 17:20:25 WARNING[213005]: chan_unicall.c:2548 handle_uc_event: UC event Local end unblocked<BR> -- UC channel 1 local unblocked</DIV>
<DIV> </DIV>
<DIV> [snipping]</DIV>
<DIV> </DIV>
<DIV>Nov 26 17:20:25 WARNING[213005]: chan_unicall.c:2548 handle_uc_event: UC event Local end unblocked<BR> -- UC channel 62 local unblocked<BR></DIV></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>I set in zaptel.conf an idle pattern as "1011" while Brazilian R2 ignores CD bits. ZTTOOL works fine and can monitor the status of signalling, and when inseizing it displays these AB=00 but on Asterisk the following displays:</DIV>
<DIV> </DIV>
<DIV>*CLI> Nov 26 17:36:32 WARNING[213005]: chan_unicall.c:634 unicall_error: UniCall: mfcr2 Rx bits 0x3 [1/40000000/ 0/0]<BR>Nov 26 17:36:32 WARNING[213005]: chan_unicall.c:634 unicall_error: UniCall: mfcr2 R2 prot. err. [1/40000000/ 0/ 0] cause 32773<BR>Nov 26 17:36:32 WARNING[213005]: chan_unicall.c:634 unicall_error: UniCall: mfcr2 Tx bits 0x9 [1/40000000/ 0/ 0]<BR>Nov 26 17:36:32 WARNING[213005]: chan_unicall.c:2548 handle_uc_event: UC event Protocol failure<BR> -- UC channel 5 protocol error. Cause 32773<BR></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Any suggestions ??</DIV>
<DIV> </DIV>
<DIV>HOSIN</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><BR><B><I>Steve Underwood <steveu@coppice.org></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">HO SIN wrote:<BR><BR>> Dear Kaws, and Dear Steve,<BR>> <BR>> I think I am facing the same kind of trouble. This kaws's case is <BR>> simple; one line inserted by patch designates wrong header file name <BR>> of "unical.h", therefore the objects are not compiled. The reality <BR>> is "unicall.h", and<BR><BR>OK, fixed that one.<BR><BR>> after modifying it, then I faced trouble that the compile does not go <BR>> through as some of Asterisk structure definition (for example, <BR>> ast_channel) seemed to have changed after around October version and <BR>> unicall.c could not compile properly. In fact the latest version of <BR>> Asterisk does not compile with the current unicall. I tracked back <BR>> to the version around late September.<BR><BR>I am in the process of updating to the latest asterisk, but right now <BR>chan_unicall will only work with
versions of * a month or more old.<BR><BR>> <BR>> My environment is RH9, and resolved libtiff trouble, and the compile <BR>> finally went through, but it still does not operate properly (does not <BR>> understand line signalling - AB bits correctly).......hmmm<BR>> <BR><BR>Which version of R2 are you using? Most use the ABCD bits in the same <BR>way. China and Thailand are different. The code should be allowing for <BR>those. It certainly works OK for China.<BR><BR>Steve<BR><BR>_______________________________________________<BR>Asterisk-Users mailing list<BR>Asterisk-Users@lists.digium.com<BR>http://lists.digium.com/mailman/listinfo/asterisk-users<BR>To UNSUBSCRIBE or update options visit:<BR>http://lists.digium.com/mailman/listinfo/asterisk-users<BR></BLOCKQUOTE><p>
<hr size=1>Do you Yahoo!?<br>
All your favorites on one personal page – <a href="http://my.yahoo.com">Try My Yahoo!</a>