Hi,

Is it possible to configure the WebRTC Snap-in to only offer ICE candidates that use TCP for WebRTC and not UDP? Can the SBC be configured to only allow TCP packets for WebRTC traffic, and therefore any UDP packets can be discarded at the firewall?

We have some concerns at the moment over permitting UDP traffic from the internet into our call center, specifically in the case of UDP flood attacks.

Many Thanks.

Hi Amit.

Thanks for your reply.

Is it possible for Avaya to provide a version of the library that does not use jQuery?

From what I can see, the usage of jQuery from the WebRTC JavaScript Library is very minimal:

avayawebrtc-client.js

$.ajaxSetup (lines 23, 26)
$.getScript (line 24)
$.grep (lines 774, 1534, 2951, 2956)
$.support.cors (line 888 )
$.ajax (lines 889, 900, 968 )
$.isArray (line 987)
$.each (line 2570)

It should be fairly straightforward to replace these calls with the equivalent JavaScript code.

Having a dependency on an 83KB library just to call 7 functions seems excessive.

Thanks again,
Neil.

Hi.

I have some questions regarding the WebRTC JavaScript Library:

Is it possible to provide a version of the WebRTC JavaScript Library that does not depend on jQuery? As WebRTC is only available in newer browsers, the dependency on jQuery seems redundant.

If it is not possible to provide a version of the WebRTC JavaScript Library without the jQuery dependency, what would our support status be if we created our own version of the WebRTC JavaScript Library that was not dependent on jQuery?

Our website is high-volume and customer facing in a highly regulated industry, and any 3rd party dependency creates issues for us in terms of managing security updates, and also adding to page load times and download sizes. Hence we prefer to minimize 3rd party dependencies where at all possible.


Thanks for your assistance,

Neil.