in Counter-Strike, there is an in-bulid feature that offer to the HLTV admins to add commentator voice to the HLTV match. This is very buggy, so first let's start with HLDS voice settings. When a client connect to the HLDS, the server tells the voice paramatersto the client. When the HLDS start, the default voice settings are low. Commands:

sv_voicecodec voice_miles
sv_voicequality 3

If you want the best quality

sv_voicecodec voice_speex
sv_voicequality 5

If hlds use higher settings, and then a client connects to the server, the server tells to the client wich the current settings. HLTV is buggy because always use the low quality. HLTV can't tell the voice paramteres to the client. This is a bug since 2003 or later. I can't understad why valve don't solve this problem : (

[How to FIX it !

1. Start a “New Game” on the map of your choice.
2. in console, type and submit “sv_voicecodec voicespeex” then “sv_voicequality 5” without the quotations.
3. connect to the hltv

Voices should now be fixed!

HLTV howto

War Server > HLTV dispatcher proxy > HLTV relay proxy

players commentators spectators


HLTV support help page:
ENG
HUN

Dispatcher HLTV config:

maxclients 10 ~ limit clients, this is a commentator server only
rate 20000 >
updaterate 40 > Maximum rate settings
maxrate 20000 >
dispatchmode 2 > Important setting, now commentator can connect only
chatmode 1 > the text will be appear in the center of the relay clients
blockvoice 1 > war players usually use ventrilo, teamspeak
nomaster 1 >
forcemaster 0 > The commentator is non public
publicgame 0 >
spectatorpassword "your password"
adminpassword "dispatcher server admin password"
serverpassword "war server password > sv_password"

Relay HLTV config:

maxclients 4000 // set spectator number limit for this proxy (default 128)
rate 20000 // data rate (maximum)
updaterate 40 // update rate
maxrate 3500 // sets the maximum bandwidth rate for spectator clients (maximum)
maxloss 0.05 // Sets the acceptable packet loss rate, default value is 0.05 (5  If packet loss is higher, new spectator clients will be rejected
nomaster 0 >
forcemaster 1 > Make it public
publicgame 0 >
dispatchmode 0
blockvoice 0 > Don't block incoming commentator voice
chatmode 1 > clients can chat

WARNING!!!
if you have lots of users use chatmode 0 and reduce rates.

How can the commentator connect ?
1. First create new game, and set voice to override the hltv bug
2. set password in the console > hltv dispatcer adminpassword
3. set int the console > commentator 1
4. connect hltv dispatcher ip:port
5. Now just use the voice communication and all the spectators can hear your sound.

HLTV required files:

linux

proxy_i386.so
libSteamValidateUserIDTickets_i386.so
filesystem_stdio_i386.so
core_i386.so
hltv.cfg
hltv
valve/valvecomm.lst
cstrike/maps/required.bsp

win32

proxy.dll
FileSystem_Stdio.dll
Core.dll
hltv.cfg
hltv.exe
valve/valvecomm.lst
cstrike/maps/required.bsp

You don't need any other files, delete it to improve the hltv.

Win32 start file:
1. make a file like: starthltv.cmd
2. edit: start "HLTV" /MIN/HIGH hltv.exe -port 27020 -ip youripaddres -maxfps 10000
3. on lan: start "HLTV" /MIN/HIGH hltv.exe -port 27020 -ip youripaddres -maxfps 10000 -nodns -highpriority

Problem: The spectator on the relay proxy can't understad the voice of the commentator. The spectator should do the voice bug fix. Advertise the solution on the hltv like this, put this your hltv.cfg on the realy proxy:

loopcmd 1 3 localmsg "Do the voice fix: 1: restart cs 2: create loacl server 3: submit in consol:" 2 -1 0.89 f0f8ff
loopcmd 2 3 localmsg "sv_voicecodec voice_speex, sv_voicequality 5, connect again here" 2 -1 1 f0f8ff

localmsg <text> [<duration> <pos x> <pos y> <color hex rgba>] - same as msg, but only seen by local clients
loopcmd <id> <n> <string> - loopcmd will execute <string> every <n> seconds. <id> is a number between 1 and 64 to identify this loopcmd.
some color here > http://www.w3.org/TR/css3-color

Please apologize me for my poor level of English skill.