[h323plus] [Fwd: Re: Silk codec support]
luke at agh.edu.pl
Fri Jan 14 05:39:06 EST 2011
Dear Simon, Robert and all H323Plus Team,
Thanks for your very fast answer.
I have successfully built ptlib, h323plus (1.22) with silk codec and
simple. I put silk_ptplugin.dll, iLBC_ptplugin.dll and
gsm0610_ptplugin.dll into c:\pwlib_plugins (then also to
c:\ptlib_plugins). Simple runs OK on XP and Windows 7, quality of G.711
and iLBC (both 13k and 15k) is good, but neither gsm nor silk work.
There are some static, MOS is about 1... Additionally, simple app logs
SKP_Silk_Encode returned -4 every few seconds. Am I doing anything wrong?
-------- Wiadomość oryginalna --------
I have checked the code into the h323plus CVS.
There is no official ITU Generic identifier yet so it is using a Packetizer
Identifer for the moment.
You can contact me offlist to discuss.
From: h323plus-bounces at lists.packetizer.com
[mailto:h323plus-bounces at lists.packetizer.com] On Behalf Of Robert Jongbloed
Sent: Wednesday, January 12, 2011 9:26 AM
To: h323plus at lists.packetizer.com
Subject: Re: [h323plus] Silk codec support
I added SILK to OPAL a couple of months back. Unfortunately it was SIP only
as I did not know what the H.245 encoding is for SILK, if any.
Now that I see there is at least a proposed standard, this should be able to
be finished in a few minutes. It would be really nice if the two systems
could use the same code for this.
OPAL/OpenH323/PTLib Architect and Co-founder.
> -----Original Message-----
> From: h323plus-bounces at lists.packetizer.com [mailto:h323plus-
> bounces at lists.packetizer.com] On Behalf Of Simon Horne
> Sent: Tuesday, 11 January 2011 9:32 PM
> To: 'Łukasz Czekierda'
> Cc: h323plus at lists.packetizer.com
> Subject: Re: [h323plus] Silk codec support
> The issue is there is no definition of Silk in H.323
> I wrote a submission to the ITU at the last meeting for inclusion
> The stumbling block is that SILK has defined dynamic payloads for each
> bitrate for interop with Skype. In H.323 you cannot tell the remote
> what payload to send, the remote will tell you want it will send. This
> issue if you are bridging to skype. There is a work around (submitted
> by Avaya for a different issue but same meeting) to include in the
> OLCack the payload that you expect the remote to send you.
> I have a development H.323 silk plugin (8k and 16k bitrate) and I will
> commit them after the next stable release as it requires audio
> capability merging which needs to be committed. The idea is there is 1
> for the different bitrates (rather than a capability for each bitrate)
> and you negotiate the actual bitrate by merging your local caps with
> the caps
> the TCS.
> -----Original Message-----
> From: h323plus-bounces at lists.packetizer.com
> [mailto:h323plus-bounces at lists.packetizer.com] On Behalf Of Lukasz
> Sent: Tuesday, January 11, 2011 7:42 PM
> To: h323plus at lists.packetizer.com
> Subject: [h323plus] Silk codec support
> Dear H.323Plus team,
> I have a question regarding support for skype's silk codec. Do you
> plan to support it soon? Maybe you have already started
> you expect any obstacles?
> Best regards,
> Łukasz Czekierda
More information about the h323plus