2142 VOIP Doesn't work anymore. Options

[Rudelaw]

Could someone please help me out here. The internal voip on my 2142 servers was working fine before the patch. Now it doesn't. I'm assuming it's something obvious, because everyone just keeps ignoring me..... This is the third time i've asked for help.... So, pretty please, could someone help me out? What exactly should my ports be set to? Is there something else I need to do? Should I just submit a support ticket and wait a few days for a response?

My servers have been patched and my cortex updated. I saved my configs and restrted coretex as well.

Ticket# 4025166PLNT

[doc]

How many 2142 instances do you have running on that server? If you have more than 1 on the same box they fight over the port and only 1 instance can win.

[Rudelaw]

2-2142 and a bf2 server. I have them set to different ports.

[doc]

but does the VOIP server run on the same port? I don't think you can control the internal VOIP port, just external.

I bet one of your 2142 instances VOIP works and the other does not.

[Rudelaw]

They are the same as they were since October... they all worked then but they don't now. I think it's something with the last Cortex update. Like I said, they worked before and i checked the other 2142 server, it's not working there eithier.

[doc]

Quick stupid questions

1) Check to make sure the cortex update did not alter your voip settings.

2) Is voip still enabled?

3) Is remote voip server enabled?



To be honest, I am very surprised that it worked before the update. Anytime you stick 2 battlefield instances on the same server, only 1 of their VOIPs will work. I suffered with that many times until I figured out how to run a remote VOIP server.

[Rudelaw]

1. I'm pretty sure there the same (scratches head). This is what they are now.

sv.voipBFClientPort 55226
sv.voipBFServerPort 55026

My other 2142 servers last digit is 5 and my BF2 is 7.

2. yes (gives Doc the do you think i'm stupid look.)

3. no, because i'm not using a remote server. (gives Doc the same look again)

Trust me on this Doc, they worked before. The BF2 voip was always a little sketchy, (i could hear others, but they couldn't here me kind of thing) but the "2" 2142 servers voip worked flawlessly until now. I have 50+ active members in my clan and when these things don't work, I hear about it.

By the way, I know how to run a remote voip server, I did it with BF2. We had to give up our dedicated non-ranked box when we decided to shell out almost $400 a month for this one. We shouldn't have to have another box for Voip when the one we have is perfectly capable of running it.

If Kevin and these other guys can take the time to add a crappy game like Stalker to Cortex, surely they could figure out how to integrate remote VOIP into it???

Sorry, just a little frustrated here...........Like I said, it has worked for the last six months now it doesn't.

[doc]

They had mentioned adding a VOIP server to the engines page at one time but have not heard anything lately. Would help out the ranked server people. The edit config would only be port and password.

I have 3 remote VOIP servers running on an unranked box and they only take up 940kb of RAM each.

[Rudelaw]

I am forwarding this ticket to our Cortex Development team to have this issue looked into further.

Lisa N
Technical Support
www.theplanet.com


I guess no one is going to be able to help me out here....

[UniSoL]

They had mentioned adding a VOIP server to the engines page at one time but have not heard anything lately. Would help out the ranked server people. The edit config would only be port and password.

I have 3 remote VOIP servers running on an unranked box and they only take up 940kb of RAM each.

You should rent out VOIP servers Doc. That is if it is allowed with all the rules about 2142 and reselling.

[doc]

I would do it if anyone is interested. Just let me know.

[Angry_Kid]

Rude -- I had a similar thing happen back in the BF2 days; 2 BF2 servers running on one box using different IPs. The VoIP worked for the most part, then (whether it due to a patch, I don't recall) for some reason, VoIP stopped working completely.

It may sound counterintuitive, but the only way we were able to re-establish VoIP on both instances was to run both BF2 instances off of the same IP using (of course) different game ports and VoIP ports.

When 2142 came out, we again tried running 2 instances on 2 different IPs on the same box. VoIP refused to work consistently - sometimes one-way audio, sometimes not at all. We went back to the '2 instances off the same IP' method and VoIP worked flawlessly.

[jestermiami]

did u update to cortex 1.36?? if you did the ports have all changed by +1000
sv.voipBFClientPort 56225
sv.voipBFServerPort 56025
sv.voipServerPort 56125

From the cortex 1.36 news-

CODE

Fixed the query, voip, rcon, and 2142cc ports for Battlefield 2142 servers. These ports are now 1000 higher than before to prevent conflicts with BF2 servers running on the same IP. Save your 2142 server configs to apply this change. Remember that you now have a new rcon and 2142cc port to connect to!

[Rudelaw]

did u update to cortex 1.36?? if you did the ports have all changed by +1000
sv.voipBFClientPort 56225
sv.voipBFServerPort 56025
sv.voipServerPort 56125

From the cortex 1.36 news-

CODE

Fixed the query, voip, rcon, and 2142cc ports for Battlefield 2142 servers. These ports are now 1000 higher than before to prevent conflicts with BF2 servers running on the same IP. Save your 2142 server configs to apply this change. Remember that you now have a new rcon and 2142cc port to connect to!

I tried this. I've tried everything. No one at I365 seems to care....You would think for the price of a car payment I could get a little service.

Whether I have it enabled on 1 server or 3, it doesn't work anymore. This port or that....It doesn't F%$#@&*% work!

What do I have to do to get some help with this issue? I've had a support ticket in for 2 weeks now, no help.

[doc]

[Rudelaw]

Udated cortex to 1.36a. Updated 2142cc, now it works. Thanks..........I think??

[klaude]

Maybe it was a cc bug then. I was scratching my head over your VOIP issues, but 1.36a didn't make any VOIP related chages at all.

[doc]

When in doubt, blame 2142cc.

[Rudelaw]

Still getting some weird issues from the BF2 voip. Some people can hear me, but I can't hear them and I can here some and they can't hear me......strange?? Too bad there's no voip in Cortex to allow for stand alone instances (wink, wink, Kevin), I probably wouldn't be having these problems..

[R_OReilly]

We did a lot of testing trying to get VoIP for multiple BF2/2142 instances to work on our servers. The internal VoIP server for both BF2 and 2142 binds to 0.0.0.0. The apparent effect of this is that it only really listens consistently on the primary IP of your box. The BF2 client will only look for an internal VoIP server on the same IP as your BF2 server, so servers on secondary IPs don't seem to work. Our experience was that one BF2 with internal VoIP on the primary IP was fine. If you put another BF2 with internal VoIP on a different IP, the second VoIP would not work and the first would be sporadic at best. This is probably what's happening on your servers.

If your only option is to use internal VoIP on a single box, you will need to run ALL BF2 and 2142 instances on the primary IP with different ports across the board. Our Research in various forums showed fairly good luck with this option. The internal VoIP code is not as stable as the dedicated code but it does work.

The BEST solution is to run dedicated external VoIP servers either on the same box or preferably on a separate unranked box. That is what we ended up doing and it has been rock solid. We have one BF2 VoIP supporting 4 instances (2 ranked, 2 unranked) and one 2142 VoIP supporting 3 instances (2 ranked, 1 unranked). You have to remember to patch your VoIP server whenever you patch the game servers or it will reject connections due to version mismatch. The dedicated BF2 VoIP server also binds to 0.0.0.0, so it will only listen on the primary IP of the box. The dedicated 2142 VoIP can be configured with a different IP but we've stuck with using the primary IP on our unranked box where both VoIP servers run. The IP address for each line in the 2142 voip.con file should be the same and it is the IP you want to listen on.

Hope this helps!