Hi, I want to configure Kamailio so that it sends a NOTIFY using the tcp connection already established by the client SUBSCRIBE request. The aim is for clients to establish secure TLS connections to Kamailio when they first register or subscribe, then for kamailio to reuse these connections for all further NOTIFY/INVITE requests. I thought that adding force_tcp_alias() in the route script would accomplish this, but it doesn't. The NOTIFY always uses the ip:port tuple specified in the SUBSCRIBE Contact header. Can anyone shed any light on this? Thanks, Owen Lynch