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
