Re: [MEDIACTRL] An implementation question about BYE and <unjoin>

[Lorenzo Miniero <lorenzo at meetecho.com>]

Hi Victor,

I can give you my view of the thing, that reflects the way we
implemented our prototype MS and AS. The way we do it is to always try
and do it the clean way, when possible: which means, first the protocol
(the explicit <unjoin>) and then the BYE. Of course we also implemented
support for the other approach, otherwise the mixer package would not be
able to get rid of the resources at asynchronous events.

L.


On Thu, 1 Oct 2009 01:38:21 -0700
Victor Paulsamy <vpaulsamy at ditechnetworks.com> wrote:

> An AS sends a <join> toward a MS to create media stream between two RTP
> sessions terminated on the MS.
> 
> At the time of <join>, the two SIP dialogs, referenced in id1 and id2
> attributes are available.
> 
> Suppose, if one of the parties hung up by emitting a BYE toward the AS, what
> is envisioned as an acceptable behavior for the controlling AS from
> MEDIACTRL perspective (this is one of the loose ends that wasn't specified):
> 
> 1. the AS sends a BYE to cleanup the session; but never sends <unjoin>,
> forcing MS to remove the media stream between the two entities -- implicitly
> -- as the SIP session is cleaned up upon receiving BYE?
> 
> or
> 
> 2. the AS sends <unjoin> first to the MS to remove the established media
> stream and then BYE to cleanup the session?
> 
> Thanks in advance.
> 
> --victor
> 


-- 
Lorenzo Miniero <lorenzo at meetecho.com>