it totally dependent of the application, the application can receive SIP and send to SIP-STACK , or RTP-STEAM and sent to media-harware.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext Franz Edler Sent: Wednesday, February 03, 2010 2:07 PM To: 'Nahum Nir' Cc: [email protected] Subject: Re: [Sip-implementors] What is worong with that sip message??? This cannot work. Either a signalling process is listening to this port or a media rendering proicess but never both. Ranz _____ From: Nahum Nir [mailto:[email protected]] Sent: Wednesday, February 03, 2010 6:00 PM To: Franz Edler Subject: Re: [Sip-implementors] What is worong with that sip message??? Hi, Yes I know it is strange - just trying something. I'm using wireshark to check if the audio arrive. Do you know what is worng? Thanks, Nahum On Wed, Feb 3, 2010 at 4:18 PM, Franz Edler <[email protected]> wrote: I'm trying to make an INVITE so that the incoming audio will be received on 89.139.126.116:44074 <http://89.139.126.116:44074/> . Are you sure that you selected the right port for media? >From the Via header field I see that the port 44074 is already occupied by signalling. That's very strange. Via: SIP/2.0/UDP 89.139.126.116:44074 <http://89.139.126.116:44074/> You obviously cannot receive signalling and media on the same port. BR Franz _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
