Displaying 6 results from an estimated 6 matches for "813c".
Did you mean:
813
2018 May 24
0
CentOS-announce Digest, Vol 159, Issue 6
...5:09 +0200
From: Fabian Arrotin <arrfab at centos.org>
To: "The CentOS developers mailing list." <centos-devel at centos.org>,
centos-announce at centos.org
Subject: [CentOS-announce] [Infra] - planned outage : {bugs, fr,
status}.centos.org
Message-ID: <2747bbbb-5c09-9ff9-813c-06f62599390d at centos.org>
Content-Type: text/plain; charset="utf-8"
Due to a hardware replacement, we'll have to power down the hypervisor
hosting several VMs, including the ones used for the following impacted
services :
* https://bugs.centops.org
* https://status.centos.org...
2014 Dec 11
2
PJSIP configuration question
Dan Cropp wrote:
> I had my screenshots flipped. Is there a way to make sure the Contact field is NOT included in the ACK response to the OK (for the Answer)?
>
> PJSIP is including the Contact for the ACK response to the OK.
> Contact:<sip:1234 at xxx.xxx.xx.xxx:5060>
>
There is no configuration option to configure this behavior. What is the
full SIP signaling?
--
Joshua
2014 Dec 11
0
PJSIP configuration question
...erisk still thinks there is a call.
Next I issue a hangup to Asterisk and it terminates the call
<--- Transmitting SIP request (456 bytes) to UDP:64.2.142.93:5060 --->
BYE sip:18005555555 at 64.2.142.192 SIP/2.0
Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;rport;branch=z9hG4bKPjd458d550-7bce-4008-813c-c84a0e446a86
From: "Dan" <sip:291 at XXX.XXX.XXX.XXX>;tag=781b4b63-0df9-47ad-9fa1-52a8729359c8
To: <sip:8005555555 at 64.2.142.93>;tag=as7aad862a
Call-ID: 309ec892-56a8-46d2-95ba-a6b1d65d0c43
CSeq: 23192 BYE
Route: <sip:64.2.142.93;lr>
Reason: Q.850;cause=0
Max-Forwards:...
2017 Oct 26
0
not healing one file
Hey Richard,
Could you share the following informations please?
1. gluster volume info <volname>
2. getfattr output of that file from all the bricks
getfattr -d -e hex -m . <brickpath/filepath>
3. glustershd & glfsheal logs
Regards,
Karthik
On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote:
> On a side note, try recently released health
2017 Oct 26
3
not healing one file
On a side note, try recently released health report tool, and see if it
does diagnose any issues in setup. Currently you may have to run it in all
the three machines.
On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote:
> Thanks for this report. This week many of the developers are at Gluster
> Summit in Prague, will be checking this and respond next
2017 Oct 26
2
not healing one file
...n.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed metadata selfheal on d45b3eb9-af42-48c8-b693-b6d45486cd37. sources=0 [2] sinks=1
[2017-10-25 10:40:26.527338] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on 174c22df-de47-4247-813c-31ad987cd8ac. sources=0 [2] sinks=1
[2017-10-25 10:40:26.531546] I [MSGID: 108026] [afr-self-heal-metadata.c:52:__afr_selfheal_metadata_do] 0-home-replicate-0: performing metadata selfheal on 261d9e42-1ddf-4fc6-b844-1f864a34e5c7
[2017-10-25 10:40:26.536037] I [MSGID: 108026] [afr-self-heal-common...