[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:              06-05-2008 19:24 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!).


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

---------------------------------------------------------------------- 
 heliocoelhojr - 06-05-08 19:24  
---------------------------------------------------------------------- 
Hi:

  I'm trying to take this version for a spin but I'm seeing the same issue
that was reported by titogarrido. 
  My E1 is from Oi/Telemar and all the setups I've seen so far are for
Embratel's E1s. There's a difference between them because using unicall 
Embratel is protocol variant br,20,4,8 and Telemar is br,20,20. But I'm
not
an expert in the field... :)

The channels are recognized and asterisk is able to answer calls, but they
soon hang up.

Here a snip from the logfile:

[Jun  5 21:13:12] NOTICE[18191] chan_zap.c: New MFC/R2 call detected on
chan 14.
[Jun  5 21:13:15] NOTICE[18191] chan_zap.c: MFC/R2 call offered on chan
14. DNIS = 1500, ANI = 24222376006, Category = National Subscriber
[Jun  5 21:13:16] NOTICE[18191] chan_zap.c: MFC/R2 call has been accepted
on chan 14
[Jun  5 21:13:28] NOTICE[18191] chan_zap.c: Far end unblocked on chan 29
[Jun  5 21:13:28] NOTICE[18191] chan_zap.c: Far end blocked on chan 29
[Jun  5 21:13:32] ERROR[18191] chan_zap.c: Chan 14 - Protocol error.
Reason = Invalid CAS, R2 State = Clear Back Transmitted, MF state = MF
Engine Off, MF Group = Backward Group B
[Jun  5 21:13:32] ERROR[18191] chan_zap.c: MFC/R2 protocol error on chan
14: Invalid CAS
[Jun  5 21:13:32] NOTICE[18191] chan_zap.c: New MFC/R2 call detected on
chan 14.
[Jun  5 21:13:32] NOTICE[18191] chan_zap.c: Chan 14 - Far end
disconnected. Reason: Normal Clearing
[Jun  5 21:13:32] NOTICE[18191] chan_zap.c: MFC/R2 call disconnected on
chan 14
[Jun  5 21:13:32] NOTICE[18191] chan_zap.c: MFC/R2 call end on chan 14

nice work, congratulations.

Best Regards,
Helio. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-05-08 19:24  heliocoelhojr  Note Added: 0087877                          
======================================================================