30 May
2008
30 May
'08
11:06 a.m.
Hi guys,
The topic was solved on the IRC channel - the error means that RURI
forces TCP as transport (proto 2), but openser has no TCP interface
configured.
The bottom issue is the misconfiguration in LCR of the GW, where proto 2
was set for one of the GWs.
Regards,
Bogdan
Juha Heinanen wrote:
mark morreny writes:
I have added "listen=tcp:192.168.1.104"
to the openser.cfg and when openser
starts up, it shows that it is listening on both tcp and udp. However, I am
still getting "ERROR:tm:update_uac_dst: failed to fwd to af 2, proto 2 (no
corresponding listening socket)" I think the problem is with the
";transport=tcp" string that next_gw() is appending at the end. Is there
anyway to fix it?
next_gw() should not on its own invent ;transport=tcp. it should only
do it if you have specified tcp transport for this gw in transport
column of gw table. see lcr README.
-- juha
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users