[asterisk-dev] Asterisk now available with bundled pjproject!

George Joseph george.joseph at fairview5.com
Fri Mar 18 08:50:48 CDT 2016


On Fri, Mar 18, 2016 at 6:08 AM, Ross Beer <ross.beer at outlook.com> wrote:

> Hi,
>
> This is now working as expected, however the build failed as the 'bzip2'
> and 'patch' package needed to be installed. Could this be added to the
> 'install_prereq' script to negate the issue?
>

​Got it.  Thanks for the feedback!​




>
> Regards,
>
> Ross
>
> ------------------------------
> From: george.joseph at fairview5.com
> Date: Wed, 16 Mar 2016 14:27:10 -0600
>
> To: asterisk-dev at lists.digium.com
> Subject: Re: [asterisk-dev] Asterisk now available with bundled pjproject!
>
>
>
> On Wed, Mar 16, 2016 at 10:25 AM, George Joseph <
> george.joseph at fairview5.com> wrote:
>
>
>
> On Wed, Mar 16, 2016 at 9:30 AM, Ross Beer <ross.beer at outlook.com> wrote:
>
>
> Package matching libsrtp-devel-1.4.4-10.20101004cvs.el7.x86_64 already
> installed.
>
> pjproject builds correct with the following:
>
> ./configure CFLAGS="-DNDEBUG" --prefix=/usr --libdir=/usr/lib64
> --enable-epoll --enable-shared --disable-video --disable-sound
> --disable-opencore-amr
>
>
>
> ​You're compiling with pjproject's internal libsrtp implementation.  Try
> with --with-external-srtp and see what happens.
> libsrtp-devel in Fedora is already at 1.5.4 so maybe it's a version thing.
>   There was a ticket open with pjproject for this exact problem but it was
> implemented 2 years ago.  Maybe it's not quite right.  I'll check.
>
>
> ​I just tested on my CentOS7 VM with the same version of libsrtp and
> didn't have any problems.  Maybe try a distclean and reconfigure?
>
>
>
>
>
>
>
> ------------------------------
> From: george.joseph at fairview5.com
> Date: Wed, 16 Mar 2016 09:09:30 -0600
>
> To: asterisk-dev at lists.digium.com
> Subject: Re: [asterisk-dev] Asterisk now available with bundled pjproject!
>
>
>
> On Wed, Mar 16, 2016 at 8:47 AM, Ross Beer <ross.beer at outlook.com> wrote:
>
> After running install_prereq I get the following error:
>
>
> [GENERATE] libasteriskpj.exports
>    [LD] libasteriskpj.o -> libasteriskpj.so.2
>    [LN] libasteriskpj.so.2 -> libasteriskpj.so
>    [LD] abstract_jb.o acl.o adsi.o alaw.o aoc.o app.o ast_expr2.o
> ast_expr2f.o asterisk.o astfd.o astmm.o astobj2.o astobj2_container.o
> astobj2_hash.o astobj2_rbtree.o audiohook.o autochan.o autoservice.o
> backtrace.o bridge.o bridge_after.o bridge_basic.o bridge_channel.o
> bridge_roles.o bucket.o callerid.o ccss.o cdr.o cel.o channel.o
> channel_internal_api.o chanvars.o cli.o codec.o codec_builtin.o config.o
> config_options.o core_local.o core_unreal.o crypt.o data.o datastore.o db.o
> devicestate.o dial.o dns.o dnsmgr.o dsp.o endpoints.o enum.o event.o
> features.o features_config.o file.o fixedjitterbuf.o format.o
> format_cache.o format_cap.o format_compatibility.o frame.o framehook.o
> fskmodem.o global_datastores.o hashtab.o heap.o http.o image.o
> indications.o io.o jitterbuf.o json.o loader.o lock.o logger.o manager.o
> manager_bridges.o manager_channels.o manager_endpoints.o manager_mwi.o
> manager_system.o max_forwards.o md5.o media_index.o message.o mixmonitor.o
> named_acl.o netsock.o netsock2.o optional_api.o parking.o pbx.o pbx_app.o
> pbx_builtins.o pbx_functions.o pbx_hangup_handler.o pbx_switch.o
> pbx_timing.o pbx_variables.o pickup.o plc.o poll.o presencestate.o
> privacy.o rtp_engine.o say.o sched.o sdp_srtp.o security_events.o sem.o
> sha1.o sip_api.o slinfactory.o smoother.o sorcery.o sounds_index.o srv.o
> stasis.o stasis_bridges.o stasis_cache.o stasis_cache_pattern.o
> stasis_channels.o stasis_endpoints.o stasis_message.o
> stasis_message_router.o stasis_system.o stdtime/localtime.o strcompat.o
> strings.o stun.o syslog.o taskprocessor.o tcptls.o tdd.o term.o test.o
> threadpool.o threadstorage.o timing.o translate.o udptl.o ulaw.o uri.o
> utils.o uuid.o version.o xml.o xmldoc.o   -> asterisk
> ./libasteriskpj.so: undefined reference to `srtp_deinit'
> collect2: error: ld returned 1 exit status
> make[1]: *** [asterisk] Error 1
> make: *** [main] Error 2
>
>
>
> ​Ok, that's weird.  I take it you have libsrtp-devel installed
> (install_prereq should have done it)?  What version?
> Can you build ​pjproject from source normally?  When you do, do you use
> --with-external-srtp?
>
>
>
>
>
>
>
> ------------------------------
> From: george.joseph at fairview5.com
> Date: Wed, 16 Mar 2016 07:37:44 -0600
> To: asterisk-dev at lists.digium.com
> Subject: Re: [asterisk-dev] Asterisk now available with bundled pjproject!
>
>
>
>
> On Wed, Mar 16, 2016 at 5:41 AM, Ross Beer <ross.beer at outlook.com> wrote:
>
> Hi,
>
> I just attempted to install with the bundled pjproject however the
> following error stopped the build:
>
> Generating embedded module rules ...
>    [CC] astdb2sqlite3.c -> astdb2sqlite3.o
>    [LD] astdb2sqlite3.o db1-ast/libdb1.a -> astdb2sqlite3
>    [CC] astdb2bdb.c -> astdb2bdb.o
>    [LD] astdb2bdb.o db1-ast/libdb1.a -> astdb2bdb
> [pjproject]  Making dependencies
> [pjproject]  Compiling libs
> [pjproject]  Generating symbols
> [pjproject]  Compiling apps
> [pjproject]  Compiling python bindings
> make[2]: *** [source/pjsip-apps/src/python/build/_pjsua.so] Error 1
> make[1]: *** [pjproject] Error 2
> make: *** [third-party] Error 2
>
>
> ​I'll bet you don't have the python development libraries installed.  The
> install_prereq script was updated to include python-devel or python-dev
> depending on the distribution.​
>
>
> Kind regards,
>
> ROss
>
> ------------------------------
> From: george.joseph at fairview5.com
> Date: Mon, 7 Mar 2016 12:28:23 -0700
> To: asterisk-dev at lists.digium.com; asterisk-users at lists.digium.com
> Subject: [asterisk-dev] Asterisk now available with bundled pjproject!
>
>
> The current Asterisk 13 and master git branches have a new feature that
> will be included in 13.8.0:  The ability to compile and run Asterisk with a
> bundled version of pjproject.
> ​​
>
> Why would you want to do this?  Several reasons:
>
>    - Predictability:  When built with the
>    ​bundled
>     pjproject, you're always certain of the version you're running
>    against, no matter where it's installed.
>    - Scalability:  The default pjproject configuration is optimized for
>    client applications. The bundled version's configuration is optimized for
>    server use.
>    - Usability:  Several feature patches, which have been submitted
>    upstream to pjproject but not yet released, have been included in the
>    bundled version.
>    - Safety:  If a security or critical issue is identified in pjproject,
>    it can be patched and made available with a new release of Asterisk instead
>    of
>    ​having to ​
>    waiting for a new release of pjproject
>    ​​
>    .
>    - Maintainability:  You don't need to build and install separate
>    packages.
>    - Supportability:  When asking others for help, there's no question
>    about which version of pjproject you're using and what options it was
>    compiled with.
>    - Compatibility:  This is especially important from a development
>    perspective because it means we can be sure that new pjproject APIs that
>    have been introduced
>    ​,​
>    or old ones that have been deprecated
>    ​,​
>    are handled and tested appropriately in Asterisk.
>    - Reliability:  You can be sure that Asterisk was tested against the
>    bundled version.
>
>
> So now that you're sold, here's how you use it:
>
> All you have to do is add the "--with-pjproject-bundled" option to your
> ./configure command line and remove any other "--with-pjproject" option you
> may have specified.  The configure and make processes will download the
> correct version of pjproject, patch it, configure it, build it and finally
> link Asterisk to it statically.  No changes in runtime configuration are
> required.
>
> Still not sold?  The default behavior hasn't changed so as long as you
> haven't specified "--with-pjproject-bundled", your build and deploy process
> remains as is.
>
> PLEASE TRY THIS!!  I'd love some feedback BEFORE 13.8.0 is released.
>
>
> -- _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> asterisk-dev mailing list To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-dev
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>
>
>
> -- _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> asterisk-dev mailing list To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-dev
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>
>
>
> -- _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> asterisk-dev mailing list To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-dev
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>
>
>
>
> -- _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> asterisk-dev mailing list To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-dev
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20160318/10e09a9f/attachment-0001.html>


More information about the asterisk-dev mailing list