[sip-comm-dev] JMF in Sip-Communicator


#1

Hi,

I’m working trying to develop a patch to use the codec h.263+ in
sip-communicator. I’m starting on that, but firstly I need to know what JMF
version is using the sip-communicator, ¿is it the JMF 2.1.1?

Does anyone implement any video codec for sip-communicator? What step should
I follow? I’ve identified the package impl.media.codec and (maybe) the
impl.media.codec.video as the packages which control the issues related to
video codec features control.

I’d appreciate any help because I’m pretty lost in that task.

Thanks a lot

Pedro Antonio Moreno Sanchez
Telecommunication Engineer & Researcher
Bioengineering and Telemedicine Group
ETSI Telecomunicación - UPM A.101-8L.
Ciudad Universitaria s/n
28040 MADRID - SPAIN

Tel. +34 91 549 57 00 ext. 3407
Fax + 34 91 336 68 28
e-mail: <mailto:pmoreno@gbt.tfo.upm.es> pmoreno@gbt.tfo.upm.es


#2

The media bundle is deprecated and not started in the latest of trunk,
use neomedia.

H.264 is a video codec and is implemented in SIP Communicator. I'd say
that H.263+ should be implemented in the same fashion so it should be
pretty easy to look at the implementation of H.264 which resides in an
appropriately named package.

···

On Thu, Nov 26, 2009 at 3:31 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> wrote:

Hi,

I’m working trying to develop a patch to use the codec h.263+ in
sip-communicator. I’m starting on that, but firstly I need to know what JMF
version is using the sip-communicator, ¿is it the JMF 2.1.1?

Does anyone implement any video codec for sip-communicator? What step should
I follow? I’ve identified the package impl.media.codec and (maybe) the
impl.media.codec.video as the packages which control the issues related to
video codec features control.

I’d appreciate any help because I’m pretty lost in that task.

Thanks a lot

Pedro Antonio Moreno Sanchez
Telecommunication Engineer & Researcher
Bioengineering and Telemedicine Group
ETSI Telecomunicación - UPM A.101-8L.
Ciudad Universitaria s/n
28040 MADRID - SPAIN

Tel. +34 91 549 57 00 ext. 3407
Fax + 34 91 336 68 28
e-mail: pmoreno@gbt.tfo.upm.es

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4638 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi Lubomir

Thanks for your answer. I'm not working with the latest version of
sip-communicator, so I have to use the media bundle. Yesterday I asked what
version JMF was, because if it was the 2.1.1 the h.263+ would be in JMF and
would be easier than doing a complete implementation of h.263+ like h.264.

Do you know about the version?

Thanks a lot and regards

Pedro

···

-----Mensaje original-----
De: Lubomir Marinov [mailto:lubo@sip-communicator.org]
Enviado el: jueves, 26 de noviembre de 2009 18:54
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

The media bundle is deprecated and not started in the latest of trunk,
use neomedia.

H.264 is a video codec and is implemented in SIP Communicator. I'd say
that H.263+ should be implemented in the same fashion so it should be
pretty easy to look at the implementation of H.264 which resides in an
appropriately named package.

On Thu, Nov 26, 2009 at 3:31 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> wrote:

Hi,

I’m working trying to develop a patch to use the codec h.263+ in
sip-communicator. I’m starting on that, but firstly I need to know what

JMF

version is using the sip-communicator, ¿is it the JMF 2.1.1?

Does anyone implement any video codec for sip-communicator? What step

should

I follow? I’ve identified the package impl.media.codec and (maybe) the
impl.media.codec.video as the packages which control the issues related to
video codec features control.

I’d appreciate any help because I’m pretty lost in that task.

Thanks a lot

Pedro Antonio Moreno Sanchez
Telecommunication Engineer & Researcher
Bioengineering and Telemedicine Group
ETSI Telecomunicación - UPM A.101-8L.
Ciudad Universitaria s/n
28040 MADRID - SPAIN

Tel. +34 91 549 57 00 ext. 3407
Fax + 34 91 336 68 28
e-mail: pmoreno@gbt.tfo.upm.es

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4638 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Hi,

we use latest jmf. But this codec will only work on windows and 32bit
linux, it wont work on 64bit linux and on Mac OS X.
And I'm not sure the actual type of h263 implementation in jmf, cause
as I remember there were three or four modifications of this codec.

Cheers
damencho

···

On Fri, Nov 27, 2009 at 10:46 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> wrote:

Hi Lubomir

Thanks for your answer. I'm not working with the latest version of
sip-communicator, so I have to use the media bundle. Yesterday I asked what
version JMF was, because if it was the 2.1.1 the h.263+ would be in JMF and
would be easier than doing a complete implementation of h.263+ like h.264.

Do you know about the version?

Thanks a lot and regards

Pedro

-----Mensaje original-----
De: Lubomir Marinov [mailto:lubo@sip-communicator.org]
Enviado el: jueves, 26 de noviembre de 2009 18:54
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

The media bundle is deprecated and not started in the latest of trunk,
use neomedia.

H.264 is a video codec and is implemented in SIP Communicator. I'd say
that H.263+ should be implemented in the same fashion so it should be
pretty easy to look at the implementation of H.264 which resides in an
appropriately named package.

On Thu, Nov 26, 2009 at 3:31 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> > wrote:

Hi,

I’m working trying to develop a patch to use the codec h.263+ in
sip-communicator. I’m starting on that, but firstly I need to know what

JMF

version is using the sip-communicator, ¿is it the JMF 2.1.1?

Does anyone implement any video codec for sip-communicator? What step

should

I follow? I’ve identified the package impl.media.codec and (maybe) the
impl.media.codec.video as the packages which control the issues related to
video codec features control.

I’d appreciate any help because I’m pretty lost in that task.

Thanks a lot

Pedro Antonio Moreno Sanchez
Telecommunication Engineer & Researcher
Bioengineering and Telemedicine Group
ETSI Telecomunicación - UPM A.101-8L.
Ciudad Universitaria s/n
28040 MADRID - SPAIN

Tel. +34 91 549 57 00 ext. 3407
Fax + 34 91 336 68 28
e-mail: pmoreno@gbt.tfo.upm.es

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4638 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

Hi Damencho,

Actually there are three version of h263 codec, and SIP Communicator are
using the first one (the simple h.263). Yesterday I was searching on JMF web
site and saw that version JMF 2.1.1 supports the h.263+ (the second version
of h263 codec).

So I suppose that if SIP Communicator is using the latest version of JMF I
would not have to implement the h.263+, like h.264 is. Then, I wanted to
know how the h.263 is implemented, that is, what are the main steps I have
to follow to succeeded in getting the correct implementation of h.263+.

Thanks and regards

Pedro

