On Wed, Dec 8, 2010 at 12:45 AM, Werner Dittmann <Werner.Dittmann at t-online.de> wrote: > Benny, > > two answers in one mail :-) . > > Regarding the media callback: > > IMHO your proposal to have a new callback function > "*on_create_media_transport(...)" is very good and would solve the > problem. Applications can use this to create the transport chain they > need. It's simple and easy to use, in particular if pjsua creates the > base transport (usually UDP or ICE) as you proposed. > Great, I just created https://trac.pjsip.org/repos/ticket/1173 for this. > > While it is not a real problem to put the ZRTP stuff into a complete > separate directory it would require some additional effort for > application developers. Using the well established third party > structure and build mechanisms simplify many things. > Okay. I guess either way it doesn't really matter as long as there is clear instruction for the users. >>> >>> Only topic to solve: enable an application to tell pjsua to use the >>> transport_zrtp :-) . >>> >> >> Yes, that's always a problem for new features that are not in the trunk. > > This will be solved for transport_zrtp ?with your proposal to add the > new callback. > I see. I thought you mean how to add few feature into (existing) pjsua application. Cheers Benny
