OpenVZ Forum


Home » General » Support » Asterisk problem reported. (Exsiting Asterisk VE affected by creation of new Asterisk VE)
Re: Asterisk problem reported. [message #38377 is a reply to message #38375] Sat, 12 December 2009 12:32 Go to previous messageGo to previous message
unxs is currently offline  unxs
Messages: 21
Registered: September 2009
Location: Oregon, USA
Junior Member
Interesting.

If you have any links or other info about the technical aspects of why this happens that would be great. I would like to know more about the technical details.

Since my problem involves creating 100's of Asterisk containers per day (on many clustered HNs.) I need to solve this problem.

The solution as I see it now, is to monitor all Asterisk containers via the autonomic VZ VE management system we use and defer creation (keep in job queue) until any conference call is over (scope is per single HN.) Another option is for the system to autonomously deploy the new Asterisk VE on another cluster member HN that has no ongoing conference calls. In order for this method to work there has to be a way to detect ongoing conference calls (or even better, about to commence conference calls.)

I'm sure there is some device information in the Asterisk VE itself or other Asterisk log file, monitoring system, etc. that can be used to detect ongoing conference calls. Will have to talk to an Asterisk engineer about this.

Thanks for your reply!

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: help ( VM creation has failed)
Next Topic: About the network interface for OpenVZ
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Jul 11 18:12:21 GMT 2026

Total time taken to generate the page: 0.19871 seconds
Powered by FUDforum Powered by Virtuozzo Containers