InstallationNotes

1. labels mms,jsr309,certified,howto,build,run,media,server,mobicents

How to install MMS implementation and verify compliance with JSR 309

  # Download and install [http://ant.apache.org/ ant] and [http://maven.apache.org/ Maven]:
  # Checkout the media server source code from the main git repository, revision [https://code.google.com/p/mediaserver/source/browse/?r=b7ab801ffca891192a1f8dbc86da0c3a10571c80 b7ab801ffca8]
  # Lets assume $mediaserver is the root folder of the checked out media server code
  # Compilation - to compile media server run {{{ mvn clean install }}} under the {{{$mediaserver}}} folder.
  # Running - go to {{{ $mediaserver/bootstrap/target/mms-server/bin/ }}} folder and run run.sh or run.bat depending on OS.
  # Before running the TCK, check the JSR 309 implementation signature. Run the following from  {{{$mediaserver/jsr-309-tck}}}:
    {{{java -cp deps/mscontrol.jar:coverage/sigtest.jar:tck.jar com.sun.tdk.signaturetest.SignatureTest -apiVersion V1.0 -FileName coverage/jsr309_api.sig}}}
    * Success is indicated by "STATUS:Passed".
  # Configure the JSR 309 TCK:
    The JSR 309 TCK is located in $mediaserver/jsr-309-tck folder. You will have to change 2 files : 
    * mixeradaptertest.properties
    * TCK.properties  
    In both of them replace file:///opt/mobsource/media/ with the value of $mediaserver.
  # After these configuration changes run from the same folder $mediaserver/jsr-309-tck:
    {{{ant -f build.xml}}}
    * Test report will be generated in {{{tck-reports/<date_time>/junit-noframes.html}}}
  # Configuration notes.
  Under bootstrap/target/mms-server.dir/deploy you have server-beans.xml.
  You can set the following items :
    * MGCP Transactions Pool size : under MGCP bean you have pool size. This property defines number of mgcp transactions that can be handled simultaniously ( in 20-40ms timeframe ).Higher load means more packets need to be handled , so this number may be incremented.
    * Endpoints : number of endpoints for each type can be configured by changing name pattern.If you need 50 endpoints set [1..50] instead of values currently set.Name of endpoints can be changed in name patterns also.
    * rtp connections pool size and local connectios pool size : you can configure how much connections each endpoint type can handle.Local Connection is used to connect 2 endpoints locally.Rtp Connection is used to create rtp connection to client.

Current configuration comes with predefined values optimized for tck tests.

Memory limitations : Default configuration comes with 256MB min and 512MB max.If you will increase number of endpoints/max connections allowed per endpoint high enough server may stuck in time of loading endpoints.You can increase the memory limits by changing one of the following: if you are running windows change following line in run.bat :

set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m.

Xms is minimum memory size , where Xmx is maximum memory.

if you are running linux change following line in run.sh :

JAVA_OPTS="$JAVA_OPTS -Xms256m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"

Both files are located in bootstrap/target/mms-server.dir/bin folder. If you are planning to modify source code and compile it several times you can make same changes in bootstrap/src/main/config/ folder for all 3 files ( run.sh,run.bat and server-beans.xml