Hello, I’m trying to compile PJSIP With TLS and WebRTC as the media engine. I have a problem because WebRTC uses boring SSL and PJSIP uses Open SSL and these two conflict. Has anyone encountered this issue already? With Best Regards, Arik Halperin

Webrtc boringSSL is almost identical to openssl , drop boringssl lib and try > On 17 Feb 2016, at 10:13 AM, Arik Halperin <arik.halperin@greenfieldtech.net> wrote: > > Hello, > > I’m trying to compile PJSIP With TLS and WebRTC as the media engine. I have a problem because WebRTC uses boring SSL and PJSIP uses Open SSL and these two conflict. > > Has anyone encountered this issue already? > > With Best Regards, > Arik Halperin > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

But how do you compile WebRTC without boring SSL? Also, there are some methods used by WebRTC in the latest versions that exist in boring SSL and not in Open SSL. boring SSL used to be just a subset of Open SSL, but they added stuff to it that’s not in OpenSSL. Arik > On 17 Feb 2016, at 10:30 AM, Shaul Kedem <shaul@yallo.com> wrote: > > Webrtc boringSSL is almost identical to openssl , drop boringssl lib and try > >> On 17 Feb 2016, at 10:13 AM, Arik Halperin <arik.halperin@greenfieldtech.net> wrote: >> >> Hello, >> >> I’m trying to compile PJSIP With TLS and WebRTC as the media engine. I have a problem because WebRTC uses boring SSL and PJSIP uses Open SSL and these two conflict. >> >> Has anyone encountered this issue already? >> >> With Best Regards, >> Arik Halperin >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing list >> pjsip@lists.pjsip.org >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

did you set use_openssl as 1 in src/build/common.gypi, and build_ssl as 0 in src/webrtc/build/common.gypi ? from here: https://groups.google.com/forum/#!topic/discuss-webrtc/muT4irg2dvI <https://groups.google.com/forum/#!topic/discuss-webrtc/muT4irg2dvI> > On 17 Feb 2016, at 10:37 AM, Arik Halperin <arik.halperin@greenfieldtech.net> wrote: > > But how do you compile WebRTC without boring SSL? Also, there are some methods used by WebRTC in the latest versions that exist in boring SSL and not in Open SSL. > > boring SSL used to be just a subset of Open SSL, but they added stuff to it that’s not in OpenSSL. > > Arik >> On 17 Feb 2016, at 10:30 AM, Shaul Kedem <shaul@yallo.com> wrote: >> >> Webrtc boringSSL is almost identical to openssl , drop boringssl lib and try >> >>> On 17 Feb 2016, at 10:13 AM, Arik Halperin <arik.halperin@greenfieldtech.net> wrote: >>> >>> Hello, >>> >>> I’m trying to compile PJSIP With TLS and WebRTC as the media engine. I have a problem because WebRTC uses boring SSL and PJSIP uses Open SSL and these two conflict. >>> >>> Has anyone encountered this issue already? >>> >>> With Best Regards, >>> Arik Halperin >>> _______________________________________________ >>> Visit our blog: http://blog.pjsip.org >>> >>> pjsip mailing list >>> pjsip@lists.pjsip.org >>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >> >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing list >> pjsip@lists.pjsip.org >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

