[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:              05-26-2008 13:35 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!).


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

---------------------------------------------------------------------- 
 asbestoshead - 05-26-08 13:35  
---------------------------------------------------------------------- 
For Pacifictel in Ecuador (see above, note 0087280) we weren't able to make
calls to some long distance numbers. They were sending us a tone 6 at the
end of DNIS. This sounds almost like the group C from Mexico stuff, but the
telco says they aren't using group C, and the tone 6 just means "call
accepted with charge".

They suggested reconfiguring the Ericsson switch to use CRLM -- this is an
Ericsson-specific E1 variant that Google doesn't know anything about. With
CRLM on their end, I had to switch the variant on our end from ITU to
Brazil. Now we can place calls anywhere. There are a few things that are
odd but not important:

- invalid numbers usually result in a tone 4 in reply to the last digit of
DNIS (still in group A!). libopenr2 says "Invalid Multi Frequency Tone"
- For some busy numbers, we get a tone 2 (in group B) and libopenr2 says
"Invalid Multi Frequency Tone". (For other busy numbers, the line is
actually answered and a recording plays, "The number you have dialled is
occupied".)

The telco says tone 2 means busy with special information and tone 3 means
busy, but we haven't seen a tone 3 from them yet. It's not just openr2 that
gets confused. Even the landlines and cellphones here have trouble with
these tone 4 and tone 2 numbers -- they tend to play ringback and busy at
the same time. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-26-08 13:35  asbestoshead   Note Added: 0087315                          
======================================================================