TO CONFIGURE CISCO CALL MANAGER FOR COMM ONE

Cisco Call Manager sends raw call records to either an FTP or SFTP server that you set up to capture those records.  Here are the steps you need to take to set up your Cisco Call Manager for Comm One Call Accounting.

 

  1. Set up an FTP or SFTP Server to capture your call records.  There are a number of free FTP servers that work well for this.  Please contact your Cisco Tech to see which one you should use for your system.

  2. Set your FTP or SFTP Server to save the logs to the \\log_ftp directory under your Comm One Folder.

  3. Put the FTP/SFTP settings in the Cisco Call Manager so it knows where to send the call records.

  4. Set the Comm One Sofware to look to the \\log_ftp directory for those call records.
     

CISCO CDR FLAT FILE INTERVAL

By default, Cisco Call Manager saves a call log file every minute.  This causes problems for windows computers because the directory where the logs are stored can get very full.  Eventually, it can cause windows directory problems and cause the windows directory to become corrupt because of the number of files in that directory.

 

To resolve this problem you should adjust the CDRFlatFileInterval in the Cisco Call Manager so that your log files are only saved once or twice per day.  That way the directory won't fill up and Comm One will be able to process the logs that you capture.

 

CISCO CDR & CMR RECORDS

The CISCO System sends both CDR and CMR Records.  Only CDR Records are required to do Call Accounting with Comm One

 

CISCO ENTERPRISE PARAMETERS FOR SMDR

You can configure these parameters on the Enterprise Parameters Configuration page in the Cisco Unified CallManager Administration. To access the Enterprise Parameters Configuration page, open Cisco Unified CallManager Administration and select System -> Enterprise Parameters.

 

CISCO CDR FLATFILEINTERVAL

 AKA CDR File Time Interval

This is a parameter for Cisco Unified CallManager that determines the number of seconds to write to a CDR file before opening another one. For example, if this

CDRFlatFileInterval is 1 minute (default), Cisco Unified CallManager will write a minutes worth of CDRs into each file. If the CDRFlatFileInterval is 60 minutes, then Unified CM will write an hours worth of CDRs into each file.  We recommend that you set this number to 240 or higher.

 

CISCO CALL MANAGER CALL ACCOUNTING FIELDS

