UMS issue with Exchange 2010 on Ip Office 2

[PhoneMan777]

Hey guys I am upgrading a system to R8 and removing IMS and upgrading to UMS. We have everything upgraded and the emails are going out but the messages are not showing up when we check the mailbox using *17 and the message waiting light is not coming on. I have seen that there are other post like this one and have tired the those options with no luck. I wnet under control panel and removed what is under SMTP and it will always add the the name of the domain user back in on the account tab and the exchange server back into the mail server field on the smtp tab. If i blank them out and restart the service then it populates the info of the mapi account name and server back in the account field and mail server field.
Also I have had their IT guy follow all of the instructions on the knowledgebase for permissions and go back in to add full access permissions to the domain account that Mapi is using and still no luck.
I have rebooted the phone system and voicemail server a couple of times. Any suggestions please?

Thanks!

 

[kwing112000]

does your outlook on the VM server work ok? do you have MAPI set in VM pro?

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[kwing112000]

1 other thing that got me 1 time was the user had a rule set up in outlook to have any messages from voicemail moved to folder under his mailbox on exchange. his would never sync because of this. the message had to land in the inbox of the user. I would double check your permissions on the exchange server and make sure the MAPI user has full access permissions and make sure the voicemail box is cleared out when you set to forward.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[PhoneMan777]

Thanks for the Reply.
Yes I can send messages fine from outlook on the vmpro server and I do have Mapi checked in vmpro. There is nothing under smtp senders or receivers.
I will check and make sure there are not any rules setup for the voicemail account. Thanks again!

 

[kwing112000]

if your permissions are right you should be able to go to file then open other users folder and open a users inbox from the outlook on the vm server

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[PhoneMan777]

I did test the permissions as you indicated above and I was able to see the users mailbox and delete a message from it.

 

[kwing112000]

you may want to try a full reboot of the VM server if you havent already.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[PhoneMan777]

Do you know whether the domain account that the voicemail server is using must be named voicemail or does it matter?

 

[kwing112000]

i dont think it matters. are you logging in as the domain user and does the service run under that account.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[PhoneMan777]

Yes we were logged in as the domain user and the service was running under that account. We even went so far as creating a new domain user, and following all of the instructions on the knowledgebase again including, adding full access permissions. We then tested the permissions as you indicated above to ensure we could access the inbox of another user and then we rebooted the exchange, vmpro and phone system. When we tested it's still a no go. We get the email, we do not get a MWL and we discovered if you log into the mailbox that it says you have no messages but if you press 2 to get messages then it will play the new message that was left. Just doesn't make sense.
Any more suggestions would be greatly appreciated.

 

[IPGuru]

We have everything upgraded and the emails are going out but the messages are not showing up when we check the mailbox using *17 and the message waiting light is not coming on.

are you sure you have not got the VM to email mode set to Forward in error?

also I would check basic UMS operation before trying any form of Exhange integration.
Do your users have UMS Web Services ticked, if not then you are only wing the basic VM to Email service

VM Pro should be acting as an IMAP Server
can you connect your e-mail clients to this?

For diagnostics I would start with plain VM operation (No UMS or email) & then add UMS followed finally by Exchange integration.

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[PhoneMan777]

I tested UMS last night by logging into the 127.0.0.1/voicemail and I was able to log in as a user and check their voicemail so I believe UMS is working fine. I do have all of the users set to forward as indicated in the documents and from my last install it seemed to work fine on Exchange 2007. Does IMAP4 have to be working on vmpro and on the exchange? I did notice somehting in another post about testing if you could telnet to port 143 on exchange and the vmpro. I can telnet to 143 on vmpro but not the exchange. Does this matter?

 

[IPGuru]

you dont want to be forwarding VM msgs, this is why the lamp is not working

VM pro ruins an IMAP server
if you configure Outlook to connect to the VMPro as a separate IMAP email account you will find things working (just a different mailbox for VM messages)

I have never tried the full integration with exchange as that just looks like a cause of pain (IMS was replaced with UMS/IMAP because of the difficulties in playing nice with exchange in the first place)


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[kwing112000]

if you want to use UMS with only 1 inbox for the users then you need to leave it as a forward. I have done like 8 to 10 full exchange integration's and it was really easy to set up and has worked very well. its not like the old IMS at all. with UMS your message store is on the exchange. that is why you need forward enabled.


if you look in the VM pro client do you see each user listed with exchange mailbox? it should show New=x,old=X next to each user.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[PhoneMan777]

Yes I have to do Exchange integration all of the way so I guess must use forward. Kwing, in vmpro I do see all of the users that are configured under exchange messages and they all show New 0 and Read 0 but I know for a fax some of them should have messages.

 

[PhoneMan777]

Sorry for the typo I meant to say I know for a fact, meaning I have left several user repeated messages, that some of them should have messages yet they dont show up. Any other suggestions woule be greatly appreciated.

 

[NYSTECH]

kwing112000

Staying on same topic I think. Why when the Exchange server is rebooted for any reason the IP Office needs to be rooted as well to have th MWI work? I have been looking for a work around or some set up flaw in the installs.. When it works UMS is fine lights light everyone happy.. When Exchange/2010 rebboted MWI no work until IPO rebooted.. I would think they should sync automatically. Or if anyone could help that would be great.. Most of the contraol are done by Exchange and I am not an Exchange tech by no means.

 

[Shortcode]

I ran into an instance where if the SMTP was EVER used, or the information populated in the SMTP fields of the VMPro, that the Voicemail Pro Service would still attempt SMTP actions. You may take a look at Debug and see if there are any SMTP errors or messages, there really shouldn't be if you are using MAPI. If there are, you may have to do what I did. Backup call flows, completely uninstall Voicemail Pro, reboot, reinstall VMPro, and blank out any SMTP account info, and set the server address to localhost. Import call flows, then go re-establish MAPI and test.
In my instance it caused the UMS to continually drop duplicate messages into a users Outlook. It would keep looping the SMTP delivery and the UMS delivery until the service locked up and had to be restarted.
If SMTP is attempting to forward then you may be losing the messages in the mailbox because it is being used by SMTP (even if not delivered by), as well as MAPI, and removing it from the mailbox as a forward.

"When you do things right, people won't be sure you have done anything at all.

 

[PhoneMan777]

Thanks again for the input. I did try to uninstall just UMS the and reinstall and that did not fix the problem. I will Follow your advice Shortcode and remove completely and then reboot and reinstall. I did notice that even when I remove everything under control panel that If I restart the service or reboot the server then it will automatically populate the account with "voicemail" which is my domain login name under control panel and populte the exchange severs name as the server addresson the smtp tab under control panel. If I delete it again and restart the service it comes right back every time...

 

[Shortcode]

If you want to try something before uninstalling, blank out the account info, and set the server to localhost. It is populating the field with cached information. It may work for you and actually stop the SMTP operation.

"When you do things right, people won't be sure you have done anything at all.