
err of course if you're talking just about IVR functionality (sorry i heard MetaSwitch and thought of softswitches) I would look at Iperia and Movius. Both have some advanced voicemail and auto attendant functionality. -katia On Fri, Jul 31, 2009 at 10:08 PM, katia goforth <voiceops at chickey.org>wrote:
Talking SIP would be at the bottom of my list just based off the fact that they run on Windows 2003 with MS SQL databases. Metaswitch, Sonus ASX and BroadSoft (BroadWorks) platforms are the top three that i would think are production-ready.
-katia
On Fri, Jul 31, 2009 at 10:00 PM, Carlos Alcantar <carlos at race.com> wrote:
Metaswitch has done a fairly nice job that's what we are running.
-----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Hiers, David Sent: Friday, July 31, 2009 5:54 PM To: Raul Rodriguez; voiceops at voiceops.org Subject: Re: [VoiceOps] Alternative IVR Platform?
How good is their scripting engine?
We've been able to handle most of our requirements with native broadsoft call handling, but I do miss the scripting engine and gui in cisco's ipcc.
David Hiers
CCIE (R/S, V), CISSP ADP Dealer Services 2525 SW 1st Ave. Suite 300W Portland, OR 97201 o: 503-205-4467 f: 503-402-3277
-----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Raul Rodriguez Sent: Friday, July 31, 2009 4:13 PM To: voiceops at voiceops.org Subject: [VoiceOps] Alternative IVR Platform?
Anyone have any suggestions for alternatives to Talking SIP (http://www.ivr.com/talking-sip.php)?
Thanks. -Raul R. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

Asterisk also makes for a very powerful and scriptable IVR platform if you are willing/able to put the work in. -Scott From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of katia goforth Sent: Friday, July 31, 2009 10:11 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Alternative IVR Platform? err of course if you're talking just about IVR functionality (sorry i heard MetaSwitch and thought of softswitches) I would look at Iperia and Movius. Both have some advanced voicemail and auto attendant functionality. -katia On Fri, Jul 31, 2009 at 10:08 PM, katia goforth <voiceops at chickey.org> wrote: Talking SIP would be at the bottom of my list just based off the fact that they run on Windows 2003 with MS SQL databases. Metaswitch, Sonus ASX and BroadSoft (BroadWorks) platforms are the top three that i would think are production-ready. -katia On Fri, Jul 31, 2009 at 10:00 PM, Carlos Alcantar <carlos at race.com> wrote: Metaswitch has done a fairly nice job that's what we are running. -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Hiers, David Sent: Friday, July 31, 2009 5:54 PM To: Raul Rodriguez; voiceops at voiceops.org Subject: Re: [VoiceOps] Alternative IVR Platform? How good is their scripting engine? We've been able to handle most of our requirements with native broadsoft call handling, but I do miss the scripting engine and gui in cisco's ipcc. David Hiers CCIE (R/S, V), CISSP ADP Dealer Services 2525 SW 1st Ave. Suite 300W Portland, OR 97201 o: 503-205-4467 f: 503-402-3277 -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Raul Rodriguez Sent: Friday, July 31, 2009 4:13 PM To: voiceops at voiceops.org Subject: [VoiceOps] Alternative IVR Platform? Anyone have any suggestions for alternatives to Talking SIP (http://www.ivr.com/talking-sip.php)? Thanks. -Raul R. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

Scott Berkman wrote:
Asterisk also makes for a very powerful and scriptable IVR platform if you are willing/able to put the work in.
I was about to say - it makes an excellent feature box. My only major concern relates to its scalability; not even so much the amount of concurrent calls per box that it can handle as how much that amount might be reduced by a weighty, complicated dial plan with database backing, etc. On the other hand, the ability to stick it on commodity PC hardware far outweighs any of these downsides from a cost perspective; per-port cost with Asterisk is among the lowest for applications, especially if you bother to do it right (i.e. centralised logic controller, nothing too host-wise). SEMS (SIP Express Media Server) from IPTel/Tekelec is another viable alternative that might scale better. Obviously, it's a pretty bad choice for doing a simple SMB-oriented IVR; it's at least 100x more difficult than doing it with the Asterisk dial plan, and requires using some poorly documented C++ and/or Python APIs. However, if it's something really esoteric and requiring the flexibility of integration and/or data acquisition paths that Asterisk can't provide, or requires a higher degree of real-time call control (i.e. continuous deduction of prepaid balances and termination of call if they have expired, for example), I think it's a pretty good platform. Also makes a great generic signaling-only B2BUA, using ann_b2bua app for exaple. Definitely not the right thing for *basic* IVR, though. -- Alex -- Alex Balashov Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 Mobile : (+1) (678) 237-1775

On Aug 1, 2009, at 12:02 PM, Alex Balashov wrote:
Scott Berkman wrote:
Asterisk also makes for a very powerful and scriptable IVR platform if you are willing/able to put the work in.
I was about to say - it makes an excellent feature box. My only major concern relates to its scalability; not even so much the amount of concurrent calls per box that it can handle as how much that amount might be reduced by a weighty, complicated dial plan with database backing, etc.
Scalability is the biggest issue. I'm lucky to get 200 - 250 calls per box with some pretty heave DB and playing some sound files/IVR prompts. But being able to put it on commodity hardware makes this pretty easy to deal with if you are accustomed/equipped to mass manage/ monitor linux boxen. I've got 15 of them online now.....and adding more is just a matter of provisioning one of the spare blades. As far as upgrades go, we pretty well steer clear. It seems that the realtime architecture and other DB functions are not at the top of the dev's lists, nor do they even have the capability of testing these things under load. Most upgrades have been massive amounts of pain until we learned the easy trick: dedicate one production box to whatever new version seems to pass muster in staging. Dump traffic on it. If it doesn't work, don't sweat. Start over with staging again in a couple of week - it's alway like a brand new product. The bugs you had are probably gone, and they are somewhere else that you don't care about now. You pay in licensing, or you pay in time. It's your call. For now, we're paying in time. Daryl
participants (4)
-
abalashov@evaristesys.com
-
daryl@introspect.net
-
scott@sberkman.net
-
voiceops@chickey.org