Custom holiday prompt

[Pcmod]

Good afternoon,

we updated to last version of 3CX.

There is a condition we cannot explain about custom holiday messages.

We expect to hear the custom message set in the specific date instead of the general one, exactly like it happened in 3CX version 18.

We tried to attach a message in today’s date set as a holiday. But after a test, we cannot hear that message (Ponte 2 maggio.wav), but we hear the standard one (Festività IT-EN.wav) from the digital receptionist selected for “holiday” option in the main queue.

Where is the issue?

 

[JoshWS]

Could be a bug with the file, perhaps try downloading it, listen to it and ensure its correct, then put it in the 3cx audio converter and re upload to ensure its in the correct format

 

[SteveITS]

@Pcmod Did you set up the script? https://www.3cx.com/docs/holiday-script/

 

[fortech]

In case it might be helpful, I know I had a few cases when I upgraded some 3cx v18>v20 instances last year, and some of the audio recording file names were -very long- and they used to work ok on prior 3cx, and did not work on the new 3cx version, and things failed silently (ie, 3cx behaved like the long filename audio files did not exist, post upgrade to v20). (in my case they were audio files used for IVR Greet message.. slightly different use case than your situation - but still relevant maybe? I think ?)

ie, all this to say - possibly one easy thing you can try is to give the audio file(s) in question - very short - concise not verbose - names. for example maybe "1Apr2025greet.wav" instead of "April-1-2025-new-greeting-message.wav" as an illustrative conceptual hint.

I am not entirely sure if there is a precise / concrete / limit internally in how 3cx prefers to refer to wav filenames / a hard-coded limit (ie, filenames must be 32 characters or less, no special characters, etc) but at the very least it is a trivial thing to test-try-change and see if it makes any difference to your situation.

-Tim