zap-devel mailing list
To subscribe, send a mail with subject 'subscribe' to zap-devel(at)croczilla.com.
Likewise, to unsubscribe, send a mail with subject 'unsubscribe'
to zap-devel(at)croczilla.com.
|
[
zap v0.2.1 / Alex Fritze <alex(at)croczilla.com... ]
[
wengo & gizmo <--> zap / Alex Fritze ... ]
ICE, Stun, Jingle
"Tom Germeau" <tom.germeau(at)gmail.com> |
2006-02-18 14:35:02 |
[ FULL ]
|
Hi,
Just writing down what we all know but just to get some written comments on it.
I hope the ICE implementation can be shared between SIP and Jabber Jingle.
If i understand it correctly to create a p2p session using ICE one needs a
- STUN server (with user authentication)
- STUN client (exists in Zap, not sure if it can authenticate)
- A mediastreamer that is aware that on the same port STUN and media
data can be received.
The part where the client sends the "candidates" to the other client
is Jabber/SIP specific. (?)
The negotiation of the codec that is being use it protocol specific too. (?)
Alex, you read the libjingle code. Could you conclude that it uses a
standard ICE implentation?
Do you think you can get inspiration from the code?
regards
Tom
|
Re: [zap-devel] ICE, Stun, Jingle
Alex Fritze <alex(at)croczilla.com> |
2006-02-19 22:47:41 |
[ FULL ]
|
Tom Germeau wrote:
[...]
Yes, in a way this is the easy part. The complicated part is
implementing the ICE state machines and signalling flow
(gathering/selecting/validating candidates).
See also draft-ietf-mmusic-ice-06.txt
(http://www.croczilla.com/zap/rfcs/draft-ietf-mmusic-ice-06.txt)
for the
latest ICE draft.
[...]
ICE is designed for use with SDP (RFC3264 specifically). I'm not sure
how it maps onto jabber. I'm assuming jabber keeps the overall ICE logic
and maps it into jabber-specific signalling somehow?
[...]
Yeah, but this falls outside of the scope of ICE. In SIP codecs are
negotiated using RFC3264.
[...]
I haven't really read enough of it to find any code that I could connect
to ICE.
Regards,
Alex
[...]
|
|
|