Can you give a quick over view on how SIP differs from HTTP in functionality and what are the proble

Can you give a quick over view on how SIP differs from HTTP in functionality and what are the proble

Can you give a quick over view on how SIP differs from HTTP in functionality and what are the problems of using PSTN as a back for VoIP?

    Requires Free Membership to View

    SearchUnifiedCommunications.com members gain immediate and unlimited access breaking industry news, expert advice on UC, technical guides, and more -- all at no cost. Join me on SearchUnifiedCommunications.com today!

    Kate Gerwig, Editorial Director

    By submitting your registration information to SearchUnifiedCommunications.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchUnifiedCommunications.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

SIP and HTTP are very similar in structure as they are both text based application layer protocols. HTTP allows for transferring hypertext based files between remote and local systems. SIP allows for setting up and tearing down sessions using any type of media (e.g., voice, video and fax). Many people today that are using VoIP service often have backup PSTN service, or use PSTN service in conjunction with their VoIP service. This is mainly for redundancy and also for toll bypass. There are no real problems with this as long as a proper VoIP phone system which supports these features is chosen.

This was first published in July 2004