App Server VM issue

[chaunymony]

I'm running VM pro, Linux, 6.1.24 on an Intel based ESXi box that has a small Win7 partition for management. I have probably 6 installed the same way with no issues whatsoever except for this one.

What seems to be happening is it's not playing the audio files. I have DID's set to auto attendants and to voicemail (*17) and when the issue occurs, I can watch the call come in and hit voicemail/AA but I'm getting no audio. I restart the service through the webcontrol but that doesn't fix it. If I SSH into it and reboot the Cent OS box it will come back and work fine once restarted. No errors in SSA or in the webcontrol.

I was on a previous release of the App server and completely rebuilt the virtual machine and loaded 6.1.24 last night and imported the .mdb and audio files. It worked for 16 hours then just had the hiccup again.

Anyone seen this or have an idea where to start?

ACSS-SME
ACIS-SME

 

[amriddle01]

You could try putting the AA in the sequential groups "Leave" startpoint instead of a forwarded user, not that it should matter but it could identify a bug and possibly avoid it, if it still happens it's fairly safe to say it's not the system config

http://www.ipoffice.tel

 

[chaunymony]

Good idea, I should say that it actually points to a time of day condition that then goes to the day or night AA. (Not that it should matter either) I will give it a shot, at this point I'm open to anything.

ACSS-SME
ACIS-SME

 

[tlpeter]

I have had issues with AA's and stuck channels but on embedded on 6.0.8!
It was caused by an external transfer from the AA.
That external number was busy and after five attempts it became stuck.


BAZINGA!

I'm not insane, my mother had me tested!

 

[chaunymony]

I have this escalated to Tier 3 possible going to Tier 4. I tried to set the ICR to the shortcode, not the huntgroup/extension/shortcode. Thought that may work as I didn't see the socket errors once that was done but just went down again about an hour and a half ago. Booo. Looks like another evening of restarting services every 4-5 hours. Maybe I should just write a script that will do it every 4

ACSS-SME
ACIS-SME

 

[Greybeard191]

this going to sound really simple, but you do actually have a VM Pro license on the IPO, right? As in installed and viewable in the pulled config?

I've seen that a couple of time where the VM Pro appeared to be going down, sort of (service appeared to still be running), except you could actually get to VM), everywhere from 1.5 to 3+ hours or so.

Feel free to smack me for raising the obvious, but the alleged 2 hour shutdown of VM Pro running without a license is considerably more "varied" in length, in my experience, although I've never seen it run remotely close to 16 hours.

GB

 

[chaunymony]

Nope, valid question. I do have the license on both of the systems experiencing issues. Actually double checked this a few times due to the time frame of them going down seemed very consistent.

ACSS-SME
ACIS-SME