I cannot get my SER to talk to my RADIUS server, its just blindly
401ing things without ever making contact with RADIUS.
SER config looks like this
if (method == "REGISTER") {
if (!radius_www_authorize("")) {
www_challenge("", "1");
break;
};
save("location");
};
radiusclient-ng servers file:
192.168.1.103 heslo
radiusclient.conf:
auth_order radius,local
login_tries 4
login_timeout 60
authserver 192.168.1.103:1812
acctserver 192.168.1.103:1813
dictionary /usr/local/etc/radiusclient-ng/dictionary
FreeRADIUS clients.conf:
client 192.168.1.109 {
secret = heslo
shortname = proxy1
nastype = other
Not sure what to do!
Hi Bogdan
The section 3.2.1 (The WWW-Authenticate Response Header) from RFC 2617 says:
"algorithm
A string indicating a pair of algorithms used to produce the digest
and a checksum. If this is not present it is assumed to be "MD5".
"
I send a INVITE to Openser but it send back a 407 (Proxy Authentication).
The parameter response was OK. But, without the parameter 'algorithm', the proxy
didn't allow the authentication. It neither consult at Radius.
Looking at the RFC above, the SIP proxy must to use MD5 by default, but it
don't accept the message without the parameter.
Can it be a bug of OpenSER? Or my interpretation is wrong? (I bet that I'm wrong :) )
Best regards.
Bruno Machado
----- Mensagem original ----
De: Bogdan-Andrei Iancu <bogdan(a)voice-system.ro>
Para: Bruno Machado <bsmufu(a)yahoo.com.br>
Cc: users(a)openser.org
Enviadas: Segunda-feira, 29 de Janeiro de 2007 14:21:31
Assunto: Re: [Users] 407 and algorithm=MD5
Hi Bruno,
you cannot configure to have the algorithm param added. If I'm not
wrong, the digest RFC says this is an optional param and the default
value is MD5.
regards,
bogdan
Bruno Machado wrote:
> Hi.
>
> When I use the function proxy_challenge(), the 407 don't have the
> parameter 'algorithm=MD5'. Look below:
>
> ...
> Proxy-Authenticate: Digest realm="proxy.com.br",
> nonce="45be00f941f137ff037436c77f80a9531a02155f".
> ...
>
> How can I put this parameter in digest informations?
>
> ...
> Proxy-Authenticate: Digest realm="proxy.com.br",
> nonce="45be00f941f137ff037436c77f80a9531a02155f",
> algorithm="MD5".
> ...
>
>
> Thanks in advance.
>
> Bruno
>
> __________________________________________________
> Fale com seus amigos de graça com o novo Yahoo! Messenger
> http://br.messenger.yahoo.com/
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Users mailing list
>Users(a)openser.org
>http://openser.org/cgi-bin/mailman/listinfo/users
>
>
__________________________________________________
Fale com seus amigos de graça com o novo Yahoo! Messenger
http://br.messenger.yahoo.com/
Hello everybody,
the development version allows now ability to use pseudo-variables
directly in configuration file. In addition to old pseudo-variables you
know, a new type was introduced: script variables - the format is
$var(name) where name can be any string of digits and characters.
Basically this are variables that can have integer or string values and
they can be set directly in the configuration file via 'assign
operation. The big advantage is that they are directly referenced at
runtime, avoiding searching each access time. They are specific per
processes and survive over multiple sip message processing (be sure you
set the value before testing it -- e.g., $var(counter) = $var(counter) +
1 at the beginning of main route is a counter of messages processed).
The script variables are initialized at startup to '0'. You can shift
between value types: e.g., '$var(a)=1; $var(a)="openser";' is valid.
The switch statement can be used now with any valid pseudo-variable
('retcode' must be now replaced with '$retcode' to get old behavior).
switch($rU) will compare the r-uri username with 'case' values. The case
'values' can be string or integer.
switch($rU) {
case "101": xlog("dialed number is 101\n"); break;
case "102": xlog("dialed number is 102\n"); break;
default: xlog("dialed number is $rU\n");
}
Assignments of script variables, AVPs, R-URI parts (username, domain,
and URI) and dst URI can be done as well in script.
$avp(i:11) = 1; - sets the value of $avp(i:11) to integer '1'
$avp(i:11) = "1"; - sets the value of $avp(i:11) to string '1'
$ru = "sip:"+$var(user)+"@"+$fd; - sets the R-URI to string composed
from value of variable $var(user) and From URI domain
'+' can be used to concatenate strings or do arithmetic addition. Other
arithmetic operators:
- '-' - minus
- '/' - divide
- '*' - multiply
- '%' - modulo
- '|' - bitwise OR
- '&' - bitwise AND
- '^' - bitwise XOR
- '~' - bitwise NOT
To make sure that the priority of the operators is right, do use
parenthesis, it is the best to get expected result:
$var(a) = 2 + (7&(~4));
If you want to evaluate arithmetic operations and test the value in
conditions, use the test operator ' [ ... ] ' . This is required to
convert the result to internal convention for drop, true and false.
if ( [ $var(a)&4 ] ) {
xlog("bit 3 is set in var a");
}
Old '*' used to match any port or proto was changed to 'any' to avoid
the conflict with multiply operator. Some operations overlap with
several avpops functions. Until sure that all cases are covered in
script variant, both will go further, avpops version being scheduled for
deprecation.
It was a big lump of changes, help in testing and feedback is very much
appreciated.
Cheers,
Daniel
Hi.
When I use the function proxy_challenge(), the 407 don't have the parameter 'algorithm=MD5'. Look below:
...
Proxy-Authenticate: Digest realm="proxy.com.br", nonce="45be00f941f137ff037436c77f80a9531a02155f".
...
How can I put this parameter in digest informations?
...
Proxy-Authenticate: Digest realm="proxy.com.br", nonce="45be00f941f137ff037436c77f80a9531a02155f",
algorithm="MD5".
...
Thanks in advance.
Bruno
__________________________________________________
Fale com seus amigos de graça com o novo Yahoo! Messenger
http://br.messenger.yahoo.com/
Hello !
I have an problem with the SER ..therefore I want to install the
OpenSER, but before I install it I want to know whether it can solve my
problem or not.
I got an shell script which starts a java application , there are no
problem with it. But when I start the script with SERs exec module
(exec_msg() ) the java application does not support german charset and
replaces german spellings with "?". The problem do not occur when I
start the shell script manually. I have testet a lot of thinks but the
problem still exists.
So can someone tell whether he/she has such a problem with OpenSER or
not or have an idea how I can solve the problem with SER ?
If not I would try out OpenSER !
thanks
Ahsen
Hello Users,
I'm Using The Following software of My Sip productions,
1) OpenSER is a Sip Server,proxy, in front-end
2) Asterisk is PBX server, in Back-end
3) Radius for AAA to OpenSER,
4) Asterisk-java for IVR for Billing Customer care
if I didn't any mistakes in these mail , forgive me .
My Question is
1) If Caller calls to Callee , Before the call established to callee.
The Caller has to know his Balance Account.
if the Balance is there, then only the call has to establish,
2) I want the OpenSER total in RealTime application Server like Java
application . Call Authorization ( Question no 1 ).
If Asterisk is Front-end , ---> problem is Solved,
How can a b2bua implement with OpenSER,
please when
--
Thanks and Regards
Ravi Prakash Sunkara
ravi.sunkara(a)hyperion-tech.com
M:+91 9985077535
O:+91 40 23114549
F:+91 40 40208727
ravi.sunkara(a)hyperion-tech.com
www.hyperion-tech.com
Hi All
I am using a FC-6 machine and installed ser-0.9.6-9.fc6. But while starting the serctl I got the following the error.
So do you have any clue about it?
Starting SER : PID file /var/run/ser.pid does not exist -- SER start failed
*********************************************************
0(4265) ERROR: load_module: could not open module </usr/lib/ser/modulessl.so>: /usr/lib/ser/modulessl.so: cannot open shared object file: No such file or directory
0(4265) parse error (30,13-14): failed to load module
0(4265) ERROR: load_module: could not open module </usr/lib/ser/modulestm.so>: /usr/lib/ser/modulestm.so: cannot open shared object file: No such file or directory
0(4265) parse error (31,13-14): failed to load module
0(4265) ERROR: load_module: could not open module </usr/lib/ser/modulesrr.so>: /usr/lib/ser/modulesrr.so: cannot open shared object file: No such file or directory
0(4265) parse error (32,13-14): failed to load module
0(4265) ERROR: load_module: could not open module </usr/lib/ser/modulesmaxfwd.so>: /usr/lib/ser/modulesmaxfwd.so: cannot open shared object file: No such file or directory
0(4265) parse error (33,13-14): failed to load module
0(4265) ERROR: load_module: could not open module </usr/lib/ser/modulesusrloc.so>: /usr/lib/ser/modulesusrloc.so: cannot open shared object file: No such file or directory
0(4265) parse error (34,13-14): failed to load module
0(4265) ERROR: load_module: could not open module </usr/lib/ser/modulesregistrar.so>: /usr/lib/ser/modulesregistrar.so: cannot open shared object file: No such file or directory
0(4265) parse error (35,13-14): failed to load module
0(4265) ERROR: load_module: could not open module </usr/lib/ser/modulestextops.so>: /usr/lib/ser/modulestextops.so: cannot open shared object file: No such file or directory
0(4265) parse error (36,13-14): failed to load module
0(4265) set_mod_param_regex: No module matching usrloc found
| 0(4265) parse error (47,21-22): Can't set module parameter
0(4265) set_mod_param_regex: No module matching rr found
| 0(4265) parse error (65,19-20): Can't set module parameter
0(4265) parse error (75,34-35): unknown command, missing loadmodule?
0(4265) parse error (76,22-23): unknown command, missing loadmodule?
0(4265) parse error (80,23-24): unknown command, missing loadmodule?
0(4265) parse error (89,32-33): unknown command, missing loadmodule?
0(4265) parse error (93,18-19): unknown command, missing loadmodule?
0(4265) parse error (95,19-20): unknown command, missing loadmodule?
0(4265) parse error (102,19-20): unknown command, missing loadmodule?
0(4265) parse error (120,11-12): unknown command, missing loadmodule?
0(4265) parse error (124,12-13): unknown command, missing loadmodule?
0(4265) parse error (126,20-21): unknown command, missing loadmodule?
0(4265) parse error (132,17-18): unknown command, missing loadmodule?
0(4265) parse error (133,24-25): unknown command, missing loadmodule?
0(4265) parse error (137,18-19): unknown command, missing loadmodule?
0(4265) parse error (145,15-16): unknown command, missing loadmodule?
0(4265) parse error (146,18-19): unknown command, missing loadmodule?
ERROR: bad config file (24 errors)
[root@host223 ~]# /usr/sbin/serctl start
Starting SER : PID file /var/run/ser.pid does not exist -- SER start failed
[root@host223 ~]# rpm -q ser
ser-0.9.6-9.fc6
[root@host223 ~]#
[root@host223 ~]# /usr/sbin/serctl start
Starting SER : PID file /var/run/ser.pid does not exist -- SER start failed
[root@host223 ~]# vi /var/log/messages
[root@host223 ~]# /usr/sbin/ser -c
0(4316) ERROR: load_module: could not open module </usr/lib/ser/modulessl.so>: /usr/lib/ser/modulessl.so: cannot open shared object file: No such file or directory
0(4316) parse error (30,13-14): failed to load module
0(4316) ERROR: load_module: could not open module </usr/lib/ser/modulestm.so>: /usr/lib/ser/modulestm.so: cannot open shared object file: No such file or directory
0(4316) parse error (31,13-14): failed to load module
0(4316) ERROR: load_module: could not open module </usr/lib/ser/modulesrr.so>: /usr/lib/ser/modulesrr.so: cannot open shared object file: No such file or directory
0(4316) parse error (32,13-14): failed to load module
0(4316) ERROR: load_module: could not open module </usr/lib/ser/modulesmaxfwd.so>: /usr/lib/ser/modulesmaxfwd.so: cannot open shared object file: No such file or directory
0(4316) parse error (33,13-14): failed to load module
0(4316) ERROR: load_module: could not open module </usr/lib/ser/modulesusrloc.so>: /usr/lib/ser/modulesusrloc.so: cannot open shared object file: No such file or directory
0(4316) parse error (34,13-14): failed to load module
0(4316) ERROR: load_module: could not open module </usr/lib/ser/modulesregistrar.so>: /usr/lib/ser/modulesregistrar.so: cannot open shared object file: No such file or directory
0(4316) parse error (35,13-14): failed to load module
0(4316) ERROR: load_module: could not open module </usr/lib/ser/modulestextops.so>: /usr/lib/ser/modulestextops.so: cannot open shared object file: No such file or directory
0(4316) parse error (36,13-14): failed to load module
0(4316) set_mod_param_regex: No module matching usrloc found
| 0(4316) parse error (47,21-22): Can't set module parameter
0(4316) set_mod_param_regex: No module matching rr found
| 0(4316) parse error (65,19-20): Can't set module parameter
0(4316) parse error (75,34-35): unknown command, missing loadmodule?
0(4316) parse error (76,22-23): unknown command, missing loadmodule?
0(4316) parse error (80,23-24): unknown command, missing loadmodule?
0(4316) parse error (89,32-33): unknown command, missing loadmodule?
0(4316) parse error (93,18-19): unknown command, missing loadmodule?
0(4316) parse error (95,19-20): unknown command, missing loadmodule?
0(4316) parse error (102,19-20): unknown command, missing loadmodule?
0(4316) parse error (120,11-12): unknown command, missing loadmodule?
0(4316) parse error (124,12-13): unknown command, missing loadmodule?
0(4316) parse error (126,20-21): unknown command, missing loadmodule?
0(4316) parse error (132,17-18): unknown command, missing loadmodule?
0(4316) parse error (133,24-25): unknown command, missing loadmodule?
0(4316) parse error (137,18-19): unknown command, missing loadmodule?
0(4316) parse error (145,15-16): unknown command, missing loadmodule?
0(4316) parse error (146,18-19): unknown command, missing loadmodule?
*********************************************************
Kindly assist me how can I start the ser.
Regards,
Subhransu
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/
Hello, All!
I'm trying to use openser as SIP-router and SEMS as
voicemail/conference/etc. But then I tried it the following error
occured then openSER tried to contact SEMS:
0(31580) ERROR: tsend_datagram_ev: failed to send: (12) Cannot allocate memory
0(31580) ERROR:tm:write_to_unixsock: writev failed: Cannot allocate memory
0(31580) ERROR:tm:t_write_unix: write_to_unixsock failed
I pointed right SEMS socked in OpenSER config, but looks like no one
single byte wasn't written in in.
omega1 ~ # openser -V
version: openser 1.2.0-dev18-notls (x86_64/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST,
SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
@(#) $Id: main.c,v 1.27 2007/01/11 10:58:47 bogdan_iancu Exp $
main.c compiled on 15:27:13 Jan 15 2007 with gcc 3.4.6
omega1 ~ #
I'm using latest SEMS from SVN (rev. 192), but stable release don't work also.
Here is my openser.cfg:
========================================
if (!t_newtran()){
sl_send_reply("500","could not create transaction");
return;
};
if (method=="INVITE"){
# avp_db_load("$ru", "$avp(email)");
if(!t_write_unix("/tmp/sems_sock","conference")) {
t_reply("500","error contacting sems");
};
}
return;
========================================
What I'm dong wrong?
--
With best regards!
Hi all,
two doubts about OpenSER version 1.2:
1. This version will support MSRP sessions ? It will implements a MSRP
Relay?
2. It will support chunking messages ?
Thank you very much and Best regards,
Danilo Vilela
Researcher
Inovax Engenharia de Sistemas
Rio de Janeiro, Brazil
Hi! I am trying to use freeradius as an authentication server for ser.
I use the latest cvs version.
I am o newbee with free radius so a kindly ask for your help becouse someone who has manage to done radius support probably wouldn/t have any probelms to point me what I do wrong.
I configured ser so it sends the requests messages to radius but I encountered a strange error.
Both are running on the same machine so it is enough to use the 127.0.0.1 client configuration from client.conf.
I defined realm that would service the request comming with the "voip.touk.pl" domain part in the proxy.conf:
realm voip.touk.pl
{
type = radius
authhost = LOCAL
accthost = LOCAL
nostrip
}
I also included the digest modules in the authentication and authorization sections in the radiusd.conf.
At the end I added the user data in the users file:
hellboy Auth-Type := Digest, User-Password := "hellboy", Huntgroup-Name == "voip.touk.pl"
Fall-Through = No,
User-Name = `%{User-Name}`,
Reply-Message = "Accepted: %{User-Name}"
And know when SER sends the authentication request radius rejects it and there is this "strange" info" in radius debug
rlm_pap: WARNING! No "known good" password found for the user. Authentication may fail because of this.
Another thing wich is strange is:
modcall[authorize]: module "suffix" returns noop for request 0
When my suffix is defined in the radiusd.conf as:
realm suffix {
format = suffix
delimiter = "@"
}
here is the whole free radius degub outout:
rad_recv: Access-Request packet from host 127.0.0.1 port 32794, id=225, length=299
User-Name = "hellboy(a)voip.touk.pl"
Digest-Attributes = 0x0a0968656c6c626f79
Digest-Attributes = 0x010e766f69702e746f756b2e706c
Digest-Attributes = 0x022a34356238633234313732386462316132343230333639303633313264366333626338363135306563
Digest-Attributes = 0x04177369703a7465737440766f69702e746f756b2e706c
Digest-Attributes = 0x0308494e56495445
Digest-Attributes = 0x050661757468
Digest-Attributes = 0x090a3030303030303031
Digest-Attributes = 0x08223133304432333745384238443837353945304441383438444443323133353542
Digest-Response = "bd2e0fd81858b8114d326394b7b92001"
Service-Type = 0x0000000f00000000
SER-Service-Type = 0x0000000300000000
SER-Uri-User = "hellboy"
NAS-Port = 0x000013c400000000
NAS-IP-Address = 0x7f00000100000000
Processing the authorize section of radiusd.conf
modcall: entering group authorize for request 0
modcall[authorize]: module "preprocess" returns ok for request 0
rlm_digest: Adding Auth-Type = DIGEST
modcall[authorize]: module "digest" returns ok for request 0
rlm_realm: Looking up realm "voip.touk.pl" for User-Name = "hellboy(a)voip.touk.pl"
rlm_realm: Found realm "voip.touk.pl"
rlm_realm: Proxying request from user hellboy to realm voip.touk.pl
rlm_realm: Adding Realm = "voip.touk.pl"
rlm_realm: Authentication realm is LOCAL.
modcall[authorize]: module "suffix" returns noop for request 0
modcall[authorize]: module "files" returns noop for request 0
modcall[authorize]: module "expiration" returns noop for request 0
modcall[authorize]: module "logintime" returns noop for request 0
rlm_pap: WARNING! No "known good" password found for the user. Authentication may fail because of this.
modcall[authorize]: module "pap" returns noop for request 0
modcall: group authorize returns ok for request 0
rad_check_password: Found Auth-Type DIGEST
auth: type "digest"
Processing the authenticate section of radiusd.conf
modcall: entering group authenticate for request 0
rlm_digest: Cleartext-Password or Digest-HA1 is required for authentication.
modcall[authenticate]: module "digest" returns invalid for request 0
modcall: group authenticate returns invalid for request 0
auth: Failed to validate the user.
Login incorrect: [hellboy(a)voip.touk.pl/<via Auth-Type = DIGEST>] (from client ip4.localhost port 0)
Found Post-Auth-Type
Processing the post-auth section of radiusd.conf
modcall: entering group REJECT for request 0
radius_xlat: 'hellboy(a)voip.touk.pl'
attr_filter: Matched entry DEFAULT at line 11
modcall[post-auth]: module "attr_filter.access_reject" returns updated for request 0
modcall: group REJECT returns updated for request 0
Best
tomasz