Re: [OpenSIPS-Users] Potential memory leak in siptrace module

2018-02-01 Thread Bogdan-Andrei Iancu
Hi Steve, Thank you for your report. Could you provide the exact revision of your OpenSIPS (opensips -V) ? Also what requests are you calling the sip_trace() for (INVITES ? PUBLISH? all?) and what are the input paramters ? Thanks, Bogdan-Andrei Iancu OpenSIPS Founder and Developer

Re: [OpenSIPS-Users] I have some doubts on contact fix in opensips-1.11 .

2018-02-01 Thread SamyGo
:D @ Bogdan. Good one. On Wed, Jan 31, 2018 at 10:51 AM, Bogdan-Andrei Iancu wrote: > Hi Sasmita, > > Of course it fixes only the first contact - afterall the function is > called fix_contact() and not fix_contactS() > > But please ignore me, this was a silly joke :D.. > >

Re: [OpenSIPS-Users] Handling 488 on a leg B

2018-02-01 Thread Dmitry
Hello Bogdan, Thank you for advice. I catched 488 and can send INVITE from failure_route, but I can’t modify body inside it. The main goal is change SAVP profile to AVP when 488 received. I tried to do it via rtpengine_offer function. It doesn’t work. I guess, it try to read the body from

Re: [OpenSIPS-Users] Potential memory leak in siptrace module

2018-02-01 Thread Steve Brisson
Hi, In answer to your questions... 1. $ opensips -V version: opensips 2.3.2 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535

Re: [OpenSIPS-Users] Handling 488 on a leg B

2018-02-01 Thread Bogdan-Andrei Iancu
Hi Dmitry, In failure route you re-process the original request (INVITE) and not the 488 reply - the reply is just the trigger. Do you change the INVITE SDP before the first attempt (which ends with 488) ? Or you change it for the first time in the failure route ? Regards, Bogdan-Andrei

Re: [OpenSIPS-Users] user location in mongodb

2018-02-01 Thread Liviu Chircu
Hi Jayesh, Absolutely yes! In fact, MongoDB is currently the only supported NoSQL backend to work with usrloc! The idea is that its document-oriented representation of data makes it easy to equivalate to an SQL backend, hence Vlad wrote the "db_cachedb" NoSQL -> SQL translation interface and