similar to: compiling Asterisk

I am trying to transition an application over from a FreePbx box to a Standard build Asterisk 11.6 box. I have a job that creates a call file and plays a sound file. If it detects a voicemail, then it plays it, waits 1 second and replays it. The FreePbx box works fine but the Standard Asterisk build is dropping the call during the first Voicemail playback and it does not leave the voicemail.

I have setup a trunk on Asterisk 11.7 to an Avaya Session Manager. Every time I try to send a call over it, the call gets rejected. Here is the sip debug trace. Could anyone tell me what may be going wrong? nxdasterisk-2*CLI> [Apr 23 08:20:59] WARNING[19047]: pbx_spool.c:309 safe_append: Unable to set utime on /var/spool/asterisk/outgoing/scott.call: Operation not permitted Audio is at 18380

I have a need to issue a dial command to a number: same => n,Dial(${DIALGROUP1},${TIMER1},t) After a number of seconds, let's say 10 seconds. I want to dial another set of numbers while continuing to ring, or interrupting the first group of numbers. same => n,Dial(${DIALGROUP2},${TIMER1},t) Is there a way to do this without interrupting the first call? Thanks, Scott Haley If you

I have a SIP trunk from my Asterisk server to an Avaya CM server. If I place calls inbound, everything works fine. If I place calls outbound, originating from the Asterisk box, everything works fine (I have done this with the use of the .call files). If I setup an extension with the findme-followme feature and have it try to hair-pin a call back out the same trunk to the Avaya, I get a

I have a situation that I need help with. I have 2 phone systems, 1 Asterisk and 1 Avaya. All voicemail is kept on the Avaya system. Whenever a call comes into an extension that the Asterisk server owns, I re-direct it to a different number that is owned by the Avaya System. If that Avaya extension does not answer it, I send it to the voicemail on the Avaya Messaging system for the extension that

I'm new to the CentOS arena and I'm curious as to what virtualization products are preferred? The two main ones that I know of are Xen and VMWare. VMWare seems to be the most capable inre: number and size of vm's allowed. When looking at Xen it appears that since Citrix acquired them the free version is cripple-ware and is very restrictive. Thanks in advance for any information.

You could use MTR command. Its a trace route improved. Marlon Araujo > On Jan 20, 2015, at 08:59, asterisk-users-request at lists.digium.com wrote: > > Send asterisk-users mailing list submissions to > asterisk-users at lists.digium.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.digium.com/mailman/listinfo/asterisk-users > or,

Hi Guys, I was wondering what our next steps should be to solve the slow write times. Recently I was debugging a large code and writing a lot of output at every time step. When I tried writing to our gluster disks, it was taking over a day to do a single time step whereas if I had the same program (same hardware, network) write to our nfs disk the time per time-step was about 45 minutes.

Are you sure using conv=sync is what you want? I normally use conv=fdatasync, I'll look up the difference between the two and see if it affects your test. -b ----- Original Message ----- > From: "Pat Haley" <phaley at mit.edu> > To: "Pranith Kumar Karampuri" <pkarampu at redhat.com> > Cc: "Ravishankar N" <ravishankar at redhat.com>,

On Mon, Jun 26, 2017 at 7:40 PM, Pat Haley <phaley at mit.edu> wrote: > > Hi All, > > Decided to try another tests of gluster mounted via FUSE vs gluster > mounted via NFS, this time using the software we run in production (i.e. > our ocean model writing a netCDF file). > > gluster mounted via NFS the run took 2.3 hr > > gluster mounted via FUSE: the run took

Hi, Today we experimented with some of the FUSE options that we found in the list. Changing these options had no effect: gluster volume set test-volume performance.cache-max-file-size 2MB gluster volume set test-volume performance.cache-refresh-timeout 4 gluster volume set test-volume performance.cache-size 256MB gluster volume set test-volume performance.write-behind-window-size 4MB gluster

Hi Ben, Sorry this took so long, but we had a real-time forecasting exercise last week and I could only get to this now. Backend Hardware/OS: * Much of the information on our back end system is included at the top of http://lists.gluster.org/pipermail/gluster-users/2017-April/030529.html * The specific model of the hard disks is SeaGate ENTERPRISE CAPACITY V.4 6TB

On Fri, Jun 23, 2017 at 9:10 AM, Pranith Kumar Karampuri < pkarampu at redhat.com> wrote: > > > On Fri, Jun 23, 2017 at 2:23 AM, Pat Haley <phaley at mit.edu> wrote: > >> >> Hi, >> >> Today we experimented with some of the FUSE options that we found in the >> list. >> >> Changing these options had no effect: >> >>

On Fri, Jun 23, 2017 at 2:23 AM, Pat Haley <phaley at mit.edu> wrote: > > Hi, > > Today we experimented with some of the FUSE options that we found in the > list. > > Changing these options had no effect: > > gluster volume set test-volume performance.cache-max-file-size 2MB > gluster volume set test-volume performance.cache-refresh-timeout 4 > gluster

Hi All, Decided to try another tests of gluster mounted via FUSE vs gluster mounted via NFS, this time using the software we run in production (i.e. our ocean model writing a netCDF file). gluster mounted via NFS the run took 2.3 hr gluster mounted via FUSE: the run took 44.2 hr The only problem with using gluster mounted via NFS is that it does not respect the group write permissions which

Andrew Haley wrote: > Nick Lewycky wrote: >> 2009/6/30 Andrew Haley <aph at redhat.com <mailto:aph at redhat.com>> >> >> Nick Lewycky wrote: >> > I'm seeing this new build failure, starting some time yesterday on >> ARM: >> >> Yes. It's just a matter of defining __sync_val_compare_and_swap_4: >> >>

Hi Soumya, I just noticed some of the notes at the bottom. In particular * Till glusterfs-3.7, gluster-NFS (gNFS) gets enabled by default. The only requirement is that kernel-NFS has to be disabled for gluster-NFS to come up. Please disable kernel-NFS server and restart glusterd to start gNFS. In case of any issues with starting gNFS server, please look at

Hi All, A follow-up question. I've been looking at various pages on nfs-ganesha & gluster. Is there a version of nfs-ganesha that is recommended for use with glusterfs 3.7.11 built on Apr 27 2016 14:09:22 CentOS release 6.8 (Final) Thanks Pat On 07/05/2017 11:36 AM, Pat Haley wrote: > > Hi Soumya, > > (1) In

Hi, On 07/07/2017 06:16 AM, Pat Haley wrote: > > Hi All, > > A follow-up question. I've been looking at various pages on nfs-ganesha > & gluster. Is there a version of nfs-ganesha that is recommended for > use with > > glusterfs 3.7.11 built on Apr 27 2016 14:09:22 > CentOS release 6.8 (Final) For glusterfs 3.7, nfs-ganesha-2.3-* version can be used. I see

Hi Soumya, (1) In http://mseas.mit.edu/download/phaley/GlusterUsers/TestNFSmount/ I've placed the following 2 log files etc-glusterfs-glusterd.vol.log gdata.log The first has repeated messages about nfs disconnects. The second had the <fuse_mnt_direcotry>.log name (but not much information). (2) About the gluster-NFS native server: do you know where we can find documentation on