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

Asterisk Bug Tracker noreply at bugs.digium.com
Sat Aug 23 23:40:54 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-23 23:40 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!).


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

---------------------------------------------------------------------- 
 (0091672) ecarruda (reporter) - 2008-08-23 23:40
 http://bugs.digium.com/view.php?id=12509#c91672 
---------------------------------------------------------------------- 
Complements Debug Concole:

[Aug 24 01:41:50] DEBUG[23080]: chan_zap.c:1152 zt_r2_write_log: Chan 43 -
ABCD Raw Rx << 0x09
[Aug 24 01:41:50] DEBUG[23080]: chan_zap.c:1152 zt_r2_write_log: Chan 43 -
Bits changed from 0x04 to 0x08
[Aug 24 01:41:50] DEBUG[23080]: chan_zap.c:1152 zt_r2_write_log: Chan 43 -
ABCD Rx << [IDLE] 0x08
[Aug 24 01:41:50] DEBUG[23080]: chan_zap.c:1152 zt_r2_write_log: Chan 43 -
Call ended
[Aug 24 01:41:50] DEBUG[23080]: chan_zap.c:1152 zt_r2_write_log: Chan 43 -
ABCD Tx >> [IDLE] 0x08
[Aug 24 01:41:50] DEBUG[23080]: chan_zap.c:1152 zt_r2_write_log: Chan 43 -
ABCD Raw Tx >> 0x09
[Aug 24 01:41:50] NOTICE[23080]: chan_zap.c:1009 zt_r2_on_call_end: MFC/R2
call end on chan 43
[Aug 24 01:41:54] DEBUG[23729]: chan_zap.c:1152 zt_r2_write_log: Chan 39 -
calling callback on chan 39
[Aug 24 01:41:54] WARNING[23729]: chan_zap.c:1143 zt_r2_write_log: Chan 39
- Seize Timeout Expired!
[Aug 24 01:41:54] ERROR[23729]: chan_zap.c:1146 zt_r2_write_log: Chan 39 -
Protocol error. Reason = Seize Timeout, R2 State = Seize Transmitted, MF
state = MF Engine Off, MF Group = Forward MF init
[Aug 24 01:41:54] DEBUG[23729]: chan_zap.c:1152 zt_r2_write_log: Chan 39 -
DNIS = 266, ANI = , Last MF Signal =  
[Aug 24 01:41:54] DEBUG[23729]: chan_zap.c:1152 zt_r2_write_log: Chan 39 -
ABCD Tx >> [IDLE] 0x08
[Aug 24 01:41:54] DEBUG[23729]: chan_zap.c:1152 zt_r2_write_log: Chan 39 -
ABCD Raw Tx >> 0x09
[Aug 24 01:41:54] ERROR[23729]: chan_zap.c:959 zt_r2_on_protocol_error:
MFC/R2 protocol error on chan 39: Seize Timeout
[Aug 24 01:41:54] DEBUG[23078]: chan_zap.c:1152 zt_r2_write_log: Chan 8 -
ABCD Raw Rx << 0x09
[Aug 24 01:41:54] DEBUG[23078]: chan_zap.c:1152 zt_r2_write_log: Chan 8 -
Bits changed from 0x00 to 0x08
[Aug 24 01:41:54] DEBUG[23078]: chan_zap.c:1152 zt_r2_write_log: Chan 8 -
ABCD Rx << [IDLE] 0x08
[Aug 24 01:41:54] NOTICE[23078]: chan_zap.c:1168 zt_r2_on_line_idle: Far
end unblocked on chan 8
[Aug 24 01:41:54] DEBUG[23729]: chan_zap.c:3005 zt_hangup: disconnecting
MFC/R2 call on chan 39
    -- Hungup 'Zap/39-1'


Sometimes on Channel Hangup i has this error on channels Hangup:

    -- Executing [h at incoming:1] Hangup("Zap/22-1", "") in new stack
  == Spawn extension (incoming, h, 1) exited non-zero on 'Zap/22-1'
  == End MixMonitor Recording Zap/22-1
