Support for video call

[GoogleCodeExporter]

Hi all,
First of all I would like to say that yo have done a great job!
I'm developing an IMS/LTE (4G) client for Android 
(http://code.google.com/p/imsdroid/) and looking for client which support video 
call (H264 or Theora). I have tried SipDroid but it cannot receive video and 
only support H263+.
Do you plan to support video call in the coming releases?

Original issue reported on code.google.com by boss...@yahoo.fr on 27 Jul 2010 at 3:18

[GoogleCodeExporter]

Yes it's planned but in a *far* future.

The main technical problem is that as I use a native stack that doesn't support 
video yet. So it has to be modified to support video and connected to the 
android video system. 
So not so easy to do, and many things are remaining to support only voice and 
provide a good user experience.

But maybe if somebody hears you and want to start something on that point ... 
he would be welcome ... it's an opensource project ;) .

Original comment by r3gis...@gmail.com on 27 Jul 2010 at 3:27

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Thanks for the quick response.
I'll stay tuned.

Original comment by boss...@yahoo.fr on 27 Jul 2010 at 3:51

[GoogleCodeExporter]

Issue 173 has been merged into this issue.

Original comment by r3gis...@gmail.com on 27 Aug 2010 at 6:03

[GoogleCodeExporter]

Quick update

Excellent news.... pjsip (the sip stack on which CSipSimple rely) support video 
media.

Now work for me... do a driver between android and pjsip :D

Too much things to do, but this is an exciting feature so I'll try to do that 
AZAP :)

Original comment by r3gis...@gmail.com on 10 Dec 2010 at 2:56

• Changed state: Accepted

[GoogleCodeExporter]

Hi,

Provide me the steps for setting up CsipSimple for video call

Thanks in Advance

Original comment by sahadeva...@gmail.com on 14 Feb 2011 at 9:22

[GoogleCodeExporter]

As explained several time above CSipSimple does not support video yet.

There is a current effort on this task. If you want to join the development 
effort you'll be welcome !

Original comment by r3gis...@gmail.com on 14 Feb 2011 at 9:39

• Changed state: Started

[GoogleCodeExporter]

I am looking into this as well; the only thing I see as the "show" stopper is 
only h.263 encoding support; Does anyone know if there is a h.264 encoder?

I am not an expert at video but I did spend some time looking into the 
possibility;

The 2 problems I see are;

1. Video Support in the SIP stack;  (Solved)
2. Video Encoding (Solved if you want h.263)

I would be curious to see what other "projects/companies" are doing about this.

(Please update me if I am completely wrong about my assumptions;)

Thanks.

Original comment by da...@styleflare.com on 21 Feb 2011 at 6:23

[GoogleCodeExporter]

> Video Support in the SIP stack;  << actually not fully yet...

In fact what is released by pjsip guys is for now only the pjmedia part. So no 
SDP nor higher level integration.

The pjmedia encoding part relies on ffmpeg. As consequence even if for now few 
encoders are integrated, would not be so hard to get more.

The biggest thing we are waiting for now is for the release of teluu for the 
integration with the rest of the stack.

The thing I'm trying to treat on my side and that is far to be an minor thing 
to do is the device glue to get and write in the android UI.

I know that there is somebody that is trying to hardcode some stuff inside the 
current pjsua to get some proof of concept. They'll commit as soon as they'll 
get something. But the driver for android has to be done before...

Original comment by r3gis...@gmail.com on 21 Feb 2011 at 6:41

[GoogleCodeExporter]

I've never used pjsip but I can help adding video support by:
- Building and adding FFMpeg
- Developing these video codecs: h263,h264,theora and mp4-es
- Writing the java glue & UI (jni,surfaceview,camera management,...)
What should I do to contribute to the project?

Original comment by boss...@yahoo.fr on 6 Mar 2011 at 10:31

[GoogleCodeExporter]

You're welcome :)

As for building and adding ffmpeg that's already done and available in the 
video branch of csipsimple.
As for the codecs if I don't mistake we will automatically benefit it from 
ffmpeg, isn't it?

