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


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

---------------------------------------------------------------------- 
 viniciusfontes - 04-30-08 08:01  
---------------------------------------------------------------------- 
A very common scenario is when you connect a two-span card to a PBX and a
telco simultaneously, that way you can intercept both incoming and outgoing
calls and change their routing, for example directing to a VoIP telco or a
SIP phone.

In this case, you need to handle variable-lenght DNIS (from the PBX). In
my test scenario I had two boxes: one with a TE110P card and another with a
Digivoice board, both using MFC/R2.

Then I originated a call from the Digivoice board using DNIS 0215421047000
and ANI 5421047000. The call eventually went through, but only after a long
time. Perhaps chan_zap ignored the end of DNIS tone?

I uploaded a dump of both signallings along with the zapata.conf file
used. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-30-08 08:01  viniciusfontes Note Added: 0086188                          
======================================================================