[VoiceOps] Voicemail options

Matt Yaklin myaklin at g4.net
Thu May 24 01:08:48 EDT 2012

What is the main reason for wanting to merge them?
More efficient provisioning?
One less system to manage?

I am in the same boat you are. Asterisk voicemail for
residential customers as well as generic boxes for one
off situations. BS vm for my hosted pbx customers that have
more bells and whistles.

Yet never did I ever consider wanting to merge them as
the amount of work to figure that out would not be worth
it to me.

Granted I have thought about residential customers getting
a voicemail account on BS as our T7000 plus adsl2+ dslams
can work with BS to give extra features to a voice line
(I forget the exact name Taqua/BS calls this) but there
seems to be very little demand above what we already offer
in our packages.

So perhaps if we knew the reason for wanting to attempt this
strategy below we might be able to offer better ideas. I am
curious why you would want to this myself.


On Wed, 23 May 2012, Nelson Hicks wrote:

> Hello,
> We currently have two separate SIP voicemail systems for two different platforms, and I'm looking at options
> to merge them.  One of them is part of an Asterisk PBX and the other is the Broadworks voice portal.
> We would like to avoid moving a large mass of users from the Asterisk platform over to Broadworks and tie up a
> bunch of messaging licenses, but I don't think we want to move the voicemail for the Broadworks subscribers
> over to the other system either (they would lose other voice portal functions).
> I'm looking for what you guys would think of to try to fill this gap, both in type of solution and software. 
> I'm not happy with any ideas I've brainstormed myself.
> Thanks,
> -- 
> Nelson Hicks
> DNS and Web Administrator
> (573) 817-0000
> dns at socket.net
> 1-800-SOCKET-3  www.socket.net

More information about the VoiceOps mailing list