[sip-comm-dev] I cant send video on Ubuntu version (maybe problem with h.264)


#1

Hello,

I'm working with SIPCommunicator on Ubuntu version. When I try to
establish a call with another user I can see his video but my video isn't
transmmited. I've been wondering why and I think that the reason is the
H.264 codec, because I get this session description of invite request
(catch with wireshark):

Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): pmoreno 0 0 IN IP4 138.4.10.142
Connection Information (c): IN IP4 138.4.10.142
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 5000 RTP/AVP 0 8 97 3 5 4
Media Attribute (a): rtpmap:4 G723/8000
Media Attribute (a): fmtp:4 annexa=no;bitrate=6.3
Media Description, name and address (m): video 5002 RTP/AVP 99 34 26 31
Media Attribute (a): rtpmap:99 H264/90000
Media Attribute (a): fmtp:99 packetization-mode=1
Media Attribute (a): recvonly

Why "recvonly"?? It should be "sendrecv", isn't it?

I've missed any specific packet on ubuntu, which is not neccesary on WinXP?

Can anybody help me? I've very stuck with this problem

Thanks a lot in advance

Pedro

···

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


#2

Hello Pedro,

We place the recvonly attribute when we can't transmit in a particular
media type. The most common reason for this is a missing device, so in
your case this is probably due to a problem with your webcam.

LTI-CIVIL only support v4l2 so make sure that you have v4l2 drivers
installed and working for your device.

Good luck!
Emil

pmoreno@gbt.tfo.upm.es wrote:

···

Hello,

I'm working with SIPCommunicator on Ubuntu version. When I try to
establish a call with another user I can see his video but my video isn't
transmmited. I've been wondering why and I think that the reason is the
H.264 codec, because I get this session description of invite request
(catch with wireshark):

Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): pmoreno 0 0 IN IP4 138.4.10.142
Connection Information (c): IN IP4 138.4.10.142
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 5000 RTP/AVP 0 8 97 3 5 4
Media Attribute (a): rtpmap:4 G723/8000
Media Attribute (a): fmtp:4 annexa=no;bitrate=6.3
Media Description, name and address (m): video 5002 RTP/AVP 99 34 26 31
Media Attribute (a): rtpmap:99 H264/90000
Media Attribute (a): fmtp:99 packetization-mode=1
Media Attribute (a): recvonly

Why "recvonly"?? It should be "sendrecv", isn't it?

I've missed any specific packet on ubuntu, which is not neccesary on WinXP?

Can anybody help me? I've very stuck with this problem

Thanks a lot in advance

Pedro

---------------------------------------------------------------------
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


#3

Hello Emil,

Thanks for your answer. First of all, I've to say I'm newbie on Ubuntu and I
don't know how to know if the v4l2 are installed.

I think that the driver is installed because on SIPCommunicator if I go to
media in option menu
I can see my camera is working on preview framework. But when I establish a
call I get the message I wrote. Is the video in preview media option related
to the driver v4l2?

I've to say I get this problem with the SIPCommunicator installed on my PC
and running the SIPCommunicator as a project through Eclipse. I suppose that
the problem come from my camera..

Please can you help me? I'd appreciate a lot.

Thanks in advance

Pedro

Enviado el: viernes, 24 de julio de 2009 15:52
problem with h.264)

Hello Pedro,

We place the recvonly attribute when we can't transmit in a particular
media type. The most common reason for this is a missing device, so in
your case this is probably due to a problem with your webcam.

LTI-CIVIL only support v4l2 so make sure that you have v4l2 drivers
installed and working for your device.

Good luck!
Emil

pmoreno@gbt.tfo.upm.es wrote:

Hello,

I'm working with SIPCommunicator on Ubuntu version. When I try to
establish a call with another user I can see his video but my video isn't
transmmited. I've been wondering why and I think that the reason is the
H.264 codec, because I get this session description of invite request
(catch with wireshark):

Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): pmoreno 0 0 IN IP4 138.4.10.142
Connection Information (c): IN IP4 138.4.10.142
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 5000 RTP/AVP 0 8 97 3 5 4
Media Attribute (a): rtpmap:4 G723/8000
Media Attribute (a): fmtp:4 annexa=no;bitrate=6.3
Media Description, name and address (m): video 5002 RTP/AVP 99 34 26 31
Media Attribute (a): rtpmap:99 H264/90000
Media Attribute (a): fmtp:99 packetization-mode=1
Media Attribute (a): recvonly

Why "recvonly"?? It should be "sendrecv", isn't it?

I've missed any specific packet on ubuntu, which is not neccesary on

WinXP?

···

-----Mensaje original-----
De: Emil Ivov [mailto:emil@sip-communicator.org] En nombre de Emil Ivov
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] I cant send video on Ubuntu version (maybe

Can anybody help me? I've very stuck with this problem

Thanks a lot in advance

Pedro

---------------------------------------------------------------------
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

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4280 (20090726) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4280 (20090726) __________

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,

you mean you are running two instances of sip-communicator on one PC ?
If this is the case you have to know that only on app can access the camera device.

Cheers
damencho

Pedro Moreno wrote:

···

Hello Emil,

Thanks for your answer. First of all, I've to say I'm newbie on Ubuntu and I
don't know how to know if the v4l2 are installed.

I think that the driver is installed because on SIPCommunicator if I go to
media in option menu I can see my camera is working on preview framework. But when I establish a
call I get the message I wrote. Is the video in preview media option related
to the driver v4l2?

I've to say I get this problem with the SIPCommunicator installed on my PC
and running the SIPCommunicator as a project through Eclipse. I suppose that
the problem come from my camera..

Please can you help me? I'd appreciate a lot.

Thanks in advance

Pedro

-----Mensaje original-----
De: Emil Ivov [mailto:emil@sip-communicator.org] En nombre de Emil Ivov
Enviado el: viernes, 24 de julio de 2009 15:52
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] I cant send video on Ubuntu version (maybe
problem with h.264)

Hello Pedro,

We place the recvonly attribute when we can't transmit in a particular
media type. The most common reason for this is a missing device, so in
your case this is probably due to a problem with your webcam.

LTI-CIVIL only support v4l2 so make sure that you have v4l2 drivers
installed and working for your device.

Good luck!
Emil

pmoreno@gbt.tfo.upm.es wrote:
  

Hello,

I'm working with SIPCommunicator on Ubuntu version. When I try to
establish a call with another user I can see his video but my video isn't
transmmited. I've been wondering why and I think that the reason is the
H.264 codec, because I get this session description of invite request
(catch with wireshark):

Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): pmoreno 0 0 IN IP4 138.4.10.142
Connection Information (c): IN IP4 138.4.10.142
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 5000 RTP/AVP 0 8 97 3 5 4
Media Attribute (a): rtpmap:4 G723/8000
Media Attribute (a): fmtp:4 annexa=no;bitrate=6.3
Media Description, name and address (m): video 5002 RTP/AVP 99 34 26 31
Media Attribute (a): rtpmap:99 H264/90000
Media Attribute (a): fmtp:99 packetization-mode=1
Media Attribute (a): recvonly

Why "recvonly"?? It should be "sendrecv", isn't it?

I've missed any specific packet on ubuntu, which is not neccesary on
    

WinXP?
  

Can anybody help me? I've very stuck with this problem

Thanks a lot in advance

Pedro

---------------------------------------------------------------------
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,

Sorry, but I didn't mean I runned two instances of SIPComm at the same
time. I tried the application twice separately. The first time I got the
error running the SIPcommunicator through eclipse, and then I close the
application and got the same problem running the application as an
installed application.

So, I mean I didnt run the two ways at the same time, I runned each way
separately.

But I would like to emphasize that I can see image in the preview
framework from my camera, but I cant see any image when I establish a
call. So, I think that the v4l2 drivers are installed, but I'm not sure.

Please again, any help?

Thanks a lot

Pedro

···

Hi,

you mean you are running two instances of sip-communicator on one PC ?
If this is the case you have to know that only on app can access the
camera device.

Cheers
damencho

Pedro Moreno wrote:

Hello Emil,

Thanks for your answer. First of all, I've to say I'm newbie on Ubuntu
and I
don't know how to know if the v4l2 are installed.

I think that the driver is installed because on SIPCommunicator if I go
to
media in option menu
I can see my camera is working on preview framework. But when I
establish a
call I get the message I wrote. Is the video in preview media option
related
to the driver v4l2?

I've to say I get this problem with the SIPCommunicator installed on my
PC
and running the SIPCommunicator as a project through Eclipse. I suppose
that
the problem come from my camera..

Please can you help me? I'd appreciate a lot.

Thanks in advance

Pedro

-----Mensaje original-----
De: Emil Ivov [mailto:emil@sip-communicator.org] En nombre de Emil Ivov
Enviado el: viernes, 24 de julio de 2009 15:52
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] I cant send video on Ubuntu version (maybe
problem with h.264)

Hello Pedro,

We place the recvonly attribute when we can't transmit in a particular
media type. The most common reason for this is a missing device, so in
your case this is probably due to a problem with your webcam.

LTI-CIVIL only support v4l2 so make sure that you have v4l2 drivers
installed and working for your device.

Good luck!
Emil

pmoreno@gbt.tfo.upm.es wrote:

Hello,

