morfair, for clarification sip responses do -not- necessarily go to the originating port, Via Route Contact headers etc can mean other ports are used. It could be 10.10.10.10 told 20.20.20.20 to respond on 5080. Hence the request to see the actual packets.

On Fri, 5 Oct 2018 at 00:02, Michael Jerris <mike@jerris.com> wrote:
I would need to see a full and UNMODIFIED sip trace to properly answer this question.

> On Oct 4, 2018, at 11:28 AM, morfair@gmail.com wrote:
>
> I have external profile on port 5080. When FS get INVITE on 5080 from remote 5060 port, FS response on 5080 port too instead 5060
>
> 20.20.20.20 - fs
>
> 10.10.10.10 - remote sip
>
> 18:23:49.675349 IP 10.10.10.10.5060 > 20.20.20.20.5080: SIP: INVITE sip:7001@20.20.20.20:5080;user=phone SIP/2.0
> 18:23:49.678953 IP 20.20.20.20.5080 > 10.10.10.10.5080: UDP, length 363
>
>
> How to fix whis? FS should response on originate udp port.
>


_________________________________________________________________________
Professional FreeSWITCH Services
sales@freeswitch.com
https://freeswitch.com

Official FreeSWITCH Sites
https://freeswitch.com/oss
https://freeswitch.org/confluence
https://cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
https://freeswitch.com