<html><head></head><body><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div>Update. I just checked inbound calls using the "rtpproxy clean" cfg. </div><div><br></div><div>Inbound calls from Carrier to UA work fine with bidirectional RTP. Its the outbound calls from UA to carrier that have a NAT issue.</div><div><br></div><div>I am so close :).... </div><div><br></div><div>KD</div><div><br></div>
<div id="yahoo_quoted_6625857899" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Wednesday, May 9, 2018, 4:29:39 PM EDT, KamDev Essa <kamdevessa@yahoo.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="yiv1406844704"><div><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div>That did not help. sip capture shows NATed SDP being sent to carrier. Obviously carrier will not be able to make head nor tails about it. And carrier SDP sent to UA is perfect as its not NATed. So UA ===> Carrier is fine. Carrier ====> UA is no RTP. Does not look like Kam alone can do RTP relase between NATed UA and the outside network entity. </div><div><br clear="none"></div><div>I will try Freeswitch piggy back and then let Freeswitch bypass media. Logic in Freeswitch may do the trick. \</div><div><br clear="none"></div><div>KD </div><div><br clear="none"></div>
<div class="yiv1406844704yqt1054802789" id="yiv1406844704yqt84850"><div class="yiv1406844704yahoo_quoted" id="yiv1406844704yahoo_quoted_6674138910">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Wednesday, May 9, 2018, 3:30:26 PM EDT, Alex Balashov <abalashov@evaristesys.com> wrote:
</div>
<div><br clear="none"></div>
<div><br clear="none"></div>
<div><div dir="ltr">You'll want to not load the rtpproxy module, and lose any rtpproxy_*() calls in the actual script. <br clear="none"><br clear="none">On May 9, 2018 3:26:43 PM EDT, KamDev Essa <<a rel="nofollow" shape="rect" ymailto="mailto:kamdevessa@yahoo.com" target="_blank" href="mailto:kamdevessa@yahoo.com">kamdevessa@yahoo.com</a>> wrote:<br clear="none">>If I comment out the modparam("rtpproxy", "rtpproxy_sock",<br clear="none">>"udp:127.0.0.1:7722") as suggested, I do get RTP flowing just in one<br clear="none">>direction. From the UA to kam and out to the carrier. I get nothing<br clear="none">>geting back to the end point. In other words 1 way RTP. Looks like its<br clear="none">>Kam RTPProxy or bust.<br clear="none">>KD<br clear="none">>On Wednesday, May 9, 2018, 2:38:08 PM EDT, Alex Balashov<br clear="none">><<a rel="nofollow" shape="rect" ymailto="mailto:abalashov@evaristesys.com" target="_blank" href="mailto:abalashov@evaristesys.com">abalashov@evaristesys.com</a>> wrote: <br clear="none">> <br clear="none">>Correct. So remove all semblance of any RTP proxy and the resulting<br clear="none">>behaviour will be exactly what you expect. <br clear="none">><br clear="none">>On May 9, 2018 2:13:22 PM EDT, KamDev Essa <<a rel="nofollow" shape="rect" ymailto="mailto:kamdevessa@yahoo.com" target="_blank" href="mailto:kamdevessa@yahoo.com">kamdevessa@yahoo.com</a>><br clear="none">>wrote:<br clear="none">>>I dont. I want the 2 end points to talk to each other because I am on<br clear="none">>>AWS with shaky bandwidth stats. It can handle signalingbut not RTP. <br clear="none">>>However the cfg entry modparam("rtpproxy", "rtpproxy_sock",<br clear="none">>>"udp:127.0.0.1:7722") gives me to believe (not tcdumped RTP ports yet<br clear="none">>>to prove it ) that Kam anchors RTP @ port 7722. <br clear="none">>>KD <br clear="none">>>On Wednesday, May 9, 2018, 2:02:14 PM EDT, Alex Balashov<br clear="none">>><<a rel="nofollow" shape="rect" ymailto="mailto:abalashov@evaristesys.com" target="_blank" href="mailto:abalashov@evaristesys.com">abalashov@evaristesys.com</a>> wrote: <br clear="none">>> <br clear="none">>>That depends. Start with a more basic question: why do you need RTP<br clear="none">>>relay in the middle at all? <br clear="none">>><br clear="none">>>On May 9, 2018 1:54:55 PM EDT, KamDev Essa <<a rel="nofollow" shape="rect" ymailto="mailto:kamdevessa@yahoo.com" target="_blank" href="mailto:kamdevessa@yahoo.com">kamdevessa@yahoo.com</a>><br clear="none">>>wrote:<br clear="none">>>>So all calls that kamailio processes using the default cfg file<br clear="none">>anchor<br clear="none">>>>RTP on the kamailio server? Is it a best architecture to farm out RTP<br clear="none">>>>to Freeswitch? Or is the Kamailio RTP proxy a better gig?<br clear="none">>>>KD<br clear="none">>>>On Wednesday, May 9, 2018, 1:38:04 PM EDT, Alex Balashov<br clear="none">>>><<a rel="nofollow" shape="rect" ymailto="mailto:abalashov@evaristesys.com" target="_blank" href="mailto:abalashov@evaristesys.com">abalashov@evaristesys.com</a>> wrote: <br clear="none">>>> <br clear="none">>>>Ironically, nothing. Kamailio doesn't touch the respective parties'<br clear="none">>>SDP<br clear="none">>>>unless you invoke an RTP relay (or something else like<br clear="none">>>>fix_nated_sdp()). <br clear="none">>>><br clear="none">>>>On May 9, 2018 1:03:19 PM EDT, KamDev Essa <<a rel="nofollow" shape="rect" ymailto="mailto:kamdevessa@yahoo.com" target="_blank" href="mailto:kamdevessa@yahoo.com">kamdevessa@yahoo.com</a>><br clear="none">>>>wrote:<br clear="none">>>>>What cfg files changes do I need to make to get Kamailio to be a<br clear="none">>>>>signally only server, yet manipulate the SDP part of the INVITE<br clear="none">>>>message<br clear="none">>>>>to allow remote parties to send media to each other? In Freeswitch<br clear="none">>>>>terms "bypassmedia".<br clear="none">>>>>KD<br clear="none">>>><br clear="none">>>><br clear="none">>>>-- Alex<br clear="none">>>><br clear="none">>>>--<br clear="none">>>>Sent via mobile, please forgive typos and brevity. <br clear="none">>>><br clear="none">>>>_______________________________________________<br clear="none">>>>Kamailio (SER) - Users Mailing List<br clear="none">>>><a rel="nofollow" shape="rect" ymailto="mailto:sr-users@lists.kamailio.org" target="_blank" href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a><br clear="none">>>><a rel="nofollow" shape="rect" target="_blank" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br clear="none">>>> <br clear="none">>><br clear="none">>><br clear="none">>>-- Alex<br clear="none">>><br clear="none">>>--<br clear="none">>>Sent via mobile, please forgive typos and brevity. <br clear="none">><br clear="none">><br clear="none">>-- Alex<br clear="none">><br clear="none">>--<br clear="none">>Sent via mobile, please forgive typos and brevity. <div class="yiv1406844704yqt1698565869" id="yiv1406844704yqtfd86902"><br clear="none"><br clear="none"><br clear="none">-- Alex<br clear="none"><br clear="none">--<br clear="none">Sent via mobile, please forgive typos and brevity. <br clear="none"><br clear="none">_______________________________________________<br clear="none">Kamailio (SER) - Users Mailing List<br clear="none"><a rel="nofollow" shape="rect" ymailto="mailto:sr-users@lists.kamailio.org" target="_blank" href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a><br clear="none"><a rel="nofollow" shape="rect" target="_blank" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br clear="none"></div></div></div>
</div>
</div></div></div></div></div></div>
</div>
</div></div></body></html>