06-04-2013 01:20 PM - edited 03-16-2019 05:42 PM
Hi everyone,
We have a Business Edition 3000 system running version 8.6.4.10000-15. We're moving to Microsoft Office 2010 from 2003. Users who have moved to Office 2010 are reporting that Outlook is sending all of their voicemail notifications to Junk E-mail. Usually, I would have them tell Outlook to "never block sender." However, Outlook 2010 refuses to do so, because the SMTP address of the sender (unityconnection@ciscocm1) is not from a FQDN. Similarly, we cannot use Outlook rules to process the notifications.
I've gone through the web console for the BE3000, and I cannot find a place to alter the SMTP address from which the voicemail notifications are sent. I gather from Googling around that this is hardcoded in the BE3000, and not alterable. If this is the case, how can I work around this issue? I suppose I could just disable Junk E-mail in Outlook, but our users are reluctant to do so.
Thanks for your advice.
-j
Solved! Go to Solution.
06-04-2013 03:42 PM
Jefferson,
Yea, I just noticed that workaround needs to be done via root access so you will need to open a TAC case to have that changed. This issue is being tracked by CSCub26360.
Thanks,
Brian Meade
06-04-2013 03:32 PM
Jefferson,
You should be able to modify the SMTP sender address in BE3k.
Go to the CUC page ---system settings----SMTP configuraton-----Server SMTP Server Configuration ----SMTP Domain---add the actual domain name here.
You will then need to reboot the BE3k for the changes to take affect.
Thanks,
Brian Meade
06-04-2013 03:39 PM
Hi Brian,
The web administrative interface for the BE3000 doesn't have "SMTP Configuration" under System Settings. It does have a "Voicemail Notification" section, but that only lets me configure the outgoing email server and a forwarding address for undelivered emails.
-j
06-04-2013 03:42 PM
Jefferson,
Yea, I just noticed that workaround needs to be done via root access so you will need to open a TAC case to have that changed. This issue is being tracked by CSCub26360.
Thanks,
Brian Meade
06-04-2013 03:44 PM
Thanks, Brian! I'll contact TAC, then. Glad to hear they can modify that via root access. I was afraid it was truly hardcoded.
-j
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide