[VoiceOps] Voicemail options

Nathan Anderson nathana at fsr.com
Thu May 24 10:22:46 EDT 2012

Have never used BroadWorks, but I can tell you that Asterisk VM audio storage options are not limited to the 3 options most commonly referenced (e.g., in the sample configuration and documentation) of WAV-wrapped PCM, WAV-wrapped GSM, or raw GSM. In my experience, it will allow you to set the storage format to any valid audio format included in your particular build; we store all of our messages natively as uLaw.

-- Nathan

On May 23, 2012, at 21:24, "Scott Berkman" <scott at sberkman.net<mailto:scott at sberkman.net>> wrote:

I don’t think sharing would work like that.  In the past when I tried pointing two different BroadSoft users at the same mailbox (IMAP account) they still only played back or “saw” the messages that came in that way.  I never dug into it but I’m guessing there is a header.  It also doesn’t just take any message with a WAV attachment, so I’m guessing it would ignore Asterisk VMs.

Or has that changed in newer versions of BW (post 14)?


From: voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org> [mailto:voiceops-bounces at voiceops.org] On Behalf Of Matthew S. Crocker
Sent: Wednesday, May 23, 2012 5:17 PM
To: Nelson Hicks
Cc: <mailto:voiceops at voiceops.org> voiceops at voiceops.org<mailto:voiceops at voiceops.org>
Subject: Re: [VoiceOps] Voicemail options

Broadworks uses IMAP & SMTP for storage of voicemail, we use SurgeMail.   Could you have Asterisk & Broadworks run off the same Surgemail server?  Best of both worlds,  you could even share voicemail accounts that way  (same IMAP folder).


From: "Nelson Hicks" <<mailto:nelsonh at socket.net>nelsonh at socket.net<mailto:nelsonh at socket.net>>
To: <mailto:voiceops at voiceops.org> voiceops at voiceops.org<mailto:voiceops at voiceops.org>
Sent: Wednesday, May 23, 2012 4:35:43 PM
Subject: [VoiceOps] Voicemail options

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.


Nelson Hicks
DNS and Web Administrator
(573) 817-0000
<mailto:dns at socket.net>dns at socket.net<mailto:dns at socket.net>
1-800-SOCKET-3  <http://www.socket.net> www.socket.net<http://www.socket.net>

VoiceOps mailing list
<mailto:VoiceOps at voiceops.org>VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20120524/37e62997/attachment.html>

More information about the VoiceOps mailing list