Same instructions as here -> http://forums.theplanet.com/index.php?showtopic=86950
BF2 remote VOIP server download -> http://vetwebhosting.com/downloads/bf2/bf2...erver_v1.41.zip
Email any questions to:
Jason
admin@vetwebhosting.com
Full Version: BF2 Remote VOIP Server Tutorial
Thanks Doc.
Sticky?
Sticky?
No, thank you Unisol. LOL!
Just FYI. I tried to connect two bf2 servers to a single VOIP server and it was a nightmare. I would recommend just creating another VOIP instance. They only take up 940kb of RAM so definitely not a resource hog on the box.
Just FYI. I tried to connect two bf2 servers to a single VOIP server and it was a nightmare. I would recommend just creating another VOIP instance. They only take up 940kb of RAM so definitely not a resource hog on the box.
QUOTE (doc @ May 4 2007, 10:43 AM) 
No, thank you Unisol. LOL!
Just FYI. I tried to connect two bf2 servers to a single VOIP server and it was a nightmare. I would recommend just creating another VOIP instance. They only take up 940kb of RAM so definitely not a resource hog on the box.
Just FYI. I tried to connect two bf2 servers to a single VOIP server and it was a nightmare. I would recommend just creating another VOIP instance. They only take up 940kb of RAM so definitely not a resource hog on the box.
o rly?
I have had more than three connected to one remote before and everything was fine. You just have to add a ridiculus amount of ports for it to work
Yep, with BF2 it worked fine, but 2142 I could never get to work with more then one server per isntance.
We've got multiple 2142 servers on one external voip. It took a while to figure out because the voip.con for 2142 dedicated is different from bf2.
Dedicated bf2 voip.con is a list of: <port> <password>
It always listens on the PRIMARY IP Address of your box. This cannot be changed.
(BTW: This is the root of the problem with the bf2 internal voip server. No matter what IP you run the game on, the voip listens on the primary IP but clients try to find it on the game server ip. Plus external voip is more stable.)
Multi-server bf2 voip looks like:
55125 pass1
55225 pass2
55325 pass3
Dedicated 2142 voip.con is a list of: <port> <password> <IP Address>
In theory you can use any IP address on your host. In practice we've found it best to just use the primary IP address of the host.
Multi-server 2142 voip.con looks like:
55425 pass1 111.222.333.444
55525 pass2 111.222.333.444
55625 pass3 111.222.333.444
We're running a bf2 dedicated voip hosting 6 servers and a 2142 dedicated voip hosting 3 servers on one box. The part you have to watch is to make sure you don't use the same port more than once in ANY voip.con file. The examples above would work running both on a server with a primary IP address of 111.222.333.444. Each port is used only once across BOTH files.
You don't have to use a really wide range of ports, I just used those numbers for clarity. I usually go up by 5's or 10's. Also, if you run multiple bf2 and/or 2142 game servers on one box, make sure the two ports you define on the gameserver for voip (sv.voipBFClientPort and sv.voipBFServerPort) are different for each server or they'll stomp all over each other.
For example, one of our servers uses these ports in its server settings:
sv.voipServerPort = 55130
sv.voipBFServerPort = 55131
sv.voipBFClientPort = 55132
The second one on that same box uses:
sv.voipServerPort = 55135
sv.voipBFServerPort = 55136
sv.voipBFClientPort = 55137
and so on...
Dedicated bf2 voip.con is a list of: <port> <password>
It always listens on the PRIMARY IP Address of your box. This cannot be changed.
(BTW: This is the root of the problem with the bf2 internal voip server. No matter what IP you run the game on, the voip listens on the primary IP but clients try to find it on the game server ip. Plus external voip is more stable.)
Multi-server bf2 voip looks like:
55125 pass1
55225 pass2
55325 pass3
Dedicated 2142 voip.con is a list of: <port> <password> <IP Address>
In theory you can use any IP address on your host. In practice we've found it best to just use the primary IP address of the host.
Multi-server 2142 voip.con looks like:
55425 pass1 111.222.333.444
55525 pass2 111.222.333.444
55625 pass3 111.222.333.444
We're running a bf2 dedicated voip hosting 6 servers and a 2142 dedicated voip hosting 3 servers on one box. The part you have to watch is to make sure you don't use the same port more than once in ANY voip.con file. The examples above would work running both on a server with a primary IP address of 111.222.333.444. Each port is used only once across BOTH files.
You don't have to use a really wide range of ports, I just used those numbers for clarity. I usually go up by 5's or 10's. Also, if you run multiple bf2 and/or 2142 game servers on one box, make sure the two ports you define on the gameserver for voip (sv.voipBFClientPort and sv.voipBFServerPort) are different for each server or they'll stomp all over each other.
For example, one of our servers uses these ports in its server settings:
sv.voipServerPort = 55130
sv.voipBFServerPort = 55131
sv.voipBFClientPort = 55132
The second one on that same box uses:
sv.voipServerPort = 55135
sv.voipBFServerPort = 55136
sv.voipBFClientPort = 55137
and so on...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.