[reSIProcate] REFER support

[Scott Godin]

There is some info on the wiki, more inline...
http://wiki.resiprocate.org/wiki/index.php?title=Dealing_with_REFERs


> -----Original Message-----
> From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-
> devel-bounces at list.sipfoundry.org] On Behalf Of Boris Rozinov
> Sent: Monday, December 19, 2005 11:39 AM
> To: resiprocate-devel at list.sipfoundry.org
> Subject: [reSIProcate] REFER support
> 
> Hi all,
> 
> Hi guys
> I'll need to make pretty extensive use of REFER and I
> got few questions about REFER support in DUM
> 
> 1)	According to RFC 3515 REFER request MAY be placed
> outside the scope of a dialog created with an INVITE.
> It looks that DUM allows refer on in context of
> connected InviteSession or I missed something?

[Scott] Take a look at DialogUsageManager::makeOutOfDialogRequest () API
for sending refer outside of an existing Dialog.  Note:  the header file
defines a makeRefer method - but it is not implemented.

> 2)	Is it possible to construct REFER with replace
> header, when UA issuing REFER does not participate in
> the dialog to be replaced and got its ID by some other
> means (for example using subscription to Dialog Event
> Package)?

[Scott] You should be able to just add a replaces header to the message
returned by makeOutOfDialogRequest, before calling send.

> 3)	How NOTIFY can be correlated with REFER in case of
> overlapping REFER subscriptions?

 [Scott] Have a look at the AppDialog/AppDialogSet stuff.  You could
also just look at the DialogSetId of the messages to match.
http://wiki.resiprocate.org/wiki/index.php?title=DUM_Associating_Applica
tion_Data_with_DialogSets_and_Dialogs


> Thanks,
> Boris
> 
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel