VoicemailAPI - patchUserpoliciesUserId not setting Enabled Flag

Platform API JavaScript SDK
1

When using the patchUserpoliciesUserId method the enabled flag is ignored and the response only returns the current status and doesn't update it

2

Sorry, this slipped through the cracks and I missed the post. I'm seeing the same behavior and have opened issue CORE-5973 to fix the API resource. There appears to be a bug that is causing several of those properties to be ignored.

3

Hi Tim thanks for responding. Any Update?

4

Tim is there any news or update?

5

The resource was updated a few days ago: PATCH /api/v2/voicemail/userpolicies/{userId}

6

Based on what I see it looks like functionality was taken away? How would you enable or disable voicemail on a user now?

{
"alertTimeoutSeconds": 0,
"pin": ""
}

7

The parameters that were removed never worked; the API was out of date and did not represent the functionality of the system. It does now.

To receive a voicemail, the user must have the receive voicemail permission. The enabled property is a read-only property that represents whether or not they have the permission. If you want to enable voicemail for a user, grant them the permission.

8

Ok but that leaves a huge gap in needed functionality. Whether you import via AD, CSV or manually add users to the system you have no way to enable Voicemail without going into each person. This is approximately 4-5 clicks. Imagine needed to update 100+ users it could take an hour. As an implementer we need to be efficient to have any hope of making margins adding an hour + to enable voicemail is not good. Either enable it through the import function of AD and CSV or allow the API to toggle it and then we can write the tools we need. Hopefully this makes sense if not feel free to call me at 952-832-3757

Thanks
AG

9

You can manage a role's permissions with PUT /api/v2/authorization/roles/{roleId} (or configure the role once in the UI) and use PUT /api/v2/users/{userId}/roles to manage the user's roles. This means all you have to do to enable voicemail for a user is assign them a role that has the voicemail permission.

10

I don't think that works I believe we've tried that. I will test that again and let you know.

11

If the APIs aren't working as expected, please post a new topic with information about what you're doing and what's happening and I can take a look.

12

Functionally this does not appear to be working even if you do it via the GUI. I have Role with the following permission.

When you try to leave VM or access VM it says this voicemail is not configured.

13

Let me know if you still want me to start another thread.

Thanks
AG

14

The feature for voicemail access to be controlled by permissions only is currently only in limited release, but is currently slated for official release next month. Once the feature is released, just applying a role with the permission to the user will enable their mailbox.

15

Hi, Following on this thread,

I am looking for a way to enable voicemail for multiple users.
I have tried the permission change suggested in previous thread, but this doesn't 'enable' voicemail.
The only way is the manual 'click in the user / edit profile / enable voicemail'

Is the new release which should enable this feature still in testing ?
When can we expect the release to be available

Is there a way to enable voicemail using :

  • AD import
  • csv import
  • API PATCH /api/v2/voicemail/userpolicies/{userdID}

Would you rather suggest this is raised via a support ticket / feature enhancement request

If you would rather this message is part of a new thread, I can create one.

Thanks

16

You need to open a ticket with PureCloud Support to have the feature toggle enabled to control the voicemail setting via permissions. The feature is still in limited availability.

17