···

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de Damian
Minkov
Enviado el: viernes, 27 de noviembre de 2009 10:01
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

we use latest jmf. But this codec will only work on windows and 32bit
linux, it wont work on 64bit linux and on Mac OS X.
And I'm not sure the actual type of h263 implementation in jmf, cause
as I remember there were three or four modifications of this codec.

Cheers
damencho

On Fri, Nov 27, 2009 at 10:46 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> wrote:

Hi Lubomir

Thanks for your answer. I'm not working with the latest version of
sip-communicator, so I have to use the media bundle. Yesterday I asked

what

version JMF was, because if it was the 2.1.1 the h.263+ would be in JMF

and

would be easier than doing a complete implementation of h.263+ like h.264.

Do you know about the version?

Thanks a lot and regards

Pedro

-----Mensaje original-----
De: Lubomir Marinov [mailto:lubo@sip-communicator.org]
Enviado el: jueves, 26 de noviembre de 2009 18:54
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

The media bundle is deprecated and not started in the latest of trunk,
use neomedia.

H.264 is a video codec and is implemented in SIP Communicator. I'd say
that H.263+ should be implemented in the same fashion so it should be
pretty easy to look at the implementation of H.264 which resides in an
appropriately named package.

On Thu, Nov 26, 2009 at 3:31 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> > wrote:

Hi,

I’m working trying to develop a patch to use the codec h.263+ in
sip-communicator. I’m starting on that, but firstly I need to know what

JMF

version is using the sip-communicator, ¿is it the JMF 2.1.1?

Does anyone implement any video codec for sip-communicator? What step

should

I follow? I’ve identified the package impl.media.codec and (maybe) the
impl.media.codec.video as the packages which control the issues related

to

video codec features control.

I’d appreciate any help because I’m pretty lost in that task.

Thanks a lot

Pedro Antonio Moreno Sanchez
Telecommunication Engineer & Researcher
Bioengineering and Telemedicine Group
ETSI Telecomunicación - UPM A.101-8L.
Ciudad Universitaria s/n
28040 MADRID - SPAIN

Tel. +34 91 549 57 00 ext. 3407
Fax + 34 91 336 68 28
e-mail: pmoreno@gbt.tfo.upm.es

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4638 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#6

Hi,

As I see we don't advertise that particular payload type, and we do
that because its not fully supported on all operating systems.
You can try adding it. As Lubo said media is deprecated and is no
longer used you must look at neomedia and especially
net.java.sip.communicator.impl.neomedia.MediaUtils. Its h263-1998/rtp
the jmf type name VideoFormat.H263_1998_RTP with payload number 42. As
I see h263+ is only extension of the packetizing and is missing from
SdpConstants.

Cheers
damencho

···

On Fri, Nov 27, 2009 at 11:28 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> wrote:

Hi Damencho,

Actually there are three version of h263 codec, and SIP Communicator are
using the first one (the simple h.263). Yesterday I was searching on JMF web
site and saw that version JMF 2.1.1 supports the h.263+ (the second version
of h263 codec).

So I suppose that if SIP Communicator is using the latest version of JMF I
would not have to implement the h.263+, like h.264 is. Then, I wanted to
know how the h.263 is implemented, that is, what are the main steps I have
to follow to succeeded in getting the correct implementation of h.263+.

Thanks and regards

Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de Damian
Minkov
Enviado el: viernes, 27 de noviembre de 2009 10:01
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

we use latest jmf. But this codec will only work on windows and 32bit
linux, it wont work on 64bit linux and on Mac OS X.
And I'm not sure the actual type of h263 implementation in jmf, cause
as I remember there were three or four modifications of this codec.

Cheers
damencho

On Fri, Nov 27, 2009 at 10:46 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> > wrote:

Hi Lubomir

Thanks for your answer. I'm not working with the latest version of
sip-communicator, so I have to use the media bundle. Yesterday I asked

what

version JMF was, because if it was the 2.1.1 the h.263+ would be in JMF

and

would be easier than doing a complete implementation of h.263+ like h.264.

Do you know about the version?

Thanks a lot and regards

Pedro

-----Mensaje original-----
De: Lubomir Marinov [mailto:lubo@sip-communicator.org]
Enviado el: jueves, 26 de noviembre de 2009 18:54
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

The media bundle is deprecated and not started in the latest of trunk,
use neomedia.

H.264 is a video codec and is implemented in SIP Communicator. I'd say
that H.263+ should be implemented in the same fashion so it should be
pretty easy to look at the implementation of H.264 which resides in an
appropriately named package.

On Thu, Nov 26, 2009 at 3:31 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> >> wrote:

Hi,

I’m working trying to develop a patch to use the codec h.263+ in
sip-communicator. I’m starting on that, but firstly I need to know what

JMF

version is using the sip-communicator, ¿is it the JMF 2.1.1?

Does anyone implement any video codec for sip-communicator? What step

should

I follow? I’ve identified the package impl.media.codec and (maybe) the
impl.media.codec.video as the packages which control the issues related

to

video codec features control.

I’d appreciate any help because I’m pretty lost in that task.

Thanks a lot

Pedro Antonio Moreno Sanchez
Telecommunication Engineer & Researcher
Bioengineering and Telemedicine Group
ETSI Telecomunicación - UPM A.101-8L.
Ciudad Universitaria s/n
28040 MADRID - SPAIN

Tel. +34 91 549 57 00 ext. 3407
Fax + 34 91 336 68 28
e-mail: pmoreno@gbt.tfo.upm.es

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4638 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#7

Hi,
As I said before, I'm using an old version of sip-communicator because I'm
working in an application that uses that version and I can't change it now.
I was checking the VideoFormat class and I saw the constant
VideoFormat.H263_1998_RTP is about the H.263+ codec. Although I've find the
problem, as Damencho has said, about the missing from SdpConstant. So, I
suppose that brings me to implement the h.263+ codec like the h.264 is,
isn't it?
Regards
Pedro

···

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de Damian
Minkov
Enviado el: viernes, 27 de noviembre de 2009 11:45
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

As I see we don't advertise that particular payload type, and we do
that because its not fully supported on all operating systems.
You can try adding it. As Lubo said media is deprecated and is no
longer used you must look at neomedia and especially
net.java.sip.communicator.impl.neomedia.MediaUtils. Its h263-1998/rtp
the jmf type name VideoFormat.H263_1998_RTP with payload number 42. As
I see h263+ is only extension of the packetizing and is missing from
SdpConstants.

Cheers
damencho

On Fri, Nov 27, 2009 at 11:28 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> wrote:

Hi Damencho,

Actually there are three version of h263 codec, and SIP Communicator are
using the first one (the simple h.263). Yesterday I was searching on JMF

web

