KJ> NetMeeting is Microsoft. That alone should tell you that you will need
KJ> magic.
Yes, try vic, nv, rendevous, ivs ... Most of them open source and for
different Unixes (or is it Unices?).
KJ> Netmeeting is based on H.263 (gosh I hope I remembered the number correctly)
KJ> and this protocol opens a series of dynamic connections to and from the
KJ> talking clients.
H.263 just specifies video compression, like MPEG 4. I don't know
NetMeeting [couldn't find the source code :)], but most serious video
transmission soft is based on RTP/RTCP (RFC1889/1890) and one of it's
payload format specifications, ie RFC2032/2190/2429. It's RTP who
indicates that a pair of sockets should be open for each session, one for
data (RTP) and one for control (RTCP). If you send video and voice you
need 2 sessions -> 4 sockets. RTP just recommends using even udp ports
above 5000 for data and next odd port for control (5004 video data, 5005
video control, 5006 voice data, 5007 voice control).
KJ> At least you will need a H.263 ip masq module. I have seen such one around
KJ> on the masq list, but if it ever reached production quality I don't know.
Are you sure? I'd like to take a look at it. H.263 doesn't know anything
about networks (ip, ports, ...). Furthermore, it was originally designed
for circuit swithching networks (video phones). H.263v98 AKA H.263+ was
then designed for packet networks.
KJ> If you want to code a H.263 module I should warn you that the rfc's are
KJ> extensive.
That'd be nice. Unfortunatelly H.263 is ITU's and you have to pay for the
codec specifications. I guess meant RTP.
Matias.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
