[asterisk-bugs] [Asterisk 0012509]: [patch] MFC/R2 support for chan_zap

Asterisk Bug Tracker noreply at bugs.digium.com
Mon Aug 25 08:02:13 CDT 2008


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:             2008-04-24 01:31 CDT
Last Modified:              2008-08-25 08:02 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!).


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

---------------------------------------------------------------------- 
 (0091687) ecarruda (reporter) - 2008-08-25 08:02
 http://bugs.digium.com/view.php?id=12509#c91687 
---------------------------------------------------------------------- 
Moy,

One more log to you

Channel 40 ( E1-2 ) calling Channel 9 ( E1-1 )

[Aug 25 10:09:22] DEBUG[3212]: chan_zap.c:8610 mfcr2_monitor: Alright,
back to work!
[Aug 25 10:09:22] DEBUG[3214]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
ABCD Raw Rx << 0x09
[Aug 25 10:09:22] DEBUG[3214]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
Bits changed from 0x00 to 0x08
[Aug 25 10:09:22] DEBUG[3214]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
ABCD Rx << [CLEAR FORWARD] 0x08
[Aug 25 10:09:22] DEBUG[3214]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
Call ended
[Aug 25 10:09:22] DEBUG[3214]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
ABCD Tx >> [IDLE] 0x08
[Aug 25 10:09:22] DEBUG[3214]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
ABCD Raw Tx >> 0x09
[Aug 25 10:09:22] NOTICE[3214]: chan_zap.c:1009 zt_r2_on_call_end: MFC/R2
call end on chan 40
[Aug 25 10:09:22] DEBUG[6306]: chan_zap.c:918 zt_r2_get_channel_category:
no MFC/R2 category specified for chan Zap/40-1, using default National
Subscriber
[Aug 25 10:09:22] DEBUG[6306]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
Attempting to make call (ANI=, DNIS=544, category=National Subscriber)
[Aug 25 10:09:22] DEBUG[6306]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
ABCD Raw Rx << 0x09
[Aug 25 10:09:22] DEBUG[6306]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
No change in bits
[Aug 25 10:09:22] DEBUG[6306]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
ABCD Tx >> [SEIZE] 0x00
[Aug 25 10:09:22] DEBUG[6306]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
ABCD Raw Tx >> 0x01
[Aug 25 10:09:22] DEBUG[3212]: chan_zap.c:1152 zt_r2_write_log: Chan 9 -
ABCD Raw Rx << 0x01
[Aug 25 10:09:22] DEBUG[3212]: chan_zap.c:1152 zt_r2_write_log: Chan 9 -
Bits changed from 0x0C to 0x00
[Aug 25 10:09:22] DEBUG[3212]: chan_zap.c:1152 zt_r2_write_log: Chan 9 -
ABCD Rx << [0x00] 0x00
[Aug 25 10:09:22] ERROR[3212]: chan_zap.c:1146 zt_r2_write_log: Chan 9 -
Protocol error. Reason = Invalid CAS, R2 State = Clear Forward Transmitted,
MF state = MF Engine Off, MF Group = Forward Group II
[Aug 25 10:09:22] DEBUG[3212]: chan_zap.c:1152 zt_r2_write_log: Chan 9 -
DNIS = 566, ANI = , Last MF Signal =  
[Aug 25 10:09:22] DEBUG[3212]: chan_zap.c:1152 zt_r2_write_log: Chan 9 -
ABCD Tx >> [IDLE] 0x08
[Aug 25 10:09:22] DEBUG[3212]: chan_zap.c:1152 zt_r2_write_log: Chan 9 -
ABCD Raw Tx >> 0x09
[Aug 25 10:09:22] ERROR[3212]: chan_zap.c:959 zt_r2_on_protocol_error:
MFC/R2 protocol error on chan 9: Invalid CAS
[Aug 25 10:09:22] DEBUG[3214]: chan_zap.c:8608 mfcr2_monitor: No one
requires my monitoring services :-(
[Aug 25 10:09:30] DEBUG[6306]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
calling callback on chan 40
[Aug 25 10:09:30] WARNING[6306]: chan_zap.c:1143 zt_r2_write_log: Chan 40
- Seize Timeout Expired!
[Aug 25 10:09:30] ERROR[6306]: chan_zap.c:1146 zt_r2_write_log: Chan 40 -
Protocol error. Reason = Seize Timeout, R2 State = Seize Transmitted, MF
state = MF Engine Off, MF Group = Forward MF init
[Aug 25 10:09:30] DEBUG[6306]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
DNIS = 544, ANI = , Last MF Signal =  
[Aug 25 10:09:30] DEBUG[6306]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
ABCD Tx >> [IDLE] 0x08
[Aug 25 10:09:30] DEBUG[6306]: chan_zap.c:1152 zt_r2_write_log: Chan 40 -
ABCD Raw Tx >> 0x09
[Aug 25 10:09:30] ERROR[6306]: chan_zap.c:959 zt_r2_on_protocol_error:
MFC/R2 protocol error on chan 40: Seize Timeout
[Aug 25 10:09:30] DEBUG[3212]: chan_zap.c:1152 zt_r2_write_log: Chan 9 -
ABCD Raw Rx << 0x09
[Aug 25 10:09:30] DEBUG[3212]: chan_zap.c:1152 zt_r2_write_log: Chan 9 -
Bits changed from 0x00 to 0x08
[Aug 25 10:09:30] DEBUG[3212]: chan_zap.c:1152 zt_r2_write_log: Chan 9 -
ABCD Rx << [IDLE] 0x08
[Aug 25 10:09:30] NOTICE[3212]: chan_zap.c:1168 zt_r2_on_line_idle: Far
end unblocked on chan 9
[Aug 25 10:09:30] DEBUG[6306]: chan_zap.c:3005 zt_hangup: disconnecting
MFC/R2 call on chan 40
[Aug 25 10:09:30] DEBUG[6306]: chan_zap.c:1021 zt_r2_update_monitor_count:
At least one device needs monitoring, let's wake up that lazy bastard. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-25 08:02 ecarruda       Note Added: 0091687                          
======================================================================




More information about the asterisk-bugs mailing list