Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Voicemail Pro 9.1.1 Build 3 Issues with IMAP

Status
Not open for further replies.

xkwhx

IS-IT--Management
May 13, 2015
3
US
Fresh Install on Windows Server 2012 R2 having some issue with IMAP
Imap apparently defaults to secure port 933. Found and reset reg key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Avaya\Media Services\Directories\IMAPSECUREONLY (1 is on 0 is off) to switch back to 143
Continuing to have issues with the attached wav files randomly not playing if delivered via IMAP to Outlook client 2010 or above. Inspecting the wav file shows "digital rights information missing" as if they are part of a DRM solution. Anyone seen or experienced this?
 
I have never used IMAP, always used SMTP when sending emails from VMPro (would be interesting to know if you have the same issue with SMTP).
But there might be some reason for using IMAP that I'm not aware of =)

"Trying is the first step to failure..." - Homer
 
You can also use IMAP as UMS access option with Voicemail pro... I also used it twice to test...
 
derfloh did you use imap with server edition? I have looked in the docs and do not see hoe to set this up. I would like to set up as separate folder in outlook. Have you done this? if so can you tell me where the doc is on knowledgebase. I have only done this with windows. Maybe its the same way?
 
Works fine with SMTP. The IMAP is preferred here as it allows for the indicator light on the phone to synch with the "read vs unread" status in Outlook
 
It's quite easy. I only tested it on Application Server but it should be the same with server edition.

Just create a new account in your preferred mail client and use the VMPro server's IP or FQDN as IMAP server. Username is the same as in IPO and password should be the user's Voicemail code.

For security I think it is not recommended to create inbound firewall rules to access that IMAP from Internet.

Today I had the idea if it could be possible to connect an exchange mailbox in someway with that IMAP account but I don't know if that is possible.

UMS exchange would be the better option but as far as I know that way there are additional UMS user licenses needed in exchange most customers want to pay for.
 
I upgraded from 9.0 to 9.1 aproximately 3 weeks ago- and have been fighting this exact issue as well.

1) No notice on switch from port 143 to port 993
2) 11 out of 15 email messages do not playback in Outlook 2013

I didn't notice anything about DRM- I'll take a look later- but I wanted to add:

The messages that don't playback don't seem to have any codec information in the file:

Here's what a GOOD file looks like:
BeforeUpgrade_fesqe5.png



Here's what a file looks like that won't playback in Windows Media Player- after saving audio message to desktop (to avoid suspicion with Outlook):
AfterUpgrade_cdr7kf.png







Did you get any further with your audio files playing back problem?
 
We never solved this issue. Although it is interesting to note that initial testing of the problem with playback appeared to show that the wav files would playback on droid or iphone devices just fine (further testing needed to confirm). I forced our small percentage of imap voicemail users to convert over to direct smtp delivery for now until the issue is recognized and hopefully patched. I was speculating on the DRM as what I saw with the non-playable files indicated that rights information was missing
 
Good News!
Avaya Development has identified a problem where audio messages that are exactly a multiple of 3 bytes long encode fine with the Base64 MIME Encoding scheme.
Those files that do not end in a multiple of 3-bytes (statistically 67% of them) do not pad the end of the file, and are not correctly read by newer versions of Outlook.

They are working on a patch.

Will let you know when the patch is released and tested.


FYI
 
Avaya Development provided me with a patch, and I've been informed that this .dll file will be included in the next Major Release.

Until then, for those running VM Pro 9.1 on Windows....here's a patch you can use.


Cheers!
 
 http://files.engineering.com/getfile.aspx?folder=a90e0a80-8026-4c58-9be6-9840a246b168&file=VMPro_IMAP_Patch_from_Avaya_Development.zip
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top