Displaying 4 results from an estimated 4 matches for "liveliness".
Did you mean:
likeliness
2016 Feb 18
2
Asterisk 13 and WebRTC. Is wiki page still valid ?
2016-02-18 15:42 GMT+01:00 Marek ?ervenka <cervajs at fpf.slu.cz>:
> my experience with pjsip for webrtc
> http://lists.digium.com/pipermail/asterisk-users/2015-September/287562.html
>
>
> Yes I saw this post earlier today.
Having to fight 14 days scared me a bit !
Did you set sipml5 on your own server or did you use Live demo (
2018 Sep 26
2
Re: OpenStack output workflow
On Wed, Sep 26, 2018 at 11:39 AM Richard W.M. Jones <rjones@redhat.com>
wrote:
> On Wed, Sep 26, 2018 at 09:57:22AM +0200, Fabien Dupont wrote:
> > Hi,
> >
> > There has been discussion about the OpenStack output and Richard asked
> for
> > a public thread on this list, so here it is.
> >
> > For v2v from VMware to RHV, there is a Python script that
2016 Feb 29
2
Asterisk 13 and WebRTC. Is wiki page still valid ?
2016-02-19 12:01 GMT+01:00 Marek ?ervenka <cervajs at fpf.slu.cz>:
> on my own server
>
Today, I'm back from holidays trip.
First of all, thanks for replying !
I'll try to use jssip as you suggested.
Anyway, I'm still failing to understand if wiki's page [1] is still valid
with Asterisk 13, and if it's not valid anymore, which is the main change
that prevent
2018 Sep 26
2
Re: OpenStack output workflow
.... The downside
of
it is that over time is becomes more and more difficult to know them all.
And
all the error messages are made for human beings, not machines, so providing
feedback through a launcher, such as virt-v2v-wrapper, is difficult.
The second challenge was monitoring the virt-v2v process liveliness and
progress. For liveliness, the virt-v2v-wrapper stores the PID and checks
that
it's still present and when absent checks its return code for success (0) or
failure (!0), and any other launcher could do the same. For progress, the
only
way to know what happens is to run virt-v2v in debug mode...