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

[Asterisk Bug Tracker]

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:             2008-04-24 01:31 CDT
Last Modified:              2008-10-09 15:40 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!).


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

---------------------------------------------------------------------- 
 (0093422) PTorres (reporter) - 2008-10-09 15:40
 http://bugs.digium.com/view.php?id=12509#c93422 
---------------------------------------------------------------------- 
We have been testing too with very good results for about 20+ days on 2
servers , 
TE405 we had 4 E1 working fine all with R2 until our client asked to
switch 2 of them to ISDN , after tweaking the timing sources it seemed to
work fine for a while, 
however this one trunk -still R2- started to show a problem similar to
ecarruda last post... on irregular intervals we can see ( sometimes as
short as 4 seconds to about 1 minute )

chan_zap.c:1152 zt_r2_write_log: Chan 32 - Alarm Raised
chan_zap.c:948 zt_r2_on_hardware_alarm: Zap alarm on chan 32.
for all channels simultaneously for that 'span' and then alarms are
cleared almost instantly...

All incoming calls are terminated, 'InAlarm=1' is set for all channels and
never cleared until restart ( dialing out fails with CHANISUNAVAIL )

We changed the timing source to 1 for this span (changing the others to
2,3,4 ) 
this went away but one of the isdns won't sync anymore 

any ideas ? , or what did ecarruda mean by 'disabling timing source'  ? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-09 15:40 PTorres        Note Added: 0093422                          
======================================================================