[reSIProcate] Slight change to onReferAccepted/onReferRejected callbacks in InviteSessionHandler

[Derek MacDonald]

DUM used to call onReferRejected even if the REFER was accepted if the
NOTIFY message terminated the ServerSubscription.

 

For example, for:

 

A                                B

| -----------REFER--------->|

| <-----------202---------------|

| <-----------NOTIFY---------|

 

Where the NOTIFY terminates the subscription, through ubscription-state of
terminated or a 200 class 

The callback sequence would be:

 

ClientSubscriptionHandler::onTerminated

InviteSessionHandler::onReferRejected.

 

 

This is not correct if the transfer was successful; the NOTIFY sipfrag could
contain a 200 class status line.  DUM now calls onReferAccepted if the REFER
message is accepted, regardless of the contents of the NOTIFY.  The new
callback sequence is:

 

InviteSessionHandler::onReferAccepted.

ClientSubscriptionHandler::onTerminated

 

--Derek

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060331/676223e9/attachment.htm>