Call Control System Fault Isolation via RTP-SIP Correlation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Identifying faulty portions in a call control system is challenging due to the complexity of the system and the difficulty in isolating intermittent failures, which leads to prolonged troubleshooting times for issues like interrupted audio.
Innovation Solution
A call control system that includes RTP status monitoring units in terminal devices to collect RTP packet information and transmit it within SIP disconnection packets, and a call control device that collects and stores SIP packet routing information to identify problem-occurring calls and determine faulty portions based on quantitative trends across devices and networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If manual isolation and troubleshooting of intermittent failures is performed in a complex call control system, then the system can identify faulty portions, but the troubleshooting time becomes excessively long
Solution Approach 1:
The system performs preliminary actions by automatically collecting and storing routing information from SIP packets and RTP packet status information before failures occur. This pre-collected data enables rapid fault isolation when intermittent failures happen, eliminating the need for manual troubleshooting and significantly reducing troubleshooting time while maintaining high identification accuracy.
Solution Approach 2:
The invention introduces an intermediary mechanism that automatically correlates routing information from multiple SIP packets with RTP packet status information. This intermediary system processes and stores the correlated data in a database, enabling operators to quickly identify faulty portions without manually analyzing complex system interactions, thus resolving the time-loss problem.
2Productivity
If the call control system collects and stores detailed routing information from multiple SIP packets and RTP packets for every call, then faulty portions can be quickly identified, but the system complexity and data management burden increase
Solution Approach 1:
The call control device performs multiple functions: it acts as a SIP packet router, an RTP packet status monitor, a data correlator, and a database manager. By consolidating these functions into a single device, the system achieves high fault identification speed without proportionally increasing overall system complexity, as the same device infrastructure is leveraged for multiple purposes.
Solution Approach 2:
The system implements self-service by automatically collecting routing information from SIP packets, monitoring RTP packet status, correlating this data, and storing it in a database without requiring external intervention. This automation reduces the operational burden and manages data complexity systematically, enabling fast fault identification while keeping data management overhead controlled.
3Loss of information
If RTP packet status information is transmitted within call disconnection SIP packets, then fault analysis data is captured without additional communication overhead, but information about intermittent failures may be lost if disconnection packets are not transmitted
Solution Approach 1:
The system uses feedback by transmitting RTP packet status information within call disconnection SIP packets back to the call control device. This feedback mechanism captures fault analysis data during call teardown, allowing the system to record status information without additional communication overhead. The feedback loop ensures that information is captured at a specific point in the call lifecycle, improving both information retention and detection reliability.
Data Source
AI summary
A terminal device 1 collects RTP information related to a call and transmits the RTP information to a CSCF 3. The CSCF 3 collects, from a plurality of SIP packets related to the call, the address of an edge router 2 that has handled the plurality of SIP packets, the address of an SBC 4 that has handled the plurality of SIP packets, and the domain name of an operator's network 5 that has handled the plurality of SIP packets, and stores in a call information list, for each call, the collected information in association with the RTP information transmitted from the terminal device 1. Then, the CSCF 3 identifies a plurality of problem-occurring calls using the RTP information, and determines a faulty portion based on a bias in the quantitative trend of the count of each of the edge router 2 addresses, the count of each of the SBC 4 addresses, and the count of each of the operator's network 5 domains.