[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:              06-05-2008 10:05 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!).


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

---------------------------------------------------------------------- 
 moy - 06-05-08 10:05  
---------------------------------------------------------------------- 
titogarrido: it seems like you have a faulty line there. Have you tried
talking with telco support to see what they have to say? you just need to
tell them that your line is being blocked once in a while.

asbestoshead: thanks a lot for the wonderful feedback again :),
effectively I need to handle the inalarm state in the zap private
structure, I will do so and update you when done. I believe you had a
similar issue as the one titogarrido is having isn't it? a faulty line in
Ecuador? did the telco fix that? or what did you do? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-05-08 10:05  moy            Note Added: 0087845                          
======================================================================