[Freeswitch-users] FS as Media Gateway Only

[David Ponzone]

I don't think that's possible at the moment.
You can still deploy several boxes which will do SIP+RTP but I agree  
this is not the same thing.

David Ponzone  Direction Technique
email: david.ponzone at ipeva.fr
tel:      01 74 03 18 97
gsm:   06 66 98 76 34

Service Client IPeva
tel:      0811 46 26 26
www.ipeva.fr  -   www.ipeva-studio.com

Ce message et toutes les pièces jointes sont confidentiels et établis  
à l'intention exclusive de ses destinataires. Toute utilisation ou  
diffusion non autorisée est interdite. Tout message électronique est  
susceptible d'altération. IPeva décline toute responsabilité au titre  
de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes  
pas destinataire de ce message, merci de le détruire immédiatement et  
d'avertir l'expéditeur.




Le 27/05/2010 à 04:01, Code Ghar a écrit :

> Is it possible -- and are there any case studies, practical  
> experience, etc -- on deploying FreeSWITCH (FS) in this  
> architecture: one server (FSSIP) handles SIP signaling only, and  
> multiple servers (FSRTP1, FSRTP2, ..., FSRTPn) handle all media  
> responsibilities? So when a call comes in, the SDP contains IP of,  
> say FSRTP1, as media handler. For this to work, FSSIP would request  
> FSRTPx for media resources for each new call and add its IP and port  
> in SDP. The media servers/gateways would play IVR, etc.; collect  
> DTMF and forward as appropriate to FSSIP; perform transcoding; etc.;  
> all while FSSIP only deals with signaling. This way multiple servers  
> could be deployed to handle media responsibilities and only a  
> handful would be required for signaling. In future if there's a  
> greater need for transcoding, etc. all you need to do is deploy a  
> media server and not have to add servers for signaling.
>
> This idea came to me because I have come across two proprietary  
> applications that do it this way. They have a SIP component and a  
> media component. You can run both on the same physical machine or  
> you can separate them out into multiple machines.
>
> Another way for this could be to integrate FS as a media component  
> to another application's SIP component. A mix-and-match, so to speak.
>
> On the flip side, deploy FS as a SIP server and use media  
> capabilities of some other hardware or software application. For  
> example, FS handles signaling and use dedicated hardware for media.  
> A good example of this is illustrated (somewhat) by an image on  
> Sangoma's website: http://www.sangoma.com/assets/images/content/transcoding_diagram.jpg 
> . Look at the "pooled transcoding".
>
> Is FS even designed to be this modular? If so, how can the  
> aforementioned scenario(s) be achieved?
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20100527/734faf84/attachment.html