reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

RE: [reSIProcate] UdpTransport problem

It looks like the 200 OK is being received and processed by the stack.
However, it looks like the filedescriptor for the UDP transport (read set)
is still in the FdSet. What does your main loop with the select call in it
look like?

Do you create a new FdSet before each call to buildFdSet. e.g.

while (1)
{
  FdSet fdset;
  stack.buildFdSet(fdset);
  int ret = fdset.selectMilliseconds(stack.getTimeTillNextProcessMS());
  if (ret >= 0)
  {
     stack.process(fdset);
  }
}

If you defined the FdSet outside the loop, you might see this behavior.

Jason


> STACK | 20040806-161216.154 | spaisner.bridgeport-networks.com | stix |
> RESIP:TRANSPORT | 28812 | 1453398960 | Transport.cxx:375 |
> SIP/2.0 200 OK - updated subscriber registration
> To:
> <sip:caller_0@xxxxxxxxxxxxxx:5060>;tag=b27e1a1d33761e85846fc98f5f3
> a7e58.1939
> From: <sip:called_0@xxxxxxxxxxxx:5080>;tag=b31d6c10
> Via: SIP/2.0/UDP
> 192.168.10.4:5080;branch=z9hG4bK-c87542-380322371-1--c87542-;rport=5080
> Call-ID: cfd2997689ab4f3f
> CSeq: 1 REGISTER
> Server: Sip EXpress router (0.8.99-dev (i386/linux))
> Content-Length: 0
> P-Behind-NAT: Yes
>
>

> RESIP:TRANSPORT | 28812 | 1453398960 | UdpTransport.cxx:159 | Scanner
> rejecting datagram as unparsable / fragmented from [ V4
> 192.168.10.105:5060 UDP received on: Transport: [ V4 0.0.0.0:5080 UDP
> connectionId=0 ] connectionId=0 ]
> DEBUG | 20040806-161235.887 | spaisner.bridgeport-networks.com | stix |
> RESIP:TRANSPORT | 28812 | 1453398960 | UdpTransport.cxx:160 |
>
> --Sharon
>
>
> On Fri, 2004-08-06 at 15:41, Jason Fischl wrote:
> > Can you rerun your test program, run it with LOG_STACK and post the log
> > results. It might also help if you provided an ethereal capture
> file (pcap)
> > of the SIP packets.
> >
> > Thanks,
> > Jason
> >
> >
> > > -----Original Message-----
> > > From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > > [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of
> > > sharon paisner
> > > Sent: Friday, August 06, 2004 12:31 PM
> > > To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > > Subject: [reSIProcate] UdpTransport problem
> > >
> > >
> > > I've recently upgraded my resiprocate code to the latest from svn. Now
> > > "200 REGISTER" responses are being discarded by the
> UdpTransport as wish
> > > the error:
> > >
> > > | UdpTransport.cxx:159 | Scanner rejecting datagram as unparsable /
> > > fragmented
> > >
> > > Can anyone tell me what's going on? release 0.4.0 was able to parse
> > > these messages.
> > >
> > > thanks,
> > > Sharon
> > >
> > > _______________________________________________
> > > resiprocate-devel mailing list
> > > resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> > >
> >
> >
>