- Joined
- May 15, 2019
- Messages
- 13
- Reaction score
- 4
Hi everyone,
I have recently started using hotdesking at a client's site and am having an issue with the logout audio message stating "file not found" to the user.
Initially, both the login and logout audio messages stated "file not found". I was able to fix the login prompt by changing back to "Standard English Prompts Set" from a custom prompt set, but the logout prompt is still affected. I have tried several different, built-in prompt sets, with and without alternate pronunciation, to no avail. All services were restarted between tests, and I am able to search for and download the LOGGEDOUTHD prompt file and listen to it without issue, despite the message that it cannot be found.
This has persisted across several updates and is still affecting us on v20u6 (build 724). There are no pending updates for prompt sets on the system, and the system otherwise functions perfectly. I've read the few threads on these forums covering similar issues, but nothing exactly like what I'm experiencing here.
Short of rebuilding the system, is there anything that I can try?
I have recently started using hotdesking at a client's site and am having an issue with the logout audio message stating "file not found" to the user.
Initially, both the login and logout audio messages stated "file not found". I was able to fix the login prompt by changing back to "Standard English Prompts Set" from a custom prompt set, but the logout prompt is still affected. I have tried several different, built-in prompt sets, with and without alternate pronunciation, to no avail. All services were restarted between tests, and I am able to search for and download the LOGGEDOUTHD prompt file and listen to it without issue, despite the message that it cannot be found.
This has persisted across several updates and is still affecting us on v20u6 (build 724). There are no pending updates for prompt sets on the system, and the system otherwise functions perfectly. I've read the few threads on these forums covering similar issues, but nothing exactly like what I'm experiencing here.
Short of rebuilding the system, is there anything that I can try?