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
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
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
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.
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]
