Mobicents Summit 2012 - Yulian Oifa - Mobicents Media Server 3

949 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
949
On SlideShare
0
From Embeds
0
Number of Embeds
22
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Mobicents Summit 2012 - Yulian Oifa - Mobicents Media Server 3

  1. 1. MMS 3.0.0Structure and logic
  2. 2. 1. Abstract ViewHow should mms structure look
  3. 3. Single Unit Each logical unit allows zero or more inputs and zero or more outputs
  4. 4. Complete MMS allows to get data from several units , modify it in some way , and send it to same units
  5. 5. Basic ElementsBasic elements allow to build lego-like media pathes
  6. 6. Abstract Source + Sink pair To allow connection for 2 logical units we need to define sender on one and receiver on second
  7. 7. Compound Input Compound Input is a special receiver ( sink ) and is part of core logic element
  8. 8. Compound Output Compound Output is special sender ( source ) and is part of core logic element
  9. 9. Compound Component Group of all compound inputs and outputs that belongs to same component
  10. 10. CompoundComponentsComponents that are defined in mms 3.0.0
  11. 11. Rtp Data Channel Used to allow remote connection ( rtp , over udp ) to mms
  12. 12. Local Data Channel Used to allow connection between 2 compound components that belongs to different paths
  13. 13. SS7 Data Channel Allows connection to single slot of E1/T1
  14. 14. Media Group Media group allows connection of all local resources available
  15. 15. Core ElementsDifferent logic available on MMS 3.0.0
  16. 16. Compound Mixer Mixes data from all compound components. Then generates output for same components by substracting data from each component from summary
  17. 17. Compound Splitter Defines 2 groups of components Mixes data from group 1 and sends it to all components in group 2 Mixes data from group 2 and sends it to all components in group 1
  18. 18. Resources Pool Starting from 3.0.0 there is no resources preallocated to any type of endpoint Global Element called Resources pool stores preloaded Rtp Channels , Local Channels , Players , Dtmf Detectors , Records , etc Memory usage is minimized Component usage is maximized ( much less components are waiting for their usage )
  19. 19. ControlsProtocols/Standarts currently available for controlfunction of MMS
  20. 20. MGCP Well known popular protocol , allows basic control over media path Development of protocols stopped a long time ago , therefore standart is very old
  21. 21. JSR 309 JSR 309 is more abstract allowing better media path control
  22. 22. MGCP EndpointsEndpoints available on MMS 3.0.0
  23. 23. Announcement Endpoint Based on Compound Mixer Allows both rtp and local channels Player only is accesible from media group
  24. 24. IVR Endpoint Based on Compound Mixer Allows both rtp and local channels Player , Recorder , Dtmf Detector , Dtmf Generator ( not accessible through mgcp ) are accessible from media group
  25. 25. Conference Endpoint Based on Compound Mixer Allows both rtp and local channels No resources are available from media group
  26. 26. Packet Relay Based on Compound Mixer Allows rtp connections only No resources are available from media group
  27. 27. Local to Remote Bridge Based on Compound Splitter. Group 1 – Local Connections Group 2 – Remote connections Allows both rtp and local data channels No resources are avaiable from media group
  28. 28. DS0 Endpoint Based on Compound Splitter Has one ss7 data channel Group 1 – ss7 data channel Group 2 – local and remote data channels + media group Both local and remote connections are avaiable Signal Detector and Signal generator are available from media group
  29. 29. JSR 309Status and future planning
  30. 30. Current Currently JSR 309 is implemented over MGCP Starting from 3.0.0 all of JSR 309 components are native components of MMS Only Vxml Dialog should be added to allow full functionallity
  31. 31. Why is it required MGCP is not customizable , therefore SS7 video support for example is hard to implement.Resource usage will be too great to use solution in production JSR does not defines predefined structure of endpoints , therefore allows more freedom in media path Restcomm like application are natively build on vxml , in case of jsr 309 they will talk a same language
  32. 32. Native JSR 309 Vxml Support should be added Driver should be rewritten to allow new structure Planned in 6 to 8 months from now
  33. 33. What ElseModules / units planned for development
  34. 34. Massive perfomance test/optimization No load test where done till now therefore its not clear number of maximum connections mms is avalaible to accept No optimization where done especially in transcoding
  35. 35. Codecs support ILBC codec support GSM EFR for better GSM network support SILKOPUS to allow communication to skype Fax support ( T.38 )
  36. 36. Config/Management Currently text based , to change config restart is required Perfomance / usage data accesible only from log SNMP support is planned Cassandra / Mongo db for configuration / logging External management / configuration unit
  37. 37. Video support Basic video Video conferencing SS7 video

×