Re: [reSIProcate-users] Does reSIProcate support RFC 5168?
First, please keep in mind that RFC 5168 is intended for limited
deployment, and is not a candidate for an IETF standard. It has a number
of shortcomings -- not the least of which is that it can overload the
proxy network with media-related information. You should not be using
RFC 5168 except to interoperate with *OLDER* Microsoft, Polycom, and
Radvision implementations.
The standard way to perform fast video update is defined in RFC 5104;
you should use that instead.
That said, resiprocate certainly supports sending and receiving INFO
messages. Handling of the content of INFO bodies -- including those
defined in RFC 5168 -- is the responsibility of the application built on
top of resiprocate.
To do this, you'll need to set up the profile you're using to indicate
support for INFO and for the "application/media_control+xml" MIME type.
See the example Scott Godin posted to the mailing list yesterday to get
an idea of how to do this (you'll also want to use the
"addSupportedMimeType()" method on the master profile).
You'll also need to be very careful not to send these messages unless
the far end indicates support for INFO and for the
"application/media_control+xml" MIME type -- otherwise, you may find the
remote party tearing the call down or doing something else unexpected
when you send this INFO message.
/a
Xiexin wrote:
Does reSIProcate support RFC 5168?
------------------------------------------------------------------------
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/