Re: [Freeswitch-users] verto, private ip, stun, and Chrome
Well, we found out commenting out the ACLs in the verto.conf.xml worked: <!-- <param name="apply-candidate-acl" value="localnet.auto"/> <param name="apply-candidate-acl" value="rfc1918.auto"/> <param name="apply-candidate-acl" value="any_v4.auto"/> --> Seems the client's private IP was one from our LAN, so FreeSWITCH thought it was a valid request from our LAN. But I wonder if STUN should have fixed this? Robert Mundkowsky From: Mundkowsky, Robert Sent: Thursday, January 11, 2018 5:25 PM To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Subject: verto, private ip, stun, and Chrome Hi, We are using a Verto javascript that is maybe a little out of date and most recent version of Chrome. We are seeing that client's private IP address is being sent to FreeSWITCH rather than client's public IP. We have "iceServers: true" which should tell verto to use the default google STUN server. I am guessing the below code that uses "navigator.mozGetUserMedia" likely is causing the problems since getusermedia has been tweaked a lot by Chrome and Firefox (per https://developer.mozilla.org/en-US/docs/Web/API/Navigator/getUserMedia ). window.moz = !!navigator.mozGetUserMedia; function RTCPeerConnection(options) { var gathering = false, done = false; var w = window, PeerConnection = w.mozRTCPeerConnection || w.webkitRTCPeerConnection, SessionDescription = w.mozRTCSessionDescription || w.RTCSessionDescription, IceCandidate = w.mozRTCIceCandidate || w.RTCIceCandidate; var STUN = { url: !moz ? 'stun:stun.l.google.com:19302' : 'stun:23.21.150.121' }; robert ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
participants (1)
-
Mundkowsky, Robert