[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
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:              04-30-2008 08:34 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 - 04-30-08 08:34  
---------------------------------------------------------------------- 
It seems the mfcr2_logging option is causing confusion, that is not
supposed to generate logging in /var/log/asterisk/mfcr2, but just to
generate normal Asterisk logging in the console or any file configured in
logger.conf, call files generation in /var/log/asterisk/mfcr2/ is
independent and enabled via the command line: mfcr2 call files on <channel
number>, see the help in the CLI for more info.

Regarding the long time for the call to go thru, the thing is that R2
variants like México and Brazil seem to be very silly, they do not have a
"End of DNIS" signal, but instead rely on the other end timing out. I just
need to decrease the timeout. I will do some testing, update the SVN  repo
for libopenr2 and let you know. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-30-08 08:34  moy            Note Added: 0086190                          
======================================================================