On 25/04/10 7:00 AM, bruce bruce wrote:
> Adobe Air and Adobe FMS are good examples of VoIP working flawlessly
> over TCP. We are actually developing a flash phone which needs only TCP
> to transmit both signal and audio.
Ok, let's look at that (UDP vs TCP for realtime stream). Let's call the
se
Adobe has not been successful in VoIP. I have worked for two companies who
were trying to make flash phones, and it always came down to the issue of
RTP over TCP. This is the primary reason there are no successfully working
flash phones out there though some companies are trying to offer service
ov
Adobe Air and Adobe FMS are good examples of VoIP working flawlessly over
TCP. We are actually developing a flash phone which needs only TCP to
transmit both signal and audio.
-Bruce
On Sat, Apr 24, 2010 at 2:01 PM, Zeeshan Zakaria wrote:
> RTP stands for Real-Time Transport Protocol. TCP is no
On Sat, 2010-04-24 at 10:56 -0500, Michael Graves wrote:
> On Fri, 23 Apr 2010 23:11:06 +0200, ad...@3a.hu wrote:
>
> >Hi Guys,
> >
> >On 04-23-2010 21:40, Nathan Clemons wrote:
> >> SIP is just the control protocol, and can be negotiated over TCP or UDP.
> >> The
> >> actual payload is done over
RTP stands for Real-Time Transport Protocol. TCP is not designed to deal
with real-time data transfer as it takes time to acknowledge packets and
re-send them if missing. All audio video data transfer happens in real time,
and it doesn't make any sense to retransmit missing packets. Real time
packe
On Fri, Apr 23, 2010 at 3:21 PM, wrote:
> i have to put an * between two other SIP gateways and due to some
> circumstances, i have to use sip over tcp. With 1.6.2.6 this is working
> fine: sip gw A (deverto4) sends the call, i hand it over to sip gw B
> (ocs) and that's about it. In the other
Hi!
> Doesn't surprise me if Microsoft tries sending RTP over TCP. Maybe
> their engineers didn't know basics of VoIP when they were programming
> their communication server.
Not quite - doing SIP over TCP rather then UDP is the right thing to do
(tm). It's just that everyone started out with U
Doesn't surprise me if Microsoft tries sending RTP over TCP. Maybe their
engineers didn't know basics of VoIP when they were programming their
communication server.
Zeeshan A Zakaria
--
Sent from my Android phone with K-9 Mail.
On 2010-04-24 12:04 PM, "Michael Graves" wrote:
On Fri, 23 Apr 201
On Fri, 23 Apr 2010 23:11:06 +0200, ad...@3a.hu wrote:
>Hi Guys,
>
>On 04-23-2010 21:40, Nathan Clemons wrote:
>> SIP is just the control protocol, and can be negotiated over TCP or UDP. The
>> actual payload is done over RTP, which is a UDP-based protocol.
>>
>
>thanks, for both of you for pointi
Hi Guys,
On 04-23-2010 21:40, Nathan Clemons wrote:
> SIP is just the control protocol, and can be negotiated over TCP or UDP. The
> actual payload is done over RTP, which is a UDP-based protocol.
>
thanks, for both of you for pointing this out. i was obviously on the
wrong track here. since i
SIP is just the control protocol, and can be negotiated over TCP or UDP. The
actual payload is done over RTP, which is a UDP-based protocol.
If you had to add firewall exceptions/PAT config for the TCP SIP traffic,
you'll also need to add the same for RTP traffic as well.
-- Nathan Clemons
On F
I don't think RTP can be sent over TCP at all, it would defeat the whole
purpose of RTP. Even if you somehow manage to do so, voice quality will go
down the drain.
Zeeshan A Zakaria
--
Sent from my Android phone with K-9 Mail.
On 2010-04-23 3:27 PM, wrote:
Hi List,
i have to put an * between
Hi List,
i have to put an * between two other SIP gateways and due to some
circumstances, i have to use sip over tcp. With 1.6.2.6 this is working
fine: sip gw A (deverto4) sends the call, i hand it over to sip gw B
(ocs) and that's about it. In the other direction however (ocs -> me ->
deve
13 matches
Mail list logo
