similar to: Digium G.729 codec binaries updated

Hi all, We have already bought 30 Digium G.729 licenses to install in several machines, but Digium only has provided on key to use in registration. We suspect that the registration has assigned the whole 30 licenses to the same server. Do anyone know how to distribute the licenses among several servers? Thanks in advance. -- Arturo D?az Contact me on FWD: 870436 Skype: arturo.diaz.almagro

This evening I posted a new set of Digium G.729 codec modules to our FTP server and web site, for Linux x86 and x86-64 processors. They were built using GCC 4.0.1, and they now report the processor they were optimized for when they are loaded. The previous x86-64 module required a non-standard Asterisk binary configuration, so this was corrected. In addition, there was only a generic version

The x86 and x86_64 Digium G.729 codec binaries have been updated for use with the Asterisk 1.4 beta (which should also work on current svn trunk). Anybody that is using the older modules with the 1.4 beta (or svn trunk newer than several days ago) is strongly encouraged to upgrade immediately, to avoid potential issues. -- Jason Parker Digium

The x86 and x86_64 Digium G.729 codec binaries have been updated for use with the Asterisk 1.4 beta (which should also work on current svn trunk). Anybody that is using the older modules with the 1.4 beta (or svn trunk newer than several days ago) is strongly encouraged to upgrade immediately, to avoid potential issues. -- Jason Parker Digium

Hi all, i have purchased the g.729 codec from digium. The registration was successful. (with the "old" binary) But there're a few questions: - should not the codec listed in the codec list when i enter "show codecs" ? - the codec is named with g729b but if i enter show codecs there is a codec g729a listed also the g729b is not installed. what is the difference between

Digium has released version 3.0.3 of its product registration utility. This is the first version of the registration utility that is compiled against the uClibc C library. A benefit of this transition is that the register binary should run more consistently and reliably across a wider range of Linux distributions. The new versions of 'register' and 'asthostid' can be

The Digium G.729 binary codec modules (both 32-bit and 64-bit), and register tool have been updated for use with the Asterisk 1.4 beta on Solaris. As always, they can be downloaded from http://ftp.digium.com/pub/telephony/asterisk/g729/ -- Jason Parker Digium

The Digium G.729 binary codec modules (both 32-bit and 64-bit), and register tool have been updated for use with the Asterisk 1.4 beta on Solaris. As always, they can be downloaded from http://ftp.digium.com/pub/telephony/asterisk/g729/ -- Jason Parker Digium

I'm asking because I'm planning to install multiple machines from the same image and I need to know what file(s) I need to backup/restore to make sure I don't lose my licences in the process. The only options I can think of are: - There's a config file, though I've seen no mention of it - The actual binary shared library is modified - The system contacts Digium every time you

I have just uploaded Solaris/SPARC G.729 codecs and register tools to our FTP site; they are located with the other non-Linux codecs in the 'unsupported' directory of the g729 subdirectory. There are versions for both Asterisk 1.2 and Asterisk 1.4 in both 32-bit and 64-bit flavors; we will be updating the other 'unsupported' codecs and also producing Solaris/X86 versions some time

I have just uploaded Solaris/SPARC G.729 codecs and register tools to our FTP site; they are located with the other non-Linux codecs in the 'unsupported' directory of the g729 subdirectory. There are versions for both Asterisk 1.2 and Asterisk 1.4 in both 32-bit and 64-bit flavors; we will be updating the other 'unsupported' codecs and also producing Solaris/X86 versions some time

Hi, I purchased a G.729 1 channel codec license from digium. And installed as per the documentation. Then configured the sip.conf to use the new codec. For that, I am added the following entries in sip.conf (via web interface, as i am using asterisknow 1.5) disallow=all allow=g729 allow=ulaw allow=alaw allow=gsm After that, when try to call through the PSTN line I can hear the voice of

I have been reading a number of the past threads about G.729 licensing., about how the registration keys are linked to the network configurations, limited number of registrations etc, etc. Is there no reason why the decoding can't be done in with some Asterisk compatible hardware, so that once the adapter is bought, all licensing issues go away. In that way the owner could fiddle with the

Hi, I am trying to post this again as I am getting no answers and the support@digium.com bounces... (I have searched the whole list and can't find the answer either) I have installed a 5 user license for G.729 and want to route calls through Asterisk from my G.729 phone to Cisco AS5300 also using G729. Both Cisco and the phone connect using this codec if I do not force the call to go

Asterisk 1.2.24 seems to crash repeatedly under any substantial call load (and sometimes without a substantial call load - just one SIP leg is enough to do it) when using the G.729 pre-compiled binaries from: http://asterisk.hosting.lv/ As per: http://www.voip-info.org/wiki-Asterisk+G.729+Licensing Time to crash is variable, but seems to require at least an hour of production performance

This evening I posted a new set of Digium G.729 codec modules to our FTP server and web site, for Linux x86 and x86-64 processors. They were built using GCC 4.0.1, and they now report the processor they were optimized for when they are loaded. The previous x86-64 module required a non-standard Asterisk binary configuration, so this was corrected. In addition, there was only a generic version

Greetings- Was running the Digium FreeBSD g.729 codec until recently when the latest Asterisk bits were obtained via svn: svn checkout http://svn.digium.com/svn/asterisk/trunk asterisk This produced: Checked out revision 30652 This on FreeBSD 6.1-RELEASE Attempting to start asterisk it returns: == Registered custom function URIENCODE [codec_g729a.so]May 27 13:29:59 WARNING[71884]:

Hi, I've been trying to get the G.729a beta codec running with my remote Asterisk box that talks IAX2 to my local Asterisk box. Digium fixed the problem I was having in registering the beta codec, so that now works fine. I've removed the old codec_g729b.so from /usr/lib/asterisk/modules and put in place the codec_g729a.so beta from digium FTP. My CVS build of Asterisk is about a

Hello, I have an asterisk server running with 23 g.729 licenses. I have also purchased a sound file from thevoice.digium.com. I need to covert this file (uLaw, PCM I think) to g.711, g.729 & g.723 for use with an IVR system. Is there a way I can convert the files using the g.729 digium codec? sox? Thanks -Matt -- Matthew S. Crocker Vice President Crocker Communications,

Hello: I got into a trap. As far as I know I do not need to pay any royalties to use G.729b in Romania, so I should have used other drivers. The installation procedure looked difficult so I decided to get one from Digium - it's not that expensive, my time is much more expensive. Made the payment, got they key, downloaded and copied everything as in