On Wednesday 14 January 2004 02:32, deen wrote:
Jiri,
Thanks for the info.
Also I cannot register from a SIP client I get an error.
Proxy registration failed. Reason : general registration failure (Client non-INVITE transaction [Trying]: timed out.
That's easy -- either the client didn't deliver the REGISTER to SER, (misconfiguration?) or the reply was not delivered (for example because of NAT presence).
There is definitely no NAT here. I am pretty new to this - what could be the likely misconfiguration.
When your SER listens only on 127.0.0.1, because you use debug mode, then no client (except clients running on the same host) can reach the server.
Nils
Thanks
Deen
----- Original Message ----- From: "Jiri Kuthan" jiri@iptel.org To: deen@slt.lk; serusers@lists.iptel.org Sent: Monday, January 12, 2004 6:20 AM Subject: Re: [Serusers] ser probs
At 12:59 AM 1/13/2004, M.I.Deen wrote:
Dear List,
My serctl ps shows very less processes see below.
/usr/sbin/serctl ps 0 24442 stand-alone receiver @ 127.0.0.1:5060 1 24444 timer 2 24446 fifo server 3 0 4 0 5 0 6 0 7 0
I wonder whether this is typical.
it is, if you started SER in debugging mode.
Also I cannot register from a SIP client I get an error.
Proxy registration failed. Reason : general registration failure (Client non-INVITE transaction [Trying]: timed out.
That's easy -- either the client didn't deliver the REGISTER to SER, (misconfiguration?) or the reply was not delivered (for example because of NAT presence).
-jiri
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers