ing with non-IP networks, Megaco and H.323 are required. Often vendors of VoIP equipment integrate all three protocols on a single platform. SIP is closely related to IP. SIP borrows most of its syntax and semantics from the familiar HTTP (hypertext transfer protocol). An SIP message looks very much like an HTTP message, especially with message formatting, header, and multipurpose Internet mail extension support. It uses addresses that are very similar to URLs (uniform resource locators) and to email. For example, a call may be made to so-in-so@such-and-such SIP messages are text-based rather than binary. This makes writing easier and the debugging of software more straightforward. There are two modes with which a caller can set up a call with SIP. These are called redirect and proxy, and servers are designed to handle these modes. Both modes issue an "invite" message for another user to participate in a call. The redirect server is used to supply the address (URL) of an unknown called addressee. In this case the "invite" message is sent to the redirect server, which consults the location server for address information. Once this address information is sent to the calling user, a second "invite" message is issued, now with the correct address. One specific type of SIP is called SIP-T (T for telephone). This is a function that allows calls from CCITT Signaling System 7 (SS7) to interface with a telephone in an IP-based network. The particular user part of SS7 for this application is ISUP (see Chapter 14, SS No. 7). 15.5.3 Media Gateway Control Protocol (MGCP) This protocol was the predecessor to Megaco (see Section 15.4.4) and still holds sway with a number of carriers and other VoIP users. MGCP [20] assumes a call control architecture where the call control "intelligence" is outside the gateways (i.e., at the network edge) and handled by external call control elements. Thus, the MGCP assumes that these call control elements, or "call agents," will synchronize with each other to send coherent commands VOICE-OVER P