Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
] On Behalf Of Christopher
AloiSent: Sunday, 30 July 2006 3:28 AMTo:
asterisk-biz@lists.digium.comSubject: RE: [asterisk-biz] Looking for
carrier grade redundant solution
Thanks for the informative replies.While Enswitch sounds
If an open-source product and a user community sharing information is
free consulting i guess I am in the wrong here.
All correct... But the answer(s) in regards to your implementation has got
so many
different answers hence only the consultation or trial by error (on your
part) can give you
Thanks for the informative replies.While Enswitch sounds like a a nice solution, I don't believe it's for our shop. I really would like to develop this solution internally.
My thoughts thus far are pointing towards a scalable, redundant solution based on stock hardware.
I am thinking of running a
On Sat, 29 Jul 2006, Christopher Aloi wrote:
As agents login to a queue or become 'available' Asterisk is maintaining
their state; I believe an agents state is maintained across an Asterisk
reload. Could an agents state be maintained should the second app server
take over for the first?
for a consultant to do most of the work for
you?
Regards
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christopher
AloiSent: Sunday, 30 July 2006 3:28 AMTo:
asterisk-biz@lists.digium.comSubject: RE: [asterisk-biz] Looking for
carrier grade
What i can say, asterisk is very flexible, you can realise any idea,
rrlated to voice processing.
Regarding NFS and multi-servers - think about asterisk realtime and
fastagi.
Andy.
On Thu, 2006-07-27 at 21:44 -0400, Christopher Aloi wrote:
Hello List -
We are looking add Asterisk to the core
Christopher,
Talk to [EMAIL PROTECTED] their Enswitch
http://integrics.com/products/enswitch/ has what you are looking for.
Regards
Danny
Christopher Aloi wrote:
Hello List -
We are looking add Asterisk to the core of our voice/data network.
Our first application will provide a hosted
Danny,
Thank you!
Chris,
In Enswitch, we've gone for the approach of multiple machines with
failover (using heartbeat), load balancing and dead machine detection
(using our own code), and replication (using MySQL). Configuration, call
routing, and billing is then done using FastAGI. More
