Setting Alternate Extensions in 7.1.3.68

Version 1
    This document was generated from CDN thread

    Created by: Jon Finke on 04-04-2011 06:38:55 PM
    I have been working with CUPI to provision our new voicemail system (upgrade from 4.x to 7.x) - and have been successful in extracting data via the REST calls (for the most part).  My first "write" attempt was to set an alternate extension for a mailbox.  
     
    I am sending the following XML via a POST request (using the Oracle APEX_WEB_INTERFACE package):
    <?xml version="1.0" encoding="ISO-8859-1"?>

    <AlternateExtensions>
        <IdIndex>1</IdIndex>

       <DtmfAccessId>15183696771</DtmfAccessId>

    </AlternateExtensions>
     
    To the target URL of
    https://xxxx.rpi.edu/vmrest/users/801373ed-732f-4ddc-a776-db8628e4c4f8/alternateextensions
     
    and I am getting back the following error message in the cisco error page
     
    The server refused this request because the request entity is in a
    format not supported by the requested resource for the requested method ()
     
    Thoughts?

    Subject: RE: Setting Alternate Extensions in 7.1.3.68
    Replied by: Jon Finke on 06-04-2011 01:49:40 PM
    After more poking, tcpdumping, googling, etc - I determined that the problem was a missing "Content-Type: application/xml".   I am now setting alternate extensions, SMTP notify devices and my integration project is moving forward once again!  (Using Oracle APEX in case anyone cares).

    There was much rejoicing!