similar to: Asterisk 1.8.0-beta4 Now Available

The Asterisk Development Team has announced the release of Asterisk 1.8.4. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.8.4 resolves several issues reported by the community. Without your help this release would not have been possible. Thank you! Below is a sample of the issues resolved in this release: *

The Asterisk Development Team has announced the release of Asterisk 1.8.4. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.8.4 resolves several issues reported by the community. Without your help this release would not have been possible. Thank you! Below is a sample of the issues resolved in this release: *

The Asterisk Development Team has announced the release of Asterisk 1.8.0-beta1. This release marks the beginning of the testing process for the eventual release of Asterisk 1.8.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ All interested users of Asterisk are encouraged to participate in the 1.8 testing process. Please report any

The Asterisk Development Team has announced the release of Asterisk 1.8.0-beta1. This release marks the beginning of the testing process for the eventual release of Asterisk 1.8.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ All interested users of Asterisk are encouraged to participate in the 1.8 testing process. Please report any

Hi, I tried to compile asterisk-1.8.0-beta4 but after ./configure && make I've got following error: [CC] res_fax.c -> res_fax.o [LD] res_fax.o -> res_fax.so [CC] res_fax_spandsp.c -> res_fax_spandsp.o res_fax_spandsp.c:117: error: field ?fax_state? has incomplete type res_fax_spandsp.c:118: error: field ?t38_state? has incomplete type res_fax_spandsp.c: In function

The Asterisk Development Team has announced the release of Asterisk 1.6.2.18. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.6.2.18 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following is a sample of the issues resolved in this

The Asterisk Development Team has announced the release of Asterisk 1.6.2.18. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.6.2.18 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following is a sample of the issues resolved in this

The Asterisk Development Team has announced the release of Asterisk 1.8.0-beta3. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ All interested users of Asterisk are encouraged to participate in the 1.8 testing process. Please report any issues found to the issue tracker, http://issues.asterisk.org/. It is also very useful to see

The Asterisk Development Team has announced the release of Asterisk 1.8.0-beta3. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ All interested users of Asterisk are encouraged to participate in the 1.8 testing process. Please report any issues found to the issue tracker, http://issues.asterisk.org/. It is also very useful to see

2015-05-21 17:59 GMT+02:00 Jean-Denis Girard <jd.girard at sysnux.pf>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Le 21/05/2015 00:16, Joshua Colp a ?crit : > > If CCSS is needed then the only option is to use chan_sip. The > > chan_pjsip module does not implement CCSS in any way. > > Is CCSS support planned for PJSIP? chan_sip is in

Ludovic Gasc wrote: > 2015-05-21 17:59 GMT+02:00 Jean-Denis Girard <jd.girard at sysnux.pf > <mailto:jd.girard at sysnux.pf>>: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Le 21/05/2015 00:16, Joshua Colp a ?crit : > > If CCSS is needed then the only option is to use chan_sip. The > > chan_pjsip module does not implement

The Asterisk Development Team has announced the release of Asterisk 1.4.41. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.4.41 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following is a sample of the issues resolved in this

The Asterisk Development Team has announced the release of Asterisk 1.4.41. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.4.41 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following is a sample of the issues resolved in this

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 21/05/2015 00:16, Joshua Colp a ?crit : > If CCSS is needed then the only option is to use chan_sip. The > chan_pjsip module does not implement CCSS in any way. Is CCSS support planned for PJSIP? chan_sip is in "extended" state in asterisk-13, so chan_pjsip should be preferred for new installations, ri ght? Thanks, - --

Jean-Denis Girard wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi list, > > It looks like Call Completion Supplementary Services is not available > for PJSIP channels, am I right? Is there another solution? If CCSS is needed then the only option is to use chan_sip. The chan_pjsip module does not implement CCSS in any way. Cheers, -- Joshua Colp Digium,

Hi, How would I go about troubleshooting this: [Dec 24 07:15:11] WARNING[5228]: chan_sip.c:3397 retrans_pkt: Maximum retries exceeded on transmission a50346a4-bfdc32ed at 192.168.1.95 for seqno 101 (Critical Response) -- See doc/sip-retransmit.txt. [Dec 24 07:15:12] WARNING[5228]: chan_sip.c:3397 retrans_pkt: Maximum retries exceeded on transmission 90bd2c4d-aaaec88 at 192.168.1.95 for seqno 101

http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz.sig This release fixes a memory corruption bug related to MODSEQ handling in earlier v1.2 releases. Memory corruption means that it's a security bug and possibly exploitable. MODSEQ code is new in v1.2, so v1.1 and older releases are not affected. Other than that, there

http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz.sig This release fixes a memory corruption bug related to MODSEQ handling in earlier v1.2 releases. Memory corruption means that it's a security bug and possibly exploitable. MODSEQ code is new in v1.2, so v1.1 and older releases are not affected. Other than that, there

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta4.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta4.tar.gz.sig Lots of fixes since beta3, but apparently there are still a few bugs left: - Is SORT working? - APPEND seems to have problems in some setups. - Still some SEARCH TEXT problems? Or Squat indexing problems? -------------- next part -------------- A non-text attachment

I am unable to get 2.0.beta4 to compile. I get the following errors: /usr/lib64/gcc/x86_64-slackware-linux/4.3.3/../../../../lib64/libwrap.a(hosts_access.o): In function `host_match': hosts_access.c:(.text+0x625): undefined reference to `yp_get_default_domain' collect2: ld returned 1 exit status make[3]: *** [tcpwrap] Error 1 make[3]: Leaving directory