Dear Simon, H323plus members,
Thanks for your reply.
One thing that I am not understand is why it happened at the packets which are sent by polycom site, but the bug was fixed at our site(h323plus) system?
Thanks. On Wed, Feb 23, 2011 at 7:25 PM, Simon Horne s.horne@packetizer.com wrote:
Kc
Yes you are correct there was a bug with the timestamp on the marker packet being incorrect, that should have been fixed in the last release.
Update to the latest release.
That should also help resolve some issues with packets being discarded.
Simon
*From:* h323plus-bounces@lists.packetizer.com [mailto: h323plus-bounces@lists.packetizer.com] *On Behalf Of *kc ooi *Sent:* 23 February 2011 19:54 *To:* h323plus@lists.packetizer.com" *Subject:* [h323plus] RTP Packet Issue
Dear H323plus Team members,
Recently, I have found some issue when I am doing H.323 testing with polycom system (eg. PVX 8.0.2) and checked the packet traffic using wireshark.
I use RTP stream analysis of wireshark for viewing the result, and I notice that every packet(which is final slice of a frame, contain Marker=1) has a status of "Incorrect timestamp".
Why it behave like this?
Does it affect the receiving site during a conference meeting?
Is there any timeout for RTP packet handling(like dropping packet) in
h323plus? Because I found out that it cause large packet loss during the conference compare to other h.323
system on the same situation(ie. same executing environment).Btw, I have done some enhancement on MyOutput display according to the suggestion of "Simon" to one of the h323 member, to avoid dropping packet.
Thanks.