<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Ben,<br>
<br>
Some NATs require symmetric RTP, so that source and destination
ports are the same for incoming and outgoing media streams. This
can be configured using the 'w' flag to rtpproxy_manage in the
NATDETECT route.<br>
<br>
<tt><span style="font-size: 15px; color: rgb(0, 0, 0);
background-color: transparent; font-weight: normal;
font-style: normal; font-variant: normal; text-decoration:
none; vertical-align: baseline;"
id="docs-internal-guid-2c327ed3-10d0-9599-654c-59e26e514c28">rtpproxy_manage("cow");</span></tt><br>
<br>
Regards,<br>
Hugh<br>
<br>
On 20/12/2013 16:13, Benjamin Trent wrote:<br>
</div>
<blockquote
cite="mid:CAAyovTU=pm0wKpbmZxfa9OMig4oXHFy6xMaAwgGQx2hBfKskQQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div style="font-family:arial,sans-serif;font-size:13px">Hey
all,</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br>
</div>
<div style="font-family:arial,sans-serif;font-size:13px">**I
apologize if this is a duplicate, I received a bounce back on
my first email.</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br>
</div>
<span style="font-family:arial,sans-serif;font-size:13px">I have
kamailio set up behind a nat(port restricted, with firewall
rules to allow sip transactions and allowing rtpproxy packet
handling if needed) on Amazon EC2. I can register and calls
complete, however, the Caller(the one initiating the
transaction) receives no rtp media feed. I am running with NAT
enabled on kamailio and have rtpproxy installed listening on
the public IP. Kamailio and the rtpproxy are communicating(I
have verified via the kamailio debug logs). If I make a call
between the exact same voip machines directly via local IP on
the same Nat(skipping kamailio), the calls complete and they
both receive feeds.</span><br
style="font-family:arial,sans-serif;font-size:13px">
<div style="font-family:arial,sans-serif;font-size:13px"><br>
</div>
<div style="font-family:arial,sans-serif;font-size:13px">Both
the Caller(party making the call) and the Callee(party
receiving the call) are behind a Port Restricted Nat.
<div>
This is a folder containing the debug output for one of
these calls and the kamailio.cfg settings</div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="https://drive.google.com/folderview?id=0B9Foq0jDF8gLRlVNc001bTUtbFE&usp=sharing"
target="_blank">https://drive.google.com/folderview?id=0B9Foq0jDF8gLRlVNc001bTUtbFE&usp=sharing</a><br>
</div>
<div><br>
</div>
<div>Quick FYI, the Caller Display Name and the Callee SIP
UserName are the same string. However, in my understanding
about sip, the display name means pretty much nothing and is
just a human readable string that does not effect packet
transport. If I am wrong and should test with a different
display name, let me know.</div>
<div><br>
</div>
<div><br>
</div>
<div>Thank you for the assistance,</div>
<div><br>
</div>
<div>ben</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Hugh Waite
Principal Design Engineer
Crocodile RCS Ltd.</pre>
</body>
</html>