Abstract
Understanding how VoIP protocols function is important as it helps debug problems, assists in generating attacks in a security audit, and helps protect one against attacks targeting one Asterisk system. It involves a set of guidelines, which are covered in various request for comments (RFCs) and describe, in detail, how a protocol functions. VoIP data is transferred using small user datagram protocol (UDP) packets. Developers follow and use these RFCs to assist in development to help build applications. There are multiple RFCs covering various VoIP protocols. These describe how signaling works, how audio and video data is transferred, and various other features. Reading and understanding these RFCs can help unlock the “magic” of how VoIP works. This chapter shows two major functions with Inter-Asterisk eXchange (IAX2) and Session Initiation Protocol (SIP) is signaling and passing the audio/video data. Signaling handles the call build up, tear down, and modification of the call. The two protocols handle passing the audio data and signaling differently. While SIP is a signaling protocol in itself and uses RTP to pass the audio/video data, IAX2 chose to build both into one protocol.
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.