site and saw that version JMF 2.1.1 supports the h.263+ (the second

version

of h263 codec).

So I suppose that if SIP Communicator is using the latest version of JMF I
would not have to implement the h.263+, like h.264 is. Then, I wanted to
know how the h.263 is implemented, that is, what are the main steps I have
to follow to succeeded in getting the correct implementation of h.263+.

Thanks and regards

Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de

Damian

Minkov
Enviado el: viernes, 27 de noviembre de 2009 10:01
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

we use latest jmf. But this codec will only work on windows and 32bit
linux, it wont work on 64bit linux and on Mac OS X.
And I'm not sure the actual type of h263 implementation in jmf, cause
as I remember there were three or four modifications of this codec.

Cheers
damencho

On Fri, Nov 27, 2009 at 10:46 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> > wrote:

Hi Lubomir

Thanks for your answer. I'm not working with the latest version of
sip-communicator, so I have to use the media bundle. Yesterday I asked

what

version JMF was, because if it was the 2.1.1 the h.263+ would be in JMF

and

would be easier than doing a complete implementation of h.263+ like

h.264.

Do you know about the version?

Thanks a lot and regards

Pedro

-----Mensaje original-----
De: Lubomir Marinov [mailto:lubo@sip-communicator.org]
Enviado el: jueves, 26 de noviembre de 2009 18:54
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

The media bundle is deprecated and not started in the latest of trunk,
use neomedia.

H.264 is a video codec and is implemented in SIP Communicator. I'd say
that H.263+ should be implemented in the same fashion so it should be
pretty easy to look at the implementation of H.264 which resides in an
appropriately named package.

On Thu, Nov 26, 2009 at 3:31 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> >> wrote:

Hi,

I’m working trying to develop a patch to use the codec h.263+ in
sip-communicator. I’m starting on that, but firstly I need to know what

JMF

version is using the sip-communicator, ¿is it the JMF 2.1.1?

Does anyone implement any video codec for sip-communicator? What step

should

I follow? I’ve identified the package impl.media.codec and (maybe) the
impl.media.codec.video as the packages which control the issues related

to

video codec features control.

I’d appreciate any help because I’m pretty lost in that task.

Thanks a lot

Pedro Antonio Moreno Sanchez
Telecommunication Engineer & Researcher
Bioengineering and Telemedicine Group
ETSI Telecomunicación - UPM A.101-8L.
Ciudad Universitaria s/n
28040 MADRID - SPAIN

Tel. +34 91 549 57 00 ext. 3407
Fax + 34 91 336 68 28
e-mail: pmoreno@gbt.tfo.upm.es

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4638 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#8

Hi!

Take a look to http://java.sun.com/javase/technologies/desktop/media/jmf/2.1.1/formats.html because I can't see anything related with H263+

Regards.

Pablo.

···

-----Mensaje original-----
De: Pedro Moreno [mailto:pmoreno@gbt.tfo.upm.es]
Enviado el: viernes, 27 de noviembre de 2009 12:23
Para: dev@sip-communicator.dev.java.net
Asunto: RE: [sip-comm-dev] JMF in Sip-Communicator

Hi,
As I said before, I'm using an old version of sip-communicator because I'm
working in an application that uses that version and I can't change it now.
I was checking the VideoFormat class and I saw the constant
VideoFormat.H263_1998_RTP is about the H.263+ codec. Although I've find the
problem, as Damencho has said, about the missing from SdpConstant. So, I
suppose that brings me to implement the h.263+ codec like the h.264 is,
isn't it?
Regards
Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de Damian
Minkov
Enviado el: viernes, 27 de noviembre de 2009 11:45
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

As I see we don't advertise that particular payload type, and we do
that because its not fully supported on all operating systems.
You can try adding it. As Lubo said media is deprecated and is no
longer used you must look at neomedia and especially
net.java.sip.communicator.impl.neomedia.MediaUtils. Its h263-1998/rtp
the jmf type name VideoFormat.H263_1998_RTP with payload number 42. As
I see h263+ is only extension of the packetizing and is missing from
SdpConstants.

Cheers
damencho

On Fri, Nov 27, 2009 at 11:28 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> wrote:

Hi Damencho,

Actually there are three version of h263 codec, and SIP Communicator are
using the first one (the simple h.263). Yesterday I was searching on JMF

web

site and saw that version JMF 2.1.1 supports the h.263+ (the second

version

of h263 codec).

So I suppose that if SIP Communicator is using the latest version of JMF I
would not have to implement the h.263+, like h.264 is. Then, I wanted to
know how the h.263 is implemented, that is, what are the main steps I have
to follow to succeeded in getting the correct implementation of h.263+.

Thanks and regards

Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de

Damian

Minkov
Enviado el: viernes, 27 de noviembre de 2009 10:01
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

we use latest jmf. But this codec will only work on windows and 32bit
linux, it wont work on 64bit linux and on Mac OS X.
And I'm not sure the actual type of h263 implementation in jmf, cause
as I remember there were three or four modifications of this codec.

Cheers
damencho

On Fri, Nov 27, 2009 at 10:46 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> > wrote:

Hi Lubomir

Thanks for your answer. I'm not working with the latest version of
sip-communicator, so I have to use the media bundle. Yesterday I asked

what

version JMF was, because if it was the 2.1.1 the h.263+ would be in JMF

and

would be easier than doing a complete implementation of h.263+ like

h.264.

Do you know about the version?

Thanks a lot and regards

Pedro

-----Mensaje original-----
De: Lubomir Marinov [mailto:lubo@sip-communicator.org]
Enviado el: jueves, 26 de noviembre de 2009 18:54
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

The media bundle is deprecated and not started in the latest of trunk,
use neomedia.

H.264 is a video codec and is implemented in SIP Communicator. I'd say
that H.263+ should be implemented in the same fashion so it should be
pretty easy to look at the implementation of H.264 which resides in an
appropriately named package.

On Thu, Nov 26, 2009 at 3:31 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> >> wrote:

Hi,

I'm working trying to develop a patch to use the codec h.263+ in
sip-communicator. I'm starting on that, but firstly I need to know what

JMF

version is using the sip-communicator, ¿is it the JMF 2.1.1?

Does anyone implement any video codec for sip-communicator? What step

should

I follow? I've identified the package impl.media.codec and (maybe) the
impl.media.codec.video as the packages which control the issues related

to

video codec features control.

I'd appreciate any help because I'm pretty lost in that task.

Thanks a lot

Pedro Antonio Moreno Sanchez
Telecommunication Engineer & Researcher
Bioengineering and Telemedicine Group
ETSI Telecomunicación - UPM A.101-8L.
Ciudad Universitaria s/n
28040 MADRID - SPAIN

