Cisco Call Manager (CSV) v6. Параметры соединения и формат данных SMDR/CDR

Данные ниже соответствуют только программе Advanced PBX Data Logger и могут быть не применимы для других программных продуктов.

Cisco Unified Communications Manager

CDR Repository Manager

Within a Cisco Unified Communications Manager server or cluster, one instance of the CDR Repository Manager runs on the CDR Repository server or node. It manages CDR files that are received from the Cisco Unified Communications Manager nodes and periodically sends the files to the specified customer/third-party billing servers via FTP/SFTP. Our PBX Data Logger polls the FTP server and retrives new data. You should add the "File" data source type and configure a FTP or SFTP connection with the FTP server.

When the file arrives on the CDR Repository server or node, the CDR Repository Manager detects it. The system archives the file in a directory that is dedicated to the date that is indicated by the UTC timestamp that was placed in the file name when the file was created.

If any external billing server is specified in the CDRM configuration, the system creates an empty file in each of the corresponding folders for CAR and the billing servers, if CAR or the corresponding billing server is activated. The CDR Agent monitors new CDR/CMR files that are generated on CallManager servers or nodes by the call processing component. It sends the files to the CDR Repository node and then deletes the local copy after the file is pushed out. The file sender component of the CDR Repository Manager detects these empty files and sends the file to the destination with the specified method. If the delivery is successful, the system removes the empty file in the destination directory. Every Cisco Unified Communications Manager can generate one CDR file and one CMR file every minute for up to 1 hour. You can configure the maximum disk space that is used for storage of CDR files in the CDR Repository through provisioning. The File Manager component of the CDR Repository Manager runs hourly. When the File Manager runs, it deletes files with dates outside the configured preservation duration. It also checks whether disk usage has exceeded the high water mark. If so, the system deletes the processed CDR files until the low water mark is reached, starting with the oldest files. However, if any CDR file to be deleted was not successfully sent to the specified billing server, the system leaves it in the CDR Repository and raises a notification or alarm. The system creates a flag file during the configured maintenance window, which denies access to the CDR files for the CDR onDemand Service. The system removes the flag file after the maintenance window expires.

For detailed procedures on configuring the CDR Repository Manager and customer billing servers, see "Cisco Unified Communications Manager Call Detail Records Administration Guide"


Data flow diagram

CDR fields

For detailed description of CDR fields, see here:
Cisco CallManager 6
Cisco CallManager 7
Cisco CallManager 8

Configuring PBX Data Logger

1. Create a new "File" data source.
2. Click "Actions → Add...".
3. Select "FTP" and configure connection with your FTP server.
4. Adjust read options.

Adding a new file data source for Cisco Call Manager

Cisco Call Manager. Data source selection dialog.

Cisco Call Manager. Folders and files.

Cisco Call Manager

Configuring FTP connection to Cisco Call Manager




Adjusting read options for Cisco Call Manager

Данные, извлекаемые PBX Data Logger

