VM/Current/VMPEGuide/PlanningVoicemail - Revision history

WikiSysop at 08:31, March 27, 2023

2023-03-27T08:31:58Z

WikiSysop at 20:01, September 13, 2022

2022-09-13T20:01:25Z

WikiSysop at 15:01, September 8, 2022

2022-09-08T15:01:38Z

WikiSysop at 14:31, September 8, 2022

2022-09-08T14:31:33Z

Show changes

Corinneh: Published

2022-03-07T18:41:15Z

Published

Corinneh: Published

2022-03-07T18:15:13Z

Published

Corinneh: Published

2022-03-02T14:08:12Z

Published

Show changes

Ed.jamer@genesys.com at 17:11, October 9, 2021

2021-10-09T17:11:04Z

Valentina.petrov@genesys.com: Published

2021-07-01T19:44:21Z

Published

Corinne.hicks@genesys.com: Published

2021-06-30T19:27:50Z

Published

@@ Line 44: / Line 44: @@
 *Persistent Volume (PV) is a piece of storage that can be mounted to a Voicemail Service deployment inside the Kubernetes cluster.
 *Voicemail Service requires a separate storage class and PV to be created for a Voicemail storage.
 *If the customer wants to extend the deployment to more than one Kubernetes cluster, Voicemail Service requires to mount the same PV for all the Kubernetes cluster for that customer.

@@ Line 105: / Line 105: @@
 |sectionHeading=Genesys dependencies
 |alignment=Vertical
-|structuredtext=For detailed information about the correct order of services deployment, see {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=ContDepOrder|display text=Order of services deployment}}.
+|structuredtext=For information about dependencies for Voicemail Service, see {{Link-SomewhereInThisVersion|manual=VMPEGuide|topic=DeployVoicemail|anchor=AdditionalPrereqs|display text=additional prerequisites}} on the {{Link-SomewhereInThisVersion|manual=VMPEGuide|topic=DeployVoicemail|display text=Deploy Voicemail}} page. For detailed information about the correct order of services deployment, see {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=ContDepOrder|display text=Order of services deployment}}.
 |Status=No
 }}{{Section

@@ Line 95: / Line 95: @@
 |sectionHeading=Network requirements
 |alignment=Vertical
-|structuredtext=For more information, see [[Draft:VM/Current/VMPEGuide/Planning|Network requirements]] in the ''Configure and deploy'' section of this guide.
+|structuredtext=For more information, see {{Link-SomewhereInThisVersion|manual=VMPEGuide|topic=Planning|anchor=Network|display text=Network requirements}} in the ''Configure and deploy'' section of this guide.
 |Status=No
 }}{{Section

@@ Line 148: / Line 148: @@
        {"consumer":
+          [
-             {"name":"Dan Akroyd"},
+             {"name":"Dan Archer"},
              {"phone":"555556161"},
              {"phone":"555556162"},
              {"email":"danny@hollywood.com"},
              {"email":"funnyguy@comedy.org"},
-             {"fbid":"Dan Akroyd"}
+             {"fbid":"Dan Archer"}
+          ]
        }],

@@ Line 176: / Line 176: @@
 *'''Export Me''': The API for '''Export Me''' returns the list of message IDs with message media URL to download the media.
 **The media URL is also authenticated and authorized with the GWS token.
-*The Voicemail Service is exposed via the Kubernetes service, and can be accessed by URL in any region: http://voice-voicemail-service.voice.svc.cluster.local:8081/fs (The FQDN remains same in all the regions wherever voicemail service is deployed).
+*The Voicemail Service is exposed via the Kubernetes service, and can be accessed by URL in any region: <nowiki>http://voice-voicemail-service.voice.svc.cluster.local:8081/fs</nowiki> (The FQDN remains same in all the regions wherever voicemail service is deployed).
 *Append the API URL with the above-mentioned base URL for accessing the APIs.
 *The Voicemail service authenticates and authorizes each request with GWS. The Voicemail service requires the OAuth token in the header for the following the API calls:

@@ Line 7: / Line 7: @@
 |sectionHeading=Limitations and assumptions
 |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}}
 |Status=No
 }}{{Section
@@ Line 32: / Line 33: @@
 |anchor=StorageReqts
 |alignment=Vertical
-|structuredtext====Choosing Voicemail storage===
+|structuredtext={{Notices|Notice=PEComingSoon}}<br />
 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.
 **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
 }}{{Section