[asterisk-bugs] [JIRA] (ASTERISK-28758) pjsip startup errors when using "with-ssl" configure option

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249841#comment-249841 ] 

Asterisk Team commented on ASTERISK-28758:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

> pjsip startup errors when using "with-ssl" configure option
> -----------------------------------------------------------
>
>                 Key: ASTERISK-28758
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28758
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 16.8.0
>         Environment: CentOS 6.10
>            Reporter: Patrick Wakano
>            Severity: Minor
>
> I am facing a problem when compiling Asterisk 16.8.0 in a CentOS 6 box and I wonder if someone can put some light on it.
> Log history short, install_prereq fails to install the packages (not sure how important they actually are....): speexdsp-devel, gmime-devel, uriparser-devel, iksemel-devel, uw-imap-devel, hoard
> Then, I am running the following commands to build Asterisk:
> ./configure --with-crypto --with-srtp --with-ssl
> make menuselect.makeopts
> menuselect/menuselect --enable DONT_OPTIMIZE --enable BETTER_BACKTRACES --enable MALLOC_DEBUG --disable BUILD_NATIVE --enable app_macro menuselect.makeopt
> make OPT=-fPIC
> make install
> make samples
> After this, when I start Asterisk, I get the following error with pjsip modules (also all other pjsip modules fail to load due to the res_pjsip.so dependency):
> ERROR[6253]: loader.c:2396 load_modules: Error loading module 'chan_pjsip.so': /usr/lib/asterisk/modules/chan_pjsip.so: undefined symbol: ast_sip_cli_traverse_objects
> ERROR[6253]: loader.c:2396 load_modules: Error loading module 'res_pjsip.so': /usr/lib/asterisk/modules/res_pjsip.so: undefined symbol: pjsip_tls_transport_start2
> ERROR[6253]: loader.c:2396 load_modules: Error loading module 'res_pjsip_config_wizard.so': /usr/lib/asterisk/modules/res_pjsip_config_wizard.so: undefined symbol: ast_sip_get_sorcery
> After a lot of investigation I found this post (https://asteriskfaqs.org/2018/09/25/asterisk-users/asterisk-1561-symbol-pjsip_tls_transport_start2-not-found.html) which pointed me to the with-ssl parameter.
> So if I run all previous commands, but remove the "--with-ssl" options from the configure, then I don't have the pjsip errors when I start Asterisk.
> I did compared the configure and make outputs and the only difference are below, so looks like nothing extra gets compiled when the with-ssl is used...
> With --with-ssl:
> [pjproject]  Configuring with --enable-ssl --prefix=/opt/pjproject --disable-speex-codec --disable-speex-aec --disable-bcg729 --disable-gsm-codec --disable-ilbc-codec --disable-l16-codec --disable-g722-codec --disable-g7221-codec --disable-opencore-amr --disable-silk --disable-opus --disable-video --disable-v4l2 --disable-sound --disable-ext-sound --disable-sdl --disable-libyuv --disable-ffmpeg --disable-openh264 --disable-ipp --disable-libwebrtc --without-external-pa --without-external-srtp --disable-resample --disable-g711-codec --enable-epoll
> checking for mandatory modules:  PJPROJECT CRYPTO SRTP OPENSSL... ok
> Without --with-ssl:
> [pjproject]  Configuring with --prefix=/opt/pjproject --disable-speex-codec --disable-speex-aec --disable-bcg729 --disable-gsm-codec --disable-ilbc-codec --disable-l16-codec --disable-g722-codec --disable-g7221-codec --disable-opencore-amr --disable-silk --disable-opus --disable-video --disable-v4l2 --disable-sound --disable-ext-sound --disable-sdl --disable-libyuv --disable-ffmpeg --disable-openh264 --disable-ipp --disable-libwebrtc --without-external-pa --without-external-srtp --disable-resample --disable-g711-codec --enable-epoll
> checking for mandatory modules:  PJPROJECT CRYPTO SRTP... ok
> Apparently the "with-ssl" option is not mandatory for encryption support, but somehow it affects the pjsip execution if it is used.



--
This message was sent by Atlassian JIRA
(v6.2#6252)