My colleague Bill's blog as noted above is worth the read. You will get a mixed bag of answers on here from folks who believe that you should always use H323 to those who only have used MGCP because of it's simplicity when setting it up. To summarize some of Bill's points:
If you have a remote site and need SRST, it's usually easier to just use H323 (or SIP) because you're gonna need much of that config anyway to get much value out of SRST.
If you are not comfortable with IOS and/or have limited support staff, MGCP has some value. It centralizes the call control and routing whereas H323/SIP push it to the edges.
There isn't really a one size fits all answer here.
It's not really a matter of "supporting" MGCP or not...it's a matter of preference. If you're going to use SRST then my preference is to just use H.323 for the remote site gateway. You can do MGCP with failover to SRST and that's OK too. When you do that, you use MGCP and CUCM for standard call control/processing but then fall back to an H.323 config on the same gateway for SRST call processing...hence, that's why I'd say just use H.323 to start with.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...