g729 - symbian port - FABIO

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

 



Seems like I am very close to get the ITU-729 going. I will start looking
into them as soon as I finish this...

-----Original Message-----
From: pjsip-bounces@xxxxxxxxxxxxxxx [mailto:pjsip-bounces at lists.pjsip.org]
On Behalf Of Fabio Pietrosanti (naif)
Sent: Thursday, October 23, 2008 1:40 PM
To: pjsip list
Subject: Re: g729 - symbian port - FABIO

Hi Rawshan,

using the APS does not require any specific kind of partnership.

You just have to use MultimediaDD capability in your DevCert retrieved 
from SymbianSigned.com website.

Then, for application for signing of your application, you will have to 
comply to Symbian Signed rules (UNI-01 from UNI-11) with additional 
requirement for MultimediaDD usage (CAP-01 to CAP-04) .

When using  such kind of capability, while submitting the Symbian Signed 
submission, you have to use "Certified Signing" instead of "Express 
Signing" .

Select a Testing House (that will verify that you comply with Symbian 
Signed Testing Requirements), pay some money for their testing (Sogeti 
costs 560 EUR for first submission and 280EUR for second submission) and 
have your application signed and ready for the market.

I know that's additional effort, but this does not mean that you have to 
became in any way partner of Symbian or Nokia, you just have to develop 
the application respecting the requirements dictated here by Symbian:

https://developer.symbian.com/wiki/display/pub/Symbian+Signed+Test+Criteria

Regards,
Fabio Pietrosanti

Rawshan Iajdani wrote:
> Fabio,
>
> I was trying to locate APS API for codecs. But seems like I have to become
a
> partner to get access to that particular category of API. Any
> thoughts??????????????  :(
>
>
>
>
>
>
> -----Original Message-----
> From: pjsip-bounces@xxxxxxxxxxxxxxx [mailto:pjsip-bounces at lists.pjsip.org]
> On Behalf Of Fabio Pietrosanti (naif)
> Sent: Tuesday, October 21, 2008 4:39 PM
> To: pjsip list
> Subject: Re: g729 - symbian port
>
> Well,
>
> First of all the Audio Subsystem must be different between S60 and UIQ 
> devices.
>
> Second, also on S60 it will have to be different between S60 MR/FP1 
> (Audio Proxy Server) and S60 FP1/FP2 devices (Voip Audio Services API) .
> Fortunately we are lucky that APS on S60 MR/FP1 it's supported while on 
> FP2 it's deprecated but it works.
>
> Third, if you implement it in Software (instead of using APS) you will 
> have to pay royalties for each piece distributed.
>
> This guide me to say that the more convenient things to do today is to 
> hook APS directly inside PJMEDIA in order to use *for free 
> *royalty-based codec like G729 and AMR, along with Hardware Acceleration 
> and Battery Saving.
>
> Fabio
>
> Rawshan Iajdani wrote:
>   
>> Why not we should try implementing ITU - g729 instead of APS. I like to
>> think outside the box as I like my application should port to at least on
>> UIQ. Working on that and will keep you guys posted.
>>
>>
>>
>>
>> -----Original Message-----
>> From: pjsip-bounces@xxxxxxxxxxxxxxx
[mailto:pjsip-bounces at lists.pjsip.org]
>> On Behalf Of Fabio Pietrosanti (naif)
>> Sent: Monday, October 20, 2008 10:08 PM
>> To: Karthik Babu
>> Cc: pjsip list
>> Subject: Re: g729 - symbian port
>>
>> Nanang,
>>
>> can we write a small web page with the description of how the APS could 
>> be integrated inside the PJMEDIA Stack?
>>
>> Mr. Karthik Babu of Cytrion proposed himself for the development of such 
>> feature.
>>
>> Imho it should be driven by your design consideration, so it would be 
>> nice to have your support about it.
>>
>> This implementation can provide to all pjsip users all the hardware 
>> codecs support by S60 platform, including royalty based one  like G729 
>> and AMR for *free* .
>>
>> Fabio
>>
>> Karthik Babu wrote:
>>   
>>     
>>> Dear Fabio , 
>>>
>>> Can you please help me to get started with directions to implement g729
>>>       
> in
>   
>>>     
>>>       
>> APS 
>>   
>>     
>>> for  S60 devices . ? 
>>>
>>>
>>>   
>>>     
>>>       
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip at lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>>
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip at lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>   
>>     
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>   


_______________________________________________
Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip at lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org




[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux