Re: [OpenSIPS-Users] Invalid parameter errors

[Liviu Chircu]

Hi, Ben!

The strange "...type 1836017711" errors seem to be caused by a poorly 
handed error condition (a secondary bug), which is now fixed [1].  If 
this theory holds, you must have a "cannot get spec value" error (or 
slew of errors) in the earlier section of your OpenSIPS log (possibly 
right after restart or shortly after starting to process traffic).


Could you please confirm/infirm the above?  If true, are there any other 
relevant errors thrown around that initial "cannot get spec value" error 
message?  Those error logs could be key to making progress in 
understanding the main bug.


Best regards,

[1]: https://github.com/OpenSIPS/opensips/commit/52ff74af8702a

Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com

On 22.01.2019 20:58, Ben Newlin wrote:


Hi,

Since upgrading to 2.4.4 we are seeing the following logs scrolling 
nearly continuously on our servers:



ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711

ERROR:core:comp_scriptvar: cannot get left var value

WARNING:core:do_action: errorin expression at opensips.cfg:583
ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711

ERROR:core:comp_scriptvar: cannot get left var value

WARNING:core:do_action: errorin expression at opensips.cfg:583
ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711

ERROR:core:comp_scriptvar: cannot get left var value

ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711

ERROR:core:comp_scriptvar: cannot get left var value

WARNING:core:do_action: errorin expression at opensips.cfg:439

It seems to be related to our use of the json module. We often pass 
json variable types as parameters to other routes and I believe the 
errors are caused by that. But it’s hard to say as there are a few 
different script lines referenced in the errors, but some of them 
point to return statements and other code sections that don’t really 
make sense. For example, line 583 referenced in the error above is:


  return(-1);

Any ideas?

Ben Newlin


___
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] Invalid parameter errors

[Ben Newlin]

Hi,

Since upgrading to 2.4.4 we are seeing the following logs scrolling nearly 
continuously on our servers:


ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711
ERROR:core:comp_scriptvar: cannot get left var value
WARNING:core:do_action: error in expression at opensips.cfg:583
ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711
ERROR:core:comp_scriptvar: cannot get left var value
WARNING:core:do_action: error in expression at opensips.cfg:583
ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711
ERROR:core:comp_scriptvar: cannot get left var value
ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711
ERROR:core:comp_scriptvar: cannot get left var value
WARNING:core:do_action: error in expression at opensips.cfg:439


It seems to be related to our use of the json module. We often pass json 
variable types as parameters to other routes and I believe the errors are 
caused by that. But it’s hard to say as there are a few different script lines 
referenced in the errors, but some of them point to return statements and other 
code sections that don’t really make sense. For example, line 583 referenced in 
the error above is:

  return(-1);

Any ideas?

Ben Newlin
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips caching

[Ben Newlin]

Apologies, that shouldn’t have been added to this thread. Will post again 
separately.

Ben Newlin

From: Users  on behalf of Ben Newlin 

Reply-To: OpenSIPS users mailling list 
Date: Tuesday, January 22, 2019 at 1:57 PM
To: OpenSIPS users mailling list 
Subject: Re: [OpenSIPS-Users] Opensips caching

Hi,


Since upgrading to 2.4.4 we are seeing the following logs scrolling nearly 
continuously on our servers:



ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711

ERROR:core:comp_scriptvar: cannot get left var value

WARNING:core:do_action: error in expression at opensips.cfg:583
ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711

ERROR:core:comp_scriptvar: cannot get left var value

WARNING:core:do_action: error in expression at opensips.cfg:583
ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711

ERROR:core:comp_scriptvar: cannot get left var value

ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711

ERROR:core:comp_scriptvar: cannot get left var value

WARNING:core:do_action: error in expression at opensips.cfg:439



It seems to be related to our use of the json module. We often pass json 
variable types as parameters to other routes and I believe the errors are 
caused by that. But it’s hard to say as there are a few different script lines 
referenced in the errors, but some of them point to return statements and other 
code sections that don’t really make sense. For example, line 583 referenced in 
the error above is:

  return(-1);

Any ideas?

Ben Newlin

From: Users  on behalf of Ben Newlin 

