Hello,
from kamailio point of view, the only major component relying on system
memory is the MI/RPC framework/commands. Otherwise, likely to be an
external library.
Cheers,
Daniel
On 19/10/16 11:46, Vasiliy Ganchev wrote:
> Hi Daniel!
>
> Thanks for the pointing out!
>
> Currently re-checking
Hi Daniel!
Thanks for the pointing out!
Currently re-checking system memory usage and monit behavior.
Will report results later (seems that there is nothing to be done on the
kamailio's point of view)
Cheers!
--
View this message in context:
http://sip-router.1086192.n5.nabble.com/memory-i
Hello,
double checking to see if you looked at:
-
https://www.kamailio.org/wiki/tutorials/troubleshooting/memory#os_memory_reports
Are you using http queries (curl library)?
Cheers,
Daniel
On 18/10/16 16:39, Vasiliy Ganchev wrote:
> Hi folk!
> Have a production server
> - used as webrtc to
Hi folk!
Have a production server
- used as webrtc to sip proxy
- it is built on kamailio v 4.4.2
- Server handles connections from ~4000 incoming SIP trunks (transport=TLS).
Kamailio provides auth for this trunks.
- Kamailio receives also connections from Webrtc app. Calls from Webrtc
routed to on