Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 306601 - provide video chat support to Sip Provider
Summary: provide video chat support to Sip Provider
Status: RESOLVED WONTFIX
Alias: None
Product: ECF
Classification: RT
Component: ecf.providers (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: ecf.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 193388
Blocks:
  Show dependency tree
 
Reported: 2010-03-20 08:24 EDT by Harshana Eranga Martin CLA
Modified: 2014-02-12 15:28 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Harshana Eranga Martin CLA 2010-03-20 08:24:12 EDT
Current sip provider supports only voice chat. But SIP protocol supports video chat as well. So this enhancement request is to provide video chat feature to sip provider.
Comment 1 Scott Lewis CLA 2010-03-20 11:52:57 EDT
This might justify a new API...i.e. a 'video' session setup API (analogous to the telephony.call API, but specifically for video sessions).  I don't know whether this will be necessary...perhaps it's just an addition to the call API.  I don't know.
Comment 2 Harshana Eranga Martin CLA 2010-03-20 12:18:42 EDT
In case of SIP, both voice and video are treated equally. If we want to create a voice session, we can send a Sip INVITE request to the intended recipient with our Voice capabilities. If we want to create a video session, then we can send a Sip INVITE request to the intended recipient with our Video capabilities. Another important thing is, the order of the sessions does not matter. If we want we can create the voice session first and while carrying out the voice session, we can create the video session. When both voice and video sessions are there they are considered as two different sessions. Even though we request to create both sessions at once they are considered as two different sessions and treated equally as I mentioned. We can terminate any session at any time without affecting any other existing session. So I think we might need a video session setup API which is very much similar to the Telephony.Call API. They'll do exactly the same thing WRT to the SIP protocol.
Comment 3 Scott Lewis CLA 2014-02-12 15:28:52 EST
Seems unlikely that resources will be available for this.  Would still like to do this, so please reopen if resources are/become available for work on sip provider and video extensions.