RE: [reSIProcate] invites not a request, nor response, or anything else
Or if the branch parameter in the via matches an existing transaction
the message will be discarded as a retransmission by the stack. Ensure
that the sender is correctly changing the branch for each transaction.
> -----Original Message-----
> From: jason.fischl@xxxxxxxxx [mailto:jason.fischl@xxxxxxxxx] On Behalf
Of
> Jason Fischl
> Sent: Monday, February 27, 2006 11:56 AM
> To: Scott Godin
> Cc: jennifer mackay; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [reSIProcate] invites not a request, nor response, or
> anything else
>
> If you received an "in dialog" INVITE without having a corresponding
> dialog, you would probably see this behavior. An "in dialog" INVITE
> would have a to tag on the To header.
>
> Jason
>
>
> On 2/27/06, Scott Godin <slgodin@xxxxxxxxxxxx> wrote:
> > I've never seen this behaviour - are you using Ethereal to ensure
that
> > the network interface is even seeing the message?
> >
> > Scott
> >
> > > -----Original Message-----
> > > From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > [mailto:resiprocate-
> > > devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of jennifer mackay
> > > Sent: Monday, February 27, 2006 11:45 AM
> > > To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > > Subject: [reSIProcate] invites not a request, nor response, or
> > anything
> > > else
> > >
> > >
> > > Hey Resippies - we are trying to do a blind transfer and
occasionally,
> > > we get INVITEs that we don't handle at all. We added in some
logging
> > to
> > > our logic and it turns out that we actually don't see those INVITE
> > > messages. We never see in our logs that it was interpreted as a
> > request
> > > message or a response message (or just for kicks, anything else).
Has
> > > anyone else ever seen this, where and INVITE (or any other
message)
> > > isn't received from the resiprocate library? Is it a timing issue?
> > Could
> > > we be losing these messages due to incorrect usage of the
> > > fdset.selectMilliSeconds method?
> > >
> > > We use it this way:
> > > fdset.selectMilliSeconds(10)
> > >
> > > We tried using this:
> > fdset.selectMilliSeconds(getTimeTillNextProcessMS),
> > > but that screwed it up even more. We adjusted the value
> > > selectMilliSeconds() from 0 to 20 and that didn't solve it.
> > >
> > > Any help would be greatly appreciated.
> > >
> > > Jennifer MacKay
> > > _______________________________________________
> > > resiprocate-devel mailing list
> > > resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> > _______________________________________________
> > resiprocate-devel mailing list
> > resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> >