Tkank you very much to make me understand the difference.
So, given these parameters:
Username:
Password: yyy
Authorisation username: zzz
My telefon number : a
Domain/registar: sip3.ovh.fr
I can fill the registrtant table's columns as follows:
registar_column :
I found how to report the internal stats from the fraud detection module.
I used this command (not as per the module documentation):
opensipsctl fifo show_fraud_stats 1
It clearly shows that the sequential call count does not increment. After 3
test calls to the same number:
calls per
Hi Dragomir!
Indeed, the error reporting ("parameter not found") is a bit strange
there - we will improve that soon! Basically, you have one of the
following problems:
* "db_mysql.so" not loaded
* insufficient permissions for "name:passwd@localhost"
* opensips.sip_trace table does not exist
I think both commands do completely opposite things. The first one is used
when opensips is needed to register with provider before sending call to
it and later one when UA needs to register with opensips before sending
calls to opensips.
On 16 March 2016 at 14:44, Francjos <35...@heb.be>
Hi Denis
I am also testing the Fraud Detection module in v2.1.2. I posted some
questions last week, but not had any responses yet.
I have not had any problems with crashing after reload.
My tests have produced code -2 when the critical threshold is reached. My
code snippet is like this:
if
Okey. And i have an other questrion:
I have connexion parameters provides by provider:
Username:
Password: yyy
Authorisation username: zzz
My telefon number : a
Domain/registar: sip3.ovh.fr
1) when i create entry in the registrant table, may i going tu use these
Useful update: The actual culprit is the initial INVITE from the SIP
trunk, which is missing the "From" header. FreeSWITCH raises an eyebrow
and replies with 400 "Bad Request", while omitting the header as well on
the way back to OpenSIPS!
Liviu Chircu
OpenSIPS Developer
Hi Dimitry!
That errors suggests the "From" Header Field of the 400 negative reply
is missing! Best way to continue from here is to perform a SIP trace on
this scenario, so you can confirm this yourself before starting to fix it.
Liviu Chircu
OpenSIPS Developer
I try to use in Opensips 2.2.
2016-03-16 11:14 GMT+02:00 Nagorny, Dimitry :
> Hi Dragomir,
>
>
>
> If I understand your lines correct the *trace_id* should read like
> modparam("siptrace","db_url","mysql://name:passwd@localhost/opensips;table=sip_trace;"),
> but not
Hi Dragomir,
If I understand your lines correct the trace_id should read like
modparam("siptrace","db_url","mysql://name:passwd@localhost/opensips;table=sip_trace;"),
but not sure.
See http://www.opensips.org/html/docs/modules/2.1.x/siptrace.html for further
reference.
Best Regards
Dimitry
Hello,
I try to add siptrace in my system.
I make follow:
git pull
make proper
make all
make install
in script put follow lines :
modparam("siptrace", "trace_id","[tid]uri=mysql://name:passwd@localhost
/opensips;table=sip_trace;")
modparam("siptrace", "trace_on", 1)
I receive follow error:
Hi Koce,
Does the first async rest_post() finish successfully by having its
resume route run? Could you please add some xlog() debugging prints, so
we can better understand where it gets stuck exactly?
Also, do you notice this behaviour with any HTTP server (100%
reproducible), or is it a
Hello!
I am testing Fraud_detection on Opensips 2.1
1) I noticed an Opensips crash after fifo fraud_relaod. GDB from core in
attachment.
2) In the log file i can see such messages "CRITICAL:core:sig_alarm_abort: BUG
- shutdown timeout triggered, dying..."
3) Fraud detection doesn`t work
13 matches
Mail list logo