Here is a list of call accounting fields that are supported by Cisco Call Manager phone systems:

 

  1. Cdr Record Type

  2. Date Time Origination

  3. Date Time Origination

  4. Original Node Id

  5. Calling Party Number

  6. Destination Node Id

  7. Original Called Party Number

  8. Final Called Party Number

  9. Pkid

  10. Duration

  11. Authorization Code Value

  12. Call duration

  13. Direction

  14. Call type

  15. Dialed phone

  16. Caller phone

  17. Trunk

  18. Extension

  19. Global CallID call Manager Id

  20. Global CallID call Id

  21. Original Leg Call Identifier

  22. Original Span

  23. Original Ip Addr

  24. Calling Party Unicode Login UserID

  25. Original Cause location

  26. Original Cause value

  27. Original Precedence Level

  28. Original Media Transport Address IP

  29. Original Media Transport Address Port

  30. Original Media Cap payload Capability

  31. Original Media Cap max Frames Per Packet

  32. Original Media Cap g723 Bit Rate

  33. Original Video Cap Codec

  34. Original Video Cap Bandwidth

  35. Original Video Cap Resolution

  36. Original Video Transport Address IP

  37. Original Video Transport Address Port

  38. Original RSVP Audio Stat

  39. Original RSVP Video Stat

  40. Destination Leg Identifier

  41. Destination Span

  42. Destination Ip Addr

  43. Final Called Party Unicode Login UserID

  44. Destination Cause location

  45. Destination Cause value

  46. Destination Precedence Level

  47. Destination Media Transport Address IP

  48. Destination Media Transport Address Port

  49. Destination Media Cap payload Capability

  50. Destination Media Cap max Frames Per Packet

  51. Destination Media Cap g723 Bit Rate

  52. Destination Video Cap Codec

  53. Destination Video Cap Bandwidth

  54. Destination Video Cap Resolution

  55. Destination Video Transport Address IP

  56. Destination Video Transport Address Port

  57. Destination RSVP Audio Stat

  58. Destination RSVP Video Stat

  59. Date Time Connect

  60. Date Time Disconnect

  61. Last Redirect Dn

  62. Original inal Called Party Number Partition

  63. Calling Party Number Partition

  64. Final Called Party Number Partition

  65. Last Redirect Dn Partition

  66. Original Device Name

  67. Destination Device Name

  68. Original Call Termination On Behalf Of

  69. Destination Call Termination On Behalf Of

  70. Original Called Party Redirect On Behalf Of

  71. Last Redirect Redirect On Behalf Of

  72. Original Called Party Redirect Reason

  73. Last Redirect Redirect Reason

  74. Destination Conversation Id

  75. Global Call Id ClusterID

  76. Join On Behalf Of

  77. Comment

  78. Auth Code Description

  79. Authorization Level

  80. Client Matter Code

  81. Original DTMF Method

  82. Destination DTMF Method

  83. Call Secured Status

  84. Original Conversation Id

  85. Original Media Cap Bandwidth

  86. Destination Media Cap Bandwidth

  87. Outpulsed Calling Party Number

  88. Outpulsed Called Party Number

  89. Original Ipv4v6 Addr

  90. Destination Ipv4v6 Addr

  91. Original Video Cap Codec Channel2

  92. Original Video Cap Bandwidth Channel2

  93. Original Video Cap Resolution Channel2

  94. Original Video Transport Address IP Channel2

  95. Original Video Transport Address Port Channel2

  96. Original Video Channel Role Channel2

  97. Destination Video Cap Codec Channel2

  98. Destination Video Cap Bandwidth Channel2

  99. Destination Video Cap Resolution Channel2

  100. Destination Video Transport Address IP Channel2

  101. Destination Video Transport Address Port Channel2

  102. Destination Video Channel Role Channel2

  103. Incoming ProtocolID

  104. Incoming Protocol Call Ref

  105. Outgoing ProtocolID

  106. Outgoing Protocol Call Ref

  107. Current Routing Reason

  108. Original Routing Reason

  109. Last Redirecting Routing Reason

  110. Hunt Pilot Partition

  111. Hunt PilotDN

  112. Called Party Pattern Usage

  113. IncomingICID

  114. Incoming OrigIOI

  115. Incoming TermIOI

  116. OutgoingICID

  117. Outgoing OrigIOI

  118. Outgoing TermIOI

  119. Outpulsed Original Called Party Number

  120. Outpulsed Last Redirecting Number

  121. Was Call Queued

  122. Total Wait Time In Queue

  123. Calling Party Number uri

  124. Original inal Called Party Number uri

  125. Final Called Party Number uri

  126. Last Redirect Dn uri

  127. Mobile Calling Party Number

  128. Final Mobile Called Party Number

  129. Original Mobile Device Name

  130. Destination Mobile Device Name

  131. Original Mobile Call Duration

  132. Destination Mobile Call Duration

  133. Mobile Call Type

  134. Original inal Called Party Pattern

  135. Final Called Party Pattern

  136. Last Redirecting Party Pattern

  137. Hunt Pilot Pattern

COMM ONE CALL ACCOUNTING

FAQ-1126 Cisco Call Manager

 

 

Technical Support

138 E 12300 S Ste #C102

Draper, UT  84020

(385) 529-5819

support@commone.com

 

FAQ-INDEX Cisco Call Manager Comm One Integration

Posted: 02/02/2017

Updated: 06/12/2019

Author: Comm One Technical Support

 

 

 

Comm One Logo - Grey - WIX Header.jpg