A method and electronic device for detecting the integrity of telephone recording data

By parsing the call detail records (CDRs) of the ZXD1000 digital PBX and matching them with the recording server, fully automated detection of recording data integrity was achieved. This solved the problems of low detection efficiency and poor accuracy in existing technologies, met real-time monitoring and compliance requirements, and improved the automation and security of recording data detection.

CN123123501APending Publication Date: 2026-11-17GUANGZHOU METRO GRP CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611349225.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-02
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing technologies cannot achieve fully automated and accurate detection of the integrity of recorded data. Furthermore, manual spot checks are time-consuming, labor-intensive, and susceptible to human factors, failing to meet the requirements for real-time monitoring of recording integrity and making it difficult to detect potential recording loss issues in a timely manner.

Method used

By parsing the call detail records (CDRs) file of the ZXD1000 digital PBX, call records are obtained and matched with the recording records in the recording server. A multi-rule matching algorithm is used to determine the integrity of the recording data, and the end marker file is combined to ensure that the data is exported completely, thus achieving fully automated detection.

Benefits of technology

It has achieved fully automated detection of audio recording data, reduced labor costs, improved detection efficiency and accuracy, ensured that potential recording deficiencies are detected in a timely manner, met real-time monitoring and compliance requirements, and enhanced the level of security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123501A_ABST
    Figure CN123123501A_ABST
Patent Text Reader

Abstract

This invention relates to the field of recording data detection technology, and more particularly to a method and electronic device for detecting the integrity of telephone recording data. The method includes: exporting call detail records (CDRs) from a ZXD1000 digital PBX; parsing the CDRs to obtain call logs; matching the call logs with recording logs in a recording server; determining the integrity of the recording data based on the matching result; and displaying the detection results and statistical data intuitively through a user interface. By parsing the CDRs of the ZXD1000 digital PBX and accurately matching them with the recording logs, the invention achieves full automation of recording integrity detection, completely eliminating the detection difficulties caused by the randomness of dispatch calls. This invention significantly reduces the time and manpower costs of manual comparison, avoids subjective misjudgments and detection delays, and ensures that potential problems such as missing recordings are detected in a timely manner.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of audio recording data detection technology, and in particular to a method and electronic device for detecting the integrity of telephone recording data. Background Technology

[0002] In rail transit operation and management, wired dispatch recording systems play a crucial role. Recordings of conversations between dispatchers, station staff, drivers, and other personnel are not only vital for daily dispatch and command work but also key evidence for operational incident analysis and accident investigation. With the rapid development of the rail transit industry and the continuous improvement of safety management requirements, the state has successively issued normative documents such as the "Technical Specifications for the Operation of Urban Rail Transit Communication Systems" (Jiaobanyun

[2023] No. 67), which clearly require that the network management function of the centralized recording subsystem should be able to monitor the operating status and recording integrity of the centralized recording equipment in real time, and display fault information and alarm prompts in real time. This places higher technical requirements on the recording data integrity detection function.

[0003] Currently, the integrity check of recordings on existing operational lines mainly relies on manual spot checks. On-duty personnel need to manually check and verify the recordings from different time periods and dispatch seats daily, comparing call logs with the recording files to determine if the recordings are complete. Some systems also use a simple continuity check method, which checks whether the recording files exist consecutively in chronological order to preliminarily determine if the recording system is working properly. However, due to the significant randomness of wired dispatch calls—the order, duration, and frequency of calls cannot be predetermined, and they cannot follow a pre-planned scenario and actions—the above-mentioned check methods face many limitations in practical applications.

[0004] Existing technologies have significant limitations and drawbacks. First, due to the randomness of the order and combination of wired dispatch calls, which cannot follow predetermined scenarios and actions, it is impossible to accurately determine the integrity of recordings using only simple continuity detection methods. Existing operational lines have never been able to achieve fully automated integrity detection. Second, manual sampling requires analyzing and evaluating each recording individually when dealing with massive amounts of data. This is not only time-consuming and labor-intensive but also susceptible to subjective human factors, making it difficult to guarantee the accuracy and consistency of the detection results, leading to frequent omissions and misjudgments. Furthermore, manual sampling suffers from significant lag and incomplete coverage. Equipment safety hazards such as missing recordings are difficult to detect and eliminate in a timely manner. It may only be discovered that critical recording data has been lost when recording evidence is needed after an operational accident. Finally, existing detection methods cannot meet the compliance requirements of the new standard for real-time monitoring of recording integrity and are insufficient to reach the technological advancements stipulated in the "Technical Specifications for the Operation of Urban Rail Transit Communication Systems," thus hindering the improvement of system reliability and compliance. Summary of the Invention

[0005] In order to solve the problems existing in the prior art, the present invention aims to provide a method and electronic device for detecting the integrity of telephone recording data, which can realize the automatic detection of recording integrity.

[0006] To achieve the above objectives, the present invention adopts the following technical solution: A method for detecting the integrity of telephone recording data includes: Export call detail records (CDRs) from a ZXD1000 digital PBX; The call log is obtained by parsing the dialog box file. The call logs are matched with the recording logs in the recording server, and the completeness of the recording data is determined based on the matching results.

[0007] As a further improvement of the present invention, the step of exporting call detail records (CDRs) from the ZXD1000 digital program-controlled exchange includes: After a user makes a call, the ZXD1000 digital program-controlled exchange writes the call data into the first file; The first file is renamed to obtain the call detail record (CDR) file.

[0008] As a further improvement of the present invention, after obtaining the call detail record (CDR) file, the following steps are also included: After the call detail record (CDR) file is detected, it is transferred to the FTP server. After the call detail record (CDR) file is transferred, upload an end marker file with the same name as the CDR file; When retrieving call detail records (CDRs) from an FTP server, the end marker file is used to determine whether the CDR has been completely exported.

[0009] As a further improvement of the present invention, the call record includes: the calling number, the called number, the call start time, and the call type; The step of matching call logs with recording logs in the recording server and determining whether the recording data is complete based on the matching result includes: Based on the called number and call start time in the call record, and the called number, recording start time, and recording end time in the recording record, the recording record corresponding to the called number is matched from the recording server; Based on the recording records, retrieve the associated caller recording records from the recording server; The associated caller recordings are aggregated to obtain a list of recordings; Find the called recording in the call log list that matches both the call start time and the called number in the call log. If there is only one recording record and it is a called party recording record, and the call record is a called party recording record, if the group call initiator can be found, the call type is determined to be a group call. When determining that the call type is a group call, it is then determined whether the called party recording record is complete.

[0010] As a further improvement of the present invention, if no recording record corresponding to the called number is matched from the recording server based on the called number and call start time of the call record, and the call record is the calling call record, then the recording record corresponding to the calling number is matched from the recording server based on the calling number and call start time of the call record, as well as the recording start time and recording end time of the recording record. If no matching recording record is found in the recording server based on the called number and call start time of the call record, and the call record is a called call record, then the recording record corresponding to the calling number is matched from the recording server based on the called number and call start time of the call record, as well as the recording start time and recording end time of the recording record. Based on the recording records corresponding to the caller's number, retrieve the associated called party recording records from the recording server; The associated called party recordings are aggregated to obtain a recording list.

[0011] As a further improvement of the present invention, if no associated calling or called recording record is found in the recording server, the recording record corresponding to the called number is found in the recording server according to the group call rules. The related audio recordings are then compiled to obtain a list of audio recordings.

[0012] As a further improvement of the present invention, if no called recording record is found in the recording record list that matches both the call start time and the called number of the call record, the call direction of the call record is determined. If the call record is the calling record, then according to the first set rule, find the called recording record; If the call record is a called party's call record, then the called party's recording record will be searched according to the second set rule.

