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!

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

SYSTEM MONITOR CALL LOGGING TRACE OUTPUT DETAILS

Status
Not open for further replies.

edcelf

Vendor
Oct 7, 2019
12
PH
Hi Guys,

I need help with understanding the trace details of Call Logging in IP Office System Monitor so I can create a very simple call logger using Microsoft Excel.

IP Office Version is R11

Here I have a sample trace:

CALL:2020/06/2216:38,00:02:49,000,1224,O,09178616472,809178616472,RTigbao,,,0,,"",1,n/a

my understanding of the trace per comma:

CALL:date time,duration of call,(no idea),extension number,call direction,called number,dialled number,User Name,(no idea),(no idea),(no idea),(no idea),(no idea),(no idea),(no idea)

As you can see there is some output that you can understand at a glance but I have no idea for the blanks and other trace outputs. I have compared this to an SMDR Output and CDR Output but they do not coincide in all areas of the trace output. I hope you get what I'm trying to say and help a novice such as myself.

Many thanks in advance, Sirs!
 
@TouchToneTommy
I have read the document you mentioned, output details of SMDR do not align with the System Monitor trace I have provided.

I have been looking for documents regarding trace output details for System Monitor, but I have found none.
 
Start IP Office Manager. Press F1. Go to the chapter on SMDR output. The System Monitor call output is repeating the SMDR output.

But since I happen to have my own notes here as I was looking at the 11.1 outputs recently:

[ul]
[li]01. 2020/06/18 09:18:06, (Call Start Time)[/li]
[li]02. 00:00:02, (Connected Time)[/li]
[li]03. 2, (Ring Time)[/li]
[li]04. 209, (Caller)[/li]
[li]05. O, (Direction)[/li]
[li]06. 210, (Called)[/li]
[li]07. 210, (Dialled)[/li]
[li]08. , (Account Code)[/li]
[li]09. 1, (Is Internal)[/li]
[li]10. 1000000, (Call ID)[/li]
[li]11. 0, (Continuation)[/li]
[li]12. E209, (Party1Device)[/li]
[li]13. Extn209, (Party1Name)[/li]
[li]14. E210,(Party2Device)[/li]
[li]15. Extn210, (Party2Name)[/li]
[li]16. 0, (Hold Time)[/li]
[li]17. 0, (Park Time)[/li]
[li]18. , (Authorization Valid)[/li]
[li]19. , (Authorization Code)[/li]
[li]20. , (User Charge)[/li]
[li]21. , (Call Charge)[/li]
[li]22. , (Currency)[/li]
[li]23. , (Amount at Last User Change)[/li]
[li]24. , (Call Units)[/li]
[li]25. , (Units at Last User Change)[/li]
[li]26. , (Cost Per Unit)[/li]
[li]27. , (Mark Up)[/li]
[li]28. , (External Targeting Cause)[/li]
[li]29. , (External Targeter ID)[/li]
[li]30. , (External Targeted Number)[/li]
[li]31. 192.168.0.36, (Calling Party Server IP Address)[/li]
[li]32. 1002, (Unique Call ID for the Caller Extension)[/li]
[li]33. 192.168.0.36, (Called Party Server IP Address)[/li]
[li]34. 1004, (Unique Call ID for the Called Extension)[/li]
[li]35. 2020/06/18 08:18:10, (SMDR Record Time)[/li]
[li]36. 0 (Caller Consent Directive)[/li]
[/ul]


Stuck in a never ending cycle of file copying.
 
Thanks guys.

I was tracing the call logs when in fact I can fetch SMDR Output using System Monitor.

@sizbut
@@TouchToneTommy

Appreciate the help guys, the document and the notes will be very useful.
 
Why would you use System Monitor instead of just catching SMDR to a CSV file?

"Trying is the first step to failure..." - Homer
 
@janni78

How do you fetch SMDR Output to CSV File? Are you using a third-party software?

It would be much better if I can fetch it to a CSV file. Appreciate it if you can help me with this :)
 
@janni78

Many thanks for this, this is really helpful! :)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top