<div dir="ltr">Thank you for your help - looks like it was indeed NAT related. Solved by adding direct_media=no to our endpoints and setting the transport to:<br><br>[simpletrans]<br>type=transport<br>protocol=udp<br>bind=0.0.0.0<br>local_net=<aws vpc cidr the ec2 instance is on><br><div>local_net=<a href="http://127.0.0.1/32">127.0.0.1/32</a><br>external_media_address=<public elastic ip of the ec2 instance><br>external_signaling_address=<public elastic ip of the ec2 instance></div><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 16, 2014 at 12:02 PM, Joshua Colp <span dir="ltr"><<a href="mailto:jcolp@digium.com" target="_blank">jcolp@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Nick Horelik wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks for your help. This is all running on amazon AWS so perhaps I do<br>
have NAT issues. However, if that's the case I don't get why media flows<br>
when I don't add 'dtmf_events' to the bridge type, and why it works when<br>
I do have that bridge type with both sides using the working trunk. Is<br>
it because asterisk detects different dtmf modes between the two outside<br>
endpoints and only then tries to have media flow through itself on our<br>
network?<br>
</blockquote>
<br></span>
I'd suggest taking ARI out of the equation for the moment and sending your calls to a simple Answer and then Playback. That will confirm one leg of your media path. After that I'd suggest using Dial() to call your outgoing leg and see what happens.<br>
<br>
As for why it works - I think what is happening is that Asterisk is using a mechanism to have both legs talk directly to eachother so media is not flowing through Asterisk. Since Flowroute has public IPs it's all good. You can disable this functionally by placing "direct_media=no" in your endpoints.<br>
<br>
If you disable direct media and you still get no media then it's most likely something network related. Personally I haven't touched AWS in *years* but I do know they do some interesting network stuff. It made be worthwhile to also post this to the asterisk-users mailing list which has much more people who have most likely run into exactly this.<div class="HOEnZb"><div class="h5"><br>
<br>
Cheers,<br>
<br>
-- <br>
Joshua Colp<br>
Digium, Inc. | Senior Software Developer<br>
445 Jan Davis Drive NW - Huntsville, AL 35806 - US<br>
Check us out at: <a href="http://www.digium.com" target="_blank">www.digium.com</a> & <a href="http://www.asterisk.org" target="_blank">www.asterisk.org</a><br>
<br>
______________________________<u></u>_________________<br>
asterisk-app-dev mailing list<br>
<a href="mailto:asterisk-app-dev@lists.digium.com" target="_blank">asterisk-app-dev@lists.digium.<u></u>com</a><br>
<a href="http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev" target="_blank">http://lists.digium.com/cgi-<u></u>bin/mailman/listinfo/asterisk-<u></u>app-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>774.208.2168
</div></div>