I'm working with SIPCommunicator on Ubuntu version. When I try to
establish a call with another user I can see his video but my video
isn't
transmmited. I've been wondering why and I think that the reason is the
H.264 codec, because I get this session description of invite request
(catch with wireshark):

Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): pmoreno 0 0 IN IP4 138.4.10.142
Connection Information (c): IN IP4 138.4.10.142
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 5000 RTP/AVP 0 8 97 3 5
4
Media Attribute (a): rtpmap:4 G723/8000
Media Attribute (a): fmtp:4 annexa=no;bitrate=6.3
Media Description, name and address (m): video 5002 RTP/AVP 99 34 26 31
Media Attribute (a): rtpmap:99 H264/90000
Media Attribute (a): fmtp:99 packetization-mode=1
Media Attribute (a): recvonly

Why "recvonly"?? It should be "sendrecv", isn't it?

I've missed any specific packet on ubuntu, which is not neccesary on

WinXP?

Can anybody help me? I've very stuck with this problem

Thanks a lot in advance

Pedro

---------------------------------------------------------------------
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


#6

Hey Pedro,

I believe I've also heard the same problem (preview is available but
nothing gets streamed) also mentioned by other people. Yet I don't
believe we have an entry for it in the tracker. Could you please create
one? Attaching logs and wireshark traces would also help.

Thanks!
Emil

pmoreno@gbt.tfo.upm.es wrote:

···

Hi,

Sorry, but I didn't mean I runned two instances of SIPComm at the same
time. I tried the application twice separately. The first time I got the
error running the SIPcommunicator through eclipse, and then I close the
application and got the same problem running the application as an
installed application.

So, I mean I didnt run the two ways at the same time, I runned each way
separately.

But I would like to emphasize that I can see image in the preview
framework from my camera, but I cant see any image when I establish a
call. So, I think that the v4l2 drivers are installed, but I'm not sure.

Please again, any help?

Thanks a lot

Pedro

Hi,

you mean you are running two instances of sip-communicator on one PC ?
If this is the case you have to know that only on app can access the
camera device.

Cheers
damencho

Pedro Moreno wrote:

Hello Emil,

Thanks for your answer. First of all, I've to say I'm newbie on Ubuntu
and I
don't know how to know if the v4l2 are installed.

I think that the driver is installed because on SIPCommunicator if I go
to
media in option menu
I can see my camera is working on preview framework. But when I
establish a
call I get the message I wrote. Is the video in preview media option
related
to the driver v4l2?

I've to say I get this problem with the SIPCommunicator installed on my
PC
and running the SIPCommunicator as a project through Eclipse. I suppose
that
the problem come from my camera..

Please can you help me? I'd appreciate a lot.

Thanks in advance

Pedro

-----Mensaje original-----
De: Emil Ivov [mailto:emil@sip-communicator.org] En nombre de Emil Ivov
Enviado el: viernes, 24 de julio de 2009 15:52
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] I cant send video on Ubuntu version (maybe
problem with h.264)

Hello Pedro,

We place the recvonly attribute when we can't transmit in a particular
media type. The most common reason for this is a missing device, so in
your case this is probably due to a problem with your webcam.

LTI-CIVIL only support v4l2 so make sure that you have v4l2 drivers
installed and working for your device.

Good luck!
Emil

pmoreno@gbt.tfo.upm.es wrote:

Hello,

I'm working with SIPCommunicator on Ubuntu version. When I try to
establish a call with another user I can see his video but my video
isn't
transmmited. I've been wondering why and I think that the reason is the
H.264 codec, because I get this session description of invite request
(catch with wireshark):

Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): pmoreno 0 0 IN IP4 138.4.10.142
Connection Information (c): IN IP4 138.4.10.142
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 5000 RTP/AVP 0 8 97 3 5
4
Media Attribute (a): rtpmap:4 G723/8000
Media Attribute (a): fmtp:4 annexa=no;bitrate=6.3
Media Description, name and address (m): video 5002 RTP/AVP 99 34 26 31
Media Attribute (a): rtpmap:99 H264/90000
Media Attribute (a): fmtp:99 packetization-mode=1
Media Attribute (a): recvonly

Why "recvonly"?? It should be "sendrecv", isn't it?

I've missed any specific packet on ubuntu, which is not neccesary on

WinXP?

Can anybody help me? I've very stuck with this problem

Thanks a lot in advance

Pedro

---------------------------------------------------------------------
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

--
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


#7

Hi Emil,

I've tried to establish a call for getting the message I wrote in my first
message from the log file.

As a summary, when SIPCommunicator start It recognize the camera devices,
but when you try to establish a call SIPComm doesn't recognize any devices
(), only sound devices. As it's shown below I've put pieces of the log file
related to the init of SIPCommunicator, when it recognizes the devices, and
then when I send a Invite response:

