Author Topic: 3300 matai mwi exchange 2010 MWI issues  (Read 2287 times)

Offline cpekar

  • New Member
  • *
  • Posts: 3
  • Country: us
  • Karma: +0/-0
    • View Profile
3300 matai mwi exchange 2010 MWI issues
« on: November 14, 2014, 11:39:36 AM »
When testing, we can leave a voice mail, the MWI is instantly lit, and we get an email with the voicemail as an attachment.  We then open the attachment, listen to the voice mail, then delete the message in outlook.  The mwi is still lit on the phone and the voicemail is still available on the phone itself.

We have tried cached mode and online mode.  Outlook 2010 and 2013.  With and without the NuPoint plugin.

We are using MATAI for MWI and IMAP for connection to exchange.

What do we need to check to get this working.


Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5768
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: 3300 matai mwi exchange 2010 MWI issues
« Reply #1 on: November 14, 2014, 01:22:28 PM »
I'm not a Nupoint tech so I won't be able to tell you how to fix it but here's what's going on.
There are two different types of email integration.
1 - forward to VM.
2 - Fully integrated

The forward to VM simply sends a copy to your email.  It is not sync'ed.
Full integration gives you exactly what you are looking for.
I believe on the NuPoint you need additional licenses to make it fully integrated.

Hopefully one of the Nupoint tech can chime in and let you know how to check if you're licensed for it and if it is what needs to be set up.

Ralph

Offline cpekar

  • New Member
  • *
  • Posts: 3
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: 3300 matai mwi exchange 2010 MWI issues
« Reply #2 on: November 14, 2014, 02:06:00 PM »
We use Advanced UM on all the VM boxes.

Offline cpekar

  • New Member
  • *
  • Posts: 3
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: 3300 matai mwi exchange 2010 MWI issues
« Reply #3 on: November 19, 2014, 03:52:16 PM »
We may have fixed this.

We changed the IMAP4 connections setting in exchange 2010 from the default 16 to 200.  Then we restarted the imap4 service.  We did this to both exchange nodes.

This may have fixed our issue.  But we earlier changed the following:

We also have a special service on our Baracuda load balancer, we changed the session time out from 60 to 120.  Also under system settings, changed the tcp connections timeout from 900 to 120.

We have yet to undo these Baracuda settings.

I have seen quite a few posts on this issue elsewhere on the internet with no answer.  This was how we fixed our issue.  Hope this helps someone.


 

Sitemap 1 2 3 4 5 6 7 8 9 10