[VoiceOps] Voicemail options

Alexander Roanauskas aroman at tessaport.com
Thu May 24 18:23:42 EDT 2012

The BroadWorks voice mail will be less than accommodating with the  
playback of any message not sent with the proper headers.  There is a  
header specific to the message ID that lets BroadWorks acknowledge  
that the particular message is a voice mail message.  This is a  
security mechanism since it's a just an email server after all and  
could be tricked into playing back any message.

    Worked with BroadWorks to allow the addition of bulk announcements  
and it was not a fun project.  In the end it did work but I would not  
attempt combining both an asterisk and broadworks voice mail server  
onto a broadworks
server.  I think that's just asking for too much mess and why burn the  
broadworks licenses.

     You say you want to combine the two voicemail servers and one is  
on the Asterisk PBX, not eactly sure from the post but are the uses on  
the Asterisk Platform or something else?  If they are on the asterisk  
platform and you're not getting rid of the Asterisk PBX why not just  
have the Asterisk PBX just use the same email server as BroadWorks.   
As long as users are mapped to separate email boxes it will not have  
any effect.

Alex Romanauskas

Quoting Nelson Hicks <nelsonh at socket.net>:

> That is very interesting, and something I was not aware of.   
> Broadworks seems to use this format for voicemail recordings:
> WAV-wrapped DVI ADPCM audio (Linux file command reports it as IMA  
> ADPCM), mono 8KHz
> If I can figure out how to get Asterisk to use that audio format,  
> that may make a lot of this a lot simpler.  Thanks for the hint!
> Nelson Hicks
> DNS and Web Administrator
> (573) 817-0000
> dns at socket.net
> 1-800-SOCKET-3  www.socket.net
> On 05/24/2012 09:22 AM, Nathan Anderson wrote:
>> 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)?
>>> -Scott
>>> *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:* 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).
>>> -Matt
>>> ------------------------------------------------------------------------
>>>    *From: *"Nelson Hicks" <nelsonh at socket.net
>>>    <mailto:nelsonh at socket.net>>
>>>    *To: *voiceops at voiceops.org <mailto:voiceops at voiceops.org>
>>>    *Sent: *Wednesday, May 23, 2012 4:35:43 PM
>>>    *Subject: *[VoiceOps] Voicemail options
>>>    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
>>>    SOCKET
>>>    (573) 817-0000
>>>    dns at socket.net <mailto:dns at socket.net>
>>>    1-800-SOCKET-3 www.socket.net <http://www.socket.net>
>>>    _______________________________________________
>>>    VoiceOps mailing list
>>>    VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>>>    https://puck.nether.net/mailman/listinfo/voiceops
>>> <ATT00001.c>

More information about the VoiceOps mailing list