Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations dencom on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP Office 500 and Chronicall query 1

Status
Not open for further replies.
cruzades

cruzades

Programmer
Sep 6, 2011
254
PH
Hi,

I would like to inquire if Chronicall can able to detect calls dropped by the agent explicitly?

e.g.
scenario:

Calls --> IVR (VM pro) --> Hunt Group --> Agent (answers) --> Agent (dropped/hunged up the call)

Now, my question is, will Chronicall be able to dertermine that state?

Currently, we're using CCR, and there is no "state" with that call scenario.
 
Sort by date Sort by votes
You are able to see if the call is ended but not who dropped the call.
This can be both the agent or the caller.
The Cradle to grave shows you exactly what you want to see in one overview.


BAZINGA!

I'm not insane, my mother had me tested!

 
Upvote 0 Downvote
Peter is right, cradle to grace will see that.

remember C2C isnt a reporting tool, its a diagnostics and verification tool so running it over a large period with a lot of calls will take a very long time.

ACSS - SME
General Geek



1832163.png
 
Upvote 0 Downvote
@HSM, tlpeter

Just to clear it up, you mean using Cradle to Grave will see how terminated to call?

can I have a screenshot for this? I'm thinking of replacing our CCR with this if it's that the case.

-cheers!
 
Upvote 0 Downvote
*how, to, i mean "who","the"

".. see who terminated the call?
 
Upvote 0 Downvote
@tlpeter,

Hi, thanks for the link, but based on the screenshot, it only shows calls were dropped, but nothing says who dropped the call.

My concern is to determine who initiated the call dropping, if it is the caller or the callee.

Any thoughts?
 
Upvote 0 Downvote
You cannot see that as i already said.
I must say this is a strange request.


BAZINGA!

I'm not insane, my mother had me tested!

 
Upvote 0 Downvote
@tlpeter

Yup very strange, while researching about this issue, I stumbled with this.. "Avaya IQ"
AnalyticsintheCCGCC48444.jpg


I wonder, where that state came from that SMDR/Chonicall/CCR can't able to show up.

?
 
Upvote 0 Downvote
That is not for the IPO i am affraid.

BAZINGA!

I'm not insane, my mother had me tested!

 
Upvote 0 Downvote
C2G WILL show you who terminated the call.

You will see either

Drop (Calling)
or
Drop (Receiving)

I suspect you wouldn't be able to create a report, but I'm sure you can run an SQL query to pull a list of Drop events.

ACSS - SME
General Geek



1832163.png
 
Upvote 0 Downvote
@Hsm,

That will be great, however, can someone provide me a structure of its database, so that we could confirm or someone provide a screen shot if it.

/happy :)

 
Upvote 0 Downvote
Best bet is if you have set up Chronicall via a reseller, then ask them to contact Ximasoft to show them how to create the SQL query. I'm still just getting my head around doing that :)

ACSS - SME
General Geek



1832163.png
 
Upvote 0 Downvote
@HSM

Thank you so much for your replies, I appreciated that :)

Anyway, I made a call scenario wherein A: caller disconnects first B: callee/agent disconnects first.

Help me to check the difference comparing the 2 sysmon log.

A:

