asterisk users - Jul 2006 - Looking for carrier grade redundant solution

Hello List -

We are looking add Asterisk to the core of our voice/data network.  Our
first application will provide a hosted call center application for a number
of tenants (customers) who will have between 5-20 agents (seats) answering
ingress calls.  The calls will ingress and egress the Asterisk server SIP
(all TDM is handled by Sonus switches).

My goal is to design a redundant solution using a multiple Asterisk servers
with an NFS mounted filesystem.

I've done some reading regarding Asterisk redundany, and so far it seems the
best approach is running redundant hardware (power supplies etc), matching
servers (with a heart beat ping between them) and a NFS filer for storage
(hot swapable) connected to each box via gigE.

Am I on the right track?  Any other suggestions or resources I might have
missed regarding developing a redundant solution?

Thanks for your time,

_Chris_
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060727/b55cd8c6/attachment.htm

Chris,

Heartbeat failover will usually be your best mixed approach.

As always there is a cost benefit to be considered.
Where the call absolutely has to stay up then Fault-Tolerant software and
hardware is the only option that works with Asterisk to date.

If however you wish to keep costs to a mimimum then possibly an onsite / hosted
model where the back up is available remotely. This model depends on set up
however.

In all cases I would suggest you take a peruse of PBXware :
http://www.bicomsystems.com/products/online_demo/ which is our SMB Edition. We
will next week launch our Call Center Edition that is packed with features and
functions to assist the running of a dedicated to running a Call Center
efficiently.

Feel free to contact me offline steve {at] bicomsystems {dot] com and can make
more precise suggestions according to requirement.

Regards
Steve


  ----- Original Message ----- 
  From: Christopher Aloi 
  To: Asterisk Users Mailing List - Non-Commercial Discussion ;
asterisk-biz@lists.digium.com
  Sent: Friday, July 28, 2006 3:44 AM
  Subject: [asterisk-users] Looking for carrier grade redundant solution


  Hello List -

  We are looking add Asterisk to the core of our voice/data network.  Our first
application will provide a hosted call center application for a number of
tenants (customers) who will have between 5-20 agents (seats) answering ingress
calls.  The calls will ingress and egress the Asterisk server SIP (all TDM is
handled by Sonus switches).

  My goal is to design a redundant solution using a multiple Asterisk servers
with an NFS mounted filesystem.

  I've done some reading regarding Asterisk redundany, and so far it seems
the best approach is running redundant hardware (power supplies etc), matching
servers (with a heart beat ping between them) and a NFS filer for storage (hot
swapable) connected to each box via gigE.

  Am I on the right track?  Any other suggestions or resources I might have
missed regarding developing a redundant solution?

  Thanks for your time,

  _Chris_



------------------------------------------------------------------------------


  _______________________________________________
  --Bandwidth and Colocation provided by Easynews.com --

  asterisk-users mailing list
  To UNSUBSCRIBE or update options visit:
     http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060728/27dbb67c/attachment.htm

What about sip registration replication?
What about SIP subscription replication?
What about BLF replication?
What about using DUNDi to replicate applications for redundancy?
How would you handle different phones ability to failover if they don't do
it so well?
How would handle the fact that the config files have a hard coded database IP?
 
And so on... 
 
I don't think anyone has a great solution to date.
 

-----Original Message-----
From: Stephen Wingfield [mailto:steve@bicom.us]
Sent: Friday, July 28, 2006 4:14 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Looking for carrier grade redundant solution


Chris,
 
Heartbeat failover will usually be your best mixed approach.
 
As always there is a cost benefit to be considered.
Where the call absolutely has to stay up then Fault-Tolerant software and
hardware is the only option that works with Asterisk to date.
 
If however you wish to keep costs to a mimimum then possibly an onsite / hosted
model where the back up is available remotely. This model depends on set up
however.
 
In all cases I would suggest you take a peruse of PBXware :
http://www.bicomsystems.com/products/online_demo/ which is our SMB Edition. We
will next week launch our Call Center Edition that is packed with features and
functions to assist the running of a dedicated to running a Call Center
efficiently.
 
Feel free to contact me offline steve {at] bicomsystems {dot] com and can make
more precise suggestions according to requirement.
 
Regards
Steve
 
 

----- Original Message ----- 
From: Christopher  <mailto:chris.aloi@gmail.com> Aloi 
To: Asterisk Users Mailing List - 
<mailto:asterisk-users@lists.digium.com> Non-Commercial Discussion ;
asterisk-biz@lists.digium.com
Sent: Friday, July 28, 2006 3:44 AM
Subject: [asterisk-users] Looking for carrier grade redundant solution

Hello List -

We are looking add Asterisk to the core of our voice/data network.  Our first
application will provide a hosted call center application for a number of
tenants (customers) who will have between 5-20 agents (seats) answering ingress
calls.  The calls will ingress and egress the Asterisk server SIP (all TDM is
handled by Sonus switches).

My goal is to design a redundant solution using a multiple Asterisk servers with
an NFS mounted filesystem.

I've done some reading regarding Asterisk redundany, and so far it seems the
best approach is running redundant hardware (power supplies etc), matching
servers (with a heart beat ping between them) and a NFS filer for storage (hot
swapable) connected to each box via gigE.

Am I on the right track?  Any other suggestions or resources I might have missed
regarding developing a redundant solution?

Thanks for your time,

_Chris_




  _____  




_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060728/eba91390/attachment.htm