WHo dropped the call?

[genesysnoob]

I just want to confirm this as to who dropped the call agent or customer


When i look in the logs i see below, does this mean agent dropepd the call

party_info 31376.c14fcb0 state change: from <Connected> to <Null>

From event released event

Type EventReleased
    Devices: <51376/31376> <-/707505999> <-/->
    Calls: 17075477/007f02de46eedf49/17075477.7005930/c:2/r:4 0/none
    Parties:          D51376/31376.7265460-7005930:1/l:2/r:1/Established,Active,Destination
                            X707505999/707505999.9cb0710-7005930:1/l:1/r:0/Established,Origination
                            none
    Flags: divert=0 hook=1 postCall=0 active=1 moveAll=1 callType=1 hideOtherPi=0 InternalOther=0
  --- Pre-event ---
  +++ Released +++
    -- XAction: start 31376.7265460-7005930:1
    SetReleased: party 31376.7265460-7005930:1, cause Null
    -- party_info 31376.c14fcb0 state change: from <Connected> to <Null>
    -- G7 release

[cavagnaro]

Search for documentation. This is well explained there

Enviado de meu SM-G9650 usando o Tapatalk

[Mr.T]

SIP env? If so check BYE msg

[genesysnoob]

[quote author=cavagnaro link=topic=11359.msg51812#msg51812 date=1560468519]
Search for documentation. This is well explained there

Enviado de meu SM-G9650 usando o Tapatalk
[/quote]

SIP deployment guide or something else?

[cavagnaro]

Just search for it, under reporting or TServer events

Enviado de meu SM-N9600 usando o Tapatalk

[genesysnoob]

[quote author=Mr.T link=topic=11359.msg51815#msg51815 date=1560473900]
SIP env? If so check BYE msg
[/quote]

Sorry for bumping an old thread

I have an "eventreleased" event from an extension

When i scrolled above  i see two bye messages
which message i need to look into and how do i determine who dropped the call.

BYE 1

Sending  [0,UDP] 673 bytes to resource manager IP address 1:5260 >>>>>
BYE sip:Genesys@MCP:5070 SIP/2.0 ----> We have GIR recording*****
From: <sip:Agentextension@SIPVirtualIP:5070;transport=tcp>;tag=869468C7-884C-43A1-9ABF-7749A2424C42-4960282
To: <sip:msml=IHPDGIAULP0OJASCQIUPC02GN00035GV@Resouce manager IP2:5260;dn=agent extension;record;tenant-dbid=101;media-service=record>;tag=320417E8-0000-34C7-627C-4A740B08E312
Call-ID: 444F23C2-1DBA-444F-B1B1-EF4D1C7628CA-2169085@SIP VIP
CSeq: 6 BYE
Content-Length: 0
Via: SIP/2.0/UDP SIPVIP:5070;branch=z9hG4bK2AAE3B55-76ED-4930-8061-033CE9E906F4-5815650
Max-Forwards: 9



BYE 2

Sending  [0,UDP] 648 bytes to RM2 IP address:5260 >>>>>
BYE sip:Genesys@GIR MCP IP:5070 SIP/2.0
From: sip:ANI@SBC IP;tag=869468C7-884C-43A1-9ABF-7749A2424C42-4960283
To: <sip:msml=IHPDGIAULP0OJASCQIUPC02GN00035GV@RM2:5260;dn=Ani;record;tenant-dbid=101;media-service=record>;tag=320417E8-0000-D8AA-6655-A89C761ED041
Call-ID: 444F23C2-1DBA-444F-B1B1-EF4D1C7628CA-2169086@SIPVIP
CSeq: 3 BYE
Content-Length: 0
Via: SIP/2.0/UDP SIPVIP:5070;branch=z9hG4bK2AAE3B55-76ED-4930-8061-033CE9E906F4-5815651
Max-Forwards: 9
Route: <sip:000000000A3DE100@RM12:5260;lr;gvp.rm.datanodes=1%7C2;confinstid=IHPDGIAULP0OJASCQIUPC02GN00035GV;idtag=00055DCF>

THanks