#17 How to learn servers multicast capabilities
If a media session is delivered through the usage of
multicast, the session description, to indicate that
delviery will be done to assigned multicast address. So
this is evident as long as you can put the multicast
address into the SDP and distribute it.
However how does a client learn that a session can be
distributed as multicast, but no multicast address is
pre-assigned to the session when the SDP is published?
It seems that we can't quite express this case. Or does
someone see a possiblity? Is it something that needs to
be solved.
Another interesting use case is if a multicast
conference invites a RTSP server into the session and
the controlling entity request the server to play to
the already used multicast addresses. Does the server
needs to be able to announce this support, or is it
something the client simply ask for and the server
either succeds or fails?
Logged In: YES
user_id=302620
I think this is most likely something for a extension.
Multicast support is not a top priority.
I will put it into the feature request tracker.
The transport header in the setup request would indicate multicast and an address.
What else is needed?