ccrtp-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ccrtp-devel] Some doubts regarding CCRTP


From: Federico Montesino Pouzols
Subject: Re: [Ccrtp-devel] Some doubts regarding CCRTP
Date: Mon, 12 Jun 2006 10:14:46 +0200 (CEST)
User-agent: SquirrelMail/1.4.5

Hi, see responses inline...

On Mon, June 12, 2006 9:04 am, Padavala Suneel-CSP03C wrote:
> Dear GNU,
>
> I have gone through the source code of CCRTP. I have some doubts
> regarding that.
>
> 1> What are the different payload types supported by CCRTP. Does it
> support EVRCA, EVRCB, 13K QCELP, etc...

In formats.h you can see an enumeration of some formats for which
ccRTP provides support. That file also declares the basic classes for
defining payload types.

Right now I don't know if there are specific payload formatting rules
for the codecs you mention. I think no standard specific rules beyond
those more or less generic ones already supported by ccRTP have been
defined for these codecs. But...

> 2> If this is not supported yet, does GNU have any plans to support
> these payloads.

If there is any specific standard, I would say there is no direct
support for it, but there is no restriction in ccRTP to implement
it. Please, if there is any specific document/standard, point us to
it.

> 3> We are planning to use, GNU CCRTP for developing one of the
> application to send bearer data using RTP/RTCP.  If we run into any
> issues, how will be the support?
>

You can always ask this list for help and use the Savannah interface
for technical support requests/patches submission. ccRTP is free
software so you have the freedom to look for support from your
favorite expert/consultant/company.

HTH.

> Please clarify me these doubts. Your prompt response is very much
> helpful.
>
> Thanks
> Suneel.
> _______________________________________________
> Ccrtp-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/ccrtp-devel
>






reply via email to

[Prev in Thread] Current Thread [Next in Thread]