14:21:46.809 INFO: impl.media.device.JavaSoundAuto.<init>().43 JavaSound
Capture Supported = true
14:21:46.852 INFO: impl.protocol.ssh.SSHActivator.start().79 SSH protocol
implementation [STARTED].
14:21:46.854 LA MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.start().42 [entry] start
14:21:46.857 INFO: impl.netaddr.NetworkAddressManagerServiceImpl.start().141
Stun server address(null)/port(null) not set (or invalid). Disabling STUN.
14:21:46.857 INFO: impl.netaddr.NetworkAddressManagerServiceImpl.start().59
Network Address Manager ...[ STARTED ]
14:21:46.857 INFO: impl.netaddr.NetworkAddressManagerServiceImpl.start().64
Network Address Manager Service ...[REGISTERED]
14:21:46.858 LA MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.start().68 [exit] start
14:21:46.941 INFO: impl.protocol.zeroconf.ZeroconfActivator.start().74
Zeroconf protocol implementation [STARTED].
14:21:46.944 INFO: impl.media.device.JavaSoundAuto.<init>().69
JavaSoundAuto: Committed ok
14:21:47.005 INFO: impl.protocol.irc.IrcActivator.start().69 IRC protocol
implementation [STARTED].
14:21:47.050 FINA:
impl.media.device.JmfDeviceDetector.detectCaptureDevices().164 No FMJ
javasound detected: net.sf.fmj.media.cdp.javasound.CaptureDevicePlugger
14:21:47.050 INFO:
impl.media.device.JmfDeviceDetector.detectCaptureDevices().176 Looking for
video capture devices
14:21:47.052 INFO: impl.protocol.dict.DictActivator.start().66 DICT protocol
implementation [STARTED].
14:21:47.095 FINA: impl.contactlist.ContactlistActivator.start().40 Service
Impl: net.java.sip.communicator.impl.contactlist.ContactlistActivator [
STARTED ]
14:21:47.100 MÁS FINA: impl.protocol.sip.SipStackSharing.<init>().92 Created
stack: gov.nist.javax.sip.SipStackImpl@e4d0cd
14:21:47.111 FINA: fmj.addCaptureDevices() CaptureDevicePlugger: Added
civil:/dev/video0
14:21:47.112 FINA: fmj.addCaptureDevices() CaptureDevicePlugger: Added
civil:/dev/video1
14:21:47.112 LA MÁS FINA: impl.media.device.JmfDeviceDetector.setupJMF().394
[exit] setupJMF
14:21:47.112 INFO:
impl.media.device.DeviceConfiguration.extractConfiguredCaptureDevices().106
Scanning for configured Audio Devices.
14:21:47.113 FINA:
impl.media.device.DeviceConfiguration.extractConfiguredCaptureDevices().118
Found 1 capture devices: [Ljavax.media.CaptureDeviceInfo;@869470
14:21:47.113 INFO:
impl.media.device.DeviceConfiguration.extractConfiguredCaptureDevices().137
Found JavaSound audio capture as an audio capture device.
14:21:47.113 INFO:
impl.media.device.DeviceConfiguration.extractConfiguredCaptureDevices().145
Scanning for configured Video Devices.
14:21:47.113 INFO:
impl.media.device.DeviceConfiguration.extractConfiguredVideoCaptureDevice().
186 Found civil:/dev/video0:0 as an RGB Video Device.
14:21:47.114 MÁS FINA:
impl.protocol.sip.ProtocolProviderServiceSipImpl.resolveSipAddress().2146
Returned SRV null
14:21:47.114 FINA:
impl.media.codec.EncodingConfiguration.registerCustomPackages().398 Adding
package : net.java.sip.communicator.impl
14:21:47.114 FINA:
impl.media.codec.EncodingConfiguration.registerCustomPackages().398 Adding
package : net.sf.fmj
14:21:47.134 FINA:
impl.media.codec.EncodingConfiguration.registerCustomPackages().404
Registering new protocol prefix list : [javax, com.sun, com.ibm,
net.java.sip.communicator.impl, net.sf.fmj]
14:21:47.134 INFO: impl.media.MediaControl.createDataSource().582 Creating
datasource for:javasound://44100
14:21:47.136 FINA: impl.contactlist.MetaContactListServiceImpl.start().146
Starting the meta contact list implementation.
14:21:47.137 LA MÁS FINA:
impl.fileaccess.FileAccessServiceImpl.getPrivatePersistentFile().112 [entry]
getPrivatePersistentFile
14:21:47.137 LA MÁS FINA:
impl.fileaccess.FileAccessServiceImpl.accessibleFile().319 [entry]
accessibleFile
14:21:47.137 LA MÁS FINA:
impl.fileaccess.FileAccessServiceImpl.accessibleFile().354 [exit]
accessibleFile
14:21:47.137 LA MÁS FINA:
impl.fileaccess.FileAccessServiceImpl.getPrivatePersistentFile().126 [exit]
getPrivatePersistentFile
14:21:47.167 FINA: impl.contactlist.ContactlistActivator.start().50 Service
Impl: net.java.sip.communicator.impl.contactlist.ContactlistActivator
[REGISTERED]
14:21:47.218 MÁS FINA:
impl.contactlist.MetaContactListServiceImpl.serviceChanged().1925 Received a
service event for:
net.java.sip.communicator.impl.protocol.rss.ProtocolProviderFactoryRssImpl
14:21:47.219 INFO: impl.protocol.rss.RssActivator.start().93 RSS protocol
implementation [STARTED].

And the part related to invite response:

14:22:45.737 FINA: service.protocol.Call.fireCallParticipantEvent().189
Dispatching a CallParticipant event to 0 listeners. event is:
CallParticipantEvent: ID=1 source participant=sip:petermoreno@ekiga.net
<sip:petermoreno@ekiga.net>;status=Unknown source call=Call:
id=124878376573032258780 participants=1
14:22:45.739 FINA:
service.protocol.AbstractCallParticipant.fireCallParticipantChangeEvent().19
1 Dispatching a CallParticipantChangeEvent event to 1 listeners. event is:
CallParticipantChangeEvent: type=CallParticipantStatusChange
oldV=net.java.sip.communicator.service.protocol.CallParticipantState:Unknown
newV=net.java.sip.communicator.service.protocol.CallParticipantState:Initiat
ing Call for participant=sip:petermoreno@ekiga.net
<sip:petermoreno@ekiga.net>;status=Initiating Call
14:22:45.741 FINA:
service.protocol.AbstractOperationSetBasicTelephony.fireCallEvent().65
Dispatching a CallEvent to 3 listeners. event is: CallEvent:[ id=1
Call=Call: id=124878376573032258780 participants=1]
14:22:45.907 FINA:
impl.media.CallSessionImpl.registerCustomCodecFormats().2479 registering
format ilbc/rtp, 8000.0 Hz, 16-bit, Mono, LittleEndian, Signed with RTP
manager
14:22:45.908 FINA:
impl.media.CallSessionImpl.registerCustomCodecFormats().2479 registering
format ALAW/rtp, 8000.0 Hz, 8-bit, Mono, Signed with RTP manager
14:22:45.908 FINA:
impl.media.CallSessionImpl.registerCustomCodecFormats().2479 registering
format speex/rtp, 8000.0 Hz, 8-bit, Mono, Signed with RTP manager
14:22:45.909 FINA:
impl.media.CallSessionImpl.registerCustomVideoCodecFormats().2504
registering format H264/RTP with RTP manager
14:22:45.911 MÁS FINA:
impl.protocol.sip.ProtocolProviderServiceSipImpl.resolveSipAddress().2146
Returned SRV null
14:22:45.941 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying a
localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.942 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will return
the following localhost address: /138.4.10.142
14:22:45.944 FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getPublicAddressFor().420 Stun
is disabled for destination ekiga.net/86.64.162.35, skipping mapped address
recovery (useStun=false, IPv6@=false).
14:22:45.945 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying a
localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.945 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will return
the following localhost address: /138.4.10.142
14:22:45.945 FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getPublicAddressFor().420 Stun
is disabled for destination ekiga.net/86.64.162.35, skipping mapped address
recovery (useStun=false, IPv6@=false).
14:22:45.946 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying a
localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.946 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will return
the following localhost address: /138.4.10.142
14:22:45.947 FINA: impl.media.CallSessionImpl.allocateMediaPorts().2215
AudioSessionAddress=DataAddress: /138.4.10.142
ControlAddress: /138.4.10.142
DataPort: 5000
ControlPort: 5001
14:22:45.948 FINA: impl.media.CallSessionImpl.allocateMediaPorts().2216
AudioPublicAddress=/138.4.10.142:5000
14:22:45.948 FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getPublicAddressFor().420 Stun
is disabled for destination ekiga.net/86.64.162.35, skipping mapped address
recovery (useStun=false, IPv6@=false).
14:22:45.948 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying a
localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.949 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will return
the following localhost address: /138.4.10.142
14:22:45.949 FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getPublicAddressFor().420 Stun
is disabled for destination ekiga.net/86.64.162.35, skipping mapped address
recovery (useStun=false, IPv6@=false).
14:22:45.950 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying a
localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.950 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will return
the following localhost address: /138.4.10.142
14:22:45.965 FINA: javax.media.rtp.rtcp.SourceDescription.generateCNAME()
this is the CNAME method.
14:22:45.966 FINA: javax.media.rtp.rtcp.SourceDescription.generateCNAME()
Returning cname=pmoreno@pmoreno-laptop
14:22:46.088 INFO:
impl.media.transform.zrtp.SecurityEventManager.showMessage().298
AUDIO_SESSION: ZRTP message: severity: Info, sub code: ZRTPNotEnabledByUser,
DH session: true, multi: 0
14:22:46.088 MÁS FINA:
impl.media.CallSessionImpl.initializeRtpManager().2347 RTP audio manager
initialized through connector
14:22:46.088 MÁS FINA:
impl.media.CallSessionImpl.initializeRtpManager().2444 set receiver buffer
len to=100
14:22:46.088 FINA: javax.media.rtp.rtcp.SourceDescription.generateCNAME()
this is the CNAME method.
14:22:46.089 FINA: javax.media.rtp.rtcp.SourceDescription.generateCNAME()
Returning cname=pmoreno@pmoreno-laptop
14:22:46.093 INFO:
impl.media.transform.zrtp.SecurityEventManager.showMessage().298
VIDEO_SESSION: ZRTP message: severity: Info, sub code: ZRTPNotEnabledByUser,
DH session: false, multi: 0
14:22:46.093 MÁS FINA:
impl.media.CallSessionImpl.initializeRtpManager().2347 RTPvideomanager
initialized through connector
14:22:46.093 MÁS FINA:
impl.media.CallSessionImpl.initializeRtpManager().2444 set receiver buffer
len to=100
14:22:46.095 FINA:
impl.media.CallSessionImpl.createSessionDescription().1678 Will create media
descs with: audio public address=/138.4.10.142:5000 and video public
address=/138.4.10.142:5002
14:22:46.095 FINA: impl.media.MediaControl.calculateSupportedEncodings().447
We will be able to transmit in:
14:22:46.119 FINA: impl.media.MediaControl.calculateSupportedEncodings().470
Audio=[1]=dvi/rtp; sdp=5
14:22:46.120 FINA: impl.media.MediaControl.calculateSupportedEncodings().470
Audio=[2]=ilbc/rtp; sdp=97
14:22:46.120 FINA: impl.media.MediaControl.calculateSupportedEncodings().470
Audio=[5]=g723/rtp; sdp=4
14:22:46.120 FINA: impl.media.MediaControl.calculateSupportedEncodings().470
Audio=[6]=gsm/rtp; sdp=3
14:22:46.120 FINA: impl.media.MediaControl.calculateSupportedEncodings().470
Audio=[7]=ULAW/rtp; sdp=0
14:22:46.120 FINA: impl.media.MediaControl.calculateSupportedEncodings().470
Audio=[8]=ALAW/rtp; sdp=8
14:22:46.121 FINA: impl.media.MediaControl.calculateSupportedEncodings().491
unknown encoding format mpegaudio/rtp
14:22:46.121 FINA: impl.media.MediaControl.calculateSupportedEncodings().491
unknown encoding format mpegaudio/rtp
14:22:46.121 FINA: impl.media.MediaControl.calculateSupportedEncodings().491
unknown encoding format mpegaudio/rtp
14:22:46.121 FINA: impl.media.MediaControl.calculateSupportedEncodings().491
unknown encoding format mpegaudio/rtp
14:22:46.121 FINA: impl.media.MediaControl.calculateSupportedEncodings().491
unknown encoding format mpegaudio/rtp
14:22:46.121 FINA: impl.media.MediaControl.calculateSupportedEncodings().491
unknown encoding format mpegaudio/rtp
14:22:46.121 FINA: impl.media.MediaControl.calculateSupportedEncodings().491
unknown encoding format mpegaudio/rtp
14:22:46.127 MÁS FINA:
impl.media.CallSessionImpl.createSessionDescription().1691 Generated SDP -
v=0
o=pmoreno 0 0 IN IP4 138.4.10.142
s=-
c=IN IP4 138.4.10.142
t=0 0
m=audio 5000 RTP/AVP 0 8 97 3 5 4
a=rtpmap:4 G723/8000
a=fmtp:4 annexa=no;bitrate=6.3
m=video 5002 RTP/AVP 99 34 26 31
a=rtpmap:99 H264/90000
a=fmtp:99 packetization-mode=1
a=recvonly

14:22:46.128 FINA:
impl.protocol.sip.OperationSetBasicTelephonySipImpl.createOutgoingCall().305
sent request:
INVITE sip:petermoreno@ekiga.net SIP/2.0
Call-ID: 051aab13308e297589f39103bc8fe37b@0:0:0:0:0:0:0:0
CSeq: 1 INVITE

From: <sip:pmoreno@ekiga.net>;tag=5e6a0ed6

Via: SIP/2.0/UDP
138.4.10.142:5060;branch=z9hG4bKcec6e84b0dad8b165271d418bc9eafca
Max-Forwards: 70
User-Agent: SIP Communicator1.0-alpha3-nightly.build.1952Linux
Contact: "pmoreno"
<sip:pmoreno@138.4.10.142:5060;transport=udp;registering_acc=ekiga_net>
Content-Type: application/sdp
Content-Length: 266

v=0
o=pmoreno 0 0 IN IP4 138.4.10.142
s=-
c=IN IP4 138.4.10.142
t=0 0
m=audio 5000 RTP/AVP 0 8 97 3 5 4
a=rtpmap:4 G723/8000
a=fmtp:4 annexa=no;bitrate=6.3
m=video 5002 RTP/AVP 99 34 26 31
a=rtpmap:99 H264/90000
a=fmtp:99 packetization-mode=1
a=recvonly

14:22:46.167 MÁS FINA:
impl.protocol.sip.SipStackSharing.processResponse().565 received response:
100 Giving a try
14:22:46.167 MÁS FINA:
impl.protocol.sip.SipStackSharing.getServiceData().847 service was found in
request data
14:22:46.167 FINA:
impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse().528
received response=
SIP/2.0 100 Giving a try
Call-ID: 051aab13308e297589f39103bc8fe37b@0:0:0:0:0:0:0:0
CSeq: 1 INVITE

From: <sip:pmoreno@ekiga.net>;tag=5e6a0ed6

Via: SIP/2.0/UDP
138.4.10.142:5060;branch=z9hG4bKcec6e84b0dad8b165271d418bc9eafca
Server: Kamailio (1.4.0-notls (i386/linux))
Content-Length: 0

I don’t know what is happening, even I've installed all packages related to
v4l2 drivers on Ubuntu.

Do I miss anything? Please help me, because I'm very stuck with this and I
need to solve this problem

Thanks a lot in advance

Regards

Pedro

Enviado el: martes, 28 de julio de 2009 2:48
problem with h.264)

