[asterisk-users] mfcr/R2

[Moises Silva]

You may want to give a try to this document I wrote about mfcr2 with Asterisk.

http://moy.ivsol.net/unicall/mfcr2-asterisk-unicall-0.2-english.pdf

Regards

On 11/24/06, Alyed Tzompa <alyed.tzompa at simitel.com> wrote:
>  Hello!
>
>  I'm tryuing to bring up an R2 connection but eventhough I've followed the
> guidelines in: http://zarzamora.com.mx/asterisk/17
> something seems to be missing.
>
>
>  When an incomming call is generated I get:
>
>  Nov 24 06:01:17 WARNING[-197416016]: chan_unicall.c:612 unicall_report:
> MFC/R2 UniCall/24      <- 0001  [1/       1/Idle          /Idle    ]
>  Nov 24 06:01:17 WARNING[-197416016]: chan_unicall.c:612 unicall_report:
> MFC/R2 UniCall/24 Detected
>  Nov 24 06:01:17 WARNING[-197416016]: chan_unicall.c:612 unicall_report:
> MFC/R2 UniCall/24 Making a new call with CRN 32771
>  Nov 24 06:01:17 WARNING[-197416016]: chan_unicall.c:612 unicall_report:
> MFC/R2 UniCall/24 1101  ->      [2/       2/Idle          /Idle    ]
>  Nov 24 06:01:17 WARNING[-197416016]: chan_unicall.c:2672 handle_uc_event:
> Unicall/24 event Detected
>
>  and that's it, afterwards just a busy tone and the telco guy says the
> channel turns "sealed".
>
>
>  When I try an outbound call I get:
>
>      -- Attempting call on Unicall/g2/12345678 for s at default:1 (Retry 1)
>  Nov 24 05:53:52 WARNING[-286483536]: chan_unicall.c:612 unicall_report:
> MFC/R2 UniCall/24 Call control(1)
>  Nov 24 05:53:52 WARNING[-286483536]: chan_unicall.c:612 unicall_report:
> MFC/R2 UniCall/24 Make call
>  Nov 24 05:53:52 WARNING[-286483536]: chan_unicall.c:612 unicall_report:
> MFC/R2 UniCall/24 Making a new call with CRN 32769
>  Nov 24 05:53:52 WARNING[-286483536]: chan_unicall.c:612 unicall_report:
> MFC/R2 UniCall/24 0001  ->      [1/       1/Idle          /Idle    ]
>  Nov 24 05:53:52 WARNING[-286483536]: chan_unicall.c:2672 handle_uc_event:
> Unicall/24 event Dialing
>  Nov 24 05:53:54 WARNING[-286483536]: chan_unicall.c:612 unicall_report:
> MFC/R2 UniCall/24 seize_ack_wait_expired
>  Nov 24 05:53:54 WARNING[-286483536]: chan_unicall.c:612 unicall_report:
> MFC/R2 UniCall/24 R2 prot. err. [1/      40/Seize         /Idle    ] cause
> 32776 - Seize ack timed out
>  Nov 24 05:53:54 WARNING[-286483536]: chan_unicall.c:612 unicall_report:
> MFC/R2 UniCall/24 1001  ->      [1/       1/Idle          /Idle    ]
>  Nov 24 05:53:54 WARNING[-286483536]: chan_unicall.c:2672 handle_uc_event:
> Unicall/24 event Protocol failure
>      -- Unicall/24 protocol error. Cause 32776
>  Nov 24 05:53:54 WARNING[-286483536]: chan_unicall.c:612 unicall_report:
> MFC/R2 UniCall/24 Channel echo cancel
>  Nov 24 05:53:54 WARNING[-286483536]: chan_unicall.c:612 unicall_report:
> MFC/R2 UniCall/24 Channel gains
>  Nov 24 05:53:54 WARNING[-286483536]: chan_unicall.c:612 unicall_report:
> MFC/R2 UniCall/24 Channel switching
>      -- Hungup 'UniCall/24-1'
>  Nov 24 05:53:54 NOTICE[-286483536]: pbx_spool.c:234 attempt_thread: Call
> failed to go through, reason 1
>
>
>
>  Something else funny is happening: as soon as the telco makes a reset of
> the trunk they say they start receving data as if the PBX would be
> generating calls, then all channels go "sealed" except for 1.
>
>
>  Anyone having an idea on how to solve this?
>
>
> Alyed
>
> _______________________________________________
> --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
>
>
>


-- 
"Su nombre es GNU/Linux, no solamente Linux, mas info en http://www.gnu.org"