Conference call service goes down randomly

[dchoward]

MiCollab 7.3.0.106
MVB Release level: 8.0 PR3

We had to fall back to the free conference number to run our meeting (embarrassing).
I stopped and started the AWV services and it started working again. How do I figure out why it stopped working? This is the third time and I am loosing user acceptance.

Thanks,

Carl

 

[OldTimingMan]

I'm assuming you are referring to audio? Possible SIP registration timing problem. Check each port to see if AWV answers. Check port status in IP Telephone inventory. Is this Virtual? Check your VMware statistics, Performance, Resource Allocation. Go back to Engineering basics and make sure you have correct number of resources. Also look at networking. Any bottlenecks, etc?

 

[dchoward]

Sorry, Yes it is audio and it is virtual.
When the issue occurs, if you dial in all you get is dead air.
All of the port state statuses are "In Service"
I can call each port and AWV answers.
VMware stats are all "normal".
It was built per the engineering guidelines.

May turn out to be a vmware network issue though. When I log into the phone system there are SDS errors and when I have it try again it cannot connect and I cannot sync via the network element either unless I reboot the MiCollab server.

I am not seeing anything in the events viewer. Is there a particular log I can check to help figure out the cause?

 

[jpruder]

Sounds like a duplicate ip address issue or something like it. I don't know what the virtual host is, but I ran into a strange issue where the gateway address for the vMCD was being changed by ICMP redirect whenever a remote site went down. All physical survivable nodes had no issue but the host vMCD routing incorrectly