For the java glue, if you want to try to do it, it will be very welcome.
To do so, try to checkout the video branch :
http://code.google.com/p/csipsimple/source/browse/#svn%2Fbranches%2Fvideo
What is missing is something there :
http://code.google.com/p/csipsimple/source/browse/#svn%2Fbranches%2Fvideo%2Fpjsi
p_android-2.0%2Fapps%2Fpjsip%2Fproject%2Fpjmedia%2Fsrc%2Fpjmedia-videodev
to make the glue with openGL (I guess that's the best choice to render video) 
and one with the android java API for cameras.

For now, pjsip guys has not yet finished everything that is missing between the 
pjsua (user agent) and their pjmedia library. However that's planned to be 
released soon as far as I understood :).

Meanwhile it should be possible to test the video dev using their unitary tests 
(for example the aviplayer.c project). 

If you have a first patch for the video branch let me know I'll open you the 
svn write access to contribute ;)

Original comment by r3gis...@gmail.com on 6 Mar 2011 at 10:55

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

FFmpeg will give encoding/ decoding(avcodec), chroma 
conversion,scaling...(swscale) but it will be up to you to develop the rtp 
packetization/depacketization(rfc3984,draft-barbato-avt-rtp-theora-01,rfc4629,..
.) unless you have it in avformat or pjsip.
OpenGL-es is a good idea but it's too heavy for a voip application where we 
only want to display the video stream "as-is". Using android "surfaceview" is 
easier even if it gives better performance (see main loop threading issue). The 
real benefit of opengl-es 2.0 could be the fact that you can draw yuv420 frames 
without converting them to rgb565 (to be checked). As you know the chroma 
conversion is one blocking point on some armv5te devices (at least 90% of the 
market). swscale doesn't really provide amrv5 optimized code for chroma 
conversion.

Original comment by boss...@yahoo.fr on 8 Mar 2011 at 8:34

[GoogleCodeExporter]

As for RTP packetization, I think (but I'm absolutely not sure ;) ) that it is 
already provided by pjsip or will be ;) (anyway pjsip is the good place to put 
it and already provides some utilities functions for rtp packetization).

For OpenGL-ES vs surfaceview you have probably better knowledge than me on this 
field. 
I was thinking about OpenGL-ES cause that's a "standard" and could be reused on 
other platforms than android. 
Besides with the very bad experience I had with the audio java API (1 month of 
dev and still not working on all devices) and the excellent experience I had 
with OpenSL-ES (1 day of dev), I was thinking that OpenGL-ES could be easier 
but it was just a guess.
I was also thinking about all stuff that could be done through the GPU for 
image optimization (contrast/balance/effects/scaling). And maybe other stuff on 
hardware acceleration I'm not aware of.

Could be interesting to test both :). But, if you think it's easier to start 
with surfaceview I entirely trust you, as I never really tried nor opengl-es 
neither surfaceview :).

Original comment by r3gis...@gmail.com on 8 Mar 2011 at 9:53

[GoogleCodeExporter]

so pjsip 2.0 with video support soon?

Original comment by ferna...@bugabundo.net on 22 Mar 2011 at 4:02

[GoogleCodeExporter]

:)... http://twitter.com/#!/CSipSimple

And in csipsimple video branch there is the dev for the display (using opengl 
-- if boss has an implementation with surface view it will be welcome to bench 
both implementation).

As for capturing I started something too. For now I have preview. next step 
will be to push frames to native stack. 

There is also something to do about converting frames from different color 
space. ffmpeg lib should be helpful, but I'd like to use the pjsip wrapper 
around ffmpeg libswscale.

I was not very reactive on the issue list all this week end and probably all 
the rest of the week cause of that point... :) Obviously I can't do support + 
dev at the same time ;) . So for now it's more dev than support. To the others 
that ask for help sorry if I'm not responsive but video is a very exciting 
feature to implement ;).

Original comment by r3gis...@gmail.com on 22 Mar 2011 at 4:42

[GoogleCodeExporter]

Make audio bulletproof, then code video.
Not that many front facing camera devices, and even less using it with sip

Original comment by ferna...@bugabundo.net on 22 Mar 2011 at 4:51

[GoogleCodeExporter]

Remember, I do csipsimple for my pleasure ;). 
So if *I* don't do video it does not mean I'll do more stuff on audio.
It just mean that I spend time playing with some other stuff.

Other stuff can be video on csipsimple, but could have been completely 
different project on android or another project on something different than 
android. I also do some html5/css3/svg projects ;).

My personal roadmap are only based on what I want to do on my free time ;). If 
some company or user want to have a feature on one device... JUST CODE IT !!! 
CSipSimple is opensource !!!

Original comment by r3gis...@gmail.com on 22 Mar 2011 at 5:21