[0013] As a further improvement of the present invention, when it is confirmed that there is only one recording record and it is a called party recording record, and the call record is a called party recording record, the method further includes: Collect other called party recordings and search for the group call initiator according to the group call initiator search rules; the group call initiator search rules are: the fourth digit of the called number in the recording is equal to the fourth digit of the called number in the call record, and the calling number in the recording is equal to the called number in the recording. If the group call initiator is found, the call type is determined to be a group call; if the group call initiator is not found, the call type is determined to be a single call. If the conditions are not met (there is only one recorded record and it is a called party's recorded record), and the call record is also a called party's record, then the call type will be determined as a single call.

[0014] As a further improvement of the present invention, the step of determining whether the called party's recording is complete includes: Confirm whether the called party's recording records contain matching recording data; If no matching recording data is found, the record integrity check result is "recording missing". If matching recording data exists, determine whether the audio file corresponding to the called party's recording can be obtained from the FTP server; If the audio file cannot be obtained, the integrity check result is recorded as file missing; If the audio file can be obtained, the record integrity check result is normal.

[0015] The present invention also provides an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; the memory is used to store computer programs; and the processor is used to implement the telephone recording data integrity detection method described above when executing the program stored in the memory.

[0016] Compared with existing technologies, this invention has the following advantages: It effectively overcomes the limitations of traditional manual spot checks and simple continuous detection. By analyzing the call detail records (CDRs) of the ZXD1000 digital program-controlled exchange and accurately matching them with recorded audio, it achieves fully automated recording integrity detection, completely eliminating the detection challenges caused by the randomness of dispatch calls. This invention significantly reduces the time and manpower costs of manual comparison, avoids subjective misjudgments and detection delays, and ensures that potential problems such as missing recordings are detected in a timely manner. Simultaneously, it achieves real-time monitoring and compliance alarms for recording data, fully meeting the latest national operational technical specifications and significantly improving the safety assurance level of rail transit dispatching and command. Attached Figure Description

[0017] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments.

[0018] Figure 1 This is a flowchart of the telephone recording data integrity detection method described in this invention; Figure 2 This is another flowchart of the telephone recording data integrity detection method described in this invention; Figure 3 This is a flowchart of step S1 of the present invention; Figure 4 Automatically export the result image from the call detail record (CDR) file and its end marker file; Figure 5 Decoding and analysis diagram of billing form for ZXD1000 digital program-controlled exchange; Figure 6 This is a flowchart of step S3 of the present invention; Figure 7 This is a graph showing the results of the audio recording data integrity check. Figure 8 A statistical chart of daily integrity check results; Figure 9 A statistical chart of monthly integrity test results; Figure 10 A statistical chart showing the completeness of historical audio recordings; Figure 11 A status diagram of the daily integrity check task execution; Figure 12 The image shows the comparison results of automatic export of call detail records (CDR) files and call log parsing. Detailed Implementation

[0019] To make the technical problems solved by the present invention, the technical solutions adopted, and the technical effects achieved clearer, the technical solutions of the embodiments of the present invention will be further described in detail below. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0020] This invention discloses a method for detecting the integrity of telephone recording data. Before implementation, the following hardware devices are required: a ZXD1000 digital program-controlled exchange, a recording server, a recording integrity detection server, and a database server. The ZXD1000 digital program-controlled exchange is used to generate and store call detail record (CDR) data, generating 32 bytes of call record for each call. The recording server has a built-in Oracle database for storing recordings and audio files. The recording integrity detection server is an FTP service used to receive CDR files and run the detection software and user interface. The database server deploys a MySQL database for storing detection results and statistical data.

[0021] like Figure 1 and Figure 2 As shown, the method for detecting the integrity of telephone recording data includes: S1. Export call detail records (CDRs) from the ZXD1000 digital PBX. The ZXD1000 digital PBX has a CDR recording module, which only writes call data to the CDR file and does not have a file export function. The export time interval can be set, such as every two hours. The entire export process runs automatically during normal telephone service use, without user awareness or manual intervention. Based on this step, reliable raw CDR data can be obtained.

[0022] As one implementation method, such as Figure 3 and Figure 4 As shown, step S1 includes: After a user makes a call, the ZXD1000 digital PBX writes the call data to a first file; the first file is then renamed to obtain a call detail record (CDR) file. Upon detecting the CDR file, it is transferred to an FTP server; after the CDR file transfer is complete, an end-of-line marker file with the same name as the CDR file is uploaded; when retrieving the CDR file from the FTP server, the end-of-line marker file is used to determine whether the CDR file has been completely exported.

