The authentication mechanism in Yate is unified which means that the
h.323 gatekeeper users can be setup in regfile.conf just as the SIP
> imfanee@y... a Ã©crit :
>> this depen on your config if u config forward_rtp=true then it will
>> bypass rtp
>> if u do it false it will proxy rtp
>> ----- Original Message ----- From: "Nicolas"
>> Sent: Tuesday, August 29, 2006 8:29 PM
>> Subject: [yate] H323-SIP proxy
>>> Sorry for all my questions ;)
>>> I need clarification about the H323-SIP proxy
>>> Does the RTP goes straight from the H323 endpoint to the SIP
>>> UserAgent or the RTP goes through the Yate?
>>> For the application I plan to use yate, it would be great if the rtp
>>> goes straight.
>>> Thank you for reply
>> The all-new Yahoo! Mail goes wherever you go - free your email
>> address from your Internet provider.
> Thanks for the reply:)
> I have another question :p
> Yate has a gatekeeper function and i don't understand where is to
> declare the aliases and H323 ID authorized