[Home]

Summary:ASTERISK-01295: registering new g729 key causes failure with safe_asterisk
Reporter:gr0k (gr0k)Labels:
Date Opened:2004-03-25 17:39:47.000-0600Date Closed:2011-06-07 14:00:45
Priority:BlockerRegression?No
Status:Closed/CompleteComponents:Core/Configuration
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:We had a key for 4 channels, we needed more so we ordered a new key with 8 channels.  Registered the new key and the registration reported no problems.  However when starting asterisk with the "safe_asterisk" command, the server appears to start, but doesn't function and when I connect to the console with "asterisk -vvvrc" I get the following messages scrolling over and over again:

Mar 25 15:17:12 WARNING[1024]: codec_g729b.c:202 lintog729_new: No available g729 resources for channel 0
Mar 25 15:17:12 WARNING[1024]: codec_g729b.c:342 lintog729_framein: G729 resources are not allocated, exiting
Mar 25 15:17:12 WARNING[1024]: codec_g729b.c:202 lintog729_new: No available g729 resources for channel 0
Mar 25 15:17:12 WARNING[1024]: codec_g729b.c:342 lintog729_framein: G729 resources are not allocated, exiting

I am able to get it started and working with the "asterisk -vvvc" command.  However I do notice the following warning:

[codec_g729b.so] => (Annex B (floating point) G.729/PCM16 Codec Translator)
== Detected 8 licensed G.729 transcoders
Mar 25 15:19:49 WARNING[1024]: translate.c:219 calc_cost: Translator 'g729tolinb' does not produce sample frames.

I am running latest cvs as of:

Asterisk CVS-03/25/04-14:34:04
Comments:By: gr0k (gr0k) 2004-03-25 18:58:03.000-0600

I found a similar bug reported at http://bugs.digium.com/bug_view_page.php?bug_id=0000303

However none of the suggestions in that report have worked for me.
By: Mark Spencer (markster) 2004-03-25 20:20:03.000-0600

It is well known that you cannot run G.729 in console mode, and unfortunately as this is binary code from voiceage, and they refuse to fix it, there is nothing we can do.  

However, instead of running safe_asterisk you can run asterisk from init by addintg the following line to your /etc/inittab:

a:2345:respawn:/usr/sbin/asterisk -vvvgc < /dev/tty9 >&/dev/tty9
By: gr0k (gr0k) 2004-03-26 10:42:10.000-0600

Just wanted to add more information to this issue.  I noticed on the voip-info.org wiki that someone suggested rebooting the server to make sure the new g729 codec is seen.  Well I rebooted and sure enough that fixed the problem and safe_asterisk starts up normally again.

edited on: 03-26-04 09:32
By: mwood (mwood) 2004-03-26 10:45:51.000-0600

It's good that it worked self out. I am closing this since it is not actually a bug.
By: Paul Cadach (pcadach) 2004-03-29 10:24:02.000-0600

Reminder sent to markster

The same story without cleaning shared memory segment by VoiceAge's codec. Server reboot was required to clean out SHMs.

I'd sent to you my suggestion needs to be added to safe_asterisk to clean-out all unattached SHMs before starting Asterisk.