Re: [OpenSIPS-Users] OpenSIPS 3.1 - raise_event() crashes OpenSIPS with segmentation fault

Hi Vlad - thanks for that, it's very helpful All the best Mark On Tue, 28 Jul 2020 at 21:40, Vlad Patrascu wrote: > Hi Mark, > > thanks for the report! I have pushed a fix for the crash. > > I've also updated the documentation to be more clear about how > raise_event() should be used and

Re: [OpenSIPS-Users] OpenSIPS 3.1 - raise_event() crashes OpenSIPS with segmentation fault

Hi Mark, thanks for the report! I have pushed a fix for the crash. I've also updated the documentation to be more clear about how raise_event() should be used and the changes from 3.0. Basically, you don't have to necessarily pass both AVP parameters in 3.1, but if you want to pass only the

[OpenSIPS-Users] How to get the routing rule and gateway list only

Hi, So I have a LRN number from a lrn dipping service and so I set $rU = $avp(reply); and then I have if ( !do_routing(1,"F",,,$var(gw_attributes)) ) { my question is, the LRN number is being dialed instead of the orig dialed number, is it proper to just get the routing rules and carriers

Re: [OpenSIPS-Users] OpenSIPS 3.1 - raise_event() crashes OpenSIPS with segmentation fault

:) On Tue, 28 Jul 2020 at 15:50, Stas Kobzar wrote: > I mean, you are welcome, Mark :) sorry > > On Tue, Jul 28, 2020 at 10:45 AM Mark Allen wrote: > >> [SOLVED] >> >> Hi Stas - good call! It's a change in behaviour from 3.0. >> >> In 3.0 documentation says... >> >> The next two parameters

Re: [OpenSIPS-Users] OpenSIPS 3.1 - raise_event() crashes OpenSIPS with segmentation fault

I mean, you are welcome, Mark :) sorry On Tue, Jul 28, 2020 at 10:45 AM Mark Allen wrote: > [SOLVED] > > Hi Stas - good call! It's a change in behaviour from 3.0. > > In 3.0 documentation says... > > The next two parameters should be AVPs and they are optional. If only > one is present, it

Re: [OpenSIPS-Users] OpenSIPS 3.1 - raise_event() crashes OpenSIPS with segmentation fault

Glad it helped. You are welcome, Allen On Tue, Jul 28, 2020 at 10:45 AM Mark Allen wrote: > [SOLVED] > > Hi Stas - good call! It's a change in behaviour from 3.0. > > In 3.0 documentation says... > > The next two parameters should be AVPs and they are optional. If only > one is present, it

Re: [OpenSIPS-Users] OpenSIPS 3.1 - raise_event() crashes OpenSIPS with segmentation fault

[SOLVED] Hi Stas - good call! It's a change in behaviour from 3.0. In 3.0 documentation says... The next two parameters should be AVPs and they are optional. If only one is present, it should contain the values attached to the event. In 3.1 it removes mention of the behaviour if only one

[OpenSIPS-Users] Opensips + rtpengine benchmark

Hello Everyone, Looking to have a rock solid cluster. i have been working for opensips for long time and it is very stable. But this time i plan to run it with rtpengine. Would you recommend having a cluster on two bare metal servers? Or have two Virtual machines as cluster on a bigger

Re: [OpenSIPS-Users] OpenSIPS 3.1 - raise_event() crashes OpenSIPS with segmentation fault

Hi Allen, Did you try with two parameters: name, value? *$avp(keys) = "registered";* $avp(values) = "true"; xlog("Raised E_WFC_REGISTERED $avp(values)"); raise_event("E_WFC_REGISTERED", *$avp(keys)*, $avp(values)); I know they are said to be optional in the

[OpenSIPS-Users] OpenSIPS 3.1 - raise_event() crashes OpenSIPS with segmentation fault

We're upgrading from 3.0 to 3.1. Everything seems ok except we get a weird error. We subscribe a dynamic event... startup_route { subscribe_event("E_WFC_REGISTERED", "udp:127.0.0.1:"); } which we can see works from /var/log/syslog... event_datagram:mod_init: initializing

[OpenSIPS-Users] t_new_request from event_route and timer_route

Hi, OpenSips doesn't allow the t_new_request function to be used from event_route, or timer_route, but the following does work: event_route[E_SOME_EVENT] { route(SEND_REQUEST); } timer_route[some_timer, 10] { route(SEND_REQUEST); } route[SEND_REQUEST] { t_new_request(); } Is there

Re: [OpenSIPS-Users] OpenSIPS 3.1 - DB version table error

Thanks Liviu. That worked. On Tue, 28 Jul 2020 at 09:12, Liviu Chircu wrote: > On 28.07.2020 11:00, Mark Allen wrote: > > Presumably, there's somewhere that I should be telling opensips-cli > > that I want it to use the 3.1 schema? > > Hey, Mark! > > That seems to be the problem, indeed. I

Re: [OpenSIPS-Users] OpenSIPS 3.1 - DB version table error

[SOLVED] Scratch that. I answered my own question. I realised that I had missed the document https://github.com/OpenSIPS/opensips-cli/blob/master/docs/modules/database.md I ran the command... opensips-cli -o database_schema_path=~/src/opensips-3.1/scripts \ -x database migrate

Re: [OpenSIPS-Users] OpenSIPS 3.1 - DB version table error

On 28.07.2020 11:00, Mark Allen wrote: Presumably, there's somewhere that I should be telling opensips-cli that I want it to use the 3.1 schema? Hey, Mark! That seems to be the problem, indeed.  I assume you haven't yet installed the 3.1 opensips-mysql-module package, so the CLI can find the

Re: [OpenSIPS-Users] OpenSIPS 3.1 - DB version table error

Presumably, there's somewhere that I should be telling opensips-cli that I want it to use the 3.1 schema? On Tue, 28 Jul 2020 at 08:54, Mark Allen wrote: > Getting version table errors on startup after move to 3.1... > > ERROR:core:db_check_table_version: invalid version 10 for table dialog

[OpenSIPS-Users] OpenSIPS 3.1 - DB version table error

Getting version table errors on startup after move to 3.1... ERROR:core:db_check_table_version: invalid version 10 for table dialog found, expected 11 Version 3.1 is built from 3.1 branch on GitHub. I think I've followed the documentation correctly but OpenSIPS 3.1 is not starting and I'm