Verto communicator client not working on Edge when we use our freeswitch server
Dear members, . We can use the verto communicator client to join a conference handled by our own Freeswitch server and using the default 'stun:stun.l.google.com:19302' Google STUN server. . It works on Chrome, Firefox and Opera, on which we can connect ok and get audio+video. . But it does NOT work on Edge. . When using Chrome we can see one of the ICE Candidates DOES have the client public IP. . But when running the client on Edge we do NOT see such candidate. . What it is interesting is that if we don't use our Freeswitch server but the one hosted in cantina.freeswitch.org then the verto client CAN connect ok and we get audio+video (although we noticed that even in this case we still not see the ICE Candidate with the client public IP in the SDP offer). . So my question is if the Freewitch server in cantina.freeswitch.org is doing something "special" to retrieve the client public IP from the signaling messages or something like that. . By the way, we already set the following params in the verto conf: <param name="apply-candidate-acl" value="localnet.auto"/> <param name="apply-candidate-acl" value="wan_v4.auto"/> <param name="apply-candidate-acl" value="rfc1918.auto"/> <param name="apply-candidate-acl" value="any_v4.auto"/> If you can give us any hints it would be much appreciated. Regards, Alex
You need to use turn with edge. They didn't implement stun. Or wait for edge to become Chrome since that is their plan. On Mon, Dec 17, 2018 at 3:30 PM Alejandro Castera < Alejandro.Castera@on24.com> wrote:
Dear members, . We can use the verto communicator client to join a conference handled by our own Freeswitch server and using the default 'stun: stun.l.google.com:19302' Google STUN server. . It works on Chrome, Firefox and Opera, on which we can connect ok and get audio+video. . But it does NOT work on Edge. . When using Chrome we can see one of the ICE Candidates DOES have the client public IP. . But when running the client on Edge we do NOT see such candidate. . What it is interesting is that if we don't use our Freeswitch server but the one hosted in cantina.freeswitch.org then the verto client CAN connect ok and we get audio+video (although we noticed that even in this case we still not see the ICE Candidate with the client public IP in the SDP offer). . So my question is if the Freewitch server in cantina.freeswitch.org is doing something "special" to retrieve the client public IP from the signaling messages or something like that. . By the way, we already set the following params in the verto conf:
<param name="apply-candidate-acl" value="localnet.auto"/> <param name="apply-candidate-acl" value="wan_v4.auto"/> <param name="apply-candidate-acl" value="rfc1918.auto"/> <param name="apply-candidate-acl" value="any_v4.auto"/>
If you can give us any hints it would be much appreciated. Regards, Alex _________________________________________________________________________ Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com
Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com
FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev https://freeswitch.com
-- Anthony Minessale II Founder, FreeSWITCH. http://freeswitch.com https://youtu.be/l_hOxzCt6X4 https://www.youtube.com/watch?v=oAxXgyx5jUw https://www.youtube.com/watch?v=9XXgW34t40s https://www.youtube.com/watch?v=NLaDpGQuZDA
Thanks for your comments. The thing is that the SAME client (which only uses Google STUN server) WORKS on Edge when connecting to the Freeswitch server hosted in cantina.freeswitch.org ... and does NOT work when connecting to our own Freeswitch server. So how come it is working on cantina.freeswitch.org ?? No turn server is being used by the peer connection object, but it still works! Any ideas? ------ Original Message ------ From: "Anthony Minessale" <anthony.minessale@gmail.com<mailto:anthony.minessale@gmail.com>> To: "freeswitch-dev@lists.freeswitch.org" <freeswitch-dev@lists.freeswitch.org<mailto:freeswitch-dev@lists.freeswitch.org>> Sent: 17-Dec-18 5:01:57 PM Subject: Re: [Freeswitch-dev] Verto communicator client not working on Edge when we use our freeswitch server You need to use turn with edge. They didn't implement stun. Or wait for edge to become Chrome since that is their plan. On Mon, Dec 17, 2018 at 3:30 PM Alejandro Castera <Alejandro.Castera@on24.com<mailto:Alejandro.Castera@on24.com>> wrote: Dear members, . We can use the verto communicator client to join a conference handled by our own Freeswitch server and using the default 'stun:stun.l.google.com:19302<http://stun.l.google.com:19302>' Google STUN server. . It works on Chrome, Firefox and Opera, on which we can connect ok and get audio+video. . But it does NOT work on Edge. . When using Chrome we can see one of the ICE Candidates DOES have the client public IP. . But when running the client on Edge we do NOT see such candidate. . What it is interesting is that if we don't use our Freeswitch server but the one hosted in cantina.freeswitch.org<http://cantina.freeswitch.org> then the verto client CAN connect ok and we get audio+video (although we noticed that even in this case we still not see the ICE Candidate with the client public IP in the SDP offer). . So my question is if the Freewitch server in cantina.freeswitch.org<http://cantina.freeswitch.org> is doing something "special" to retrieve the client public IP from the signaling messages or something like that. . By the way, we already set the following params in the verto conf: <param name="apply-candidate-acl" value="localnet.auto"/> <param name="apply-candidate-acl" value="wan_v4.auto"/> <param name="apply-candidate-acl" value="rfc1918.auto"/> <param name="apply-candidate-acl" value="any_v4.auto"/> If you can give us any hints it would be much appreciated. Regards, Alex _________________________________________________________________________ Professional FreeSWITCH Services sales@freeswitch.com<mailto:sales@freeswitch.com> https://freeswitch.com Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org<mailto:FreeSWITCH-dev@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev https://freeswitch.com -- Anthony Minessale II Founder, FreeSWITCH. http://freeswitch.com https://youtu.be/l_hOxzCt6X4 https://www.youtube.com/watch?v=oAxXgyx5jUw https://www.youtube.com/watch?v=9XXgW34t40s https://www.youtube.com/watch?v=NLaDpGQuZDA
Hello all, The candidates Edge provides are the following: candidate:1 1 UDP 2130706431 192.168.0.7 63832 typ host candidate:2 1 TCP 1684798975 192.168.0.7 63832 typ srflx raddr 192.168.0.7 rport 63832 tcptype active So for for every local IP, Edge generates 2 candidates: 1 host candidate, and 1 srflx candidate. The srvflx candidate is built wrong on purpose (transport address == related address). I guess they do that so that when the ICE connection checks take place, the server side can "learn" a new prflx candidate (see RFC5245, section 7.2.1.3) I have tested the same scenario using a server which makes use of the libnice library for the ICE implementation, and it works!!! No TURN server is being used, no STUN server is being used, the candidates Edge sends are the 2 above (which do not contain a public IP) and still the server generates a prflx candidate and the connection is established perfectly. But when using our Freeswitch server (which does not make use of the libnice library for ICE) the connection does not work. Then again, the funny thing is that if we use the cantina.freeswitch.org Freeswitch server, then it DOES work! So there must be something in the code/configuration that could be done so that the Freeswitch server can "learn" a prflx candidate from those Edge is sending out. Could anyone help us? Alex ------ Original Message ------ From: "Alejandro Castera" <Alejandro.Castera@on24.com<mailto:Alejandro.Castera@on24.com>> To: "freeswitch-dev@lists.freeswitch.org" <freeswitch-dev@lists.freeswitch.org<mailto:freeswitch-dev@lists.freeswitch.org>>; "freeswitch-dev@lists.freeswitch.org" <freeswitch-dev@lists.freeswitch.org<mailto:freeswitch-dev@lists.freeswitch.org>> Sent: 17-Dec-18 6:41:59 PM Subject: Re: [Freeswitch-dev] Verto communicator client not working on Edge when we use our freeswitch server Thanks for your comments. The thing is that the SAME client (which only uses Google STUN server) WORKS on Edge when connecting to the Freeswitch server hosted in cantina.freeswitch.org ... and does NOT work when connecting to our own Freeswitch server. So how come it is working on cantina.freeswitch.org ?? No turn server is being used by the peer connection object, but it still works! Any ideas? ------ Original Message ------ From: "Anthony Minessale" <anthony.minessale@gmail.com<mailto:anthony.minessale@gmail.com>> To: "freeswitch-dev@lists.freeswitch.org<mailto:freeswitch-dev@lists.freeswitch.org>" <freeswitch-dev@lists.freeswitch.org<mailto:freeswitch-dev@lists.freeswitch.org>> Sent: 17-Dec-18 5:01:57 PM Subject: Re: [Freeswitch-dev] Verto communicator client not working on Edge when we use our freeswitch server You need to use turn with edge. They didn't implement stun. Or wait for edge to become Chrome since that is their plan. On Mon, Dec 17, 2018 at 3:30 PM Alejandro Castera <Alejandro.Castera@on24.com<mailto:Alejandro.Castera@on24.com>> wrote: Dear members, . We can use the verto communicator client to join a conference handled by our own Freeswitch server and using the default 'stun:stun.l.google.com:19302<http://stun.l.google.com:19302>' Google STUN server. . It works on Chrome, Firefox and Opera, on which we can connect ok and get audio+video. . But it does NOT work on Edge. . When using Chrome we can see one of the ICE Candidates DOES have the client public IP. . But when running the client on Edge we do NOT see such candidate. . What it is interesting is that if we don't use our Freeswitch server but the one hosted in cantina.freeswitch.org<http://cantina.freeswitch.org> then the verto client CAN connect ok and we get audio+video (although we noticed that even in this case we still not see the ICE Candidate with the client public IP in the SDP offer). . So my question is if the Freewitch server in cantina.freeswitch.org<http://cantina.freeswitch.org> is doing something "special" to retrieve the client public IP from the signaling messages or something like that. . By the way, we already set the following params in the verto conf: <param name="apply-candidate-acl" value="localnet.auto"/> <param name="apply-candidate-acl" value="wan_v4.auto"/> <param name="apply-candidate-acl" value="rfc1918.auto"/> <param name="apply-candidate-acl" value="any_v4.auto"/> If you can give us any hints it would be much appreciated. Regards, Alex _________________________________________________________________________ Professional FreeSWITCH Services sales@freeswitch.com<mailto:sales@freeswitch.com> https://freeswitch.com Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org<mailto:FreeSWITCH-dev@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev https://freeswitch.com -- Anthony Minessale II Founder, FreeSWITCH. http://freeswitch.com https://youtu.be/l_hOxzCt6X4 https://www.youtube.com/watch?v=oAxXgyx5jUw https://www.youtube.com/watch?v=9XXgW34t40s https://www.youtube.com/watch?v=NLaDpGQuZDA
participants (2)
-
Alejandro Castera
-
Anthony Minessale