13 Jan
2004
13 Jan
'04
8:32 p.m.
Jiri,
Thanks for the info.
There is definitely no NAT here. I am pretty new to this - what could be the
likely misconfiguration.
Thanks
Deen
----- Original Message -----
From: "Jiri Kuthan" <jiri(a)iptel.org>
To: <deen(a)slt.lk>lk>; <serusers(a)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.
>
>
> -jiri
>
>
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). 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).