Re: [OpenSIPS-Users] Payload location
Hi Alain, is it possible to show here the SIP debug with SDP? I'm not sure if a payload parameter must have any location - this is not related to IP address. Have you tried this function? http://www.opensips.org/html/docs/modules/2.4.x/sipmsgops.html#func_sipmsg_validate It's possible to read its retcode value. I'm sure it will return "-6 - SDP body parsing error." --- BR, Alexey http://alexeyka.zantsev.com/ ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Payload location
>> I think it's only one of my clients that produces this defect, how can I >>find out which call it is linked to? I think you can try the function which I mentioned in the previous message (http://www.opensips.org/html/docs/modules/2.4.x/sipmsgops.html#func_sipmsg_validate) and add xlog function to write some info about the call to the log. Start tcpdump or sngrep before it, and then you will be able to find that malformed call in the SIP debug (e.g. by Call ID). --- BR, Alexey http://alexeyka.zantsev.com/ ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] mid registrar
I have issue with very simple setup.
Two OpenSIPS servers (first is Active, second starts with keepalived only on
Active server failure, so not a cluster at all) connected to MariaDB with
same configs. Asterisk farm is registrar.
# USeR LOCation module
loadmodule "usrloc.so"
modparam("usrloc", "nat_bflag", "NAT")
modparam("usrloc", "working_mode_preset",
"single-instance-sql-write-through")
modparam("usrloc", "db_url", "DB_URL")
Mid Registrar module
loadmodule "mid_registrar.so"
modparam("mid_registrar", "mode", 2) /* 0 = mirror / 1 = ct / 2 = AoR */
modparam("mid_registrar", "outgoing_expires", 1800)
modparam("mid_registrar", "received_avp", "$avp(received_uri)")
modparam("mid_registrar", "tcp_persistent_flag",
"TCP_PERSIST_REGISTRATIONS")
This setup works somehow. Failover server starts with all locations
consistent and continues working. But when there are several switching
between Active/Failover in relatively short time, like 5-10 minutes then
most of the phones can't update their registrations because of the errors:
ERROR:mid_registrar:process_contacts_by_aor: 'last_reg_ts' key not found!
Only cleaning user location helps, like "opensipsctl ul rm " After that
phone can register again.
--
Sent from:
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Opensips 2.5 and fraud module
Hmm.And what is the purpose of control "per call"?As i understand it triggers AFTER calls finishing. What can we do in such situation?Just send email to, for example, support, that "potential fraud" call has been finished?-- Best regards, DenisС уважением,Путято Денис19:32, 9 июня 2018 г., Liviu Chircu :
The "call duration" is a "per call" statistic, while
"sequential", "concurrent", "cpm" and "total" are "interval-based"
statistics -- indeed, once they trigger, subsequent calls have a
good chance of also being rejected (e.g. unlike "total" and
"sequential", which are only reset when a new interval starts,
if you wait a bit, the "cpm" will cool down and you will be able
to safely dial again).
Cheers,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 09.06.2018 15:51, Denis via Users
wrote:
Liviu,
I expect that ones the module detects fraud, it should return
-2 on subsequent calls. As it does to "total calls" and
"subsequent calls" respectively.
In my example, the second call was successful (return 1) ,
although, as i expected, it should be fail (return -2)
Thank you
--
С уважением, Денис.
Best regards, Denis
09.06.2018, 15:11, "Liviu Chircu" :
Hi Denis,
If these are your tests:
1. 101
06.06.2018 15:34:54
2. 0
06.06.2018 15:38:21
Then the 1st one should return -2 ("call duration" critical
threshold
hit, since 101 sec > 60 sec), and the second one should
return 1
(success, no thresholds have been hit yet).
This seems to be exactly how it behaved in your case. Did I
misunderstand your test? If not, how exactly are you expecting
it to work?
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 09.06.2018 11:32, Denis via Users wrote:
Hello!
Liviu, can i be sure, that you will analyze my question?
___
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
___Users mailing listUsers@lists.opensips.orghttp://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] Payload location
Hi Alexey and thanks for your response.
I already run a sipmsg_validate for each INVITE received but it produces no
error.
if(!sipmsg_validate("shrm"))
{
xlog("L_WARN", "Dropping mal formed Messages Retcode : $retcode");
xlog("L_WARN","--- error from [$si:$sp]\n+\n$mb\n\n");
exit;
}
I have a lot of traffic on this server (around 6000 simultaneous calls - 200
CAPS) and I am unable to find which of these calls causes this fault with a
network trace.
any help would be welcome.
Thanks
Le 12/06/2018 09:41, « Users au nom de Alexey Kazantsev via Users »
a écrit :
>> I think it's only one of my clients that produces this defect, how can
I find out which call it is linked to?
I think you can try the function which I mentioned in the previous message
(http://www.opensips.org/html/docs/modules/2.4.x/sipmsgops.html#func_sipmsg_validate)
and add xlog function to write some info about the call to the log.
Start tcpdump or sngrep before it, and then you will be able to find that
malformed
call in the SIP debug (e.g. by Call ID).
---
BR, Alexey
http://alexeyka.zantsev.com/
___
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] event based routing module with clustering
Hi, We're using event based routing module to do a push notification to a client so it'll wake up a register (similar to documented "advanced sip scenarios with ebr" example). Is it possible to propagate events throughout a cluster (clusterer module)? The SIP clients might register with any one of n nodes (by SRV query), and so a transaction on a different node won't see the new contact event (unless clusterer module works in the way I hope). FYI we're using Redis for the registry db, so we could hack something using Redis pub/sub functionality -- e.g. some dedicated python thread on node A gets notified by Redis when a record is updated by node B. thoughts? thanks, Ryan -- Ryan Mitchell Telecom Logic, LLC ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