[GoogleCodeExporter]

First video call done with csipsimple ;).

It was done between csipsimple on nexus one and my pc (ubuntu) running pjsip.
For now pjsip-2.0 only support (I think so) h263 CIF which result poor quality. 
As it relies on ffmpeg lib I guess other codecs will come shortly.

For now hard to say how quality will finally be using a good codec, but video 
flaw seems to be pretty good. As the N1 camera already support CIF size there 
is no scale operation on capture and as I use opengl-es to display it the 
resize of display in done by GPU (I guess...) so the only CPU work is to 
encode/decode codec + change pixel format. 
Unfortunately, opengl-es 1 does not support pixel formats used in the codec I 
tested - however I'm wondering if for some conversion a pixel shader could not 
do the trick...

So this is a good news, however do not expect something for daily use soon. 
pjsip-2.0 is still in dev and other things has to be done before having this 
landing. (Modular stuff (tls/video/codecs) in csipsimple for example).

If you want to build and test it it's available on the video branch of this 
svn. Build it yourself if you want to test : I've not yet checked all licenses 
of ffmpeg parts so I do not release anything. Besides as it require to build on 
pc it must be used by expert only for now... I don't want users to cry about 
the fact it's incomplete ;). 

Of course, any contribution to the video branch will be welcome if you build 
and improve it :)

Original comment by r3gis...@gmail.com on 24 Mar 2011 at 12:12

[GoogleCodeExporter]

congrats!

Original comment by ferna...@bugabundo.net on 24 Mar 2011 at 12:17

[GoogleCodeExporter]

Congratz!!! I have been waiting for this feature for some time :)

Original comment by sahadeva...@gmail.com on 25 Mar 2011 at 11:53

[GoogleCodeExporter]

congrats!!!I think this is the great news for this community.

Original comment by ocean.ra...@gmail.com on 26 Mar 2011 at 2:02

[GoogleCodeExporter]

Well done 3R! Let's hope this becomes available soon...

Original comment by peterfri...@gmail.com on 25 Apr 2011 at 11:32

[GoogleCodeExporter]

Hi. First off great work. I followed this thread and see that you were able to 
create a version that supports video. Do you know where I can get it? I would 
like to test video calling using my Nexus S. Thanks!

Original comment by kishanra...@gmail.com on 26 Apr 2011 at 3:14

[GoogleCodeExporter]

@kishanra : you could try to build it from video branch. However that's still 
complicated to build.
I'll release soon on the market and then will focus more to provide a build of 
csipsimple with a real support of video. Pjsip project has now h264 support 
which would make video calls much more interesting than just QCIF h263 which I 
was able to test ;).

Original comment by r3gis...@gmail.com on 7 May 2011 at 3:45

[GoogleCodeExporter]

Great news!  Keep up the good work!  Can't wait to test SIP video calls on my 
Nexus S!

Original comment by Bart.Van...@gmail.com on 18 May 2011 at 1:19

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

For who is interested in compiling video branch these are the instructions:

download branches Video:
- svn checkout http://csipsimple.googlecode.com/svn/branches/video/ folder_name

Then download ffmpeg for Android from Bambuser project 
(http://bambuser.com/opensource)

Follow the instructions in the file README to compile the project 
ffmpeg-android of Bambuser.

Once compiled ffmpeg for Android, put the folder in

/home/gio/..../folder_name/pjsip_android-2.0/apps (at the same level of pjsip).

Replace the folders: swig_tools and apps in the pjsip of the trunk version and 
then follow the build instruction at: 
http://code.google.com/p/csipsimple/wiki/HowToBuild

Your build are only under armeabi-v7a and not armeabi

../CSipSimple/libs/armeabi-v7a

ps: when I run video branches under my htc desire with frojo I have the 
following error:

E/AndroidRuntime( 5177): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 5177):    at 
com.csipsimple.pjsip.PjSipService.addAccount(PjSipService.java:519)
E/AndroidRuntime( 5177):    at 
com.csipsimple.service.SipService.addAllAccounts(SipService.java:977)
E/AndroidRuntime( 5177):    at 
com.csipsimple.service.SipService.reAddAllAccounts(SipService.java:1038)
E/AndroidRuntime( 5177):    at 
com.csipsimple.service.SipService.access$3(SipService.java:1035)
E/AndroidRuntime( 5177):    at 
com.csipsimple.service.SipService$1.reAddAllAccounts(SipService.java:155)
E/AndroidRuntime( 5177):    at 
com.csipsimple.wizards.BasePrefsWizard$4.run(BasePrefsWizard.java:320)

