Hi Ryan,

Yes, it is allowed to create a user template via REST APIs.

You need to do the following for achieving this:

POST: https://<Connection-ip>/vmrest/usertemplates?templateAlias=<template>

Where template for a voice mail user would be "voicemailusertemplate", so the request would become

https://<Connection-ip>/vmrest/usertemplates?templateAlias=voicemailusertemplate

And in the request xml body you can give:

<UserTemplate>
<Alias>AkkiTemplate</Alias>
<DisplayName>Akanksha Template</DisplayName>
</UserTemplate>

As a response, you will receive the user template object id. You can view this template by hitting a GET : https://<Connection-ip>/vmrest/usertemplates

Let me know if you have any other question.

Thanks & Regards,
Akanksha A

Cisco Unity Connection Provisioning Interface (CUPI) API -- HTML Notification Templates

Howard

Hello,
  I am trying to create a user in a version 7.1.5 Unity Connection server.
A use the following informations:
- Method: POST
- URI: https://10.230.110.177:8443/vmrest/users?templateAlias=voicemailusertemplate

- XML Data:
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<User>
  <Alias>tst2345</Alias>
  <LastName>PROVUser</LastName>
  <FirstName>Test1</FirstName>
  <DisplayName>Test1 PROVUser</DisplayName>
  <DtmfAccessId>23456</DtmfAccessId>
</User>


I got the following error: The remote server returned an error: (400) Bad Request
For information, I can get, update and delete a user. Only the create process fail!
Christian

Hello Utkarsh,

  The exact version is 7.1.5.0ES33

  And for the request, I got an exception when I send the request to the server with the error message giving in my first post. So I don't receive any answer to my request ... and I don't have any other information.

Christian
 

Hello,
  My code is based on the sample available on the CUPI documentation (http://developer.cisco.com/documents/4453236/4479360/VoiceMailboxQuotaReport.zip/f2437d92-fe8b-4cc9-9729-674ea5827ad3?version=1.0).
All the others actions work correctly.
I can get (GET method), update (PUT method) and delete (DELETE method) existing users or update user's PIN code.
I try yesterday to create a "user template" an I got 405 (405 Method Not Allowed ) exception error. It's normal "user template" creation is not allowed with our CUC version !
So can you help me to find where is the mistake in my create action.
Best regards
Christian
 

Hello,
  I have tried to do to POST actions:

First one, I tried to create a contact with the following informations:
- Method: POST
- URI: https://10.230.110.177:8443/vmrest/contacts?templateAlias=voicemailusertemplate
- XML Data: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><Contact><Alias>ctc2345</Alias><DisplayName>ctc2345</DisplayName></Contact>
For this firts test, I got the same error: The remote server returned an error: (400) Bad Request.
-------------------------------
On a second time, I tried a POST to reset a user's MWI with the following informations:
- Method: POST
- URI: https://10.230.110.177:8443/vmrest/users/75adf033-6a05-4460-bc58-e623186924ec?method=resetmwi
- XML Data: Nothing
For this second test, I got the result code: 204 - NoContent
Thus it works on the second test ...
Have you some idea ?


Christian

OK, I can try to get these informations but why did it work when I do a PUT action like this:
- Method: PUT
- URI: https://10.230.110.177:8443/vmrest/users/75adf033-6a05-4460-bc58-e623186924ec
- XML Data: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<User>
  <Alias>tst12345</Alias>
  <LastName>PROVUser</LastName>
  <FirstName>Test</FirstName>
  <DisplayName>Test PROVUser</DisplayName>
  <DtmfAccessId>12345</DtmfAccessId>
</User>
I use the same programming code for the two actions. I only change the method ....

Hello,
  I don't know fiddler and I don't have a lot of time to understand, install, parameter and use it !
Is it possible to get traces on the unity connection server concerning vmrest requests ?
To see what is received and eventually what is wrong ...
Christian

Alright. So you must be getting an error XML in the response something like <ErrorDetails><errors>.....That's why I asked for the complete output of the request.
This issue has been fixed as a part of CSCty85181 in 8.0ES and above branches.