It is already implemented and seems to work well. A small "pre beta" of the new ANet version was released a few days ago. If you want you can join?

There are not all functions for the new version implemented yet (the voip feature isn't finished yet and also some changes on the entity system have to be done). After that a public Beta will be released.

Edit: Had a lot of fun on my vacation, thanks

great to hear that!

I have a small question concerning the new ANet Voip system (version 1.4+) and portforwarding. As the new ANet Voip feature is now peer-to-peer based, does it mean you have to forward also the ports as a Voip client if your pc is behind a router to be able to communicate?

good question! would like to know that, too.

You only have to forward the VoIP server port. A technic called NAT punsh-through is used to determine the client ports outside the router. Thus no portforwarding is needed for the clients.

Thx thats good.
Now if you have a server and connect 2 clients both behind a router, is it possible to use the udp socket functions to directly send data between the two clients by using this "NAT punsh-through technique" so you only have to forward the port of the server if it is behind a router as well? Would this be possible? Like your VOip feature allready does more or less.

Yes that would be possible.

Shematic network example:


The problem is, that the routers change the port number of client 1 and 2 because of NAT/PAT as you can see in the example above. Thus if the server wants to send a packet to client1 and uses port 2300 it won't work.

Solution (NAT punsh-through): The server is reachable through port 2300 because port forwarding was done here. Now all clients contact the server by sending a packet. Thus the server can store the destination ports of the packets (which are 8947 and 38495). If the server then sends a packet to these ports, the clients will receive the packet.

And that's it. It's very simple.

1. Thx for quick and nice reply
2. Does this mean if i know which ports the clients routers are using client1 can also send a package directly to client 2 using the port 38495?
3. So this means if I don`t manually do portforwarding and tell the router which port it has to use it just gonna choose a random port that is usable if i send package from a pc behind a router, to the server.
4. Now I think the header of every package contains the port it was sent from but how can the server find out the port? Is there a function to find it out?
5. Thx for your great help

1. No problem

2. Yes. The server should store all ports of the clients in a table. If a new client connects, you could send the whole table to all participants for example.

3. Yes, that's basicly what NAT/PAT is doing. This technic allows you to access the internet through more than one pc at the same time, although you only have one internet ip address. You can find more informations about that in wikipedia.

4. Every packet contains the source and destination port. You are right, this is currently not possible because the sock_recv() function doesn't return the destination port. This will be changed!

I was reading stuff about udp, portforwarding... all day but wasn`t quite sure if i understood all the stuff correctly. So thx for the extra explanations.
4. Awesome can`t wait Is it realistic that this feature will be avaiable in ANet v1.5 allready?

I think this would be a better port forwarding workaround than using upnp

Thx again