26 Oct
2010
26 Oct
'10
4:03 a.m.
Hello List;
I was following along the Kamailio Asterisk Realtime Integration; I
modified the script to get it working on Kamailio v 3.1.
One area I had a question about was here...
We have the following block;
# Forward REGISTER to Asterisk
route[REGFWD] {
if(!is_method("REGISTER"))
{
return;
}
$var(rip) = $sel(cfg_get.asterisk.bindip);
$uac_req(method)="REGISTER";
$uac_req(ruri)="sip:" + $var(rip) + ":" +
$sel(cfg_get.asterisk.bindport);
$uac_req(furi)="sip:" + $au + "@" + $var(rip);
$uac_req(turi)="sip:" + $au + "@" + $var(rip);
$uac_req(hdrs)="Contact: <sip:" + $au + "@" + $ad
+ ":" + $sel(cfg_get.kamailio.bindport)
+ ">\r\n";
if($sel(contact.expires) != $null)
$uac_req(hdrs)= $uac_req(hdrs) + "Expires: " +
$sel(contact.expires) + "\r\n";
else
$uac_req(hdrs)= $uac_req(hdrs) + "Expires: " +
$hdr(Expires) + "\r\n";
uac_req_send();
}
If I change the line to read : $uac_req(hdrs)="Contact: <sip:" + $au +
"@" + $ad
from : $uac_req(hdrs)="Contact: <sip:" + $au + "@" +
$sel(cfg_get.kamailio.bindip)
I get the following error;
loading modules under
/usr/local/kamailio-3.1-proxy/lib/kamailio/modules_k/:/usr/local/kamailio-3.1-proxy/lib/kamailio/modules/
$ad
0(13715) ERROR: <core> [pvapi.c:445]: bad parameters
0(13715) : <core> [cfg.y:3409]: parse error in config file
/usr/local/kamailio-3.1-proxy/etc/kamailio/kamailio.cfg, line 717,
column 48-47: unknown script pseudo variable
ERROR: bad config file (1 errors)
I would imagine that if the "$au" pseudo variable is available the
"$ad"
variable would be available as well.
Please help point out my mistake.
Thanks.
David.
26 Oct
26 Oct
2:48 p.m.
Hello,
$ad is exported by pv module so it should work. Can you try to use $(ad)
and see if works?
Can you run with -dddd -E and paste the log messages here?
Cheers,
Daniel
On 10/26/10 3:03 AM, David J. wrote:
Hello List;
I was following along the Kamailio Asterisk Realtime Integration; I
modified the script to get it working on Kamailio v 3.1.
One area I had a question about was here...
We have the following block;
# Forward REGISTER to Asterisk
route[REGFWD] {
if(!is_method("REGISTER"))
{
return;
}
$var(rip) = $sel(cfg_get.asterisk.bindip);
$uac_req(method)="REGISTER";
$uac_req(ruri)="sip:" + $var(rip) + ":" +
$sel(cfg_get.asterisk.bindport);
$uac_req(furi)="sip:" + $au + "@" + $var(rip);
$uac_req(turi)="sip:" + $au + "@" + $var(rip);
$uac_req(hdrs)="Contact: <sip:" + $au + "@" + $ad
+ ":" +
$sel(cfg_get.kamailio.bindport) + ">\r\n";
if($sel(contact.expires) != $null)
$uac_req(hdrs)= $uac_req(hdrs) + "Expires: " +
$sel(contact.expires) + "\r\n";
else
$uac_req(hdrs)= $uac_req(hdrs) + "Expires: " +
$hdr(Expires) + "\r\n";
uac_req_send();
}
If I change the line to read : $uac_req(hdrs)="Contact: <sip:" + $au +
"@" + $ad
from : $uac_req(hdrs)="Contact: <sip:" + $au + "@" +
$sel(cfg_get.kamailio.bindip)
I get the following error;
loading modules under
/usr/local/kamailio-3.1-proxy/lib/kamailio/modules_k/:/usr/local/kamailio-3.1-proxy/lib/kamailio/modules/
$ad
0(13715) ERROR: <core> [pvapi.c:445]: bad parameters
0(13715) : <core> [cfg.y:3409]: parse error in config file
/usr/local/kamailio-3.1-proxy/etc/kamailio/kamailio.cfg, line 717,
column 48-47: unknown script pseudo variable
ERROR: bad config file (1 errors)
I would imagine that if the "$au" pseudo variable is available the
"$ad" variable would be available as well.
Please help point out my mistake.
Thanks.
David.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://www.asipto.com
4:55 p.m.
New subject: provoke delay?
Hello,
is there a mechanism to provoke a DELAY for certain incoming INVITES before passing them
to the callee???
Just the single message needs to be delayed as the caller might be suspicios. I do already
have a list in database and can check the caller against the list.
I do need something in routing logic to delay the current message WITHOUT slowing down
kamailio and kill performance.
something like in this pseudo_code:
route{
if (is_method("INVITE") && !has_totag() ) {
if (user_delaylist == TRUE){
delay_message_for(30 sec.);
}
}
}
Any ideas and suggestions are appreciated!
Regards,
Nicolas
--
GRATIS! Movie-FLAT mit über 300 Videos.
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome
5:09 p.m.
New subject: provoke delay?
Pike or ratelimit modules may facilitate this; otherwise, no.
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
On Oct 26, 2010, at 9:55 AM, "Nicolas Rüger" <NicolasRueger(a)gmx.de>
wrote:
Hello,
is there a mechanism to provoke a DELAY for certain incoming INVITES
before passing them to the callee???
Just the single message needs to be delayed as the caller might be
suspicios. I do already have a list in database and can check the
caller against the list.
I do need something in routing logic to delay the current message
WITHOUT slowing down kamailio and kill performance.
something like in this pseudo_code:
route{
if (is_method("INVITE") && !has_totag() ) {
if (user_delaylist == TRUE){
delay_message_for(30 sec.);
}
}
}
Any ideas and suggestions are appreciated!
Regards,
Nicolas
--
GRATIS! Movie-FLAT mit über 300 Videos.
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
5:22 p.m.
New subject: provoke delay?
On 10/26/2010 05:09 PM, Alex Balashov wrote:
Pike or ratelimit modules may facilitate this;
otherwise, no.
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
On Oct 26, 2010, at 9:55 AM, "Nicolas Rüger"<NicolasRueger(a)gmx.de>
wrote:
> Hello,
>
> is there a mechanism to provoke a DELAY for certain incoming INVITES
> before passing them to the callee???
>
>
>
Hello, It is not a good design practice to do it synchronously, mainly
because the worker process will remain blocked for 30s . Imagine an
attacker sending 30 requests and DoS the whole server , because of the
limited number of worker process (not to mention that 30s delay means
retrasmits from the TM layer- so these need to be handled by tm before
the "sleep").
Anyway I wouldn't recommend a design like this. As others suggested
pike and ratelimite (mostly ratelimit) will allow you to drop calls from
attackers. You could add a Retry-After header so to inform a normal UA
to retry the request after a number of seconds.
Marius
Just the
single message needs to be delayed as the caller might be
suspicios. I do already have a list in database and can check the
caller against the list.
I do need something in routing logic to delay the current message
WITHOUT slowing down kamailio and kill performance.
something like in this pseudo_code:
route{
if (is_method("INVITE")&& !has_totag() ) {
if (user_delaylist == TRUE){
delay_message_for(30 sec.);
}
}
}
Any ideas and suggestions are appreciated!
Regards,
Nicolas
--
GRATIS! Movie-FLAT mit über 300 Videos.
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
6:34 p.m.
New subject: provoke delay?
Hello,
thank you. I see the problem with the worker processes now. I had a look at PIKE module
and RATELIMIT module as well.
My idea was to delay the call WITHOUT sending any reply-message to the caller, as I wanted
to save performance and I can identify suspicios users by a reputation that I compute
before.
It seems the only way to do so, might be to store the INVITE information somewhere and
keep on routing it again after a certain timeout.
Do you agree?
Regards,
Nicolas
On 10/26/2010 05:09 PM, Alex Balashov wrote:
> Pike or ratelimit modules may facilitate this; otherwise, no.
>>
>>
Hello, It is not a good design practice to do it
synchronously, mainly
because the worker process will remain blocked for 30s . Imagine an
attacker sending 30 requests and DoS the whole server , because of the
limited number of worker process (not to mention that 30s delay means
retrasmits from the TM layer- so these need to be handled by tm before
the "sleep").
Anyway I wouldn't recommend a design like this. As others suggested
pike and ratelimite (mostly ratelimit) will allow you to drop calls from
attackers. You could add a Retry-After header so to inform a normal UA
to retry the request after a number of seconds.
Marius
--
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!
Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
6:42 p.m.
New subject: provoke delay?
On 10/26/10 5:34 PM, "Nicolas Rüger" wrote:
Hello,
thank you. I see the problem with the worker processes now. I had a look at PIKE module
and RATELIMIT module as well.
My idea was to delay the call WITHOUT sending any reply-message to the caller, as I
wanted to save performance and I can identify suspicios users by a reputation that I
compute before.
It seems the only way to do so, might be to store the INVITE information somewhere and
keep on routing it again after a certain timeout.
Do you agree?
there is support in the code to suspend the transaction and resume
the
processing, iirc, look in tm module for t_suspend() function.
Right now you can do following:
- set timeout to 30 sec
- set failure route timeout
- send the invite via udp to a invalid destination (e.g., your ip port 9)
- when the 30sec will pass, the failure route timeout will be executed
and you can do further routing.
Drawbacks - for the 30sec tm will do retransmission. To avoid that, run
another kamailio on a different port where you send the invite and reply
back 100 trying so first kamailio stops the retransmission.
Cheers,
Daniel
Regards,
Nicolas
--
Daniel-Constantin Mierla
http://www.asipto.com
On 10/26/2010 05:09 PM, Alex Balashov wrote:
> Pike or ratelimit modules may facilitate this; otherwise, no.
>>
> Hello, It is not a good design practice to do it synchronously, mainly
> because the worker process will remain blocked for 30s . Imagine an
> attacker sending 30 requests and DoS the whole server , because of the
> limited number of worker process (not to mention that 30s delay means
> retrasmits from the TM layer- so these need to be handled by tm before
> the "sleep").
>
> Anyway I wouldn't recommend a design like this. As others suggested
> pike and ratelimite (mostly ratelimit) will allow you to drop calls from
> attackers. You could add a Retry-After header so to inform a normal UA
> to retry the request after a number of seconds.
>
> Marius
6:47 p.m.
New subject: provoke delay?
I get this question a lot privately from people who want to play games
to pad out the billable time in a call by sitting on it for a while
before passing it up to their vendors/upstreams.
If by chance that is the real motive, don't do it. :-) It's far more
trouble than it's worth.
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
8:33 p.m.
New subject: provoke delay?
Hi Alex,
NO that definitely NOT the motive!!!
I do write my master's thesis about SPIT prevention (SPAM over Internet Telephony) and
I try to implement several ideas in kamailio to detect SIP-URI's that try to
"spit".
So don't worry...I won't use your help to do illegal stuff! Hope that's
clarified.
Amongst other ideas I try to implement a functionality that matches a suspicios
caller's identity on a list in the database.
Afterwards the caller is either rejected or delayed, depending on his reputation that I
compute before using other ideas.
I want to delay some of these suspicios calls instead of rejecting them completly as
rejecting a call is really hard.
Further I expect automatically initiated calls to have a timeout. If the
"spitting" party won't get an answer fast enough it might walk on and try
another IP.
The idea is indeed adapted from the "e-mail world".
Regards,
Nicolas
-------- Original-Nachricht --------
Datum: Tue, 26 Oct 2010 11:47:52 -0400
Von: Alex Balashov <abalashov(a)evaristesys.com>
An: sr-users(a)lists.sip-router.org
Betreff: Re: [SR-Users] provoke delay?
I get this question a lot privately from people who
want to play games
to pad out the billable time in a call by sitting on it for a while
before passing it up to their vendors/upstreams.
If by chance that is the real motive, don't do it. :-) It's far more
trouble than it's worth.
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!
Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
8:55 p.m.
New subject: provoke delay?
2010/10/26 "Nicolas Rüger" <NicolasRueger(a)gmx.de>de>:
I want to delay some of these suspicios calls instead
of rejecting them completly as rejecting a call is really hard.
Further I expect automatically initiated calls to have a timeout. If the
"spitting" party won't get an answer fast enough it might walk on and try
another IP.
The idea is indeed adapted from the "e-mail world".
This is called "gray-lists" in SMTP world and it works really well
(I've worker with it some years ago). :)
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
9:27 p.m.
New subject: provoke delay?
Interesting stuff!
Just to clarify, I was not accusing you. I was being a little tongue-
in-cheek. :)
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
On Oct 26, 2010, at 1:33 PM, "Nicolas Rüger" <NicolasRueger(a)gmx.de>
wrote:
Hi Alex,
NO that definitely NOT the motive!!!
I do write my master's thesis about SPIT prevention (SPAM over
Internet Telephony) and I try to implement several ideas in kamailio
to detect SIP-URI's that try to "spit".
So don't worry...I won't use your help to do illegal stuff! Hope
that's clarified.
Amongst other ideas I try to implement a functionality that matches
a suspicios caller's identity on a list in the database.
Afterwards the caller is either rejected or delayed, depending on
his reputation that I compute before using other ideas.
I want to delay some of these suspicios calls instead of rejecting
them completly as rejecting a call is really hard.
Further I expect automatically initiated calls to have a timeout. If
the "spitting" party won't get an answer fast enough it might walk
on and try another IP.
The idea is indeed adapted from the "e-mail world".
Regards,
Nicolas
-------- Original-Nachricht --------
Datum: Tue, 26 Oct 2010 11:47:52 -0400
Von: Alex Balashov <abalashov(a)evaristesys.com>
An: sr-users(a)lists.sip-router.org
Betreff: Re: [SR-Users] provoke delay?
I get this question a lot privately from people
who want to play
games
to pad out the billable time in a call by sitting on it for a while
before passing it up to their vendors/upstreams.
If by chance that is the real motive, don't do it. :-) It's far
more
trouble than it's worth.
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!
Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
5143
days inactive
5143
days old
10 comments
6 participants
participants (6)
-
"Nicolas Rüger" -
Alex Balashov -
Daniel-Constantin Mierla -
David J. -
Iñaki Baz Castillo -
marius zbihlei