Re: [Serusers] TCP main process and TCP receiver not starting

Hi I'm using the Hello World.cgf as my configuration file. My problem is that SER does not appear to be listening for TCP connections; it returns an RST when it receives a SYN. at http://mit.edu/sip/sip.edu/ser.shtml it says a correctly running SER listening on 10.1.2.3 and the loop back configured to use 4 processes looks like this: # serctl ps 0 25254 attendant 1 25258 receiver child=0 sock=0 @ 10.1.2.3:5060 2 25259 receiver child=1 sock=0 @ 10.1.2.3:5060 3 25261 receiver child=2 sock=0 @ 10.1.2.3:5060 4 25263 receiver child=3 sock=0 @ 10.1.2.3:5060 5 25265 receiver child=0 sock=1 @ 127.0.0.1:5060 6 25267 receiver child=1 sock=1 @ 127.0.0.1:5060 7 25274 receiver child=2 sock=1 @ 127.0.0.1:5060 8 25280 receiver child=3 sock=1 @ 127.0.0.1:5060 9 25282 fifo server 10 25312 timer 11 25314 tcp receiver 12 25316 tcp receiver 13 25318 tcp receiver 14 25320 tcp receiver 15 25323 tcp main process However when I run serctl ps I get the following: $ serctl ps 0 31360 stand-alone receiver @ 132.181.14.210:5060 1 31361 timer 2 31362 fifo server 3 0 4 0 5 0 6 0 7 0 This SER is listing on 132.181.14.210, but there is only a stand-alone receiver, not receiving childs. I have specified in the cfg file children=4, but it doesnt appear to do so. What am I missing, and why don't the tcp receivers, receiver childs and tcp main process start? Thanks Andrew _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers