CUC Forums

« Back to CUPI Questions

Http 405 on wav file upload for voicemail

Combination View Flat View Tree View
Threads [ Previous | Next ]
Http 405 on wav file upload for voicemail
Answer
11/29/12 5:39 PM
We have a wav file to upload against a username for voicemail.

This is the URL

<CUCServer>/vmrest/users/6e2ca867-b1fc-4e27-ac66-3f32965878fd/voicename

we use to do a Http POST on, and write the wav file as a stream.

We are able to successfully upload to an

8.5.1ES54.13029-54

whereas when we try the same on an

8.5.1ES47.12024-47

we get the following exception

Failure runHTTPCommandPost (execute3)java.io.IOException: Server returned HTTP response code: 405 for URL: https://<CUCServer>/vmrest/users/6e2ca867-b1fc-4e27-ac66-3f32965878fd/voicename

Seems clear that POST is blocked on this particular server.

Is there a way we could get the server to allow POST?
Flag

RE: Http 405 on wav file upload for voicemail
Answer
12/3/12 6:20 AM as a reply to Vinay S.
There were some changes related to voice name upload using APIs in the ES version which you have mentioned.
A similar thread which you can refer is:
http://developer.cisco.com/web/cuc/forums/-/message_boards/message/8940762
 
Flag

RE: Http 405 on wav file upload for voicemail
Answer
12/4/12 7:07 AM as a reply to Utkarsh Katiyar.
Thanks Utkarsh, that helps us communicate the same to the Customer.
 
The other thread your mentioned states the same issue, where may we find what exactly the change is with the API? Could you point us to an alias or contact/
 
Thanks again,
Vinay
Flag

RE: Http 405 on wav file upload for voicemail
Answer
12/12/12 7:16 AM as a reply to Vinay S.
Vinay S:
Thanks Utkarsh, that helps us communicate the same to the Customer.
 
The other thread your mentioned states the same issue, where may we find what exactly the change is with the API? Could you point us to an alias or contact/
 
Thanks again,
Vinay

 
I am able to add the voice name for a user using the said API but its a PUT request not a POST. Try executing a PUT request on the same setup, if it still fails then we can have a webex session to debug the issue further.
Flag