Re: [OpenSIPS-Users] CDRtool freeradius mysql error
In my radiusd.conf I have the following
accounting {
detail
sql
ok
}
So that should be good.
As for my /var/log/freeradius/radius.log I didn't see anything in the log
except for starting and stopping freeradius logs. I did notice in the
OpenSIPS logs that there was an error because it didn't recognize something.
I found that I needed to uncomment the following in my dictionary file on
OpenSIPS
$INCLUDE /etc/radiusclient-ng/dictionary
Once I did that noticed the following logs in /var/log/freeradius/radius.log
Thu Dec 24 10:16:04 2009 : Error: Ignoring request from unknown client
12.*.*.218:1814
Thu Dec 24 10:16:11 2009 : Error: Rejecting request 0 due to lack of any
response from home server sip:59084
Thu Dec 24 10:16:14 2009 : Error: Ignoring request from unknown client
12.*.*.218:1814
Thu Dec 24 10:16:21 2009 : Error: Rejecting request 1 due to lack of any
response from home server sip:59084
Thu Dec 24 10:16:24 2009 : Error: Ignoring request from unknown client
12.*.*.218:1814
Thu Dec 24 10:16:31 2009 : Error: Rejecting request 2 due to lack of any
response from home server sip:59084
So I had to install radiusclient-ng on the CDRTool server and set up the
client.conf and servers file. After that I see the following logs in
/var/log/freeradius/radius.log
Sat Dec 26 00:25:11 2009 : Proxy: marking accounting server 12.*.*.218:1813
for realm DEFAULT dead
Sat Dec 26 00:25:11 2009 : Proxy: marking accounting server 12.*.*.218:1813
for realm DEFAULT dead
Sat Dec 26 00:25:11 2009 : Proxy: marking accounting server 12.*.*.218:1813
for realm DEFAULT dead
Sat Dec 26 00:25:11 2009 : Proxy: marking accounting server 12.*.*.218:1813
for realm DEFAULT dead
Sat Dec 26 00:25:11 2009 : Proxy: marking accounting server 12.*.*.218:1813
for realm DEFAULT dead
I still have the same issue though. The radacctMM is still not being
created.
Saul Ibarra Corretge wrote:
>
> Hi,
>
> On 23/12/09 11:21 PM, osiris123d wrote:
>>
>> One more bit of info.
>>
>> If I start freeradius in debug mode I see the following
>>
>
> Can you see anything unusual in the freeradius logs when a call is
> accounted? Check /var/log/freeradius/
>
> Also, did you uncomment 'sql' from the accounting section in radiusd.conf?
>
>
> Regards,
>
>
> --
> Saúl Ibarra Corretgé
> AG Projects
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
--
View this message in context:
http://n2.nabble.com/CDRtool-freeradius-mysql-error-tp4200490p4217530.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Strange SIP packets
Thank you for the explanation, we'll take not of this. Probably, somebody really tries to attack our OpenSIPS - such packets come regularly. 2009/12/25 Stanisław Pitucha > 2009/12/25 Alexander : > > Can anyone explain me, what is this: > > It's a completely corrupt packet. If you're receiving that, then > whoever is sending it has some serious bugs in their software. Not > much you can do about it if you don't control the other host. > > Alternatively someone might try to crash your host, since the start of > the packet is fine (which allows to start the parsing), but then some > random characters follow. > > -- > KTHXBYE, > > Stanisław Pitucha, Gradwell Voip Engineer > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Strange SIP packets
2009/12/25 Alexander : > Can anyone explain me, what is this: It's a completely corrupt packet. If you're receiving that, then whoever is sending it has some serious bugs in their software. Not much you can do about it if you don't control the other host. Alternatively someone might try to crash your host, since the start of the packet is fine (which allows to start the parsing), but then some random characters follow. -- KTHXBYE, Stanisław Pitucha, Gradwell Voip Engineer ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Need help Nathelper + rtpproxy
Hi all
i set up rtpproxy run in same machine with opensips
my network topology:
ip phone1 (192.168.1.6)
(192.168.1.248)opensips(172.26.0.2)---(172.26.0.100)ip phone 2
media :
ip phone1 (192.168.1.6)
(192.168.1.248)rtpproxy(172.26.0.2)---(172.26.0.100)ip phone 2
i start rtpproxy :
rtpproxy -l 172.26.0.2/192.168.1.248 -f -F -s udp:127.0.0.1:2 -d
DBUG:LOG_LOCAL7
the IP Phone 2 call IP Phone 1 and i did successfull on signaling + media
when i disconnect the call i didnt see the command tear down the media session
on rtpproxy
it is normal or i mis-config the opensips.cfg, please help
Thank you
Ha
here is my opensips.cfg:
# --- global configuration parameters
debug=9 # debug level (cmd line: -dd)
fork=yes
log_facility=LOG_LOCAL7
log_stderror=no # (cmd line: -E)
children=4
port=5060
# -- module loading --
#set module path
mpath="/usr/local/lib/opensips/modules/"
loadmodule "db_mysql.so"
loadmodule "signaling.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.so"
loadmodule "xlog.so"
loadmodule "nathelper.so"
#loadmodule "snmpstats.so"
# - setting module-specific parameters ---
# -- mi_fifo params --
modparam("mi_fifo", "fifo_name", "/tmp/opensips_fifo")
# -- usrloc params --
#modparam("usrloc", "db_mode", 0)
# Uncomment this if you want to use SQL database
# for persistent storage and comment the previous line
modparam("usrloc", "db_url", "mysql://opensips:opensip...@localhost/opensips")
modparam("usrloc", "db_mode", 2)
# -- rr params --
# add value to ;lr param to make some broken UAs happy
modparam("rr", "enable_full_lr", 1)
modparam("nathelper", "rtpproxy_sock", "udp:127.0.0.1:2")
modparam("nathelper", "nortpproxy_str", "")
# - request routing logic ---
# main routing logic
route{
# initial sanity checks -- messages with
# max_forwards==0, or excessively long requests
if (!mf_process_maxfwd_header("10")) {
sl_send_reply("483","Too Many Hops");
exit;
};
if (msg:len >= 2048 ) {
sl_send_reply("513", "Message too big");
exit;
};
# we record-route all messages -- to make sure that
# subsequent messages will go through our proxy; that's
# particularly good if upstream and downstream entities
# use different transport protocol
if (!method=="REGISTER")
record_route();
# subsequent messages withing a dialog should take the
# path determined by record-routing
if (loose_route()) {
# mark routing logic in request
append_hf("P-hint: rr-enforced\r\n");
route(1);
};
if (!uri==myself) {
# mark routing logic in request
append_hf("P-hint: outbound\r\n");
route(1);
};
# if the request is for other domain use UsrLoc
# (in case, it does not work, use the following command
# with proper names and addresses in it)
if (uri==myself) {
if (method=="REGISTER") {
save("location");
exit;
};
}
# native SIP destinations are handled using our USRLOC DB
if(method=="INVITE"){
if (dst_ip == 192.168.1.248)
force_rtp_proxy("oei");
if (dst_ip == 172.26.0.2)
force_rtp_proxy("oie");
t_on_reply("1");
};
if (is_method("BYE"))
unforce_rtp_proxy();
if (!lookup("location","m")) {
switch ($retcode) {
case -1:
case -3:
t_newtran();
t_on_failure("1");
t_reply("404", "Not Found");
exit;
case -2:
sl_send_reply("405", "Method Not Allowed");
exit;
}
}
route(1);
}
route[1] {
# send it out now; use stateful forwarding as it works
# reliably even for UDP2TCP
failure_route[1];
if (!t_relay()) {
sl_reply_error();
};
exit;
}
onreply_route[1]{
if (status=="200"){
if(dst_ip == 172.26.0.2)
force_rtp_proxy("oie");
if(dst_ip == 192.168.1.248)
force_rtp_proxy("oei");
}
}
failure_route[1]{
unforce_rtp_proxy();
}
when i make call and check on rtpproxy debug and see the rtpproxy debug :
DBUG:handle_command: receiv
