#112 Support for video call

[Anonymous]

Originally created by: boss...@yahoo.fr

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 (https://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?

[Anonymous]

Originally posted by: r3gis...@gmail.com

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

[Anonymous]

Originally posted by: r3gis...@gmail.com

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

[Anonymous]

Originally posted by: MyG...@gmail.com

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

Thanks

[Anonymous]

Originally posted by: saket...@gmail.com

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.

[Anonymous]

Originally posted by: saket...@gmail.com

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

[Anonymous]

Originally posted by: r3gis...@gmail.com

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 )

[Anonymous]

Originally posted by: saket...@gmail.com

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

[Anonymous]

Originally posted by: paragpat...@gmail.com

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 

[Anonymous]

Originally posted by: r3gis...@gmail.com

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

[Anonymous]

Originally posted by: matyas.o...@gmail.com

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

[Anonymous]

Originally posted by: r3gis...@gmail.com

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

[Anonymous]

Originally posted by: matyas.o...@gmail.com

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

[Anonymous]

Originally posted by: r3gis...@gmail.com

yep :)

[Anonymous]

Originally posted by: joze.rov...@gmail.com

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.

[Anonymous]

Originally posted by: r3gis...@gmail.com

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

[Anonymous]

Originally posted by: joze.rov...@gmail.com

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.

[Anonymous]

Originally posted by: truongle...@gmail.com

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.  

[Anonymous]

Originally posted by: r3gis...@gmail.com

@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).

[Anonymous]

Originally posted by: Tadeusz...@gmail.com

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.

[Anonymous]

Originally posted by: r3gis...@gmail.com

Issue 2189 has been merged into this issue.

[Anonymous]

Originally posted by: r3gis...@gmail.com

Issue 2357 has been merged into this issue.

[Anonymous]

Originally posted by: r3gis...@gmail.com

Issue 2540 has been merged into this issue.

[Anonymous]

Originally posted by: poonia.t...@gmail.com

Hi
I've built CSipSimple ([r2336]) and its video plugin, checked 'Use video' in 'call setting' and have video call button in dial panel in both caller and receiver.
But when I tried to make a video call nothing happened and a voice call was established.
Please provide me with what I missed?
Thanks.

[Anonymous]

Originally posted by: zhlmfly1...@gmail.com

Hi
Please check your server
sometimes the server is not support a video call.
when i used "yate" as a sip-serverŁŹi cannot establish a video call ,just
like yours.

2013-12-10 18:00 GMT+08:00 <csipsimple@googlecode.com>:

[Anonymous]

Originally posted by: pcri...@gmail.com

Hi, I am using voipswitch as my server. (http://www.voipswitch.com)
I have the same problem as  poonia.t...@gmail.com.

I can not transmit video and sometimes when I enable it, the application crashes.

If the other end uses voipswitch'es client I can see them, but they cannon see me.

It is like csipsimple doesn't transmit.

I enabled h263 (our server supports it).
If you have any ideas I would be gratefull.

Thank you.