Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1826
Views
0
Helpful
1
Replies

UC560 call monitoring

Ricardo Munioz Cabero
Level 1
Level 1

‎02-03-2012 01:52 PM - edited ‎03-21-2019 05:17 AM

Hi to all,

Previously: I had a SPA9000 with some other devices and IP Phones (more info is not not relevant). The thing is that when browsing to the SPA's IP address I could see which phones were making or receiving a call, the number they were dialing, and the line that was bussy.

Now: I have an UC560, with the CCA v3.1.1 installed on my laptop, I'm trying to see the same information but can't find an option for it. Not sure if I'm missing something, need an additional software, or if it's not possible with this system. I think it should be a very simple thing since it was very easy on a very inferior system such as the SPA9000.

Thanks in advance for your help.

Labels:
0 Helpful
1 Reply 1

mcasimirc63
Level 4
Level 4

‎02-04-2012 03:05 PM

The CDR's that the UC500/CME spits out are very detailed raw files.  It would take a long time to parse through and look for what you are requesting. 

The easiest way to go about it is to check into the third party apps that are on this page.  They would make the reports very easy to read

https://supportforums.cisco.com/docs/DOC-9780

Below is one call I made to UPS which lasted 16 seconds.

02-04-2012          17:49:38          Local7.Notice          192.168.10.1          144163: 286119: Feb  4 23:00:46.896: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:02/04/2012 18:00:31.052,cgn:211,cdn:18007425877,frs:0,fid:971,fcid:DD977C6E4EBA11E188A5BE6F963B151D,legID:9FDF,bguid:DD977C6E4EBA11E188A5BE6F963B151D

02-04-2012          17:49:37          Local7.Notice          192.168.10.1          144162: 286118: Feb  4 23:00:46.896: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId DD977C6E4EBA11E188A5BE6F963B151D, SetupTime 18:00:34.846 EST Sat Feb 4 2012, PeerAddress 18007425877, PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 18:00:38.676 EST Sat Feb 4 2012, DisconnectTime 18:00:46.896 EST Sat Feb 4 2012, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 388, TransmitBytes 65184, ReceivePackets 409, ReceiveBytes 65440

02-04-2012          17:49:37          Local7.Notice          192.168.10.1          144161: 286117: Feb  4 23:00:46.876: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:02/04/2012 18:00:28.640,cgn:211,cdn:,frs:0,fid:970,fcid:DD977C6E4EBA11E188A5BE6F963B151D,legID:9FDE,bguid:DD977C6E4EBA11E188A5BE6F963B151D

02-04-2012          17:49:37          Local7.Notice          192.168.10.1          144160: 286116: Feb  4 23:00:46.876: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId DD977C6E4EBA11E188A5BE6F963B151D, SetupTime 18:00:28.646 EST Sat Feb 4 2012, PeerAddress 211, PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 18:00:38.676 EST Sat Feb 4 2012, DisconnectTime 18:00:46.876 EST Sat Feb 4 2012, CallOrigin 2, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 388, ReceiveBytes 62080

02-04-2012          17:49:26          Local7.Notice          192.168.10.1          144159: 286115: Feb  4 23:00:34.836: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:02/04/2012 18:00:31.052,cgn:211,cdn:18007425877,frs:0,fid:971,fcid:DD977C6E4EBA11E188A5BE6F963B151D,legID:9FDF,bguid:DD977C6E4EBA11E188A5BE6F963B151D

02-04-2012          17:49:25          Local7.Notice          192.168.10.1          144158: 286114: Feb  4 23:00:34.836: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId DD977C6E4EBA11E188A5BE6F963B151D, SetupTime 18:00:33.586 EST Sat Feb 4 2012, PeerAddress 18007425877, PeerSubAddress , DisconnectCause 22  , DisconnectText no circuit (34), ConnectTime 18:00:34.836 EST Sat Feb 4 2012, DisconnectTime 18:00:34.836 EST Sat Feb 4 2012, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0

02-04-2012          17:49:25          Local7.Notice          192.168.10.1          144157: 286113: Feb  4 23:00:33.572: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:02/04/2012 18:00:31.052,cgn:211,cdn:18007425877,frs:0,fid:971,fcid:DD977C6E4EBA11E188A5BE6F963B151D,legID:9FDF,bguid:DD977C6E4EBA11E188A5BE6F963B151D

02-04-2012          17:49:24          Local7.Notice          192.168.10.1          144156: 286112: Feb  4 23:00:33.572: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId DD977C6E4EBA11E188A5BE6F963B151D, SetupTime 18:00:32.322 EST Sat Feb 4 2012, PeerAddress 18007425877, PeerSubAddress , DisconnectCause 22  , DisconnectText no circuit (34), ConnectTime 18:00:33.572 EST Sat Feb 4 2012, DisconnectTime 18:00:33.572 EST Sat Feb 4 2012, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0

02-04-2012          17:49:23          Local7.Notice          192.168.10.1          144155: 286111: Feb  4 23:00:32.312: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:02/04/2012 18:00:31.052,cgn:211,cdn:18007425877,frs:0,fid:971,fcid:DD977C6E4EBA11E188A5BE6F963B151D,legID:9FDF,bguid:DD977C6E4EBA11E188A5BE6F963B151D

02-04-2012          17:49:22          Local7.Notice          192.168.10.1          144154: 286110: Feb  4 23:00:32.312: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId DD977C6E4EBA11E188A5BE6F963B151D, SetupTime 18:00:31.062 EST Sat Feb 4 2012, PeerAddress 18007425877, PeerSubAddress , DisconnectCause 22  , DisconnectText no circuit (34), ConnectTime 18:00:32.312 EST Sat Feb 4 2012, DisconnectTime 18:00:32.312 EST Sat Feb 4 2012, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0

0 Helpful
Customers Also Viewed These Support Documents