that is the same of the  issue 768 : 
http://code.google.com/p/csipsimple/issues/detail?id=768

I think the problem is my android phone. How can i compile video trunk also for 
armeabi and not only for armv7a? thanks in advance!

Original comment by gasc...@gmail.com on 8 Jun 2011 at 10:15

[GoogleCodeExporter]

@gasc : ffmpeg should go in the lib dir of the apk.

To all others.... the very very very first alpha version is available here :
http://nightlies.csipsimple.com/video/

THIS IS AN pre-ALPHA !!! PLEASE, do not report me bugs about this one. There is 
many missing things, only h263, and crashes after each call and UI is weird... 
but just don't worry, I know about that. This is just for tests.

Quick additional infos :
 * only h263. (h264 tests I did were not succesful at all, I guess pjsip still have things to do on this point to provide something clean -- or could be on my side with the video dev glue)
 * You may observe big latency on playing way. To avoid to cumulate latency use Jitsi on your pc to test for example. (I do my tests using pure SIP to SIP calls (no server). I don't know yet why we have such a latency - maybe on pjsip rtp management or on my opengl renderer (pjsip-2.0 is still you and my device is even more young ! )
 * Obviously network bandwidth is really really important to get good result ;)
 * It should be compatible with armv6 and armv7 on android 2.0 and upper devices. (I even did a test on a x10 mini).
 * It will consume a lot of CPU cause (I guess) the video capture on android tries to get frames as frequently as possible. On SGS I observe around 80% CPU. 

Original comment by r3gis...@gmail.com on 13 Jun 2011 at 10:34

[GoogleCodeExporter]

Alpha 1 available on the nightly build website :
 * Big latency on playing way is now fixed. 
You should now be able to do tests between two csipsimple without observing big 
latency. And you'll now see the remote party in almost real time ;).

(unfortunately this fix does not help with h264...)

Original comment by r3gis...@gmail.com on 14 Jun 2011 at 4:10

[GoogleCodeExporter]

I tried to check but I suppose it's still in dev. Any planned release for this 
feature ?

Thanks

Original comment by MyG...@gmail.com on 4 Sep 2011 at 2:44

[GoogleCodeExporter]

Can you please outline the steps to enable video support in the trunk version? 
I have the following projects loaded in eclipse and compiled
ActionBarSherlock  CSipSimpleCodecPack  CSipSimpleVideoPlugin
CSipSimple

I only see audio codecs but not video codecs in the settings. When I check "Use 
Video"
on calls, the call fails. However, I succeed making audio calls in the apk that 
I compile.

Original comment by saket...@gmail.com on 5 Mar 2012 at 11:11

[GoogleCodeExporter]

Maybe the more appropriate question is how to activate the video plugin 
assuming it got compiled since I got no errors in the compile

Original comment by saket...@gmail.com on 5 Mar 2012 at 11:23

[GoogleCodeExporter]

Normally if the plugin is installed and the "Use Video" option is activated it 
should automatically use video. The failure is maybe due to something else.
Can you collect some logs (see HowToCollectLogs wiki page). Maybe I'll find 
some interesting clue.

I'll add very soon the option in the user interface to setup video codec. It 
will also need some option about video codec config that I don't know yet how 
to show :). 
The bitrate setting seems very important to get something with less packet loss 
( there is also interesting investigation done on pjsip mailing : 
http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2012-March/014238.html 
it's for ipad, but I guess that it will goes almost the same on android )

Original comment by r3gis...@gmail.com on 6 Mar 2012 at 9:02

[GoogleCodeExporter]

Finally! I got video with csipsimple -- I had not enumerated project 
dependencies for  the SipHome project explicitly.

Before the declaring the dependency explictly, I had this
[2012-03-08 20:57:58 - SipHome] ------------------------------
[2012-03-08 20:57:58 - SipHome] Android Launch!
[2012-03-08 20:57:58 - SipHome] adb is running normally.
[2012-03-08 20:57:58 - SipHome] Performing com.csipsimple.ui.SipHome activity 
launch
[2012-03-08 20:57:58 - SipHome] Automatic Target Mode: using device 
'0146DD600F00900E'
[2012-03-08 20:57:58 - SipHome] Uploading SipHome.apk onto device 
'0146DD600F00900E'
[2012-03-08 20:57:59 - SipHome] Installing SipHome.apk...
[2012-03-08 20:58:08 - SipHome] Success!
[2012-03-08 20:58:08 - SipHome] Starting activity com.csipsimple.ui.SipHome on 
device 0146DD600F00900E
[2012-03-08 20:58:09 - SipHome] ActivityManager: Starting: Intent { 
act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] 
cmp=com.csipsimple/.ui.SipHome }