Tried this, didn’t help(Could be I did something wrong). Did you try it on the latest WebRTC revision? Arik > On 17 Feb 2016, at 11:08 AM, Shaul Kedem <shaul@yallo.com> wrote: > > did you set use_openssl as 1 in src/build/common.gypi, and build_ssl as 0 in src/webrtc/build/common.gypi ? > > from here: https://groups.google.com/forum/#!topic/discuss-webrtc/muT4irg2dvI <https://groups.google.com/forum/#!topic/discuss-webrtc/muT4irg2dvI> > > >> On 17 Feb 2016, at 10:37 AM, Arik Halperin <arik.halperin@greenfieldtech.net <mailto:arik.halperin@greenfieldtech.net>> wrote: >> >> But how do you compile WebRTC without boring SSL? Also, there are some methods used by WebRTC in the latest versions that exist in boring SSL and not in Open SSL. >> >> boring SSL used to be just a subset of Open SSL, but they added stuff to it that’s not in OpenSSL. >> >> Arik >>> On 17 Feb 2016, at 10:30 AM, Shaul Kedem <shaul@yallo.com <mailto:shaul@yallo.com>> wrote: >>> >>> Webrtc boringSSL is almost identical to openssl , drop boringssl lib and try >>> >>>> On 17 Feb 2016, at 10:13 AM, Arik Halperin <arik.halperin@greenfieldtech.net <mailto:arik.halperin@greenfieldtech.net>> wrote: >>>> >>>> Hello, >>>> >>>> I’m trying to compile PJSIP With TLS and WebRTC as the media engine. I have a problem because WebRTC uses boring SSL and PJSIP uses Open SSL and these two conflict. >>>> >>>> Has anyone encountered this issue already? >>>> >>>> With Best Regards, >>>> Arik Halperin >>>> _______________________________________________ >>>> Visit our blog: http://blog.pjsip.org <http://blog.pjsip.org/> >>>> >>>> pjsip mailing list >>>> pjsip@lists.pjsip.org <mailto:pjsip@lists.pjsip.org> >>>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >>> >>> >>> _______________________________________________ >>> Visit our blog: http://blog.pjsip.org <http://blog.pjsip.org/> >>> >>> pjsip mailing list >>> pjsip@lists.pjsip.org <mailto:pjsip@lists.pjsip.org> >>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >> >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org <http://blog.pjsip.org/> >> >> pjsip mailing list >> pjsip@lists.pjsip.org <mailto:pjsip@lists.pjsip.org> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

49? no I am using the default and remove boringssl. share how you did it when you find the answer :) > On 17 Feb 2016, at 11:10 AM, Arik Halperin <arik.halperin@greenfieldtech.net> wrote: > > Tried this, didn’t help(Could be I did something wrong). Did you try it on the latest WebRTC revision? > > Arik >> On 17 Feb 2016, at 11:08 AM, Shaul Kedem <shaul@yallo.com <mailto:shaul@yallo.com>> wrote: >> >> did you set use_openssl as 1 in src/build/common.gypi, and build_ssl as 0 in src/webrtc/build/common.gypi ? >> >> from here: https://groups.google.com/forum/#!topic/discuss-webrtc/muT4irg2dvI <https://groups.google.com/forum/#!topic/discuss-webrtc/muT4irg2dvI> >> >> >>> On 17 Feb 2016, at 10:37 AM, Arik Halperin <arik.halperin@greenfieldtech.net <mailto:arik.halperin@greenfieldtech.net>> wrote: >>> >>> But how do you compile WebRTC without boring SSL? Also, there are some methods used by WebRTC in the latest versions that exist in boring SSL and not in Open SSL. >>> >>> boring SSL used to be just a subset of Open SSL, but they added stuff to it that’s not in OpenSSL. >>> >>> Arik >>>> On 17 Feb 2016, at 10:30 AM, Shaul Kedem <shaul@yallo.com <mailto:shaul@yallo.com>> wrote: >>>> >>>> Webrtc boringSSL is almost identical to openssl , drop boringssl lib and try >>>> >>>>> On 17 Feb 2016, at 10:13 AM, Arik Halperin <arik.halperin@greenfieldtech.net <mailto:arik.halperin@greenfieldtech.net>> wrote: >>>>> >>>>> Hello, >>>>> >>>>> I’m trying to compile PJSIP With TLS and WebRTC as the media engine. I have a problem because WebRTC uses boring SSL and PJSIP uses Open SSL and these two conflict. >>>>> >>>>> Has anyone encountered this issue already? >>>>> >>>>> With Best Regards, >>>>> Arik Halperin >>>>> _______________________________________________ >>>>> Visit our blog: http://blog.pjsip.org <http://blog.pjsip.org/> >>>>> >>>>> pjsip mailing list >>>>> pjsip@lists.pjsip.org <mailto:pjsip@lists.pjsip.org> >>>>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org <http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org> >>>> >>>> >>>> _______________________________________________ >>>> Visit our blog: http://blog.pjsip.org <http://blog.pjsip.org/> >>>> >>>> pjsip mailing list >>>> pjsip@lists.pjsip.org <mailto:pjsip@lists.pjsip.org> >>>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org <http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org> >>> >>> >>> _______________________________________________ >>> Visit our blog: http://blog.pjsip.org <http://blog.pjsip.org/> >>> >>> pjsip mailing list >>> pjsip@lists.pjsip.org <mailto:pjsip@lists.pjsip.org> >>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org <http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org> >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org <http://blog.pjsip.org/> >> >> pjsip mailing list >> pjsip@lists.pjsip.org <mailto:pjsip@lists.pjsip.org> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org