[serusers]: trusted table(permissions module)

Kamal.Mann at t-systems.com Kamal.Mann at t-systems.com
Mon Nov 6 10:03:00 CET 2006


Hi All,
So what you guys expect; I need to do in this case? Please give your
helpful suggestions;

Regards
Kamal Mann

-----Original Message-----
From: Andrey Kuprianov [mailto:andrey.kouprianov at gmail.com] 
Sent: Monday, November 06, 2006 1:26 PM
To: serusers at iptel.org
Subject: Re: [serusers]: trusted table(permissions module)

Hi again,

Yups.. Nils is right..It says:

"... req_src_ip=10.25.119.155 req_src_port=5060 in_uri=10.25.119.155
out_uri=10.25.119.155 ..."

out_uri should be 10.25.119.156 (not 155)

  Andrey.

On 11/6/06, Andrey Kuprianov <andrey.kouprianov at gmail.com> wrote:
> Hi,
>
> See inline
>
> On 11/6/06, Kamal.Mann at t-systems.com <Kamal.Mann at t-systems.com> wrote:
> > Hi Andrey
> > On SIP AS side sip stack is running on port 5060, then this packet
send
> > to Application running over on top of it. Is their any issue with
this
> > scenario?
>
> I think there might be... I just think there should be some
> consistency between your SIP and UDP/TCP packets. If UDP source port
> is 4141, for example, then your Contact header (and From header too),
> should have this port. If someone else has some good ideas, plz,
> comment.
>
> > In SIP packet its 5060 only. Port is changed only in UDP/TCP
packets.
> > But I think their shouldn't be anything wrong with this cause SIP
Stack
> > utilizes only sip packets (inside of UDP). And SER is replying to
it.
> >
>
> Your ethereal traces on SER side show 100 and 407 responses are marked
> as black and red color (i use ethereal 0.99.x). That means something
> is wrong.
>
> > Regards
> > Kamal Mann
> >
>
>  Regards,
>
>     Andrey.
>
> > -----Original Message-----
> > From: Andrey Kuprianov [mailto:andrey.kouprianov at gmail.com]
> > Sent: Monday, November 06, 2006 11:52 AM
> > To: serusers at iptel.org
> > Subject: Re: [serusers]: trusted table(permissions module)
> >
> >  Hi Kamal,
> >
> > I noticed one strange thing in your traces. INVITE from SIP-AS is
sent
> > from port 4141 (!) to port 5060, but 100 and 407 response from SER
is
> > sent back to port 5060 (not port 4141)! Can you, please, explain
why?
> >
> >   Andrey.
> >
> > On 11/6/06, Kamal.Mann at t-systems.com <Kamal.Mann at t-systems.com>
wrote:
> > > Hi Andrey
> > > Please find ethereal packet capture enclosed. SER n/w dump is
> > 'SER_SERVER' and SIP_AS n/w dump is 'SAS_SERVER'.
> > > SER IP = 10.25.119.155
> > > SIP AS IP = 10.25.119.156
> > > To URI is registered at SER end (dilip)
> > > From URI is Application Name (example) and neither created nor
> > registered (WakeUpService) with SER.
> > >
> > > Thanks in anticipation
> > > Kamal Mann
> > _______________________________________________
> > 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



More information about the sr-users mailing list