RE: [reSIProcate] Handling unanswered INVITE requests

["Derek MacDonald" <derek@xxxxxxxx>]

Well, the problem here is retransmissions are up handled at the stack level
and a CANCEL cannot be sent until a provisional response has been received.
See 9.1 of 3261.

If your application wishes to ignore an invite, calling AppDialogSet::cancel
will not stop retransmissions, but will send a CANCEL once a provisional
response is received.

Your app can ignore the dialogset at this point, although a dialog will be
created, and onTerminated will be called for a final response.  Also, if a
200 is received(no 180) I forget if DUM will automactically sned a bye.

I propose that I clean this up as follows:

If DialgoSet::cancel is called(via AppDialogSet::cancel) before any reponses
have been received:

A CANCEL will be set if a provisional response is received.
A BYE will be sent if a 2xx is received.

*No* InviteSessionHandler callbacks will be called as the app has expressed
a lack of interest in that DialogSet.

If the app doesn't want to wait 64T1 it has to set its own Timer and call
Cancel when it loses interest.

--Derek



> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-
> devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Dominique Prunier
> Sent: Tuesday, August 17, 2004 7:00 AM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [reSIProcate] Handling unanswered INVITE requests
> 
> Hello,
> 
> I have the same problem and i may have found something for the (1) but i
> have not tested it yet.
> When you create an InviteSession, you can give your own AppDialogSet which
> has a cancel function.
> Though, i wonder if this function can cancel these kind of invites, i will
> give it a try today.
> 
> Regards,
> Dom.
> 
> ----- Original Message -----
> From: "Dmitry Semyonov" <dsemyonov@xxxxxxx>
> To: <resiprocate-devel@xxxxxxxxxxxxxxxxxxx>
> Sent: Tuesday, August 17, 2004 3:21 PM
> Subject: [reSIProcate] Handling unanswered INVITE requests
> 
> 
> > Hello.
> >
> > I'm sending INVITE to non-existing IP via DUM.
> >
> > I want to be able to
> > 1) cancel retransmissions of such INVITE.
> > 2) know whether DUM is still retransmitting the request or not.
> >
> > I can't do either (1) or (2) since I don't know the
> > InviteSessionHandle, which is normally reported via onXxx() callbacks,
> > because no callback is called in the described situation.
> >
> > Is it a missing functionality, or is it my misunderstanding of the
> > DUM concepts?
> >
> > Thanks.
> >
> >
> > ...Bye..Dmitry.
> > _______________________________________________
> > 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