[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-15-2008 15:54 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 - 07-15-08 15:54  
---------------------------------------------------------------------- 
korihor: thanks for the patch :)

Regarding by-passing B/II signals, I already added half-support for that,
I accept that from the forward side, but not yet from the backward. We need
to add some simple code for a new option in zapata.conf, something like
immediate_accept=yes|no and then a new API to openr2 like
openr2_set_immediate_accept(r2context, 1|0); then openr2 will send the
proper signal to by-pass the GB/II stuff. You can take a look at
src/r2proto.c, I named this signal as
mf_ga_tones.address_complete_charge_setup, we just need to send that signal
on variants that support when the new API openr2_set_immediate_accept is
used to configure the context.

You have 2 options.

1. Either you wait for me to add it, I expect to have some time this
weekend to do so.

2. Add it yourself and send me a patch. However, if the patch covers
things in chan_zap.c you will need to sign Digium's disclaimer.

Thanks! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-15-08 15:54  moy            Note Added: 0090311                          
======================================================================