[asterisk-r2] asterisk-r2 Digest, Vol 17, Issue 2

Thu Jan 14 08:48:21 CST 2010

It could be either 2 things.... Telmex changed the r2 spec.... Or....
Something was wrong with what you are using... Try using asterisk 1.6.2,
latest dahdi, openr2 1.2.0 and let me know how it goes...

> From: "Ing. Jose Jaime Guzmán Romero" <jaime.guzman at kokusai.com.mx>
> Reply-To: <asterisk-r2 at lists.digium.com>
> Date: Wed, 13 Jan 2010 23:40:34 -0600
> To: <asterisk-r2 at lists.digium.com>
> Subject: Re: [asterisk-r2] asterisk-r2 Digest, Vol 17, Issue 2
> 
> Hi Anton,
> 
> This week I change my astunicall 1.6.0.1 to asterisk 1.6.2 with open R2, but
> I had many problems. My users reported me cut calls and I matched with this
> error:
> 
> [Jan 12 11:59:44] DEBUG[27798] chan_dahdi.c: Chan 12 - Bits changed from
> 0x00 to 0x04
> [Jan 12 11:59:44] DEBUG[27798] chan_dahdi.c: Chan 12 - CAS Rx << [0x04] 0x04
> [Jan 12 11:59:44] ERROR[27798] chan_dahdi.c: Chan 12 - Protocol error.
> Reason = Invalid CAS, R2 State = Clear Back Transmitted, MF state = MF
> Engine Off, MF Group = Backward Group B, CAS = 0x04
> [Jan 12 11:59:44] DEBUG[27798] chan_dahdi.c: Chan 12 - CAS Tx >> [IDLE] 0x08
> [Jan 12 11:59:44] DEBUG[27798] chan_dahdi.c: Chan 12 - CAS Raw Tx >> 0x09
> [Jan 12 11:59:44] ERROR[27798] chan_dahdi.c: MFC/R2 protocol error on chan
> 12: Invalid CAS
> [Jan 12 11:59:44] DEBUG[27798] chan_dahdi.c: Chan 12 - Bits changed from
> 0x04 to 0x00
> [Jan 12 11:59:44] DEBUG[27798] chan_dahdi.c: Chan 12 - CAS Rx << [SEIZE]
> 0x00
> [Jan 12 11:59:44] DEBUG[27798] chan_dahdi.c: Chan 12 - Call started at Tue
> Jan 12 11:59:44 2010 on chan 12 [openr2 version 1.2.0, revision (release)]
> [Jan 12 11:59:44] DEBUG[27798] chan_dahdi.c: Chan 12 - CAS Tx >> [SEIZE ACK]
> 0x0C
> [Jan 12 11:59:44] DEBUG[27798] chan_dahdi.c: Chan 12 - CAS Raw Tx >> 0x0D
> [Jan 12 11:59:44] VERBOSE[27798] chan_dahdi.c: New MFC/R2 call detected on
> chan 12.
> 
> 
> The failures occurs primarily at the intermittent channels:
> [Jan 12 09:00:56] NOTICE[4580]: chan_dahdi.c:1947 dahdi_r2_on_line_blocked:
> Far end blocked on chan 6
> [Jan 12 09:00:56] NOTICE[4580]: chan_dahdi.c:1956 dahdi_r2_on_line_idle: Far
> end unblocked on chan 6
> 
> I changed the balun but the problem persisted and I had to return to the
> astunicall version. I have this messages
>  [Jan 13 23:09:58] NOTICE[30485] chan_unicall.c: Unicall/6 event Far end
> blocked
> [Jan 13 23:09:58] VERBOSE[30485] logger.c:     -- Unicall/6 far blocked
> [Jan 13 23:09:58] NOTICE[30485] chan_unicall.c: Unicall/6 event Far end
> unblocked
> [Jan 13 23:09:58] VERBOSE[30485] logger.c:     -- Unicall/6 far unblocked
> 
> I think it could be problem of Telmex.
> 
> Regards,
> 
> 
> Jaime Guzmán
> 
> 
> -----Mensaje original-----
> De: asterisk-r2-bounces at lists.digium.com
> [mailto:asterisk-r2-bounces at lists.digium.com] En nombre de
> asterisk-r2-request at lists.digium.com
> Enviado el: miércoles, 13 de enero de 2010 12:00 p.m.
> Para: asterisk-r2 at lists.digium.com
> Asunto: asterisk-r2 Digest, Vol 17, Issue 2
> 
> Send asterisk-r2 mailing list submissions to
> asterisk-r2 at lists.digium.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.digium.com/mailman/listinfo/asterisk-r2
> or, via email, send a message with subject or body 'help' to
> asterisk-r2-request at lists.digium.com
> 
> You can reach the person managing the list at
> asterisk-r2-owner at lists.digium.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of asterisk-r2 digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: asterisk-r2 Digest, Vol 16, Issue 27 (Anton Krall)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 12 Jan 2010 14:30:22 -0600
> From: Anton Krall <antonkrall at gmail.com>
> Subject: Re: [asterisk-r2] asterisk-r2 Digest, Vol 16, Issue 27
> To: <asterisk-r2 at lists.digium.com>
> Message-ID: <C77237FE.9F820%antonkrall at gmail.com>
> Content-Type: text/plain; charset="ISO-8859-1"
> 
> Hi Jaime.... So far this seems like a problem with asterisk 1.2 and openr2
> because Ive tested it with Sangoma and Digium cards and I get the same
> results.
> 
> Next Monday I?ll be testing the same Sangoma card and openr2 1.2.0 but using
> asterisk 1.6.2 which now has openr2 built-in. Ill let you know if this fixes
> things.
> 
> But right now what Im seen is that for some reason, PBX?es that were working
> fine with asterisk 1.2 and openr2 are now giving out errors like the inalid
> cas ones and red alarms with sudden blocked and unblocked channels or seize
> timeout errors. It would look as if the openr2 spec for Mexico had suddenly
> changed but I wont be sure until I can test it with our own E1 which is from
> Axtel and gets installed on Friday.
> 
> Will keep you posted.
> 
> If you want a fast fix, when you get this, stop asterisk for a moment,
> unload all sangoma or digium drivers, reload them and then reload asterisk,
> this stops the invalid cas and seize timeout problems for a bit at least.
> 
> 
> 
> From: "Ing. Jaime Guzman Romero" <jaime.guzman at kokusai.com.mx>
> Organization: Kokusai Naturista S.A de C.V
> Reply-To: <asterisk-r2 at lists.digium.com>
> Date: Tue, 12 Jan 2010 09:24:57 +0000
> To: <asterisk-r2 at lists.digium.com>
> Subject: Re: [asterisk-r2] asterisk-r2 Digest, Vol 16, Issue 27
> 
> Hi everybody,
> 
> 
> 
> I have the same problem. The asterisk Cli frequently gives this message:
> 
> 
> 
> [Jan 12 09:00:44] NOTICE[4580]: chan_dahdi.c:1956 dahdi_r2_on_line_idle: Far
> end unblocked on chan 6
> [Jan 12 09:00:45] NOTICE[4580]: chan_dahdi.c:1947 dahdi_r2_on_line_blocked:
> Far end blocked on chan 6
> [Jan 12 09:00:45] NOTICE[4580]: chan_dahdi.c:1956 dahdi_r2_on_line_idle: Far
> end unblocked on chan 6
> [Jan 12 09:00:50] NOTICE[4582]: chan_dahdi.c:1947 dahdi_r2_on_line_blocked:
> Far end blocked on chan 26
> [Jan 12 09:00:50] NOTICE[4582]: chan_dahdi.c:1956 dahdi_r2_on_line_idle: Far
> end unblocked on chan 26
> [Jan 12 09:00:51] NOTICE[4580]: chan_dahdi.c:1947 dahdi_r2_on_line_blocked:
> Far end blocked on chan 6
> [Jan 12 09:00:51] NOTICE[4580]: chan_dahdi.c:1956 dahdi_r2_on_line_idle: Far
> end unblocked on chan 6
> [Jan 12 09:00:56] NOTICE[4580]: chan_dahdi.c:1947 dahdi_r2_on_line_blocked:
> Far end blocked on chan 6
> [Jan 12 09:00:56] NOTICE[4580]: chan_dahdi.c:1956 dahdi_r2_on_line_idle: Far
> end unblocked on chan 6
> 
> 
> 
> And sometimes income a call and a few minutes later a can see:
> 
> 
> 
> SIP/1131-00000072 answered DAHDI/12-1
> 
> MFC/R2 call end on channel 35
> [Jan 12 08:56:23] ERROR[5167]: chan_dahdi.c:1925 dahdi_r2_write_log: Chan 12
> - Protocol error. Reason = Invalid CAS, R2 State = Answer Transmitted, MF
> state = MF Engine Off, MF Group = Backward Group B, CAS =0x04
> DNIS = 3200, ANI = 5556726862, MF = 0x20
> 
> 
> [Jan 12 08:56:23] ERROR[5167]: chan_dahdi.c:1710 dahdi_r2_on_protocol_error:
> MFC/R2 protocol error on chan 12: Invalid CAS
> 
> 
> 
> And the call suddenly broke. Did you resolve the problem Anton?
> 
> 
> 
> Regards,
> 
> 
> 
> Ing. Jaime Guzm?n
> 
> 
> 
> asterisk-r2-request at lists.digium.com escribi?:
>>  
>> Send asterisk-r2 mailing list submissions to
>> asterisk-r2 at lists.digium.com
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://lists.digium.com/mailman/listinfo/asterisk-r2
>> or, via email, send a message with subject or body 'help' to
>> asterisk-r2-request at lists.digium.com
>> 
>> You can reach the person managing the list at
>> asterisk-r2-owner at lists.digium.com
>> 
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of asterisk-r2 digest..."
>> 
>> 
>> Today's Topics:
>> 
>>    1. Re: Invalid CAS (Moises Silva)
>>    2. Re: Invalid CAS (Anton Krall)
>>    3. R2 over microwave (Anton Krall)
>>    4. Re: R2 over microwave (Vin?cius Fontes)
>>    5. Re: R2 over microwave (Anton Krall)
>>    6. Re: R2 over microwave (Vin?cius Fontes)
>>    7. Re: help!! i cant make outbound calls telco bestel
>>       (vanesa estrada)
>> 
>> 
>> ----------------------------------------------------------------------
>> 
>> Message: 1
>> Date: Mon, 14 Dec 2009 13:12:25 -0500
>> From: Moises Silva <moises.silva at gmail.com>
> <mailto:moises.silva at gmail.com>
>> Subject: Re: [asterisk-r2] Invalid CAS
>> To: asterisk-r2 at lists.digium.com
>> Message-ID:
>> <c4d05cbe0912141012r48e28bb0v14150992faaacf2b at mail.gmail.com>
>> <mailto:c4d05cbe0912141012r48e28bb0v14150992faaacf2b at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>> 
>> Means there is unexpected/invalid CAS signaling on the line, not sure why
>> though, have seen that when the balun is broken or poor quality.
>> 
>> On Mon, Dec 14, 2009 at 11:33 AM, Anton Krall <antonkrall at gmail.com>
>> <mailto:antonkrall at gmail.com>  wrote:
>> 
>>   
>>  
>>>  
>>> Moy
>>> 
>>> What does this mean:
>>> 
>>> [Dec 14 10:27:01] ERROR[10739]: Chan 12 - Protocol error. Reason =
> Invalid
>>> CAS, R2 State = Idle, MF state = MF Engine Off, MF Group = No Group, CAS
> =
>>> 0x04
>>> [Dec 14 10:27:01] ERROR[10740]: Chan 29 - Protocol error. Reason =
> Invalid
>>> CAS, R2 State = Idle, MF state = MF Engine Off, MF Group = No Group, CAS
> =
>>> 0x04
>>> [Dec 14 10:27:01] ERROR[10739]: MFC/R2 protocol error on chan 12: Invalid
>>> CAS
>>> [Dec 14 10:27:01] ERROR[10740]: MFC/R2 protocol error on chan 29: Invalid
>>> CAS
>>> 
>>> I see no call file... Just this errors and from time to time a sudden
>>> 
>>> [Dec 14 10:28:47] NOTICE[10740]: Far end blocked on chan 30
>>> [Dec 14 10:28:47] NOTICE[10740]: Far end unblocked on chan 30
>>> 
>>> Whats does it mean?
>>> 
>>> My card is a digium so no wanpipe ehere... Im using openr2 1.2.0
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> --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
>>> 
>     