[OpenSIPS-Users] Utimer delaying execution
Hi, We are in the process of upgrading to Opensips 3.2.10 (from 1.11 TLS). Opensips has run without any issues on Centos 7 for about a week, but the other day, we got the following message (many), and eventually Opensips 3.2.10 hung up/stopped processing requests: Mar 5 21:46:15 opensips2 /usr/local/sbin/opensips[123477]: WARNING:core:utimer_ticker: utimer task already scheduled 695330 ms ago (now 136521190 ms), delaying execution We use Opensips only as a dispatcher, and do not call any external processes. Opensips tables reside in a mysql database. We have used 1.11 TLS (with openssl) for many years, and never run into this issue. Init.d script is the one that comes with 3.2.10. I came across these two related issues: https://github.com/OpenSIPS/opensips/issues/1767 https://github.com/OpenSIPS/opensips/issues/1858 It seems openssl is the culprit there, but we use wolfssl. (We had major issues with openssl). Any ideas? I will run a trap when/if this happens, but I think I need to install opensips-dbg module (Centos 7), which I can't find. Any help is appreciated. Thanks, Matt ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] opensips-cli installation issue
Hi Răzvan, Thank you for your quick response. I was able to get a hold of sqlalchemy 1.3.3, and manually copy it to python3 site-packages. Opensips-cli works fine now, but I will change the requirement in setup.py and re-install it. I think that's a better option going forward. Thanks, Matt On Tue, Mar 7, 2023, 4:38 AM Răzvan Crainea wrote: > Hi, Matt! > > I think you can try bumping the sqlalchemy version [1] to one of the > supported versions, then try to manual install [2]. > > [1] https://github.com/OpenSIPS/opensips-cli/blame/master/setup.py#L70 > [2] > > https://github.com/OpenSIPS/opensips-cli/blob/master/docs/INSTALLATION.md#from-source-code > > Best regards, > > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > > On 3/6/23 16:12, L S wrote: > > Hi, > > > > We are trying to install opensips-cli (on centos 7). > > > > It requires sqlalchemy==1.3.3, and doesn't accept 1.4.46. > > > > pip install returns: > > > > Collecting sqlalchemy==1.3.3 > >Could not find a version that satisfies the requirement > > sqlalchemy==1.3.3 (from versions: 1.3.16, 1.3.17, 1.3.18, 1.3.19, > > 1.3.20, 1.3.21, 1.3.22, 1.3.23, 1.3.24, 1.4.0b1, 1.4.0b2, 1.4.0b3, > > 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8, 1.4.9, > > 1.4.10, 1.4.11, 1.4.12, 1.4.13, 1.4.14, 1.4.15, 1.4.16, 1.4.17, 1.4.18, > > 1.4.19, 1.4.20, 1.4.21, 1.4.22, 1.4.23, 1.4.24, 1.4.25, 1.4.26, 1.4.27, > > 1.4.28, 1.4.29, 1.4.30, 1.4.31, 1.4.32, 1.4.33, 1.4.34, 1.4.35, 1.4.36, > > 1.4.37, 1.4.38, 1.4.39, 1.4.40, 1.4.41, 1.4.42, 1.4.43, 1.4.44, 1.4.45, > > 1.4.46) > > No matching distribution found for sqlalchemy==1.3.3 > > > > Any workarounds? Thanks, Matt > > > > ___ > > 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
[OpenSIPS-Users] Need some help while running opensips as docker container .
Hi All , I have an aws instance on which opensips runs as a docker container and uses database as RDS mysql . I have rtpengine Ip added in the opensips DB . When I will add another rtpengine IP in the table, how do my opensips container start using the newly added rtpengine IP without restart (restart will hamper live calls so I don't want to restart the service )? I have another machine on which Opensips-cli is running . Is it possible to connect remotely with the opensips instance and run the command " *reload_rtpengine*" ? If opensips is running on a host machine , I am able to reload_rtpengine from remote opensips-cli server but if it's in docker container then it's not working for me . Is it possible or not ? If not , is there any other process to do this ? *Thanks & Regards* *Sasmita Panda* *Senior Network Testing and Software Engineer* *3CLogic , ph:07827611765* ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] PAID not in resent INVITE from Failure Block
Hi, Richard! When a transaction is created, either by t_newtran(), either by using a function that internally creates it, the request message, along with its changes are stored/cloned in the transaction. When failure_route is run, you are actually seeing the message stored in the transaction. This essentially means that if the headers had been added *after* the transaction was created, you will not be able to access them in failure route. Of course, Ben is right as well - if you are adding the headers in the branch route, you will not see them in a different branch. And half of the reason is similar to the one above: when the transaction is created (i.e. by t_relay()), the request message is cloned in transaction, then branch routes are executed. Whatever change you make per branch, they are stored in each branch's structure (not in the message itself). Hence, when the failure route is executed, you will get the message cloned when the transaction was created (before branch routes are even executed). Hope this helps you identify missing headers in failure route :) Best regards, Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 2/24/23 17:14, Ben Newlin wrote: Richard, Are you by chance adding the PAID/RPID headers in a branch route? Changes to a SIP message made in a branch route exist only in that branch, and will not be present in the failure route. Ben Newlin *From: *Users on behalf of Richard Robson *Date: *Friday, February 24, 2023 at 6:58 AM *To: *users@lists.opensips.org *Subject: *[OpenSIPS-Users] PAID not in resent INVITE from Failure Block * EXTERNAL EMAIL - Please use caution with links and attachments * I have an OpenSIPS 2.3 instance, where we are sending a call to the next hop and are receiving a 403 forbidden. This is expected and we need to update the from or to header and resend the call to the same destination whish will accept this. we do not make any other changed in the failure route, nor want to. This is working, however, the additional PAID and RPID headers, which were added by OpenSIPs before the INVITE was t_relayed are missing from the updated INVITE, ( the from header is modified.) The documentation implies that the headers should be there: *Processing* : the original SIP request (that was sent out) There is nothing in the failure route to cause the headers to be dropped. Therefore is this by design? i.e. additional headers are dropped and need to be re-applied, they are missing because the 403 did not contain them or is this a bug and the headers should be there? INVITE (with PAID & RPID headers) -> <- 403 forbidden (no PAID or RPID) INVITE (no PAID & RPID headers) -> (this just has the from header modified) Regards, Richard ___ 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] opensips-cli installation issue
Hi, Matt! I think you can try bumping the sqlalchemy version [1] to one of the supported versions, then try to manual install [2]. [1] https://github.com/OpenSIPS/opensips-cli/blame/master/setup.py#L70 [2] https://github.com/OpenSIPS/opensips-cli/blob/master/docs/INSTALLATION.md#from-source-code Best regards, Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 3/6/23 16:12, L S wrote: Hi, We are trying to install opensips-cli (on centos 7). It requires sqlalchemy==1.3.3, and doesn't accept 1.4.46. pip install returns: Collecting sqlalchemy==1.3.3 Could not find a version that satisfies the requirement sqlalchemy==1.3.3 (from versions: 1.3.16, 1.3.17, 1.3.18, 1.3.19, 1.3.20, 1.3.21, 1.3.22, 1.3.23, 1.3.24, 1.4.0b1, 1.4.0b2, 1.4.0b3, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8, 1.4.9, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 1.4.14, 1.4.15, 1.4.16, 1.4.17, 1.4.18, 1.4.19, 1.4.20, 1.4.21, 1.4.22, 1.4.23, 1.4.24, 1.4.25, 1.4.26, 1.4.27, 1.4.28, 1.4.29, 1.4.30, 1.4.31, 1.4.32, 1.4.33, 1.4.34, 1.4.35, 1.4.36, 1.4.37, 1.4.38, 1.4.39, 1.4.40, 1.4.41, 1.4.42, 1.4.43, 1.4.44, 1.4.45, 1.4.46) No matching distribution found for sqlalchemy==1.3.3 Any workarounds? Thanks, Matt ___ 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
