Hello,
We are facing an issue with multi-leg support in acc module. Actually we
have more than 40 leg_fields in our CDRs. Opensips crashes when we started
with these many fields. It supports up to some number of leg_fields. Can
anyone help me out to solve this issue?
version: opensips 2.4.6 (x86_
Thank you guys. It's working now.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
On 23.01.2020 17:42, Liviu Chircu wrote:
will look into it asap!
This is now fixed, according to [1]. Thank you for the help, Vitalii!
[1]: https://github.com/OpenSIPS/opensips/commit/c2e0603331a
Best regards,
--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIP
On 23.01.2020 17:16, Vitalii Aleksandrov wrote:
Will return it back to broken version and send you the pcap. Do you
want me to put some additional logs into replace.c?
Just pcap is more than fine, thanks!
P.S. FYI, also found a crash in tm that is reproduced under high load.
Will create a git
I use uac_replace_from(). uac_replace_to() is not used at all.
"replace_mode" is not set, so must be "auto" by default.
I also use "dialog" module and spiral calls where external call leg uses
TLS and internal (spiral) works over UDP.
Checked it once again with the latest 2.4 + my patches and e
On 23.01.2020 15:55, Vitalii Aleksandrov wrote:
I never had broken To uri before and now can easily reproduce it.
Also, what "restore_mode" are you using? I did a lot of tests with
"auto" (default),
maybe I broke some other one.
--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-sol
On 23.01.2020 15:55, Vitalii Aleksandrov wrote:
After updating my proxy from the latest 2.4 repository I've got a new
problem with "To" header uri.
Somehow opensips received BYE with correct "To" uri and forwards it
with an URI without "<>".
Checked latest commits and this one:
> commit de76
After updating my proxy from the latest 2.4 repository I've got a new
problem with "To" header uri.
Somehow opensips received BYE with correct "To" uri and forwards it with
an URI without "<>".
Checked latest commits and this one:
> commit de7606dfb2deeb0ebb07e329511164b784970e6c
> Author: Li
Thank you Bogdan,
Will be nice to have NSS certificate management in mix.
volga629
Sent from mobile device typos are expected.
> On Jan 23, 2020, at 08:34, Bogdan-Andrei Iancu wrote:
>
>
> There is no doubt about the danger and security threats presented by the
> robocalls or identity thie
There is no doubt about the danger and security threats presented by the
robocalls or identity thieves. Also there is no doubt that STIR/SHAKEN
is the solution that addresses the threats.
And starting with 3.1 OpenSIPS provides a very flexible implementation
for STIR/SHAKEN, for any operator
Hello to you all!
I am pleased to announce you that we will make two more stable minor
releases next week. I'm talking about OpenSIPS 2.4.7 and 3.0.2.
These new releases will contain several bug fixes (more than 150
commits), the headline being the notorious OpenSSL fix for the TLS
connectio
Hi Ali,
Glad the suggestions were helpful.
The certificate is just a regular SSL cert, in PEM format just with a
different file extension. Depending on your implementation you might want
to look into public verifiable certificates (if you're public facing) -
available for free if you want to chec
12 matches
Mail list logo
