[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
Wed Nov 7 13:44:50 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.2.17
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: Yes
Request Review:
======================================================================
Date Submitted: 04-09-2007 00:33 CDT
Last Modified: 11-07-2007 13:44 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.
======================================================================
----------------------------------------------------------------------
qwell - 11-07-07 13:44
----------------------------------------------------------------------
Has anybody confirmed that this is an issue in 1.4?
Issue History
Date Modified Username Field Change
======================================================================
11-07-07 13:44 qwell Note Added: 0073320
======================================================================
More information about the asterisk-bugs
mailing list