- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-24-2019 02:58 AM
Hi,
So the team i'm currently working on is actually trying to get/read the content of a document within the "document" folder, we did find a solution thanks to this post :
However we soon realized that this wasn't a viable solution for what we wanted to do. We have multiple language folder and for some reason we can't access all of them using the port 9080/9443 as it seems to be bound to the "Default IVR Language Configuration".
For example we can acess the "parameters.xml" file in the en_US folder but it won't work in "de" however if we change the Default IVR Language to "de" it will work but not anymore with "en_US"...
Has anyone got a solution using the api, configurations or something else to access or download the content of a file from the "document" section ?
Solved! Go to Solution.
- Labels:
-
UCCX
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2020 02:46 AM
We found out that we just needed the header "Accept-Language" in our web request to solve our problem.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-26-2019 07:46 AM
If you are creating a multi-language application, you can change the language dynamically for the calling contact in the "Set Contact Info" step. Once this done, the search order for the contact will be adjusted by the language specific directories in the repository.
An example using prompts is here: Changing call contact language
If your application needs to remain static, I would recommend using a different trigger for the application, for each different language used, and have the specific desired language assigned to each the of trigger defaults...
Hope this helps.
-Sean
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2020 02:46 AM
We found out that we just needed the header "Accept-Language" in our web request to solve our problem.
