[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-08-25 01:58 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!).


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

---------------------------------------------------------------------- 
 (0091682) moy (reporter) - 2008-08-25 01:58
 http://bugs.digium.com/view.php?id=12509#c91682 
---------------------------------------------------------------------- 
ecarruda: thanks for testing! :)

As of the protocol errors. You seem to have 2 issues.

The first one is reported as a "seize timeout", which means the other side
did not  attended our request for starting a call. I cannot think of a good
reason for that to happen. For that error I require the call logs (see
mfcr2_call_files configuration in zapata.conf/chan_dahdi.conf)

The second error is much more easier to fix. Brazilian MFC/R2 variant
handles a "Forced Release" that I have not seen in any other country, I
have a patch for that and I will try to include it this tuesday.

Along with the patch for "Forced Release" for Brazil, I plan to merge all
the changes from Asterisk trunk, including chan_dahdi changes, which means,
openr2 will work now with chan_dahdi in 1.6 and not chan_zap, do you have a
problem testing with DAHDI instead? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-25 01:58 moy            Note Added: 0091682                          
======================================================================