[Asterisk-Users] MFC R2 - Can this problem be solved??????????

[Steve Underwood]

j_amorim wrote:

>Hi, 
>
>MFC R2 - UniCall implementation. 
>
>The * is configured to send a 1101 Idle signal: 
>
>zaptel.conf 
>
>
>span=3,1,0,cas,hdb3 
># 
>cas=9-23:1101 
>cas=25-39:1101
>
You seem to have configured 1101 as the blocking signal.

> 
>But is sending 1001 Idle signal 
>  
>
1001 is the usual idle signal.

>Can anyone send me a tip?????? 
>
>Jun 20 19:06:56 WARNING[24118]: chan_unicall.c:704 unicall_report: MFC/R2 
>UniCall/12 1001  ->      [1/40000000/Idle          /Idle         ] 
>Jun 20 19:06:56 WARNING[24118]: chan_unicall.c:704 unicall_report: MFC/R2 
>UniCall/12      <- 1011  [1/40000000/Idle          /Idle         ] 
>Jun 20 19:06:56 WARNING[24118]: chan_unicall.c:704 unicall_report: MFC/R2 
>UniCall/12 R2 prot. err. [1/40000000/Idle          /Idle         ] cause 
>32773 
>Jun 20 19:06:56 WARNING[24118]: chan_unicall.c:704 unicall_report: MFC/R2 
>UniCall/12 1001  ->      [1/40000000/Idle          /Idle         ] 
>Jun 20 19:06:56 WARNING[24118]: chan_unicall.c:2865 handle_uc_event: 
>Unicall/12 event Protocol failure 
>    -- Unicall/12 protocol error. Cause 32773 
>  
>
The far ends seems to be acting like the China or Thailand protocols, 
but I guess from your email address you are in Brazil. A number of 
people use my R2 software Brazil, but this is the second time someone 
has reported this problem this week. Strange. I am currently changing 
the software to make it more flexible, and tolerate this kind of 
behaviour. It should be ready in a day or two.

Regards,
Steve