conf_run issue

[rrb555]

Hi,
vicibox server
is there any of you having issues with this?

cli output
[Jan 6 14:26:14] WARNING[22049]: app_meetme.c:2463 conf_run: Unable to write frame to channel Local/8600053@default-98e6,2

I receive that warning a lot. and not sure why

please anyone help

thanks

[williamconley]

if it does not happen when there is a "problem", it's normal. if it happens when you drop a call, then you should worry about it.

[rrb555]

it happened during drop calls. should i re-install? i am thinking about that now. and maybe use Vicibox Redux 3.1.13 installer. not sure why this happens as this is a very new server.

[williamconley]

you are likely having a network issue somewhere that causes your agent to drop off.

is this between you and the agent or you and the prospect?

[rrb555]

this is between me and the agent. this happened when no one can make out going calls. also experienced to other two agents.

there are a total of 8 agents calling using manual dial with force recordings/

btw, already reinstalled, backup and restored asterisk database, did zypper refresh && zypper up for opensuse os. hope new server would be alright.

[williamconley]

try wireshark (free!!) to see if/when you are dropping packets between agent/server.

also: server load during this?

[rrb555]

had a problem again calling out to customers. I had to restart my server, after that all calls are now going through,.

one thing I noticed was the fail2ban running on the background stopped working. not sure why. I have tried running it again and says started but when I checked its status it is unused.

should this be a fail2ban application issue? should I remove/uninstall it or leave it there for the meantime?

I experienced this issue when 8 agents went back from lunch break and started calling out again.

when I checked "top" server load 0.12 0.05 0.01

[williamconley]

your system specs mention nothing about fail2ban. did you install it or was it included in goautodial?

i do not recommend fail2ban, i recommend iptables with allowed ip only. (there have been many posts on the topic ...)

[rrb555]

the issue is from my new single server Vicibox Redux 3.1.14 installation.

fail2ban comes with it, I have just enabled it.

For some reason agents unable to call after a break, needed to reboot server in order to call out again

[williamconley]

fair enough. but fail2ban is not "set up" by default. did you turn it on? fail2ban has the capacity to be supercool software ... or mess up your life. turning it on without a full understanding of what it can/will do is not generally a good idea.

so ... what did you do to configure/activate/etc fail2ban?

Also: Consider checking your fail2ban logs ... perhaps you have an agent doing things at lunch that fail2ban does not appreciate?

[rrb555]

enabled the ssh iptables only, and unban the local IP Address in jail.conf

i am not sure why fail2ban stopped working as there are no brute force on ssh.

I have already uninstalled fail2ban now.

hoping now that the server will work well this time.

is there any logs should i be checking?

[williamconley]

the fail2ban logs?

[rrb555]

2012-01-09 09:42:58,024 fail2ban.server : INFO Changed logging target to /var/log/fail2ban.log for Fail2ban v0.8.4
2012-01-09 09:45:52,173 fail2ban.server : INFO Exiting Fail2ban
2012-01-09 09:45:52,374 fail2ban.server : INFO Changed logging target to /var/log/fail2ban.log for Fail2ban v0.8.4
2012-01-09 09:45:52,375 fail2ban.jail : INFO Creating new jail 'ssh-iptables'
2012-01-09 09:45:52,375 fail2ban.jail : INFO Jail 'ssh-iptables' uses poller
2012-01-09 09:45:52,466 fail2ban.filter : INFO Added logfile = /var/log/messages
2012-01-09 09:45:52,466 fail2ban.filter : INFO Set maxRetry = 5
2012-01-09 09:45:52,467 fail2ban.filter : INFO Set findtime = 600
2012-01-09 09:45:52,468 fail2ban.actions: INFO Set banTime = 6000000000000
2012-01-09 09:45:52,508 fail2ban.jail : INFO Jail 'ssh-iptables' started
2012-01-09 09:46:43,904 fail2ban.jail : INFO Jail 'ssh-iptables' stopped
2012-01-09 09:46:43,905 fail2ban.server : INFO Exiting Fail2ban
2012-01-09 09:46:44,077 fail2ban.server : INFO Changed logging target to /var/log/fail2ban.log for Fail2ban v0.8.4
2012-01-09 09:46:44,078 fail2ban.jail : INFO Creating new jail 'ssh-iptables'
2012-01-09 09:46:44,078 fail2ban.jail : INFO Jail 'ssh-iptables' uses poller
2012-01-09 09:46:44,088 fail2ban.filter : INFO Added logfile = /var/log/messages
2012-01-09 09:46:44,089 fail2ban.filter : INFO Set maxRetry = 5
2012-01-09 09:46:44,090 fail2ban.filter : INFO Set findtime = 600
2012-01-09 09:46:44,091 fail2ban.actions: INFO Set banTime = 6000000000000
2012-01-09 09:46:44,128 fail2ban.jail : INFO Jail 'ssh-iptables' started

[rrb555]

I have already removed Fail2ban on my Vicibox Server yet I am still experiencing issue "unable to hear by the customer" when all agents went to break and start dialing out again.

Would this issue started with the agents workstation? As my the current setup all agents PC are using Opensuse as OS and XLITE running in Wine.
- I am having issue in other linux softphone (twinkle) to where it doesn't recognize the headset agents are using.

[williamconley]

