mobicents summit 2012 - yulian oifa - mobicents media server 3
Post on 14-Jun-2015
665 Views
Preview:
TRANSCRIPT
MMS 3.0.0
Structure and logic
1. Abstract View
How should mms structure look
Single Unit
Each logical unit allows zero or more inputs and zero or more outputs
Complete
MMS allows to get data from several units , modify it in some way , and send it to same units
Basic ElementsBasic elements allow to build lego-like media pathes
Abstract Source + Sink pair
To allow connection for 2 logical units we need to define sender on one and receiver on second
Compound Input
Compound Input is a special receiver ( sink ) and is part of core logic element
Compound Output
Compound Output is special sender ( source ) and is part of core logic element
Compound Component
Group of all compound inputs and outputs that belongs to same component
Compound ComponentsComponents that are defined in mms 3.0.0
Rtp Data Channel
Used to allow remote connection ( rtp , over udp ) to mms
Local Data Channel
Used to allow connection between 2 compound components that belongs to different paths
SS7 Data Channel
Allows connection to single slot of E1/T1
Media Group
Media group allows connection of all local resources available
Core Elements
Different logic available on MMS 3.0.0
Compound Mixer
Mixes data from all compound components.
Then generates output for same components by substracting data from each component from summary
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
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 )
ControlsProtocols/Standarts currently available for control function of MMS
MGCP
Well known popular protocol , allows basic control over media path
Development of protocols stopped a long time ago , therefore standart is very old
JSR 309
JSR 309 is more abstract allowing better media path control
MGCP Endpoints
Endpoints available on MMS 3.0.0
Announcement Endpoint
Based on Compound Mixer
Allows both rtp and local channels
Player only is accesible from media group
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
Conference Endpoint
Based on Compound Mixer
Allows both rtp and local channels
No resources are available from media group
Packet Relay
Based on Compound Mixer
Allows rtp connections only
No resources are available from media group
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
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
JSR 309
Status and future planning
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
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
Native JSR 309
Vxml Support should be added
Driver should be rewritten to allow new structure
Planned in 6 to 8 months from now
What ElseModules / units planned for development
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
Codecs support
ILBC codec support
GSM EFR for better GSM network support
SILK\OPUS to allow communication to skype
Fax support ( T.38 )
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
Video support
Basic video
Video conferencing
SS7 video
top related