Cisco Unity Connection Unified Messaging(Single Inbox) Fails

[master001]

Hi all,

Recently Unified Messaging(Single Inbox) feature has been failed for some reason. 

While I run the test on individual user's unified messaging accounts, I receive the error "Some possible reasons for 401: Incorrect service account name or password".   

However, in Unity connection Admin web page ->Unified Messaging -> Unified messaging service, I run the test successfully. 

This troubleshooting guide said "Possible causes include an incorrect password for the unified messaging services account, an incorrect username, or an invalid format for the username",  but this feature has been working for years. the um services account's password is set up as "never expired".    (https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/troubleshooting/guide/10xcuctsgx/10xcuctsg038.html)

Does anyone have the same issue? 

Any input/recommendation will be appreciated.

error message: 

"Some possible reasons for 401: Incorrect service account name or password.
Service account password expired. Proper permissions not granted to service
account. Exchange mailbox uninitialized."

Thanks in advance for your input and support. 

Best regards,

Master001

[Jonathan Schulenberg]

Have you migrated to OAuth? Microsoft deprecated Basic Auth last month.

https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online
CUC added OAuth support for Single Inbox in 11.5(1)SU8, 12.5(1)SU2+, and 14.

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/14/unified_messaging/guide/b_14cucumgx/b_14cucumgx_chapter_01.html

https://community.cisco.com/t5/collaboration-applications/oauth-for-office-365-unity-connection-12-5-su2/td-p/4023422

[master001]

Thanks Jonathan for the info.

It looks CUC version prior to the one you mentioned, won't support OAuth.  

Unfortunately this CUC version is 10.5,  any workaround?   setting up forwarding only?  

Thanks again,

Master001

[Jonathan Schulenberg]

Alternatives would be setting the Message Action on a mailbox to Relay (or Accept and Relay) if you have an SMTP Smarthost configured as an unauthenticated relay. Or configure Integrated Messaging which is just adding CUC as an IMAP server to a user's email client (requires VPN connectivity when remote though).

At risk of stating the obvious: CUC, and likely CUCM, need to be upgraded. 10.5 stopped receiving updates - including for vulnerabilities - in July 2020.

https://www.cisco.com/c/en/us/products/collateral/unified-communications/unity-connection/eos-eol-notice-c51-741765.html