[0023] The specific implementation process is divided into the following three stages: The first stage involves splitting the call detail record (CDR) file. When an actor (user) makes a call, the CDR recording module writes the call data to the ZXD1000.bill file (the first file). At this point, the CDR export task renames this file to ZXD1000-xxx.bill_export, resulting in the CDR file. This operation leverages the inode feature of the Linux file system—the CDR recording module writes data via file descriptors rather than filenames. Therefore, renaming does not interrupt the ongoing write process, fundamentally resolving the read / write contention issue between CDR writing and file export.

[0024] The second stage involves the automatic creation of a new file. When the actor (user) dials the number again, the call detail record (CDR) module detects that the ZXD1000.bill file no longer exists (it has been renamed), automatically creates a new file with the same name, and writes the new CDR data to it. At this point, the old file (ZXD1000-xxx.bill_export) has completed all writing and becomes an independent, complete file that can be safely exported. The new and old files are independent of each other, ensuring the integrity and continuity of the data.

[0025] The third stage involves FTP file transfer. After detecting the ZXD1000-xxx.bill_export file, the call detail record (CDR) export task transfers it to the FTP server via the FTP protocol. Upon completion of the transfer, an additional finish flag file with the same name (ZXD1000-xxx.bill_export_finish) is uploaded. The receiving end uses the presence of this flag file as a criterion for complete CDR file export, preventing incomplete file parsing due to network interruptions, system power outages, or other anomalies. Local files are only deleted after confirming successful upload of both the CDR file and the finish flag file, ensuring no data loss. If the upload fails, the local files are retained and await re-upload in the next task.

[0026] This invention automatically exports call detail records (CDRs) in binary format from a PBX (Publicly-Controlled Switched Bank) and automatically parses these CDRs to obtain key data such as the calling number, called number, call start time, and call type, thus generating call records. To ensure complete export of CDRs, an end-of-file flag is used. Each exported CDR file generates a corresponding end-of-file flag (with the filename appended with "_finish"). Parsing only proceeds after the end-of-file flag is confirmed to exist, avoiding the processing of incomplete data. This invention utilizes the inode number and filename mapping feature of the Linux file system, splitting the CDR file into multiple independent files by renaming them. This ensures that the generation and export of CDR records are independent and do not affect each other, solving the problem of incomplete data caused by simultaneous CDR writing and exporting.

[0027] S2. The call log is obtained by parsing the dialog box file. For example... Figure 5 As shown, the process reads the completed call detail record (CDR) file, parses it into 32-byte records, extracts fields such as caller ID, called number, call start time, and call type to obtain the call records, and writes the call records to the MySQL database. The purpose of this step is to convert binary data into usable structured call records.

[0028] S3. Match the call logs with the recording records in the recording server. Determine the integrity of the recording data based on the matching results. The call logs include: caller ID, called ID, call start time, and call type. Retrieve the parsed call logs from MySQL and simultaneously connect to the recording server's Oracle database to retrieve the recording records. Execute a multi-rule matching algorithm to perform integrity checks.

[0029] If the recording server connection fails, the record integrity match result will be "Recording server cannot connect".

[0030] As one implementation method, such as Figure 6As shown, step S3 includes: S31. Based on the called number and call start time in the call record, and the called number, recording start time, and recording end time in the recording record, match the recording record corresponding to the called number from the recording server.

[0031] If the call record is an outgoing call record, the corresponding recording record is matched from the recording server according to the matching rules. The matching rules are: Call record called number = Recording record called number && Call record start time = Recording record start time.

[0032] If the call record is a called call record, the corresponding recording record is matched from the recording server according to the matching rules. The matching rules are: Call record called number = Recording record called number && Call record start time = Recording record start time.

[0033] If no matching recording record is found in the recording server based on the called number and call start time of the call record, and the call record is the calling party's call record, then the recording record corresponding to the calling party's number will be matched from the recording server based on the calling party's number, call start time of the call record, and the recording start time and recording end time of the recording record. The matching rule is: calling party's number in the call record = calling party's number in the recording record && recording start time <= call start time in the call record <= recording end time.

