WEBRTC Cannot make calls without Internet

[Jayant Dhole]

Hello guys,

I have been stuck here for a while now.

I have a VOIP call system With WEBRTC UI which runs from google chrome.

I am using Freeswitch in the Backend and SIPML5 in my Webrtc.

Now My calling system Works fine When there is internet connection available as it goes through ICE servers.

I want my system to run without internet and my whole system is running on a local network without any NAT or something.

Whenever i disable my ICE servers (by setting ICE servers [] empty array). It gives arror INCOMPATIBLE DESTINATION.

I have attached google chrome console log file below.

Any kind of help will be appreciated, Thanks.

[davidsw...@gmail.com]

"Incompatible destination" is an error specific to Freeswitch (FS). Look in your browser console for the 'host' candidates in the SDP offer sent to FS. It's likely that FS can't reach the IP number or port offered.

[Jayant Dhole]

Hello David,

I have uploaded the console logs and yes it is not able to reach the server ip. 

But then why is it able to successfully establish calls when there is internet connection and ICE servers are enabled.

Please advise and if you have any way to solve this issue please let me know.

Thank you

On Mon, Mar 25, 2019, 2:10 AM <davidsw...@gmail.com> wrote:

This message is eligible for Automatic Cleanup! (davidsw...@gmail.com) Add cleanup rule | More info

"Incompatible destination" is an error specific to Freeswitch (FS). Look in your browser console for the 'host' candidates in the SDP offer sent to FS. It's likely that FS can't reach the IP number or port offered.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/55d67bbe-ba07-4e13-99bd-f2ce6bcaaa9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[davidsw...@gmail.com]

You've mentioned that calling works only when you use a STUN or TURN. When you use TURN, you should note the 'relay' candidate that appears in your browser console or FS log; note the port it's using. Then you might try STUN without TURN; if it works, note the IP number of the 'srflx' candidate; this is the public-facing IP of your FS. When you try without STUN or TURN, note the 'host' IP number. I suspect this is an IP number that's not reachable by your browser. Is that because the browser is in the wrong network, or because FS needs to be configured with its public-facing IP (look for 'ext-rtp-ip')?

[Jayant Dhole]

Hi david,

As you told , i checked the logs With and Without stun server. There is not much difference except while gathering Candidates. the stun 'srflx' ip you told about gives the IP address of webrtc client. And the IN IP is some STUN ip. 

Whereas in Without Stun, NO host ip comes as such. I have uploaded the logs for both ICE and Without_ICE call logs. If you find anything please do let me know.

I also assigned the (ext-rtp-ip )to my freeswitch server ip but it didn't solve the problem. Are you sure the problem is in Freeswitch, As i am working on local network therefore is there a need to set external-ip ?and when i try calling from 2 softphones , the call is perfect. the problem arises only when i  am using my webrtc client.

If there is any other Configuration needed, please do let me know.

plus i would like to add that i am using a Centos PC. With apache server attached to it. and freeswitch installed in it. The Webrtc client is also in that server.

And i access the UI from other PC from same network to make calls to other cells.

Thank you for you time.

[David P]

Hi Jayant,

Overall, I'm suggesting that you double-check that the machine where you're using webrtc is in the same IP-addressing space as your Freeswitch server; the fact that webrtc calls only work when you use TURN or STUN implies that they aren't.

When I try my own webrtc page with our FS, the browser console SDP line (in a section starting "Dialog [...] ANSWER SDP") of this format,

o=FreeSWITCH someNumber someNumber IN IP4 publicIpNumberOfFS

reveals the IP number under which my FS can be reached. If you were running FS on a cloud machine, that IP-number would usually not be reachable by any browser until you told FS via ext-rtp-ip what its "public" IP-number is, which is the cloud machine's public IP (if it has one). Then that ext-rtp-ip value would appear in your browser after "IN IP4".

It might also be that the machine where your browser is running is in a non-public IP-addressing space, and that would explain why a STUN server is making those calls possible. In my browser console, in a section starting "RECV offer SDP v=0", there are lines with "typ relay raddr IpOfMyBrowserMachineAppearsHere". You might check that your browser machine and your FS machine can ping each other's addresses that were revealed in these lines.

You might want to join the Freeswitch users mailing list via http://lists.freeswitch.org/mailman/listinfo to ask more, if you isolate the problem to FS.

[Jayant Dhole]

Hi David,

Yes my FS and Webrtc is in same IP-addressing space. They both are pingable with each other. I read online that it moght be a problem regarding Openssl, If you know what to do, please do let me. And thanks for the Freeswitch link, i will definately check it out