Re: [SR-Users] Limiting registrations to known users without auth
Thanks Ovidiu,
I've opened a bug about it.
BR,
Pedro
De:
Ovidiu Sas o...@voipembedded.com
Para:
SIP Router -
Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List sr-users@lists.sip-router.org
Fecha:
07/03/2012 17:25
Asunto:
Re: [SR-Users]
Limiting registrations to known users without auth
Enviado por:
sr-users-boun...@lists.sip-router.org
db_text doesn't have sql capabilites (I think it should
be mentioned
in the documentation).
Also, it should not crash too (this is a bug that needs to be
addressed - please open a bug and provide a backtrace).
If you don't want to use a truedb, you can try to use sqlite:
http://kamailio.org/docs/modules/stable/modules_k/db_sqlite.html
This should be compatible with sqlops.
Regards,
Ovidiu Sas
--
VoIP Embedded, Inc.
http://www.voipembedded.com
On Wed, Mar 7, 2012 at 11:18 AM, Pedro Antonio Vico Solano
pvsol...@amper.es wrote:
Thanks for the clarification, Daniel.
I've tried the 'sqlops' solution but there is something wrong. Is
sqlops
compatible with the db_text DB?
I've tried:
modparam(sqlops,sqlcon,ca=text:///etc/kamailio/dbtext)
...
sql_query(ca, select * from uri, ra);
xlog(rows: $dbr(ra=rows) cols: $dbr(ra=cols)\n);
sql_result_free(ra);
...
It gives a segmentation fault.
Thanks BR,
Pedro
De:Daniel-Constantin Mierla mico...@gmail.com
Para:SIP Router - Kamailio (OpenSER)
and SIP Express Router (SER) -
Users Mailing List sr-users@lists.sip-router.org
cc:Pedro Antonio Vico Solano pvsol...@amper.es
Fecha:02/03/2012 10:04
Asunto:Re: [SR-Users] Limiting registrations
to known users without
auth
Hello,
check_to() matches to see if the authenticated user is allowed to
use the
address in the To header, so it has to be called for authenticated
requests.
does_uri_exist() is checking to see if r-uri address is a valid local
subscriber, but it does not have an option take it from To header.
What you can do is to use sqlops module to do a query and check if
the
address (or user part of it) in To header is matching a record (username
and
eventually the domain) in subscriber table.
Cheers,
Daniel
On 3/1/12 6:10 PM, Pedro Antonio Vico Solano wrote:
Hello,
I'm trying to restrict registrations based on the username/number
but
without authentication. I'm using uri_db module, the URI
table and the
check_to() function. But when a user tries to register Kamailio 3.1.5
says
the following error:
0(11832) ERROR: uri_db [checks.c:71]: No authorized credentials found
(error
in scripts)
0(11832) ERROR: uri_db [checks.c:72]: Call {www,proxy}_authorize before
calling check_* functions!
I've read README from uri_db and seems to be possible doing it the
way I do.
I have the following configuration:
modparam(usrloc|uri_db, db_url, text:///etc/kamailio/dbtext)
modparam(uri_db, db_table, uri)
modparam(uri_db, use_uri_table, 1)
route{
...
check_to()
...
}
am I doing right?
Thanks BR,
Pedro
ADVERTENCIA
Este mensaje y/o sus anexos, pueden contener información personal
y
confidencial cuyo uso, reproducción o distribución no autorizados
están
legalmente prohibidos. Por lo tanto, si Vd. no fuera su destinatario
y,
erróneamente, lo hubiera recibido, le rogamos que informe al remitente
y lo
borre de inmediato.
En cumplimiento de la Ley Orgánica 15/1999, de Protección de Datos
de
Carácter Personal le informamos de que su dirección de correo electrónico,
así como sus datos personales y de empresa pasarán a formar parte
de nuestro
fichero de Gestión, y serán tratados con la única finalidad de mantenimiento
de la relación adquirida con usted. Los datos personales que existen
en
nuestro poder están protegidos por nuestra Política de Seguridad,
y no serán
compartidos con ninguna otra empresa. Usted puede ejercitar los derechos
de
acceso, rectificación, cancelación y oposición dirigiéndose por escrito
a la
dirección arriba indicada.
This e-mail and its attachments may include confidential personal
information which may be protected by any legal rules and cannot be
used,
copied, distributed or disclosed to any person without authorisation.
If you
are not the intended recipient and have received this e-mail by mistake,
please advise the sender and erase it.
In compliance with the Spanish Organic Act 15/1999 on Personal Data
Protection, we hereby inform you that your email address, as well
as your
personal and business information, will be included in our Management
files
and used solely for purposes corresponding to our commercial relationship.
All personal data in our possession is protected by our Data Safety
Policy
and thus shall not be released to any other third party whatsoever.
You may
exercise your right to access, rectify, cancel and contest by writing
to the
address provided above.
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
Re: [SR-Users] Limiting registrations to known users without auth
Thanks for the clarification, Daniel.
I've tried the 'sqlops' solution but
there is something wrong. Is sqlops compatible with the db_text DB?
I've tried:
modparam(sqlops,sqlcon,ca=text:///etc/kamailio/dbtext)
...
sql_query(ca, select
* from uri, ra);
xlog(rows: $dbr(ra=rows) cols:
$dbr(ra=cols)\n);
sql_result_free(ra);
...
It gives a segmentation fault.
Thanks BR,
Pedro
De:
Daniel-Constantin Mierla
mico...@gmail.com
Para:
SIP Router -
Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List
sr-users@lists.sip-router.org
cc:
Pedro Antonio Vico
Solano pvsol...@amper.es
Fecha:
02/03/2012 10:04
Asunto:
Re: [SR-Users]
Limiting registrations to known users without auth
Hello,
check_to() matches to see if the authenticated user is allowed to use the
address in the To header, so it has to be called for authenticated requests.
does_uri_exist() is checking to see if r-uri address is a valid local subscriber,
but it does not have an option take it from To header.
What you can do is to use sqlops module to do a query and check if the
address (or user part of it) in To header is matching a record (username
and eventually the domain) in subscriber table.
Cheers,
Daniel
On 3/1/12 6:10 PM, Pedro Antonio Vico Solano wrote:
Hello,
I'm trying to restrict registrations based on the username/number but without
authentication. I'm using uri_db module, the URI table and
the check_to() function. But when a user tries to register Kamailio 3.1.5
says the following error:
0(11832) ERROR: uri_db [checks.c:71]: No authorized credentials found (error
in scripts)
0(11832) ERROR: uri_db [checks.c:72]: Call {www,proxy}_authorize before
calling check_* functions!
I've read README from uri_db and seems to be possible doing it the way
I do. I have the following configuration:
modparam(usrloc|uri_db, db_url, text:///etc/kamailio/dbtext)
modparam(uri_db, db_table, uri)
modparam(uri_db, use_uri_table, 1)
route{
...
check_to()
...
}
am I doing right?
Thanks BR,
Pedro
ADVERTENCIA
Este mensaje y/o sus anexos, pueden contener información personal y confidencial
cuyo uso, reproducción o distribución no autorizados están legalmente
prohibidos. Por lo tanto, si Vd. no fuera su destinatario y, erróneamente,
lo hubiera recibido, le rogamos que informe al remitente y lo borre de
inmediato.
En cumplimiento de la Ley Orgánica 15/1999, de Protección de Datos de
Carácter Personal le informamos de que su dirección de correo electrónico,
así como sus datos personales y de empresa pasarán a formar parte de
nuestro fichero de Gestión, y serán tratados con la única finalidad
de mantenimiento de la relación adquirida con usted. Los datos personales
que existen en nuestro poder están protegidos por nuestra Política de
Seguridad, y no serán compartidos con ninguna otra empresa. Usted puede
ejercitar los derechos de acceso, rectificación, cancelación y oposición
dirigiéndose por escrito a la dirección arriba indicada.
This e-mail and its attachments may include confidential personal information
which may be protected by any legal rules and cannot be used, copied, distributed
or disclosed to any person without authorisation. If you are not the intended
recipient and have received this e-mail by mistake, please advise the sender
and erase it.
In compliance with the Spanish Organic Act 15/1999 on Personal Data Protection,
we hereby inform you that your email address, as well as your personal
and business information, will be included in our Management files and
used solely for purposes corresponding to our commercial relationship.
All personal data in our possession is protected by our Data Safety Policy
and thus shall not be released to any other third party whatsoever. You
may exercise your right to access, rectify, cancel and contest by writing
to the address provided above.
___
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
--
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda
-- http://twitter.com/miconda
ADVERTENCIA
Este mensaje y/o sus anexos, pueden contener información personal y confidencial
cuyo uso, reproducción o distribución no autorizados están legalmente prohibidos.
Por lo tanto, si Vd. no fuera su destinatario y, erróneamente, lo hubiera
recibido, le rogamos que informe al remitente y lo borre de inmediato.
En cumplimiento de la Ley Orgánica 15/1999, de Protección de Datos de Carácter
Personal le informamos de que su dirección de correo electrónico, así como
sus datos personales y de empresa pasarán a formar parte de nuestro fichero
de Gestión, y serán tratados con la única finalidad de mantenimiento de
la relación adquirida con usted. Los datos personales que existen en nuestro
poder están protegidos por nuestra Política de Seguridad, y no serán compartidos
con ninguna
Re: [SR-Users] Limiting registrations to known users without auth
db_text doesn't have sql capabilites (I think it should be mentioned
in the documentation).
Also, it should not crash too (this is a bug that needs to be
addressed - please open a bug and provide a backtrace).
If you don't want to use a truedb, you can try to use sqlite:
http://kamailio.org/docs/modules/stable/modules_k/db_sqlite.html
This should be compatible with sqlops.
Regards,
Ovidiu Sas
--
VoIP Embedded, Inc.
http://www.voipembedded.com
On Wed, Mar 7, 2012 at 11:18 AM, Pedro Antonio Vico Solano
pvsol...@amper.es wrote:
Thanks for the clarification, Daniel.
I've tried the 'sqlops' solution but there is something wrong. Is sqlops
compatible with the db_text DB?
I've tried:
modparam(sqlops,sqlcon,ca=text:///etc/kamailio/dbtext)
...
sql_query(ca, select * from uri, ra);
xlog(rows: $dbr(ra=rows) cols: $dbr(ra=cols)\n);
sql_result_free(ra);
...
It gives a segmentation fault.
Thanks BR,
Pedro
De: Daniel-Constantin Mierla mico...@gmail.com
Para: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
Users Mailing List sr-users@lists.sip-router.org
cc: Pedro Antonio Vico Solano pvsol...@amper.es
Fecha: 02/03/2012 10:04
Asunto: Re: [SR-Users] Limiting registrations to known users without
auth
Hello,
check_to() matches to see if the authenticated user is allowed to use the
address in the To header, so it has to be called for authenticated requests.
does_uri_exist() is checking to see if r-uri address is a valid local
subscriber, but it does not have an option take it from To header.
What you can do is to use sqlops module to do a query and check if the
address (or user part of it) in To header is matching a record (username and
eventually the domain) in subscriber table.
Cheers,
Daniel
On 3/1/12 6:10 PM, Pedro Antonio Vico Solano wrote:
Hello,
I'm trying to restrict registrations based on the username/number but
without authentication. I'm using uri_db module, the URI table and the
check_to() function. But when a user tries to register Kamailio 3.1.5 says
the following error:
0(11832) ERROR: uri_db [checks.c:71]: No authorized credentials found (error
in scripts)
0(11832) ERROR: uri_db [checks.c:72]: Call {www,proxy}_authorize before
calling check_* functions!
I've read README from uri_db and seems to be possible doing it the way I do.
I have the following configuration:
modparam(usrloc|uri_db, db_url, text:///etc/kamailio/dbtext)
modparam(uri_db, db_table, uri)
modparam(uri_db, use_uri_table, 1)
route{
...
check_to()
...
}
am I doing right?
Thanks BR,
Pedro
ADVERTENCIA
Este mensaje y/o sus anexos, pueden contener información personal y
confidencial cuyo uso, reproducción o distribución no autorizados están
legalmente prohibidos. Por lo tanto, si Vd. no fuera su destinatario y,
erróneamente, lo hubiera recibido, le rogamos que informe al remitente y lo
borre de inmediato.
En cumplimiento de la Ley Orgánica 15/1999, de Protección de Datos de
Carácter Personal le informamos de que su dirección de correo electrónico,
así como sus datos personales y de empresa pasarán a formar parte de nuestro
fichero de Gestión, y serán tratados con la única finalidad de mantenimiento
de la relación adquirida con usted. Los datos personales que existen en
nuestro poder están protegidos por nuestra Política de Seguridad, y no serán
compartidos con ninguna otra empresa. Usted puede ejercitar los derechos de
acceso, rectificación, cancelación y oposición dirigiéndose por escrito a la
dirección arriba indicada.
This e-mail and its attachments may include confidential personal
information which may be protected by any legal rules and cannot be used,
copied, distributed or disclosed to any person without authorisation. If you
are not the intended recipient and have received this e-mail by mistake,
please advise the sender and erase it.
In compliance with the Spanish Organic Act 15/1999 on Personal Data
Protection, we hereby inform you that your email address, as well as your
personal and business information, will be included in our Management files
and used solely for purposes corresponding to our commercial relationship.
All personal data in our possession is protected by our Data Safety Policy
and thus shall not be released to any other third party whatsoever. You may
exercise your right to access, rectify, cancel and contest by writing to the
address provided above.
___
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
--
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda
ADVERTENCIA
Este mensaje y/o sus anexos, pueden contener información personal y
confidencial cuyo uso, reproducción o
