similar to: perl agi : get_variable problem

I am originating a call to a Local channel using an Originate Action: Action: Originate Channel: Local/dial at outdial Context: outdial Exten: answer Priority: 1 Timeout: 45000 ActionID: some_id In my dialplan, I have this: [outdial] exten => dial,1,Dial(${DIAL_STRING}, ${DIAL_TIMEOUT}) exten => dial,n,NoOp(Dial Status = ${DIALSTATUS}) exten =>

First off, I also posted this on the digium forums so if anyone here also reads those, sorry for the cross-post. When I place an outbound call using SIP to my cell phone, asterisk immediately starts processing the dialplan without waiting for the call to be answered. We could handle this on DAHDI using callprogress, but I don't know of a similar setting for SIP. Here is the contents of

I'm using the Dial application in the extensions file with the G option to execute an AGI script after the Dial (I need to track the call status) as follows: exten => _X.,3, Dial({DIAL_STRING},,G(_X.^4)) exten => _X.,4, Answer() exten => _X.,5,AGI,agiScript.php The problem is that testing between two internal phones (with two ATA) I loose the audio when I include the G option in the

I got four phones: 601 is a SIP phone (no brand) 615 is Snom 190 621 is a Grand stream 628 is a remote SIP phone (no brand) 601, 615, 628 can call each other without any problems 621 used to be able to call remote 628, but after upgrade to CVS Head Nov. 11 the remote party cannot hear me. 615 never could call remote 628, both party hear nothing. 601 can always call 628 [Oct 16 00:52:13] --

Hello, Anyone know how to set the "To:" in an invite for PJSIP to custom settings. I got the "from" to be the way I need it. From: <sip:e04f43a2ed59 at xaccel.net;tag=44l1nRmW2 To: "TEST" <sip:5tf2f2s0rbtdj-20d14fl6n65t0o-0u03 at 34.221.174.202> I have tried a lot of changes to get to this but nothing works. I am getting this From: sip:109643183 at

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Either Xen, or the Dom0 kernel (I guess you know better) spits out error messages about ata4 containing "status: { DRDY ERR }" (similar error can be found googling DRDY ERR). I'm not putting the whole error message here because I couldn't copy-paste the message at the booting stage. I'm adding the autoconfigured menu

Hi, I wonder if there is specific requirement or restriction for the decoder in order to be consider "Vorbis" compliant (or let's say, to be a "correct" vorbis decoder). I am experimenting with integerized libvorbis and the decoder delivers the audio data as following, (and compare with the floating point version below). $ tail audioout-int.txt 0290670 025e 085c 02cf 0895

I have been going crazy with this also since Sat. Our server was working perfectly with BV but will now not place calls to BV. Incoming from BV works fine. I felt sad rebooting it today, it had been running for almost 200 days! Here is my error message from the console... Notice I am running today's CVS Connected to Asterisk CVS-03/08/05-14:32:39 currently running on com (pid = 1624)

Hi everyone, I am currently in the process of setting up a firewall/access point DomU and I would like to know if there is any way to run a linux kernel 2.4(.34) based system as a DomU. The primary reason for this is that I want to run IPCop on such a kernel, but also that I consider kernel 2.4 based systems to be more suitable for some applications, especially for use as a firewall.

I''ve just finished installing onto an OCZ Agilent v2 SSD with btrfs as filesystem. However to my surprise I''ve hit an ENOSPC condition one one of the partitions within less than a day of uptime, while the filesystem on that partition only reported 50% to be in use, which is far from the 75% limit people mention on the ML. Note that this occurs using a vanilla 2.6.32-rc5 kernel

Hi everyone, I''ve pushed out my current kernel git tree to a new branch called integration-test. This is meant for integration testing only and should not be run by anyone who doesn''t love crashes. I''ve pulled together a lot of important work from a lot of different people. It includes: The new inode number allocator Delayed inode and directory item updates Scrub,

Hello to everyone. I'm trying to install both dotnetfx 1.2.3 in order to check to run a special program for windows xp we use in our office. First of all I installed dotnet 2, 3. and the installation worked great. The problem is to install dotnet 1.1. When I run winetricks I receive this error message. lorenzo at lorenzo-virtual-machine:~/.cache/winetricks/dotnet11$ winetricks Executing

Hello everyone, please I need your help. To reproduce my problem I created simple pass for backends (TestPass.cpp in attached files). That pass I call from Mips backend in this way (MipsTargetMachine.cpp): bool MipsPassConfig::addPreRegAlloc() { addPass(createTestPass()); return false; } The problem becomes, when I am trying compile file ldtoa.ll (in attached files). Compiling

I should mention a couple of useful self-explanatory LLVM flags for triage: -enable-misched=false -verify-misched -Andy On Oct 15, 2013, at 4:43 PM, Eric Christopher <echristo at gmail.com> wrote: > Grats on the work, a long time coming! > > Beware the incoming register allocation bugs ;) > > -eric > > On Tue, Oct 15, 2013 at 4:33 PM, Andrew Trick <atrick at

Hi Karthik, thanks for taking a look at this. I'm not working with gluster long enough to make heads or tails out of the logs. The logs are attached to this mail and here is the other information: # gluster volume info home Volume Name: home Type: Replicate Volume ID: fe6218ae-f46b-42b3-a467-5fc6a36ad48a Status: Started Snapshot Count: 1 Number of Bricks: 1 x 3 = 3 Transport-type: tcp

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

Hi, Thanks alot to Mark and his team for bringing a great voip project and a great conference. I am a developper in the *BSD projects and will go back to these with the intention to help in providing a better availability of '*' for these OS's and also working the zaptel4BSD. cheers and see you soon. Julien