[0034] If no matching recording record is found in the recording server based on the called number and call start time in the call record, and the call record is a called call record, then the recording record corresponding to the calling number will be matched from the recording server based on the called number and call start time in the call record, as well as the recording start time and recording end time in the recording record. The matching rule is: called number in the call record = called number in the recording record && recording start time <= call start time in the call record <= recording end time.

[0035] S32-A: After matching the recording record corresponding to the called number from the recording server, search for the associated calling recording record from the recording server based on the found recording record. The matching rules include: the calling number of the found recording record is not empty && the calling number of the found recording record = the calling number of the recording record && (the start time of the recording record <= the start time of the found recording record <= the start time of the recording record || the start time of the found recording record <= the end time of the recording record <= the start time of the found recording record), and the called number of the found recording record is not empty && the called number of the found recording record = the called number of the recording record && (the start time of the recording record <= the start time of the found recording record <= the end time of the recording record || the start time of the found recording record <= the start time of the recording record <= the end time of the found recording record).

[0036] S32-B: After matching the recording record corresponding to the calling number from the recording server, based on the found recording record corresponding to the calling number, search for the associated called recording record from the recording server. The matching rules include: the called number of the found recording record is not empty && the called number of the found recording record = the called number of the recording record && (recording record start time <= found recording record start time <= recording record end time || found recording record start time <= recording record start time <= found recording record end time), and the calling number of the found recording record is not empty && the calling number of the found recording record = the calling number of the recording record && (recording record start time <= found recording record start time <= recording record start time || found recording record start time <= recording record end time <= found recording record start time).

[0037] S32-C: If no associated calling record or called record is found in the recording server, then the recording record corresponding to the called number is searched in the recording database according to the group call rules. The group call rules are: the called number in the found recording is not equal to the called number in the original recording, and (the start time of the original recording is less than or equal to the start time of the found recording, or the start time of the found recording is less than or equal to the end time of the found recording). Based on the found called record, the recording database is searched for a matching calling record. If a matching calling record is found, that called record is excluded.

[0038] S33-A: After finding the relevant calling party recording records from the recording server, the relevant calling party recording records are summarized to obtain a recording record list.

[0039] S33-B: After finding the relevant called party recording records from the recording server, the relevant called party recording records are summarized to obtain a recording record list.

[0040] S33-C. After searching for the recording record corresponding to the called number in the recording database, the recording records corresponding to the called number are summarized to obtain a recording record list.

[0041] S34. Find the called party recording record that matches the call start time in the call record from the recording record list. The search rule is: call record start time = recording record start time && call record called number = recording record called number.

[0042] If no called party recording is found in the recording record list that matches the call start time of the call record, the call direction of the call record is determined.

[0043] If the call record is the calling record, then according to the first set rule, the called record is searched; the first set rule is: the start time of the recording record <= the start time of the call record <= the end time of the recording record && the called number in the recording record = the called number in the call record && the calling number in the recording record = the calling number in the call record.

[0044] If the call record is a called call record, then according to the second set rule, find the called recording record; the second set rule is: the start time of the recording record <= the start time of the call record <= the end time of the recording record && the called number in the recording record = the called number in the call record.

[0045] S35. If there is only one recording record and it is a called recording record, and the call record is a called record, if the group call initiator can be found, the call type is determined to be a group call, and when the call type is determined to be a group call, it is determined whether the called recording record is complete.

[0046] Specifically, after finding the called party's recording, if both the calling and called party numbers are not empty, the calling party's recording is searched according to the rules. If the calling party number is empty, only the called party number is checked for equality; if the called party number is empty, only the calling party number is checked for equality. The rules are: called party's recording start time <= calling party's recording start time && called party's recording number == calling party's recording number && called party's recording number == calling party's recording number.

[0047] If there is only one recording record and it is a called party recording record, and the call record is a called party recording record, then according to the search rules, the group call initiator is searched. The search rules are: the fourth digit of the recording record number == the fourth digit of the call record number && the calling number == the called party number.

