[asterisk-bugs] [Asterisk 0017508]: G729 codecs not being released

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17508 
====================================================================== 
Reported By:                warlock52
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17508
Category:                   Codecs/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.2.9-rc3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 not fixable
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-06-15 19:14 CDT
Last Modified:              2010-06-15 20:26 CDT
====================================================================== 
Summary:                    G729 codecs not being released
Description: 
I have just installed * 1.6.2.9-RC3 with 90 digium G729 licenses and have a
setup of 50 Polycom Phones that all use G729 as well as an IAX2 trunk to
another Asterisk that also uses G.729. I have a reasonably high call volume
and after about 1 hour of operation no more calls can be made because the
G729 Encoder licenses show 90 in use and decoders are between 10 and 30.
The only way to get calls to be processed again is to restart Asterisk.

I had exactly the same setup with * V1.4 with which I had absolutely no
problem, but I needed MFCR2 support with a newly installed E1 which is why
I had to move to 1.6 which supports openr2 natively.

Please let me know what else you would need to diagnose this because I
cannot continue like this for long.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-15 20:26 pabelanger     Resolution               open => not fixable 
======================================================================