[Spce-user] WebRTC <-> RTP: No audio on public host, works fine on local vagrant VM

[Manu Raghavan]

You saved the day again. That did it!

Quick confirmation: I went ahead and edited the raw network.yml to reflect my public, Elastic IP. I hope it this file is not the output of a template, and this edit won’t be rewritten later by template generation. Is this right?


On Saturday, March 21, 2015 at 4:27 AM, Richard Fuchs wrote:

> On 20/03/15 03:48 PM, Manu Raghavan wrote:
>  
> > When running Sipwise CE mr3.7.2 from your vagrant box locally (both
> > peers and the server running on the same dev host), calls work fine with
> > this setup. But, when I try this same setup when running mr3.7.2 using
> > your AWS image, calls establish successful signaling, but the audio is
> > completely blank once the call starts out.
> >  
>  
>  
> Amazon hosts generally are behind NAT, so you need to use the
> "advertised address" feature correctly to make things work. For example
> using ngcp-network, you would set --ip= to the local (private) address,
> but --advertised-ip= to the public NAT address. Post your network.yml
> together with details about your network setup if you're unsure about
> how to config it.
>  
> Cheers
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com (mailto:Spce-user at lists.sipwise.com)
> https://lists.sipwise.com/listinfo/spce-user
>  
>  


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20150321/09aa1be3/attachment-0001.html>