This is a bit more than I had in mind, actually. My goal is humbler: a SIP device joins a domain and knows of a device sip url who has a web server with some interesting info. He requests to start a session with such device, of type HTTP. The proxy network routes the invite to the proper device and this returns info on the HTTP url to use ... for this matter, generic UDP or TCP pipes, which I need also, could be setup ... Maybe for protocols such HTTP or FTP, in which (at least for me) receiving a URL is the final objective, doing a whole INV-OK-ACK-BYE-OK is a bit overkill ... maybe the INFO method shall be more appropriate ... but is it accepted out-of-dialog?
Cesc On 5/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I am interested in this. For sometime now, I have been reading and > thinking of how to use SIP to manage HTTP session. > Basically, I want to achieve HTTP Session mobility between similar and > disparate UAs using SIP. > > Any information on this will be much appreciated. > > MIKE > > > > > On 5/10/07, Paul Kyzivat <[EMAIL PROTECTED]> wrote: > >> > >> > >> Cesc wrote: > >> > Hi, > >> > > >> > Is there any limitations on the type of sessions SIP can create? > >> > For example, could plain data sessions (TCP or UDP) be created > >> > (negotiate listen port and IP, max framelength, ... ); or set up > >> > sessions for other known protocols, like HTTP (what IP/port that > >> > resource has the web page) or FTP? > >> > Is this specified in some RFC? any implementations? > >> > >> This certainly possible, and not restricted. You might want to look at > >> RFCs 4145 and 4572. But this may not always be wise even if possible. > >> There may be better ways, depending on the case. > >> > >> Paul > >> > > > > Care to elaborate on why and which better ways could there be? > > First, a comment ... I am not allowed to use DNS on my system, for > > many reasons that are here not relevant. Was DNS in your mind? > > I can imagine that HTTP and FTP (to name two) may have other ways ... > > which? > > But imagine I need a plain data link, to "tunnel" data from one point > > to the other of the network ... SIP sounds like a good set up > > mechanism (I want to avoid static configs, of course). > > > > Cesc > > _______________________________________________ > > Sip-implementors mailing list > > [email protected] > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > > > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
