Difference between revisions of "VM/Current/VMPEGuide/PlanningVoicemail"

From Genesys Documentation
Jump to: navigation, search
(Published)
(Published)
Line 7: Line 7:
 
|sectionHeading=Limitations and assumptions
 
|sectionHeading=Limitations and assumptions
 
|alignment=Vertical
 
|alignment=Vertical
|structuredtext=Voice Voicemail Service integration with Workspace Web Edition and Web Services and Applications is in progress. The integration brings an appearance of actionable voice mailbox information in the Workspace Web Edition UI, presenting users with Message Waiting Indicator(s) for each voice mailbox assigned to them either directly as a personal mailbox or as a group mailbox via membership in a group(s) having a mailbox provisioned. Users still have access to voicemail from Workspace Web Edition by dialing directly to a voicemail access number, which is 5555.
+
|structuredtext={{Notices|Notice=PEComingSoon}}
 +
<!--Voice Voicemail Service integration with Workspace Web Edition and Web Services and Applications is in progress. The integration brings an appearance of actionable voice mailbox information in the Workspace Web Edition UI, presenting users with Message Waiting Indicator(s) for each voice mailbox assigned to them either directly as a personal mailbox or as a group mailbox via membership in a group(s) having a mailbox provisioned. Users still have access to voicemail from Workspace Web Edition by dialing directly to a voicemail access number, which is 5555.-->
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 32: Line 33:
 
|anchor=StorageReqts
 
|anchor=StorageReqts
 
|alignment=Vertical
 
|alignment=Vertical
|structuredtext====Choosing Voicemail storage===
+
|structuredtext={{Notices|Notice=PEComingSoon}}<br />
 +
<!--
 +
===Choosing Voicemail storage===
 
To store mailbox metadata and messages, consider the following supported options for storage in the Private Edition deployment:
 
To store mailbox metadata and messages, consider the following supported options for storage in the Private Edition deployment:
  
Line 80: Line 83:
 
**Store access keys in Azure Key Vault and mount it via a Container Storage Interface (CSI) driver.
 
**Store access keys in Azure Key Vault and mount it via a Container Storage Interface (CSI) driver.
 
**Create access keys as a Kubernetes secret and volume mount the Kubernetes secret. (This option is considered less secured than the CSI driver approach.)
 
**Create access keys as a Kubernetes secret and volume mount the Kubernetes secret. (This option is considered less secured than the CSI driver approach.)
*The '''values.yaml''' file can be overridden for configuring either a Kubernetes secret or CSI driver, which is explained in {{Link-SomewhereInThisVersion|manual=VMPEGuide|topic=ConfigureVoicemail|anchor=OverrideHelmValues|display text=Override Helm chart values}}.
+
*The '''values.yaml''' file can be overridden for configuring either a Kubernetes secret or CSI driver, which is explained in {{Link-SomewhereInThisVersion|manual=VMPEGuide|topic=ConfigureVoicemail|anchor=OverrideHelmValues|display text=Override Helm chart values}}.-->
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section

Revision as of 19:44, July 1, 2021

This topic is part of the manual Voice Microservices Private Edition Guide for version Current of Voice Microservices.

Find out what to do before deploying the Voicemail Service.

Limitations and assumptions

Content coming soon

Download the Helm charts

For information about how to download the Helm charts, see Downloading your Genesys Multicloud CX containers.

The following table identifies the Helm chart version associated with the Voicemail service.

Service name Helm chart version
voice-voicemail voice-voicemail-9.0.xx.tgz

Third-party prerequisites

See the Third-party prerequisites for the Voice Services.

Storage requirements

Content coming soon


Network requirements

Content coming soon

Browser requirements

Not applicable

Genesys dependencies

For detailed information about the correct order of services deployment, see Order of services deployment.

GDPR support

Content coming soon
Comments or questions about this documentation? Contact us for support!