Displaying 3 results from an estimated 3 matches for "53851".
Did you mean:
3851
2007 Oct 26
2
1.0.2
Hi all,
1.0.2 final will drop as soon as I get the win32 builds from Luis. Watch for it.
In the future we won''t do RCs but will just make point releases,
because no one really installed them except for ourselves. This is
what Zed used to do and what we should have done all along.
Note that the bug tracker is empty:
2018 Feb 12
1
Re: Nested KVM: L0 guest produces kernel BUG on wakeup from managed save (while a nested VM is running)
On Fri, Feb 09, 2018 at 12:02:25PM +0100, Florian Haas wrote:
> On Fri, Feb 9, 2018 at 11:48 AM, Kashyap Chamarthy <kchamart@redhat.com> wrote:
[...]
> > I've made some minor edits to clarify a bunch of bits, and a link to the
> > Kernel doc about Intel nVMX. (Hope that looks fine.)
>
> I'm sure they it does, but just so you know I currently don't see any
2011 Mar 04
2
Asterisk <-> Lync / Call Center Transfer / Refer
...lt;sip:500;phone-context=DefaultProfile at domainname.com;user=phone>;epid=B3E26C1E76;tag=9227b8a39d
CSeq: 2 REFER
Call-ID: aa6f8871-4151-4149-ad5a-29ab941bf4d0
Via: SIP/2.0/TLS 20.20.20.20:54166;branch=z9hG4bKEB39D72C.F05E7E34CF9EF4FD;branched=FALSE
Max-Forwards: 69
Via: SIP/2.0/TLS 172.16.2.29:53851;ms-received-port=53851;ms-received-cid=400
User-Agent: CPE/4.0.7577.107 OCPhone/4.0.7577.107 (Microsoft Lync 2010 Phone Edition)
Supported: ms-dialog-route-set-update
Refer-to: <sip:user2 at domainname.com>
Referred-By: <sip:user1 at domainname.com>;ms-referee-uri="sip:500;phone-co...