Hello all,
My gw table contains a gateway group with 5 entries which have the same
IP but different prefixes. If I use lcr module in cache mode
(db_mode=1), the same entry is always picked. If I use lcr in db mode,
then it works as expected and it picks randomly one of the five entries.
Is this a known issue? My Openser version is 1.1.x
thank you
George
Disclaimer
The information in this e-mail and any attachments is confidential. It is intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, or person responsible for delivering this information to the intended recipient, please notify the sender immediately. Unless you are the intended recipient or his/her representative you are not authorized to, and must not, read, copy, distribute, use or retain this message or any part of it. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
Hi list I need to implement multileg radius accounting on openser 1.1.x cfg.
I have configured radius to handle Sip-Leg-Source and Sip-Leg-Destination.
The problem is to configure openser.cfg propely.
In the beginning i have:
modparam("acc", "multi_leg_enabled", 1)
modparam("acc", "src_leg_avp_id", 110)
modparam("acc", "dst_leg_avp_id", 111)
then in the route that handle the invite I load the avp by radius:
avp_load_radius("callee");
But then I miss the point to have two accounting start and two accounting stop, one for each leg.
Then...if it is not possible to have two accounting records, I would liek to know how to store all the information of the two legs insede one start and one stop.
something like this one?
avp_write("$from/username", "$avp(i:110)");
avp_pushto("$ru","$avp(s:callee_callfwd)");
avp_write("$ruri/username", "$avp(i:111)");
Hope some one can drive me to understand better this situation.
Regards
Rosario
SER's configuration files can be quite complex, both to understand as a
newcomer and to manage for experts. The challenge is to make getting
started easy, while keeping the power of the configuration language.
Thus, as an example, some would like to simplify ser.cfg so they can
use: if(nated) { fix_nating() } while others need a lot more control.
The SER - Getting Started configuration files and document quickly
became a starting point for newcomers. Also, as you normally modify and
add to your first configuration, the Getting Started files have formed
the basis for many configuration files in production.
We realized that updating and adding functionality to the Getting
Started configurations quickly became time-consuming. So, we needed a
better way of managing and improving these reference configurations.
The result of these needs is a new build system for SER configuration
files where you use a configure script to generate your basic
configurations and run make to create the ser.cfg configuration file.
Once you have run configure, you can edit some (simple) configuration
files to change how ser.cfg is created. You can also add code snippets
of your own.
In order to make this system something people can grow with (and
something experts would like to migrate their configs to), the build
system is built around a generic splitting of ser.cfg into smaller
pieces, so that different logical parts of your SER config can be
managed in separate files. In its simplest form, the build system is
just an empty structure of files you can use to manage your ser.cfg
code. In its most advanced form, you can use code from the Getting
Started files and add your own code and even modify the way things work
(this last part is not yet ready in the initial version of the build
system). The idea is that migration of your ser.cfg will become easier
if you use the build system.
Finally, a logging system has been included. It offers a powerful way to
unify your logging across your ser.cfg, as well as multiple ways of
controlling when logging is done (you can for example turn off logging
for a production server, both by removing logging code and by
dynamically turning it on and off).
Well, I think that's enough for an introduction. The announcement can be
found here:
http://www.iptel.org/finally_making_ser_accessible_to_newcomers_while_keepi…
while the build system documentation (and actual code until it gets into
CVS) can be found at:
http://iptel.org/ser/doc/buildsystem
Play with it, test it, and please send your comments, ideas, suggestions
to serdev or serusers!
g-)
Sorry...
The contents follows:
Radius Protocol
Code: Accounting-Request (4)
Packet identifier: 0x61 (97)
Length: 128
Authenticator: 22B8D8F7AEE79429749AED94FBC1874C
Attribute Value Pairs
AVP: l=6 t=Acct-Status-Type(40): Start(1)
AVP: l=6 t=Service-Type(6): IAPP-Register(15)
AVP: l=6 t=Unknown-Attribute(102): 000000C8
AVP: l=6 t=Error-Cause(101): Unknown(1)
[Not enough room in packet for AVP]
Looking on the dictionary, there is no attribute 102... neither error-cause
101 or attribute value of C8. Any ideas where they are?
Edson.
> -----Original Message-----
> From: Edson [mailto:4lists@gmail.com]
> Sent: terça-feira, 24 de abril de 2007 15:10
> To: 'Juha Heinanen'
> Cc: 'users(a)openser.org'
> Subject: RE: [Users] Malformed Radius packet
>
> Humm....
>
> This is what appears:
>
>
> Edson.
> ------
> "It wouldn't be sell if it were easy..." (myself)
>
>
> > -----Original Message-----
> > From: Juha Heinanen [mailto:jh@tutpro.com]
> > Sent: terça-feira, 24 de abril de 2007 14:51
> > To: Edson
> > Cc: users(a)openser.org
> > Subject: [Users] Malformed Radius packet
> >
> > Edson writes:
> >
> > > Error: WARNING: Malformed RADIUS packet from host 127.0.0.1: packet
> > > attributes do NOT exactly fill the packet
> >
> > can you repeat this error at will? if so, check using wireshark how the
> > packet looks like.
> >
> > -- juha
Hi...
I'm receiving this message on FreeRadius (1.1.3), running RadiusClient-NG
(0.5.5.1) and OpenSER SVN 20070416-143000 on an OpenSUSE 10.2-64 bits:
Error: WARNING: Malformed RADIUS packet from host 127.0.0.1: packet
attributes do NOT exactly fill the packet
Since the dictionary used by the RadiusClient-NG and FreeRadius are the
same, any ideas from the source of this error? The dictionary is the one
provided on the Radius module, and I INCLUDE it on FreeRadius AND
RadiusClient-NG.
Edson.
Hi, all.
I am trying to setup two openser servers each running its own Mysql with
dual master configuration. Master 1 has initially all locations info in
its table.
Once master 2 comes on as mysql dual master, It seems functioning
initially however, as time goes by, I noticed that location table changes
in a way that master 1 loses all location entries when those devices
register to master 2. Eventually only locations where master 2 responded
to "REGISTER" are being in the database.
Can anyone tell me what may be going wrong?
John Kim
Guys,
since I have upgraded to 1.2 my fifo interface stopped
working.
# MI_Fifo Module Parameters
modparam("mi_fifo","fifo_name", "/tmp/openser_fifo")
modparam("mi_fifo", "fifo_mode", 0666)
Example of old command I was using in 1.1:
cat 1177428091.96-1.14-4263 (using # to mark the
command, so not used in the command)
##########################################
:t_uac_dlg:dan_fifo
NOTIFY
sip:jksdjksjdksjdkj@domain.com
.
From: sip:jksdjksjdksjdkj@domain.com;tag=3152259304
To: <sip:jksdjksjdksjdkj@domain.com>;tag=babble
Event: accounting
Content-Type: text/xml; charset=UTF-8
Call-ID: 3827705921(a)10.0.0.4
CSeq: 20 NOTIFY
.
<?xml version="1.0"?>
<accountingInfo>
<credit>0.00</credit>
</accountingInfo>
.
####################################
Anybody can help me with an example of using t_uac_dlg
with mi_fifo? I get differet errors: command empty,
pharse error before <?xml line .. etc, and I am forced
to downgrade otherwise.
Thank you in advance,
Dan Bogos
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Hi all,
frm where i can get latest rpm package for ser.
in ftp of ser there is only debian packages.
waiting for reply,
thnx
mukesh
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
I need CFU on our systems, however - it seems to work but if the forwarded
call isn't picked up within a time limit the system just drops the call.
My script is something like this;
(...)
loadmodule "tm.so"
modparam ("tm", "fr_timer", 30)
modparam ("tm", "fr_inv_timer", 10)
route{
xlog("L_INFO", "Route - $fu $rm $ru");
t_on_failure("1");
(... Some tweaking ...)
t_relay();
}
failure_route[1] {
if (!t_was_cancelled()) {
xlog("L_INFO","Failure_route[1] - redirect to callcentre");
seturi("sip:callcentre@localhost");
append_branch();
t_relay();
};
return;
}
So what happens is this;
I call a number... After 10 seconds the call "fails" and failure_route is
invoked, whereupon the call is "redirected" to the new uri. It rings for 10
seconds and then the the call is just terminated... (no call to
failure_route)...
The log looks like this;
15:30:00 Route sip:usera@localhost INVITE sip:userb@localhost
15:30:10 Failure_route[1] - redirect to callcentre
15:30:20 Route sip:usera@localhost ACK sip:userb@localhost
Any ideas? Typically I would like for the 2dn call to ring indefinitely...
// sip:gojensen@uninett.no | h323: 004710012
pstn: +47 73 55 79 23 | fax: +47 73 55 79 01