16 May
2018
16 May
'18
1:54 p.m.
Wilkins, Steve writes:
Yes, I do. It seems so strange that nothing I try
will enable it to
go out over TCP. There is very little configuration to force it out
TCP. I have tried a few thing that Alex has suggested but nothing
sends it over TCP.
Show what you get about Listening to syslog when you start K, for
example:
May 16 14:49:21 trout sip-proxy[22795]: Listening on
May 16 14:49:21 trout sip-proxy[22795]: udp: 192.168.43.82
[192.168.43.82]:5060
May 16 14:49:21 trout sip-proxy[22795]: udp: 127.0.0.1 [127.0.0.1]:5070
May 16 14:49:21 trout sip-proxy[22795]: tcp: 192.168.43.82
[192.168.43.82]:5060
May 16 14:49:21 trout sip-proxy[22795]: tcp: 127.0.0.1 [127.0.0.1]:5070
May 16 14:49:21 trout sip-proxy[22795]: tcp: 127.0.0.1 [127.0.0.1]:6060
then
$ru = $ru + ";transport=tcp";
force_send_socket(192.168.43.82:5060); # replace ip:port with yours
t_relay();
-- Juha