[0048] If the group call initiator can be found, the call type is determined to be a group call, and it is confirmed whether there is matching recording data in the called party's recording record. If matching recording data exists and the corresponding audio file can be obtained through the FTP server, the record integrity check result is normal. If no matching recording data exists, the record integrity check result is that the recording is missing. If the audio file corresponding to the called party's recording record cannot be obtained from the FTP server, the record integrity check result is that the file is missing.

[0049] If there is more than one called party recording, only one recording and it is the calling party recording, the call record is not the called party recording, or there is only one recording and it is the called party recording while the call record is the called party recording but the group call initiator cannot be found, then the call type is determined to be a single call; confirm whether there is matching recording data for the called party recording; if there is matching recording data and the audio file corresponding to the called party recording can be obtained from the FTP server, then the record integrity check result is normal; if there is no matching recording data, then the record integrity check result is a missing recording; if the audio file corresponding to the called party recording cannot be obtained from the FTP server, then the record integrity check result is a missing file.

[0050] In step S3, a multi-rule matching algorithm is designed. It prioritizes precise matching using the start time of the called party's record. If a match cannot be found, a time interval matching method is used. This is supplemented by calling and called party number matching rules and group call matching rules, covering various scenarios for individual and group calls. Upon successful matching, the call record and recording record are summarized into a session record. If a match fails, the abnormal situation is recorded, and all results are written to the database for permanent storage.

[0051] S4. The integrity detection results are written to a MySQL database for permanent storage. The user interaction module displays the detection result list, daily / monthly / historical statistics, task execution status, and other information through a web interface. This step enables visualized querying and historical tracing of the detection results. Figures 7 to 12 As shown.

[0052] It should be noted that the above rules are matched sequentially, and if a previous rule is met, the next rule will not be executed.

[0053] In summary, the telephone recording data integrity detection method of the present invention has the following beneficial effects: This invention achieves fully automated, timed detection of the integrity of recorded data through intelligent means, effectively replacing the repetitive manual sampling work, significantly reducing the workload of on-site maintenance personnel, saving human resources and time costs, while improving detection efficiency and accuracy, and enabling the rapid detection of problems in the recorded data.

[0054] This invention performs testing according to preset rules and standards, ensuring consistency and standardization in the testing process, eliminating the possibility of human error and oversight, and enabling timely detection and elimination of equipment security risks such as missing recordings. The system automatically generates detailed test reports and log records, facilitating managers to formulate corresponding security strategies and improvement measures, thereby improving overall management efficiency.

[0055] This invention realizes the real-time monitoring function of recording integrity required by the "Technical Specifications for Operation of Urban Rail Transit Communication Systems", which can provide reliable data for accident investigation and safety monitoring, and ensure that rail transit operation complies with relevant laws and regulations and compliance requirements.

[0056] Based on the same inventive concept, the present invention also provides an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; the memory is used to store computer programs; and the processor is used to implement the above-mentioned telephone recording data integrity detection method when executing the program stored in the memory.

[0057] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0058] The communication interface is used for communication between the aforementioned terminal and other devices.

[0059] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0060] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0061] Furthermore, it should be understood that although this specification describes embodiments, not every embodiment contains only one independent technical solution. This narrative style of the specification is merely for clarity. Those skilled in the art should consider the specification as a whole, and the technical solutions in each embodiment can also be appropriately combined to form other embodiments that can be understood by those skilled in the art.

[0062] The technical principles of the present invention have been described above with reference to specific embodiments. These descriptions are merely for explaining the principles of the invention and should not be construed as limiting the scope of protection of the invention in any way. Based on this explanation, those skilled in the art can readily conceive of other specific embodiments of the invention without inventive effort, and these embodiments will all fall within the scope of protection of the present invention.

Claims

1. A method for detecting the integrity of telephone recording data, characterized in that, include: Export call detail records (CDRs) from a ZXD1000 digital PBX; The call log is obtained by parsing the dialog box file. The call logs are matched with the recording logs in the recording server, and the completeness of the recording data is determined based on the matching results.

