1.2 is considered stable upstream, and fixes many bugs over 1.0. Have been running for almost a year with no real problems.
net-misc/asterisk-1.2.9_p1: USE="alsa gtk ssl mysql postgres" in x86: 1) emerges fine 2) passes collision tests 3) starts and connects Please note that: QA Notice: USE Flag 'elibc_uclibc' not in IUSE for net-misc/asterisk-1.2.9_p1 Portage 2.1-r1 (default-linux/x86/2005.1, gcc-20050130, glibc-2.3.4.20041102-r1, 2.6.16-gentoo-r7 i686) ================================================================= System uname: 2.6.16-gentoo-r7 i686 Intel(R) Celeron(R) M processor 1.50GHz Gentoo Base System version 1.6.13 distcc 2.18.3 i386-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] app-admin/eselect-compiler: [Not Present] dev-lang/python: 2.3.5-r2, 2.4.2 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.11-r4 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i386-pc-linux-gnu" CFLAGS="-Os -mcpu=i686 -pipe" CHOST="i386-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/lib/mozilla/defaults/pref /usr/share/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/splash /etc/terminfo" CXXFLAGS="-Os -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache collision-protect distlocks metadata-transfer parallel-fetch sandbox sfperms strict test" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://mirror.datapipe.net/gentoo http://open-systems.ufl.edu/mirrors/gentoo" LANG="es_ES" LC_ALL="es_ES" LINGUAS="es" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa apm arts avi berkdb bitmap-fonts cli crypt cups dlloader dri eds emboss encode foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 imlib ipv6 isdnlog jpeg kde libg++ libwww mad mikmod motif mp3 mpeg ncurses nls ogg oggvorbis opengl oss pam pcre pdflib perl png pppd python qt3 qt4 quicktime readline reflection sdl session spell spl ssl tcpd truetype truetype-fonts type1-fonts vorbis xml2 xmms xorg xv zlib elibc_glibc input_devices_mouse input_devices_keyboard input_devices_synaptics kernel_linux linguas_es userland_GNU video_cards_i915 video_cards_i810 video_cards_i830 video_cards_vesa video_cards_fbdev" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS
I'm not as confident for net-misc/asterisk-1.2.9_p1. I'm trying to use it some time now and am forced to use the wrapper in the init.d script as it crashes now and then with SIGABRT and SIGSEGV (about once every 2 days). I tested the PC hardware several times just to be sure that it's not causing that. Unfortunately I can't go back to 1.0.x because of some new parameters I need to use in my setup. Does anyone know when the 1.2.11 ebuild will be out?
Compile asterisk with -g to get symbols, then attach gdb to the running asterisk daemon. When it eventually crashes you'll be able to get a backtrace and see what's happening. If it's a bug and consistently happens in the same place report it upstream, if not it could still be some hardware problem, just one that your testing didn't uncover.
1.2.12.1 is here, any update?
what's the status on this currently? ^.^
well 1.2.13 went stable for security, so i'm going to assume this is fixed.