similar to: Cisco 7905 can't register

Displaying 20 results from an estimated 1000 matches similar to: "Cisco 7905 can't register"

2008 Apr 14
4
Unable to load module chan_zap.so
I am having trouble with chan_zap.so not loading. When I load it from modules.conf, Asterisk bails out without any error message. When I load it from the console, it just says "Unable to load module chan_zap.so" no matter what verbose level I am using. dmesg says: Zaptel Version: 1.4.4 Zaptel Echo Canceller: MG2 Freshmaker version: 73 Freshmaker passed register test Module 0:
2007 Jul 13
3
asterisk-addons compilation "error: dereferencing pointer to incomplete type"
I am having trouble getting asterisk-addons 1.4.2 to compile (after a successful configure). Asterisk itself (and AsteriskGUI) compile fine. I get: cdr_addon_mysql.c: In function `handle_cdr_mysql_status': cdr_addon_mysql.c:91: error: dereferencing pointer to incomplete type cdr_addon_mysql.c:93: error: dereferencing pointer to incomplete type cdr_addon_mysql.c:95: error: dereferencing
2007 Apr 23
1
app_rxfax produces "RTP: Received packet with bad UDP checksum"
I have tried to set up app_rxfax to receive faxes over IP. I realise there are mixed stories about how reliable this is at the best of times, but at this point all I'm after is some guidance in interpreting the log below. What does "RTP: Received packet with bad UDP checksum" suggest? Here is the full log: -- Executing SetVar("SIP/0892130888-b27c",
2016 Dec 12
0
RFC: Constructing StringRefs at compile time
Well, apparently clang has clang::StringLiteral in clang/AST/Expr.h So, our options are either: Allow this name clash (obviously the namespaces don't clash, only the names) and deal with it when it's an issue (which will be limited to clang, and even then not very often), or choose a different name. Thoughts? On Mon, Dec 12, 2016 at 11:53 AM Zachary Turner <zturner at google.com>
2016 Feb 19
2
should `data` respect default.stringsAsFactors()?
Aha... Hadn't noticed that stringsAsFactors only works via as.is in read.table. Yes, the doc should probably be fixed. The code probably not -- packages loading different data sets depending on user options is an even worse idea than hav?ng the option in the first place... (I don't mean having the possibility, I mean the default.stringsAsFactor thing). In general, read.table() gets
2016 Feb 19
4
should `data` respect default.stringsAsFactors()?
Hi Peter, Sorry if I was not clear. Perhaps an example will make my point: > data(iris) > class(iris$Species) [1] "factor" > write.table(iris,'data/myiris.tab') > data(myiris) > class(myiris$Species) [1] "factor" > rm(myiris) > options(stringsAsFactors = FALSE) > data(myiris) > class(myiris$Species) [1] "factor" >
2016 Dec 12
4
RFC: Constructing StringRefs at compile time
I can. I'll whip something up today On Fri, Dec 9, 2016 at 1:18 AM Malcolm Parsons <malcolm.parsons at gmail.com> wrote: > On 2 December 2016 at 17:12, James Y Knight <jyknight at google.com> wrote: > > +1 from me for the StringLiteral proposal from a few messages back. > > Zachary, do you want to commit StringLiteral? > > -- > Malcolm Parsons >
2016 Dec 12
2
RFC: Constructing StringRefs at compile time
On Mon, Dec 12, 2016 at 1:03 PM Zachary Turner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Well, apparently clang has clang::StringLiteral in clang/AST/Expr.h > > So, our options are either: Allow this name clash (obviously the > namespaces don't clash, only the names) and deal with it when it's an issue > (which will be limited to clang, and even then not
2016 Nov 29
2
RFC: Constructing StringRefs at compile time
On 28 November 2016 at 19:30, Mehdi Amini <mehdi.amini at apple.com> wrote: > This thread started with: "There is a desire to be able to create constexpr > StringRefs to avoid static initializers for global tables of/containing > StringRefs.” > > I don’t have more information, but maybe Malcolm can elaborate? I was restating your motivation from
2016 Dec 12
0
RFC: Constructing StringRefs at compile time
> On Dec 12, 2016, at 3:45 PM, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > On Mon, Dec 12, 2016 at 1:03 PM Zachary Turner via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > Well, apparently clang has clang::StringLiteral in clang/AST/Expr.h > > So, our options are either: Allow this name
2016 Nov 29
2
RFC: Constructing StringRefs at compile time
char buffer[100]; And it also allows LIT(buffer) to compile, whereas the UDL doesn't. On Tue, Nov 29, 2016 at 9:54 AM Mehdi Amini <mehdi.amini at apple.com> wrote: > > > On Nov 29, 2016, at 9:52 AM, Malcolm Parsons <malcolm.parsons at gmail.com> > wrote: > > > > On 29 November 2016 at 17:38, Zachary Turner <zturner at google.com> wrote: > >>
2009 Aug 16
5
Plot(x,y)
Hi , I am using the plot function for some data , and the plot is coming back pure black , with scales on the side . Regards Malcolm [[alternative HTML version deleted]]
2016 Nov 29
4
RFC: Constructing StringRefs at compile time
On 29 November 2016 at 17:38, Zachary Turner <zturner at google.com> wrote: > I see, but I looked over your proposed implementation from earlier in the > thread, and if I'm not mistaken I see this: That's a different suggestion. > That said, what did you think about my other proposal of the complicated UDL > with macro? > > #define LIT(x) x_string_ref_literal >
2015 Oct 07
1
Error generated by .Internal(nchar) disappears when debugging
Malcolm, I tested the code on a clean R 3.2.0 session. Not even in RStudio, just to rule that out. > sessionInfo() R version 3.2.0 (2015-04-16) Platform: x86_64-w64-mingw32/x64 (64-bit) Running under: Windows 8 x64 (build 9200) locale: [1] LC_COLLATE=English_United Kingdom.1252 [2] LC_CTYPE=English_United Kingdom.1252 [3] LC_MONETARY=English_United Kingdom.1252 [4] LC_NUMERIC=C [5]
2016 Feb 18
2
should `data` respect default.stringsAsFactors()?
Hiya, Probably been debated elsewhere.... I note that R's `data` function does not respect default.stringsAsFactors By my lights, it should, especially as it is documented to call read.table, which DOES respect. Oh, but: http://r.789695.n4.nabble.com/stringsAsFactors-FALSE-tp921891p921893.html Compelling. I have to agree. So, I change my mind. By my lights, `data` should then be
2005 Jun 29
1
Teliax Problems
One might also conclude that during the outage the support people were focusing on getting the system back up and were not near phones. At least that is what I would bet on. Just a thought considering how most of the smaller ITSPs seem to work. Cheers, Wiley -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of
2016 Nov 28
3
RFC: Constructing StringRefs at compile time
On Mon, Nov 28, 2016 at 11:01 AM Mehdi Amini <mehdi.amini at apple.com> wrote: > On Nov 28, 2016, at 9:47 AM, David Blaikie via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > OK - good to know. (not sure we're talking about pessimizing it - just not > adding a new/possible optimization, to be clear) > > > This does not seem that clear to me. The
2016 Nov 29
2
RFC: Constructing StringRefs at compile time
On 28 November 2016 at 20:51, Zachary Turner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > The basic idea here is that you introduce a StringLiteral class and anywhere > you want to use a global constructor, you make sure to declare a constexpr > array instead of a normal array, and you make it of type StringLiteral. I prefer constexpr llvm_strlen() over StringLiteral because
2005 Apr 07
2
half-normal residual plots
Hi all, I am trying to produce a half-normal plot of residuals from a GLM. I have found the qqnorm function for producing a normal plot but can't figure out how to produce a half-normal. Can anyone help with this? Thanks Malcolm ---------------------- MJ Price, Social Medicine epmjp at bristol.ac.uk
2016 Nov 28
3
RFC: Constructing StringRefs at compile time
The fact that the templatized constructor falls down because of the possibility of initializing StringRef with a stack-allocated char array kills that idea in my mind. I feel like the only two reasonable solutions are 1) allow UDL for this case, document that this is an exception and that UDLs are still not permitted anywhere else, and require (by policy, since I don't know of a way to have