Which version are you using -- this appeared in a prerelease version
of SER and has been fixed.
-jiri
At 10:24 PM 9/10/2003, Felix Schmid wrote:
Hi,
I got a problem with ser when it's been idle for a while. Any request
sent to it is answered with
SIP/2.0 500 I'm terribly sorry, server error occured (7/TM)..Via
Syslog says this:
Sep 10 16:18:41 gurke ser[65803]: ERROR: get_out_socket: no socket found
Sep 10 16:18:41 gurke ser[65803]: ERROR: add_uac: can't fwd to af 2,
proto 1 (no corresponding listening socket)
Sep 10 16:18:41 gurke ser[65803]: ERROR: t_forward_nonack: failure to
add branches
Sep 10 16:18:58 gurke ser[65809]: BUG: tcp_main_loop: dead child 1
Ser runs on freebsd4.8 here. Any suggestions what could be the reason
for this? Why is it complaining about problems with tcp? I thought that
sip is udp-based (though I know that latest version of ser supports tcp
connections also)?
regards,
felix
--
PGP-Key:
http://belugalounge.net/~felix/Felix%20Schmid.asc
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers