I'm not sure about the custom headers part, but converting hex to ascii is probably best handled by a peripheral (IP IVR/CVP) so you can use Java to do it. The only way I could imagine doing this in ICM is to have a massive custom function which parses every value then does a if/then check to replace the hex with ascii. This will not be pretty and it will probably take a long time to get the custom formular right. Also, not sure if such a long custom formula would be supported.
If you are only receiving numbers in the UUI string, you can use the attached ICM custom function to convert it. This script converts up to 24 ASCII characters (that's 48 hex characters when represented in ICM). This script uses the fact that ASCII 0 - 9 characters are 30 - 39 in hex, so we can just use every other number.
If you need to convert specific letters or symbols as well, you can could do that with a more complex ICM custom function, but they are very limited and won't work with any kind of recursion or if custom functions call other custom functions more than a few times in a script.
If you need to convert most or all ASCII characters, you'd need to do it in Java in an IVR application.
Edit: I have attached a new script that safely ignores any ASCII character except numerical digits; so, it works the same as the first script but will skip over hex characters that are not ASCII 0 - 9.
Ok, I have figured the max amount of abridged hex-to-ascii code we can do in ICM custom functions (therefore, this is pretty much the max that ICM can do) is 19 ASCII characters of 0-9,A-Z,a-z. You could do more character lenght if you recognize fewer ASCII character hex values, or you could add recognition for more types of characters and further limit the number of total characters your can recognize. That might be nice actually, if you needed a few extra characters like a comma or period or plus sign, but at a max length of 16 - 18 ASCII output characters.
FYI, ICM custom functions are limited to 30,000 characters and 32 stacked function calls (you can only stack/chain up to 32 function calls within each other). Modularizing the code doesn't help, either, and actually seems to further limit how much you can get done with this code.
I put all this code into a bitbucket repository so it's easier to manage, and you can get updates that I might make to the code in the future.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.