Hey Pedro,

I believe I've also heard the same problem (preview is available but
nothing gets streamed) also mentioned by other people. Yet I don't
believe we have an entry for it in the tracker. Could you please create
one? Attaching logs and wireshark traces would also help.

Thanks!
Emil

pmoreno@gbt.tfo.upm.es wrote:

···

To: <sip:petermoreno@ekiga.net>
To: <sip:petermoreno@ekiga.net>
-----Mensaje original-----
De: Emil Ivov [mailto:emil@sip-communicator.org] En nombre de Emil Ivov
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] I cant send video on Ubuntu version (maybe

Hi,

Sorry, but I didn't mean I runned two instances of SIPComm at the same
time. I tried the application twice separately. The first time I got the
error running the SIPcommunicator through eclipse, and then I close the
application and got the same problem running the application as an
installed application.

So, I mean I didnt run the two ways at the same time, I runned each way
separately.

But I would like to emphasize that I can see image in the preview
framework from my camera, but I cant see any image when I establish a
call. So, I think that the v4l2 drivers are installed, but I'm not sure.

Please again, any help?

Thanks a lot

Pedro

Hi,

you mean you are running two instances of sip-communicator on one PC ?
If this is the case you have to know that only on app can access the
camera device.

Cheers
damencho

Pedro Moreno wrote:

Hello Emil,

Thanks for your answer. First of all, I've to say I'm newbie on Ubuntu
and I
don't know how to know if the v4l2 are installed.

I think that the driver is installed because on SIPCommunicator if I go
to
media in option menu
I can see my camera is working on preview framework. But when I
establish a
call I get the message I wrote. Is the video in preview media option
related
to the driver v4l2?

I've to say I get this problem with the SIPCommunicator installed on my
PC
and running the SIPCommunicator as a project through Eclipse. I suppose
that
the problem come from my camera..

Please can you help me? I'd appreciate a lot.

Thanks in advance

Pedro

-----Mensaje original-----
De: Emil Ivov [mailto:emil@sip-communicator.org] En nombre de Emil Ivov
Enviado el: viernes, 24 de julio de 2009 15:52
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] I cant send video on Ubuntu version (maybe
problem with h.264)

Hello Pedro,

We place the recvonly attribute when we can't transmit in a particular
media type. The most common reason for this is a missing device, so in
your case this is probably due to a problem with your webcam.

LTI-CIVIL only support v4l2 so make sure that you have v4l2 drivers
installed and working for your device.

Good luck!
Emil

pmoreno@gbt.tfo.upm.es wrote:

Hello,

I'm working with SIPCommunicator on Ubuntu version. When I try to
establish a call with another user I can see his video but my video
isn't
transmmited. I've been wondering why and I think that the reason is the
H.264 codec, because I get this session description of invite request
(catch with wireshark):

Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): pmoreno 0 0 IN IP4 138.4.10.142
Connection Information (c): IN IP4 138.4.10.142
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 5000 RTP/AVP 0 8 97 3 5
4
Media Attribute (a): rtpmap:4 G723/8000
Media Attribute (a): fmtp:4 annexa=no;bitrate=6.3
Media Description, name and address (m): video 5002 RTP/AVP 99 34 26 31
Media Attribute (a): rtpmap:99 H264/90000
Media Attribute (a): fmtp:99 packetization-mode=1
Media Attribute (a): recvonly

Why "recvonly"?? It should be "sendrecv", isn't it?

I've missed any specific packet on ubuntu, which is not neccesary on

WinXP?

Can anybody help me? I've very stuck with this problem

Thanks a lot in advance

Pedro

---------------------------------------------------------------------
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

--
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

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4284 (20090728) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4285 (20090728) __________

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

Yes, I think that's what I gathered which is why I asked you to log an
issue on our tracker.

Now that I am looking at your logs however I am seeing something else:
SIP Communicator starts with video turned off by default and only
enables it upon user request. In order to start video streaming, a user
is supposed to click on the webcam (rightmost gray) button. Are you
actually clicking on it?

Cheers
Emil

Pedro Moreno wrote:

···

Hi Emil,

I've tried to establish a call for getting the message I wrote in my first
message from the log file.

As a summary, when SIPCommunicator start It recognize the camera devices,
but when you try to establish a call SIPComm doesn't recognize any devices
(), only sound devices. As it's shown below I've put pieces of the log file
related to the init of SIPCommunicator, when it recognizes the devices, and
then when I send a Invite response:

14:21:46.809 INFO: impl.media.device.JavaSoundAuto.<init>().43 JavaSound
Capture Supported = true
14:21:46.852 INFO: impl.protocol.ssh.SSHActivator.start().79 SSH protocol
implementation [STARTED].
14:21:46.854 LA MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.start().42 [entry] start
14:21:46.857 INFO: impl.netaddr.NetworkAddressManagerServiceImpl.start().141
Stun server address(null)/port(null) not set (or invalid). Disabling STUN.
14:21:46.857 INFO: impl.netaddr.NetworkAddressManagerServiceImpl.start().59
Network Address Manager ...[ STARTED ]
14:21:46.857 INFO: impl.netaddr.NetworkAddressManagerServiceImpl.start().64
Network Address Manager Service ...[REGISTERED]
14:21:46.858 LA MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.start().68 [exit] start
14:21:46.941 INFO: impl.protocol.zeroconf.ZeroconfActivator.start().74
Zeroconf protocol implementation [STARTED].
14:21:46.944 INFO: impl.media.device.JavaSoundAuto.<init>().69
JavaSoundAuto: Committed ok
14:21:47.005 INFO: impl.protocol.irc.IrcActivator.start().69 IRC protocol
implementation [STARTED].
14:21:47.050 FINA:
impl.media.device.JmfDeviceDetector.detectCaptureDevices().164 No FMJ
javasound detected: net.sf.fmj.media.cdp.javasound.CaptureDevicePlugger
14:21:47.050 INFO:
impl.media.device.JmfDeviceDetector.detectCaptureDevices().176 Looking for
video capture devices
14:21:47.052 INFO: impl.protocol.dict.DictActivator.start().66 DICT protocol
implementation [STARTED].
14:21:47.095 FINA: impl.contactlist.ContactlistActivator.start().40 Service
Impl: net.java.sip.communicator.impl.contactlist.ContactlistActivator [
STARTED ]
14:21:47.100 MÁS FINA: impl.protocol.sip.SipStackSharing.<init>().92 Created
stack: gov.nist.javax.sip.SipStackImpl@e4d0cd
14:21:47.111 FINA: fmj.addCaptureDevices() CaptureDevicePlugger: Added
civil:/dev/video0
14:21:47.112 FINA: fmj.addCaptureDevices() CaptureDevicePlugger: Added
civil:/dev/video1
14:21:47.112 LA MÁS FINA: impl.media.device.JmfDeviceDetector.setupJMF().394
[exit] setupJMF
14:21:47.112 INFO:
impl.media.device.DeviceConfiguration.extractConfiguredCaptureDevices().106
Scanning for configured Audio Devices.
14:21:47.113 FINA:
impl.media.device.DeviceConfiguration.extractConfiguredCaptureDevices().118
Found 1 capture devices: [Ljavax.media.CaptureDeviceInfo;@869470
14:21:47.113 INFO:
impl.media.device.DeviceConfiguration.extractConfiguredCaptureDevices().137
Found JavaSound audio capture as an audio capture device.
14:21:47.113 INFO:
impl.media.device.DeviceConfiguration.extractConfiguredCaptureDevices().145
Scanning for configured Video Devices.
14:21:47.113 INFO:
impl.media.device.DeviceConfiguration.extractConfiguredVideoCaptureDevice().
186 Found civil:/dev/video0:0 as an RGB Video Device.
14:21:47.114 MÁS FINA:
impl.protocol.sip.ProtocolProviderServiceSipImpl.resolveSipAddress().2146
Returned SRV null
14:21:47.114 FINA:
impl.media.codec.EncodingConfiguration.registerCustomPackages().398 Adding
package : net.java.sip.communicator.impl
14:21:47.114 FINA:
impl.media.codec.EncodingConfiguration.registerCustomPackages().398 Adding
package : net.sf.fmj
14:21:47.134 FINA:
impl.media.codec.EncodingConfiguration.registerCustomPackages().404
Registering new protocol prefix list : [javax, com.sun, com.ibm,
net.java.sip.communicator.impl, net.sf.fmj]
14:21:47.134 INFO: impl.media.MediaControl.createDataSource().582 Creating
datasource for:javasound://44100
14:21:47.136 FINA: impl.contactlist.MetaContactListServiceImpl.start().146
Starting the meta contact list implementation.
14:21:47.137 LA MÁS FINA:
impl.fileaccess.FileAccessServiceImpl.getPrivatePersistentFile().112 [entry]
getPrivatePersistentFile
14:21:47.137 LA MÁS FINA:
impl.fileaccess.FileAccessServiceImpl.accessibleFile().319 [entry]
accessibleFile
14:21:47.137 LA MÁS FINA:
impl.fileaccess.FileAccessServiceImpl.accessibleFile().354 [exit]
accessibleFile
14:21:47.137 LA MÁS FINA:
impl.fileaccess.FileAccessServiceImpl.getPrivatePersistentFile().126 [exit]
getPrivatePersistentFile
14:21:47.167 FINA: impl.contactlist.ContactlistActivator.start().50 Service
Impl: net.java.sip.communicator.impl.contactlist.ContactlistActivator
[REGISTERED]
14:21:47.218 MÁS FINA:
impl.contactlist.MetaContactListServiceImpl.serviceChanged().1925 Received a
service event for:
net.java.sip.communicator.impl.protocol.rss.ProtocolProviderFactoryRssImpl
14:21:47.219 INFO: impl.protocol.rss.RssActivator.start().93 RSS protocol
implementation [STARTED].

And the part related to invite response:

14:22:45.737 FINA: service.protocol.Call.fireCallParticipantEvent().189
Dispatching a CallParticipant event to 0 listeners. event is:
CallParticipantEvent: ID=1 source participant=sip:petermoreno@ekiga.net
<sip:petermoreno@ekiga.net>;status=Unknown source call=Call:
id=124878376573032258780 participants=1
14:22:45.739 FINA:
service.protocol.AbstractCallParticipant.fireCallParticipantChangeEvent().19
1 Dispatching a CallParticipantChangeEvent event to 1 listeners. event is:
CallParticipantChangeEvent: type=CallParticipantStatusChange
oldV=net.java.sip.communicator.service.protocol.CallParticipantState:Unknown
newV=net.java.sip.communicator.service.protocol.CallParticipantState:Initiat
ing Call for participant=sip:petermoreno@ekiga.net
<sip:petermoreno@ekiga.net>;status=Initiating Call
14:22:45.741 FINA:
service.protocol.AbstractOperationSetBasicTelephony.fireCallEvent().65
Dispatching a CallEvent to 3 listeners. event is: CallEvent:[ id=1
Call=Call: id=124878376573032258780 participants=1]
14:22:45.907 FINA:
impl.media.CallSessionImpl.registerCustomCodecFormats().2479 registering
format ilbc/rtp, 8000.0 Hz, 16-bit, Mono, LittleEndian, Signed with RTP
manager
14:22:45.908 FINA:
impl.media.CallSessionImpl.registerCustomCodecFormats().2479 registering
format ALAW/rtp, 8000.0 Hz, 8-bit, Mono, Signed with RTP manager
14:22:45.908 FINA:
impl.media.CallSessionImpl.registerCustomCodecFormats().2479 registering
format speex/rtp, 8000.0 Hz, 8-bit, Mono, Signed with RTP manager
14:22:45.909 FINA:
impl.media.CallSessionImpl.registerCustomVideoCodecFormats().2504
registering format H264/RTP with RTP manager
14:22:45.911 MÁS FINA:
impl.protocol.sip.ProtocolProviderServiceSipImpl.resolveSipAddress().2146
Returned SRV null
14:22:45.941 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying a
localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.942 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will return
the following localhost address: /138.4.10.142
14:22:45.944 FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getPublicAddressFor().420 Stun
is disabled for destination ekiga.net/86.64.162.35, skipping mapped address
recovery (useStun=false, IPv6@=false).
14:22:45.945 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying a
localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.945 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will return
the following localhost address: /138.4.10.142
14:22:45.945 FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getPublicAddressFor().420 Stun
is disabled for destination ekiga.net/86.64.162.35, skipping mapped address
recovery (useStun=false, IPv6@=false).
14:22:45.946 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying a
localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.946 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will return
the following localhost address: /138.4.10.142
14:22:45.947 FINA: impl.media.CallSessionImpl.allocateMediaPorts().2215
AudioSessionAddress=DataAddress: /138.4.10.142
ControlAddress: /138.4.10.142
DataPort: 5000
ControlPort: 5001
14:22:45.948 FINA: impl.media.CallSessionImpl.allocateMediaPorts().2216
AudioPublicAddress=/138.4.10.142:5000
14:22:45.948 FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getPublicAddressFor().420 Stun
is disabled for destination ekiga.net/86.64.162.35, skipping mapped address
recovery (useStun=false, IPv6@=false).
14:22:45.948 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying a
localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.949 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will return
the following localhost address: /138.4.10.142
14:22:45.949 FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getPublicAddressFor().420 Stun
is disabled for destination ekiga.net/86.64.162.35, skipping mapped address
recovery (useStun=false, IPv6@=false).
14:22:45.950 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying a
localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.950 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will return
the following localhost address: /138.4.10.142
14:22:45.965 FINA: javax.media.rtp.rtcp.SourceDescription.generateCNAME()
this is the CNAME method.
14:22:45.966 FINA: javax.media.rtp.rtcp.SourceDescription.generateCNAME()
Returning cname=pmoreno@pmoreno-laptop
14:22:46.088 INFO:
impl.media.transform.zrtp.SecurityEventManager.showMessage().298
AUDIO_SESSION: ZRTP message: severity: Info, sub code: ZRTPNotEnabledByUser,
DH session: true, multi: 0
14:22:46.088 MÁS FINA:
impl.media.CallSessionImpl.initializeRtpManager().2347 RTP audio manager
initialized through connector
14:22:46.088 MÁS FINA:
impl.media.CallSessionImpl.initializeRtpManager().2444 set receiver buffer
len to=100
14:22:46.088 FINA: javax.media.rtp.rtcp.SourceDescription.generateCNAME()
this is the CNAME method.
14:22:46.089 FINA: javax.media.rtp.rtcp.SourceDescription.generateCNAME()
Returning cname=pmoreno@pmoreno-laptop
14:22:46.093 INFO:
impl.media.transform.zrtp.SecurityEventManager.showMessage().298
VIDEO_SESSION: ZRTP message: severity: Info, sub code: ZRTPNotEnabledByUser,
DH session: false, multi: 0
14:22:46.093 MÁS FINA:
impl.media.CallSessionImpl.initializeRtpManager().2347 RTPvideomanager
initialized through connector
14:22:46.093 MÁS FINA:
impl.media.CallSessionImpl.initializeRtpManager().2444 set receiver buffer
len to=100
14:22:46.095 FINA:
impl.media.CallSessionImpl.createSessionDescription().1678 Will create media
descs with: audio public address=/138.4.10.142:5000 and video public
address=/138.4.10.142:5002
14:22:46.095 FINA: impl.media.MediaControl.calculateSupportedEncodings().447
We will be able to transmit in:
14:22:46.119 FINA: impl.media.MediaControl.calculateSupportedEncodings().470
Audio=[1]=dvi/rtp; sdp=5
14:22:46.120 FINA: impl.media.MediaControl.calculateSupportedEncodings().470
Audio=[2]=ilbc/rtp; sdp=97
14:22:46.120 FINA: impl.media.MediaControl.calculateSupportedEncodings().470
Audio=[5]=g723/rtp; sdp=4
14:22:46.120 FINA: impl.media.MediaControl.calculateSupportedEncodings().470
Audio=[6]=gsm/rtp; sdp=3
14:22:46.120 FINA: impl.media.MediaControl.calculateSupportedEncodings().470
Audio=[7]=ULAW/rtp; sdp=0
14:22:46.120 FINA: impl.media.MediaControl.calculateSupportedEncodings().470
Audio=[8]=ALAW/rtp; sdp=8
14:22:46.121 FINA: impl.media.MediaControl.calculateSupportedEncodings().491
unknown encoding format mpegaudio/rtp
14:22:46.121 FINA: impl.media.MediaControl.calculateSupportedEncodings().491
unknown encoding format mpegaudio/rtp
14:22:46.121 FINA: impl.media.MediaControl.calculateSupportedEncodings().491
unknown encoding format mpegaudio/rtp
14:22:46.121 FINA: impl.media.MediaControl.calculateSupportedEncodings().491
unknown encoding format mpegaudio/rtp
14:22:46.121 FINA: impl.media.MediaControl.calculateSupportedEncodings().491
unknown encoding format mpegaudio/rtp
14:22:46.121 FINA: impl.media.MediaControl.calculateSupportedEncodings().491
unknown encoding format mpegaudio/rtp
14:22:46.121 FINA: impl.media.MediaControl.calculateSupportedEncodings().491
unknown encoding format mpegaudio/rtp
14:22:46.127 MÁS FINA:
impl.media.CallSessionImpl.createSessionDescription().1691 Generated SDP -
v=0
o=pmoreno 0 0 IN IP4 138.4.10.142
s=-
c=IN IP4 138.4.10.142
t=0 0
m=audio 5000 RTP/AVP 0 8 97 3 5 4
a=rtpmap:4 G723/8000
a=fmtp:4 annexa=no;bitrate=6.3
m=video 5002 RTP/AVP 99 34 26 31
a=rtpmap:99 H264/90000
a=fmtp:99 packetization-mode=1
a=recvonly

14:22:46.128 FINA:
impl.protocol.sip.OperationSetBasicTelephonySipImpl.createOutgoingCall().305
sent request:
INVITE sip:petermoreno@ekiga.net SIP/2.0
Call-ID: 051aab13308e297589f39103bc8fe37b@0:0:0:0:0:0:0:0
CSeq: 1 INVITE
From: <sip:pmoreno@ekiga.net>;tag=5e6a0ed6
To: <sip:petermoreno@ekiga.net>
Via: SIP/2.0/UDP
138.4.10.142:5060;branch=z9hG4bKcec6e84b0dad8b165271d418bc9eafca
Max-Forwards: 70
User-Agent: SIP Communicator1.0-alpha3-nightly.build.1952Linux
Contact: "pmoreno"
<sip:pmoreno@138.4.10.142:5060;transport=udp;registering_acc=ekiga_net>
Content-Type: application/sdp
Content-Length: 266

v=0
o=pmoreno 0 0 IN IP4 138.4.10.142
s=-
c=IN IP4 138.4.10.142
t=0 0
m=audio 5000 RTP/AVP 0 8 97 3 5 4
a=rtpmap:4 G723/8000
a=fmtp:4 annexa=no;bitrate=6.3
m=video 5002 RTP/AVP 99 34 26 31
a=rtpmap:99 H264/90000
a=fmtp:99 packetization-mode=1
a=recvonly

14:22:46.167 MÁS FINA:
impl.protocol.sip.SipStackSharing.processResponse().565 received response:
100 Giving a try
14:22:46.167 MÁS FINA:
impl.protocol.sip.SipStackSharing.getServiceData().847 service was found in
request data
14:22:46.167 FINA:
impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse().528
received response=
SIP/2.0 100 Giving a try
Call-ID: 051aab13308e297589f39103bc8fe37b@0:0:0:0:0:0:0:0
CSeq: 1 INVITE
From: <sip:pmoreno@ekiga.net>;tag=5e6a0ed6
To: <sip:petermoreno@ekiga.net>
Via: SIP/2.0/UDP
138.4.10.142:5060;branch=z9hG4bKcec6e84b0dad8b165271d418bc9eafca
Server: Kamailio (1.4.0-notls (i386/linux))
Content-Length: 0

I don’t know what is happening, even I've installed all packages related to
v4l2 drivers on Ubuntu.

Do I miss anything? Please help me, because I'm very stuck with this and I
need to solve this problem

Thanks a lot in advance

Regards

Pedro

-----Mensaje original-----
De: Emil Ivov [mailto:emil@sip-communicator.org] En nombre de Emil Ivov
Enviado el: martes, 28 de julio de 2009 2:48
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] I cant send video on Ubuntu version (maybe
problem with h.264)

