Duplicate email messages after single VM msg

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • conno50
    Aspiring Member
    • Jun 2016
    • 2

    Duplicate email messages after single VM msg

    For some reason we have been receiving a duplicate email message stamped From:WITHHELD in our Outlook mailbox after receiving a single vm message. Avaya Support has been working on this SR for two weeks with no resolution in site. Any suggestions? Thanks
  • ccarly
    Member
    • Jan 2014
    • 5

    #2
    Originally posted by conno50 View Post
    For some reason we have been receiving a duplicate email message stamped From:WITHHELD in our Outlook mailbox after receiving a single vm message. Avaya Support has been working on this SR for two weeks with no resolution in site. Any suggestions? Thanks
    I am having the same issue, did you get this resolved?

    Comment

    • sheasley
      Member
      .
      • Jan 2013
      • 8

      #3
      There are a couple of configuration scenarios I can think of that would cause this effect in Avaya Aura Messaging.

      If the Exchange Storage destination is used and the user has message notification to corporate email with ‘include wav file’ enabled, or if there is an Outlook rule configured to forward the email, users would get duplicate emails from a single voice message.

      Comment

      • ccarly
        Member
        • Jan 2014
        • 5

        #4
        Thanks for the heads up on the rules; not the case for me unfortunately. Mine is doing it on IPO with VMPro. Sometimes it does it and sometimes it doesn't, pretty hit or miss.

        Comment

        • ccarly
          Member
          • Jan 2014
          • 5

          #5
          I found a work around to this via a doc search at the support site. The issue was that both the primary and secondary were both sending emails via SMTP. The workaround was to set the secondary voicemail settings to be centralized pointing to the primary server. Per the doc, this is a bug and is to be fixed in SP10. I havent upgraded to SP10 but the above method worked like a champ. Thought it might help someone out.

          Comment

          • tcanla
            Hot Shot
            • Mar 2017
            • 10

            #6
            Thanks, ccarly. I think I'll use the method above and also upgrade to SP10 just to be sure.

            Comment

            Loading