app_meetme.c: Unable to write frame to channel SIP/

[spaquet]

After reducing load to an average 25% on my Asterisk server (Vicidial and Lighttpd are running on a separate server) I still have the following warning from time to time.

[Oct 30 18:31:56] WARNING[23179] app_meetme.c: Unable to write frame to channel SIP/Telco-09c9bc10

At first I though this was due to load, but now that load is very low on my server I do think this error is due to something else, but what.

One of my guess is priority inversion with an other process since all vicidial perl scripts are running on the server.

For that reason I moved mp3 compression to once a day when there is no production on the server.

But I let mixing of -in and -out.wav file to happen every 3 minutes. However, I do not see any correlation between this event and the warning which seems to occur randomly on the server.

I assume there might be an other process that leads to this error.

Any help to make Asterisk the top level priority process on the server is welcomed.

Bests

[williamconley]

Hello spaquet!

Please post your complete setup when you ask a question, especially when it refers to a specific "bug-like" flaw such as this. If you do, it is much more likely that someone who recognizes it will be able to help you out. So post your Vicidial version (with build), Asterisk version and your installation method (including OS with version), any Other Software that may be installed in the box. Hardware would be nice as well (CPU Brand Model and speed, RAM, HD, and it's a good idea to name your Motherboard and NIC if you can).

If you put this information into your signature (on one line) you can forget about it until it changes and it will ALWAYS be available for those looking at your questions.

Remember that we are all volunteers here, and sometimes we only have time to glance at a question and if it doesn't "click", we move on. Give more technical background information, and you're more likely to get a "click".

that being said: you also did not mention whether this even has an effect on call quality or coincides with ANY other event in the system (disconnected call, misdirected call, static or popping noise ...).

If it doesn't affect call quality, it could merely be a "Notice" that's poorly named (as Warning instead). It could also be that there are issues with your network connection or pathway to your provider, in no way related to Vicidial itself or even your server for that matter, just your server notifying you that the problem exists.