Hey Pedro,

I believe I've also heard the same problem (preview is available but
nothing gets streamed) also mentioned by other people. Yet I don't
believe we have an entry for it in the tracker. Could you please create
one? Attaching logs and wireshark traces would also help.

Thanks!
Emil

pmoreno@gbt.tfo.upm.es wrote:

Hi,

Sorry, but I didn't mean I runned two instances of SIPComm at the same
time. I tried the application twice separately. The first time I got the
error running the SIPcommunicator through eclipse, and then I close the
application and got the same problem running the application as an
installed application.

So, I mean I didnt run the two ways at the same time, I runned each way
separately.

But I would like to emphasize that I can see image in the preview
framework from my camera, but I cant see any image when I establish a
call. So, I think that the v4l2 drivers are installed, but I'm not sure.

Please again, any help?

Thanks a lot

Pedro

Hi,

you mean you are running two instances of sip-communicator on one PC ?
If this is the case you have to know that only on app can access the
camera device.

Cheers
damencho

Pedro Moreno wrote:

Hello Emil,

Thanks for your answer. First of all, I've to say I'm newbie on Ubuntu
and I
don't know how to know if the v4l2 are installed.

I think that the driver is installed because on SIPCommunicator if I go
to
media in option menu
I can see my camera is working on preview framework. But when I
establish a
call I get the message I wrote. Is the video in preview media option
related
to the driver v4l2?

I've to say I get this problem with the SIPCommunicator installed on my
PC
and running the SIPCommunicator as a project through Eclipse. I suppose
that
the problem come from my camera..

Please can you help me? I'd appreciate a lot.

Thanks in advance

Pedro

-----Mensaje original-----
De: Emil Ivov [mailto:emil@sip-communicator.org] En nombre de Emil Ivov
Enviado el: viernes, 24 de julio de 2009 15:52
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] I cant send video on Ubuntu version (maybe
problem with h.264)

Hello Pedro,

We place the recvonly attribute when we can't transmit in a particular
media type. The most common reason for this is a missing device, so in
your case this is probably due to a problem with your webcam.

LTI-CIVIL only support v4l2 so make sure that you have v4l2 drivers
installed and working for your device.

Good luck!
Emil

pmoreno@gbt.tfo.upm.es wrote:

Hello,

I'm working with SIPCommunicator on Ubuntu version. When I try to
establish a call with another user I can see his video but my video
isn't
transmmited. I've been wondering why and I think that the reason is the
H.264 codec, because I get this session description of invite request
(catch with wireshark):

Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): pmoreno 0 0 IN IP4 138.4.10.142
Connection Information (c): IN IP4 138.4.10.142
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 5000 RTP/AVP 0 8 97 3 5
4
Media Attribute (a): rtpmap:4 G723/8000
Media Attribute (a): fmtp:4 annexa=no;bitrate=6.3
Media Description, name and address (m): video 5002 RTP/AVP 99 34 26 31
Media Attribute (a): rtpmap:99 H264/90000
Media Attribute (a): fmtp:99 packetization-mode=1
Media Attribute (a): recvonly

Why "recvonly"?? It should be "sendrecv", isn't it?

I've missed any specific packet on ubuntu, which is not neccesary on

WinXP?

Can anybody help me? I've very stuck with this problem

Thanks a lot in advance

Pedro

---------------------------------------------------------------------
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

--
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


#9

Hi, Emil

Thanks a lot for your answer, because I didn’t know that in last versions
initially SIPCommunicator disables the video, because I've been working with
a older version only one week ago and I decided to update the version.

I don’t know exactly what you mean when you ask me to log an issue on the
tracker. Should I open a new issue with my problem??
Could you make clear that point?

Best whishes

Pedro

Enviado el: martes, 28 de julio de 2009 16:29
problem with h.264)

Yes, I think that's what I gathered which is why I asked you to log an
issue on our tracker.

Now that I am looking at your logs however I am seeing something else:
SIP Communicator starts with video turned off by default and only
enables it upon user request. In order to start video streaming, a user
is supposed to click on the webcam (rightmost gray) button. Are you
actually clicking on it?

Cheers
Emil

Pedro Moreno wrote:

Hi Emil,

I've tried to establish a call for getting the message I wrote in my first
message from the log file.

As a summary, when SIPCommunicator start It recognize the camera devices,
but when you try to establish a call SIPComm doesn't recognize any devices
(), only sound devices. As it's shown below I've put pieces of the log

file

related to the init of SIPCommunicator, when it recognizes the devices,

and

then when I send a Invite response:

14:21:46.809 INFO: impl.media.device.JavaSoundAuto.<init>().43 JavaSound
Capture Supported = true
14:21:46.852 INFO: impl.protocol.ssh.SSHActivator.start().79 SSH protocol
implementation [STARTED].
14:21:46.854 LA MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.start().42 [entry] start
14:21:46.857 INFO:

impl.netaddr.NetworkAddressManagerServiceImpl.start().141

Stun server address(null)/port(null) not set (or invalid). Disabling STUN.
14:21:46.857 INFO:

impl.netaddr.NetworkAddressManagerServiceImpl.start().59

Network Address Manager ...[ STARTED ]
14:21:46.857 INFO:

impl.netaddr.NetworkAddressManagerServiceImpl.start().64

Network Address Manager Service ...[REGISTERED]
14:21:46.858 LA MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.start().68 [exit] start
14:21:46.941 INFO: impl.protocol.zeroconf.ZeroconfActivator.start().74
Zeroconf protocol implementation [STARTED].
14:21:46.944 INFO: impl.media.device.JavaSoundAuto.<init>().69
JavaSoundAuto: Committed ok
14:21:47.005 INFO: impl.protocol.irc.IrcActivator.start().69 IRC protocol
implementation [STARTED].
14:21:47.050 FINA:
impl.media.device.JmfDeviceDetector.detectCaptureDevices().164 No FMJ
javasound detected: net.sf.fmj.media.cdp.javasound.CaptureDevicePlugger
14:21:47.050 INFO:
impl.media.device.JmfDeviceDetector.detectCaptureDevices().176 Looking for
video capture devices
14:21:47.052 INFO: impl.protocol.dict.DictActivator.start().66 DICT

