CMM 6.2 Internet Messaging-- Delivery Issues

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • ctmcbain
    Member
    • May 2014
    • 3

    CMM 6.2 Internet Messaging-- Delivery Issues

    Hi
    I am running Avaya CMM 6.2 and would like to enable voicemail to email using IMAP4. I seem to be missing something as I cannot seem to get the client setup properly (they are using Outlook Exchange Online 2013). Test always fails when trying to complete local mail setup. I have I think that I may need to configure the external host but I am not sure what to add here and was wondering if anyone has succesfully set this up on their Avaya.

    Any assistance would be greatly appreciated

    Thanks
    Colin


    My current setup:

    Under Messaging Admin/System Admin I have set the following.
    Internal System IMAP4 port 55143 enabled
    IMAP4 port 143 enabled
    IMAP4 SSL port 993 enabled
    SMTP port 25 enabled
    SMTP SSL port 465 enabled
    LDAP port 389 enabled
    LDAP SSL port 636 enabled

    User has MCAPI access, MCAPI Message Transfer and Trusted server set to yes in his subscriber profile.

    When I test IMAP4 connection I get the following:

    ipcopen `tcp!x.x.x.x!143`Trying x.x.x.x ...Opening connection to tcp!x.x.x.x!143---> * OK XXXXXX IMAP4 server ready<--- a CAPABILITY---> * CAPABILITY IMAP4rev1 AUTH=CRAM-MD5 AUTH=DIGEST-MD5 AUTH=NTLM UIDPLUS QUOTA IDLE UNSELECT STARTTLS X-MSGTYPES XClientCapability XSendUnsolicitedResponses XSearch-Time X-AV-ExtendedStatus=INBOX(MESSAGES,RECENT,UIDNEXT,UIDVA LIDITY,UNSEEN,DELETED,DSN,NEW,N---> WVOICE,NEWFAX,NEWEMAIL,NEWDSN,OLD,OLDVOICE,OLDFAX, OLDEMAIL,OLDDSN,DELETEDVOICE,DELETEDFAX,DELETEDEMA IL,DELETEDDSN,NEWBCAST,NEWBCASTVOICE,NEWBCASTFAX,N EWBCASTEMAIL,NEWBCASTDSN,NEWFLAGGED,NEWFLAGGEDVOIC E,NEWFLAGGEDFAX,NEWFLAGGEDEMAIL,NEWFLAGGEDDSN,NEWB CAST---> LAGGED,NEWBCASTFLAGGEDVOICE,NEWBCASTFLAGGEDFAX,NEW BCASTFLAGGEDEMAIL,NEWBCASTFLAGGEDDSN);(MESSAGES,RE CENT,UIDNEXT,UIDVALIDITY,UNSEEN,DELETED)---> a OK Completed<--- a LOGOUT---> * BYE LOGOUT received---> a OK Completed

    When I do a mail delivery test to a known mailbox on the system I get a message queued repsonse.
    Last edited by ctmcbain; 05-22-2014, 01:03 PM.
  • sunilkumarv
    Guru
    .
    • Mar 2010
    • 124

    #2
    Hello,

    you may need to specify mailbox gateway ipaddress if you need mail delivery from CMM. however this should not stop you from receiving voice mail's via emails to your outlook client.

    you can also upgrade the CMM to 6.3 which supports email forwarding , i.e your Voice messages will be forwarded to your exchange email address.

    regards
    Sunil
    Regards,
    Sunil

    AVAYA| Voice: US:- +1 720 444 5271, India: +91 80 6715 3277 | Email:[email protected]|

    Comment

    • ctmcbain
      Member
      • May 2014
      • 3

      #3
      Thanks for the reply Sunil,
      Sorry I should have updated this post and closed earlier .
      Client decided to cancel this request shortly after my posting .

      FYI I had tried using the CMM IP for Mailbox gateway but the test still failed when trying to complete local mail setup (OUtlook client setup) .

      Thanks
      Colin

      Comment

      • sunilkumarv
        Guru
        .
        • Mar 2010
        • 124

        #4
        Hi colin,

        the mailbox gateway is normally customer SMTP gateway, yes i have see the test's failing when adding the mailbox via outlook, but the incoming message passes most of the time.

        we need to check the IIM logs to isolate the root cause

        Regards
        Sunil
        Regards,
        Sunil

        AVAYA| Voice: US:- +1 720 444 5271, India: +91 80 6715 3277 | Email:[email protected]|

        Comment

        • ctmcbain
          Member
          • May 2014
          • 3

          #5
          Thanks Sunil,
          Thanks for the helpful info !! but, there is no further action required since the customer has decided to cancel this request.
          I have archived your input though as it is very helpful, in case the client decides to re-open the request (which we know happens often ).

          Cheers
          Colin

          Comment

          Loading