<div style="font-family: Helvetica; font-size: 13px;">You saved the day again. That did it!<div><br></div><div>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?</div><div><div><br></div></div></div>
<div></div>
<p style="color: #A0A0A8;">On Saturday, March 21, 2015 at 4:27 AM, Richard Fuchs wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>On 20/03/15 03:48 PM, Manu Raghavan wrote:</div><div><br></div><blockquote type="cite"><div><div>When running Sipwise CE mr3.7.2 from your vagrant box locally (both</div><div>peers and the server running on the same dev host), calls work fine with</div><div>this setup. But, when I try this same setup when running mr3.7.2 using</div><div>your AWS image, calls establish successful signaling, but the audio is</div><div>completely blank once the call starts out.</div></div></blockquote><div><br></div><div>Amazon hosts generally are behind NAT, so you need to use the</div><div>"advertised address" feature correctly to make things work. For example</div><div>using ngcp-network, you would set --ip= to the local (private) address,</div><div>but --advertised-ip= to the public NAT address. Post your network.yml</div><div>together with details about your network setup if you're unsure about</div><div>how to config it.</div><div><br></div><div>Cheers</div><div>_______________________________________________</div><div>Spce-user mailing list</div><div><a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a></div><div><a href="https://lists.sipwise.com/listinfo/spce-user">https://lists.sipwise.com/listinfo/spce-user</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>