similar to: clear SIP channel

Displaying 20 results from an estimated 2000 matches similar to: "clear SIP channel"

2005 Sep 15
0
SIP rogue channel
Hi, one of the sip-extensions we created always returns busy when someone tries to call the phone. The extension itself can place calls. We're using snom360 phones with the latest firmware. On every one of those phones when we register with the sip-extension, we've experienced the same problem. This is the output from sip show channels: Peer User/ANR Call ID Seq
2006 Jan 24
1
need help asterisk and AS5300
hi All Any body already setup asteriks call routing to Cisco AS5300 with SIP Server ? i need informations sample config for that, or can show how to route docs . thanks Dirgan --------------------------------- Meet your soulmate! Yahoo! Asia presents Meetic - where millions of singles gather -------------- next part -------------- An HTML attachment was scrubbed... URL:
2006 Jan 31
5
Queue() with timeout=0
Hello, i've recently switched over from 1.0.9 to 1.2.3. I've experienced some (to me) weird behaviour. This is the config for an example queue.conf: [654] wrapuptime=30 timeout=20 strategy=ringall retry=5 queue-youarenext=queue-youarenext queue-thereare=queue-thereare queue-thankyou=queue-thankyou queue-callswaiting=queue-callswaiting music=default monitor-join=yes monitor-format=
2006 Apr 20
3
still some moh troubles
Hi, After following the suggestions on the mailing lists and the wiki I'm still experiencing choppy moh. The song plays but with frequent noise parts. - I'm using asterisk 1.2.4 on our production server and 1.2.7 on the test server. - native moh with .gsm and .pcm formats (according to http://astrecipes.net/?n=152) - compiled ztdummy as a timing source any pointers on how to dig deeper
2015 Oct 09
0
[PATCH 1/2] kvm/x86: Hyper-V synthetic interrupt controller
From: Andrey Smetanin <asmetanin at virtuozzo.com> Synic is a lapic extension, which is controlled via MSRs and maintains for each vCPU - 16 synthetic interrupt "lines" (SINT's); each can be configured to trigger a specific interrupt vector optionally with auto-EOI semantics - a message page in the guest memory with 16 256-byte per-SINT message slots - an event
2002 Apr 25
1
understanding and resolving seg faults
Dear r-devel, I am mutating rpart to do calculations on trees. I am trying to extract information from the tree. However, I got a seg. fault. This is the offending line in "rpmatrix.c": deltaI[0][0] = spl->improve; (Commenting it out cures the seg fault) I would like some advice on how to debug this. I have allocated memory with calloc and deltaI[0][0] should be
2018 Jun 05
0
[PATCH v2 1/2] compiler-gcc.h: add gnu_inline to all inline declarations
On Tue, 2018-06-05 at 10:23 -0700, Joe Perches wrote: > Perhaps these are simpler as > > #define __inline__ inline > #define __inline inline Currently, there are these uses of inline variants in the kernel $ git grep -w inline | wc -l 68410 $ git grep -w __inline__ | wc -l 503 $ git grep -w __inline | wc -l 57 So it seems it's also reasonable to sed all uses of __inline to
2004 Jun 17
2
using "= matrix (...)" in .C calls
Dear R-devel, I am trying to alter rpart so that it makes additional calculations when growing the tree. In the "rpart.s" there is a call to the C routine: rp <- .C("s_to_rp2", as.integer(nobs), as.integer(nsplit), as.integer(nodes), as.integer(ncat),
2015 Sep 11
1
Dovecot CalDAV server
* Niklaas Baudet von Gersdorff <niklaas at kulturflatrate.net>: > On Fri, 11 Sep 2015 00:43:16 +0300 > Timo Sirainen <tss at iki.fi> wrote: > > > I've been once in a while over the years thinking about implementing > > CalDAV (and CardDAV) to Dovecot. It might be time to start that soon. > > Does anyone have any suggestions? So far my main goals would
2016 May 24
3
IPv6, ULAs and FreeBSD
Guus Sliepen [2016-05-24 11:26 +0200] : > On Tue, May 24, 2016 at 08:17:07AM +0200, Niklaas Baudet von Gersdorff wrote: [...] > > A $ cat /usr/local/etc/tinc/klaas/tinc-up > > ifconfig $INTERFACE inet6 fd16:dcc0:f4cc:0:0:1:0:1 prefixlen 80 > > route -6 add -host fd16:dcc0:f4cc:0:0:2:0:1 fd16:dcc0:f4cc:0:0:1:0:1 > > route -6 add -net
2015 Oct 09
4
[PATCH 1/2] kvm/x86: Hyper-V synthetic interrupt controller
Christian, the question for you is towards the end... On 09/10/2015 15:39, Denis V. Lunev wrote: > diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c > index 62cf8c9..15c3c02 100644 > --- a/arch/x86/kvm/hyperv.c > +++ b/arch/x86/kvm/hyperv.c > @@ -23,13 +23,265 @@ > > #include "x86.h" > #include "lapic.h" > +#include "ioapic.h"
2015 Oct 09
4
[PATCH 1/2] kvm/x86: Hyper-V synthetic interrupt controller
Christian, the question for you is towards the end... On 09/10/2015 15:39, Denis V. Lunev wrote: > diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c > index 62cf8c9..15c3c02 100644 > --- a/arch/x86/kvm/hyperv.c > +++ b/arch/x86/kvm/hyperv.c > @@ -23,13 +23,265 @@ > > #include "x86.h" > #include "lapic.h" > +#include "ioapic.h"
2014 Jun 12
0
[Bug 1402] Support auditing through Linux Audit subsystem
https://bugzilla.mindrot.org/show_bug.cgi?id=1402 Laurent Bigonville <l.bigonville at edpnet.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |l.bigonville at edpnet.be -- You are receiving this mail because: You are watching someone on the CC
2016 Feb 15
0
[PATCH 09/23] nv50-: separate vertex formats from surface format descriptions
From: Ben Skeggs <bskeggs at redhat.com> We've previously had identical naming between vertex and texture formats, so it mostly made sense to define these together. However, upcoming patches are going to transition the driver over to using updated texture header definitions using NVIDIA's naming, and this will no longer be the case. Signed-off-by: Ben Skeggs <bskeggs at
2009 May 12
2
[LLVMdev] Compiler error: LoopStrengthReduce.cpp
The error given: ..\..\..\..\trunk\lib\Transforms\Scalar\LoopStrengthReduce.cpp(1016) : error C2668: 'abs' : ambiguous call to overloaded function f:\Program Files\Microsoft Visual Studio 8\VC\include\math.h(539): could be 'long double abs(long double)' f:\Program Files\Microsoft Visual Studio 8\VC\include\math.h(491): or 'float abs(float)'
2009 May 12
0
[LLVMdev] Compiler error: LoopStrengthReduce.cpp
On May 12, 2009, at 3:09 PMPDT, OvermindDL1 wrote: > The error given: > > ..\..\..\..\trunk\lib\Transforms\Scalar\LoopStrengthReduce.cpp(1016) : > error C2668: 'abs' : ambiguous call to overloaded function > > It should be rather obvious from the message. The error is in > LoopStrengthReduce.cpp on line 1016: > (unsigned(abs(SInt)) < SSInt || (SInt %
2002 Nov 19
1
fexact.c
Dear All, I am using fexact.c on a C++ program I wrote. To minimize dependencies on other files (e.g., to not need to include R.h and ctest.h ---now I only include the R files Boolean.h, Constants.h, and Memory.h), I have re-written all declarations of Sints as ints and, what is potentially more serious, I have re-written the line (lines 329 and 330, in fexact.c on R-1.6.1) /* IMAX is the
2010 Mar 19
1
chron package install fail in intel I7 - fedora 12
install packages chron fail in Fedora 12, cpu I7/860 See down. Regard, Juan S. Ramseyer. > install.packages() Loading Tcl/Tk interface ... done --- Please select a CRAN mirror for use in this session --- Warning in install.packages() : argument 'lib' is missing: using '/usr/lib64/R/library' tentando a URL
2010 Feb 17
1
crhon compile directive faul in version x64, in Intel i7?
==> CRASH INSTALLING PACKAGES CHRON IN: Intel(R) Core(TM) i7 CPU 860 @ 2800GHz ==> IT'S COMPILED DIRECTIVE WRONG? REGARD YOUR ATENTION ==> I RUN: SO:Linux 2.6.31.12-174.2.19.fc12.x86_64 x86_64 Fedora release 12 (Constantine) ==> AND RECEIVE NEXT MESSAGENS IN INSTALLING: > install.packages() Loading Tcl/Tk interface ... done --- Please select a CRAN mirror for use in this
2016 Feb 15
1
[PATCH 09/23] nv50-: separate vertex formats from surface format descriptions
Why not fix the new names instead to be like the old names? Seems like that would be way simpler... On Feb 15, 2016 12:38 AM, "Ben Skeggs" <skeggsb at gmail.com> wrote: > From: Ben Skeggs <bskeggs at redhat.com> > > We've previously had identical naming between vertex and texture > formats, so it mostly made sense to define these together. > > However,