Displaying 20 results from an estimated 20000 matches similar to: "channel destruction after a transfer call"
2009 Nov 12
0
Scheduling destruction of SIP dialog
Hello,
I got situation which is unclear for me, hope somebody could explain this.
A calls to B
INVITE sent from A to B
B responds with 100 Trying
B responds with 183 Progress
After 10 seconds: Asterisk CLI: Scheduling destruction of SIP dialog '..' in
32000 ms (Method: INVITE)
Asterisk sends CANCEL _instantly_
B responds with 200 OK and 487 Request Terminated
Asterisk confirms 102 ACK
2007 May 22
0
[1029] trunk/wxruby2/swig/classes/MenuBar.i: Add special GC protection for Wx::Menu to prevent premature destruction
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2008 May 12
0
[LLVMdev] Python bindings available.
On May 12, 2008, at 02:58, Mahadevan R wrote:
>> Consider the case where a function creates and populates a Module,
>> stuffs it in an ExistingModuleProvider for the JIT, then returns
>> the ModuleProvider, dropping direct reference to the Module.
>> (ModuleProvider takes ownership of the Module.) I presume that your
>> Python object is under the impression
2008 May 12
2
[LLVMdev] Python bindings available.
On Mon, May 12, 2008 at 7:55 PM, Gordon Henriksen
<gordonhenriksen at mac.com> wrote:
> On May 12, 2008, at 02:58, Mahadevan R wrote:
>
> >> Consider the case where a function creates and populates a Module,
> >> stuffs it in an ExistingModuleProvider for the JIT, then returns
> >> the ModuleProvider, dropping direct reference to the Module.
> >>
2007 Aug 27
0
Bad hangup event cause
Hello, i have a problem with the hangup cause received from the AMI in the Hangup events. All calls that arent answered after ringing are returning hangup cause 16 (normal clearing) instead 19.
Im running asterisk 1.4.11, the calls are generated to a SIP peer using the AMI originate command.
This is the 'sip debug' output:
Reliably Transmitting (no NAT) to 192.168.0.70:5060:
INVITE sip:1
2010 Mar 19
1
[LLVMdev] Checker for destruction-needing classes allocated in BumpPtrAllocators?
Hi Ted,
Doug said you might have a clang-based checker that would detect when
people allocate memory with a BumpPtrAllocator and then construct a
class into it that needs destruction. In killing valgrind-found memory
leaks in LLVM, I've found several instances of this mistake. They
often involve SmallVectors, which only show up as leaks in valgrind if
they happen to overflow their static
2014 Apr 29
0
Destruction of SIP dialog for OPTIONS requests
Hi all,
I'd like to verify whether an Asterisk behaviour is expected or not, and
ask for advice for the best solution.
I have Asterisk 1.8.17.0 on debian wheezy, listening on UDP and TCP 5060,
and TLS 5061.
Asterisk is part of a dispatcher set in Kamailio (4.1.3), and is marked as
AP (Active Probing): this means that Kamailio sends an OPTIONS request
every N seconds to verify Asterisk is
2019 Oct 22
0
[PATCH v5 01/14] drm/dp_mst: Destroy MSTBs asynchronously
When reprobing an MST topology during resume, we have to account for the
fact that while we were suspended it's possible that mstbs may have been
removed from any ports in the topology. Since iterating downwards in the
topology requires that we hold &mgr->lock, destroying MSTBs from this
context would result in attempting to lock &mgr->lock a second time and
deadlocking.
So, fix
2019 Jan 16
2
Skipping construction/destruction of stack allocated objects
Hello,
For performance reasons, I would like to provide a way to skip
construction/destruction of objects that are stack allocated. Typically,
C-style arrays of std::complex create an initialization loops that is
almost always unnecessary.
I am thinking of providing an __attribute__((uninitialized)) that can be
applied to an object declaration:
{
std::complex<float> foo[64][64]
2006 Jul 21
1
GLX redirection extension
I think that I may have found a potentially useful way out of some
problems within the current compositing framework. Basically, the server
has information that the compositor would find useful.
Of course, I may be wrong ...
GLX redirection
---------------
The GLX protocol provides GL applications with the contexts and
drawables that they require to execute GL. Since the X server is
usually in
2009 Jun 30
0
Redirect with ExtraChannel on Bridged call give AMI event with second channel name AsyncGoto/...<ZOMBIE>
Originally posted on asterisk-dev with no response for 5 days, so posting it
to the wider audience now.
Asterisk Release 1.6.1.1
Scenario:-
1. 2 SIP peers (Zoiper softphone, if it matters) registered as 901 and
902
2. Using AMI, 901 is Originated
3. When 901 answers, it is Redirected to an extension "exten =>
dial,1,Dial(SIP/902)"
4. 902 rings, then answers
5.
2004 Dec 16
1
Calls arent handled by asterisk - destruction of call
Hello, I'm trying to get started with asterisk/SIP so I was trying the demo that is provided in the extensions config file, but the call isn't "answered" by my server when I try calling the number that I registered at my SIP provider.
I've registered with register => John.Doe:MyPass:MyUser@my-sip-provider/1000 in sip.conf and if I use "sip debug" I can see the
2013 Feb 14
5
using @releaseDomain to subscribe for domain destruction
Hello!. How can i use @releaseDomain from dom0 to subscribe for domain
destruction?
I''m try to add watch for @releaseDomain path with token equal of
needed domain id. But when another domain dies, i get domain that i
provide via token to xs_watch.
Is that possible to get id of domain what released from xenstore?
--
Vasiliy Tolstov,
Clodo.ru
e-mail: v.tolstov@selfip.ru
jabber:
2009 Dec 21
2
[PATCH 1/2] Unreference state/buffer objects on context/screen destruction
- unreference state objects so that buffer objects are unreferenced and
eventually destroyed
- free channel at screen's destruction
Index: nv50/nv50_screen.c
===================================================================
--- nv50/nv50_screen.c (wersja 32083)
+++ nv50/nv50_screen.c (kopia robocza)
@@ -162,7 +162,22 @@
nv50_screen_destroy(struct pipe_screen *pscreen)
{
struct
2015 Apr 07
0
Help debugging a possible SIP channel leak in 11.17.0, possible race condition
El 07/04/15 a las 17:38, Alex Villac??s Lasso escribi?:
> I am trying to collect enough information about an problem a client is having with its asterisk 11.17.0 x86_64. This issue was observed before in 1.8.20, and we upgraded to 11.15.0 and then to 11.17.0 with no solution.
>
> Background: this client is a telemarketing call-center that generates outgoing calls with close to a hundred
2006 Aug 01
3
Validation on ActiveRecord destruction
Rails has many built in validation methods to ensure that an
ActiveRecord instance cannot be created or updated under certain
situations (typically caused by invalid data). However, I can find no
methods to govern whether an ActiveRecord instance can be destroyed.
Essentially, I wish an error to be raised when a user tries to delete an
ActiveRecord without first adhering to a certain set of
2013 Feb 13
0
[LLVMdev] ManagedStatic and order of destruction
Right, I'm suggesting we keep llvm_shutdown() for users who want this
control, but also destroy still-live ManagedStatic instances if
llvm_shutdown() is not called. This helps in the case where there is not a
clear time when llvm_shutdown() can be called, especially given that LLVM
cannot be resurrected in the same process due to current limitations in the
pass registry, and perhaps
2019 Sep 03
0
[PATCH v2 03/27] drm/dp_mst: Destroy MSTBs asynchronously
When reprobing an MST topology during resume, we have to account for the
fact that while we were suspended it's possible that mstbs may have been
removed from any ports in the topology. Since iterating downwards in the
topology requires that we hold &mgr->lock, destroying MSTBs from this
context would result in attempting to lock &mgr->lock a second time and
deadlocking.
So, fix
2013 Feb 09
3
[LLVMdev] ManagedStatic and order of destruction
I'm curious about the design rationale for how ManagedStatic instances are
cleaned up, and I'm hoping someone can shed some light on it.
Currently, ManagedStatic objects are cleaned up when llvm_shutdown()
traverses the global list of initialized objects and calls destroy() on
each. This leads to two questions:
1. An assertion enforces that the objects are deleted in reverse order of
2019 Sep 25
0
[PATCH v2 03/27] drm/dp_mst: Destroy MSTBs asynchronously
On Wed, 2019-09-25 at 14:16 -0400, Sean Paul wrote:
> On Tue, Sep 03, 2019 at 04:45:41PM -0400, Lyude Paul wrote:
> > When reprobing an MST topology during resume, we have to account for the
> > fact that while we were suspended it's possible that mstbs may have been
> > removed from any ports in the topology. Since iterating downwards in the
> > topology requires