| MMS 1.X.Y | MMS 2.X.Y | |
| Standalone MMS Server | Not available | Available |
| Embedded in JBoss AS | JBoss AS 4.X.Y | JBoss AS 5.X.Y |
| MGCP Support | MGCP Support available via MGCP JAIN SLEE Service (SBB). Hence to use MGCP control protocol one needs to install JAIN SLEE Server, MGCP RA and mgcp-controller-sbb service | MGCP Controller is inbuilt with MMS. No SLEE required |
| JSR-309 Support | Not available | JSR-309 is availale which uses MGCP as MS control protocol |
| MSC API | Available. This is custom API developed by Mobicents Media Server. | Not available |
| Performance | Compared to 2.x.y, 1.x.y has very high Jitter problems due to large number of threads used. It uses plain sockets for RTP | Very less Jitter as compared to 1.x.y. It uses NIO for RTP |
| Basic Architecture | MMS 1.x.y is built on JMX Microkernel. No flexibility of deciding the media-path for endpoints. For example for IVR, DTMF detection will be used irrespective of application may use it or not. | MMS 2.x.y is built on top of Jboss Microcontainer. Flexibility of defining the media-path for endpoints. For example if application will never detect DTMF but only recording, the DTMF detector media component can be completely removed from IVR endpoint and hence save some processing. |