Implications of not enabling STUN's CHANGE-REQUEST

44 views
Skip to first unread message

KNC

unread,
Apr 13, 2015, 11:43:48 AM4/13/15
to turn-server-project...@googlegroups.com
Hi all,

From the docs, I see that supporting STUN's change-request requires 2 IP addresses that are both public (i.e. NOT behind a NAT, like in the case of EC2). If I'm building a WebRTC application and looking to support enterprise users who are often behind restrictive firewalls, what are the implications of not supporting the change-request feature? According to this post, there are no drawbacks - can someone please confirm that?

Thanks,

KN.
Reply all
Reply to author
Forward
0 new messages