Running on port 443, pros and cons...
Hi, Are anyone running FS on port 443 for making such service more available on public WiFis and such?
Some networks have fw with depth inspection enabled. That may stop you. Port 443/TCP. Same if you use port 53/UDP. However, I have found that using DNS port of mine reliable, because many vendors don't filter it. Le 27 oct. 2015 10:44 AM, "Michael Nielsen" <mic.niel84@gmail.com> a écrit :
Hi,
Are anyone running FS on port 443 for making such service more available on public WiFis and such?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Are anyone running FS on port 443 for making such service more available on public WiFis and such?
Configure a VPN on your FS server and make it listen on port 443 and register to FS over the VPN. Using a VPN in case of public wifi networks is a win anyway. Bonus: the ISP can't see the voip traffic. -- EL
Greets! If we talking about sip it useless. Because it will work only for sip TCP or sip TLS . It would not work if proxy in the middle. Don't forget about rtp ports. On Oct 28, 2015 12:34 AM, "EL" <fs.user@fordior.net> wrote:
Are anyone running FS on port 443 for making such service more available on public WiFis and such?
Configure a VPN on your FS server and make it listen on port 443 and register to FS over the VPN. Using a VPN in case of public wifi networks is a win anyway. Bonus: the ISP can't see the voip traffic.
-- EL
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
I'm running sip with TLS and Srtp. But I guess you are right with the rtp ports :( On Wednesday, October 28, 2015, Volodymyr Fedorov <lexxua@gmail.com> wrote:
Greets! If we talking about sip it useless. Because it will work only for sip TCP or sip TLS . It would not work if proxy in the middle. Don't forget about rtp ports. On Oct 28, 2015 12:34 AM, "EL" <fs.user@fordior.net <javascript:_e(%7B%7D,'cvml','fs.user@fordior.net');>> wrote:
Are anyone running FS on port 443 for making such service more available on public WiFis and such?
Configure a VPN on your FS server and make it listen on port 443 and register to FS over the VPN. Using a VPN in case of public wifi networks is a win anyway. Bonus: the ISP can't see the voip traffic.
-- EL
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','FreeSWITCH-users@lists.freeswitch.org');> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
If we talking about sip it useless. Because it will work only for sip TCP or sip TLS . It would not work if proxy in the middle. Don't forget about rtp ports.
Adapt conf/sip_profiles/internal.xml (or make a separate sip profile for the vpn) to listen on the VPN address. Config your sip client to listen on the tun interface with the relevant VPN ip. If the public wifi is only allowing egress 443 over tcp, adapt the vpn config to use tcp. You can even run two different vpn configurations at the same time (listening on different ports and protocols). -- EL
Actually unfortunately vpn is not so ideal solution. You have to support VPN-server, Certificates so on. And not all of types vpn can use only one tcp port that can be changed (I know that only OpenVPN can do this). And usage it on mobile clients gives another layer of problems. Interesting how WebRTC works behind proxy / nat with crazy firewall rules ? Someone in mailing list test it ? Thanks.
I think is bad idea to make call trough HTTP proxy. FS can work on any port if no man(proxy) in the middle. Try authenticate on HTTP proxy and scan what is TCP and UDP ports open communication. Then make decisions. On Wed, Oct 28, 2015 at 6:55 PM, Volodymyr Fedorov <lexxua@gmail.com> wrote:
Actually unfortunately vpn is not so ideal solution. You have to support VPN-server, Certificates so on. And not all of types vpn can use only one tcp port that can be changed (I know that only OpenVPN can do this). And usage it on mobile clients gives another layer of problems. Interesting how WebRTC works behind proxy / nat with crazy firewall rules ? Someone in mailing list test it ? Thanks.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (5)
-
EL
-
Luis Daniel Lucio Quiroz
-
Michael Nielsen
-
Sergey Safarov
-
Volodymyr Fedorov