********** Warning: Logging to Screen Started **********
1650283829mS CMLineRx: v=0
CMConnect
Line: type=SIPLine 26 Call: lid=26 id=123729 in=0
Called[7982401205] Type=Default (100) Reason=CMDRdirect
IE CMIEFastStartInfoData (6)
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=4413232710575
IE CMIEDeviceDetail (231) LOCALE=eng HW=15 VER=7 class=CMDeviceSIPTrunk type=0 number=26 channel=1 rx_gain=32 tx_gain=32 ep_callid=123729 ipaddr=192.168.3.250 apps=8
1650283835mS CMExtnTx: v=5000, p1=0
CMConnect
Line: type=SIPLine 260 Call: lid=1772 id=123727 in=0
Called[7982401205] Type=Default (100) Reason=CMDRdirect
IE CMIEFastStartInfoData (6)
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=4413232710575
IE CMIEDeviceDetail (231) LOCALE=eng HW=15 VER=7 class=CMDeviceSIPTrunk type=0 number=26 channel=1 rx_gain=32 tx_gain=32 ep_callid=123729 ipaddr=192.168.3.250 apps=8
Timed: 09/11/12 17:37
1650283837mS CMExtnRx: v=5000, p1=0
CMConnectAck
Line: type=SIPLine 260 Call: lid=1772 id=123727 in=0
1650283840mS CMLineTx: v=0
CMConnectAck
Line: type=SIPLine 26 Call: lid=26 id=123729 in=0
IE CMIERespondingPartyName (228)(Type=CMNameDefault) name=testAccount
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:101 N:100 R:4) number=5000
IE CMIEDeviceDetail (231) LOCALE=eng HW=15 VER=7 class=CMDeviceSIPPhone type=89 number=9521 channel=0 rx_gain=32 tx_gain=32 ep_callid=123727 ipaddr=192.168.3.250 apps=8
1650283841mS CMLineTx: v=0
CMFacility
Line: type=SIPLine 26 Call: lid=26 id=123729 in=0
1650302472mS CMLineTx: v=0
CMInformation
Line: type=SIPLine 26 Call: lid=26 id=123729 in=0
Called[3] Type=Default (100) Reason=CMDRdirect
1650321982mS CMLineRx: v=0
CMReleaseComp
Line: type=SIPLine 26 Call: lid=26 id=123729 in=0
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=4413232710575
IE CMIEDeviceDetail (231) LOCALE=eng HW=15 VER=7 class=CMDeviceSIPTrunk type=0 number=26 channel=1 rx_gain=32 tx_gain=32 ep_callid=123729 ipaddr=192.168.3.250 apps=8
Cause=16, Normal call clearing
1650321984mS CMExtnTx: v=5000, p1=0
CMFacility
Line: type=SIPLine 260 Call: lid=1772 id=123727 in=0
IE CMIEFastStartInfoData (6)
Timed: 09/11/12 17:37
1650321989mS CMExtnTx: v=5000, p1=0
CMReleaseComp
Line: type=SIPLine 260 Call: lid=1772 id=123727 in=0
Called[4413232710575] Type=Default (100) Reason=CMDRdirect Calling[5000] Type=Internal Plan=Default
Cause=16, Normal call clearing
Timed: 09/11/12 17:37

********** Warning: Logging to Screen Stopped **********

B:

