Thank you very much, Răzvan;
We are using the compression module for mc_compact(). We use SIP
headers for passing around data (don't ask) and the compact headers
are mandatory or else we hit MTU/fragmentation problems. We're on the
cusp of moving to SIP/TCP but haven't gotten there quite yet.
The
Got it!
Thanks
On Fri, Sep 21, 2018 at 6:12 AM Bogdan-Andrei Iancu
wrote:
> Hi Daniel,
>
> OK, so you want to get the parameter into the local route (when the calls
> are sent out). Right now, the out of the box solution is what you already
> did - put the scenario parameters into RURI so you c
Bogdan,
Yes, as per the script example I provided originally I am arming failure_route
always in local_route and setting the acc_extra variable in failure_route. Even
in the case where the first BYE response is a failure, the acc_extra variable
is not being set. This seems to indicate the dialo
On 20 Sep 2018, at 20:19, Dan Pascu wrote:
>
> On 20 Sep 2018, at 19:08, Bogdan-Andrei Iancu wrote:
>
>> Hi Dan,
>>
>> Please report this on the GitHub tracker ; in addition - is the crash
>> reproducible , have you identified the faulty xlog() in your script ? is all
>> the time the same ?
After I started to test the lastest git code from master I noticed errors like
this in my logs:
Sep 21 13:01:41 node03 /usr/sbin/opensips[22838]:
CRITICAL:db_mysql:wrapper_single_mysql_real_query: driver error (1062):
Duplicate entry 'dan-test.sip2sip.info-presence-a.1537527127.22838.2.1' for
On 21 Sep 2018, at 12:48, Bogdan-Andrei Iancu wrote:
> Dan,
>
> For the delay warnings, that's what the code does - it checks time difference
> (internal ticker) between writing and reading from a pipe. If you there is no
> load (to prevent the workers to read from the pipe), the only delay ma
Hi Bogdan,
Not in this server, But I'll try run on a bare-metal server and see if there's
a change.
On Friday, 21 September 2018, 3:22:20 PM GMT+5:30, Bogdan-Andrei Iancu
wrote:
Hi Pasan,
Are you able to run (just for testing purposes) opensips directly on the host
machine? I ju
Hi Pasan,
Are you able to run (just for testing purposes) opensips directly on the
host machine? I just trying to see if the difference will impact.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Bootcamp 2018
http://opensips.org/tr
Dan,
For the delay warnings, that's what the code does - it checks time
difference (internal ticker) between writing and reading from a pipe. If
you there is no load (to prevent the workers to read from the pipe), the
only delay may come from the actual pipe communication. Why the delay,
not
Discussion continued here https://github.com/OpenSIPS/opensips/issues/1472
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Bootcamp 2018
http://opensips.org/training/OpenSIPS_Bootcamp_2018/
On 09/20/2018 08:19 PM, Dan Pascu wrote:
On
Hi Ben,
The Dialog is not terminated (as status) with the first successful BYE
reply, but with the first reply (whatever the status is). Even if
bothcaller and callee BYEwill turn into 408 or 481, the first to fire
will terminate the dialog session. But you say that if failure_route is
trigge
Hi Daniel,
OK, so you want to get the parameter into the local route (when the
calls are sent out). Right now, the out of the box solution is what you
already did - put the scenario parameters into RURI so you can extract
them in the local route.
This is ugly, let me think of a better solution
Hi, Jock!
I think you are actually heating two memory leaks: one in private memory
and one in shared memory.
In the memory dump you sent I can spot a pkg mem related to (I believe)
the compression module. Can you tell me what functions of the
compression module you are using and what flags are
13 matches
Mail list logo