Re: [OpenSIPS-Users] drouting WARNING
Hello, dr_rules has a prefix and gwlist shows cr2 ; not #cr2 ... What am I missing here? I think it is what you wrote in the comment. Carrier ids are prefixed by '#' in dr_rules. Without this prefix it use gateways directly without carriers. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] [Crash Report] Weird crash with drouting/tls_mgm/usrloc/db_postgresql
Hello volga629, Thanks to Liviu Chircu, #2161 is fixed. If you are using tls_mgm in db mode, and the Postgresql connections are limited to 1, it could be useful for you too. Thanks for your emails, you helped me to find what to search for the bug report. Regards, -- Adrien Martin signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] [Crash Report] Weird crash with drouting/tls_mgm/usrloc/db_postgresql
Hello, Ok, thanks for your explanation. Regards, -- Adrien Martin signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] [Crash Report] Weird crash with drouting/tls_mgm/usrloc/db_postgresql
Hello, I tried to reduce the number of workers to 1 with Opensips 3.1 (can not change TCP workers with 2.4+) and there is another crash about tls_domain that i have to investigate :) Our problems are somewhat different though, in this one there is no load/no calls, just some registrations (less than 5 UAC) and some drouting probing UDP and TLS. As #1579 was closed, did the commit https://github.com/OpenSIPS/opensips/commit/c1403a1d9bee2254a84a866352266a41d9ff93bc fixed your problem or did you just tweak the workers/sysctl.conf/postgresql.conf? Thanks, regards, -- Adrien Martin Le 11/08/2020 à 14:34, Slava Bendersky a écrit : > Hello Everyone, > You need tweak sysctl and postgresql.conf to allow opensips connect properly > to remote postgresql. > In opensips I can't pass for any transport udp_worker tcp_worker more then > 10. Other wise it starts segfaulting. One opensips open from 150-170 > connections to database under load when cluster of 3 nodes you need > postgresql at least 650 connection limit. If you use TCP or WSS or TLS you > need increase tcp protocol buffer on protocol level other wise it will be > bottleneck for database and it will slow down all. > > volga629 signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] [Crash Report] Weird crash with drouting/tls_mgm/usrloc/db_postgresql
Hello, Thanks for your answer. Do you mean the patch didn't resolve the issue for volga629? Anyway it's an interesting idea, this would point to a concurrency problem. Gonna try but i think it would not work because there would still be udp and tcp/tls workers at the same time. Regards, -- Adrien Martin Le 11/08/2020 à 12:00, Johan De Clercq a écrit : > I believe that 1579 was fixed by volga629 by reducing the number of workers > in opensips.cfg. signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] [Crash Report] Weird crash with drouting/tls_mgm/usrloc/db_postgresql
Hello, As i am adding some TLS gateways (drouting) to our configuration some crashes happen. The crash dump seems to show db_postgresql is reading an answer that does not match the current query (usrloc). I don't really know how to find what causes this. Does anyone have an idea how to progress on this? How to extract more from the crash dump/what to do to find the problem? Does anyone have experienced this problem? NB: https://github.com/OpenSIPS/opensips/issues/1579 seems similar but how the patch interact with the issue is not obvious to me. More information is present here: https://github.com/OpenSIPS/opensips/issues/2161. Regards, -- Adrien Martin signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] APT and YUM repositories down
Hello, It seems there is another server outage with apt and yum repositories. Regards, Adrien Martin Le 30/09/2019 à 15:34, Bogdan-Andrei Iancu a écrit : And now back online, thanks to Nick Altmann !! (some server outage) Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 9/30/19 11:06 AM, Callum Guy wrote: Hopefully just in prep for 3.0.1! On Mon, 30 Sep 2019 at 08:42, Adrien Martin mailto:a.mar...@alphalink.fr>> wrote: Hello, Both apt.opensips.org <http://apt.opensips.org> and yum.opensips.org <http://yum.opensips.org> seem down (IPv4 and IPv6). Regards, Adrien Martin ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users *^0333 332 | www.x-on.co.uk <http://www.x-on.co.uk> | _**_^<https://www.linkedin.com/company/x-on> <https://www.facebook.com/XonTel> <https://twitter.com/xonuk> * X-on is a trading name of Storacall Technology Ltd a limited company registered in England and Wales. Registered Office : Avaland House, 110 London Road, Apsley, Hemel Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient, please notify X-on immediately on +44(0)333 332 and delete the message from your computer. If you are not a named addressee you must not use, disclose, disseminate, distribute, copy, print or reply to this email. Views or opinions expressed by an individual within this email may not necessarily reflect the views of X-on or its associated companies. Although X-on routinely screens for viruses, addressees should scan this email and any attachments for viruses. X-on makes no representation or warranty as to the absence of viruses in this email or any attachments. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] APT and YUM repositories down
Thank you Nick! And thank you Bogdan for your message. Regards, Adrien Martin Le 30/09/2019 à 15:34, Bogdan-Andrei Iancu a écrit : > And now back online, thanks to Nick Altmann !! (some server outage) > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 9/30/19 11:06 AM, Callum Guy wrote: >> Hopefully just in prep for 3.0.1! >> >> On Mon, 30 Sep 2019 at 08:42, Adrien Martin > <mailto:a.mar...@alphalink.fr>> wrote: >> >> Hello, >> >> >> Both apt.opensips.org <http://apt.opensips.org> and >> yum.opensips.org <http://yum.opensips.org> seem down (IPv4 and IPv6). >> >> >> Regards, >> >> Adrien Martin >> >> ___ >> Users mailing list >> Users@lists.opensips.org <mailto:Users@lists.opensips.org> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> *^0333 332 | www.x-on.co.uk <http://www.x-on.co.uk> | >> _**_^<https://www.linkedin.com/company/x-on> >> <https://www.facebook.com/XonTel> <https://twitter.com/xonuk> * >> >> X-on is a trading name of Storacall Technology Ltd a limited company >> registered in England and Wales. >> Registered Office : Avaland House, 110 London Road, Apsley, Hemel Hempstead, >> Herts, HP3 9SD. Company Registration No. 2578478. >> The information in this e-mail is confidential and for use by the >> addressee(s) only. If you are not the intended recipient, please notify X-on >> immediately on +44(0)333 332 and delete the >> message from your computer. If you are not a named addressee you must not >> use, disclose, disseminate, distribute, copy, print or reply to this email. >> Views or opinions expressed by an individual >> within this email may not necessarily reflect the views of X-on or its >> associated companies. Although X-on routinely screens for viruses, >> addressees should scan this email and any attachments >> for viruses. X-on makes no representation or warranty as to the absence of >> viruses in this email or any attachments. >> >> >> ___ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] APT and YUM repositories down
Hello, Both apt.opensips.org and yum.opensips.org seem down (IPv4 and IPv6). Regards, Adrien Martin signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Dialog replication problems
Hello,
I backported the commit 00be97f151d254af281c4f05611c1905f51fbcde ("dialog: Fix
incorrect replicated dialog ids") from git in an Opensips 2.2.2.
opensipsctl fifo dlg_list show the same dialogs on both sides, but after
fail-over the BYE is not routed (no problem if no fail-over).
My setup use topology_hiding (with dialog), topology_hiding_match returns false.
Debug logs show the dialog is found (eg: DBG:dialog:lookup_dlg: dialog
id=1590931783 found on entry 2370).
There is difference in logs between a normal call and a fail-over call :
DBG:dialog:run_dlg_callbacks: dialog=0x7f19bfd60f20, type=32
DBG:dialog:fix_route_dialog: Fixing message. Next hop is Loose router
DBG:dialog:fix_route_dialog: Setting new URI to ...
Wich are not present when using a replicated dialog.
"ref dlg" and "unref dlg" logs do not have the same ref in both case (don't
know if relevant).
The request URI of the BYE has the Opensips in the host part, so the BYE is
routed locally because the request URI is not rewritten.
Opensips search again the same dialog but does not find it at this moment.
Regards,
--
Adrien Martin
On 03/11/2016 11:27, Liviu Chircu wrote:
> Hi, Dawid!
>
> I have looked into the problem and also managed to come up with a fix! Could
> you please go to your OpenSIPS 2.2 source code directory, apply the below
> patch, recompile the dialog module and see if it fixes the problem?
>
> git apply <(base64 -d < ZGlmZiAtLWdpdCBhL21vZHVsZXMvZGlhbG9nL2RsZ19yZXBsaWNhdGlvbi5jIGIvbW9kdWxlcy9k
> aWFsb2cvZGxnX3JlcGxpY2F0aW9uLmMKaW5kZXggYTg0NTVhZi4uZGE2MmRiNiAxMDA2NDQKLS0t
> IGEvbW9kdWxlcy9kaWFsb2cvZGxnX3JlcGxpY2F0aW9uLmMKKysrIGIvbW9kdWxlcy9kaWFsb2cv
> ZGxnX3JlcGxpY2F0aW9uLmMKQEAgLTE4Miw3ICsxODIsNiBAQCBpbnQgZGxnX3JlcGxpY2F0ZWRf
> Y3JlYXRlKHN0cnVjdCBkbGdfY2VsbCAqY2VsbCwgc3RyICpmdGFnLCBzdHIgKnR0YWcsIGludCBz
> YWZlKQogCWRsZy0+bGVnc19ub1tETEdfTEVHXzIwME9LXSA9IERMR19GSVJTVF9DQUxMRUVfTEVH
> OwogCiAJLyogbGluayB0aGUgZGlhbG9nIGludG8gdGhlIGhhc2ggKi8KLQlkbGctPmhfaWQgPSBk
> X2VudHJ5LT5uZXh0X2lkKys7CiAJaWYgKCFkX2VudHJ5LT5maXJzdCkKIAkJZF9lbnRyeS0+Zmly
> c3QgPSBkX2VudHJ5LT5sYXN0ID0gZGxnOwogCWVsc2Ugewo=
> EOF
> )
>
> Liviu Chircu
> OpenSIPS Developer
> http://www.opensips-solutions.com
signature.asc
Description: OpenPGP digital signature
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Topology hiding and Route header
Hello,
Thank you for the clarification, yes it was about a pre-loaded Route header.
Regards,
--
Adrien Martin
On 06/01/2017 14:01, Răzvan Crainea wrote:
> Hi, Adrien!
>
> If you are talking about a pre-loaded Route header (received from the client)
> for an initial INVITE, then the topology_hiding() module does not remove it
> and you have to remove it yourself.
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Solutions
> www.opensips-solutions.com
>
> On 01/06/2017 02:44 PM, Adrien Martin wrote:
>> Hello,
>>
>> I'm using the module topology_hiding with Opensips 2.2 but I'm not sure to
>> understand properly the documentation.
>>
>> Is the header Route supposed to be removed ? (No problem removing and
>> restoring Record-Route)
>> In my tests Route header was not removed unless I added remove_hf("Route")
>> after topology_hiding.
>>
>> Regards,
>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
signature.asc
Description: OpenPGP digital signature
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Topology hiding and Route header
Hello,
I'm using the module topology_hiding with Opensips 2.2 but I'm not sure to
understand properly the documentation.
Is the header Route supposed to be removed ? (No problem removing and restoring
Record-Route)
In my tests Route header was not removed unless I added remove_hf("Route")
after topology_hiding.
Regards,
--
Adrien Martin
signature.asc
Description: OpenPGP digital signature
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Registrar - max_contacts and 503 logging
Hello, Ok, thanks. Regards, Adrien Martin ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Registrar - max_contacts and 503 logging
Hello,
I tested it, and it works.
About the save() return codes, there are a lot of cases, so I would have
sorted it this way:
- no error,
- error codes in parsing SIP,
- server side errors (like manipulating usrloc),
- and service errors (like too many registers).
Here is a patch by way of example, but I can't say if it's the right way
to do.
Regards,
--
Adrien Martin
diff --git a/modules/registrar/save.c b/modules/registrar/save.c
index 63e2d4d..9c0b2cf 100644
--- a/modules/registrar/save.c
+++ b/modules/registrar/save.c
@@ -816,7 +816,42 @@ error:
if (forced_c) free_contacts(forced_c);
- return 0;
+ switch (rerrno) {
+case R_FINE:
+case R_OOO:
+case R_RETRANS:
+ return 0;
+case R_TOO_MANY:
+ return -2; /* Account errors */
+case R_INV_CSEQ:
+case R_TO_USER:
+case R_AOR_PARSE:
+case R_INV_EXP:
+case R_INV_Q:
+case R_PARSE:
+case R_TO_MISS:
+case R_CID_MISS:
+case R_CS_MISS:
+case R_PARSE_EXP:
+case R_PARSE_CONT:
+case R_STAR_EXP:
+case R_STAR_CONT:
+case R_UNESCAPE:
+case R_CONTACT_LEN:
+case R_CALLID_LEN:
+case R_PARSE_PATH:
+case R_PATH_UNSUP:
+ return -3; /* UAC's SIP errors */
+case R_UL_DEL_R:
+case R_UL_GET_R:
+case R_UL_NEW_R:
+case R_UL_INS_C:
+case R_UL_INS_R:
+case R_UL_DEL_C:
+case R_UL_UPD_C:
+case R_AOR_LEN:
+ return -4; /* Server side errors */
+ }
return_minus_one:
if (forced_c) free_contacts(forced_c);
signature.asc
Description: OpenPGP digital signature
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Registrar - max_contacts and 503 logging
Hello, In the registrar module I set the max_contacts parameter. Save function work as expected, but I did not manage to log the 503 status when max contacts is reached. It seems configuration after save function is not used by Opensips in this case. Is this an expected behavior and could I log the 503 in this way or another ? PS: I found an appropriate log at INFO level, but at the moment I would rather keep NOTICE level. Indeed I could use INFO level if there is no other way to check save function's return. PS2: Opensips version is 1.8.0. Regards, Adrien Martin signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
