On Tue, Feb 8, 2011 at 9:40 AM, Thomas Przyklenk <[email protected]> wrote: > Am 08.02.11, schrieb Douglas Hubler <[email protected]>: > What version of sipXecs are you using?
^----- Still would like an answer here. Be sure to run yum update to get latest. Please report back results of rpm -qa | grep sipxecs > On Tue, Feb 8, 2011 at 8:52 AM, Thomas Przyklenk >> I tried to create my own queue, but in this tries I used the >> default_queue. >> Yes, the specified value for Queue field match the one configured in >> openACD >> UI. Even if you got the queue's horribly mis-configured, i would think you would still hear the MoH > If using latest 0.0.4.5.2 check for errors > /var/log/sipxpbx/freeswitch.log > /var/log/sipxpbx/openacd/*.log > > If using 4.4 check for errors > /var/log/sipxpbx/freeswitch.log > /opt/openacd/*.log > > 15:31:43.444262 [WARNING] <0.233.0>@sipxplugin_poller:80 No Command to > execute > 15:31:53.445255 [WARNING] <0.233.0>@sipxplugin_poller:80 No Command to > execute > 15:32:03.446241 [WARNING] <0.233.0>@sipxplugin_poller:80 No Command to > execute > 15:32:04.252275 [DEBUG] <0.620.0>@freeswitch_media_manager:561 recieved > event '"edb25c0f-1ff2-42f8-9e1d-4dcede13d8df"' from c node. > 15:32:11.759427 [DEBUG] <0.620.0>@freeswitch_media_manager:561 recieved > event '"25f13c74-4176-402d-9e98-16258f1e0001"' from c node. > 15:32:13.447256 [WARNING] <0.233.0>@sipxplugin_poller:80 No Command to > execute > 15:32:23.448257 [WARNING] <0.233.0>@sipxplugin_poller:80 No Command to > execute > 15:32:33.449251 [WARNING] <0.233.0>@sipxplugin_poller:80 No Command to > execute looks ok . NOTE: in the latest code i changed "No Command to execute" to a DEBUG level. what about freeswitch log? _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
