Sorry again for being late … was enjoying my weekend first time in three weeks.
5th July:It’s 19th day. While entering into the office I noticed pity in receptionist’s voice when she said good morning even without looking at her. I went to the terrace… smoked like a train… smoking normally has a great effect on me, calming me and helping me to think. It didn't do much good this day. Haven’t I tried everything, even those that doesn't make any sense? Nothing worked. To be perfectly honest dudes …I have faced issues before but for some reason this one has me in a state of panic! It’s the same feeling when I get on a plane, or even worse, when I look down from the high building.
Don't worry, I'll get over it. I'll try to approach the situation with determination, confidence... Like a man! I want my mommy!!!!
I was stuck with William’s idea that day “it is more likely a networking issue” ... But what does that mean in real life –LOL. Ok, if it means test every visible network component in this place, THEN SO BE IT!
Next time the error started rolling on the CLI I picked up the error message ….
- Code: Select all
[Jul 5 15:39:39] WARNING[3508]: app_meetme.c:2463 conf_run: Unable to write frame to channel Local/8600063@default-e92c,2
Looked for SESSION ID 8600063 in Real Time Report and found the STATION ID, the guy was on a manual call. I saw autodialer was slowing down its pace, I understood it was going to stop within few seconds. Logged into DB and ran gmcust3’s savior SQL query a few times in panic. The very first time I ran it I found around 350 rows were affected. Autodialer took its pace but agents were not getting calls. Warnings were still rolling on the CLI almost 50 in a second. I wanted to hit that guy in the nose … but… hang on a second...doesn't he look stronger than me? No problem, haven’t I read ‘computer is mightier than the sword’? …yeah, I can kick him out of this campaign …AND SO I DID…in Matt’s language it’s ‘EMERGENCY LOG AGENT OUT’. Voila …warnings stopped and agents started to get calls. Why I did not do that in all those days??? I stood up and yelled like Tarzan, female members of the room thought this was a little amusing. I turned to them and said, “Common sense is a wonderful thing...Use it”.
A SWITCH GONE WILD!!!!!!!!!
Found some strange behavior of that switch. There were two ports that caused the warnings on CLI when manual calls were being made, the third port, doesn’t generate any warning on CLI but was causing vicidial_auto_calls table to fill up with NULL channels …a lot of them, over 100 in few seconds and causing autodialer to slow down and eventually stop it in the span of two minutes.
6th JulyReplaced that switch .... and I am the happiest man in this world.
If it wasn't for this forum, I'd be foaming at the mouth, surrounded by rubber walls and wearing a long sleeved jacket by now! Thanks to everyone here for helping to keep me sane.... Well, as sane as I'll ever be.
Thing that remains a mystery: Why only manual calls were affected ?
Bottom Line: A Rolling stone gathers no moss, a rolling error does
PS: Light travels faster than sound. That's why some people appear bright, until you hear them speak.
Some people aren't just missing a SCREW... they're missing the whole damn TOOLBOX!
