Audio Call versus Visio Call versus 2-way Video Call??

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Currently Audio call precludes you from adding Video at a later point. I 
guess you need to select Visio call if you want to upgrade at any point during 
the call
2. Currently there is no option to start a video call with both sides sending 
video right off the bat without any additional "Send Video" key presses
3.

What is the expected output? What do you see instead?

It would be nice to not completely preclude audio calls from upgrading to video 
if the two sides are capable. 

It would also be nice to provide an option to launch a video call with the 
initial INVITE itself containing both audio&video SDP(that can later be 
downgraded to 1-way/audio-only way by either party using the "Stop Video" menu 
item).

I am proposing that Audio Only call be elimiated from the GUI. If no video 
codecs are selected, the Visio Call can mimic what Audio Call currently does.

Your thoughts?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by saket...@gmail.com on 16 Nov 2010 at 11:47

[GoogleCodeExporter]

I have received many mails asking why it's not possible to start receiving 
video stream without pressing "Send Video". I was confused because there is no 
relation between the outgoing and incoming stream. It's only the last days that 
I've understood that it's a NAT issue. In order to open the UDP channel both 
parties must send at least one packet to open pinhole in the NAT. The latest 
SVN version should solve the problem (or try 
http://imsdroid.googlecode.com/svn/trunk/debug/imsdroid-1.0.324-armv7-a.apk).

About the issue:
1. What you are describing (Add/remove media stream) make sense and it's 
formerly defined in MMTel specification. It will be easy to implement as 
doubango already support this.
2. See Above.

For eliminating audio call from the UI, I don't really now if it's a good idea 
or not. Don't know percent of person using audio only calls.

Original comment by boss...@yahoo.fr on 16 Nov 2010 at 12:35

• Changed state: Accepted

[GoogleCodeExporter]

I was thinking about this as well. I think UI will be cleaner if we don't 
differentiate between video and audio call. After all, the user may not know if 
the remote supports video capabilities or not. Therefore, I suggest just have a 
single call option and always send audio and video parameters that the user 
configured. Let's SIP exchange negotiate the proper type of the call. the users 
making just audio call will not need to make any changes to their behavior. 
Voice call will still be supported. My recommendation is to have a single call 
button to make UI easier.

Original comment by alex9...@gmail.com on 29 Nov 2010 at 3:32

[GoogleCodeExporter]

Strongly agree with Alex's point above, the design should be simplified to a 
single call option with all user enabled codecs presented in initial SDP; 
Optimally, this change could also benefit from an extra settings feature to let 
users prioritize the presented codecs as well, in order to keep things flexible.

Original comment by webde...@gmail.com on 30 Dec 2010 at 3:21