Hi - I am trying to get webrtc running on AWS. I have used webrtc locally and works fine.
I have All the ports open on the AWS firewall. A linphone client works just fine with audio on the AWS server. I have added the external_media_address and external_signaling_address to pjsip.conf and set the local_net.
My setup for webrtc is: (I am using sipml5 as the client)
I have used webrtc “locally” for some time - without STUN or ICE in play. I am just trying to move the setup to AWS. We have all the certificates (LetsEncypt) on the server and for asterisk. A softphone works with AWS - but the webrtc I get nothing …. I would rather not use ICE or anything additional. Why/how can I take what works locally and get to work on AWS ?
You’ve used STUN and ICE, it is fundamental technology used by WebRTC. There is no “not using it”. The browser requires it, just like it requires DTLS-SRTP. Even local, it would have been used.
And to go into more detail. Locally it would have ICE candidates that are, well, local IP address and port. Each side would exchange, figure out that it works, and tada - you’ve got media flow. With Asterisk being remote then the best option to ensure that media flow occurs unhindered is to configure rtp.conf so it places the public IP address as an ICE candidate, and ensuring the RTP ports are forwarded.