[Nice] minimal example

Eduardo Bezerra kdubezerra at gmail.com
Fri Jan 13 12:36:59 PST 2012

Yes, I guess I'll need some 3rd guy in the middle to allow the two peers to
connect to each other (and then, hopefully, communicate directly). But how
to you go from a NiceCandidate struct of a peer (which contains several
other structs and unions) to, say, a string? Such string could be sent to
the 3rd-party and forwarded to the other peer, which would parse it and
recreate the NiceCandidate struct, for each received remote candidate...
The thing is that I want different platforms to communicate, so there
should be some "protocol" to send the candidates info...

On Fri, Jan 13, 2012 at 8:49 PM, Youness Alaoui <
youness.alaoui at collabora.co.uk> wrote:

> Hi,
> Thanks Tiago for taking over while I was asleep! Nice to see all this
> activity
> and to have Eduardo's tests successful! :)
> Having a nat friendly retwork as one of the peers guarantees success, if
> you
> have two nat-hostile networks, then it depends on the type of NATs
> involved, if
> both are symmetric NATs, then it will fail, if at least one of them is not
> a
> symmetric NAT, then it should succeed (c.f.
> http://en.wikipedia.org/wiki/Network_address_translation#Methods_of_Port_translation
> )
> libnice does not provide any serialization method, you will still always
> need a
> third party server to do the candidate exchange and that will depend on the
> protocol used by this server, could be XMPP, could be SIP, could be
> custom, it
> really all depends on what your needs are and what the server
> supports/accepts.
> Youness.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/nice/attachments/20120113/c3d2534c/attachment.htm>

More information about the Nice mailing list