Greetings OpenSIPS gurus;
I've run into an issue that I'm not making any real headway with on my
own. I have an OpenSIPS 2.4.2 running on CentOS7 that does not appear
to be releasing the bulk of its shared memory when calls die off.
Eventually OpenSIPS runs itself out of shared memory and goes
Hi Bogdan
I'm triggering the script via MI. The idea is to send some parameter with
the MI parameters and use this as a variable on localroute.
For example, a dialer place call to B destination, after answer, place call
to A destination, then bridge.
On B side, i need to store on DB the
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 ?
It happened multiple times, but I cannot reproduce it
On 20 Sep 2018, at 19:06, Bogdan-Andrei Iancu wrote:
> Hi Dan,
>
> Copying from my previous reply to Pasan:
>
>
> "If there is no load (worker processes are idle, no busy with anything else),
> the reported delay may be generated only by the interprocess communication
> (passing the job
On 20 Sep 2018, at 19:04, Bogdan-Andrei Iancu wrote:
> Hi Dan,
>
> Please report this on the GitHub tracker ; in addition - is the crash
> reproducible ?
It happened multiple times, but I do not have a way to reproduce it at will.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder
Hi Bogdan,
Nice to here from you :) Thank for clarifying about the warning. My delay times
are only vary between 4 us - 5 us. I got 6 vCPUs allocated to my kvm
guest , host machine has 16 cores in total. I wondered if these are related to
guest CPU stealing as I get 0.02% of max cpu
Hi Dan,
Copying from my previous reply to Pasan:
"If there is no load (worker processes are idle, no busy with anything
else), the reported delay may be generated only by the interprocess
communication (passing the job from the triggering process to the
executing process via internal
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 ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Bootcamp
Hi Dan,
Please report this on the GitHub tracker ; in addition - is the crash
reproducible ?
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 05:15 PM,
Here is another crash that happened multiple times:
Core was generated by `/usr/sbin/opensips -w /run/opensips -P opensips.pid -m
512'.
Program terminated with signal SIGABRT, Aborted.
#0 0xb770ccf9 in __kernel_vsyscall ()
(gdb) bt
#0 0xb770ccf9 in __kernel_vsyscall ()
#1 0xb7546dd0 in
Bogdan,
This is a good point and I did consider that. However, this only makes sense in
the case where there is a successful response prior to the error response. As I
noted I have seen this occur when both parties reply to the BYE with a 481
response. If the Dialog and ACC modules were
Hi Pasan,
That warning (harmless in 99% of the cases) reports the delays between
(a) triggering a timer job in timer processes and (b) executing that
timer job in a worker process.
If there is no load (worker processes are idle, no busy with anything
else), the reported delay may be
On 20 Sep 2018, at 18:19, Pasan Meemaduma via Users wrote:
> Hi Dan,
>
> I'm experiencing same on 2.3.5 as per my initial email. still couldn't find
> out the exact reason. btw are you using a virtualise environment ?
No
--
Dan
___
Users
Hi Daniel,
Could you detail a bit on the flow of this customer related value ?
where does is originate (when triggering the b2b script via MI?) and
where do you want to get it ?
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS
Hi Ravi,
why do you say the remove_hf() doesn't work ? do you still see the
incoming Route hdr in the outbound message ??
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Bootcamp 2018
Hi Ben,
The issue is a bit more complex. When generating the BYE requests, the
dialog module triggers the event of call terminated when it gets back
the first final reply (to any of the BYEs). And ACC module generates the
CDR when the dialog is terminated.
So, the second BYE (which probably
Hi Dan,
I'm experiencing same on 2.3.5 as per my initial email. still couldn't find out
the exact reason. btw are you using a virtualise environment ?
On Thursday, 20 September 2018, 7:35:28 PM GMT+5:30, Dan Pascu
wrote:
Here is a follow up on this problem. I started to use the
Thanks for the reply Liviu, let me know if I can do anything to help, this
is a dev environment so I can try anything on it if it can be usefull.
Dominic
On Thu, Sep 20, 2018 at 10:11 AM Liviu Chircu wrote:
> Hi Dominic,
>
> The 200 OK returned by OpenSIPS should definitely contain a 120s
I got this crash (memory seems to be corrupted in src->h_addr_list[0]):
Core was generated by `/usr/sbin/opensips -w /run/opensips -P opensips.pid -m
512'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __memcpy_sse2_unaligned () at
Hi Dominic,
The 200 OK returned by OpenSIPS should definitely contain a 120s expiry
time. Thanks for the detailed explanation - I will look into this asap.
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 20.09.2018 16:29, Dominic wrote:
Hi all, I have
Here is a follow up on this problem. I started to use the system to do some
testing. I only have 1 device registered that makes some calls. I started to
notice similar type of messages, but with a slightly different pattern while
testing it. They seem to happen more often when I end the call,
Hi all, I have the following setup:
-sip device is registering to OpenSIPS setup as a mid_registrar who then
fowards registers to asterisk once they are authenticated
-OpenSIPS is setup in contact throttling mode with outgoing expires set to
3600 sec.
The scenario I came accross is the following:
22 matches
Mail list logo