On 5/11/06, Fernando Camarero <[EMAIL PROTECTED]> wrote:
I don't know the RTCP implementation state in the oRTP project, but it might be better to make sure that their implementation is complete before doing anything on client software such as WengoPhone NG. Even then, it seems that there are already all that is needed in PhApi to use RTCP, and Classic uses RTCP whenever it's not behind a NAT.
So, what I suggest is:
- make sure that everything is done in oRTP regarding RTCP.
- make sure that RTCP support is not already implemented in Classic.
- see if it is correctly implemented in phapi that is included in NG's source code.
- Add support in WengoPhone NG for RTCP.
Also, i've been told that Extended RTCP is an extended
RTCP protocol that is better suited for VoIP traffic. Maybe it's worth
considering.
I see. I've been thinking about it and I've come to the conclusion that I'll
try to implement the RTCP protocol by myself. What do you recommend me?, to
use WP Classic or NG? I think that could be better for the community to make
it in NG, but I'm scared about the fault of reliability, and the problems I
would have to solve to make it work properly.
I don't know the RTCP implementation state in the oRTP project, but it might be better to make sure that their implementation is complete before doing anything on client software such as WengoPhone NG. Even then, it seems that there are already all that is needed in PhApi to use RTCP, and Classic uses RTCP whenever it's not behind a NAT.
So, what I suggest is:
- make sure that everything is done in oRTP regarding RTCP.
- make sure that RTCP support is not already implemented in Classic.
- see if it is correctly implemented in phapi that is included in NG's source code.
- Add support in WengoPhone NG for RTCP.
I hope it helps!
Best regards,
--
Julien Gilli
_______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