ОписаниеТип данныхИмя колонки
Cdr Тип записиintegerCDRRECORDTYPE
Date Time OriginationintegerCALL_TIME
Date Time OriginationintegerCALL_TIME2
Original Узел IdintegerORIGNODEID
Вызывающая сторона NumberstringCALLINGPARTYNUMBER
Конечный Узел IdintegerDESTNODEID
Original Вызываемая сторона NumberstringORIGINALCALLEDPARTYNUMBER
Код авторизации ValuestringAUTH
Длительность звонкаdatetimeCALL_DURATION
Тип звонкаstringCALL_TYPE
Набранный номерstringDIALED_PHONE
Вызывающий телефонstringCALLER_PHONE
Global CallID call Manager IdintegerGLOBALCALLID_CALLMANAGERID
Global CallID Идентификатор вызоваintegerGLOBALCALLID_CALLID
Original Leg Идентификатор вызоваentifierintegerORIGLEGCALLIDENTIFIER
Original SpanintegerORIGSPAN
Original Ip AddrintegerORIGIPADDR
Вызывающая сторона Unicode Login UserIDstringCALLINGPARTYUNICODELOGINUSERID
Original Cause locationintegerORIGCAUSE_LOCATION
Original Cause valueintegerORIGCAUSE_VALUE
Original Precedence LevelintegerORIGPRECEDENCELEVEL
Original Media Transport Address IPintegerORIGMEDIATRANSPORTADDRESS_IP
Original Media Transport Address PortintegerORIGMEDIATRANSPORTADDRESS_PORT
Original Media Cap payload CapabilityintegerORIGMEDIACAP_PAYLOADCAPABILITY
Original Media Cap max Frames Per PacketintegerORIGMEDIACAP_MAXFRAMESPERPACKET
Original Media Cap g723 Bit RateintegerORIGMEDIACAP_G723BITRATE
Original Video Cap CodecintegerORIGVIDEOCAP_CODEC
Original Video Cap BandwidthintegerORIGVIDEOCAP_BANDWIDTH
Original Video Cap ResolutionintegerORIGVIDEOCAP_RESOLUTION
Original Video Transport Address IPintegerORIGVIDEOTRANSPORTADDRESS_IP
Original Video Transport Address PortintegerORIGVIDEOTRANSPORTADDRESS_PORT
Конечный Leg IdentifierintegerDESTLEGIDENTIFIER
Конечный SpanintegerDESTSPAN
Конечный Ip AddrintegerDESTIPADDR
Final Вызываемая сторона NumberstringFINALCALLEDPARTYNUMBER
Final Вызываемая сторона Unicode Login UserIDstringFINALCALLEDPARTYUNICODELOGINUSERID
Конечный Cause locationintegerDESTCAUSE_LOCATION
Конечный Cause valueintegerDESTCAUSE_VALUE
Конечный Precedence LevelintegerDESTPRECEDENCELEVEL
Конечный Media Transport Address IPintegerDESTMEDIATRANSPORTADDRESS_IP
Конечный Media Transport Address PortintegerDESTMEDIATRANSPORTADDRESS_PORT
Конечный Media Cap payload CapabilityintegerDESTMEDIACAP_PAYLOADCAPABILITY
Конечный Media Cap max Frames Per PacketintegerDESTMEDIACAP_MAXFRAMESPERPACKET
Конечный Media Cap g723 Bit RateintegerDESTMEDIACAP_G723BITRATE
Конечный Video Cap CodecintegerDESTVIDEOCAP_CODEC
Конечный Video Cap BandwidthintegerDESTVIDEOCAP_BANDWIDTH
Конечный Video Cap ResolutionintegerDESTVIDEOCAP_RESOLUTION
Конечный Video Transport Address IPintegerDESTVIDEOTRANSPORTADDRESS_IP
Конечный Video Transport Address PortintegerDESTVIDEOTRANSPORTADDRESS_PORT
Date Time ConnectdatetimeDATETIMECONNECT
Date Time DisconnectdatetimeDATETIMEDISCONNECT
Last Redirect DnstringLASTREDIRECTDN
Original inal Вызываемая сторона Number PartitionstringORIGINALCALLEDPARTYNUMBERPARTITION
Вызывающая сторона Number PartitionstringCALLINGPARTYNUMBERPARTITION
Final Вызываемая сторона Number PartitionstringFINALCALLEDPARTYNUMBERPARTITION
Last Redirect Dn PartitionstringLASTREDIRECTDNPARTITION
Original Device NamestringORIGDEVICENAME
Конечный Device NamestringDESTDEVICENAME
Original Call Termination On Behalf OfintegerORIGCALLTERMINATIONONBEHALFOF
Конечный Call Termination On Behalf OfintegerDESTCALLTERMINATIONONBEHALFOF
Original Вызываемая сторона Redirect On Behalf OfintegerORIGCALLEDPARTYREDIRECTONBEHALFOF
Last Redirect Redirect On Behalf OfintegerLASTREDIRECTREDIRECTONBEHALFOF
Original Вызываемая сторона Redirect ReasonintegerORIGCALLEDPARTYREDIRECTREASON
Last Redirect Redirect ReasonintegerLASTREDIRECTREDIRECTREASON
Конечный Conversation IdintegerDESTCONVERSATIONID
Global Идентификатор вызова ClusterIDstringGLOBALCALLID_CLUSTERID
Join On Behalf OfintegerJOINONBEHALFOF
Код авторизации DescriptionstringAUTHCODEDESCRIPTION
Authorization LevelintegerAUTHORIZATIONLEVEL
Client Matter CodestringCLIENTMATTERCODE
Original DTMF MethodintegerORIGDTMFMETHOD
Конечный DTMF MethodintegerDESTDTMFMETHOD
Call Secured StatusintegerCALLSECUREDSTATUS
Original Conversation IdintegerORIGCONVERSATIONID
Original Media Cap BandwidthintegerORIGMEDIACAP_BANDWIDTH
Конечный Media Cap BandwidthintegerDESTMEDIACAP_BANDWIDTH

Замечание: Продукты и компании, указанные здесь используются только для обозначение и идентификации и могут быть торговыми и/или зарегистрированными марками соответствующих компаний.