search

signalwire / freeswitch

FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a versatile software implementation that runs on any commodity hardware. From a Raspberry PI to a multi-core server, FreeSWITCH can unlock the telecommunications potential of any device.
https://freeswitch.com/#getting-started
Other
3.6k stars 1.42k forks source link

Webrtc client having RTP issues with freeswitch on docker #892

Open erezl opened 4 years ago

erezl commented 4 years ago

Hi I having problem with my webRTC client, when dialing out (sending call request to FS) 5 out 10 times, the audio is not working (not hearing the ringback tone) I am using FS version 1.10.5 I have no idea what the problem is Best regards Erez lavie

josefig commented 4 years ago

Hello,

You have any logs about this? it happened to me once.

On Tue, Oct 6, 2020 at 10:02 AM erezl notifications@github.com wrote:

Hi I having problem with my webRTC client, when dialing out (sending call request to FS) 5 out 10 times, the audio is not working (not hearing the ringback tone) I am using FS version 1.10.5 I have no idea what the problem is Best regards Erez lavie

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/signalwire/freeswitch/issues/892, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEUBO7U4ABJD6YE3HO6RETSJMWSHANCNFSM4SGEXBSQ .

tinpotnick commented 4 years ago

I run FS in docker. How are you configuring networking? If you are giving FS a private network, then you will have to configure all the relevant NAT options. I run FS on the host network te lessen any issues related to NAT.

erezl commented 4 years ago

Hi In my case, I am running multiple FS containers on the same docker host (each one listening to a different wss port), and using iptables to direct RTP ports (500 ports...) to each FS container. I don't have any problems with IP phones (works like a charm), but with webRTC clients, it's work sometimes (about 50%). The question is, is there any special network settings on the docker host level, for this to work ? Best regards Erez lavie

tinpotnick commented 4 years ago

There are not special settings for this.

NAT will have to be taken care of though. SIP from UDP and via WSS will have differences - so you may have something fixing UDP but not WSS. If you are using iptables to NAT then ensure you set the public facing IP of FS.

You can certainly test this by running the FS container in a host networking mode and if this fixes it (which I bet it does) then you know you have a NAT issue.

On Thu, Oct 8, 2020 at 11:39 AM erezl notifications@github.com wrote:

Hi In my case, I am running multiple FS containers on the same docker host (each one listening to a different wss port), and using iptables to direct RTP ports (500 ports...) to each FS container. I don't have any problems with IP phones (works like a charm), but with webRTC clients, it's work sometimes (about 50%). The question is, is there any special network settings on the docker host level, for this to work ? Best regards Erez lavie

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/signalwire/freeswitch/issues/892#issuecomment-705485255, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABBM4NSPHC4QPN7FVQZJDXLSJWJEZANCNFSM4SGEXBSQ .

themsley-voiceflex commented 11 months ago

This can probably be closed, duplicate of #2283