CISCO UTILITY version inconsistencies

Version 1
    This document was generated from CDN thread

    Created by: Rajesh Gadipuuri on 07-12-2012 02:03:00 PM
    Hey Guys:
    We're running couple of different version of cisco utility voice server in our lab.

    Version: Cisco Unity Connection version: 8.6.2.20000-76
    Version: Cisco Unity Connection version: 8.5.1.14900-5
    On 8.6.X we're able to access user  with URL - https://<host>/vmrest/user using voice user login credentails
    On 8.5.X https://<host>/vmrest/user returns HTTP status 404 while https://<host>/vmrest/users (plural) returns user info
    Rest all other APIs works fine on both versions
    https://<host>/vmrest/mailbox/folders
    https://<host>/vmrest/mailbox/folders/mailboxfolder/messages
    https://<host>/vmrest/messages/msgId
    https://<host>/voiceMsgURL/attachments/0
    https://<host>vmrest/mailbox/folders/mailboxfolder/messages/?method=empty
    https://<host>/vmrest/messages/msgId/?method=undelete
    Can you someone help me to resolve this incosistancy in accessing the user APIs on 8.5.1.14900-5? Is there a workaround?

    -Rajesh

    Subject: RE: CISCO UTILITY version inconsistencies
    Replied by: Utkarsh Katiyar on 08-12-2012 09:54:13 AM
    Can you share the output of https://<host>/vmrest/application.wadl on your server.
    -Utkarsh

    Subject: RE: CISCO UTILITY version inconsistencies
    Replied by: Rajesh Gadipuuri on 10-12-2012 11:16:19 AM
    Utkarsh Katiyar:
    Can you share the output of https:///vmrest/application.wadl on your server. -Utkarsh
      Attached 8.5 and 8.6 wadl files

    Subject: RE: CISCO UTILITY version inconsistencies
    Replied by: Utkarsh Katiyar on 11-12-2012 12:18:30 PM
    Rajesh Gadipuuri:

    Utkarsh Katiyar:

    Can you share the output of https:///vmrest/application.wadl on your server. -Utkarsh

      Attached 8.5 and 8.6 wadl files

     
    It seems to me that you are using a version of 8.5 which did not have end user CUPI (/vmrest/user) introduced to it.
    Can you upgrade your setup to an 8.5 build version greater than 8.5.0.21 and check whether you are able to access the API.