Hi Is it possible to store user logon/logout dates + user agent used. I know that the info is in the location table but it is not persistent, and I am using the accounting table to store calls. But I am not sure there is a way to store logon/logout/user agent. Any input please ? Regards
Hi Ali,
On 09/05/2012 07:18 AM, Ali Jawad wrote:
Is it possible to store user logon/logout dates + user agent used. I know that the info is in the location table but it is not persistent, and I am using the accounting table to store calls. But I am not sure there is a way to store logon/logout/user agent.
By "logon" and "logout" I assume you are referring to registration, not something else.
You can capture a REGISTER request in the main request route and call a SQL operation via 'sqlops' to store that timestamp ($Ts) wherever you want.
There is no such thing as an "unregistration", technically, just a REGISTER request with an ;expires=0 parameter in the Contact header, or an Expires: 0 header. If you look for those parameters in your processing of the REGISTER request, e.g.
if((is_present_hf("Expires") && $hdr(Expires) == "0") || $hdr(Contact) =~ "expires=0")
you can store those times, too.
-- Alex
Hi Alex Sounds good, thanks for the input so far, anyway I can add the useragent to the entry ? Regards
On Wed, Sep 5, 2012 at 2:49 PM, Alex Balashov abalashov@evaristesys.comwrote:
Hi Ali,
On 09/05/2012 07:18 AM, Ali Jawad wrote:
Is it possible to store user logon/logout dates + user agent used. I
know that the info is in the location table but it is not persistent, and I am using the accounting table to store calls. But I am not sure there is a way to store logon/logout/user agent.
By "logon" and "logout" I assume you are referring to registration, not something else.
You can capture a REGISTER request in the main request route and call a SQL operation via 'sqlops' to store that timestamp ($Ts) wherever you want.
There is no such thing as an "unregistration", technically, just a REGISTER request with an ;expires=0 parameter in the Contact header, or an Expires: 0 header. If you look for those parameters in your processing of the REGISTER request, e.g.
if((is_present_hf("Expires") && $hdr(Expires) == "0") || $hdr(Contact) =~ "expires=0")
you can store those times, too.
-- Alex
-- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
______________________________**_________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**usershttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Sure, just pull it out with the $ua or $hdr(User-Agent) PVs.
On 09/05/2012 07:53 AM, Ali Jawad wrote:
Hi Alex Sounds good, thanks for the input so far, anyway I can add the useragent to the entry ? Regards
On Wed, Sep 5, 2012 at 2:49 PM, Alex Balashov <abalashov@evaristesys.com mailto:abalashov@evaristesys.com> wrote:
Hi Ali, On 09/05/2012 07:18 AM, Ali Jawad wrote: Is it possible to store user logon/logout dates + user agent used. I know that the info is in the location table but it is not persistent, and I am using the accounting table to store calls. But I am not sure there is a way to store logon/logout/user agent. By "logon" and "logout" I assume you are referring to registration, not something else. You can capture a REGISTER request in the main request route and call a SQL operation via 'sqlops' to store that timestamp ($Ts) wherever you want. There is no such thing as an "unregistration", technically, just a REGISTER request with an ;expires=0 parameter in the Contact header, or an Expires: 0 header. If you look for those parameters in your processing of the REGISTER request, e.g. if((is_present_hf("Expires") && $hdr(Expires) == "0") || $hdr(Contact) =~ "expires=0") you can store those times, too. -- Alex -- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ _________________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>-- *Ali Jawad
*Information Systems Manager CISSP - ITIL V3 - RHCE - VCP - C|EH - CCNA - MCSA
*Splendor Telecom (www.splendor.net http://www.splendor.net/) Beirut, Lebanon Phone: +9611373725/ext 116 FAX: +9611375554
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi Alex Thanks to your pointers above, I am able to login into a custom table insert queries as needed. However, I am not sure how to define the correct variables, what I am doing now is the following :
sql_query("cb", "insert into registrations (`user`,`agent`,`type`,`ip`,`unique`,`auth`) VALUES('test','VOS','IN','8.8.8.8', 'someID' , 'register wrong ') ", "ra");
sql_result_free("ra");
How do I get the variables for username,agent and IP.
Thanks
On Wed, Sep 5, 2012 at 3:25 PM, Alex Balashov abalashov@evaristesys.comwrote:
Sure, just pull it out with the $ua or $hdr(User-Agent) PVs.
On 09/05/2012 07:53 AM, Ali Jawad wrote:
Hi Alex
Sounds good, thanks for the input so far, anyway I can add the useragent to the entry ? Regards
On Wed, Sep 5, 2012 at 2:49 PM, Alex Balashov <abalashov@evaristesys.com <mailto:abalashov@evaristesys.**com abalashov@evaristesys.com>> wrote:
Hi Ali, On 09/05/2012 07:18 AM, Ali Jawad wrote: Is it possible to store user logon/logout dates + user agentused. I know that the info is in the location table but it is not persistent, and I am using the accounting table to store calls. But I am not sure there is a way to store logon/logout/user agent.
By "logon" and "logout" I assume you are referring to registration, not something else. You can capture a REGISTER request in the main request route and call a SQL operation via 'sqlops' to store that timestamp ($Ts) wherever you want. There is no such thing as an "unregistration", technically, just a REGISTER request with an ;expires=0 parameter in the Contact header, or an Expires: 0 header. If you look for those parameters in your processing of the REGISTER request, e.g. if((is_present_hf("Expires") && $hdr(Expires) == "0") || $hdr(Contact) =~ "expires=0") you can store those times, too. -- Alex -- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ ______________________________**___________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailinglist sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-**router.orgsr-users@lists.sip-router.org
http://lists.sip-router.org/__**cgi-bin/mailman/listinfo/sr-__**users<http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users> <http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>-- *Ali Jawad
*Information Systems Manager
CISSP - ITIL V3 - RHCE - VCP - C|EH - CCNA - MCSA
*Splendor Telecom (www.splendor.net http://www.splendor.net/)
Beirut, Lebanon Phone: +9611373725/ext 116 FAX: +9611375554
______________________________**_________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**usershttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
______________________________**_________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**usershttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 09/06/2012 09:25 AM, Ali Jawad wrote:
How do I get the variables for username,agent and IP.
This information comes from pseudovariables ("PVs"), which are basically parts of the SIP message that are parsed by Kamailio and exposed inside the config script environment as read-only (and in a cases, mutable) variables.
Take a look at the full list here:
http://www.kamailio.org/dokuwiki/doku.php/pseudovariables:3.1.x
The ones you are looking for are:
(1) $au - for authentication username, or $fU for From URI user part.
(2) $ua - user agent identifier, if present. A good way to check if it is present is to check for the existence of the User-Agent header, which is not a mandatory header:
$var(ua) = '';
if(is_present_hf("User-Agent")) $var(ua) = $ua;
# Log $var(ua)...
(3) $si - source IP of the request being processed.
-- Alex
Thank you Alex, I got where I need to. Appreciated. Regards
On Thu, Sep 6, 2012 at 4:30 PM, Alex Balashov abalashov@evaristesys.comwrote:
On 09/06/2012 09:25 AM, Ali Jawad wrote:
How do I get the variables for username,agent and IP.
This information comes from pseudovariables ("PVs"), which are basically parts of the SIP message that are parsed by Kamailio and exposed inside the config script environment as read-only (and in a cases, mutable) variables.
Take a look at the full list here:
http://www.kamailio.org/**dokuwiki/doku.php/**pseudovariables:3.1.xhttp://www.kamailio.org/dokuwiki/doku.php/pseudovariables:3.1.x
The ones you are looking for are:
(1) $au - for authentication username, or $fU for From URI user part.
(2) $ua - user agent identifier, if present. A good way to check if it is present is to check for the existence of the User-Agent header, which is not a mandatory header:
$var(ua) = '';
if(is_present_hf("User-Agent")**) $var(ua) = $ua;
# Log $var(ua)...
(3) $si - source IP of the request being processed.
-- Alex
-- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
______________________________**_________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**usershttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
No problem!
As always, be mindful of security; some of the parameters can be easily spoofed or manipulated by someone who knows what they're doing. If you're taking their values and throwing them straight into a SQL statement unsanitised, these values can form the basis of a SQL injection attack.
This is why the Kamailio route script also offers something called transformations, which you can think of essentially as string functions/methods that can be applied to any variable.
They are listed here:
http://www.kamailio.org/dokuwiki/doku.php/transformations:3.1.x
In particular, the transformation that I had in mind for you was:
http://www.kamailio.org/dokuwiki/doku.php/transformations:3.1.x#sescapecommo...
So, when putting, for instance, $ua into the DB, you might consider applying the {s.escape.common} transformation to it. Instead of $ua, use $(ua{s.escape.common}).
-- Alex
On 09/06/2012 10:04 AM, Ali Jawad wrote:
Thank you Alex, I got where I need to. Appreciated. Regards
On Thu, Sep 6, 2012 at 4:30 PM, Alex Balashov <abalashov@evaristesys.com mailto:abalashov@evaristesys.com> wrote:
On 09/06/2012 09:25 AM, Ali Jawad wrote: How do I get the variables for username,agent and IP. This information comes from pseudovariables ("PVs"), which are basically parts of the SIP message that are parsed by Kamailio and exposed inside the config script environment as read-only (and in a cases, mutable) variables. Take a look at the full list here: http://www.kamailio.org/__dokuwiki/doku.php/__pseudovariables:3.1.x <http://www.kamailio.org/dokuwiki/doku.php/pseudovariables:3.1.x> The ones you are looking for are: (1) $au - for authentication username, or $fU for From URI user part. (2) $ua - user agent identifier, if present. A good way to check if it is present is to check for the existence of the User-Agent header, which is not a mandatory header: $var(ua) = ''; if(is_present_hf("User-Agent")__) $var(ua) = $ua; # Log $var(ua)... (3) $si - source IP of the request being processed. -- Alex -- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ _________________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi Alex Thanks again for walking the extra mile and bringing this to my attention, I did apply your fix. You are a Kamailio gold mine. Thanks again
On Thu, Sep 6, 2012 at 5:08 PM, Alex Balashov abalashov@evaristesys.comwrote:
No problem!
As always, be mindful of security; some of the parameters can be easily spoofed or manipulated by someone who knows what they're doing. If you're taking their values and throwing them straight into a SQL statement unsanitised, these values can form the basis of a SQL injection attack.
This is why the Kamailio route script also offers something called transformations, which you can think of essentially as string functions/methods that can be applied to any variable.
They are listed here:
http://www.kamailio.org/**dokuwiki/doku.php/**transformations:3.1.xhttp://www.kamailio.org/dokuwiki/doku.php/transformations:3.1.x
In particular, the transformation that I had in mind for you was:
http://www.kamailio.org/**dokuwiki/doku.php/**transformations:3.1.x#** sescapecommonhttp://www.kamailio.org/dokuwiki/doku.php/transformations:3.1.x#sescapecommon
So, when putting, for instance, $ua into the DB, you might consider applying the {s.escape.common} transformation to it. Instead of $ua, use $(ua{s.escape.common}).
-- Alex
On 09/06/2012 10:04 AM, Ali Jawad wrote:
Thank you Alex, I got where I need to. Appreciated.
Regards
On Thu, Sep 6, 2012 at 4:30 PM, Alex Balashov <abalashov@evaristesys.com <mailto:abalashov@evaristesys.**com abalashov@evaristesys.com>> wrote:
On 09/06/2012 09:25 AM, Ali Jawad wrote: How do I get the variables for username,agent and IP. This information comes from pseudovariables ("PVs"), which are basically parts of the SIP message that are parsed by Kamailio and exposed inside the config script environment as read-only (and in a cases, mutable) variables. Take a look at the full list here: http://www.kamailio.org/__**dokuwiki/doku.php/__**pseudovariables:3.1.xhttp://www.kamailio.org/__dokuwiki/doku.php/__pseudovariables:3.1.x
<http://www.kamailio.org/**dokuwiki/doku.php/**pseudovariables:3.1.x<http://www.kamailio.org/dokuwiki/doku.php/pseudovariables:3.1.x>The ones you are looking for are: (1) $au - for authentication username, or $fU for From URI user part. (2) $ua - user agent identifier, if present. A good way to check if it is present is to check for the existence of the User-Agent header, which is not a mandatory header: $var(ua) = ''; if(is_present_hf("User-Agent")**__) $var(ua) = $ua; # Log $var(ua)... (3) $si - source IP of the request being processed. -- Alex -- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ ______________________________**___________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailinglist sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-**router.orgsr-users@lists.sip-router.org
http://lists.sip-router.org/__**cgi-bin/mailman/listinfo/sr-__**users<http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users> <http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>______________________________**_________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**usershttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
______________________________**_________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**usershttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-
Alex Balashov -
Ali Jawad