The "Your message has been sent" prompt that you are referring to is actually associated not with the "hang up" but with the message taking/message delivery function of Unity. When you are calling to leave a message for a user, and press #, that is a part of the conversation that you don't have access to change the prompts for. Hence, your "hang up action" is doing just that, after the caller presses # to indicate they want to send the message as opposed to mark it urgent or future delivery, etc. If you take a look at the wallet card for the record a message section, this is illustrated well. Sorry for the bad news
You're welcome. No, because it is part of the "record a message" conversation, I can think of no work-arounds. Changing caller input would only affect what happens when a caller is hearing the subscriber greeting.
There are always ways to hack the system, which was a lot easier to do in the Windows based Unity, but if you are good a Linux and if the files are visible in the O/S (I'm guessing not but have never tried to look in Connection), the only way to do what you want would be to figure out what conversation .wav file is played when a caller presses # after recording a message and then rename that file to .old or something and replace that file name with a silent .wav file of a second long or so. You would NOT be TAC supported and any upgrade or ES to the system would again overwrite your silent file.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...