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 it
>> 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 funct
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", "n
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 г., Livi
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++
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
