Hi,

Not sure how easy that would be, if at all. I’m too long out the VoIP domain to 
know what’s available on this right now.

Regards,
Jaap


> On 19 Dec 2023, at 06:14, Mahesh V <maheshvenkateshwa...@gmail.com> wrote:
> 
> Hi 
> Thanks for the response.
> Is there anyway that we can measure call statistics even for the encrypted 
> traffic without using any server API?
> thanks
> 
> On Sun, Dec 17, 2023 at 3:16 AM Jaap Keuter <jaap.keu...@xs4all.nl 
> <mailto:jaap.keu...@xs4all.nl>> wrote:
> Hi,
> 
> What you are probably looking at is the encrypted form of RTCP, as defined in 
> RFC 3711.
> Therefor the first part of the packet looks okay, while the data following 
> the SSRC is undissectable, because encrypted.
> To be able to decrypt this the key and negotiated transforms would be needed. 
> They are usually not available.
> And even if they were, Wireshark currently is not able to decrypt this.
> 
> 
>> On 16 Dec 2023, at 11:05, Mahesh V <maheshvenkateshwa...@gmail.com 
>> <mailto:maheshvenkateshwa...@gmail.com>> wrote:
>> 
>> Hi Folks
>> 
>> I was trying to capture RTCP packets from a Microsoft Teams call
>> to decode the sender and receiver reports to calculate MOScore.
>> (Using D/J/PL data).
>> However, I find that my wireshark is unable to decode these packets.
>> (please see attached rtcp.pcapng)
>> However, wireshark was able to decode packet correctly
>> from a pcap file from here 
>> https://www.wireshark.org/lists/wireshark-users/200705/msg00166.html 
>> <https://www.wireshark.org/lists/wireshark-users/200705/msg00166.html>
>> 
>> any idea whats going on?
>> thanks in advance
> 
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users@wireshark.org 
> <mailto:wireshark-users@wireshark.org>>
> Archives:    https://www.wireshark.org/lists/wireshark-users 
> <https://www.wireshark.org/lists/wireshark-users>
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users 
> <https://www.wireshark.org/mailman/options/wireshark-users>
>              mailto:wireshark-users-requ...@wireshark.org 
> <mailto:wireshark-users-requ...@wireshark.org>?subject=unsubscribe
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users@wireshark.org>
> Archives:    https://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
>             mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe

Reply via email to