I am not sure what announcement you are referring to, as I have not seen anything to this effect.
One thing that is happening with the release of Cisco CallManager 3.1 is expanded MGCP support. In that release, the only gateways I know of that will still use Skinny are the AT-x and AS-x gateways, which are not too common anymore. The Cat6k and Cat4k voice cards will use MGCP to talk to CallManager, same for the VG200, 2600, 3600, 4224, and hopefully more IOS gateways soon.
Note that none of this has anything to do with H.323 support in CallManager. It is still supported, and still works pretty much the same way.
I can't say at this time exactly which telephone signaling protocols will be supported with which MGCP gateways.
But yes, MGCP support in CallManager 3.1 has been expanded to support some digital interfaces. I think many of the commonly desired configurations will work. For example:
6608-T1 - PRI, CAS
6608-E1 - PRI
VG200 - FXO, FXS, T1-PRI, T1-CAS, E1-PRI
2600 - same
3600 - same
Note that there is more than one piece to this puzzle; CallManager 3.1 supports the primitives to handle MGCP analog FXO/FXS, T1 CAS, PRI, PRI backhaul, etc.
But the CCMAdmin GUI has to be programmed to work with each of the gateways since it needs to know the slot layouts, etc.
And the software on the gateway needs to support these various methods. So the first IOS platform to support the above is the VG200, and there will be a specific IOS version where doing the above is supported with CallManager 3.1. Then the 2600 and 3600 IOS will have these required features in a certain version of IOS, and so on.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...