1650596747mS CMLineRx: v=0
CMConnect
Line: type=SIPLine 26 Call: lid=26 id=123758 in=0
Called[7982401205] Type=Default (100) Reason=CMDRdirect
IE CMIEFastStartInfoData (6)
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=4413232710575
IE CMIEDeviceDetail (231) LOCALE=eng HW=15 VER=7 class=CMDeviceSIPTrunk type=0 number=26 channel=1 rx_gain=32 tx_gain=32 ep_callid=123758 ipaddr=192.168.3.250 apps=8
1650596752mS CMExtnTx: v=5000, p1=0
CMConnect
Line: type=SIPLine 260 Call: lid=1773 id=123756 in=0
Called[7982401205] Type=Default (100) Reason=CMDRdirect
IE CMIEFastStartInfoData (6)
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=4413232710575
IE CMIEDeviceDetail (231) LOCALE=eng HW=15 VER=7 class=CMDeviceSIPTrunk type=0 number=26 channel=1 rx_gain=32 tx_gain=32 ep_callid=123758 ipaddr=192.168.3.250 apps=8
Timed: 09/11/12 17:42
1650596755mS CMExtnRx: v=5000, p1=0
CMConnectAck
Line: type=SIPLine 260 Call: lid=1773 id=123756 in=0
1650596758mS CMLineTx: v=0
CMConnectAck
Line: type=SIPLine 26 Call: lid=26 id=123758 in=0
IE CMIERespondingPartyName (228)(Type=CMNameDefault) name=testAccount
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:101 N:100 R:4) number=5000
IE CMIEDeviceDetail (231) LOCALE=eng HW=15 VER=7 class=CMDeviceSIPPhone type=89 number=9522 channel=0 rx_gain=32 tx_gain=32 ep_callid=123756 ipaddr=192.168.3.250 apps=8
1650596759mS CMLineTx: v=0
CMFacility
Line: type=SIPLine 26 Call: lid=26 id=123758 in=0
1650608860mS CMExtnRx: v=152, p1=0
CMSetup
Line: type=SIPLine 260 Call: lid=1765 id=123759 in=0
Called[*08] Type=Default (100) Reason=CMDRdirect SndComp Calling[152] Type=Internal Plan=Default
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
IE CMIERespondingPartyName (228)(Type=CMNameDefault) name=rascaño
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:101 N:100 R:4) number=152
IE CMIEFastStartInfoData (6)
IE CMIEMediaWaitForConnect (16) CMIEMediaWaitForConnect
1650608864mS CMExtnTx: v=152, p1=0
CMProgress
Line: type=SIPLine 260 Call: lid=1765 id=123759 in=0
IE CMIEProgressIndicator (30) cs=CMCSITUT (0), loc=CMLUser (0), pd=CMPDInbandPattern (8)
IE CMIEFastStartInfoData (6)
Display [PROGRESSING]
Timed: 09/11/12 17:42
1650618765mS CMLineTx: v=0
CMInformation
Line: type=SIPLine 26 Call: lid=26 id=123758 in=0
Called[3] Type=Default (100) Reason=CMDRdirect
1650633280mS CMExtnRx: v=5000, p1=0
CMReleaseComp
Line: type=SIPLine 260 Call: lid=1773 id=123756 in=0
Cause=16, Normal call clearing
1650633282mS CMLineTx: v=0
CMFacility
Line: type=SIPLine 26 Call: lid=26 id=123758 in=0
IE CMIEFastStartInfoData (6)

********** Warning: Logging to Screen Stopped **********

What I've noticed is that, at A: (caller disconnects first) log file has its time stamp, while in B: doesn't have.

Any thoughts?


 
Upvote 0 Downvote
Yup, before I posted this query.

But in SMDR, there's no particular fields that emphasize for 'origin of termination'.
 
Upvote 0 Downvote
Hi to All,

just recently finished a query tool to satisfy this.

I've just extracted the data from sysmon log files (filter option -> Trace Option -> Calls -> Extn Send/Recv), using PHP and MySql, I came to this tool.

drop.jpg


I hope I got it (somehow) right :)

Release type:
Normal = caller disconnect the call.
Agent = agent disconnect first.
 
Upvote 0 Downvote
Give this info to Xima and i bet they can built this in to there system.


BAZINGA!

I'm not insane, my mother had me tested!

 
Upvote 0 Downvote
I will be gladly if they can able to include (if not yet) this to their system.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

Scuzzie2k
  • Locked
  • Question
IP Office 500 and Avaya Workplace 1
Replies
6
Views
487
derfloh
derfloh
4thright
  • Locked
  • Question
IP Office 500 v2 - T1 Trunking
Replies
14
Views
1K
derfloh
derfloh
Zero6
  • Locked
  • Question
Ip office cold start and power failure
Replies
3
Views
274
biv343
biv343
L
  • Question
analogue trunk problem ip office
Replies
4
Views
347
LuigiEspo
L
timbreck
  • Locked
  • Question
Connecting avaya ip office 500 v2 to a valcom page system 1
2
Replies
26
Views
2K
timbreck
timbreck

Part and Inventory Search

Sponsor

Back
Top