11 Mar
2013
11 Mar
'13
8:32 a.m.
For sake of completion, I wanted to add that for tcp traffic is a load
balancing distribution of connections over tcp receive workers -- the
worker with least number of assigned connection will take next one, a
connection being assigned to a worker when there is traffic on it.
Besides this, one may build kind of own scheduling in processing via
mqueue and timer, together using t_suspend()/t_continue(), although is
more easy for to do distributing for particular processing, than setting
priorities of processing.
Cheers,
Daniel
On 3/5/13 4:13 PM, Jiri Kuthan wrote:
On 3/5/13 2:36 PM, irma zujovic wrote:
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, April 16-17, 2013, Berlin
- http://conference.kamailio.com -
Hello,
I am using FOKUS IMS Core open source platform, and trying to
investigate scheduling and queuing inside IMS. FOKUS IMS uses SER.
My question is : where inside SER configuration scripts, the
*scheduling * and *queueing *of SIP messages is done? I am interested
in a special function or part
of the written program.
this is not done in SER, it is done in kernel. kernel dispatches
incoming traffic to
one of multiple processes listening on sockets. Same for outgoing
traffic -- SER leaves
it to kernel's decision.
jiri
I hope that engineers that worked on developing of SER could help me
with this issue.
Thank you in advance
Irma
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users