I wnat to enlarge...
When Tandberg (MXP) sends extended video channel, it sends sessionID=0, and only in OLCAck it accept actual sessionID.
If send OLC for extended video with sessionID != 0 than Tandberg MXP sends OLCReject (InvalidSessionID).
Hi,
I'm working on H.239 implementation and find out that devices might ask SessionID=0 for a new video channel. In particular I did a test with Mirial.
I was checking the šthread http://lists.packetizer.com/pipermail/h323plus/2009-December/001269.html and it's mentioned that the SessionID=0 is invalid.
I know it's not following the standard as for RTPSession šthe range is from 1..255, but for compatibility, don't you think we should allow it? I did a test call from Mirial to Tandberg and Tandberg didn't have a problem with it.
The lines involved are
rtp.cxx
from šPAssert(id > 0 && id < 256, PInvalidParameter); to PAssert(id >= 0 && id < 256, PInvalidParameter);
and
h323.cxx
š// We must have a valid sessionID
šif (sessionID < 1 || sessionID > 255) to if (sessionID < 0 || sessionID > 255)
Thanks,
Marek