Tel. +34 91 549 57 00 ext. 3407
Fax + 34 91 336 68 28
e-mail: pmoreno@gbt.tfo.upm.es

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4638 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#9

Hi Pablo

I checked that page yesterday and it seems that JMF 2.1.1 doesn´t support
the h.263+ codec, but if you take a look to
http://java.sun.com/javase/technologies/desktop/media/jmf/reference/faqs/ind
ex.html#jmf2.1.1 in What is JMF 2.1.1? question you see H.263/1998 (h.263+)
is supported.

But the problem is that in this codec is not mention in sdpConstant, so I
don't if I have to implement like h.264 or just use the JMF and create a
constant for the h.263+ payload.

Any idea??

Thanks

Pedro

···

-----Mensaje original-----
De: PABLO LOPEZ GARCIA [mailto:palg@tid.es]
Enviado el: viernes, 27 de noviembre de 2009 12:39
Para: dev@sip-communicator.dev.java.net
Asunto: RE: [sip-comm-dev] JMF in Sip-Communicator

Hi!

Take a look to
http://java.sun.com/javase/technologies/desktop/media/jmf/2.1.1/formats.html
because I can't see anything related with H263+

Regards.

Pablo.

-----Mensaje original-----
De: Pedro Moreno [mailto:pmoreno@gbt.tfo.upm.es]
Enviado el: viernes, 27 de noviembre de 2009 12:23
Para: dev@sip-communicator.dev.java.net
Asunto: RE: [sip-comm-dev] JMF in Sip-Communicator

Hi,
As I said before, I'm using an old version of sip-communicator because I'm
working in an application that uses that version and I can't change it now.
I was checking the VideoFormat class and I saw the constant
VideoFormat.H263_1998_RTP is about the H.263+ codec. Although I've find the
problem, as Damencho has said, about the missing from SdpConstant. So, I
suppose that brings me to implement the h.263+ codec like the h.264 is,
isn't it?
Regards
Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de Damian
Minkov
Enviado el: viernes, 27 de noviembre de 2009 11:45
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

As I see we don't advertise that particular payload type, and we do
that because its not fully supported on all operating systems.
You can try adding it. As Lubo said media is deprecated and is no
longer used you must look at neomedia and especially
net.java.sip.communicator.impl.neomedia.MediaUtils. Its h263-1998/rtp
the jmf type name VideoFormat.H263_1998_RTP with payload number 42. As
I see h263+ is only extension of the packetizing and is missing from
SdpConstants.

Cheers
damencho

On Fri, Nov 27, 2009 at 11:28 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> wrote:

Hi Damencho,

Actually there are three version of h263 codec, and SIP Communicator are
using the first one (the simple h.263). Yesterday I was searching on JMF

web

site and saw that version JMF 2.1.1 supports the h.263+ (the second

version

of h263 codec).

So I suppose that if SIP Communicator is using the latest version of JMF I
would not have to implement the h.263+, like h.264 is. Then, I wanted to
know how the h.263 is implemented, that is, what are the main steps I have
to follow to succeeded in getting the correct implementation of h.263+.

Thanks and regards

Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de

Damian

Minkov
Enviado el: viernes, 27 de noviembre de 2009 10:01
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

we use latest jmf. But this codec will only work on windows and 32bit
linux, it wont work on 64bit linux and on Mac OS X.
And I'm not sure the actual type of h263 implementation in jmf, cause
as I remember there were three or four modifications of this codec.

Cheers
damencho

On Fri, Nov 27, 2009 at 10:46 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> > wrote:

Hi Lubomir

Thanks for your answer. I'm not working with the latest version of
sip-communicator, so I have to use the media bundle. Yesterday I asked

what

version JMF was, because if it was the 2.1.1 the h.263+ would be in JMF

and

would be easier than doing a complete implementation of h.263+ like

h.264.

Do you know about the version?

Thanks a lot and regards

Pedro

-----Mensaje original-----
De: Lubomir Marinov [mailto:lubo@sip-communicator.org]
Enviado el: jueves, 26 de noviembre de 2009 18:54
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

The media bundle is deprecated and not started in the latest of trunk,
use neomedia.

H.264 is a video codec and is implemented in SIP Communicator. I'd say
that H.263+ should be implemented in the same fashion so it should be
pretty easy to look at the implementation of H.264 which resides in an
appropriately named package.

On Thu, Nov 26, 2009 at 3:31 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> >> wrote:

Hi,

I'm working trying to develop a patch to use the codec h.263+ in
sip-communicator. I'm starting on that, but firstly I need to know what

JMF

version is using the sip-communicator, ¿is it the JMF 2.1.1?

Does anyone implement any video codec for sip-communicator? What step

should

I follow? I've identified the package impl.media.codec and (maybe) the
impl.media.codec.video as the packages which control the issues related

to

video codec features control.

I'd appreciate any help because I'm pretty lost in that task.

Thanks a lot

Pedro Antonio Moreno Sanchez
Telecommunication Engineer & Researcher
Bioengineering and Telemedicine Group
ETSI Telecomunicación - UPM A.101-8L.
Ciudad Universitaria s/n
28040 MADRID - SPAIN

Tel. +34 91 549 57 00 ext. 3407
Fax + 34 91 336 68 28
e-mail: pmoreno@gbt.tfo.upm.es

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4638 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#10

Hi,
I don't see it either :slight_smile: so it seems at the end they don't have full
support for it, even you have seen it somewhere mentioned. So you can
grab the jmf source and see whats in it, is something for h263+ in
there. Also you can take a look how is h264 created, all you have to
do is use ffmpeg h263 encoder/decoder and write an appropriate
packetizer. All this can be done and in an the old version of
sip-communicator. Then we can integrate it in the current one with the
patch supplied.

Cheers
damencho

···

On Fri, Nov 27, 2009 at 1:38 PM, PABLO LOPEZ GARCIA <palg@tid.es> wrote:

Hi!

Take a look to http://java.sun.com/javase/technologies/desktop/media/jmf/2.1.1/formats.html because I can't see anything related with H263+

Regards.

Pablo.

-----Mensaje original-----
De: Pedro Moreno [mailto:pmoreno@gbt.tfo.upm.es]
Enviado el: viernes, 27 de noviembre de 2009 12:23
Para: dev@sip-communicator.dev.java.net
Asunto: RE: [sip-comm-dev] JMF in Sip-Communicator

Hi,
As I said before, I'm using an old version of sip-communicator because I'm
working in an application that uses that version and I can't change it now.
I was checking the VideoFormat class and I saw the constant
VideoFormat.H263_1998_RTP is about the H.263+ codec. Although I've find the
problem, as Damencho has said, about the missing from SdpConstant. So, I
suppose that brings me to implement the h.263+ codec like the h.264 is,
isn't it?
Regards
Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de Damian
Minkov
Enviado el: viernes, 27 de noviembre de 2009 11:45
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

