Well, formally speaking, the bug in question appears if one uses
Skype4Com library as a wrapper around "bare" Skype API.
So in theory it may be the bug not in Sype API itself,
but in Skype4Com, and this bug is not present in
Java wrapper -- Skype4Java.
Though I doubt that this is the case. As far as I understand,
Skype4Com just sends text commands to Skype API,
without trying to interpret or change them.
By the way, it seems that You have tried yourself to use PORT command
with Skype4Java and Your attempt failed?

If so, this confirms imho,
that the bug in question is in API itself, not in one of the wrappers around this API.
As to the links You gave: the presentation there is too schematic, with no concrete details.
Skype API's are mentioned in one place as being used, but again with no details,
so that one can not conclude from vague description given there, that
PORT command was used at all. Moreover, it seems as if there is described
only the project, which is not jet realized: no source, no jar's -- nothing real.
Really i havn't tested the PORT property because i don't know how to test it and see the result to confirm that
PORT works.
For the SOUNDCARD and the FILE properties i can see the results because i see the output of my program but for the PORT it's not the case.