protocol

implementation [STARTED].
14:21:47.095 FINA: impl.contactlist.ContactlistActivator.start().40

Service

Impl: net.java.sip.communicator.impl.contactlist.ContactlistActivator [
STARTED ]
14:21:47.100 MÁS FINA: impl.protocol.sip.SipStackSharing.<init>().92

Created

stack: gov.nist.javax.sip.SipStackImpl@e4d0cd
14:21:47.111 FINA: fmj.addCaptureDevices() CaptureDevicePlugger: Added
civil:/dev/video0
14:21:47.112 FINA: fmj.addCaptureDevices() CaptureDevicePlugger: Added
civil:/dev/video1
14:21:47.112 LA MÁS FINA:

impl.media.device.JmfDeviceDetector.setupJMF().394

[exit] setupJMF
14:21:47.112 INFO:

impl.media.device.DeviceConfiguration.extractConfiguredCaptureDevices().106

Scanning for configured Audio Devices.
14:21:47.113 FINA:

impl.media.device.DeviceConfiguration.extractConfiguredCaptureDevices().118

Found 1 capture devices: [Ljavax.media.CaptureDeviceInfo;@869470
14:21:47.113 INFO:

impl.media.device.DeviceConfiguration.extractConfiguredCaptureDevices().137

Found JavaSound audio capture as an audio capture device.
14:21:47.113 INFO:

impl.media.device.DeviceConfiguration.extractConfiguredCaptureDevices().145

Scanning for configured Video Devices.
14:21:47.113 INFO:

impl.media.device.DeviceConfiguration.extractConfiguredVideoCaptureDevice().

186 Found civil:/dev/video0:0 as an RGB Video Device.
14:21:47.114 MÁS FINA:
impl.protocol.sip.ProtocolProviderServiceSipImpl.resolveSipAddress().2146
Returned SRV null
14:21:47.114 FINA:
impl.media.codec.EncodingConfiguration.registerCustomPackages().398 Adding
package : net.java.sip.communicator.impl
14:21:47.114 FINA:
impl.media.codec.EncodingConfiguration.registerCustomPackages().398 Adding
package : net.sf.fmj
14:21:47.134 FINA:
impl.media.codec.EncodingConfiguration.registerCustomPackages().404
Registering new protocol prefix list : [javax, com.sun, com.ibm,
net.java.sip.communicator.impl, net.sf.fmj]
14:21:47.134 INFO: impl.media.MediaControl.createDataSource().582 Creating
datasource for:javasound://44100
14:21:47.136 FINA: impl.contactlist.MetaContactListServiceImpl.start().146
Starting the meta contact list implementation.
14:21:47.137 LA MÁS FINA:
impl.fileaccess.FileAccessServiceImpl.getPrivatePersistentFile().112

[entry]

getPrivatePersistentFile
14:21:47.137 LA MÁS FINA:
impl.fileaccess.FileAccessServiceImpl.accessibleFile().319 [entry]
accessibleFile
14:21:47.137 LA MÁS FINA:
impl.fileaccess.FileAccessServiceImpl.accessibleFile().354 [exit]
accessibleFile
14:21:47.137 LA MÁS FINA:
impl.fileaccess.FileAccessServiceImpl.getPrivatePersistentFile().126

[exit]

getPrivatePersistentFile
14:21:47.167 FINA: impl.contactlist.ContactlistActivator.start().50

Service

Impl: net.java.sip.communicator.impl.contactlist.ContactlistActivator
[REGISTERED]
14:21:47.218 MÁS FINA:
impl.contactlist.MetaContactListServiceImpl.serviceChanged().1925 Received

a

service event for:
net.java.sip.communicator.impl.protocol.rss.ProtocolProviderFactoryRssImpl
14:21:47.219 INFO: impl.protocol.rss.RssActivator.start().93 RSS protocol
implementation [STARTED].

And the part related to invite response:

14:22:45.737 FINA: service.protocol.Call.fireCallParticipantEvent().189
Dispatching a CallParticipant event to 0 listeners. event is:
CallParticipantEvent: ID=1 source participant=sip:petermoreno@ekiga.net
<sip:petermoreno@ekiga.net>;status=Unknown source call=Call:
id=124878376573032258780 participants=1
14:22:45.739 FINA:

service.protocol.AbstractCallParticipant.fireCallParticipantChangeEvent().19

1 Dispatching a CallParticipantChangeEvent event to 1 listeners. event is:
CallParticipantChangeEvent: type=CallParticipantStatusChange

oldV=net.java.sip.communicator.service.protocol.CallParticipantState:Unknown

newV=net.java.sip.communicator.service.protocol.CallParticipantState:Initiat

ing Call for participant=sip:petermoreno@ekiga.net
<sip:petermoreno@ekiga.net>;status=Initiating Call
14:22:45.741 FINA:
service.protocol.AbstractOperationSetBasicTelephony.fireCallEvent().65
Dispatching a CallEvent to 3 listeners. event is: CallEvent:[ id=1
Call=Call: id=124878376573032258780 participants=1]
14:22:45.907 FINA:
impl.media.CallSessionImpl.registerCustomCodecFormats().2479 registering
format ilbc/rtp, 8000.0 Hz, 16-bit, Mono, LittleEndian, Signed with RTP
manager
14:22:45.908 FINA:
impl.media.CallSessionImpl.registerCustomCodecFormats().2479 registering
format ALAW/rtp, 8000.0 Hz, 8-bit, Mono, Signed with RTP manager
14:22:45.908 FINA:
impl.media.CallSessionImpl.registerCustomCodecFormats().2479 registering
format speex/rtp, 8000.0 Hz, 8-bit, Mono, Signed with RTP manager
14:22:45.909 FINA:
impl.media.CallSessionImpl.registerCustomVideoCodecFormats().2504
registering format H264/RTP with RTP manager
14:22:45.911 MÁS FINA:
impl.protocol.sip.ProtocolProviderServiceSipImpl.resolveSipAddress().2146
Returned SRV null
14:22:45.941 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying

a

localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.942 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will

return

the following localhost address: /138.4.10.142
14:22:45.944 FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getPublicAddressFor().420

Stun

is disabled for destination ekiga.net/86.64.162.35, skipping mapped

address

recovery (useStun=false, IPv6@=false).
14:22:45.945 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying

a

localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.945 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will

return

the following localhost address: /138.4.10.142
14:22:45.945 FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getPublicAddressFor().420

Stun

is disabled for destination ekiga.net/86.64.162.35, skipping mapped

address

recovery (useStun=false, IPv6@=false).
14:22:45.946 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying

a

localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.946 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will

return

the following localhost address: /138.4.10.142
14:22:45.947 FINA: impl.media.CallSessionImpl.allocateMediaPorts().2215
AudioSessionAddress=DataAddress: /138.4.10.142
ControlAddress: /138.4.10.142
DataPort: 5000
ControlPort: 5001
14:22:45.948 FINA: impl.media.CallSessionImpl.allocateMediaPorts().2216
AudioPublicAddress=/138.4.10.142:5000
14:22:45.948 FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getPublicAddressFor().420

Stun

is disabled for destination ekiga.net/86.64.162.35, skipping mapped

address

recovery (useStun=false, IPv6@=false).
14:22:45.948 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying

a

localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.949 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will

return

the following localhost address: /138.4.10.142
14:22:45.949 FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getPublicAddressFor().420

Stun

is disabled for destination ekiga.net/86.64.162.35, skipping mapped

address

recovery (useStun=false, IPv6@=false).
14:22:45.950 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().234 Querying

a

localhost addr for dst=ekiga.net/86.64.162.35
14:22:45.950 MÁS FINA:
impl.netaddr.NetworkAddressManagerServiceImpl.getLocalHost().338 Will

return

the following localhost address: /138.4.10.142
14:22:45.965 FINA: javax.media.rtp.rtcp.SourceDescription.generateCNAME()
this is the CNAME method.
14:22:45.966 FINA: javax.media.rtp.rtcp.SourceDescription.generateCNAME()
Returning cname=pmoreno@pmoreno-laptop
14:22:46.088 INFO:
impl.media.transform.zrtp.SecurityEventManager.showMessage().298
AUDIO_SESSION: ZRTP message: severity: Info, sub code:

ZRTPNotEnabledByUser,

DH session: true, multi: 0
14:22:46.088 MÁS FINA:
impl.media.CallSessionImpl.initializeRtpManager().2347 RTP audio manager
initialized through connector
14:22:46.088 MÁS FINA:
impl.media.CallSessionImpl.initializeRtpManager().2444 set receiver buffer
len to=100
14:22:46.088 FINA: javax.media.rtp.rtcp.SourceDescription.generateCNAME()
this is the CNAME method.
14:22:46.089 FINA: javax.media.rtp.rtcp.SourceDescription.generateCNAME()
Returning cname=pmoreno@pmoreno-laptop
14:22:46.093 INFO:
impl.media.transform.zrtp.SecurityEventManager.showMessage().298
VIDEO_SESSION: ZRTP message: severity: Info, sub code:

ZRTPNotEnabledByUser,

DH session: false, multi: 0
14:22:46.093 MÁS FINA:
impl.media.CallSessionImpl.initializeRtpManager().2347 RTPvideomanager
initialized through connector
14:22:46.093 MÁS FINA:
impl.media.CallSessionImpl.initializeRtpManager().2444 set receiver buffer
len to=100
14:22:46.095 FINA:
impl.media.CallSessionImpl.createSessionDescription().1678 Will create

media

descs with: audio public address=/138.4.10.142:5000 and video public
address=/138.4.10.142:5002
14:22:46.095 FINA:

impl.media.MediaControl.calculateSupportedEncodings().447

We will be able to transmit in:
14:22:46.119 FINA:

impl.media.MediaControl.calculateSupportedEncodings().470

Audio=[1]=dvi/rtp; sdp=5
14:22:46.120 FINA:

impl.media.MediaControl.calculateSupportedEncodings().470

Audio=[2]=ilbc/rtp; sdp=97
14:22:46.120 FINA:

impl.media.MediaControl.calculateSupportedEncodings().470

Audio=[5]=g723/rtp; sdp=4
14:22:46.120 FINA:

impl.media.MediaControl.calculateSupportedEncodings().470

Audio=[6]=gsm/rtp; sdp=3
14:22:46.120 FINA:

impl.media.MediaControl.calculateSupportedEncodings().470

Audio=[7]=ULAW/rtp; sdp=0
14:22:46.120 FINA:

impl.media.MediaControl.calculateSupportedEncodings().470

Audio=[8]=ALAW/rtp; sdp=8
14:22:46.121 FINA:

impl.media.MediaControl.calculateSupportedEncodings().491

unknown encoding format mpegaudio/rtp
14:22:46.121 FINA:

impl.media.MediaControl.calculateSupportedEncodings().491

unknown encoding format mpegaudio/rtp
14:22:46.121 FINA:

impl.media.MediaControl.calculateSupportedEncodings().491

unknown encoding format mpegaudio/rtp
14:22:46.121 FINA:

impl.media.MediaControl.calculateSupportedEncodings().491

unknown encoding format mpegaudio/rtp
14:22:46.121 FINA:

impl.media.MediaControl.calculateSupportedEncodings().491

unknown encoding format mpegaudio/rtp
14:22:46.121 FINA:

impl.media.MediaControl.calculateSupportedEncodings().491

unknown encoding format mpegaudio/rtp
14:22:46.121 FINA:

impl.media.MediaControl.calculateSupportedEncodings().491

unknown encoding format mpegaudio/rtp
14:22:46.127 MÁS FINA:
impl.media.CallSessionImpl.createSessionDescription().1691 Generated SDP -
v=0
o=pmoreno 0 0 IN IP4 138.4.10.142
s=-
c=IN IP4 138.4.10.142
t=0 0
m=audio 5000 RTP/AVP 0 8 97 3 5 4
a=rtpmap:4 G723/8000
a=fmtp:4 annexa=no;bitrate=6.3
m=video 5002 RTP/AVP 99 34 26 31
a=rtpmap:99 H264/90000
a=fmtp:99 packetization-mode=1
a=recvonly

14:22:46.128 FINA:

impl.protocol.sip.OperationSetBasicTelephonySipImpl.createOutgoingCall().305

sent request:
INVITE sip:petermoreno@ekiga.net SIP/2.0
Call-ID: 051aab13308e297589f39103bc8fe37b@0:0:0:0:0:0:0:0
CSeq: 1 INVITE
From: <sip:pmoreno@ekiga.net>;tag=5e6a0ed6
To: <sip:petermoreno@ekiga.net>
Via: SIP/2.0/UDP
138.4.10.142:5060;branch=z9hG4bKcec6e84b0dad8b165271d418bc9eafca
Max-Forwards: 70
User-Agent: SIP Communicator1.0-alpha3-nightly.build.1952Linux
Contact: "pmoreno"
<sip:pmoreno@138.4.10.142:5060;transport=udp;registering_acc=ekiga_net>
Content-Type: application/sdp
Content-Length: 266

v=0
o=pmoreno 0 0 IN IP4 138.4.10.142
s=-
c=IN IP4 138.4.10.142
t=0 0
m=audio 5000 RTP/AVP 0 8 97 3 5 4
a=rtpmap:4 G723/8000
a=fmtp:4 annexa=no;bitrate=6.3
m=video 5002 RTP/AVP 99 34 26 31
a=rtpmap:99 H264/90000
a=fmtp:99 packetization-mode=1
a=recvonly

14:22:46.167 MÁS FINA:
impl.protocol.sip.SipStackSharing.processResponse().565 received response:
100 Giving a try
14:22:46.167 MÁS FINA:
impl.protocol.sip.SipStackSharing.getServiceData().847 service was found

in

request data
14:22:46.167 FINA:
impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse().528
received response=
SIP/2.0 100 Giving a try
Call-ID: 051aab13308e297589f39103bc8fe37b@0:0:0:0:0:0:0:0
CSeq: 1 INVITE
From: <sip:pmoreno@ekiga.net>;tag=5e6a0ed6
To: <sip:petermoreno@ekiga.net>
Via: SIP/2.0/UDP
138.4.10.142:5060;branch=z9hG4bKcec6e84b0dad8b165271d418bc9eafca
Server: Kamailio (1.4.0-notls (i386/linux))
Content-Length: 0

I don’t know what is happening, even I've installed all packages related

to

v4l2 drivers on Ubuntu.

Do I miss anything? Please help me, because I'm very stuck with this and I
need to solve this problem

Thanks a lot in advance

Regards

Pedro

De: Emil Ivov [mailto:emil@sip-communicator.org] En nombre de Emil Ivov
Enviado el: martes, 28 de julio de 2009 2:48
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] I cant send video on Ubuntu version (maybe
problem with h.264)