As I see we don't advertise that particular payload type, and we do
that because its not fully supported on all operating systems.
You can try adding it. As Lubo said media is deprecated and is no
longer used you must look at neomedia and especially
net.java.sip.communicator.impl.neomedia.MediaUtils. Its h263-1998/rtp
the jmf type name VideoFormat.H263_1998_RTP with payload number 42. As
I see h263+ is only extension of the packetizing and is missing from
SdpConstants.

Cheers
damencho

On Fri, Nov 27, 2009 at 11:28 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> > wrote:

Hi Damencho,

Actually there are three version of h263 codec, and SIP Communicator are
using the first one (the simple h.263). Yesterday I was searching on JMF

web

site and saw that version JMF 2.1.1 supports the h.263+ (the second

version

of h263 codec).

So I suppose that if SIP Communicator is using the latest version of JMF I
would not have to implement the h.263+, like h.264 is. Then, I wanted to
know how the h.263 is implemented, that is, what are the main steps I have
to follow to succeeded in getting the correct implementation of h.263+.

Thanks and regards

Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de

Damian

Minkov
Enviado el: viernes, 27 de noviembre de 2009 10:01
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

we use latest jmf. But this codec will only work on windows and 32bit
linux, it wont work on 64bit linux and on Mac OS X.
And I'm not sure the actual type of h263 implementation in jmf, cause
as I remember there were three or four modifications of this codec.

Cheers
damencho

On Fri, Nov 27, 2009 at 10:46 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> >> wrote:

Hi Lubomir

Thanks for your answer. I'm not working with the latest version of
sip-communicator, so I have to use the media bundle. Yesterday I asked

what

version JMF was, because if it was the 2.1.1 the h.263+ would be in JMF

and

would be easier than doing a complete implementation of h.263+ like

h.264.

Do you know about the version?

Thanks a lot and regards

Pedro

-----Mensaje original-----
De: Lubomir Marinov [mailto:lubo@sip-communicator.org]
Enviado el: jueves, 26 de noviembre de 2009 18:54
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

The media bundle is deprecated and not started in the latest of trunk,
use neomedia.

H.264 is a video codec and is implemented in SIP Communicator. I'd say
that H.263+ should be implemented in the same fashion so it should be
pretty easy to look at the implementation of H.264 which resides in an
appropriately named package.

On Thu, Nov 26, 2009 at 3:31 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> >>> wrote:

Hi,

I'm working trying to develop a patch to use the codec h.263+ in
sip-communicator. I'm starting on that, but firstly I need to know what

JMF

version is using the sip-communicator, ¿is it the JMF 2.1.1?

Does anyone implement any video codec for sip-communicator? What step

should

I follow? I've identified the package impl.media.codec and (maybe) the
impl.media.codec.video as the packages which control the issues related

to

video codec features control.

I'd appreciate any help because I'm pretty lost in that task.

Thanks a lot

Pedro Antonio Moreno Sanchez
Telecommunication Engineer & Researcher
Bioengineering and Telemedicine Group
ETSI Telecomunicación - UPM A.101-8L.
Ciudad Universitaria s/n
28040 MADRID - SPAIN

Tel. +34 91 549 57 00 ext. 3407
Fax + 34 91 336 68 28
e-mail: pmoreno@gbt.tfo.upm.es

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4638 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#11

I may be wrong, but I remember that I read in some place that this change means JMF is ready to receive H263 from a Darwin Server due to Darwin uses a different payload with different packetizations and H263 annexes.

So I don't think JMF include a specific h263+ encoder/decoder.

But as I've said, I'm not sure.

Regards,

Pablo.

···

-----Mensaje original-----
De: Pedro Moreno [mailto:pmoreno@gbt.tfo.upm.es]
Enviado el: viernes, 27 de noviembre de 2009 13:14
Para: dev@sip-communicator.dev.java.net
Asunto: RE: [sip-comm-dev] JMF in Sip-Communicator

Hi Pablo

I checked that page yesterday and it seems that JMF 2.1.1 doesn´t support
the h.263+ codec, but if you take a look to
http://java.sun.com/javase/technologies/desktop/media/jmf/reference/faqs/ind
ex.html#jmf2.1.1 in What is JMF 2.1.1? question you see H.263/1998 (h.263+)
is supported.

But the problem is that in this codec is not mention in sdpConstant, so I
don't if I have to implement like h.264 or just use the JMF and create a
constant for the h.263+ payload.

Any idea??

Thanks

Pedro

-----Mensaje original-----
De: PABLO LOPEZ GARCIA [mailto:palg@tid.es]
Enviado el: viernes, 27 de noviembre de 2009 12:39
Para: dev@sip-communicator.dev.java.net
Asunto: RE: [sip-comm-dev] JMF in Sip-Communicator

Hi!

Take a look to
http://java.sun.com/javase/technologies/desktop/media/jmf/2.1.1/formats.html
because I can't see anything related with H263+

Regards.

Pablo.

-----Mensaje original-----
De: Pedro Moreno [mailto:pmoreno@gbt.tfo.upm.es]
Enviado el: viernes, 27 de noviembre de 2009 12:23
Para: dev@sip-communicator.dev.java.net
Asunto: RE: [sip-comm-dev] JMF in Sip-Communicator

Hi,
As I said before, I'm using an old version of sip-communicator because I'm
working in an application that uses that version and I can't change it now.
I was checking the VideoFormat class and I saw the constant
VideoFormat.H263_1998_RTP is about the H.263+ codec. Although I've find the
problem, as Damencho has said, about the missing from SdpConstant. So, I
suppose that brings me to implement the h.263+ codec like the h.264 is,
isn't it?
Regards
Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de Damian
Minkov
Enviado el: viernes, 27 de noviembre de 2009 11:45
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

As I see we don't advertise that particular payload type, and we do
that because its not fully supported on all operating systems.
You can try adding it. As Lubo said media is deprecated and is no
longer used you must look at neomedia and especially
net.java.sip.communicator.impl.neomedia.MediaUtils. Its h263-1998/rtp
the jmf type name VideoFormat.H263_1998_RTP with payload number 42. As
I see h263+ is only extension of the packetizing and is missing from
SdpConstants.

Cheers
damencho

On Fri, Nov 27, 2009 at 11:28 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> wrote:

Hi Damencho,

Actually there are three version of h263 codec, and SIP Communicator are
using the first one (the simple h.263). Yesterday I was searching on JMF

web

site and saw that version JMF 2.1.1 supports the h.263+ (the second

version

of h263 codec).

