In the new RC2 patch notes, it is listed that there is now support for .raw files for prompts, which should improve the efficiency of the Media Server and phone system itself whilst dealing with queues, etc. Which format does 3CX expect in the .raw file? As there is no header (i.e. raw), 3CX will be reading this data interpreting a certain format, sample rate and sample size. My educated guess is that it will be in the format that the phone system is set to use - one of either g711a or g711u. If 3CX could confirm this it would be great. Assuming that's correct, if a phone call itself is dropped into another codec - example, an endpoint calls with g729 only - then will 3CX be using the .raw file as a g729 file, or will it continue to read .raw files in whatever the default format is? An expansion to the feature could work similarly to the Asterisk system, in which you store multiple files with extensions like .ulaw, .alaw, .g729, .gsm, etc. and the system picks whichever is the closest match to it's required codec - I imagine this would further increase the efficiency of the phone system, however it would require either X sets to be uploaded, or a service to pre-transcode those files when given a higher quality source in the beginning - example, you just upload a 16-bit 8KHz PCM file, and 3CX will produce and save those 5 raw formats into it's prompts folder. Furthermore, will it be accepting .raw files for Music on Hold content? This would be a great improvement, as we can deliver much better 'end-quality' music on hold content if we're delivering in g711 format rather than PCM.