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

Re: [reSIProcate] added support for suppression of REFER method implicit sbscription based on draft-ietf-sip-refer-with-norefersub-03


Daniel -

This is great! Thanks!

Note that -04 slipped out while you were working. There were no normative
changes IIRC.

Several questions:

1. Is this a complete implementation of the draft? Did you make changes to
    the client side of DUM or only the server side?

2. Did you find anything that was hard to implement?

3. How are you addressing the requirement that any client issuing a
norefersub REFER ensure that the request doesn't fork? I don't think
     we have gruus down enough yet to rely on them do we?

4. What modifications to the stack did you make to allow (or do we allow yet) REFERs to make it up to DUM if they show up outside an existing dialog?

(For those not tracking where this is going in the IETF - once we have a way to get REFERs to the right places without forking and a way to talk about other dialogs in progress (gruu and target-dialog respectively), we'll have
enabled a way to issue a REFER and ask for a subscription to the result
only if we care and without causing multiple usages to exist on any given dialog.)

RjS

On Jan 30, 2006, at 4:07 PM, Daniel Shi wrote:

Hi,



The following changes were made to suppress the implicit subscription with
the REFER method based on draft-ietf-sip-refer-with-norefersub-03:



1.      A new header called Refer-Sub was added in the stack.
2.      An extra parameter was added to the refer methods in InviteSession.
3.      Two new methods called acceptReferNoSub and rejectReferNoSub were
added to InviteSession to accept or reject a refer without implicit
subscription requests.
4.      A new callback onReferNoSub was added in InviteSessionHandler. This
callback will be called upon receiving a refer request with Refer- Sub field
is set to false.



The changes have been commited revision 5830.



Thanks.

Daniel



<winmail.dat>
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel