[asterisk-r2] Problem MFC R2

Tue Mar 3 10:29:41 CST 2009

Is not, but, if you want a solution need to provide more details.

Call logs presenting the issue.
Information about when does it happens, how frequent and how are you
using these R2 alines.
OpenR2 version and Asterisk version.

On Tue, Mar 3, 2009 at 11:25 AM, Juan Carlos Gonzalez Cardona
<juancarlosg6 at gmail.com> wrote:
> I restart the server and all ok, but i think that is not a solution.
>
> 2009/3/3 Moises Silva <moises.silva at gmail.com>
>>
>> That means an incoming call was received just  an instant before an
>> outgoing was placed. You should rarely see this error. If you see it
>> often then may be something else is wrong that is forcing that
>> condition. Can you easily reproduce?
>>
>> Moy
>>
>> On Tue, Mar 3, 2009 at 10:38 AM, Juan Carlos Gonzalez Cardona
>> <juancarlosg6 at gmail.com> wrote:
>> > Hi every one, i am have this problem
>> >
>> > dahdi_r2_on_call_init: Collision of calls on channel 1 detected!.
>> >
>> >
>> >
>> > pbx*CLI> mfcr2 show channels
>> > Chan Variant Max ANI Max DNIS ANI First Immediate Accept Tx CAS   Rx CAS
>> >    1 AR      20      4        No        No               SEIZE AC SEIZE
>> >    2 AR      20      4        No        No               IDLE     IDLE
>> >    3 AR      20      4        No        No               SEIZE AC SEIZE
>> >    4 AR      20      4        No        No               IDLE     IDLE
>> >    5 AR      20      4        No        No               SEIZE AC SEIZE
>> >    6 AR      20      4        No        No               IDLE     IDLE
>> >    7 AR      20      4        No        No               SEIZE AC SEIZE
>> >    8 AR      20      4        No        No               IDLE     IDLE
>> >    9 AR      20      4        No        No               SEIZE AC SEIZE
>> >   10 AR      20      4        No        No               IDLE     IDLE
>> >   11 AR      20      4        No        No               SEIZE AC SEIZE
>> >   12 AR      20      4        No        No               IDLE     IDLE
>> >   13 AR      20      4        No        No               SEIZE AC SEIZE
>> >   14 AR      20      4        No        No               IDLE     IDLE
>> >   15 AR      20      4        No        No               SEIZE AC SEIZE
>> >   17 AR      20      4        No        No               IDLE     IDLE
>> >   18 AR      20      4        No        No               SEIZE AC SEIZE
>> >   19 AR      20      4        No        No               IDLE     IDLE
>> >   20 AR      20      4        No        No               SEIZE AC SEIZE
>> >   21 AR      20      4        No        No               IDLE     IDLE
>> >   22 AR      20      4        No        No               SEIZE AC SEIZE
>> >   23 AR      20      4        No        No               IDLE     IDLE
>> >   24 AR      20      4        No        No               SEIZE AC SEIZE
>> >   25 AR      20      4        No        No               IDLE     IDLE
>> >   26 AR      20      4        No        No               SEIZE AC SEIZE
>> >   27 AR      20      4        No        No               IDLE     IDLE
>> >   28 AR      20      4        No        No               SEIZE AC SEIZE
>> >   29 AR      20      4        No        No               IDLE     IDLE
>> >   30 AR      20      4        No        No               SEIZE AC SEIZE
>> >   31 AR      20      4        No        No               IDLE     IDLE
>> >
>> >
>> > What can be?
>> >
>> > And later this error
>> >
>> > Mar  3 10:29:22] ERROR[3571]: chan_dahdi.c:1218 dahdi_r2_write_log: Chan
>> > 1 -
>> > Protocol error. Reason = Invalid CAS, R2 State = Seize ACK Transmitted,
>> > MF
>> > state = Seize ACK Transmitted, MF Group = Backward MF init, CAS = 0x0C
>> > DNIS = , ANI = , MF = 0x20
>> > [Mar  3 10:29:22] ERROR[3571]: chan_dahdi.c:1028
>> > dahdi_r2_on_protocol_error:
>> > MFC/R2 protocol error on chan 1: Invalid CAS
>> > [Mar  3 10:29:22] ERROR[3571]: chan_dahdi.c:1218 dahdi_r2_write_log:
>> > Chan 3
>> > - Protocol error. Reason = Invalid CAS, R2 State = Seize ACK
>> > Transmitted, MF
>> > state = Seize ACK Transmitted, MF Group = Backward MF init, CAS = 0x0C
>> > DNIS = , ANI = , MF = 0x20
>> > [Mar  3 10:29:22] ERROR[3571]: chan_dahdi.c:1028
>> > dahdi_r2_on_protocol_error:
>> > MFC/R2 protocol error on chan 3: Invalid CAS
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Juan Carlos Gonzalez C.
>> >
>> > _______________________________________________
>> > --Bandwidth and Colocation Provided by http://www.api-digital.com--
>> >
>> > asterisk-r2 mailing list
>> > To UNSUBSCRIBE or update options visit:
>> >   http://lists.digium.com/mailman/listinfo/asterisk-r2
>> >
>>
>>
>>
>> --
>> "I do not agree with what you have to say, but I’ll defend to the
>> death your right to say it." Voltaire
>> _______________________________________________
>> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>>
>> asterisk-r2 mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>
>
> --
> Juan Carlos Gonzalez C.
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>

-- 
"I do not agree with what you have to say, but I’ll defend to the
death your right to say it." Voltaire