Hi!
I'm trying to enable RADIUS accounting on OpenSER with the use of
radiusclient-ng, and using FreeRADIUS as radius server.
When I initiate or terminate a session on OpenSER, following error occurs:
Jan 10 12:21:58 [30155] ERROR:acc:acc_rad_request: radius-ing failed
I've been googling for this issue, and I've found out that some people
also had this error, but in their case RADIUS packet was sent to RADIUS
server but was rejected , but in my case it wasn't even sent to the
RADIUS server, as I saw from debug output on FreeRADIUS. As I've seen on
forums, people said that this kind of error means that something's wrong
with radiusclient-ng. I've used radiusclient-ng 0.5.5 & 0.5.6, both
with same results. Did anyone had similar problem? Does radiusclient-ng
have some kind of log or something?
Thanks for your answer!
openser.conf:
#set module path
mpath="/usr/local/lib/openser/modules/"
/* uncomment next line for MySQL DB support */
#loadmodule "mysql.so"
loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "maxfwd.so"
loadmodule "usrloc.so"
loadmodule "registrar.so"
loadmodule "textops.so"
loadmodule "mi_fifo.so"
loadmodule "uri_db.so"
loadmodule "uri.so"
loadmodule "xlog.so"
loadmodule "acc.so"
loadmodule "auth_radius.so"
loadmodule "auth.so"
loadmodule "group_radius.so"
loadmodule "avp_radius.so"
loadmodule "avpops.so"
.....
# -- acc params --
modparam("acc", "radius_flag", 1)
modparam("acc", "radius_missed_flag", 2)
modparam("acc", "log_flag", 1)
modparam("acc", "log_missed_flag", 1)
modparam("acc", "service_type", 15)
#modparam("acc", "radius_extra", "Sip-Src-IP=$si;Sip-Src-Port=$sp")
modparam("acc|auth_radius|group_radius|avp_radius", "radius_config",
"/usr/local/etc/radiusclient-ng/radiusclient.conf")
# -- group_radius params --
modparam("group_radius", "use_domain", 1)
....
Hi,
I made a small modification in openxcap version 0.9.7 in file openxcap
it enables now to specify the configuration directory and runtime directory.
This is very useful when You run openxcap in deamon mode.
xcap@venom:~/src/openxcap-0.9.7$ ./openxcap -h
usage: openxcap [options]
options:
--version show program's version number and exit
-h, --help show this help message and exit
--no-fork run the process in the foreground (for debugging)
--pid=File pid file (/var/run/openxcap/openxcap.pid)
--conf-dir=Dir config directory (/etc/openxcap)
--run-dir=Dir pid file (/var/run/openxcap)
Cheers
tomasz
Hi all.
Is it possible to configure aliases as regular expressions?
I mean:
I have to manage some accounts on a SER: each account must receive calls
on an arc of numbers.
so i have an account "foo" with (for example) 200 aliases
foo000,foo001,...,foo199.
Is it possible to configure only one alias in form of regexp?
"foo[01][0-9][0-9]" in this case
I don't want to touch ser.cfg.
Thanks a lot.
Sandro.
On Wednesday 09 January 2008, TCB wrote:
> Got it, you are right , This is set as the default for
> rewrite_prefix_column in the
> online manual( This might be a typo).
>
> Got it working 100% now , thanks
>
> modparam("carrierroute", "rewrite_prefix_column", "rewrite_host"
Good. Yes, there is a typo in the documentation. I'll fix this.
Cheers,
Henning
I wish to replace the from address in the following manner
Received From: "05551233" sip:05551233@203.89.001.001
Replaced From: "5551233" sip:18585551233@203.89.001.001
In other words I want to do what the strip and prefix commands do but on a
from header. Could anyone advise how this can be achieved in OpenSER 1.1?
Regards
Cameron
On Wednesday 09 January 2008, TCB wrote:
> Thanks Henning , i have just realised i had not set the prob,
> now the routing works but i'm afraid i have created another
> problem. For some reason the ip address is being prefixed to the
> called number.
> See below.
>
> Jan 9 14:56:02 ss-za /usr/sbin/openser[20127]:
> INFO:carrierroute:get_route_tree_by_id: searching in carrier default
> Jan 9 14:56:02 ss-za /usr/sbin/openser[20127]:
> DBG:carrierroute:get_route_tree_by_id: tree default, domain 0 : 0
> Jan 9 14:56:02 ss-za /usr/sbin/openser[20127]: DBG:core:hash_func: hash:
> 2298 % 1000 = 298
> Jan 9 14:56:02 ss-za /usr/sbin/openser[20127]:
> INFO:carrierroute:carrier_rewrite_msg: uri 0727785841 was rewritten to sip:
> 196.15.164.13727785841(a)196.15.164.13
>
> My carrierroute table looks like this:
>
> id | carrier | scan_prefix | domain | prob | strip | rewrite_host | rewrite_prefix | rewrite_suffix
> ----+---------+-------------+--------+------+-------+---------------+----------------+----------------
> 2 | 0 | 072 | 0 | 1 | 1 | 19.1.164.13 | 27 |
> 1 | 0 | 011 | 0 | 1 | 1 | 19.1.164.13 | 27 |
Hi,
your table is correct. I've seens this before, there was some user who copied
the content of rewrite_host into rewrite_prefix, i think. Could you check if the
RAM-cache on the module has also the correct data? (with 'openserctl fifo cr_dump_routes')
Do you do other RURI rewriting before the route[22] where the cr method is called?
Cheers,
Henning
I seem to be running into problems using avps and parallel forking. Is it possible to insure the invite message sent to each contact address has the same "avp checks" performed for the username portion of the URI?
Thanks,Steve
Hi all,
I'm relatively new to OpenSER (and SER for that matter). I have the
following need and can't quite figure out how to do it.
We have several Asterisk servers being used strictly for IVR purposes
(IVR cluster). We also have several Asterisk servers used for standard
telephone services and Agent/Queue services (telephone Cluster). We
would like to setup one or two OpenSER machines in front of all that
to serve the following purposes:
1) Route incoming calls appropriately to either the IVR cluster or the
telephone cluster based on the DNIS
2) Be used as LCR servers so that the telephone cluster will send all
outbound calls to and the OpenSER will determine if it needs to reach
one of our termination carriers or simply just handle it internally
(e.g. extension-to-extension calling)
3) When a caller in the IVR presses certain options, the caller may be
transferred to an agent. So, we need to take the call away from the
IVR cluster (possibly back to the OpenSER server) and redirect it to
the telephone cluster so that an agent may handle the caller
4) CDR and billing purposes
5) Ideally, all our telephone users would register with OpenSER
(instead of the Asterisk telephone cluster) and for "regular" calls,
we could just handle everything within OpenSER, and only involve the
telephone cluster if we need to redirect to voicemail or something
like that
We have read on the wiki about integrating SER with Asterisk for
voicemail. We also have some snippets, mainly from the mailing list,
about SER load balancing traffic to Asterisk. However, we really
haven't found something that could address all items above. Could
anyone provide some hits, snippets, or references to what we need in
order to accomplish these goals?
Thanks
Hi
I'm developing a "conference agent" that will receive INVITEs and invites a
list of invitees defined in the SIP INVITE message payload.
Let's say that this agent is available behind the URI
sip:conf@yourdomain.com and openser should forward all incoming "INVITE
sip:conf@yourdomain.com SIP/2.0" to my agent.
How should I configure openser to do that ?
The easiest way would be to have my conference agent to REGISTER against the
openser but I don't want to maintain this registration and I think there is
a better way to do that.
I've seen there is also a function called "ul_insert_urecord" in USRLOC
module. Might it be a possible solution to add a new entry for my conference
agent ?
Any other solution or idea ?
Regards,
Pascal