After declaring the dependency, it installed the dependent apk  -- namely 
csipsimple_plugins_codecs_pack1.apk, csipsimple_plugins_video.apk

[2012-03-08 21:06:26 - SipHome] ------------------------------
[2012-03-08 21:06:26 - SipHome] Android Launch!
[2012-03-08 21:06:26 - SipHome] adb is running normally.
[2012-03-08 21:06:26 - SipHome] Performing com.csipsimple.ui.SipHome activity 
launch
[2012-03-08 21:06:26 - SipHome] Automatic Target Mode: using device 
'0146DD600F00900E'
[2012-03-08 21:06:26 - SipHome] Uploading SipHome.apk onto device 
'0146DD600F00900E'
[2012-03-08 21:06:27 - SipHome] Installing SipHome.apk...
[2012-03-08 21:06:33 - SipHome] Success!
[2012-03-08 21:06:33 - com_actionbarsherlock] Could not find 
com_actionbarsherlock.apk!
[2012-03-08 21:06:33 - SipHome] Project dependency found, installing: 
com_csipsimple_plugins_codecs_pack1
[2012-03-08 21:06:33 - com_csipsimple_plugins_codecs_pack1] Uploading 
com_csipsimple_plugins_codecs_pack1.apk onto device '0146DD600F00900E'
[2012-03-08 21:06:33 - com_csipsimple_plugins_codecs_pack1] Installing 
com_csipsimple_plugins_codecs_pack1.apk...
[2012-03-08 21:06:37 - com_csipsimple_plugins_codecs_pack1] Success!
[2012-03-08 21:06:37 - SipHome] Project dependency found, installing: 
com_csipsimple_plugins_video
[2012-03-08 21:06:37 - com_csipsimple_plugins_video] Uploading 
com_csipsimple_plugins_video.apk onto device '0146DD600F00900E'
[2012-03-08 21:06:38 - com_csipsimple_plugins_video] Installing 
com_csipsimple_plugins_video.apk...
[2012-03-08 21:06:41 - com_csipsimple_plugins_video] Success!
[2012-03-08 21:06:41 - SipHome] Starting activity com.csipsimple.ui.SipHome on 
device 0146DD600F00900E
[2012-03-08 21:06:41 - SipHome] ActivityManager: Starting: Intent { 
act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] 
cmp=com.csipsimple/.ui.SipHome }
[2012-03-08 21:07:38 - SipHome] ------------------------------

Thanks

Original comment by saket...@gmail.com on 9 Mar 2012 at 3:32

[GoogleCodeExporter]

Hello,

Hartley thanks for make such a gr8 project open source,
I want to make video call using csipsimple and want to show demo,
Can any one guide me from where should i start, should i use main trunk or 
video branch?

Thanks in advance,
Parag patel  

Original comment by paragpat...@gmail.com on 25 Mar 2012 at 8:01

[GoogleCodeExporter]

* download the latest nightly build : http://nightlies.csipsimple.com/trunk/ 
and install it
* download the video plugin : nightlies.csipsimple.com/plugins/ and install it
* Setup csipsimple account to connect it a server that does support video (or 
rtp transparent)
* Go in csipsimple global settings, and in "call options" select "Use video" 
option.
* call a remote contact that also support video.

It should work, but keep in mind it's the beginning of video support and just 
reflects current state of development about video but not what is finally 
expected. 

Original comment by r3gis...@gmail.com on 25 Mar 2012 at 9:44

[GoogleCodeExporter]

Hello,

I've just tried the steps provided above, to try out the video call feature. 
However the called party responses with "400 Bad SDP" when the "Use Video" 
option is enabled. 
Could you take a look at this problem? It seems to me the the video media part 
in the SDP didn't contain any video codec. I'v neither found video codec listed 
in the client under the Settings/Media/Codecs part. Here is the SIP trace I 
hope it helps:

