search for: 89bb

Displaying 6 results from an estimated 6 matches for "89bb".

Did you mean: 89ab
2003 Sep 27
0
More Sip/Grandstream issues
...ith capability 4 Answering with capability 8 Reliably Transmitting (no NAT): SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.50.248 From: "Michael Hess" <sip:mlh@192.168.50.1>;tag=f3e33d4d-5431-b2d1-443e-0183d2cac6c7 To: <sip:8@192.168.50.1>;tag=as568b15d0 Call-ID: ccf9d2ca-982b-523b-89bb-10ce270b5847@192.168.50.248 CSeq: 53592 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER Contact: <sip:8@192.168.50.1> Content-Type: application/sdp Content-Length: 178 v=0 o=root 1434 1434 IN IP4 192.168.50.1 s=session c=IN IP4 192.168.50.1 t=0 0 m=audio 27838...
2013 Mar 04
0
samba rodc
...80525496-3468030855-4252408690) as an RODC But after that i see this on my PDC log 2013/03/03 19:54:50, 0] ../source4/librpc/rpc/dcerpc_util.c:660(dcerpc_pipe_auth_recv) Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for e3514235-4b06-11d1-ab04-00c04fc2dcd2 at ncacn_ip_tcp:37a0236c-89bb-481c-95e9-257682646e2a._msdcs.forsa.com.co[1024,seal,krb5] NT_STATUS_UNSUCCESSFUL And in my RODC i see this Default-First-Site-Name\BDC DSA Options: 0x00000025 DSA object GUID: 37a0236c-89bb-481c-95e9-257682646e2a DSA invocationId: 64f4a862-309d-4a0d-a3de-5aa8998da68a ==== INBOUND NEIGHBORS ====...
2003 May 16
1
kphone fails to register with asterisk (sip)
....168.0.10>;expires=900 Date: Fri, 16 May 2003 09:54:02 GMT Content-Length: 0 to 192.168.144.247:5060 Sip read: REGISTER sip:pbx SIP/2.0 Via: SIP/2.0/UDP 192.168.16.38:11430 From: <sip:tore@pbx>;tag=a40edf0e-4aa8-4d30-b24e-9db25efe660c To: <sip:tore@pbx> Call-ID: ff8c9ba3-35d6-437a-89bb-f9b711d9a530@192.168.16.38 CSeq: 11 REGISTER Contact: <sip:192.168.16.38:11430>;methods="INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK" User-Agent: Windows RTC/1.0 Expires: 900 Event: registration Allow-Events: presence Content-Length: 0 12 headers, 0 lines I...
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 033ada38-34fd-4acd-b4bd-aa6cc1b2b357. sources=0 [2] sinks=1 [2017-10-25 10:40:10.431801] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on bdf2830e-4e86-43fc-89bb-0bd666b97ff6. sources=0 [2] sinks=1 [2017-10-25 10:40:10.445830] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on f5f3471f-919b-4f8d-a7cb-031e8552b233. sources=0 [2] sinks=1 [2017-10-25 10:40:10.460781] I [MSGID: 108026] [afr-self-h...