I've built using latest trunk now, but I won't be able to test again until tomorrow - I'll get back to you after that. Just to make the scenario a bit more clear; The Avaya CM has an internal SIP-trunk over tls, to an Avaya SES Server (SIP Enablement Services), this one talks UDP to FreeSWITCH. Could this be something that causes the problem? I also tried to dial into the dialplan, answer the call, and then try to deflect the call using REFER. This didn't create any SIP messages either (and nothing happened with the call), so it seems there might be a bigger issue than just BYE. Peter On 09-04-15 20.04, "Brian West" <brian@freeswitch.org> wrote: I recall this and transport=tls in this case... maybe MikeJ can chime in on this one..I thought we already fixed this. On Apr 15, 2009, at 12:50 PM, Peter Olsson wrote: Record-Route: <sip:192.168.94.53:6001;lr;transport=tls> Brian West brian@freeswitch.org -- Meet us at ClueCon! http://www.cluecon.com <http://www.cluecon.com/><http://www.cluecon.com/> !DSPAM:49e623a532931080721630!