similar to: Registering of Asterisk against a SIP provider

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! Days ago I bought a OpenVox A400P card with a port FXS and another FXO that I am testing with my Asterisk installation in my house. I'm using Asterisk 1.4.24.1 with DAHDI Linux 2.1.0.4 and DAHDI Tools 2.1.0.2 on Debian GNU/Linux Lenny. I was reading "The future of telephony" and this [1] document looking for information about

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! I'm trying to doing a transfer from an analog extension to a SIP extension but until the moment I was not successful. I was testing both the recall key and uncomment the following lines in the features.conf file: blindxfer => #1 atxfer => *2 verifying previously that the extension uses the arguments "tT" with the Dial

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! I'm testing a telephone connected to FXS port of a Sangoma A200 card. But I'm observing that callerid is not working. The configuration that I'm using in chan_dahdi.conf is the following one: - --------------------------------------------------------------------- ;autogenerated by /usr/sbin/wancfg_dahdi do not hand edit

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! I am trying to redirect to a local extension the incoming calls that I receive to an account which I have in iptel.org, but when receiving I'm obtaining this error: alderamin*CLI> -- Executing [300 at from-internal:1] Dial("SIP/danib-089f8820", "SIP/300|30|tTrm") in new stack [Feb 19 19:22:50] WARNING[19254]:

----- Original Message ---- > From: Chris Lattner <clattner at apple.com> > To: Yuri <yuri at rawbw.com> > Cc: llvmdev at cs.uiuc.edu > Sent: Sun, February 20, 2011 3:26:35 AM > Subject: Re: [LLVMdev] Announcing: LLVM 2.9 Tentative Release Schedule > > > On Feb 19, 2011, at 8:05 PM, Yuri wrote: > > > On 02/19/2011 14:52, Yuri wrote: > >>

Hi, Im new to llvm and I'm using llvm-2.6 and I know how to extract the metadata in the stoppoints but what I'm interested in is the meta data regarding a local variable. I know that the @llvm.dgb.declare such as: call void @llvm.dbg.declare({ }* %2, { }* bitcast (%llvm.dbg.variable.type* @llvm.dbg.variable9 to { }*)) links to meta data for @llvm.dbg.variable9 which is:

Sorry for the noise. On 10/23/05, Mark Knecht <markknecht@gmail.com> wrote: > On 10/23/05, Mark Knecht <markknecht@gmail.com> wrote: > > Hi, > > Does anyone know what happened to the --debug option in winebuild? > > It seems to have disappeared in more recent versions of Wine. > > > > I am attempting to build a program that uses winebuild with

On Feb 24, 2011, at 4:05 AM, Jan Sjodin wrote: > On Feb 19, 2011, at 8:05 PM, Yuri wrote: >> >>> On 02/19/2011 14:52, Yuri wrote: >>>> Will MC path for JNI be included in 2.9? >>>> >>> >>> Sorry. I meant: Will MC path for JIT be included in 2.9? >> >> While it would be nice, it doesn't seem like anyone is working on

Hi all LLVMdev! Here is a question: I try to understand how I can realize a debugging in LLVM!? I have written a back end for my target and now I need a debug. I asked developers Chris Lattner and Robert L. Bocchino. They recommend me ask the LLVMdev. Is there a tool like "llvm-db" about Robert said? Here a mail from Robert: On Jun 29, 2009, at 17:14 PM, Robert L. Bocchino

Hi, Does anyone know what happened to the --debug option in winebuild? It seems to have disappeared in more recent versions of Wine. I am attempting to build a program that uses winebuild with the debug in a Make file. This no longer builds. What's the proper way to change the Makefile now that this option no longer exists? I know that's a vague question, but it seems that often

I''ve got an app that iterates through an array of 1000+ ActiveRecords in order to support quick AJAX filtering. When the app is running on mongrel(s), this process makes the RAM usage go through the roof (i.e., adding 50MB per iteration) and the usage never goes back down. Running on webrick, the app stabilizes at around 70MB and never goes higher no matter how many times I iterate

Hi Artem, GDB only works with native applications. If you compile your code to a native executable with -g, then debug info should work for you. However, if you've built your own backend, then you may need to add the debug info hooks etc. If you have further questions, please email the llvmdev mailing list instead of me directly, thanks! -Chris On Jun 26, 2009, at 11:11 AM,

On Feb 19, 2011, at 8:05 PM, Yuri wrote: > On 02/19/2011 14:52, Yuri wrote: >> Will MC path for JNI be included in 2.9? >> > > Sorry. I meant: Will MC path for JIT be included in 2.9? While it would be nice, it doesn't seem like anyone is working on it at the moment. -Chris

On 02/19/2011 14:52, Yuri wrote: > Will MC path for JNI be included in 2.9? > Sorry. I meant: Will MC path for JIT be included in 2.9?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! Now that I have a little more time, I was debugging my dialplan and it was of the following way: - ------------------------------------------------------------------------- ; DGB - 20090615 [macro-dial] exten => s,1,Dial(${ARG1},15) exten => s,n,Goto(s-${DIALSTATUS},1) exten => s-NOANSWER,1,Voicemail(${MACRO_EXTEN}@voicemail,u)

Hallo, LLVMdev! I have found you in LLVM Developers page (http://llvm.org/developers.cgi). First thank you for all of your work with LLVM. About: I work with the LLVM Compiler Infrastructure to implement a backend for specific processor xPEC of chip NetX (http://hilscher.com/netx.html). So C-code already possible compile to the native xPEC assembly code (works perfect! LLWM a big

Hi I was having just one more problem. I would like to find these datastructures/ primitive types etc inside a block, however the valuesymbol table is available only at a functional level. What can I do so as to get the number + type of datastructs(eg. arrays etc) inside a single block? Thanks Nipun On Fri, Oct 31, 2008 at 12:05 PM, Devang Patel <dpatel at apple.com> wrote: > Hi

Do you want to debug the native executables generated by your back-end? What debug info format your native executables support? In general, this is how it works for that case. 1. clang-cc -g generates required debug info in the .bc file. 2. The backend (llc) converts that to Dwarf (or something else as desired by that back-end). 3. Native debuggers like (gdb) understands Dwarf and provide source

hello. Today I had a problem (core dumped) in a dovecot installation update yesterday. After many hours I found that when one settings "protocol imap" the option "replication" causes (core dumped). In this server settings "replication" was removed leaving only the "protocol imap" (my error) I send my documentation error so they can add a validation and

Hi all! Is it possible to use a usb printer from a DomU? I don''t get to see any device using both lscpi and lsusb. I''m using Xen 3.0.2-2. Thanks in advance. Regards, Daniel -- Daniel Bareiro - System Administrator Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Etch - Linux user #188.598