[asterisk-bugs] [Asterisk 0012509]: [patch] MFC/R2 support for chan_zap

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12509 
====================================================================== 
Reported By:                moy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12509
Category:                   Channels/chan_zap/NewFeature
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 114097 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-24-2008 01:31 CDT
Last Modified:              07-02-2008 17:00 CDT
====================================================================== 
Summary:                    [patch] MFC/R2 support for chan_zap
Description: 
Here we go. This is my first try to give R2 support to chan_zap. I'm sure I
am missing locks and/or features here and there but I have tested it
internally with success with a considerable amount of concurrent channels
(64). That's the best I can do with the hardware I currently have (more
coming!).


====================================================================== 

---------------------------------------------------------------------- 
 asbestoshead - 07-02-08 17:00  
---------------------------------------------------------------------- 
Oh, my script to check for broken lines was broken -- I had tons. With a
timeout of 8000 ms I still get timeouts.

Now I've got a cron job to find broken lines (rxbits == 1 when txbits ==
9) and block them each for five seconds using "mfcr2 set blocked", then
idle them with "mfcr2 set idle". It looks like it actually takes only two
seconds to get the lines back. Works pretty well, thanks a lot.

When the lines come back I see this error, but it's benign:

ERROR[11292]: chan_zap.c:1476 in zt_r2_write_log: Chan 28 - Protocol
error. Reason = Invalid R2 state, R2 State = *Unknown*, MF state = MF
Engine Off, MF Group = No Group 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-02-08 17:00  asbestoshead   Note Added: 0089628                          
======================================================================