Difference between revisions of "M4 Call Info"

From Kolmisoft Wiki
Jump to navigationJump to search
 
(15 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= Call Info page =
The Call Info page provides additional information about the Call
[[File:m2_call_info.png]]
<br><br>
== MOS ==
Some calls do not have MOS information because MOS calculations depend on RTCP reports from the RTP endpoints involved. If they don't send RTCP, then there's no MOS and other stats (Loss, Jitter, Roundtrip).
<br><br>
= PCAP File/data =
= PCAP File/data =


Background process records pcap files for every call. Later it is very easy to retrieve pcap file for exact call from Call Info page.
* NOTE: Sometimes not all calls are captured due to hardware limitations


Press on the Download PCAP file button and if you have Wireshark installed - it will open the pcap file in the Wireshark.
Background process records pcap files for (almost) every call. Later it is very easy to retrieve pcap file for the exact call from the Call Info page.


NOTE: pcap file takes up to 10kb of data. By default it is reserved 1Gb of HDD space for pcap files. Approximately it is enough for 100.000 calls. Older files are deleted when space limit is reached. HDD space limit can be increased if necessary.  
Press on the Download PCAP file button and if you have Wireshark installed - it will open the pcap file in Wireshark.


[[File:m2_call_info.png]]
NOTE: pcap file takes up to 10kb of data. By default, it is reserved 1Gb of HDD space for pcap files. Approximately it is enough for 100.000 calls. Older files are deleted when the space limit is reached. HDD space limit can be increased if necessary.
 
 
 
[[File:m2_pcap.png]]


<br><br>
= Log =
= Log =


Call Log is useful feature for troubleshooting Calls. It shows the exact Call Flow that was used when User made a Call. Call Log includes Radius log (billing part of Switch) and FreeSWITCH log (routing part of Switch) but most of the time, Radius log is enough troubleshoot Calls.<br>
Call Log is a useful feature for troubleshooting Calls. It shows the exact Call Flow that was used when the User made a Call. Call Log includes Radius log (billing part of Switch) and FreeSWITCH log (routing part of Switch) but most of the time, Radius log is enough to troubleshoot Calls.<br>


Note: Datetime is in server timezone<br>
Note: Datetime is in server timezone<br>


[[File:M2_call_log.png]]
[[File:M2_call_log.png]]
<br><br>
= See also =
* [[PCAP does not show LegB of a call]]

Latest revision as of 08:43, 6 December 2022

Call Info page

The Call Info page provides additional information about the Call

M2 call info.png



MOS

Some calls do not have MOS information because MOS calculations depend on RTCP reports from the RTP endpoints involved. If they don't send RTCP, then there's no MOS and other stats (Loss, Jitter, Roundtrip).



PCAP File/data

  • NOTE: Sometimes not all calls are captured due to hardware limitations

Background process records pcap files for (almost) every call. Later it is very easy to retrieve pcap file for the exact call from the Call Info page.

Press on the Download PCAP file button and if you have Wireshark installed - it will open the pcap file in Wireshark.

NOTE: pcap file takes up to 10kb of data. By default, it is reserved 1Gb of HDD space for pcap files. Approximately it is enough for 100.000 calls. Older files are deleted when the space limit is reached. HDD space limit can be increased if necessary.


M2 pcap.png



Log

Call Log is a useful feature for troubleshooting Calls. It shows the exact Call Flow that was used when the User made a Call. Call Log includes Radius log (billing part of Switch) and FreeSWITCH log (routing part of Switch) but most of the time, Radius log is enough to troubleshoot Calls.

Note: Datetime is in server timezone

M2 call log.png




See also