Eric Chamberlain wrote: > The voice performance would be terrible over HTTP. Skype proved the opposite - voice quality can be fine, even over HTTP(S) > > Rather than hacking up the sip and RTP stacks with a custom solution, > I'd look at using solutions that are already out there. SIPTLS on a > non-standard port and IPsec for the RTP traffic, or IPsec for both > signaling and media. You can't inspect the traffic if it is > encrypted and IPsec can be used to obfuscate call traffic heuristics. Varun mentioned that OpenVPN does not work too. If there are Packet Inspectors which can detect VoIP like traffic and block it (e.g. RTP over OpenVPN or IPsec also generates typical traffic - a packet every 20ms, all the same size, regularly, bidirectional ...) then IPsec might be problematic too. Anyway, it is worth a try. Sounds like a cat-and-mouse-game .... regards Klaus > > > > On May 10, 2010, at 11:30 PM, Varun Singh wrote: > >> HI All. >> >> These we have a big problem in the gulf for the telecom companies >> are facing that is they are incapable of routing the sip traffic >> through the internet. AFAIK the sip traffic is blocked not only by >> the standard port blocking for SIP and RTP but also Deep Packet >> Analyzers are being used. The DPA(Deep Packet Analyzers) algorithms >> are read the packets and can also determine the nature of >> communication going on. That is why in some areas the OpenVPN >> Tunneling on PJSIP is also being caught and blocked. >> >> Other solution can be HTTP tunneling which can be great solution >> but I don't think it will be a performance oriented as being a TCP >> oriented protocol. But it is the most effective solution. So is >> there any implementation available for the HTTP Tunneling with the >> PJSIP so that can be implemented. Is there are other solutions for >> it. >> >> >> Please propose so that we can start finding the best solution. >> >> >> Regards: varun >> >> DISCLAIMER: >> ----------------------------------------------------------------------------------------------------------------------- >> >> >> The contents of this e-mail and any attachment(s) are confidential >> and intended for the named recipient(s) only. It shall not attach >> any liability on the originator or HCL or its affiliates. Any views >> or opinions presented in this email are solely those of the author >> and may not necessarily reflect the opinions of HCL or its >> affiliates. Any form of reproduction, dissemination, copying, >> disclosure, modification, distribution and / or publication of this >> message without the prior written consent of the author of this >> e-mail is strictly prohibited. If you have received this email in >> error please delete it and notify the sender immediately. Before >> opening any mail and attachments please check them for viruses and >> defect. >> >> ----------------------------------------------------------------------------------------------------------------------- >> >> >> _______________________________________________ Visit our blog: >> http://blog.pjsip.org >> >> pjsip mailing list pjsip at lists.pjsip.org >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > _______________________________________________ Visit our blog: > http://blog.pjsip.org > > pjsip mailing list pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
