[Freeswitch-users] FreeSWITCH-users Digest, Vol 72, Issue 66
Dave R. Kompel
drk at drkngs.net
Sat Jun 9 22:54:51 MSD 2012
There are still some devices that are broken, and won't send RPORT. It sux...
From: Brian West [mailto:brian at freeswitch.org]
To: FreeSWITCH Users Help [mailto:freeswitch-users at lists.freeswitch.org]
Sent: Sat, 09 Jun 2012 11:42:43 -0700
Subject: Re: [Freeswitch-users] FreeSWITCH-users Digest, Vol 72, Issue 66
um this is the purpose of rport, enable it on the endpoint for pain relief.
Sent from my iPad
On Jun 9, 2012, at 9:59 AM, BELint Inc <belintinc at gmail.com> wrote:
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.
Do you have any other idea about this?
-------------- next part --------------
An HTML attachment was scrubbed...
Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users