Generally you can monitor for this with: netstat -nlp|grep opensips but I suspect you are already doing something similar. The statistics module also has a similar statistics. The command: opensipsctl fifo get_statistics all
If you look near the bottom, you'll see the load in percent of the children for each listening interface. It looks like this: load:udp:1.2.3.4:5060-load = 18 ie: 1.2.3.4 is 18% busy. If this number reaches 100, your children are no longer capable of responding to UDP packets on that interface and the kernel will begin to queue if possible. -Brett On Tue, Oct 7, 2014 at 8:58 AM, Vandan Joshi <vandan.jo...@panamaxil.com> wrote: > Dear Bogdan, > > I am using opensips-1.6 on CentOS-5.8. > In certain conditions I am seeing lot of packets queued in recv queue and > not getting processed. > I am monitoring the same using "netstat" command. > While observing the siptrace I found, opensips couldn't reply to incoming > msgs, and if replied, it replies very late. > > What sort of params I should observe/optimize to handle this kinda > situation(when getting very high traffic on switch) ?? > thnx > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users