1 Oct
2012
1 Oct
'12
9:42 a.m.
Owen Lynch writes:
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.
perhaps calling add_contact_alias() on subscribe would help.
-- juha