2. The telephone recording data integrity detection method according to claim 1, characterized in that, The steps for exporting call detail records (CDRs) from the ZXD1000 digital PBX include: After a user makes a call, the ZXD1000 digital program-controlled exchange writes the call data into the first file; The first file is renamed to obtain the call detail record (CDR) file.

3. The telephone recording data integrity detection method according to claim 2, characterized in that, After obtaining the call detail record (CDR) file, the following steps are also included: After the call detail record (CDR) file is detected, it is transferred to the FTP server. After the call detail record (CDR) file is transferred, upload an end marker file with the same name as the CDR file; When retrieving call detail records (CDRs) from an FTP server, the end marker file is used to determine whether the CDR has been completely exported.

4. The telephone recording data integrity detection method according to claim 1, characterized in that, Call logs include: caller ID, called number, call start time, and call type; recording logs include: caller ID, called number, recording start time, and recording end time. The step of matching call logs with recording logs in the recording server and determining whether the recording data is complete based on the matching result includes: Based on the called number and call start time in the call record, and the called number, recording start time, and recording end time in the recording record, the recording record corresponding to the called number is matched from the recording server. Based on the recording records, retrieve the associated caller recording records from the recording server; The associated caller recordings are aggregated to obtain a list of recordings; Find the called recording in the call log list that matches both the call start time and the called number in the call log. If there is only one recording record and it is a called party recording record, and the call record is a called party recording record, if the group call initiator can be found, the call type is determined to be a group call. When determining that the call type is a group call, it is then determined whether the called party recording record is complete.

5. The telephone recording data integrity detection method according to claim 4, characterized in that, If no matching recording record is found in the recording server based on the called number and call start time of the call record, and the call record is the calling number, then the recording record corresponding to the calling number will be matched in the recording server based on the calling number, call start time of the call record, and the recording start time and recording end time of the recording record. If no matching recording record is found in the recording server based on the called number and call start time of the call record, and the call record is a called call record, then the recording record corresponding to the calling number is matched from the recording server based on the called number and call start time of the call record, as well as the recording start time and recording end time of the recording record. Based on the recording records corresponding to the caller's number, retrieve the associated called party recording records from the recording server; The associated called party recordings are aggregated to obtain a recording list.

6. The telephone recording data integrity detection method according to claim 5, characterized in that, If no related calling or called recording record is found in the recording server, the recording record corresponding to the called number will be found in the recording server according to the call rules based on the agent number, start time, and end time of the recording record. The related audio recordings are then compiled to obtain a list of audio recordings.

7. The telephone recording data integrity detection method according to any one of claims 4 to 6, characterized in that, If no called recording is found in the recording record list that matches both the call start time and the called number, the call direction of the call record will be determined. If the call record is the calling record, then according to the first set rule, find the called recording record; If the call record is a called party's call record, then the called party's recording record will be searched according to the second set rule.

8. The telephone recording data integrity detection method according to claim 7, characterized in that, When it is confirmed that there is only one recorded audio record and it is a called party's recorded audio record, and the call record is a called party's recorded audio record, it also includes: Collect other called party recordings and search for the group call initiator according to the group call initiator search rules; the group call initiator search rules are: the fourth digit of the called number in the recording is equal to the fourth digit of the called number in the call record, and the calling number in the recording is equal to the called number in the recording. If the group call initiator is found, the call type is determined to be a group call; if the group call initiator is not found, the call type is determined to be a single call. If the conditions are not met (there is only one recorded record and it is a called party's recorded record), and the call record is also a called party's record, then the call type will be determined as a single call.

9. The telephone recording data integrity detection method according to claim 8, characterized in that, The step of determining whether the called party's recording is complete includes: Confirm whether the called party's recording records contain matching recording data; If no matching recording data is found, the record integrity check result is "recording missing". If matching recording data exists, determine whether the audio file corresponding to the called party's recording can be obtained from the FTP server; If the audio file cannot be obtained, the integrity check result is recorded as file missing; If the audio file can be obtained, the record integrity check result is normal.

10. An electronic device, characterized in that, The device includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus; the memory is used to store computer programs; and the processor, when executing the program stored in the memory, implements the telephone recording data integrity detection method as described in any one of claims 1 to 9.