Comment # 5
on bug 11446
from Jim Young
In response to comment 4
Glad one of the workarounds will apparently suffice.
I concur with Anders comment on this: "the application may have issues".
You said:
> our old guru-guy who developed telephony core doesn't want to allocate only even
> ports for RTP to maximize server's port range utilization. He thinks that RFCs
> text doesn't deny this behavior.
The RFCs may not explicitly deny this behavior but it certainly does not appear
to condone it! ;-)
Is your old guru-guy old enough to have followed the discussions/debates
regarding the development of the RTP/RTCP protocols up to the point of
publishing the initial RFCs? I am. The old threads that discussed the pros and
cons of the even/odd protocol usage were quite "interesting"; the suggestion
for an odd/even port usage was quite novel at the time. I suspect an awful lot
of RTP/RTCP code assumes the wisdom implied by SHOULD in those RFC's.
At this point I will leave it to others decide if there is any real bug to be
fixed here or if this is simply at artifact of the how Wireshark works for the
more general RTP/RTCP case.
You are receiving this mail because:
- You are watching all bug changes.