[ previous ] [ next ] [ threads ]
 To :  Yate mailing list <yate@v...>
 From :  Paul Chitescu <paulc@v...>
 Subject :  Re: [yate] routing with database
 Date :  Mon, 10 Dec 2007 22:24:52 +0200 (EET)
Hi, Marc

There are good reasons to proxy the RTP through Yate sometimes.
- You can control the audio, insert messages, beeps, do recording and 
- You get RFC 2833 events and/or inband DTMF, can implement PBX functions.
- Having a public IP for the media stream fixes most NAT issues (with 
server's assistance).
- The identities of the parties can be held private to each other.

On the other hand, sending the RTP directly between parties:
- Saves bandwidth to the server and CPU usage.
- Reduces latency a little.
- Allows using codecs that Yate may not handle correctly, including video.

By far NATed clients are the main reason to retain RTP through the server. 
Despite the best effort with ICE and STUN there are cases when voice just 
doesn't get through because both parts are behind crowded symmetrical 


On Mon, 10 Dec 2007, Marc Dirix wrote:
> Hi,
> If rtp_forward='possible' is set, should I always set this to
> rtp_forward='yes'? If not, why, when not?
> Marc