What is the relationship between MGCP/Megaco and SIP?
sagitraz 19-June-2008 04:23:38 AM
Comments


The details of combining the two in a system are still being fleshed out. MGCP is a device control protocol, where a slave (gateway (MG)) is controlled by a master (media gateway controller (MGC), call agent). SIP may be used between controllers, in a peer-to-peer relationship. Note that to the SIP side, the MGC looks like a node with a large number of connections, but otherwise the same as a "native" SIP device. Similarly, the MG is completely unaware that the call between MGCs is established via SIP. Only the MGC needs to understand both protocols.
Posted by gsmxprt


SIP is call control protocol which handles signaling messages such as INVITE, ACK 200K etc. Megaco is gateway control protocol with ADD, REPLY message for connecting the voice channels between call server and Media Gateway. Media Gateway Control Protocol (MGCP) is a signaling and call control protocol used within a distributed Voice over IP system. All these protocol are have open and can monitiored via wireshark which brings so much visibility.
Posted by johnwesley


Posted: 20-June-2008 03:37:29 PM By: johnwesley

SIP is call control protocol which handles signaling messages such as INVITE, ACK 200K etc. Megaco is gateway control protocol with ADD, REPLY message for connecting the voice channels between call server and Media Gateway. Media Gateway Control Protocol (MGCP) is a signaling and call control protocol used within a distributed Voice over IP system. All these protocol are have open and can monitiored via wireshark which brings so much visibility.

Posted: 30-June-2008 11:30:11 AM By: gsmxprt

The details of combining the two in a system are still being fleshed out. MGCP is a device control protocol, where a slave (gateway (MG)) is controlled by a master (media gateway controller (MGC), call agent). SIP may be used between controllers, in a peer-to-peer relationship. Note that to the SIP side, the MGC looks like a node with a large number of connections, but otherwise the same as a "native" SIP device. Similarly, the MG is completely unaware that the call between MGCs is established via SIP. Only the MGC needs to understand both protocols.