I am personally not familiar with a re-invite call flow working like you describe. Since you are being told by someone that this should work, I’d suggest asking them to point to the relevant section of the RFC ? A re-invite with no SDP I have typically only seen as a 3pcc INVITE when first setting up a session (ie when the initiator wants to delay sending its SDP until the ACK). Perhaps others have had experience with this in a reinvite scenario as you describe, but I find it pretty atypical. On Aug 11, 2017, at 10:48 AM, Andrew Cassidy <andrew@cassidywebservices.co.uk> wrote: Hi Guys, Just wanted to check a behaviour with you guys before rushing to upgrade FreeSWITCH from 1.4.26-37 We are reciveing a reinvite with a=inactive followed by an reinvite with no SDP. I am being told the one with no SDP should revert the media the the previously established. FreeSWITCH isn't currently doing that, (or passing the empty one back to the endpoint) it's just keeping the call held. Which is the correct behaviour? Kind regards, -- Andrew Cassidy BSc (Hons) MBCS SSCA Managing Director 03303 880 960 andrew@cassidyweb.co.uk <mailto:andrew@cassidywebservices.co.uk> www.cassidyweb.co.uk <http://www.cassidywebservices.co.uk/>_________________________________________________________________________ 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