Re: [OpenSIPStack] Question Regarding opening the RTP sockets in openSBC.

[Joegen E. B. <joe...@gm...>]

Yes currently this is a limitation.  OpenSBC utilizes two threads per 
connection for the RTP proxy.    Media aggregation allows you to use a 
finite set of threads to handle multiple number of rtp sessions.     
Media aggregation code is incomplete and has never been tested.

Ashish Khare wrote:
> Hi joegen,
> Sorry for clarifying once again.
> As of now openSBC is limited by the number of threads, the system can have,
> in handling the RTP streams, as 2 threads are needed for  one RTP session.
> Please reply.
>
> -Ashish
>
>
> On 8/21/07, Joegen E. Baclor <joe...@gm...> wrote:
>   
>> That is TRUE.   If you check the Media Interface handler...  there are
>> inactive code there that pertains to media aggregation.   This code
>> allows for the RTP streams to be aggregated by a limited number of
>> threads which will allow OpenSBC to just be limited by the CPU in terms
>> of max concurrency.   However, the OpenSBC team does not have time right
>> now to revisit this "incomplete" segment.  Feel free to work on this
>> code and send back your patches.
>>
>> Ashish Khare wrote:
>>     
>>> Hi Joegen,
>>>
>>> Thanks for the reply.
>>> But if this is the case, then concurrent media sessions is
>>>       
>> not  restricted
>>     
>>> to the maximun number
>>> of threads the system / machine can have.
>>> How can we scale the system to accomodate lets say 1 million subscriber
>>> which can lead to 1 million media sessions concurrently?
>>>
>>> Thanks,
>>> Ashish
>>>
>>> On 8/21/07, Joegen E. Baclor <joe...@gm...> wrote:
>>>
>>>       
>>>> Ashish Khare wrote:
>>>>
>>>>         
>>>>> Hi,
>>>>>
>>>>> I have a question regarding the opening of RTP sockets in the openSBC.
>>>>> When openSBC recieved the INVITE request, it creates the new rtp/rtcp
>>>>> sockets for that leg in the new thread.
>>>>> Similarly when openSBC sends the outgoing INVITE in the same Call
>>>>> session, it creates another new rtp/rtcp sockets for the call leg 2 in
>>>>> the new thread instance.
>>>>> So altogether 2 threads are there for one call between 2 parties to
>>>>> handle RTP/RTCP packets.
>>>>> Then if there are N * 2 subscribers are talking to each other, then it
>>>>> means there are N * 2 threads handling the RTP streams.
>>>>> is my understanding correct?
>>>>>
>>>>>
>>>>>
>>>>>           
>>>> yes.
>>>>
>>>>
>>>>         
>> -------------------------------------------------------------------------
>>     
>>> This SF.net email is sponsored by: Splunk Inc.
>>> Still grepping through log files to find problems?  Stop.
>>> Now Search log events and configuration files using AJAX and a browser.
>>> Download your FREE copy of Splunk now >>  http://get.splunk.com/
>>> _______________________________________________
>>> opensipstack-devel mailing list
>>> ope...@li...
>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>
>>>
>>>
>>>       
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems?  Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >>  http://get.splunk.com/
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>
>>     
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
>