So I suppose that if SIP Communicator is using the latest version of JMF I
would not have to implement the h.263+, like h.264 is. Then, I wanted to
know how the h.263 is implemented, that is, what are the main steps I have
to follow to succeeded in getting the correct implementation of h.263+.

Thanks and regards

Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de

Damian

Minkov
Enviado el: viernes, 27 de noviembre de 2009 10:01
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

we use latest jmf. But this codec will only work on windows and 32bit
linux, it wont work on 64bit linux and on Mac OS X.
And I'm not sure the actual type of h263 implementation in jmf, cause
as I remember there were three or four modifications of this codec.

Cheers
damencho

On Fri, Nov 27, 2009 at 10:46 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> > wrote:

Hi Lubomir

Thanks for your answer. I'm not working with the latest version of
sip-communicator, so I have to use the media bundle. Yesterday I asked

what

version JMF was, because if it was the 2.1.1 the h.263+ would be in JMF

and

would be easier than doing a complete implementation of h.263+ like

h.264.

Do you know about the version?

Thanks a lot and regards

Pedro

-----Mensaje original-----
De: Lubomir Marinov [mailto:lubo@sip-communicator.org]
Enviado el: jueves, 26 de noviembre de 2009 18:54
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

The media bundle is deprecated and not started in the latest of trunk,
use neomedia.

H.264 is a video codec and is implemented in SIP Communicator. I'd say
that H.263+ should be implemented in the same fashion so it should be
pretty easy to look at the implementation of H.264 which resides in an
appropriately named package.

On Thu, Nov 26, 2009 at 3:31 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> >> wrote:

Hi,

I'm working trying to develop a patch to use the codec h.263+ in
sip-communicator. I'm starting on that, but firstly I need to know what

JMF

version is using the sip-communicator, ¿is it the JMF 2.1.1?

Does anyone implement any video codec for sip-communicator? What step

should

I follow? I've identified the package impl.media.codec and (maybe) the
impl.media.codec.video as the packages which control the issues related

to

video codec features control.

I'd appreciate any help because I'm pretty lost in that task.

Thanks a lot

Pedro Antonio Moreno Sanchez
Telecommunication Engineer & Researcher
Bioengineering and Telemedicine Group
ETSI Telecomunicación - UPM A.101-8L.
Ciudad Universitaria s/n
28040 MADRID - SPAIN

Tel. +34 91 549 57 00 ext. 3407
Fax + 34 91 336 68 28
e-mail: pmoreno@gbt.tfo.upm.es

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4638 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#12

Hey Pedro,

In addition to what others have just commented about JMF not supporting
H.263+ it may also be worth noting that there is no constant for H.263+
because it is not defined by the RTP Audio Video profile [1]. You'd need
to negotiate it dynamically. You may have a look at [2] for more
information on the H.263+ payload type.

Note that previous versions of SIP Communicator, like the one you seem
to be using, had very poor support for dynamic payload type mapping. You
may therefore want to consider switching to the latest.

Hope this helps,
Emil

[1] http://tools.ietf.org/html/rfc3551
[2] http://tools.ietf.org/html/rfc4629

Pedro Moreno wrote:

···

Hi Pablo

I checked that page yesterday and it seems that JMF 2.1.1 doesn´t support
the h.263+ codec, but if you take a look to
http://java.sun.com/javase/technologies/desktop/media/jmf/reference/faqs/ind
ex.html#jmf2.1.1 in What is JMF 2.1.1? question you see H.263/1998 (h.263+)
is supported.

But the problem is that in this codec is not mention in sdpConstant, so I
don't if I have to implement like h.264 or just use the JMF and create a
constant for the h.263+ payload.

Any idea??

Thanks

Pedro

-----Mensaje original-----
De: PABLO LOPEZ GARCIA [mailto:palg@tid.es]
Enviado el: viernes, 27 de noviembre de 2009 12:39
Para: dev@sip-communicator.dev.java.net
Asunto: RE: [sip-comm-dev] JMF in Sip-Communicator

Hi!

Take a look to
http://java.sun.com/javase/technologies/desktop/media/jmf/2.1.1/formats.html
because I can't see anything related with H263+

Regards.

Pablo.

-----Mensaje original-----
De: Pedro Moreno [mailto:pmoreno@gbt.tfo.upm.es]
Enviado el: viernes, 27 de noviembre de 2009 12:23
Para: dev@sip-communicator.dev.java.net
Asunto: RE: [sip-comm-dev] JMF in Sip-Communicator

Hi,
As I said before, I'm using an old version of sip-communicator because I'm
working in an application that uses that version and I can't change it now.
I was checking the VideoFormat class and I saw the constant
VideoFormat.H263_1998_RTP is about the H.263+ codec. Although I've find the
problem, as Damencho has said, about the missing from SdpConstant. So, I
suppose that brings me to implement the h.263+ codec like the h.264 is,
isn't it?
Regards
Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de Damian
Minkov
Enviado el: viernes, 27 de noviembre de 2009 11:45
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

As I see we don't advertise that particular payload type, and we do
that because its not fully supported on all operating systems.
You can try adding it. As Lubo said media is deprecated and is no
longer used you must look at neomedia and especially
net.java.sip.communicator.impl.neomedia.MediaUtils. Its h263-1998/rtp
the jmf type name VideoFormat.H263_1998_RTP with payload number 42. As
I see h263+ is only extension of the packetizing and is missing from
SdpConstants.

Cheers
damencho

On Fri, Nov 27, 2009 at 11:28 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> > wrote:

Hi Damencho,

Actually there are three version of h263 codec, and SIP Communicator are
using the first one (the simple h.263). Yesterday I was searching on JMF

web

site and saw that version JMF 2.1.1 supports the h.263+ (the second

version

of h263 codec).

So I suppose that if SIP Communicator is using the latest version of JMF I
would not have to implement the h.263+, like h.264 is. Then, I wanted to
know how the h.263 is implemented, that is, what are the main steps I have
to follow to succeeded in getting the correct implementation of h.263+.

Thanks and regards

Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de

Damian

Minkov
Enviado el: viernes, 27 de noviembre de 2009 10:01
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

we use latest jmf. But this codec will only work on windows and 32bit
linux, it wont work on 64bit linux and on Mac OS X.
And I'm not sure the actual type of h263 implementation in jmf, cause
as I remember there were three or four modifications of this codec.

Cheers
damencho

On Fri, Nov 27, 2009 at 10:46 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> >> wrote:

Hi Lubomir

Thanks for your answer. I'm not working with the latest version of
sip-communicator, so I have to use the media bundle. Yesterday I asked

what

version JMF was, because if it was the 2.1.1 the h.263+ would be in JMF

and

would be easier than doing a complete implementation of h.263+ like

h.264.

Do you know about the version?

Thanks a lot and regards

Pedro

