At this point of time, the communication protocol is a simple, home-brew, tcp/udp mixture (tcp to negotiate the connection and parameters later udp to actualy send/receive voice).
There is nothing stopping you adding another comm protocol as the internal structure of the software is preety open.
We can even add a flag to the matching server that will describe, what comm protocols are supported by particular client.
At this point of time, i want to get it working ASAP and without too many major bugs, later on, we can work on the interoperability.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Who much compatiblity will there be with other phone systems? Will someone not using E-Phone be able to call you?
I realize the development is early in the cycle, but I wanted to check on what was planned.
S.W.
At this point of time, the communication protocol is a simple, home-brew, tcp/udp mixture (tcp to negotiate the connection and parameters later udp to actualy send/receive voice).
There is nothing stopping you adding another comm protocol as the internal structure of the software is preety open.
We can even add a flag to the matching server that will describe, what comm protocols are supported by particular client.
At this point of time, i want to get it working ASAP and without too many major bugs, later on, we can work on the interoperability.