12 messages in com.googlegroups.google-talk-openRe: Problems witih linephonemediaengi...
FromSent OnAttachments
Anthony24 Jan 2006 12:51 
david feurle25 Jan 2006 01:24 
Anthony25 Jan 2006 04:06 
mikma25 Jan 2006 04:23 
david feurle25 Jan 2006 06:34 
david feurle25 Jan 2006 06:54 
david feurle25 Jan 2006 07:07 
mikma25 Jan 2006 07:18 
Anthony25 Jan 2006 10:46 
david feurle26 Jan 2006 01:48 
Anthony26 Jan 2006 04:03 
david feurle26 Jan 2006 06:56 
Subject:Re: Problems witih linephonemediaengine.cc and rtp port and correct ip address
From:Anthony (anth@gmail.com)
Date:01/25/2006 04:06:45 AM
List:com.googlegroups.google-talk-open

Hi David,

Thanks for the quick reply.

Maybe I need to look above the media streaming layer cause what winRTP provides is a COM+ interface that allows you to tell it the IP address and the rtp port number for the data to be sent to. It then takes care of getting audio from the microphone and converting it to PCMU and sending it out via RTP to the remote port. And of course it also takes what the remote end sends over RTP and decodes the PCMU into what the speaker subsystem requires. I can hear what the remote machine is saying (the one running the Googletalk audio client) but not what the googletalk audio client says on the client running libjingle.

I know that if I could get the correct RTP port and IP address that it would all work correctly since I wrote a little stub that recieves on RTP Port 8500 and if I hard code that into my code I do hear the audio both ways.

I'm assuming that each end tells the other what RTP port to connect to? Is this your understanding of how the googletalk audio XMPP extensions work, or do I need to tell the remote end what port I'm listening on?

In any case any thanks for your help.