similar to: g729 codec + kernel upgrade

Hi there, im having some problems with my asterisk box, it seems codec is the principal cause of it. Reading in some forums i found that i can get the new codec_g729 from ftp://ftp.digium.com/pub/telephony/asterisk/g729/new_codec_binary/codec_g729b.so i checked it but the directory new_codec_binary doesnt exist. Anybody knows where can i found it?? Thanks for your help. Carlos Andres Medina

I am having some problems with g729 with SIP and ZAP channels. 1) I have two g729 licences. Very frequetnly (I don?t know what triggers the error) I get the following warnings and error when I try to place a call via SIP to my X100P. The only way to get out of this is through a restart of *. When the error ocurrs there are no other calls in place. Any ideas? Error Opening channel:2 not

hi just after talking to Jeremy, I downloaded the source he's using and compiled. core dump! This was without gatekeeper: (gdb) bt #0 0x40141118 in mallopt () from /lib/libc.so.6 #1 0x401400fc in malloc () from /lib/libc.so.6 #2 0x405e981b in PAbstractArray::SetSize(int) () from /usr/src/pwlib/lib/libpt_linux_x86_r.so.1 #3 0x405ed006 in PString::SetSize(int) () from

Hello, I have that problem with codec G729. Please can somebody help me! WARNING[16384]: File codec_g729b.c, Line 413 (load_module): Unable to initialize va stuff: -1 == Detected 4 licensed G.729 transcoders WARNING[16384]: File translate.c, Line 219 (calc_cost): Translator 'g729tolinb' does not produce sample frames. == Registered translator 'g729tolinb' from format G729A to

I want use iLBC and have following in mind, please help me is it possible ? ISDN <-----(ALAW)-----> * <-----(ALAW)-----> SNOM SIP??<-----(iLBC)----->?*?<-----(ALAW)----->?SNOM 1. ISDN incoming codec is ALAW SNOM codec should be ALAW (can't be iLBC because a lack of codec). 2. SIP incoming codec should be iLBC (snom is ALAW). 3. SIP outgoing codec should be iLBC /snom

If I have a resource called ''assets'' then I get for free a bunch of helpers, like assets_path new_asset_path and so forth, right? I would like to be able to create a call to one of these on the fly when I only find out the name of the resource at run time. For example I would like to do this: resource_name = "assets" resource_path(resource_name, method => :new)

Im having an issue that seems to only happen when trying to use a transaction. Ive used transactions many times in the past and Im at a loss as to why im getting the stack level too deep problem. SystemStackError - stack level too deep: actionpack (3.2.13) lib/action_dispatch/middleware/reloader.rb:70:in `'' I have a StackOveflow with more detail -

Virtio-mem managed memory is always detected and added by the virtio-mem driver, never using something like the firmware-provided memory map. This is the case after an ordinary system reboot, and has to be guaranteed after kexec. Especially, virtio-mem added memory resources can contain inaccessible parts ("unblocked memory blocks"), blindly forwarding them to a kexec kernel is

Virtio-mem managed memory is always detected and added by the virtio-mem driver, never using something like the firmware-provided memory map. This is the case after an ordinary system reboot, and has to be guaranteed after kexec. Especially, virtio-mem added memory resources can contain inaccessible parts ("unblocked memory blocks"), blindly forwarding them to a kexec kernel is

On 29.04.20 18:08, David Hildenbrand wrote: > Some paravirtualized devices that add memory via add_memory() and > friends (esp. virtio-mem) don't want to create entries in > /sys/firmware/memmap/ - primarily to hinder kexec from adding this > memory to the boot memmap of the kexec kernel. > > In fact, such memory is never exposed via the firmware (e.g., e820), but > only

On 29.04.20 18:08, David Hildenbrand wrote: > Some paravirtualized devices that add memory via add_memory() and > friends (esp. virtio-mem) don't want to create entries in > /sys/firmware/memmap/ - primarily to hinder kexec from adding this > memory to the boot memmap of the kexec kernel. > > In fact, such memory is never exposed via the firmware (e.g., e820), but > only

I have Now a G729 codec license and when i start it comes: [format_g729.so] => (Raw G729 data) == Registered file format g729, extension(s) g729 [app_datetime.so] => (Date and Time) == Registered application 'DateTime' [codec_g729b.so] => (Annex B (floating point) G.729/PCM16 Codec Translator) sh: line 1: tmp: Is a directory rm: cannot remove `tmp': Is a directory

Hey all, Does anyone know what this means? I was running asterisk fine. Installed it on a new pc and I am using the g729b. codec that is optional. I ran the install for the codec it went ok but when I run askterisk via asterisk -vvvgc it gives me this error anyone know? I make sure I entered in the correct reg number. I followed the steps correctly. Too Registration error! Please try

>> Now, let's clarify what I want regarding virtio-mem: >> >> 1. kexec should not add virtio-mem memory to the initial firmware >> memmap. The driver has to be in charge as discussed. >> 2. kexec should not place kexec images onto virtio-mem memory. That >> would end badly. >> 3. kexec should still dump virtio-mem memory via kdump. > > Ok,

Rumor on the IRC channel has a bug being fixed in the g729.so codec that was causing some hangups under certain circumstances. I see that codec_g729b.so in the ftp://ftp.digium.com/pub/asterisk/g729/ directory has a timestamp of today. Can anyone comment on the advisability of upgrading all of my g729-licensed sites? JT

What is this? chan_iax2.c line 4695 (build_peer): Unable to support trunking on peer 'lamas-tigris' without zaptel timing codec_g729b.c Line 413 (load_module): Unable to initialize va stuff: -1 This is why I can't start asterisk in the background -------------- next part -------------- An HTML attachment was scrubbed... URL:

This series is based on [1]: [PATCH v2 00/10] virtio-mem: paravirtualized memory That will hopefull get picked up soon, rebased to -next. The following patches were reverted from -next [2]: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use As discussed in that thread, they should be reverted from -next already. In theory, if people agree, we could take the first two patches

Hi all CentOS users, I have writing shell script for check oracle processes in real time and alert with e-mail. I read script like below NUMBEROFPRO=/oracle/10.2.0/db_1/bin/sqlplus / as sysdba <<EOF1 |grep processes|awk '{print $2}' SELECT resource_name,current_utilization,limit_value FROM V\$RESOURCE_LIMIT WHERE RESOURCE_NAME IN ('processes','sessions'); quit EOF1

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where