similar to: asterisk@home basic

Displaying 20 results from an estimated 7000 matches similar to: "asterisk@home basic"

2008 Jun 11
2
time on asterisk
Hi, I'm using gotoiftime on asterisk, but it seems  there is a difference between the asterisk time and the system time. could it be because i adjusted the system timezone on my linux? do asterisk not detect the change of timezone on the system? How can I fix this prob? Regards, nhadie -------------- next part -------------- An HTML attachment was scrubbed... URL:
2012 Jan 03
0
fixme:ntdll:find_reg_tz_info
Date - 28-Dec-2011 22:16 After see many sites about Timezone, i tried on tzselect. And i did it change in my date to be in UTC - GST mode. sudo date sudo ls /usr/share/zoneinfo/America/ | grep Sao_Paulo sudo ln -s /usr/share/zoneinfo/America/Sao_Paulo /etc/localtime sudo date sudo /usr/bin/tzselect select 11) none - I want to specify the time zone using the Posix TZ format. sudo /usr/bin/tzselect
2018 Jun 22
2
Pigeonhole extdata repo?
Pigeonhole download page has links for extdata plugin up to v0.4 but nothing more and no link to the master repository https://pigeonhole.dovecot.org/download.html I want to use with dovecot 2.3.2rc1 but v0.4 won't compile with it. Thanks for helping ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's
2017 Oct 24
1
[RFC] virtio-iommu version 0.5
Hi Jean, On Mon Oct 23, 2017 at 10:32:41AM +0100, Jean-Philippe Brucker wrote: > This is version 0.5 of the virtio-iommu specification, the paravirtualized > IOMMU. This version addresses feedback from v0.4 and adds an event virtqueue. > Please find the specification, LaTeX sources and pdf, at: > git://linux-arm.org/virtio-iommu.git viommu/v0.5 >
2007 Jun 22
1
Btrfs v0.4 available (warning: disk format change)
Hello everyone, I wasn't planning on sending out v0.4 until ENOSPC was fixed, but Frank Groeneveld narrowed down a bug with the file data checksumming code on highmem 32bit machines. Basically the way I was using cryptomgr made it incorrectly calculate checksums on highmem pages. So to simplify things, I've switched over to plain libcrc32c. Anyone running on a 32 bit with highmem is
2007 Jun 22
1
Btrfs v0.4 available (warning: disk format change)
Hello everyone, I wasn't planning on sending out v0.4 until ENOSPC was fixed, but Frank Groeneveld narrowed down a bug with the file data checksumming code on highmem 32bit machines. Basically the way I was using cryptomgr made it incorrectly calculate checksums on highmem pages. So to simplify things, I've switched over to plain libcrc32c. Anyone running on a 32 bit with highmem is
2018 Jun 25
2
Pigeonhole extdata repo?
thanks you AKi for alway responding! >> Pigeonhole download page has links for extdata plugin up to v0.4 but >> nothing more and no link to the master repository >> >> https://pigeonhole.dovecot.org/download.html >> >> I want to use with dovecot 2.3.2rc1 but v0.4 won't compile with it. > > Seems to need v0.5 for it. What are you using it for? For a
2017 Oct 24
2
[RFC] virtio-iommu version 0.5
Hi Jean, Thanks for your reply. On Tue Oct 24, 2017 at 09:37:12AM +0100, Jean-Philippe Brucker wrote: > Hi Linu, > > On 24/10/17 07:27, Linu Cherian wrote: > > Hi Jean, > > > > On Mon Oct 23, 2017 at 10:32:41AM +0100, Jean-Philippe Brucker wrote: > >> This is version 0.5 of the virtio-iommu specification, the paravirtualized > >> IOMMU. This version
2017 Oct 24
2
[RFC] virtio-iommu version 0.5
Hi Jean, Thanks for your reply. On Tue Oct 24, 2017 at 09:37:12AM +0100, Jean-Philippe Brucker wrote: > Hi Linu, > > On 24/10/17 07:27, Linu Cherian wrote: > > Hi Jean, > > > > On Mon Oct 23, 2017 at 10:32:41AM +0100, Jean-Philippe Brucker wrote: > >> This is version 0.5 of the virtio-iommu specification, the paravirtualized > >> IOMMU. This version
2017 Aug 04
7
[RFC] virtio-iommu version 0.4
This is the continuation of my proposal for virtio-iommu, the para- virtualized IOMMU. Here is a summary of the changes since last time [1]: * The virtio-iommu document now resembles an actual specification. It is split into a formal description of the virtio device, and implementation notes. Please find sources and binaries at [2]. * Added a probe request to describe to the guest different
2017 Aug 04
7
[RFC] virtio-iommu version 0.4
This is the continuation of my proposal for virtio-iommu, the para- virtualized IOMMU. Here is a summary of the changes since last time [1]: * The virtio-iommu document now resembles an actual specification. It is split into a formal description of the virtio device, and implementation notes. Please find sources and binaries at [2]. * Added a probe request to describe to the guest different
2017 Sep 12
1
[RFC] virtio-iommu version 0.4
Hi jean, On 04/08/2017 20:19, Jean-Philippe Brucker wrote: > This is the continuation of my proposal for virtio-iommu, the para- > virtualized IOMMU. Here is a summary of the changes since last time [1]: > > * The virtio-iommu document now resembles an actual specification. It is > split into a formal description of the virtio device, and implementation > notes. Please find
2017 Oct 25
2
[RFC] virtio-iommu version 0.5
Hi Jean, On Tue Oct 24, 2017 at 10:28:59PM +0530, Linu Cherian wrote: > Hi Jean, > Thanks for your reply. > > On Tue Oct 24, 2017 at 09:37:12AM +0100, Jean-Philippe Brucker wrote: > > Hi Linu, > > > > On 24/10/17 07:27, Linu Cherian wrote: > > > Hi Jean, > > > > > > On Mon Oct 23, 2017 at 10:32:41AM +0100, Jean-Philippe Brucker wrote:
2017 Oct 23
3
[RFC] virtio-iommu version 0.5
This is version 0.5 of the virtio-iommu specification, the paravirtualized IOMMU. This version addresses feedback from v0.4 and adds an event virtqueue. Please find the specification, LaTeX sources and pdf, at: git://linux-arm.org/virtio-iommu.git viommu/v0.5 http://linux-arm.org/git?p=virtio-iommu.git;a=blob;f=dist/v0.5/virtio-iommu-v0.5.pdf A detailed changelog since v0.4 follows. You can find
2017 Oct 23
3
[RFC] virtio-iommu version 0.5
This is version 0.5 of the virtio-iommu specification, the paravirtualized IOMMU. This version addresses feedback from v0.4 and adds an event virtqueue. Please find the specification, LaTeX sources and pdf, at: git://linux-arm.org/virtio-iommu.git viommu/v0.5 http://linux-arm.org/git?p=virtio-iommu.git;a=blob;f=dist/v0.5/virtio-iommu-v0.5.pdf A detailed changelog since v0.4 follows. You can find
2013 Mar 29
2
problem with ices 0.4 and playlist scripting
hello all, I have been using ices V0.4 successfully with the built-in playlist handler for a couple of years now, but I recently decided I?d like a bit more control over what is played and when. I?ve read as much as I could find on the internet about doing this. I?ve written a php script to connect to, and query a MySQL database for the tracks to play. When I run the php script manually from
2004 Mar 02
1
VP3 Format Doc, v0.4
Hi, Check it out-- another update in the space of a week: http://home.pcisys.net/~melanson/codecs/vp3-format.txt v0.4: March 2, 2004 - renamed and expanded section "Initializing The Quantization Matrices" - outlined section "Reconstructing The Frame" - moved Theora Differences Appendix to its own section entitled "Theora Specification" - added Appendix:
2004 Sep 14
0
Tip: using icecast in chroot mode may break timestamp in access.log
Hi all, Just thought I'd share this little bit of information. If you're running Icecast in a chroot jail the timestamps in the access.log file will almost certainly be in UTC times. If you want local timezone timestamps you need to make sure the file /etc/localtime is in <chrootdir>/etc/localtime. If you use a different timezone settings (generated using tzselect for example).
2018 Mar 05
1
pigeonhole 0.4.22 with sieve_before script crashes
Op 3/3/2018 om 6:29 PM schreef Stephan Bosch: > Op 3/3/2018 om 6:17 PM schreef Jan: >>>>> We're looking into it. >>>> Right, this is not reproducible in the test suite, but I can reproduce >>>> it when I replicate your setup. >>> I created a special test suite that reproduces the problem reliably. >>> This occurs when Sieve
2005 May 06
1
ZapBarge a PRI DDI
I'm using a TE405p with all four spans enabled, two configured as pri_cpe and two as pri_net, the asterisk is sitting between our ISDN (UK BT EuroISDN30) and our phone system. We have 200 DDI numbers on the ISDN's and I need to give one of our clients dial-in access to be able to monitor calls we handle on their behalf. I've got ZapBarge working but I need to restrict the client