Avaya Messaging 11.0 SP2 visual voicemail Avaya Workplace

[avayaguy23]

Has anyone tried the new visual voicemail using Avaya Messaging 11.0 SP2 and Avaya workplace 3.25? I am trying to understand how it all works. Does Avaya really require an individual to authenticate with the "Avaya Cloud" if the Avaya Messaging instance is all local AD authentication? At this point, I am testing Avaya Workplace on Windows connected to a VPN. The below setting makes it sound like the ONLY way to make visual voicemail happen is through "Avaya Cloud" but Avaya Messaging documentation doesn't say anything about having to connect the system to Avaya Cloud. Any guidance/insight would be helpful.


This setting is very concerning:
MESSAGING_SSO
Numeric: 2
Android, iOS, Windows
This parameter indicates that the messaging server uses the Avaya Cloud Authorization service. To use the visual voice mail feature, you must not change the default value.

 

[biglebowski]

isn't that just for IP Office?

 

[avayaguy23]

Nope. It’s all new in the last 4 months or so for workplace/avaya messaging natively through an API and doesn’t require CES. All the release notes say for avaya messaging 11.0 sp2 is “support for visual messaging.”

 

[kyle555]

Bout time!

https://documentation.avaya.com/bun..._Mac_Windows/page/Voice_mail_parameters_.html

MESSAGING_SSO

Numeric

2

Android

iOS

Windows

This parameter indicates that the messaging server uses the Avaya Cloud Authorization service. To use the visual voice mail feature, you must not change the default value.

Client Navigation: Not Applicable

 

[avayaguy23]

I talked to Avaya. You need to configure Avaya Messaging with Hybrid SSO through Avaya's "cloud" implementation. It is just adding additional complexities and more point of failures. They can't tell me what URLs, ports or even what server types (consolidated or web) I need to open up firewall rules on (shocker). I'm sure it goes through multiple redirect URLs. I am in the process of opening up a GRIP to support Legacy SSO through Windows or even direct through Office 365. Once again Avaya screwed this one up.