Call Quality Log Reference
Call quality logs are recorded in the OpenEye installation path \Log\TsdkLog\tsdk\tup_callapi.log.
Log Format
The format of call quality logs is as follows: [Time][Log level][Log definition module name][Location of the code file where the log is recorded Name of the function where the log is recorded][Process ID Thread ID][Log content].
Example:
[2025-04-02 16:25:41.674-08:00][INFO][][][api][call_interface.c:893 callPrintChannelInfo][P=16124, T=109172][[audio]bIsCalling:1, bIsSRTP:0, acEncodeProtocol:opus, acDecodeProtocol:opus, ulChannelID:0, ulSendBitRate:7, ulRecvBitRate:29, ulSendTotalLostPacket:0, fSendLossFraction:0.000000, fSendNetLossFraction:0.000000, fSendJitter:120.000000, fSendDelay:12.000000, ulRecvTotalLostPacket:0, fRecvLossFraction:0.000000, fRecvNetLossFraction:0.000000, fRecvJitter:0.000000, fRecvDelay:12.000000]
|
Element |
Description |
|---|---|
|
Time |
Time when log information is recorded. Format: yyyy-MM-dd HH:mm:ss.SSS Example: 2012-09-18 13:40:32.401 |
|
Log level |
Level of the information recorded in a log. Call quality log level: [INFO] |
|
Location of the code file where the log is recorded |
Location of the code for recording the log. Call quality logs are recorded in the call_interface.c file. The line number varies depending on the OpenEye version. In this example, the line number is 893. |
|
Name of the function where the log is recorded |
Call quality logs are recorded in the function callPrintChannelInfo. |
|
Process ID Thread ID |
Different call quality logs with the same process ID are recorded by the same OpenEye program. P indicates the process, and T indicates the thread. |
|
Log content |
Call quality logs are classified into the following types:
|
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot