[asterisk-bugs] [Asterisk 0013513]: Recording transcoded call with Monitor() uses 3 licenses of G.729

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13513 
====================================================================== 
Reported By:                blitzrage
Assigned To:                kpfleming
====================================================================== 
Project:                    Asterisk
Issue ID:                   13513
Category:                   Resources/res_monitor
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 140850 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-09-18 10:24 CDT
Last Modified:              2008-11-24 15:56 CST
====================================================================== 
Summary:                    Recording transcoded call with Monitor() uses 3
licenses of G.729
Description: 
When recording a call with Monitor() in the dialplan where one end is ulaw,
and the other G.729, it appears that Asterisk utilizes 4 licenses of G.729
in a single call. There may be some sort of optimization that could be done
here, or perhaps there is a reason this needs to happen?

My guess is that Asterisk is converting the ulaw to g.729 before it hits
Monitor(), and is then converting it back to .wav for recording?
====================================================================== 

---------------------------------------------------------------------- 
 (0095430) blitzrage (administrator) - 2008-11-24 15:56
 http://bugs.digium.com/view.php?id=13513#c95430 
---------------------------------------------------------------------- 
Suspending this issue as this is a known issue, but there are no plans to
have this issue fixed anytime in the near future. Please reopen when there
is interest in resolving this issue. Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-24 15:56 blitzrage      Note Added: 0095430                          
======================================================================