NuPoint Advanced UM and Multiple Exchange Servers

[alex053]

NuPoint Messenger Base Software Release 17.0.0.24 Rev 01

I have a customer that's going to be migrating from Exchange 2007 to a cluster of Exchange 2013 behind a F5 load balancer.

I have Advanced UM working while pointed directly to a single a 2007 server. If I point it to the IP of the load balancer then AUM fails.

the customer is looking to migrate users from 07 to 13 and not have an interruption in service. the release notes say AUM will support a cluster of servers but they all need to be the same version.

can anyone think of a scenario where there would be no interruption? perhaps some programming on the Exchange servers (that I know nothing about). I really just need to know whats possible so I know how much hair to pull out looking for a solution.

Thanks,

Alex

 

[alex053]

I am also getting a lot of errors on the advanced UM. I have the email addresses in and was told the alias is the same as the first part of the email but i keep getting errors like below and messages not showing up.

below is from putty using tail -f msblog.txt and leaving a message in mailbox 5154 after deleting and adding in the alias and leaving a message.



24/Feb/15 14:36:33.983 msb INFO [13825:9239b70] npmMailbox.cpp#1118: Mailbox 5154 successfully registered for polling
24/Feb/15 14:36:34.015 mailbxDepot INFO [13829:b61feb70] mbd.cpp#2101: Mailbox 5089 is going to be initialized by MSB on socket 9
24/Feb/15 14:36:34.016 msb INFO [13825:382ab70] masAgent.cpp#11160: Adding Initialization task for 5089 to task queue
24/Feb/15 14:36:34.023 replication INFO [13825:271eb70] masAgent.cpp#7328: NPM Voice Mail ID for[5089] -> [ 34636 35240 36053 ]
24/Feb/15 14:36:34.037 replication INFO [13825:6619b70] masAgent.cpp#7357: NPM Unreplicated Voice Mail ID for[5089] -> []
>4/Feb/15 14:36:34.042 imapAdapter ERROR [13825:b21f7b70]../Imap4Adapter/imap4Client.cpp#3314: [b21f7b70]:[b7513008] IMAP4 Login failed -> Invalid Login Response <LOGIN failed.
24/Feb/15 14:36:34.042 imapAdapter ERROR [13825:b21f7b70]../Imap4Adapter/imap4Adapter.cpp#1155: Login failed!
24/Feb/15 14:36:34.042 imapAdapter ERROR [13825:b21f7b70]../Imap4Adapter/imap4Adapter.cpp#1225: [b21f7b70] Fetching voice Mail info for Mailbox[mjaumer] Failed
24/Feb/15 14:36:34.042 msb ERROR [13825:b21f7b70] masAgent.cpp#9462: Mailbox 5154 polling the voice mail status from email adapter failed -> adapter error
24/Feb/15 14:36:34.043 msb INFO [13825:b21f7b70] npmMailbox.cpp#1029: Mailbox 5154 reinit reason = Failed in 'pAdapter->GetVoiceMailInfo' - UID validity changed
24/Feb/15 14:36:34.043 msb INFO [13825:b21f7b70] npmMailbox.cpp#1029: Mailbox 5154 reinit reason = Poll mailbox change failed for some reason
24/Feb/15 14:36:34.043 msb ERROR [13825:b21f7b70] masAgent.cpp#4775: Poll Task for Mailbox 5154 Failed
24/Feb/15 14:36:34.068 mailbxDepot WARN [13829:b4bffb70] mbd.cpp#1187: mailbox 5154 has been un-initialized*********
24/Feb/15 14:36:34.068 mailbxDepot INFO [13829:b4bffb70] mbd.cpp#1356: Adding mailbox 5154 to init queue with delay = 300 seconds
24/Feb/15 14:36:34.069 mailbxDepot WARN [13829:b4bffb70] mbd.cpp#1187: mailbox 5154 has been un-initialized*********
>4/Feb/15 14:36:34.079 imapAdapter ERROR [13825:6619b70]../Imap4Adapter/imap4Client.cpp#3314: [06619b70]:[b730ad90] IMAP4 Login failed -> Invalid Login Response <LOGIN failed.
24/Feb/15 14:36:34.079 imapAdapter ERROR [13825:6619b70]../Imap4Adapter/imap4Adapter.cpp#1316: Login failed!

 

[Waldosworld]

what IMAP configuration are you using?
are the IMAP errors before the upgrade?
did you update the AUM licenses after making the change to the mailbox?
note there are known delay sync issues with exchange 2013
IMAP is generally for smaller single server installations, so setting up using a cluster best call Mitel.

 

[kwbMitel]

I just recently went through this exact exersize.

Your version is supported and it can work.

I got it working using Mapi, do you use Mapi or IMAP directly.

If IMAP, I may not be of any use to you.

If Mapi, I have some ideas / notes of my struggles. Mitel's documentation was flawed when I did this and may still be so as I was asked not to share the solution by my customer that had to fork over $400 to Microsoft to fix it for him. A step that was insisted on by Mitel after they verified the programming was "Correct" on their side. Coincedently, the tool the used to "Prove" the issue resided in the Exchange was Co-developed by the Microsoft tech that resolved the issue. If memory serves, the issue was in 1 variable that was set to 10 instead of 00 based on Mitel's Docs in the Superuser account parameters on the Exchange.

It's very late for me, I'll check back in 8 hours or so to see if your interested in more info.

**********************************************
What's most important is that you realise ... There is no spoon.