Sooo, been tracing the logs, and I've noticed that when the problems start occuring (i.e., the outbound call doesn't rollover when I get a rejection from our gateway provider), I see the following in syslog
ERROR: get_out_socket: no socket found forward_req: ERROR: cannot forward to af 2, proto 1 no corresponding listening socket
What socket d'you think it is referring to?
cheers
Mahesh Paolini-Subramanya wrote:
Nope. No error messages. That is what makes this whole thing so strange...
cheers
Juha Heinanen wrote:
Mahesh Paolini-Subramanya writes:
For various reasons, the providers frequently reject the > call,
and we roll the call over to the next provider (next_gw(), etc., etc.)
The lcr module, however, stop rolling the calls over after a
couple of > thousand rejections. in 1.0.1, load_gws()/next_gw() has no "memory" between calls. of course, it is possible that there is a memory leak in lcr module (or some other place), which makes lcr functions fail. do you get any error message in syslog?
-- juha
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users