McDewey

C H A P T E R 9 Cisco Unity Connection Provisioning Interface (CUPI) API -- Voice Names Links to Other API pages: Cisco_Unity_Connection_APIs • About Voice Names, on page 19 • Listing and Viewing, on page 19 • Setting Voice Names, on page 20 About Voice Names Many objects available via the CUPI interface have a voice name field. There are two ways to access the voice name for these objects: • For Connection versions 7.x and 8.0.x the voice names are accessed by using the VoiceFileURI. Modifying the voice name as a voice file requires a three step process as detailed below. • For Connection versions 8.5 and later the voice name access has been simplified so that it can be accessed by using a VoiceNameURI. This new URI is a standard sub-resource of the primary resource URI (see example below). Modifying the voice name by using the new URI reduces the three step process to a single step. The old VoiceFileURI still works in the later versions of Connection, but use of the new URI is easier. http://<server>/users/<user object id>/voicename) Listing and Viewing Voice Name GET for Connection 8.5 and Later Use the standard VoiceNameURI directly to get the file: GET http://<connection-server>/vmrest/<resource>/<resource id>/voicename The response will return the audio/wav data for the voice name. Cisco Unity Connection Provisioning Interface (CUPI) API 19