Discussion:
VideoFastUpdate in dual video mode
Oren Libis
2010-03-08 14:41:43 UTC
Permalink
Hi all,

I would appreciate your help with the following question:
I have a single SIP session of several video streams. Call initiation
(INVITE) contained SDP body with different SDP media descriptors - one
media descriptor for every video stream. (this is common for example
when there is a presentation channel). Please note that each video
stream has different destination port.
Due to packet loss on one of the streams, I would like to issue
VideoFastUpdate request. However, the VideoFastUpdate is for the entire
session, and I could not find a way to indicate to the remote party
which of the streams requests for an Intra frame.
Please advise.

Thanks,
Oren Libis
Peter Musgrave
2010-03-08 20:14:28 UTC
Permalink
Hi Oren,

Are you sending an INFO with a body as per RFC5168 to request the update?

There are fields in the XML that relate to the stream source - although how
they are linked to a specific stream in terms of IP and port is not clear to
me (on a quick read of that doc).

Since this came out of mmusic - that list may be able to enlighten us?

Regards,

Peter
Olle E. Johansson
2010-03-09 07:21:54 UTC
Permalink
Post by Oren Libis
Hi all,
I have a single SIP session of several video streams. Call initiation (INVITE) contained SDP body with different SDP media descriptors – one media descriptor for every video stream. (this is common for example when there is a presentation channel). Please note that each video stream has different destination port.
Due to packet loss on one of the streams, I would like to issue VideoFastUpdate request. However, the VideoFastUpdate is for the entire session, and I could not find a way to indicate to the remote party which of the streams requests for an Intra frame.
You can send a FUR - fast update request - in the RTCP stream, which is one per video stream.

/O
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is essentially closed and only used for finishing old business.
Use sip-***@cs.columbia.edu for questions on how to develop a SIP implementation.
Use ***@ietf.org for new developments on the application of sip.
Use ***@ietf.org for issues related to maintenance of the core SIP specifications.
Loading...