Hi, Agalya!
I've just written an article about dimensioning OpenSIPS memory on the
OpenSIPS blog[1]. Perhaps that can help you.
To do further debugging, you should add some thresholds warnings to
determine what function spends most of the time processing. You can do
this by using msg
I've just posted a new article[1] on the OpenSIPS blog[2] that talks
about OpenSIPS memory usage: understanding memory internals and
explaining how you can dimension your OpenSIPS installation to support
your customers and the services you offer. I hope this will be useful
for some of you.
I just added modparam("sipcapture", "hep_capture_on", 1) and its not
crashing anymore but now my syslog gets flooded with the following error
WARNING:sipcapture:w_sip_capture: not a hep message!
On Thu, Dec 29, 2016 at 3:34 PM, Schneur Rosenberg wrote:
> I'm trying
I'm trying to use Homer on OpenSIPS 2.2 and when I call sip_capture() the
system crashes without creating a dump and this is what I find in my syslog
file
Dec 29 08:28:52 sip /sbin/opensips[15524]: CRITICAL:sipcapture:ip_addr2a:
unknown address family 825112372
Dec 29 08:28:52 sip
I'll be more specific
I'm running the opensips application inside a docker container.
The configuration of the listener is
listen=tls:eth0:5061 as test.communitake.com:5063
and I also have the following configurations
advertised_address=test.communitake.com
advertised_port=5063
the contact