Abstract
Session Initiation Protocol (SIP), despite its beginnings as a protocol for multimedia session signaling over the Internet, has rapidly evolved as a prominent signaling protocol for Internet telephony. While most efforts to evolve the protocol have resulted in greater simplicity, flexibility, and extensibility, some uncoordinated efforts have engendered a few open challenges for the protocol implementers. In this paper, we contemplate some of these challenges, including the 3rd Generation Partnership Project's (3GPP's) use of SIP, flexibility in the service model, lack of ratification of user/application interaction model, and network address translator (NAT) traversal. In analyzing these issues, it is important to recognize two facts early. First, some of these issues are inherent in Internet telephony in general and are not endemic to SIP. Second, although standards bodies are attempting to address most of these issues, competing and proprietary implementations are emerging to the detriment of the entire SIP community.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
