Displaying 2 results from an estimated 2 matches for "76e5".
Did you mean:
765
2004 Mar 02
0
LDAP-Domain confusion
...0)
api_pipe_bind_req: \PIPE\lsarpc -> \PIPE\lsass
[2004/03/01 17:59:50, 3, effective(0, 1), real(0, 0)]
rpc_server/srv_pipe.c:check_bind_req(732)
check_bind_req for \PIPE\lsarpc
[2004/03/01 17:59:50, 3, effective(0, 1), real(0, 0)]
smbd/pipes.c:reply_pipe_write_and_X(199)
writeX-IPC pnum=76e5 nwritten=72
[2004/03/01 17:59:50, 3, effective(0, 1), real(0, 0)]
smbd/process.c:process_smb(890)
Transaction 7 of length 63
[2004/03/01 17:59:50, 3, effective(0, 1), real(0, 0)]
smbd/process.c:switch_message(685)
switch message SMBreadX (pid 25315)
[2004/03/01 17:59:50, 3, effective(0, 1), r...
2004 Jul 30
1
SIP connections do not hang up
...26-32
Found description format telephone-event
Capabilities: us - 0x41e(GSM|ULAW|ALAW|G726|ILBC), peer -
audio=0x41e(GSM|ULAW|ALAW|G726|ILBC)/video=0x0(EMPTY), combined -
0x41e(GSM|ULAW|ALAW|G726|ILBC)
Non-codec capabilities: us - 0x1(G723), peer - 0x1(G723), combined -
0x1(G723)
-- SIP/sipgate-76e5 is making progress passing it to SIP/2112-495b
Reliably Transmitting:
CANCEL sip:497141220856@217.10.64.78 SIP/2.0
Via: SIP/2.0/UDP 82.83.56.91:5060;branch=z9hG4bK0b9e12cc
From: "Florian" <sip:8888888@sipgate.de>;tag=as1c3c2263
To: <sip:07141220856@sipgate.de>
Contact: <sip...