-----Mensaje original-----
De: Lubomir Marinov [mailto:lubo@sip-communicator.org]
Enviado el: jueves, 26 de noviembre de 2009 18:54
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

The media bundle is deprecated and not started in the latest of trunk,
use neomedia.

H.264 is a video codec and is implemented in SIP Communicator. I'd say
that H.263+ should be implemented in the same fashion so it should be
pretty easy to look at the implementation of H.264 which resides in an
appropriately named package.

On Thu, Nov 26, 2009 at 3:31 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> >>> wrote:

Hi,

I'm working trying to develop a patch to use the codec h.263+ in
sip-communicator. I'm starting on that, but firstly I need to know what

JMF

version is using the sip-communicator, ¿is it the JMF 2.1.1?

Does anyone implement any video codec for sip-communicator? What step

should

I follow? I've identified the package impl.media.codec and (maybe) the
impl.media.codec.video as the packages which control the issues related

to

video codec features control.

I'd appreciate any help because I'm pretty lost in that task.

Thanks a lot

Pedro Antonio Moreno Sanchez
Telecommunication Engineer & Researcher
Bioengineering and Telemedicine Group
ETSI Telecomunicación - UPM A.101-8L.
Ciudad Universitaria s/n
28040 MADRID - SPAIN

Tel. +34 91 549 57 00 ext. 3407
Fax + 34 91 336 68 28
e-mail: pmoreno@gbt.tfo.upm.es

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4638 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#13

Hi,
I see. You can try that, try adding the format as other formats are
registered (speex, h264, ...) in the rtpManager (rtpManager.addFormat)
and see what happens.

Good Luck
damencho

···

On Fri, Nov 27, 2009 at 2:14 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> wrote:

Hi Pablo

I checked that page yesterday and it seems that JMF 2.1.1 doesn´t support
the h.263+ codec, but if you take a look to
http://java.sun.com/javase/technologies/desktop/media/jmf/reference/faqs/ind
ex.html#jmf2.1.1 in What is JMF 2.1.1? question you see H.263/1998 (h.263+)
is supported.

But the problem is that in this codec is not mention in sdpConstant, so I
don't if I have to implement like h.264 or just use the JMF and create a
constant for the h.263+ payload.

Any idea??

Thanks

Pedro

-----Mensaje original-----
De: PABLO LOPEZ GARCIA [mailto:palg@tid.es]
Enviado el: viernes, 27 de noviembre de 2009 12:39
Para: dev@sip-communicator.dev.java.net
Asunto: RE: [sip-comm-dev] JMF in Sip-Communicator

Hi!

Take a look to
http://java.sun.com/javase/technologies/desktop/media/jmf/2.1.1/formats.html
because I can't see anything related with H263+

Regards.

Pablo.

-----Mensaje original-----
De: Pedro Moreno [mailto:pmoreno@gbt.tfo.upm.es]
Enviado el: viernes, 27 de noviembre de 2009 12:23
Para: dev@sip-communicator.dev.java.net
Asunto: RE: [sip-comm-dev] JMF in Sip-Communicator

Hi,
As I said before, I'm using an old version of sip-communicator because I'm
working in an application that uses that version and I can't change it now.
I was checking the VideoFormat class and I saw the constant
VideoFormat.H263_1998_RTP is about the H.263+ codec. Although I've find the
problem, as Damencho has said, about the missing from SdpConstant. So, I
suppose that brings me to implement the h.263+ codec like the h.264 is,
isn't it?
Regards
Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de Damian
Minkov
Enviado el: viernes, 27 de noviembre de 2009 11:45
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

As I see we don't advertise that particular payload type, and we do
that because its not fully supported on all operating systems.
You can try adding it. As Lubo said media is deprecated and is no
longer used you must look at neomedia and especially
net.java.sip.communicator.impl.neomedia.MediaUtils. Its h263-1998/rtp
the jmf type name VideoFormat.H263_1998_RTP with payload number 42. As
I see h263+ is only extension of the packetizing and is missing from
SdpConstants.

Cheers
damencho

On Fri, Nov 27, 2009 at 11:28 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> > wrote:

Hi Damencho,

Actually there are three version of h263 codec, and SIP Communicator are
using the first one (the simple h.263). Yesterday I was searching on JMF

web

site and saw that version JMF 2.1.1 supports the h.263+ (the second

version

of h263 codec).

So I suppose that if SIP Communicator is using the latest version of JMF I
would not have to implement the h.263+, like h.264 is. Then, I wanted to
know how the h.263 is implemented, that is, what are the main steps I have
to follow to succeeded in getting the correct implementation of h.263+.

Thanks and regards

Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de

Damian

Minkov
Enviado el: viernes, 27 de noviembre de 2009 10:01
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

we use latest jmf. But this codec will only work on windows and 32bit
linux, it wont work on 64bit linux and on Mac OS X.
And I'm not sure the actual type of h263 implementation in jmf, cause
as I remember there were three or four modifications of this codec.

Cheers
damencho

On Fri, Nov 27, 2009 at 10:46 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> >> wrote:

Hi Lubomir

Thanks for your answer. I'm not working with the latest version of
sip-communicator, so I have to use the media bundle. Yesterday I asked

what

version JMF was, because if it was the 2.1.1 the h.263+ would be in JMF

and

would be easier than doing a complete implementation of h.263+ like

h.264.

Do you know about the version?

Thanks a lot and regards

Pedro

-----Mensaje original-----
De: Lubomir Marinov [mailto:lubo@sip-communicator.org]
Enviado el: jueves, 26 de noviembre de 2009 18:54
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

The media bundle is deprecated and not started in the latest of trunk,
use neomedia.

H.264 is a video codec and is implemented in SIP Communicator. I'd say
that H.263+ should be implemented in the same fashion so it should be
pretty easy to look at the implementation of H.264 which resides in an
appropriately named package.

On Thu, Nov 26, 2009 at 3:31 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> >>> wrote:

Hi,

I'm working trying to develop a patch to use the codec h.263+ in
sip-communicator. I'm starting on that, but firstly I need to know what

JMF

version is using the sip-communicator, ¿is it the JMF 2.1.1?

Does anyone implement any video codec for sip-communicator? What step

should

I follow? I've identified the package impl.media.codec and (maybe) the
impl.media.codec.video as the packages which control the issues related

to

video codec features control.

I'd appreciate any help because I'm pretty lost in that task.

Thanks a lot

Pedro Antonio Moreno Sanchez
Telecommunication Engineer & Researcher
Bioengineering and Telemedicine Group
ETSI Telecomunicación - UPM A.101-8L.
Ciudad Universitaria s/n
28040 MADRID - SPAIN

Tel. +34 91 549 57 00 ext. 3407
Fax + 34 91 336 68 28
e-mail: pmoreno@gbt.tfo.upm.es

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4638 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#14

