add support for sip info method

[GoogleCodeExporter]

What steps will reproduce the problem?
1. in some case ,we want to get video I frame to display the video, this is a 
standard , that ,when we canot decode the video we should send video frame 
update request, as such ,we use INFO method in sip,

i have learn the doubango stack , the flow should be that : video session make 
a video frame update event ,
 the sip stack get the event and send a info request which sdp is a xml ,
but i donot know how to info from tdav_session_video to sip stack as there is 
no struct which hold the video session and sip stack, so , please give me some 
hint ,
 thanks :)

2.
3.

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

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 openser@yeah.net on 15 Jul 2011 at 8:13

[GoogleCodeExporter]

Could you please give us as reference (IETF, 3GPP, ESTI...)?

Original comment by boss...@yahoo.fr on 18 Jul 2011 at 2:06

• Changed state: Accepted

[GoogleCodeExporter]

Sending video fast update using the SIP signaling path ,the fallow is rfc 
definition.

http://www.rfc-editor.org/rfc/rfc5168.txt

Original comment by openser@yeah.net on 18 Jul 2011 at 2:59

[GoogleCodeExporter]

from the code , i learn that you can control video/audio session from sip stack 
, but seems no way to control sip stack from video/audio session, my mean is, 
for example, when  we cannot decode the video we may send an envent to sip 
stack ,then sip stack  send INFO request remote for update video frame, 
linphone has this feature .

Original comment by openser@yeah.net on 19 Jul 2011 at 7:11

[GoogleCodeExporter]

any idea about this sir ?

Original comment by openser@yeah.net on 22 Jul 2011 at 1:21

[GoogleCodeExporter]

TinyDav is a media container plugin and cannot be linked with tinySIP or any 
signaling (e.g. xmpp) library. The reverse is also true: tinySIP doesn't have 
any link with tinyDAY.
TinyDav contains plugin implementations (audio/video condecs, consumers, 
producers,...) defined (not implemented) in TinyMedia. TinySIP depends on 
TinyMedia.
To summary: TinySIP (signaling protocol) <---->TinyMedia(plugin 
definitions)<---->TinyDAV(plugin implementations) <-> SipSessions 
(Audio,video,msrp...) <-> Codec,Producer,Consumer,...

This is our design and we think it's the most flexible one to have mutiplatform 
framework.

As you can see, it's possible to alert the end-user(java code) when the 
sipsession starts the video consumer/producer using callbacks. You must 
implement the same mechanism ...but it's not so easy if you are beginner. I'll 
keep the issue open and will provide more details in the coming days.

Original comment by boss...@yahoo.fr on 22 Jul 2011 at 2:26

[GoogleCodeExporter]

i know it, thanks for your time sir.

Original comment by openser@yeah.net on 22 Jul 2011 at 3:44

[GoogleCodeExporter]

Fixed by revision 640.

Original comment by boss...@yahoo.fr on 31 Oct 2011 at 11:04

• Changed state: Fixed

[GoogleCodeExporter]

Sorry, it's revision 667.

Original comment by boss...@yahoo.fr on 31 Oct 2011 at 11:04