hi Alan, another way could be to use SIP INFO or SIP MESSAGE requests for low bandwith messaging, however you would have to write the handling yourself. regards, Harry Von meinem iPad gesendet > Am 04.06.2015 um 18:21 schrieb Alan Synnestvedt <asynnestvedt at gmail.com>: > > I would like to extend my earlier question below by asking what mechanisms are available in PJSIP that are useful for custom application messaging. I stumbled across the RTCP APP packet specification and am considering using this for passing things like volume level, etc. Has anyone implemented this or something similar in a Media Transport Adapter before? If there is a better way I would like to hear some opinions. > > Thanks! > Alan > > >> On Thu, Jun 4, 2015 at 10:43 AM, Alan Synnestvedt <asynnestvedt at gmail.com> wrote: >> In my application I am running into issues handling a scenario where a capture device on one side of the conversation changes his orientation, which needs to reflect on the rendering device on the other side. >> >> I am using iOS and have figured out how to use pjsua_vid_win_rotate() to deal with changes of orientation assuming the capture side of the conversation is using a static orientation. The issue seems to be that the render side of the conversation does not get notified that the orientation of the video being sent to him has changed. What is the proper way to handle this with pjsip? >> >> So basically the problem is as follows: >> >> User A is in portrait. >> User B is also in portrait and sets window rotation to 270. This leads to a proper video render. >> User A changes orientation to landscape mid call. >> User B needs to change his window rotation to 0 to accommodate the change but is not aware a change has been made. > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20150605/9a2b1c60/attachment.html>