Reply-To: OpenSIPS users mailling list 
Date: Thursday, January 17, 2019 at 8:51 AM
To: OpenSIPS users mailling list 
Subject: Re: [OpenSIPS-Users] Opensips caching

No, the dynamic routing module will cache the entire configuration and only 
read from memory. It must be reloaded when the configuration changes. It’s very 
quick.

Ben Newlin

From: Users  on behalf of Schneur Rosenberg 

Reply-To: OpenSIPS users mailling list 
Date: Thursday, January 17, 2019 at 2:44 AM
To: OpenSIPS users mailling list 
Subject: Re: [OpenSIPS-Users] Opensips caching

I believe that dynamic routing runs a SQL query every time, I don't think that 
can be cached, but if you do your own logic in opensips, you should be able to 
use cashedb_memcached

On Thu, Jan 17, 2019, 9:40 AM Schneur Rosenberg 
mailto:rosenberg11...@gmail.com> wrote:
In the script you have multiple caching options, cache_store and cache_fetch 
from cachedb_mamcached work without external servers like cachedb_mongo that 
requires mongodb or other nosql modules.

On Thu, Jan 17, 2019, 9:18 AM Vishal Pai 
mailto:vishalm...@gmail.com> wrote:
Hello everyone

what is the best way to implement the caching in opensips. I am doing following

we have a rate table with NPANXX with rate per minute. Every time when we do 
outbound calls we get NPANXX of dialed number and search it in database. Since 
in this way it will create a load on cpu for each select query.

Can anyone help me in this also let me know if there is any caching 
functionality is available in opensips ?


Vishal Pai
___
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 caching

[Ben Newlin]

Hi,


Since upgrading to 2.4.4 we are seeing the following logs scrolling nearly 
continuously on our servers:


ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711

ERROR:core:comp_scriptvar: cannot get left var value

WARNING:core:do_action: error in expression at opensips.cfg:583
ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711

ERROR:core:comp_scriptvar: cannot get left var value

WARNING:core:do_action: error in expression at opensips.cfg:583
ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711

ERROR:core:comp_scriptvar: cannot get left var value

ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711

ERROR:core:comp_scriptvar: cannot get left var value

WARNING:core:do_action: error in expression at opensips.cfg:439



It seems to be related to our use of the json module. We often pass json 
variable types as parameters to other routes and I believe the errors are 
caused by that. But it’s hard to say as there are a few different script lines 
referenced in the errors, but some of them point to return statements and other 
code sections that don’t really make sense. For example, line 583 referenced in 
the error above is:

  return(-1);

Any ideas?

Ben Newlin

From: Users  on behalf of Ben Newlin 

Reply-To: OpenSIPS users mailling list 
Date: Thursday, January 17, 2019 at 8:51 AM
To: OpenSIPS users mailling list 
Subject: Re: [OpenSIPS-Users] Opensips caching

No, the dynamic routing module will cache the entire configuration and only 
read from memory. It must be reloaded when the configuration changes. It’s very 
quick.

Ben Newlin

From: Users  on behalf of Schneur Rosenberg 

Reply-To: OpenSIPS users mailling list 
Date: Thursday, January 17, 2019 at 2:44 AM
To: OpenSIPS users mailling list 
Subject: Re: [OpenSIPS-Users] Opensips caching

I believe that dynamic routing runs a SQL query every time, I don't think that 
can be cached, but if you do your own logic in opensips, you should be able to 
use cashedb_memcached

On Thu, Jan 17, 2019, 9:40 AM Schneur Rosenberg 
mailto:rosenberg11...@gmail.com> wrote:
In the script you have multiple caching options, cache_store and cache_fetch 
from cachedb_mamcached work without external servers like cachedb_mongo that 
requires mongodb or other nosql modules.

On Thu, Jan 17, 2019, 9:18 AM Vishal Pai 
mailto:vishalm...@gmail.com> wrote:
Hello everyone

what is the best way to implement the caching in opensips. I am doing following

we have a rate table with NPANXX with rate per minute. Every time when we do 
outbound calls we get NPANXX of dialed number and search it in database. Since 
in this way it will create a load on cpu for each select query.

Can anyone help me in this also let me know if there is any caching 
functionality is available in opensips ?


Vishal Pai
___
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