Last updated on NOVEMBER 11, 2016
Applies to:Oracle Communications Session Monitor - Version 3.3.90 and later
Information in this document applies to any platform.
This article aims to cover the RTP stream analysis in the Wireshark for the purpose of the OCOM's internal jitter buffer evaluation for the specific cases when the RTP gap / pause / re-sync is included in the stream. This article assumes the knowledge provided in the core article of the OCOM jitter buffer topic - Doc ID 1990734.1 - and is meant as its extension for the specific case.
Explanations in the referenced core article count with an uninterrupted RTP stream, however in some scenarios the RTP stream gets interrupted (i.e. on hold). This alters how one would track the skew in the Wireshark in order to find out which packets were too late for the OCOM's jitter buffer.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms