search for: _hangup

...,NoOp(Call-ID: ${PJSIP_HEADER(read,Call-ID)}) same => n,Dial(PJSIP/xyz011101/sip:xyz011101@<outbound_proxy>:5060,30,b(_pre_dial,s,1)) exten => h,1,NoOp() [_pre_dial] exten => s,1,NoOp(Call-ID: ${PJSIP_HEADER(read,Call-ID)}) same => n,Set(CHANNEL(hangup_handler_push)=_hangup,s,1()) same => n,Return [_hangup] exten => s,1,NoOp(Call-ID: ${PJSIP_HEADER(read,Call-ID)}) same => n,Return Here's the result: -- Executing [999 at xyz:1] NoOp("PJSIP/poly_650_2_01-0000006f", "Call-ID: e3e249e5-7e8941dd-da386565 at 192.168.100...

...: this function is not supported by > >the connection driver: virStreamEventRemoveCallback > > > > > >Is there other way to stop getting this errors? or perhaps this is a bug. > > > > This sounds like a bug. Do you get no other event than just _READABLE? > No _HANGUP or _ERROR? Does virStreamAbort() work, even though it's > probably not what you are looking for? > > >Thanks in advance. > > > >Jose Valencia > > >_______________________________________________ > >libvirt-users mailing list > >libvirt-users@redhat....

Hello everyone, I am opening a virChannel(unix) to a domain and receiving data with a non-blocking virStream using events, when the connected domain gets stopped(which deletes the channel unix socket) by calling destroy, shutdown, pause or migrate on that domain, with the stream open the read event is triggered repeatedly, and virStreamRecv returns 0 bytes indicating EOF but neither

...ion driver: virStreamEventRemoveCallback >>> > >>> > >>> >Is there other way to stop getting this errors? or perhaps this is a bug. >>> > >>> >>> This sounds like a bug. Do you get no other event than just _READABLE? >>> No _HANGUP or _ERROR? Does virStreamAbort() work, even though it's >>> probably not what you are looking for? >>> >>> >Thanks in advance. >>> > >>> >Jose Valencia >>> >>> >_______________________________________________ >>&g...

...t; >libvirt: I/O Stream Utils error : this function is not supported by >the connection driver: virStreamEventRemoveCallback > > >Is there other way to stop getting this errors? or perhaps this is a bug. > This sounds like a bug. Do you get no other event than just _READABLE? No _HANGUP or _ERROR? Does virStreamAbort() work, even though it's probably not what you are looking for? >Thanks in advance. > >Jose Valencia >_______________________________________________ >libvirt-users mailing list >libvirt-users@redhat.com >https://www.redhat.com/mailman/list...

...by >> >the connection driver: virStreamEventRemoveCallback >> > >> > >> >Is there other way to stop getting this errors? or perhaps this is a bug. >> > >> >> This sounds like a bug. Do you get no other event than just _READABLE? >> No _HANGUP or _ERROR? Does virStreamAbort() work, even though it's >> probably not what you are looking for? >> >> >Thanks in advance. >> > >> >Jose Valencia >> >> >_______________________________________________ >> >libvirt-users mailing lis...

...> >>> > > >>> > > >>> >Is there other way to stop getting this errors? or perhaps this is a > bug. > >>> > > >>> > >>> This sounds like a bug. Do you get no other event than just _READABLE? > >>> No _HANGUP or _ERROR? Does virStreamAbort() work, even though it's > >>> probably not what you are looking for? > >>> > >>> >Thanks in advance. > >>> > > >>> >Jose Valencia > >>> > >>> >_______________________...

The following series of patches comprises the bulk of our outstanding changes for Ocfs2. Aside from the usual set of cleanups and fixes that were inappropriate for 2.6.25, there are a few highlights: The '/sys/o2cb' directory has been moved to '/sys/fs/o2cb'. The new location meshes better with modern sysfs layout. A symbolic link has been placed in the old location so as to