Hello,

I'm going back to work in that issue about codec h.263+ I was talking with
all of you. I've decided to use the FFMPEG libraries that SIP-Comm uses to
implement h264 codec as example. I'm sure that I should implement 4 object
(packetizer, encoder, decoder, parser). I've downloaded the FFMPEG source
code to check the encoder/decoder files with the JNIEncoder and JNIDecoder
of H.264 in SIPComm, and it seems to be very different between them. At the
moment I'm bit lost because I don’t know how to follow with the h.263+
implementation.

Could anybody help me, please??

I'd appreciate your contribution

Regards

···

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de Damian
Minkov
Enviado el: viernes, 27 de noviembre de 2009 13:22
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,
I see. You can try that, try adding the format as other formats are
registered (speex, h264, ...) in the rtpManager (rtpManager.addFormat)
and see what happens.

Good Luck
damencho

On Fri, Nov 27, 2009 at 2:14 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> wrote:

Hi Pablo

I checked that page yesterday and it seems that JMF 2.1.1 doesn´t support
the h.263+ codec, but if you take a look to

http://java.sun.com/javase/technologies/desktop/media/jmf/reference/faqs/ind

ex.html#jmf2.1.1 in What is JMF 2.1.1? question you see H.263/1998

(h.263+)

is supported.

But the problem is that in this codec is not mention in sdpConstant, so I
don't if I have to implement like h.264 or just use the JMF and create a
constant for the h.263+ payload.

Any idea??

Thanks

Pedro

-----Mensaje original-----
De: PABLO LOPEZ GARCIA [mailto:palg@tid.es]
Enviado el: viernes, 27 de noviembre de 2009 12:39
Para: dev@sip-communicator.dev.java.net
Asunto: RE: [sip-comm-dev] JMF in Sip-Communicator

Hi!

Take a look to

http://java.sun.com/javase/technologies/desktop/media/jmf/2.1.1/formats.html

because I can't see anything related with H263+

Regards.

Pablo.

-----Mensaje original-----
De: Pedro Moreno [mailto:pmoreno@gbt.tfo.upm.es]
Enviado el: viernes, 27 de noviembre de 2009 12:23
Para: dev@sip-communicator.dev.java.net
Asunto: RE: [sip-comm-dev] JMF in Sip-Communicator

Hi,
As I said before, I'm using an old version of sip-communicator because I'm
working in an application that uses that version and I can't change it

now.

I was checking the VideoFormat class and I saw the constant
VideoFormat.H263_1998_RTP is about the H.263+ codec. Although I've find

the

problem, as Damencho has said, about the missing from SdpConstant. So, I
suppose that brings me to implement the h.263+ codec like the h.264 is,
isn't it?
Regards
Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de

Damian

Minkov
Enviado el: viernes, 27 de noviembre de 2009 11:45
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

As I see we don't advertise that particular payload type, and we do
that because its not fully supported on all operating systems.
You can try adding it. As Lubo said media is deprecated and is no
longer used you must look at neomedia and especially
net.java.sip.communicator.impl.neomedia.MediaUtils. Its h263-1998/rtp
the jmf type name VideoFormat.H263_1998_RTP with payload number 42. As
I see h263+ is only extension of the packetizing and is missing from
SdpConstants.

Cheers
damencho

On Fri, Nov 27, 2009 at 11:28 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> > wrote:

Hi Damencho,

Actually there are three version of h263 codec, and SIP Communicator are
using the first one (the simple h.263). Yesterday I was searching on JMF

web

site and saw that version JMF 2.1.1 supports the h.263+ (the second

version

of h263 codec).

So I suppose that if SIP Communicator is using the latest version of JMF

I

would not have to implement the h.263+, like h.264 is. Then, I wanted to
know how the h.263 is implemented, that is, what are the main steps I

have

to follow to succeeded in getting the correct implementation of h.263+.

Thanks and regards

Pedro

-----Mensaje original-----
De: damencho@damencho.com [mailto:damencho@damencho.com] En nombre de

Damian

Minkov
Enviado el: viernes, 27 de noviembre de 2009 10:01
Para: dev
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

Hi,

we use latest jmf. But this codec will only work on windows and 32bit
linux, it wont work on 64bit linux and on Mac OS X.
And I'm not sure the actual type of h263 implementation in jmf, cause
as I remember there were three or four modifications of this codec.

Cheers
damencho

On Fri, Nov 27, 2009 at 10:46 AM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> >> wrote:

Hi Lubomir

Thanks for your answer. I'm not working with the latest version of
sip-communicator, so I have to use the media bundle. Yesterday I asked

what

version JMF was, because if it was the 2.1.1 the h.263+ would be in JMF

and

would be easier than doing a complete implementation of h.263+ like

h.264.

Do you know about the version?

Thanks a lot and regards

Pedro

-----Mensaje original-----
De: Lubomir Marinov [mailto:lubo@sip-communicator.org]
Enviado el: jueves, 26 de noviembre de 2009 18:54
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] JMF in Sip-Communicator

The media bundle is deprecated and not started in the latest of trunk,
use neomedia.

H.264 is a video codec and is implemented in SIP Communicator. I'd say
that H.263+ should be implemented in the same fashion so it should be
pretty easy to look at the implementation of H.264 which resides in an
appropriately named package.

On Thu, Nov 26, 2009 at 3:31 PM, Pedro Moreno <pmoreno@gbt.tfo.upm.es> >>> wrote:

Hi,

I'm working trying to develop a patch to use the codec h.263+ in
sip-communicator. I'm starting on that, but firstly I need to know what

JMF

version is using the sip-communicator, ¿is it the JMF 2.1.1?

Does anyone implement any video codec for sip-communicator? What step

should

I follow? I've identified the package impl.media.codec and (maybe) the
impl.media.codec.video as the packages which control the issues related

to

video codec features control.

I'd appreciate any help because I'm pretty lost in that task.

Thanks a lot

Pedro Antonio Moreno Sanchez
Telecommunication Engineer & Researcher
Bioengineering and Telemedicine Group
ETSI Telecomunicación - UPM A.101-8L.
Ciudad Universitaria s/n
28040 MADRID - SPAIN

Tel. +34 91 549 57 00 ext. 3407
Fax + 34 91 336 68 28
e-mail: pmoreno@gbt.tfo.upm.es

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4638 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4640 (20091126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus

signature

database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4641 (20091127) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET Smart Security, version of virus signature
database 4762 (20100111) __________

The message was checked by ESET Smart Security.

http://www.eset.com

__________ Information from ESET Smart Security, version of virus signature
database 4762 (20100111) __________

The message was checked by ESET Smart Security.

http://www.eset.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net