INVITE sip:halaszbalint@open-ims-dev.test SIP/2.0
Via: SIP/2.0/UDP 
192.168.10.149:56488;rport;branch=z9hG4bKPjLzl7dzXXo9te01B2Hp1zBWwZRV7SpTjO
Max-Forwards: 70
From: <sip:szabonora@open-ims-dev.test>;tag=kLmHTSTHTWrY27tcSwFfAlJUxzKTU-DR
To: <sip:halaszbalint@open-ims-dev.test>
Contact: <sip:szabonora@192.168.10.149:56488;ob>
Call-ID: D5w.CUjGK6eF-1b7AVE39mDwVERq0wa.
CSeq: 6908 INVITE
Route: <sip:open-ims-dev.test:4060;lr>
Route: <sip:orig@scscf.open-ims-dev.test:6060;lr>
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, 
MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: CSipSimple r1461 / SK17i-10
Content-Type: application/sdp
Content-Length:   478

v=0
o=- 3545475249 3545475249 IN IP4 192.168.10.149
s=pjmedia
c=IN IP4 192.168.10.149
b=AS:84
t=0 0
a=X-nat:0
m=audio 40056 RTP/AVP 9 99 0 8 101
c=IN IP4 192.168.10.149
b=TIAS:64000
a=rtcp:40057 IN IP4 192.168.10.149
a=sendrecv
a=rtpmap:9 G722/8000
a=rtpmap:99 SILK/24000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
m=video 40058 RTP/AVP
c=IN IP4 192.168.10.149
a=rtcp:40059 IN IP4 192.168.10.149
a=sendrecv

SIP/2.0 400 Bad SDP
Via: SIP/2.0/UDP 
192.168.10.149:56488;rport=56488;branch=z9hG4bKPjLzl7dzXXo9te01B2Hp1zBWwZRV7SpTj
O
Record-Route: <sip:mt@pcscf.open-ims-dev.test:4060;lr>
Record-Route: <sip:mt@scscf.open-ims-dev.test:6060;lr>
Record-Route: <sip:mo@scscf.open-ims-dev.test:6060;lr>
Record-Route: <sip:mo@pcscf.open-ims-dev.test:4060;lr>
Call-ID: D5w.CUjGK6eF-1b7AVE39mDwVERq0wa.
From: <sip:szabonora@open-ims-dev.test>;tag=kLmHTSTHTWrY27tcSwFfAlJUxzKTU-DR
To: <sip:halaszbalint@open-ims-dev.test>;tag=z9hG4bK7b8f.e59ea666.0
CSeq: 6908 INVITE
Warning: 399 localhost "No SDP payload format in the media line 
(PJMEDIA_SDP_ENOFMT)"
Content-Length:  0
P-Asserted-Identity: <sip:halaszbalint@open-ims-dev.test>
ACK sip:halaszbalint@open-ims-dev.test SIP/2.0
Via: SIP/2.0/UDP 
192.168.10.149:56488;rport;branch=z9hG4bKPjLzl7dzXXo9te01B2Hp1zBWwZRV7SpTjO
Max-Forwards: 70
From: <sip:szabonora@open-ims-dev.test>;tag=kLmHTSTHTWrY27tcSwFfAlJUxzKTU-DR
To: <sip:halaszbalint@open-ims-dev.test>;tag=z9hG4bK7b8f.e59ea666.0
Call-ID: D5w.CUjGK6eF-1b7AVE39mDwVERq0wa.
CSeq: 6908 ACK
Route: <sip:open-ims-dev.test:4060;lr>
Route: <sip:orig@scscf.open-ims-dev.test:6060;lr>
Content-Length:  0

Original comment by matyas.o...@gmail.com on 8 May 2012 at 2:23

[GoogleCodeExporter]

The video plugin is not recognize anymore, I have to do a new build for latest 
nightlies.

Original comment by r3gis...@gmail.com on 8 May 2012 at 4:45

[GoogleCodeExporter]

Is it the "09-May-2012 00:40" ?

Original comment by matyas.o...@gmail.com on 9 May 2012 at 9:34

[GoogleCodeExporter]

yep :)

Original comment by r3gis...@gmail.com on 9 May 2012 at 9:55

[GoogleCodeExporter]

