[asterisk-bugs] [Asterisk 0009506]: problem with CDR record when using AUTOMON fetaure or res_monitor on outgoing calls (phone->*->telco)

noreply at bugs.digium.com noreply at bugs.digium.com
Thu Nov 22 07:06:37 CST 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9506 
====================================================================== 
Reported By:                nenadr
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   9506
Category:                   Resources/res_features
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     confirmed
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Disclaimer on File?:        Yes 
Request Review:              
====================================================================== 
Date Submitted:             04-09-2007 00:33 CDT
Last Modified:              11-22-2007 07:06 CST
====================================================================== 
Summary:                    problem with CDR record when using AUTOMON fetaure
or res_monitor on outgoing calls (phone->*->telco)
Description: 
when i try to use (almost undocumented) option of res_monitor: if you set
monitor format in form of "format:<string>" (i.e. "wav:monitor"),
res_monitor prefixes the monitored file name with <string> and appends that
resulting string to a CDR(userfiled) all by itself, I get warrnings and one
fake CSV CDR record before real CDR record for conversation. please see
description below.

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

---------------------------------------------------------------------- 
 nenadr - 11-22-07 07:06  
---------------------------------------------------------------------- 
I cannot confirm it for 1.4 since I have to stay on 1.2 because almost all
of  my customers still need my support for their 1.2 installations. 
On the other hand I see that bug is now confirmed. 
I'm very interested to see a solution for 1.4 and try to backport it to a
1.2. Unfotunatly I didn't got too far (read it as didn't got anywhere) with
understanding of how CDR works in Asterisk, to be able to find a solution
myself. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-22-07 07:06  nenadr         Note Added: 0074185                          
======================================================================




More information about the asterisk-bugs mailing list