<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN'>
<html><head><meta http-equiv="Content-Type" content="text/html;charset=us-ascii">
<style>BODY{font:10pt Tahoma, Verdana, sans-serif}</style></head><body>
<DIV>Brian,</DIV>
<DIV> </DIV>
<DIV>There are still some devices that are broken, and won't send RPORT. It sux...</DIV>
<DIV> </DIV>
<DIV>--Dave</DIV><BR>
<BLOCKQUOTE style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<HR>
<B>From:</B> Brian West [mailto:brian@freeswitch.org]<BR><B>To:</B> FreeSWITCH Users Help [mailto:freeswitch-users@lists.freeswitch.org]<BR><B>Sent:</B> Sat, 09 Jun 2012 11:42:43 -0700<BR><B>Subject:</B> Re: [Freeswitch-users] FreeSWITCH-users Digest, Vol 72, Issue 66<BR><BR>
<DIV>um this is the purpose of rport, enable it on the endpoint for pain relief.<BR><BR>Sent from my iPad</DIV>
<DIV><BR>On Jun 9, 2012, at 9:59 AM, BELint Inc <<A href="mailto:belintinc@gmail.com">belintinc@gmail.com</A>> wrote:<BR><BR></DIV>
<BLOCKQUOTE type="cite">
<DIV>Thanks Dave,</DIV>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<DIV>We already tried "NDLB-connectile-dysfunction=true" as the client (Yealink T28P) is not using rport in its VIA header. But still no luck freeswitch still sending the response to the port in Contact header (5062) instead of the recieving port (14335). 5062 port is actually not valid as the client is behind NAT and only can get the response if freeswitch will send it to 14335 port.</DIV>
<DIV> </DIV>
<DIV>Do you have any other idea about this?</DIV>
<DIV>:-( .........</DIV></BLOCKQUOTE>
<DIV>Regards,</DIV>
<DIV>Belint</DIV></BLOCKQUOTE>
<DIV></DIV></BLOCKQUOTE>
<STYLE>
</STYLE>
<DIV> </DIV>
<DIV> </DIV></body></html>