Hey Pedro,

I believe I've also heard the same problem (preview is available but
nothing gets streamed) also mentioned by other people. Yet I don't
believe we have an entry for it in the tracker. Could you please create
one? Attaching logs and wireshark traces would also help.

Thanks!
Emil

Hi,

Sorry, but I didn't mean I runned two instances of SIPComm at the same
time. I tried the application twice separately. The first time I got the
error running the SIPcommunicator through eclipse, and then I close the
application and got the same problem running the application as an
installed application.

So, I mean I didnt run the two ways at the same time, I runned each way
separately.

But I would like to emphasize that I can see image in the preview
framework from my camera, but I cant see any image when I establish a
call. So, I think that the v4l2 drivers are installed, but I'm not sure.

Please again, any help?

Thanks a lot

Pedro

Hi,

you mean you are running two instances of sip-communicator on one PC ?
If this is the case you have to know that only on app can access the
camera device.

Cheers
damencho

Pedro Moreno wrote:

Hello Emil,

Thanks for your answer. First of all, I've to say I'm newbie on Ubuntu
and I
don't know how to know if the v4l2 are installed.

I think that the driver is installed because on SIPCommunicator if I go
to
media in option menu
I can see my camera is working on preview framework. But when I
establish a
call I get the message I wrote. Is the video in preview media option
related
to the driver v4l2?

I've to say I get this problem with the SIPCommunicator installed on my
PC
and running the SIPCommunicator as a project through Eclipse. I suppose
that
the problem come from my camera..

Please can you help me? I'd appreciate a lot.

Thanks in advance

Pedro

De: Emil Ivov [mailto:emil@sip-communicator.org] En nombre de Emil Ivov
Enviado el: viernes, 24 de julio de 2009 15:52
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] I cant send video on Ubuntu version (maybe
problem with h.264)

Hello Pedro,

We place the recvonly attribute when we can't transmit in a particular
media type. The most common reason for this is a missing device, so in
your case this is probably due to a problem with your webcam.

LTI-CIVIL only support v4l2 so make sure that you have v4l2 drivers
installed and working for your device.

Good luck!
Emil

Hello,

I'm working with SIPCommunicator on Ubuntu version. When I try to
establish a call with another user I can see his video but my video
isn't
transmmited. I've been wondering why and I think that the reason is

the

H.264 codec, because I get this session description of invite request
(catch with wireshark):

Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): pmoreno 0 0 IN IP4 138.4.10.142
Connection Information (c): IN IP4 138.4.10.142
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 5000 RTP/AVP 0 8 97 3 5
4
Media Attribute (a): rtpmap:4 G723/8000
Media Attribute (a): fmtp:4 annexa=no;bitrate=6.3
Media Description, name and address (m): video 5002 RTP/AVP 99 34 26

31

Media Attribute (a): rtpmap:99 H264/90000
Media Attribute (a): fmtp:99 packetization-mode=1
Media Attribute (a): recvonly

Why "recvonly"?? It should be "sendrecv", isn't it?

I've missed any specific packet on ubuntu, which is not neccesary on

WinXP?

Can anybody help me? I've very stuck with this problem

Thanks a lot in advance

Pedro

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

dev-help@sip-communicator.dev.java.net

···

-----Mensaje original-----
De: Emil Ivov [mailto:emil@sip-communicator.org] En nombre de Emil Ivov
Para: dev@sip-communicator.dev.java.net
Asunto: Re: [sip-comm-dev] I cant send video on Ubuntu version (maybe

-----Mensaje original-----
pmoreno@gbt.tfo.upm.es wrote:

-----Mensaje original-----
pmoreno@gbt.tfo.upm.es wrote:

---------------------------------------------------------------------
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

--
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

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4285 (20090728) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4285 (20090728) __________

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

Hey Pedro,

Pedro Moreno wrote:

I don’t know exactly what you mean when you ask me to log an issue on the
tracker.

You may want to have a look here then:
http://www.sip-communicator.org/index.php/Development/BugsAndIssues

Should I open a new issue with my problem??

Yes, provided you still don't get video _after_ clicking the camera
button on the call dialog.

Cheers
Emil

···

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