Hi Folks,
I have managed to diagnose this a little further.
The call to the check_fraud() function only crashes OpenSIPS if a rule
is matched. For example:
If we call to profileid 3 and 3 does not exist in the table, then all is OK.
If we call to profileid 2 which does exist but for a prefix that does
not exist, then all is OK.
If we call to profileid 2 which does exist and with a prefix that does
exist, then OpenSIPS crashes.
My database is Postgres V13.5.0 - opensips-postgres-module:amd64 3.2.3
What can I do now to diagnose this further? Any help very much appreciated.
Kind regards,
Adrian Fretwell
Nottinghamshire
UK.
On 12/12/2021 22:58, Adrian Fretwell wrote:
Hi All,
I am upgrading a routing script from v2.4 to v3.2 but I find that the
call to check_fraud crashes OpenSIPS, is the syntax for my check_fraud
call OK?
Script section:
xlog("L_NOTICE", "FD: $var(t_fd_user) - $rU - $var(t_fd_p)");
check_fraud("$var(t_fd_user)", "$rU", $var(t_fd_p));
Log output:
Dec 12 22:28:25 sipproxy /usr/sbin/opensips[164806]: FD: OP0022 -
07770759924 - 2
Dec 12 22:28:25 sipproxy /usr/sbin/opensips[164778]:
INFO:core:handle_sigs: child process 164806 exited by a signal 8
Dec 12 22:28:25 sipproxy /usr/sbin/opensips[164778]:
INFO:core:handle_sigs: core was not generated
Dec 12 22:28:25 sipproxy /usr/sbin/opensips[164778]:
INFO:core:handle_sigs: terminating due to SIGCHLD
Dec 12 22:28:25 sipproxy /usr/sbin/opensips[164798]:
INFO:core:sig_usr: signal 15 received
Dec 12 22:28:25 sipproxy /usr/sbin/opensips[164800]:
INFO:core:sig_usr: signal 15 received
Any pointers greatly appreciated. Many thanks.
--
Kind regards,
Adrian Fretwell
Nottinghamshire
UK.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