[Aug 24 01:48:11] DEBUG[24447]: chan_zap.c:3005 zt_hangup: disconnecting
MFC/R2 call on chan 22
[Aug 24 01:48:11] DEBUG[24447]: chan_zap.c:1152 zt_r2_write_log: Chan 22 -
Call ended
[Aug 24 01:48:11] DEBUG[24447]: chan_zap.c:1152 zt_r2_write_log: Chan 22 -
ABCD Tx >> [IDLE] 0x08
[Aug 24 01:48:11] DEBUG[24447]: chan_zap.c:1152 zt_r2_write_log: Chan 22 -
ABCD Raw Tx >> 0x09
[Aug 24 01:48:11] NOTICE[24447]: chan_zap.c:1009 zt_r2_on_call_end: MFC/R2
call end on chan 22
[Aug 24 01:48:11] DEBUG[24447]: chan_zap.c:1021
zt_r2_update_monitor_count: At least one device needs monitoring, let's
wake up that lazy bastard.
    -- Hungup 'Zap/22-1'
  == Parsing '/etc/asterisk/manager.conf': Found
[Aug 24 01:48:11] DEBUG[24642]: chan_zap.c:918 zt_r2_get_channel_category:
no MFC/R2 category specified for chan Zap/22-1, using default National
Subscriber
[Aug 24 01:48:11] DEBUG[24642]: chan_zap.c:1152 zt_r2_write_log: Chan 22 -
Attempting to make call (ANI=, DNIS=204, category=National Subscriber)
[Aug 24 01:48:11] DEBUG[24642]: chan_zap.c:1152 zt_r2_write_log: Chan 22 -
ABCD Raw Rx << 0x09
[Aug 24 01:48:11] DEBUG[24642]: chan_zap.c:1152 zt_r2_write_log: Chan 22 -
No change in bits
[Aug 24 01:48:11] DEBUG[24642]: chan_zap.c:1152 zt_r2_write_log: Chan 22 -
Call started at Sun Aug 24 01:48:11 2008 on chan 22
[Aug 24 01:48:11] DEBUG[24642]: chan_zap.c:1152 zt_r2_write_log: Chan 22 -
ABCD Tx >> [SEIZE] 0x00
[Aug 24 01:48:11] DEBUG[24642]: chan_zap.c:1152 zt_r2_write_log: Chan 22 -
ABCD Raw Tx >> 0x01
[Aug 24 01:48:11] DEBUG[23079]: chan_zap.c:8610 mfcr2_monitor: Alright,
back to work!
[Aug 24 01:48:11] DEBUG[23081]: chan_zap.c:1152 zt_r2_write_log: Chan 53 -
ABCD Raw Rx << 0x01
[Aug 24 01:48:11] DEBUG[23081]: chan_zap.c:1152 zt_r2_write_log: Chan 53 -
Bits changed from 0x04 to 0x00
[Aug 24 01:48:11] DEBUG[23081]: chan_zap.c:1152 zt_r2_write_log: Chan 53 -
ABCD Rx << [0x00] 0x00
[Aug 24 01:48:11] ERROR[23081]: chan_zap.c:1146 zt_r2_write_log: Chan 53 -
Protocol error. Reason = Invalid CAS, R2 State = Clear Forward Transmitted,
MF state = MF Engine Off, MF Group = Forward Group II
[Aug 24 01:48:11] DEBUG[23081]: chan_zap.c:1152 zt_r2_write_log: Chan 53 -
DNIS = 80, ANI = , Last MF Signal =  
[Aug 24 01:48:11] DEBUG[23081]: chan_zap.c:1152 zt_r2_write_log: Chan 53 -
ABCD Tx >> [IDLE] 0x08
[Aug 24 01:48:11] DEBUG[23081]: chan_zap.c:1152 zt_r2_write_log: Chan 53 -
ABCD Raw Tx >> 0x09
[Aug 24 01:48:11] ERROR[23081]: chan_zap.c:959 zt_r2_on_protocol_error:
MFC/R2 protocol error on chan 53: Invalid CAS 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-23 23:40 ecarruda       Note Added: 0091672                          
======================================================================




More information about the asterisk-bugs mailing list