VoIP uses the Internet Protocol (IP) to transmit voice as packets over an IP network. Using VoIP protocols, voice...
communications can be achieved on any IP network regardless it is Internet, Intranets or Local Area Networks (LAN). In a VoIP enabled network, the voice signal is digitized, compressed and converted to IP packets and then transmitted over the IP network. VoIP signaling protocols are used to set up and tear down calls, carry information required to locate users and negotiate capabilities. The key benefits of Internet telephony (voice over IP) are the very low cost, the integration of data, voice and video on one network, the new services created on the converged network and simplified management of end user and terminals.
There are a few VoIP protocol stacks which are derived from various standard bodies and vendors, namely H.323, SIP, MEGACO and MGCP.
H.323 is the ITU-T's standard, which was originally developed for multimedia conferencing on LANs, but was later extended to cover VoIP. The standard encompasses both point to point communications and multipoint conferences. H.323 defines four logical components: Terminals, Gateways, Gatekeepers and Multipoint Control Units (MCUs). Terminals, gateways and MCUs are known as endpoints.
Session Initiation Protocol (SIP) is the IETF's standard for establishing VOIP connections. SIP is an application layer control protocol for creating, modifying and terminating sessions with one or more participants. The architecture of SIP is similar to that of HTTP (client-server protocol). Requests are generated by the client and sent to the server. The server processes the requests and then sends a response to the client. A request and the responses for that request make a transaction.
Media Gateway Control Protocol (MGCP) is a Cisco and Telcordia proposed VOIP protocol that defines communication between call control elements (Call Agents or Media Gateway) and telephony gateways. MGCP is a control protocol, allowing a central coordinator to monitor events in IP phones and gateways and instructs them to send media to specific addresses. In the MGCP architecture, The call control intelligence is located outside the gateways and is handled by the call control elements (the Call Agent). Also the call control elements (Call Agents) will synchronize with each other to send coherent commands to the gateways under their control.
The Media Gateway Control Protocol (Megaco) is a result of joint efforts of the IETF and the ITU-T (ITU-T Recommendation H.248). Megaco/H.248 is for control of elements in a physically decomposed multimedia gateway, which enables separation of call control from media conversion. Megaco/H.248 addresses the relationship between the Media Gateway (MG), which converts circuit-switched voice to packet-based traffic, and the Media Gateway Controller, which dictates the service logic of that traffic). Megaco/H.248 instructs an MG to connect streams coming from outside a packet or cell data network onto a packet or cell stream such as the Real-Time Transport Protocol (RTP). Megaco/H.248 is essentially quite similar to MGCP from an architectural standpoint and the controller-to-gateway relationship, but Megaco/H.248 supports a broader range of networks, such as ATM.