AMD

[umop3plsdn]

I feel like i'm spamming the forum =(.... I'm having troubles with AMD i'm in the asterisk console and it keeps spamming -- Got 0ms silence< 2000ms required over and over causing the loadavg to spike seems like it's caught in a loop. Any suggestions?

[xCape]

I am having the exact same issue. Let me know if you find anything out. I ended up lowering the verbosity for asterisk so I could see AMD working.

Thanks.

[umop3plsdn]

I have it configured with the default AMD in my extensions.conf and haven't changed any of those settings. If i dial the extension 8320 from a softphone it goes into an indefinate loop with "-- Got 0ms silence< 2000ms required". Is there a way i could put a failsafe timeout for that extension?

[xCape]

What are your hardware specs?

[umop3plsdn]

a little more headway i did another scratch install to see if it was just my initial install came up with the same results. So from there i dialed the extension 8320 and punched a bunch of dtmf tones and got it to stop which then started playing what sounded to me like a MoH file. I guess i'm wondering if maybe it's confused between MoH and just analyzing for an answering machine. I dunno. It seems like it maybe functioning but being WAY too aggressive with the count cycles.

[umop3plsdn]

i have a p4 core2duo 3.0ghz with 1g of ram and a TE120p. The above happens with no current load on the dialer no users logged in aside from my xlite that i'm dialing extension 8320 with.

[umop3plsdn]

I dont know if this is related at all but we went live without AMD and i keep getting thousands of "Jul 29 12:30:19 WARNING[20533]: format_wav.c:247 update_header: Unable to find our position" All recordings are 0 when this comes up

[umop3plsdn]

alright that last problem i solved it was filling up the ram disk because i altered the cron scripts to not mix the recordings. so everything was stuck... I am still having issues with AMD however.

[umop3plsdn]

some of my recordings exceed the 16M though how do i resize that ramdisk? I do constant call recording btw

[gardo]

You can resize the ramdisk by appending this entry in your /boot/grub/menu.1st:

ramdisk_size=102400

That will increase your ramdisk to 100mb. Change it to whatever size you want.

[umop3plsdn]

really strange answering machine detection works fine for about 10 minutes and it seems like it just hits a certain condition and then spins out of control on the "-- Got 0ms silence< 2000ms" and jumps my load avg to an astronomical level and will not let up even if i wait 30 minutes.

[xCape]

I just posted this on another topic. It may help:

In my extensions.conf, i changed the line:

exten => 8320,1,WaitForSilence(2000,2);
to:
exten => 8320,1,WaitForSilence(2000,2,30);

and this helped my cpu percentage and channel_find_locked warning.

I noticed that a channel would be 'stuck' and stay that way until i restarted asterisk. The 'WatiForSilence' function would be in an infinite loop on the CLI prompt.

This may not be a solution but it helped. I am doing around 4800 outbound calls per hour.

you'll notice the cpu go up, but then it will recover.

[umop3plsdn]

That works for me!! thanks!

[mcargile]

The real issue is that WaitForSilence is broken in asterisk 1.2.

We wrote a fix for this a while ago which is an optional step in the Scratch Install for installing Asterisk. From the sounds of it, the fixed version did not get into the VicidialNOW release.

What is happening without the timeout is that every call going to the answering machine extension is getting stuck till the other end hangs up the call. All your 30 second timeout is doing is making it so that the message is being left after 30 seconds not when the answering machine is done playing it's message.

If you need this feature you will need to recompile asterisk on your system with the fixed version in place.

Our support staff is more than willing to do this for you. Our rate is $200 an hour. For VicidialNOW systems we highly suggest a 2 hour tune up on this system where we fix the known bugs in VicidialNOW and optimize it for your system.

[gardo]

The wait for silence patch is included in VicidialNOW since the first release.

The real issue is that WaitForSilence is broken in asterisk 1.2.

We wrote a fix for this a while ago which is an optional step in the Scratch Install for installing Asterisk. From the sounds of it, the fixed version did not get into the VicidialNOW release.

What is happening without the timeout is that every call going to the answering machine extension is getting stuck till the other end hangs up the call. All your 30 second timeout is doing is making it so that the message is being left after 30 seconds not when the answering machine is done playing it's message.

If you need this feature you will need to recompile asterisk on your system with the fixed version in place.

Our support staff is more than willing to do this for you. Our rate is $200 an hour. For VicidialNOW systems we highly suggest a 2 hour tune up on this system where we fix the known bugs in VicidialNOW and optimize it for your system.

[xCape]

I looked at the updated watiforsilence patch and it is the same as the one I have.

I will probably get support for this system. When we go live.

I was hoping there was not any "known" bugs that you must pay for to fix. Thanks for your information.

[gardo]

There are no known bugs being reported yet for the latest VicidialNOW version (1.1).