I have already removed Fail2ban on my Vicibox Server yet I am still experiencing issue "unable to hear by the customer" when all agents went to break and start dialing out again.

have to catch it when ONE is having a problem and send in the asterisk cli or other information to resolve the issue with a single call. general info won't help to solve anything technical ... except by getting general statements in return: turn off your firewall when it happens next time and see if that resolves the issue. also please describe the network(s) involved. is the vicidial system local to the agents? do you have a router between vicidial and the internet? etc

Would this issue started with the agents workstation? As my the current setup all agents PC are using Opensuse as OS and XLITE running in Wine.
- I am having issue in other linux softphone (twinkle) to where it doesn't recognize the headset agents are using.

sorry, but that is purely non-vicidial. try windows ... try another headset ... try another linux distro ... try another softphone ...

hopefully another call center manager will notice this and post ... but we've never had that problem.

[rrb555]

Server has two NIC, with public IP address and local IP address, to which it's default ip address is local.

firewall open ports are http, https and ssh

I turned off the server every time all the 8 agents are done calling for the day.
open it every morning when they are about to dial again with no issues. issue experienced when they get back from lunch break (1 hour break). I tend to see the VOIP disconnects to server when issue is experiencing (lagged first then unreachable to reachable in asterisk cli). VOIP has no issue and even for internet since when i rebooted the server all went back to normal. this issue almost happens everyday so I really doubt that it is VOIP nor internet.

maybe I am missing something, any recommendation would greatly help
I am planning to install Vicibox 3.1.13 to check

My machine are composed of Core i7, 12G RAM, 1 TB 7200 rpm, 2 NIC, Asus motherboard

[williamconley]

I tend to see the VOIP disconnects to server when issue is experiencing (lagged first then unreachable to reachable in asterisk cli).

show this! i know YOU can see it, but your generalized statements do not allow technicians to answer your technical support request. show a line or two of the offending commands from the cli at least.

also: check your firewall to see if you are being attacked at this time. check your AGENTS to see which one is using limewire on the lunchbreak.

VOIP has no issue and even for internet since when i rebooted the server all went back to normal.

above: VOIP disconnects, here: VOIP has no issue ...? I'm assuming you mean that VOIP has no issue AFTER the reboot (please correct me if I'm wrong). Before rebooting next time: check "htop" (install it if you have to) and find out what processes are running that use a lot of CPU. Also check your server load (also in htop). Check again AFTER the reboot and see if there is a difference that you can post.

this issue almost happens everyday so I really doubt that it is VOIP nor internet.

I actually had a room i Orlando that used to drop off every day at about the same time. Just about the time that the room on the floor above them started working. Shared broadband internet. Changing to a Dedicated T1 resolved the problem, but cost $$. Never assume what it is ... TEST.

[rrb555]

Experienced again at the start of the shift. 5 agents login.
Network setup:
two internet connections
1st internet to Dialer server and one pc for testing both using public IP
Dialer server are using two NIC one local and one Public
2nd internet for agents PC

VOIP connection has no issue since when I ping it from a test PC it has a stable reply of 200ms unlike with the Dialer server pings was unstable when all agents started dialing out see image

Dialer is still OK when there are only 2 agents dialing.
asterisk connection disconnects to the VOIP IP when all agents started logging and dialing.

in order to fix the issue I had to restart the server again

CLI
[Jan 13 09:20:19] NOTICE[3597] chan_sip.c: Peer 'accela2' is now UNREACHABLE! Last qualify: 211
[Jan 13 09:25:00] NOTICE[3597] chan_sip.c: Peer 'accela2' is now UNREACHABLE! Last qualify: 2124

[williamconley]

VOIP connection has no issue since when I ping it from a test PC it has a stable reply of 200ms unlike with the Dialer server pings was unstable when all agents started dialing out see image

Dialer is still OK when there are only 2 agents dialing.
asterisk connection disconnects to the VOIP IP when all agents started logging and dialing.

pinging from a workstation does not mean your VOIP connection is reliable and capable of a VOIP phone call. Try holding a call directly from your agent's workstation through the voip provider when your vicidial server has a problem and that would be an indicator, but pinging and SIP connections are not equivalent.

Also: It sounds a bit like a few clients who have had issues with their routers.

Just for curiosity: iptables-save ... post the results. Or turn off the iptables firewall instead of rebooting once.

[rrb555]

do you happen to know what this is?
Message from syslogd@VICIdial at Jan 17 09:21:32 ...
kernel:[ 491.513995] Disabling IRQ #16

issue started when i saw that message

[Dovid]

Maybe this is related to:

jira ASTERISK 18760 ?

System wont let me post link yet so go to Jira and figure it out....

[rrb555]

still having the same problem. What I do now is automate a reboot in crontab before agents login.

things I check to know if server will have a problem
1. ping to VOIP server IP are more than 200 ms
2. a single agent can make outgoing calls without any problem but when other agents join them problem are now starting. ping to VOIP server IP increases to 100000ms and more

things I check to know if server are now ok
1. ping to VOIP server IP stabilize at 165 to 170ms
2. all agents can now login and dial simultaneously with no problem
3. server should be use without any long break(sample lunch for 1 hour) in order to utilize good server performance

I hope someone with the same problem read this and help me with my problem.

agents are using OpenSUSE 12.1 as their workstation and linphone for softphone.