Why was MGCP developed when we already had H.323 & SIP? - sip simple
Why MGCP was developed after H.323 and SIP?
I understand that debug messages H.323 is complex and difficult to debug, error, SIP has solved this problem with a simple text message / reply and best practices services SIP stack.
But the question is: What was the need for the development of the battery when MGCP, H.323 and SIP have prevailed in the market, how it is different VoIP network and a better quality for the end user and the network better that H 323 and SIP?
All the pros and cons of course ..
Not a question of distribution for pointers, and subjective responses that are good.
Thanks in advance
Monday, January 11, 2010
Sip Simple Why Was MGCP Developed When We Already Had H.323 & SIP?
Subscribe to:
Post Comments (Atom)
1 comments:
MGCP and H.248 are device control protocols, not session control protocols like H.323 and SIP. MGCP and H.248 are used by a device like a softswitch to control devices centrally, which is useful in some cases. In theory, MGCP and H.248 allow one to build simpler devices. It also allows a network operator to have tight control over the device, even capturing every dialed digit, like the old PSTN.
As for SIP being simpler than H.323, I disagree. If it were so simple, we would not suffer with so many interoperability issues around the world.
Post a Comment