Hi, I have three R2 installation on different carriers, all shows the same inconsistency at varying degree. But, on most test calls we made, it reaches T3. The worst part of these, the carrier claims that it's my R2 box that is not responding in time. Please, check the attached file and take note of the timestamp, you'll find that in some call, it already contradict what the carrier claims but they too have logs to counter my claim. So, I hope people, please give me a good insight and direction to resolve this problem. I have the following for my R2 box: unicall-0.0.3pre8 libmfcr2-0.0.3 libsupertone-0.0.2 libunicall-0.0.3 spandsp-0.0.2pre25 asterisk-1.2.6 zaptel-1.2.5 wanpipe-2.3.3-2 2.6.11-1.1369_FC4smp sangoma A101 in my zaptel.conf I got the following: span=1,0,0,cas,hdb3 loadzone = us defaultzone=us cas=1-15:1101 cas=17-31:1101 in my unicall.conf I got these lines: [channels] context=default usecallerid=yes hidecallerid=no callwaitingcallerid=yes threewaycalling=yes transfer=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes rxgain=0.0 txgain=0.0 group=1 callgroup=1 pickupgroup=1 immediate=no supertones=ph loglevel=255 protocolclass=mfcr2 protocolvariant=ph,10,3,12 protocolend=co group = 1 channel => 1-15 channel => 17-31 Thanks a lot. Dennis __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- Apr 3 11:34:54 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 0001 [1/ 1/Idle /Idle ] Apr 3 11:34:54 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 Detected Apr 3 11:34:54 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 Making a new call with CRN 32769 Apr 3 11:34:54 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1101 -> [2/ 2/Idle /Idle ] Apr 3 11:34:54 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/1 event Detected Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 3 on [2/ 2/Seize ack /Seize ack ] Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1 on -> [2/ 2/Seize ack /Seize ack ] Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 3 off [2/ 2/Group A /DNIS request ] Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1 off -> [2/ 2/Group A /DNIS request ] Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 3 on [2/ 2/Group A /DNIS request ] Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1 on -> [2/ 2/Group A /DNIS request ] Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 3 off [2/ 2/Group A /DNIS request ] Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1 off -> [2/ 2/Group A /DNIS request ] Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 3 on [2/ 2/Group A /DNIS request ] Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 5 on -> [2/ 2/Group A /DNIS request ] Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 1 on [2/ 2/Group A /Category req ] Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 1 off [2/ 2/Group A /ANI request ] Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 5 off -> [2/ 2/Group A /ANI request ] Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 R2 prot. err. [2/ 2/Group A /ANI request ] cause 32771 - T3 timed out Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1001 -> [1/ 1/Idle /Idle ] Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/1 event Protocol failure -- Unicall/1 protocol error. Cause 32771 Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 Channel echo cancel Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 1001 [1/ 1/Idle /Idle ] Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1001 -> [1/ 1/Idle /Idle ] =========================================================================================================Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 0001 [1/ 1/Idle /Idle ] Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Detected Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Making a new call with CRN 32769 Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1101 -> [2/ 2/Idle /Idle ] Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/2 event Detected Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 on [2/ 2/Seize ack /Seize ack ] Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 on -> [2/ 2/Seize ack /Seize ack ] Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 off [2/ 2/Group A /DNIS request ] Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 off -> [2/ 2/Group A /DNIS request ] Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 on [2/ 2/Group A /DNIS request ] Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 on -> [2/ 2/Group A /DNIS request ] Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 off [2/ 2/Group A /DNIS request ] Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 off -> [2/ 2/Group A /DNIS request ] Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 on [2/ 2/Group A /DNIS request ] Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 on -> [2/ 2/Group A /DNIS request ] Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 off [2/ 2/Group A /Category req ] Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 off -> [2/ 2/Group A /Category req ] Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 1 on [2/ 2/Group A /Category req ] Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 on -> [2/ 2/Group A /Category req ] Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 1 off [2/ 2/Group A /ANI request ] Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 off -> [2/ 2/Group A /ANI request ] Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 0 on [2/ 2/Group A /ANI request ] Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 on -> [2/ 2/Group A /ANI request ] Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 0 off [2/ 2/Group A /ANI request ] Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 off -> [2/ 2/Group A /ANI request ] Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 R2 prot. err. [2/ 2/Group A /ANI request ] cause 32771 - T3 timed out Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1001 -> [1/ 1/Idle /Idle ] Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/2 event Protocol failure -- Unicall/2 protocol error. Cause 32771 Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Channel echo cancel Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 1001 [1/ 1/Idle /Idle ] Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1001 -> [1/ 1/Idle /Idle ] ============================================================================================================================================================================Connected to Asterisk 1.2.6 currently running on prompt (pid = 17308) Verbosity is at least 3 Apr 3 14:40:26 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 0001 [1/ 1/Idle /Idle ] Apr 3 14:40:26 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 Detected Apr 3 14:40:26 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 Making a new call with CRN 32770 Apr 3 14:40:27 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1101 -> [2/ 2/Idle /Idle ] Apr 3 14:40:27 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/1 event Detected Apr 3 14:40:27 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 3 on [2/ 2/Seize ack /Seize ack ] Apr 3 14:40:27 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1 on -> [2/ 2/Seize ack /Seize ack ] Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 3 off [2/ 2/Group A /DNIS request ] Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1 off -> [2/ 2/Group A /DNIS request ] Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 R2 prot. err. [2/ 2/Group A /DNIS request ] cause 32771 - T3 timed out Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1001 -> [1/ 1/Idle /Idle ] Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/1 event Protocol failure -- Unicall/1 protocol error. Cause 32771 Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 Channel echo cancel Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 1001 [1/ 1/Idle /Idle ] Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1001 -> [1/ 1/Idle /Idle ] =====================================================================================================Apr 3 15:30:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 0001 [1/ 1/Idle /Idle ] Apr 3 15:30:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Detected Apr 3 15:30:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Making a new call with CRN 32770 Apr 3 15:30:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1101 -> [2/ 2/Idle /Idle ] Apr 3 15:30:50 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/2 event Detected Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 on [2/ 2/Seize ack /Seize ack ] Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 on -> [2/ 2/Seize ack /Seize ack ] Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 off [2/ 2/Group A /DNIS request ] Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 off -> [2/ 2/Group A /DNIS request ] Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 on [2/ 2/Group A /DNIS request ] Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 on -> [2/ 2/Group A /DNIS request ] Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 off [2/ 2/Group A /DNIS request ] Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 off -> [2/ 2/Group A /DNIS request ] Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 on [2/ 2/Group A /DNIS request ] Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 on -> [2/ 2/Group A /DNIS request ] Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 off [2/ 2/Group A /Category req ] Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 off -> [2/ 2/Group A /Category req ] Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 1 on [2/ 2/Group A /Category req ] Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 on -> [2/ 2/Group A /Category req ] Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 0 on [2/ 2/Group A /ANI request ] Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 0 off [2/ 2/Group A /ANI request ] Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 off -> [2/ 2/Group A /ANI request ] Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 R2 prot. err. [2/ 2/Group A /ANI request ] cause 32771 - T3 timed out Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1001 -> [1/ 1/Idle /Idle ] Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/2 event Protocol failure -- Unicall/2 protocol error. Cause 32771 Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Channel echo cancel Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 1001 [1/ 1/Idle /Idle ] Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1001 -> [1/ 1/Idle /Idle ]
Why you are not using "span=1,1,0,cas,hdb3" ? Since the other end is the Telco, they will provide you the source timing sync. Try upgrade your sangoma drivers and make sure the TE_CLOCK line inside /etc/wanpipe/wanpipe1.conf says "NORMAL". []'s MM -----Original Message----- From: Dennis Nacino <starisk11@yahoo.com> To: asterisk-users@lists.digium.com Cc: Sent: Mon, 3 Apr 2006 02:10:10 -0700 (PDT) Delivered: Mon, 03 Apr 2006 03:13:17 Subject:[Asterisk-Users] R2 protocol error Hi, I have three R2 installation on different carriers, all shows the same inconsistency at varying degree. But, on most test calls we made, it reaches T3. The worst part of these, the carrier claims that it's my R2 box that is not responding in time. Please, check the attached file and take note of the timestamp, you'll find that in some call, it already contradict what the carrier claims but they too have logs to counter my claim. So, I hope people, please give me a good insight and direction to resolve this problem. I have the following for my R2 box: unicall-0.0.3pre8 libmfcr2-0.0.3 libsupertone-0.0.2 libunicall-0.0.3 spandsp-0.0.2pre25 asterisk-1.2.6 zaptel-1.2.5 wanpipe-2.3.3-2 2.6.11-1.1369_FC4smp sangoma A101 in my zaptel.conf I got the following: span=1,0,0,cas,hdb3 loadzone = us defaultzone=us cas=1-15:1101 cas=17-31:1101 in my unicall.conf I got these lines: [channels] context=default usecallerid=yes hidecallerid=no callwaitingcallerid=yes threewaycalling=yes transfer=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes rxgain=0.0 txgain=0.0 group=1 callgroup=1 pickupgroup=1 immediate=no supertones=ph loglevel=255 protocolclass=mfcr2 protocolvariant=ph,10,3,12 protocolend=co group = 1 channel => 1-15 channel => 17-31 Thanks a lot. Dennis __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com E-mail classificado pelo Identificador de Spam Inteligente Terra. Para alterar a categoria classificada, visite http://mail.terra.com.br/protected_email/imail/imail.cgi?+_u=levelz&_l=1,1144055598.8638.2003.almora.terra.com.br,19124,20031127114101,20031127114101 --Original Message Ends-- -- Melcon Moraes <melcon.moraes@terra.com.br>
Hi Dennis, Update to libmfcr2-0.0.3 pre9. I made a slip in pre8. Sorry. Steve Dennis Nacino wrote:>Hi, > >I have three R2 installation on different carriers, all shows the same inconsistency at varying >degree. But, on most test calls we made, it reaches T3. The worst part of these, the carrier >claims that it's my R2 box that is not responding in time. Please, check the attached file and >take note of the timestamp, you'll find that in some call, it already contradict what the carrier >claims but they too have logs to counter my claim. So, I hope people, please give me a good >insight and direction to resolve this problem. > >I have the following for my R2 box: >unicall-0.0.3pre8 > libmfcr2-0.0.3 > libsupertone-0.0.2 > libunicall-0.0.3 >spandsp-0.0.2pre25 > >asterisk-1.2.6 >zaptel-1.2.5 >wanpipe-2.3.3-2 > >2.6.11-1.1369_FC4smp >sangoma A101 > >in my zaptel.conf I got the following: > >span=1,0,0,cas,hdb3 >loadzone = us >defaultzone=us >cas=1-15:1101 >cas=17-31:1101 > >in my unicall.conf I got these lines: > >[channels] >context=default >usecallerid=yes >hidecallerid=no >callwaitingcallerid=yes >threewaycalling=yes >transfer=yes >cancallforward=yes >callreturn=yes >echocancel=yes >echocancelwhenbridged=yes >rxgain=0.0 >txgain=0.0 >group=1 >callgroup=1 >pickupgroup=1 >immediate=no >supertones=ph >loglevel=255 >protocolclass=mfcr2 >protocolvariant=ph,10,3,12 >protocolend=co >group = 1 >channel => 1-15 >channel => 17-31 > > >Thanks a lot. > >Dennis > > > > > > >__________________________________________________ >Do You Yahoo!? >Tired of spam? Yahoo! Mail has the best spam protection around >http://mail.yahoo.com > >------------------------------------------------------------------------ > >Apr 3 11:34:54 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 0001 [1/ 1/Idle /Idle ] >Apr 3 11:34:54 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 Detected >Apr 3 11:34:54 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 Making a new call with CRN 32769 >Apr 3 11:34:54 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1101 -> [2/ 2/Idle /Idle ] >Apr 3 11:34:54 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/1 event Detected >Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 3 on [2/ 2/Seize ack /Seize ack ] >Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1 on -> [2/ 2/Seize ack /Seize ack ] >Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 3 off [2/ 2/Group A /DNIS request ] >Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1 off -> [2/ 2/Group A /DNIS request ] >Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 3 on [2/ 2/Group A /DNIS request ] >Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1 on -> [2/ 2/Group A /DNIS request ] >Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 3 off [2/ 2/Group A /DNIS request ] >Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1 off -> [2/ 2/Group A /DNIS request ] >Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 3 on [2/ 2/Group A /DNIS request ] >Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 5 on -> [2/ 2/Group A /DNIS request ] >Apr 3 11:34:55 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 1 on [2/ 2/Group A /Category req ] >Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 1 off [2/ 2/Group A /ANI request ] >Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 5 off -> [2/ 2/Group A /ANI request ] >Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 R2 prot. err. [2/ 2/Group A /ANI request ] cause 32771 - T3 timed out >Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1001 -> [1/ 1/Idle /Idle ] >Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/1 event Protocol failure > -- Unicall/1 protocol error. Cause 32771 >Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 Channel echo cancel >Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 1001 [1/ 1/Idle /Idle ] >Apr 3 11:35:20 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1001 -> [1/ 1/Idle /Idle ] >=========================================================================================================>Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 0001 [1/ 1/Idle /Idle ] >Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Detected >Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Making a new call with CRN 32769 >Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1101 -> [2/ 2/Idle /Idle ] >Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/2 event Detected >Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 on [2/ 2/Seize ack /Seize ack ] >Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 on -> [2/ 2/Seize ack /Seize ack ] >Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 off [2/ 2/Group A /DNIS request ] >Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 off -> [2/ 2/Group A /DNIS request ] >Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 on [2/ 2/Group A /DNIS request ] >Apr 3 11:41:49 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 on -> [2/ 2/Group A /DNIS request ] >Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 off [2/ 2/Group A /DNIS request ] >Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 off -> [2/ 2/Group A /DNIS request ] >Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 on [2/ 2/Group A /DNIS request ] >Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 on -> [2/ 2/Group A /DNIS request ] >Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 off [2/ 2/Group A /Category req ] >Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 off -> [2/ 2/Group A /Category req ] >Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 1 on [2/ 2/Group A /Category req ] >Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 on -> [2/ 2/Group A /Category req ] >Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 1 off [2/ 2/Group A /ANI request ] >Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 off -> [2/ 2/Group A /ANI request ] >Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 0 on [2/ 2/Group A /ANI request ] >Apr 3 11:41:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 on -> [2/ 2/Group A /ANI request ] >Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 0 off [2/ 2/Group A /ANI request ] >Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 off -> [2/ 2/Group A /ANI request ] >Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 R2 prot. err. [2/ 2/Group A /ANI request ] cause 32771 - T3 timed out >Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1001 -> [1/ 1/Idle /Idle ] >Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/2 event Protocol failure > -- Unicall/2 protocol error. Cause 32771 >Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Channel echo cancel >Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 1001 [1/ 1/Idle /Idle ] >Apr 3 11:42:15 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1001 -> [1/ 1/Idle /Idle ] >====================================================================================================>========================================================================>Connected to Asterisk 1.2.6 currently running on prompt (pid = 17308) >Verbosity is at least 3 >Apr 3 14:40:26 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 0001 [1/ 1/Idle /Idle ] >Apr 3 14:40:26 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 Detected >Apr 3 14:40:26 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 Making a new call with CRN 32770 >Apr 3 14:40:27 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1101 -> [2/ 2/Idle /Idle ] >Apr 3 14:40:27 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/1 event Detected >Apr 3 14:40:27 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 3 on [2/ 2/Seize ack /Seize ack ] >Apr 3 14:40:27 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1 on -> [2/ 2/Seize ack /Seize ack ] >Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 3 off [2/ 2/Group A /DNIS request ] >Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1 off -> [2/ 2/Group A /DNIS request ] >Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 R2 prot. err. [2/ 2/Group A /DNIS request ] cause 32771 - T3 timed out >Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1001 -> [1/ 1/Idle /Idle ] >Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/1 event Protocol failure > -- Unicall/1 protocol error. Cause 32771 >Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 Channel echo cancel >Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 <- 1001 [1/ 1/Idle /Idle ] >Apr 3 14:40:52 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/1 1001 -> [1/ 1/Idle /Idle ] >=====================================================================================================>Apr 3 15:30:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 0001 [1/ 1/Idle /Idle ] >Apr 3 15:30:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Detected >Apr 3 15:30:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Making a new call with CRN 32770 >Apr 3 15:30:50 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1101 -> [2/ 2/Idle /Idle ] >Apr 3 15:30:50 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/2 event Detected >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 on [2/ 2/Seize ack /Seize ack ] >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 on -> [2/ 2/Seize ack /Seize ack ] >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 off [2/ 2/Group A /DNIS request ] >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 off -> [2/ 2/Group A /DNIS request ] >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 on [2/ 2/Group A /DNIS request ] >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 on -> [2/ 2/Group A /DNIS request ] >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 off [2/ 2/Group A /DNIS request ] >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1 off -> [2/ 2/Group A /DNIS request ] >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 on [2/ 2/Group A /DNIS request ] >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 on -> [2/ 2/Group A /DNIS request ] >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 3 off [2/ 2/Group A /Category req ] >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 off -> [2/ 2/Group A /Category req ] >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 1 on [2/ 2/Group A /Category req ] >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 on -> [2/ 2/Group A /Category req ] >Apr 3 15:30:51 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 0 on [2/ 2/Group A /ANI request ] >Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 0 off [2/ 2/Group A /ANI request ] >Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 5 off -> [2/ 2/Group A /ANI request ] >Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 R2 prot. err. [2/ 2/Group A /ANI request ] cause 32771 - T3 timed out >Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1001 -> [1/ 1/Idle /Idle ] >Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:2644 handle_uc_event: Unicall/2 event Protocol failure > -- Unicall/2 protocol error. Cause 32771 >Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 Channel echo cancel >Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 <- 1001 [1/ 1/Idle /Idle ] >Apr 3 15:31:16 WARNING[17334]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/2 1001 -> [1/ 1/Idle /Idle ] > > >------------------------------------------------------------------------ > >_______________________________________________ >--Bandwidth and Colocation provided by Easynews.com -- > >Asterisk-Users mailing list >To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > >
Hi MM and Steve, I still got the same problem when I changed the span configuration setting into span=1,1,0,cas,hdb3 Where can I get the pre9? Is there something wrong with www.soft-switch.org site? It seems unreachable. Thanks again. Dennis __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Hi, Thanks a lot, guys! The problem is now fixed by updating the libmfcr2-0.0.3 to pre9 and setting the span timing correctly. Dennis __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com