Displaying 20 results from an estimated 300 matches similar to: "Asterisk 1.8.6.0 Now Available"
2016 Jul 05
2
Function SHELL not registered
I have rebuilt a new version, making sure func_shell was selected, but I am still getting this error.
-----Original Message-----
From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of A J Stiles
Sent: maandag 4 juli 2016 09:34
To: Asterisk Users Mailing List - Non-Commercial Discussion <asterisk-users at lists.digium.com>
Subject:
2003 Mar 03
0
NZ Telepermit
DOes any of the kit from Digium kit have a NZ Telepermit for use here?
TIA
cheers
W
--
William Hamilton
TheVirtual Ltd
Wellington, New Zealand Mobile: +64 21 650936
william at thevirtual.co.nz www.thevirtual.co.nz
Making Virtual Business Reality
2005 Feb 11
2
Incorrect disk size reported at 20.0 MB
All,
I'm recently seeing an issue with how Samba is reporting
the disk space available from a NFS share. Checking the
properties from a PC system displays all mapped network
drives as having 20.0 MB size with zero free disk space
available. We updated to Samba version 3.0.11 this morning
with no change in results. I have checked the bug reports
and haven't found anything that resembles
2016 Jul 05
4
Function SHELL not registered
If you just need the name of the system it may be contained in the variable
${SYSTEMNAME}.
This is assuming you have the systemname set in asterisk.conf
https://wiki.asterisk.org/wiki/display/AST/Asterisk+Main+Configuration+File
That said, for SHELL support you probably need to set :
live_dangerously = yes
Also in your asterisk.conf
2011 Nov 10
0
DTMF issue with 1.8.6.0 and SIP Trunks [WORKING]
> I recently turned up some 1.8.6.0 call servers in productions, SIP trunks in
> routing calls to upstream carrier via SIP trunks out.? I spent a lot of time
> in the lab testing 1.8 which included heavily testing DTMF with no issues
> that came up.? It all just seemed to work fine.? But then again you can?t
> reproduce every real work scenario in the lab.
>
>
>
> I?m
2011 Sep 06
2
trying to build 1.8.6.0 on CentOS 6, problems with ptlib
I'm having annoying errors trying to get configure working.
tar xvzf /usr/local/src/asterisk-1.8.6.0.tar.gz
cd asterisk-1.8.6.0
./configure
I get complaints related to pwlib / ptlib...
checking for openr2_chan_new in -lopenr2... no
checking /root/pwlib/include/ptlib.h usability... no
checking /root/pwlib/include/ptlib.h presence... no
checking for /root/pwlib/include/ptlib.h... no
checking
2011 Sep 05
1
Variables error in 1.8.6.0.
Hello,
I have a problem with some variables in 1.8.6.0. I set on extension the
following lines:
exten => h, n, Set (CDR (LLP) = $ {CHANNEL (rtpqos, audio,
local_lostpackets)}) ; lost packets by local end **
exten => h, n, Set (CDR (PCR) = $ {CHANNEL (rtpqos, audio,
remote_lostpackets)}) ; lost packets by remote end
exten => h, n, Set (CDR (ljitt) = $ {CHANNEL (rtpqos,
2015 Feb 06
0
Asterisk 13.2.0 Now Available
The Asterisk Development Team has announced the release of Asterisk 13.2.0.
This release is available for immediate download at
http://downloads.asterisk.org/pub/telephony/asterisk
The release of Asterisk 13.2.0 resolves several issues reported by the
community and would have not been possible without your participation.
Thank you!
The following are the issues resolved in this release:
Bugs
2015 Feb 06
0
Asterisk 13.2.0 Now Available
The Asterisk Development Team has announced the release of Asterisk 13.2.0.
This release is available for immediate download at
http://downloads.asterisk.org/pub/telephony/asterisk
The release of Asterisk 13.2.0 resolves several issues reported by the
community and would have not been possible without your participation.
Thank you!
The following are the issues resolved in this release:
Bugs
2016 Jul 04
2
Function SHELL not registered
Hi all,
I am getting the following error when starting asterisk:
pbx_functions.c: Function SHELL not registered
Some of my conf files use a SHELL command, which used to work with an older version of asterisk, but now with version 13.9.1 I see this warning in the error log.
How can I register the SHELL function? From what I can find in the wiki's, it should just be available?
Best regards,
2017 Jan 24
0
hpux:- Not able to access samba4 share from windows xp client.
Hello,
I am trying to access samba4(hpux) from windows xp client but not able to
do the same.
Below are the snippet from error log.
[2017/01/23 16:45:04.327471, 3, pid=16263, effective(102, 102), real(0,
0)] ../source3/smbd/error.c:82(error_packet_set)
804 NT error packet at ../source3/smbd/trans2.c(9280) cmd=50
(SMBtrans2) NT_STATUS_NOT_FOUND
[2017/01/23 16:45:04.374366, 5,
2007 Feb 12
2
Incorrect time again with glibc 2.5
Hi ALL
rsync 2.6.9 fixed the time issue. I felt this issue is truly behind, but
then I upgraded to glibc 2.5. The time problem again started. I
recompiled rsync after upgrading glibc thinking that might be the
problem. No ways, problem still persists.
I am using Gentoo 2.6.19 + glibc 2.5.
From logs
Time: Mon Feb 12 15:46:43 EST 2007
2007/02/12 04:46:43 [16263] receiving file list
2014 Mar 10
0
AST-2014-002: Denial of Service Through File Descriptor Exhaustion with chan_sip Session-Timers
Asterisk Project Security Advisory - AST-2014-002
Product Asterisk
Summary Denial of Service Through File Descriptor Exhaustion
with chan_sip Session-Timers
Nature of Advisory Denial of Service
Susceptibility Remote
2014 Mar 10
0
AST-2014-002: Denial of Service Through File Descriptor Exhaustion with chan_sip Session-Timers
Asterisk Project Security Advisory - AST-2014-002
Product Asterisk
Summary Denial of Service Through File Descriptor Exhaustion
with chan_sip Session-Timers
Nature of Advisory Denial of Service
Susceptibility Remote
2007 Feb 18
8
DO NOT REPLY [Bug 4402] New: Incorrect time logged with glibc 2.5
https://bugzilla.samba.org/show_bug.cgi?id=4402
Summary: Incorrect time logged with glibc 2.5
Product: rsync
Version: 2.6.9
Platform: Other
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy: kilburna@iservnetworks.com
2019 Oct 18
3
Dovecot v2.3.8 released
On 2019-10-18 13:25, Tom Sommer via dovecot wrote:
> I am seeing a lot of errors since the upgrade, on multiple client
> accounts:
>
> Info: Connection closed: read(size=7902) failed: Connection reset by
> peer (UID FETCH running for 0.242 + waiting input/output for 108.816
> secs, 60 B in + 24780576+8192 B out, state=wait-output)
>
> Using NFS storage (not running with
2004 Sep 03
0
freebsd-security Digest, Vol 75, Issue 2
On Fri, 3 Sep 2004 freebsd-security-request@freebsd.org wrote:
> Send freebsd-security mailing list submissions to
> freebsd-security@freebsd.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.freebsd.org/mailman/listinfo/freebsd-security
> or, via email, send a message with subject or body 'help' to
>
2019 Mar 15
0
lua policy for Weakforce and web mail failed login attempts
The good news is I believe I got Weakforce running
1) curl -X GET http://127.0.0.1:8084/?command=ping -u wforce:ourpassword
{"status":"ok"}[
2) after running the sample for loop:
for a in {1..101}; do curl -X POST -H "Content-Type:
application/json" --data '{"login":"ahu", "remote": "127.0.0.1",
2011 Dec 15
0
Asterisk 1.8.8.0 Now Available
The Asterisk Development Team is pleased to announce the release of
Asterisk 1.8.8.0. This release is available for immediate download at
http://downloads.asterisk.org/pub/telephony/asterisk/
The release of Asterisk 1.8.8.0 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
2011 Dec 15
0
Asterisk 1.8.8.0 Now Available
The Asterisk Development Team is pleased to announce the release of
Asterisk 1.8.8.0. This release is available for immediate download at
http://downloads.asterisk.org/pub/telephony/asterisk/
The release of Asterisk 1.8.8.0 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