[libnice] sometimes connectivity checks fail...
philip at tecnocode.co.uk
Mon Jan 4 14:05:10 PST 2016
Can you please provide a debug log from libnice for this? It’s hard to
work out what the problem is otherwise.
Does the component state change to NICE_COMPONENT_STATE_FAILED? If you
wait, does it later change to NICE_COMPONENT_STATE_READY or
*_CONNECTED? What are you waiting for to know when the connection is
What version of libnice is this with? 0.1.13, or master? Can you try
On Thu, 2015-12-24 at 21:40 +0800, Jack Wang wrote:
> I also test by using the random ports , which is used originally in
> and found it also fails sometimes,
> however, it still can work in some later calls.
> Keep tracking and testing....:P
> 2015-12-24 21:20 GMT+08:00 Jack Wang <antirazin at gmail.com>:
> > Hi, everyone
> > For several media channels (ex: audio,video etc.),
> > I create ICE agents for each of them,
> > and each channel I used a fixed port which is a fixed RTP port.
> > Then after I did a SIP call to exchange the ICE SDP with the
> > callee,
> > I found the one who sent the offer often failed on negotiation on
> > some channels (not the same ones every time),
> > while the answer one is always OK.
> > And if failed on the first time, it will always fail in the
> > following calls.
> > The Offer one is behind a symmetric NAT, and the Answer one is on
> > WAN.
> > I trace the log and found the failed(for negotiation) ones always
> > discover the prflx candidate very late, and cannot be READY state
> > in the end.
> > I cannot figure out why this happens,
> > does it is related to the NAT policy for port forwarding??
> > Thanks in advance :)
> nice mailing list
> nice at lists.freedesktop.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 213 bytes
Desc: This is a digitally signed message part
More information about the nice