[Serusers] ser probs

[deen]

Hi All,

How do I check whether the SIP registration request hits the server, I
cannot find these in the debug. At what level of
debug should I run to see the SIP requests between the server and the
client.

Thanks

Deen

----- Original Message -----
From: "Jan Janak" <jan at iptel.org>
To: "deen" <deen at slt.lk>
Cc: "Nils Ohlmeier" <nils at iptel.org>; <serusers at lists.iptel.org>; "Jiri Kuthan"
<jiri at iptel.org>
Sent: Wednesday, January 14, 2004 1:44 AM
Subject: Re: [Serusers] ser probs


> Probably if (uri==myself) condition doesn't match the hostname or IP
> address in the Request-URI of the message. SER prints all IP addresses
> and hostnames that will be matched by the condition when it starts. If
> the hostname/IP address is not there, use listen and/or alias directive
> to add it.
>
> See also the archives of the mailing list, this has been discussed many
> times.
>
>   Jan.
>
> On 14-01 08:22, deen wrote:
> >
> >
> > Thanks Nils, I started with debug mode off. And the registration fails
with
> >
> > registration denied: (SIP/2.0 483 Too Many Hops)
> >
> > Now I suspect the request is coming to the server but there is a routing
> > issue. Any idea why this could be.
> >
> > Deen
> >
> > ----- Original Message -----
> > From: "Nils Ohlmeier" <nils at iptel.org>
> > To: "deen" <deen at slt.lk>; <serusers at lists.iptel.org>; "Jiri Kuthan"
> > <jiri at iptel.org>
> > Sent: Tuesday, January 13, 2004 6:19 AM
> > Subject: Re: [Serusers] ser probs
> >
> >
> > > 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 at iptel.org>
> > > > To: <deen at slt.lk>; <serusers at 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 at lists.iptel.org
> > > > http://lists.iptel.org/mailman/listinfo/serusers
> > >
> > >
> >
> > _______________________________________________
> > Serusers mailing list
> > serusers at lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serusers
>