RTP listen Port
Hi Guys
Maybe I have missed something, but is it possible to set the listen port for a RTP session?
I am trying to build a very simple RTP app, but am running into difficulties as I only have one windows machine easily available to develop on, and if I cannot set the listen port I will not be able to develop with only one machine. I am also trying to set up a simple unicast stream - does it matter that I am using unicast addresses? Are there any specific changes I need to make to use only unicast?
At the moment I am trying to do the following:participant = new RtpParticipant("Cname", "Display_Name"); RtpEvents.RtpParticipantAdded += new RtpEvents.RtpParticipantAddedEventHandler(Rtp..etc); RtpEvents.RtpParticipantRemoved += new RtpEvents.RtpParticipantRemovedEventHandler(Rtp..etc); rtpsession = new RtpSession(destination_end_point, participant, true, true); sender = rtpsession.CreateRtpSender(participant.CName, PayloadType.dynamicAudio, null); sender.Send(message_as_bytes);
This seems to work as I can see the message on the network using a network sniffer (getting bounced as the port I’m sending to is not open, but at least it is going. The source port is set to the same as the destination port, which would be fine normally, unless you are trying to communicate between two participants on one machine)
I need to be able to set the listen port / destination port as the application I am trying to develop will be negotiating these ip/port combinations through a combination of SIP and SDP
Any pointers as to how I can accomplish this very simple two way unicast RTP stream would be greatly appreciated. I tried to look at the two way unicast conference example I found somewhere in the svn, but this is as far as I have managed to get......
Thanks in advance
Kind Regards
Richard Spiers
P.S. Is there any IRC channel where the conference XP developers hang out on ?P.S. I havn't had much luck trying to build the source code of conference XP using visual studio 2008 express edition. Bandwidth is rather limited here, and the windows server SDK is too large to download (1330.0 MB). I will make a plan if I need it in order to add any features (such as this listening port - I already attempted to do this, but my attempt resulted in a listening port being opened in the 20xx range instead of port 8888 that I set it to.......)

