It looks to me like Freeswitch is actually trying to send the BYE, but is unable to establish a tcp connection back to the address:port of the UAC (which in this case is 1.1.1.1:33919).  See from your log snippet below, which is right after you received and responded to the BYE from UAS.

nta.c:8304 outgoing_send() nta: sent BYE (103901687) to tcp/1.1.1.1:33919
tport.c:4160 tport_pend() tport_pend(0x7f78940e3e90): pending 0x7f78941006e0 for tcp/1.1.1.1:33919 (already 0)
2017-03-02 17:25:02.992038 [DEBUG] switch_core_state_machine.c:584 (sofia/internal/3059001003@9.9.9.9:5066) Running State Change CS_REPORTING (Cur 1 Tot 101)
2017-03-02 17:25:02.992038 [DEBUG] switch_core_state_machine.c:938 (sofia/internal/3059001003@9.9.9.9:5066) State REPORTING
2017-03-02 17:25:02.992038 [DEBUG] switch_core_state_machine.c:174 sofia/internal/3059001003@9.9.9.9:5066 Standard REPORTING, cause: NORMAL_CLEARING
2017-03-02 17:25:02.992038 [DEBUG] switch_core_state_machine.c:938 (sofia/internal/3059001003@9.9.9.9:5066) State REPORTING going to sleep
2017-03-02 17:25:02.992038 [DEBUG] switch_core_state_machine.c:610 (sofia/internal/3059001003@9.9.9.9:5066) State Change CS_REPORTING -> CS_DESTROY
2017-03-02 17:25:02.992038 [DEBUG] switch_core_session.c:1664 Session 100 (sofia/internal/3059001003@9.9.9.9:5066) Locked, Waiting on external entities
2017-03-02 17:25:02.992038 [NOTICE] switch_core_session.c:1682 Session 100 (sofia/internal/3059001003@9.9.9.9:5066) Ended
2017-03-02 17:25:02.992038 [NOTICE] switch_core_session.c:1686 Close Channel sofia/internal/3059001003@9.9.9.9:5066 [CS_DESTROY]
2017-03-02 17:25:02.992038 [DEBUG] switch_core_state_machine.c:741 (sofia/internal/3059001003@9.9.9.9:5066) Running State Change CS_DESTROY (Cur 0 Tot 101)
2017-03-02 17:25:02.992038 [DEBUG] switch_core_state_machine.c:751 (sofia/internal/3059001003@9.9.9.9:5066) State DESTROY
2017-03-02 17:25:02.992038 [DEBUG] mod_sofia.c:343 sofia/internal/3059001003@9.9.9.9:5066 SOFIA DESTROY
2017-03-02 17:25:02.992038 [DEBUG] switch_core_state_machine.c:181 sofia/internal/3059001003@9.9.9.9:5066 Standard DESTROY
2017-03-02 17:25:02.992038 [DEBUG] switch_core_state_machine.c:751 (sofia/internal/3059001003@9.9.9.9:5066) State DESTROY going to sleep
tport.c:2689 tport_connected() tport_connected(0x7f78940e3e90): events CONNECTED ERR
tport.c:4222 tport_release() tport_release(0x7f78940e3e90): 0x7f78941006e0 by 0x7f78940f43f0 with (nil)
nta.c:8496 outgoing_print_tport_error() nta: BYE (103901687): Connection refused (111) with tcp/[1.1.1.1]:33919



On Mar 3, 2017, at 10:33 AM, David Villasmil <david.villasmil.work@gmail.com> wrote:

Anyone on this? If more debug info is needed, i can provide it.
ᐧ

Regards,

David Villasmil
phone: +34669448337

On Thu, Mar 2, 2017 at 11:53 PM, David Villasmil <david.villasmil.work@gmail.com> wrote:
Hello guys,

By the way, the subject reads "200 ok not forwarded", but it's actually the BYE...

I'm hoping there's something obvious i'm not seeing.... but it's still happening, BYE is not being forwarded and the other leg stays there until a timeout where the a leg triggers a BYE to be sent to FS and FS responds with 481... 

The only thing I see is a "not found by name" but i'm not sure what that means (I'd say fs can't find the other leg by name? Don't know why, the call is up)

Help is very much appreciated.

Attaching fs log with sofia debug on...

David
ᐧ

Regards,

David Villasmil

On Thu, Mar 2, 2017 at 9:13 PM, David Villasmil <david.villasmil.work@gmail.com> wrote:
Michael,

Installing FreeSWITCH (Version 1.6.15 -32-bec4538 64bit) seems to have solved the problem, keep you posted.

Thanks for the suggestion.

David
ᐧ

Regards,

David Villasmil

On Thu, Mar 2, 2017 at 6:38 PM, David Villasmil <david.villasmil.work@gmail.com> wrote:
Will do, still will also do the debugging

On Thu, Mar 2, 2017 at 6:24 PM Michael Jerris <mike@jerris.com> wrote:
I’d update to latest 1.6 release or latest master before you do anything else here.

On Mar 2, 2017, at 10:04 AM, David Villasmil <david.villasmil.work@gmail.com> wrote:

Hello Guys,

I'm using FreeSWITCH (Version 1.9.0 git f3b7105 2016-11-15 01:50:51Z 64bit) is ready

And i'm seeing the issue where the 200OK is not being forwarded from FS to the client.

I'm attaching FS Log and sip trace.

1.1.1.1 = Client (Grandstream GXP1165)
9.9.9.9 = freeSWITCH
10.10.10.10 = Terminating GW (my_gateway)

Been scratching my head for some time...


Appreciate your help!



Regards,

David Villasmil
ᐧ
<no_forward_200_ok.txt><no_forward_200ok_fs_log.txt>_________________________________________________________________________
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.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
http://www.freeswitch.org



_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.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
http://www.freeswitch.org