I tried to get a working combination of nightly build of CSipSimple with latest 
CSipSimpleVideoPlugin (from May 8th) but no luck.
I tried first CSipSimpleVideoPlugin with the official version of CSipSimple 
(from Google Play "Market"), but it didn't work.
How can I verify, if CSipSimpleVideoPlugin is compatible with certain version 
of CSipSimple?
Should I install also CSipSimpleCodecPack (from May 13th) or it is not needed? 
I only want to test H.263 as a videocodec.
I know that video call in CSipSimple is in beta phase, but give me a hint, 
please, for any instructions to enable it.

Original comment by joze.rov...@gmail.com on 15 May 2012 at 7:54

[GoogleCodeExporter]

Normally only latest nightly works with latest CSipSimpleVideoPlugin.
You also have to enable video calls in settings (calls settings) and let 
account auto-transmit/show in expert wizard mode.
You can then check that the video plugin is correctly loaded in media settings 
> codecs. You should see H263 and H264.
Then, you can try a call, and if remote party and server(s) on the middle are 
compliant with video calls it should work. If not you should try investigate 
logs (I can help with that, see HowToCollectLogs wiki page).
However, keep in mind that's still under development and not made for 
production use. There is a lot of optim missing and the csipsimple ui has just 
very basic support of video (there is no button to make a video call - and no 
button to turn video on/off during a call).

Original comment by r3gis...@gmail.com on 15 May 2012 at 12:53

[GoogleCodeExporter]

Thank you for your help.
I tried a call and send a log to [developers at csipsimple dot com] with issue 
112 in the begining of the message.
I use the SIP server of Telekom Slovenije, which is based on Counterpath core 
(main client is banded Counterpath Bria for windows).
CSipSimple works fine (with STUN=voip.mobitel.si for NAT-ed LAN) for 
voicecalls, but video part doesn't work. Could you, please, verify the log file 
to check what should be wrong.

Original comment by joze.rov...@gmail.com on 18 May 2012 at 9:07

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi all,

Currently, I have finished to build Csipsimple as 
library and use this library to build another Voip App, I have built another 
app successful with audio call. Now I want to develop video call feature in my 
app with Csipsimple API. Because I have seen there are some APIs in Csipsimple 
library which seem to use to make video call, but I have some wrong with these 
API, I have configure the SipConfigManager.USE_VIDEO is TRUE property before I 
call API to start Sip service, and put TRUE to Sipsession.OPT_CALL_VIDEO and 
replace makecall() API by makecallwithoption(). But I'm not successful, anyone 
have experience please help me about this.

I also have seen we have to install the videocallplugin in Csipsimple app on 
the device to use video call feature. Are there some things wrong here?

Thanks.   

Original comment by truongle...@gmail.com on 7 Nov 2012 at 1:59

[GoogleCodeExporter]

@tuonglenhut : please ask these question on the dev google group (it has been 
already replied BTW) :
Video is not ready to land in any product for now and so it's not yet supported 
officially in API (only those that understand the inside code can use it and 
help to debug -- if other tries to use it will make us loose time to get it 
land for anyone).
Else, yes you need the video plugin, you also need to turn on the video option 
in settings and you need to use the csipsimple in call control view (as for now 
it's the only one able to manage the video stream and it uses something that is 
not available in the external API to do the rendering for technical reason that 
will be solved later).

Original comment by r3gis...@gmail.com on 7 Nov 2012 at 8:56

[GoogleCodeExporter]

Hi Regis,
I hope all is going well. In fact I can see CSS project is moving forward.:)
I have tested recent version and have found progress in video. During my tests 
in our EuroTELEFON network I can have perfect video connection while initiated 
from our EuroTELEFON Video app on PC to my CSS on LG P880 or Samsung Note 2, 
but if the call is initiated from an android device to the PC app or to other 
CSS on another device, CSS does not even try to show video windows. I have 
checked logs on our VoIP server and it shows that the connection was 
established with codecs for video (H264) on both directions, so the problem is 
probably on CSS side. If you need any logs I can send it to you, but I hope you 
still have access to your account in ET. However, I would be happy to provide 
any help from our side. 

Original comment by Tadeusz...@gmail.com on 27 Nov 2012 at 6:49

[GoogleCodeExporter]

Issue 2189 has been merged into this issue.

Original comment by r3gis...@gmail.com on 5 May 2013 at 3:09

[GoogleCodeExporter]

Issue 2357 has been merged into this issue.

Original comment by r3gis...@gmail.com on 14 May 2013 at 9:42

[GoogleCodeExporter]

Issue 2540 has been merged into this issue.

Original comment by r3gis...@gmail.com on 7 Nov 2013 at 8:08