[asterisk-r2] MFC/R2 protocol error on chan 1: Seize Timeout

[Petya Minovska]

Thanks Moises,

I will appreciate if you can help me a little more. I have tried some 
different configurations but still no luck.
The following table shows the signalling bits, which I can configure 
from the other side:

Towards Exchange

	

 From Exchange

	

Bitsabcd

	

	

Bitsabcd

On-Hook

	

0101

	

Ringing

	

1101

Off-Hook

	

0001

	

Metering Pulse

	

1011

Ground

	

1001

	

Polarity Reversal

	

0001


By default my Digium Te133 board sends 1001, which I can see from the 
dahdi_tool.
In the right side (From Exchange) I set ringing: 0001, because this is 
the only combination of bits when the phone rings if I make a call. The 
combinations of the bits on the left side (Towards Exchange) I have 
tried are:
1) On-hook 1010
     Off-hook 0101
When I try to make a call the phone is ringing continuously and when I 
pick up the signal is busy and the CLI sends /*Invalid CAS*/ error.
2) On-hook 1010
     Off-hook 1001
When I try to make a call the phone is ringing continuously and when I 
pick up there is no signal and after some seconds the CLI sends /*Seize 
Timeout*/ error.
3) On-hook 1010
     Off-hook 0001
When I try to make a call the phone is ringing continuously and when I 
pick up the CLI shows: /*Far end disconnected. Reason: Forced Release*/ 
and then /*Seize Timeout Expired!*//*
*/
Would you give me any clue how to proceed?

Regards,
Petya

Petya Minovska
Telecommunication Engineer
Balkantel Ltd
bul. Bratia Bakston, 68
Post Code 1618, Sofia
Bulgaria
e-mail: p.minovska at balkantel.net
phone: +359 887 005 158

On 2/4/2015 8:20 PM, Moises Silva wrote:
> On Wed, Feb 4, 2015 at 3:43 AM, Petya Minovska 
> <p.minovska at balkantel.net <mailto:p.minovska at balkantel.net>> wrote:
>
>     Hello,
>
>     I have an Asterisk server and a multiplexer connected via E1
>     boards (TE133 Digium for the server and Lomif for the
>     multiplexer). I have connected a phone to the FXS board of the
>     multiplexer and I am trying to make a call to it. Through
>     dahdi_tool I can see the rx and tx CAS bits and when I change them
>     I see it.
>     Both rx CAS and tx CAS are in state 'idle', but when I try to make
>     a call I see the following error in the CLI;
>
>     /* == Using SIP RTP CoS mark 5*//*
>     *//*    -- Executing [812 at demo:1] Dial("SIP/101-00000015",
>     "DAHDI/1/812,,tT") in new stack*//*
>     *//*    -- Called DAHDI/1/812*//*
>     *//*[Feb  4 10:36:10] WARNING[32752]: chan_dahdi.c:4185
>     dahdi_r2_write_log: Chan 1 - Seize Timeout Expired!*//*
>     *//*[Feb  4 10:36:10] ERROR[32752]: chan_dahdi.c:4188
>     dahdi_r2_write_log: Chan 1 - Protocol error. Reason = Seize
>     Timeout, R2 State = Seize Transmitted, MF state = MF Engine Off,
>     MF Group = Forward MF init, CAS = 0x08*//*
>     *//*DNIS = 812, ANI = 101, MF = 0x20*//*
>     *//*[Feb  4 10:36:10] ERROR[32752]: chan_dahdi.c:3973
>     dahdi_r2_on_protocol_error: MFC/R2 protocol error on chan 1: Seize
>     Timeout*//*
>     *//*    -- Hungup 'DAHDI/1-1'*//*
>     *//*  == Everyone is busy/congested at this time (1:0/0/1)*//*
>     *//*    -- Executing [812 at demo:2] NoOp("SIP/101-00000015", " DAN
>     CHANUNAVAIL") in new stack*//*
>     *//*    -- Executing [812 at demo:3] Hangup("SIP/101-00000015", "")
>     in new stack*//*
>     *//*  == Spawn extension (demo, 812, 3) exited non-zero on
>     'SIP/101-00000015'*/
>
>     Would you please tell me what can help me to solve the problem. Is
>     there a problem with the signalling bits, configured in the
>     multiplexer or the configuration in the Asterisk.
>
>
> This error is typically a configuration problem on the other end. It 
> means we sent a CAS signal but did not receive any response (no bit 
> changes on the rx)
>
>



---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-r2/attachments/20150205/e391a4d9/attachment-0001.html>