This is done in FMJ as follows:
// SIP communicator
packetizers/depacketizers.
PlugInUtility.registerPlugIn("net.java.sip.communicator
.impl.media.codec.audio.speex.JavaEncoder");
PlugInUtility.registerPlugIn("net.java.sip.communicator
.impl.media.codec.audio.speex.JavaDecoder");
PlugInUtility.registerPlugIn("net.java.sip.communicator
.impl.media.codec.audio.ilbc.JavaEncoder");
PlugInUtility.registerPlugIn("net.java.sip.communicator
.impl.media.codec.audio.ilbc.JavaDecoder");
The source for PlugInUtility is attached.
Ken
Koch Michael wrote:
> Hello all!
>
> Incidentally I've just today tried to do the same
thing. The posting came
> just at the right time for me.
>
> I haven't been successful so far, unfortunately. Adding
the format to the
> RTP Manager is not all one has to do it seems.
According to the SIP
> Communicator log messages, the encoders/decoders for
the custom formats are
> not registered when I use the standard JMF. I guess
they are already added
> to the Registry of the custom JMF, so I'll have to add
them to the standard
> JMF registry by hand.
>
> I won't have time to do this today, but will try
tomorrow and keep you
> informed.
>
> This is my first post to the list, BTW. Thanks to all
contributors for the
> great work.
>
> Regards
> Michael Koch
>
>
>> Von: Emil Ivov [mailto:emcho emcho.com]
>> Gesendet: Mittwoch, 11. Juli 2007 13:43
>> An: devsip-communicator.dev.java.net
>> Betreff: Re: [sip-comm-dev] PlugInManager
customCodecs missing
>>
>> Hi Michael,
>>
>> We're initializing all RTP Managers in here:
>>
>>
net.java.sip.communicator.impl.media.CallSessionImpl.initial
iz
>> eRtpManager()
>>
>> You should be able to easily add what Ken suggested
in this method.
>>
>> Hope this helps
>> Emil
>>
>> On 7/11/07, mik <rivael_ilyahoo.com> wrote:
>>
>>> Hello Ken and Damencho!
>>>
>>> Thank you for your prompt response! I did need
to use the
>>>
>> sip-communicator
>>
>>> JMF libs.
>>> As I have spent 5 working days on this, you
might want to alert the
>>> unsuspecting programmer.
>>>
>>> In case I do want to use the latest standard
JMF libs, how
>>>
>> do I register the
>>
>>> plugins?
>>> (
>>> There are two calls to RTPManager.newInstance:
>>>
>>> grep "RTPManager.newInstance"
>>>
./net/java/sip/communicator/impl/media/CallSessionImpl.java:
>>>
>>> private RTPManager audioRtpManager =
RTPManager.newInstance();
>>>
./net/java/sip/communicator/impl/media/CallSessionImpl.java:
>>>
>>> private RTPManager videoRtpManager =
RTPManager.newInstance();
>>>
>>> )
>>>
>>> Thanks again for your help,
>>>
>>> Michael
>>>
>>>
>>> Damian Minkov <damenchodamencho.com> wrote:
>>> Hi Ken,
>>>
>>> Ken Larson wrote:
>>>
>>>> From what I can tell, SC does not properly
register the
>>>>
>> formats with
>>
>>>> the RTPManager. Here is some info that is
similar to what
>>>>
>> I recently
>>
>>>> sent to Chris, who is working on RTP in
SC.
>>>>
>>>> Every time RTPManager.newInstance() is
called, the
>>>>
>> nonstandard formats
>>
>>>> need to be resistered. ALAW/RTP, Speex/RTP,
and ILBC/rtp are all
>>>> nonstandard.
>>>>
>>>>
>>> I agree that ALAW/RTP, Speex/RTP, and ILBC/rtp
are nonstandard and
>>> missing in jmf. But I have changed
>>>
>> com.sun.media.rtp.FormatInfo and have
>>
>>> added them there - for example :
>>> formatList[110] = new
AudioFormat("speex/rtp", 8000D, -1, 1);
>>>
>>> In answer to Michael maybe: he is not using our
jmf libs (which have
>>> little changes  ).
>>> But this is a good idea to register the formats
in the newly created
>>> RTPManager I will change to that approach in
sip-communicator.
>>> Thanks for the hint.
>>>
>>> damencho
>>>
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
|
