Hi Mauro, When HTTP tunnel is used, both SIP and RTP traffic pass inside a single HTTP tunnel. It is not possible actually to seperate SIP and RTP traffic to different tunnels.
Regards, Minh 2009/5/12 Mauro Sergio Ferreira Brasil <[email protected]> > Hi Vadim! > > I think I'm not understanding how the http tunneling work. > I'll have a closer look on it as soon as I get myself free of some urgent > demands here. > > My impression was that the configuration will only make the SIP information > to be encapsulated on HTTP requests, and not the RTP data. > Here we need both data (SIP and RTP) to be tunneled to different servers, > and I'm not sure if this will work. > > On old codes we have here, the tunneling configuration using HttpTunnel > library was made to both servers (SIP and RTP) given by names " > tunnel.sip.domain.com.br" and "tunnel.media.domain.com.br". (with some > internal adjustments off course). > That's why I'm probably messing things up. > > Thanks and best regards, > Mauro. > > > > Vadim Lebedev escreveu: > > Hi Mauro, > It could be possible, but what the interest? > > HTTP tunnelis simply a firewall traversal method.. > > However, If you REALLY need this i'll accept it into the tree > > Thanks > Vadim > Le 7 mai 09 à 22:33, Mauro Sergio Ferreira Brasil a écrit : > > Hi Vadim! > > Let me first get things clear that I don't even know whether what I'll > consider bellow is possible, and I don't want to create false expectations. > I'm quite new to this version codes, you know. > > If I find some acceptable way to provide separated configuration to SIP and > RTP http tunneling, does the resulting patch have a chance to be applied ? > I mean, is this something desirable to QuteCom ? > > Thank's and best regards, > Mauro. > > > > > Vadim Lebedev escreveu: > > Http tunnel setting is global > > Thanks > Vadim > Le 7 mai 09 à 21:23, Mauro Sergio Ferreira Brasil a écrit : > > Hello there! > > I was having a look on "qutecom-2-2-RC3" package of codes and I've got > stuck on a configuration that is made on > "PhApiWrapper::setNetworkParameter()". > It seems to me that the configuration that is made to support http > tunneling is global or is intended just to be used by SIP transmissions. > > Am I right ? > > If I am right and I need to use QuteCom libraries on a scenario with http > tunneling demand for SIP and RTP data, and with different server > configuration to both protocols, will it be too difficult to adjust ? > > Thanks and best regards, > > -- > *At., > * <CMMI_2.jpg> *Technology and Quality on Information* Mauro Sérgio > Ferreira Brasil Coordenador de Projetos e Analista de Sistemas + > [email protected] <@tqi.com.br> : www.tqi.com.br ( + 55 > (34)3291-1700 ( + 55 (34)9971-2572 > _______________________________________________ > QuteCom-dev mailing list > [email protected] > http://lists.qutecom.org/mailman/listinfo/qutecom-dev > > > > -- > *At., > * <CMMI_2.jpg> *Technology and Quality on Information* Mauro Sérgio > Ferreira Brasil Coordenador de Projetos e Analista de Sistemas + > [email protected] <@tqi.com.br> : www.tqi.com.br ( + 55 > (34)3291-1700 ( + 55 (34)9971-2572 > > > > -- > *At., > * *Technology and Quality on Information* Mauro Sérgio Ferreira > Brasil Coordenador de Projetos e Analista de Sistemas + > [email protected] <@tqi.com.br> : www.tqi.com.br ( + 55 > (34)3291-1700 ( + 55 (34)9971-2572 > > _______________________________________________ > QuteCom-dev mailing list > [email protected] > http://lists.qutecom.org/mailman/listinfo/qutecom-dev > >
_______________________________________________ QuteCom-dev mailing list [email protected] http://lists.qutecom.org/mailman/listinfo/qutecom-dev
