Re: [OpenSIPS-Devel] Full Sharing N Contact Pings problem

2019-01-18 Thread John Quick
Hi Liviu, Yes, adding the parameter line: modparam("usrloc", "shared_pinging", 1) to all three nodes has fixed the problem. So it looks like it was just the default setting was 0, not 1. Thanks. John Quick Smartvox Limited Web

[OpenSIPS-Devel] Full Sharing N Contact Pings problem

2019-01-11 Thread John Quick
umentation so I assume this is a bug. John Quick Smartvox Limited The topology/architecture I am using is an edge proxy in front of a 3-node cluster to handle registrations, NAT pings and call routing, using path headers. For reference, here are some code snippets from the opensips.cfg file on o

Re: [OpenSIPS-Devel] siptrace hep "hit a programming bug"

2017-03-15 Thread John Quick
Humble pie time. My excuse is that I was fooled by the lag time before the Homer dashboard updated with the new data. Now it is working using UDP. Thanks. John Quick Smartvox Limited Tel: 01727-221221 -Original Message- From: Ionut Ionita [mailto:ionution...@opensips.org] Sent: 15

Re: [OpenSIPS-Devel] siptrace hep "hit a programming bug"

2017-03-15 Thread John Quick
Ionut, Sorry, Hold fire on that last email please. I just found that Kamailio is not listening on tcp. I will go back to udp and report what happens. John Quick Smartvox Limited Tel: 01727-221221 -Original Message- From: Ionut Ionita [mailto:ionution...@opensips.org] Sent: 15 March

Re: [OpenSIPS-Devel] siptrace hep "hit a programming bug"

2017-03-15 Thread John Quick
t want to have to upgrade). The capture node did receive some traffic from my test server, but nothing appeared on the homer dashboard. Here is the iptables output for the listening port 9060 on the server at xx.yy.zz.234: ]# iptables -L -nv | grep 9060 0 0 ACCEPT udp -- * *

[OpenSIPS-Devel] siptrace hep "hit a programming bug"

2017-03-14 Thread John Quick
h is not init!#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues 2017-03-14 09:32:13 ERROR:siptrace:trace_send_hep_duplicate: cannot send duplicate message 2017-03-14 09:32:13

Re: [OpenSIPS-Devel] Memory leak in DR module, I think

2016-12-16 Thread John Quick
Glad I could be of help. Please could you email me the diff on that file, routing.c, so I can fix it on my proxy servers. Thanks. John Quick -Original Message- From: Devel [mailto:devel-boun...@lists.opensips.org] On Behalf Of Liviu Chircu Sent: 16 December 2016 14:42 To: devel

[OpenSIPS-Devel] Memory leak in DR module, I think

2016-12-16 Thread John Quick
0c0c0c0c0c0c0c0, abcdefedabcdefed I use the DR module to select a route for calls through this proxy. The memory leak is fastest when there are lots of calls during the day, then it is slow at night. OpenSIPS Version 2.1.4 John Quick Smartvox Limited Web: www

[OpenSIPS-Devel] Finding a memory leak

2016-12-15 Thread John Quick
ases where the value for "frag size" exceeds 240. The line that starts "alloc'd from" never seems to have a value in parentheses exceeding 4480. I cannot see anything that looks like a smoking gun. The list never goes beyond