[OpenSIPS-Devel] [ opensips-Feature Requests-2171028 ] [avp_radius] Support other strings for (user)

[SourceForge.net]

Feature Requests item #2171028, was opened at 2008-10-16 12:12
Message generated for change (Settings changed) made by bogdan_iancu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086413&aid=2171028&group_id=232389

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: trunk
>Status: Closed
Priority: 5
Private: No
Submitted By: danbogos (danbogos)
>Assigned to: Irina-Maria Stanescu (ironmissy)
Summary: [avp_radius] Support other strings for (user)

Initial Comment:
Folks,

saw that Juha had already implemented support for other $user strings than the one currently supported (caller, callee, diges).

Can these changes be ported in opensips as well?
 http://sourceforge.net/tracker/index.php?func=detail&aid=1999353&group_id=139143&atid=743023

Cheers,
DanB

----------------------------------------------------------------------

>Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2009-08-22 23:43

Message:
Done  - see http://www.opensips.org/Main/News0038

----------------------------------------------------------------------

Comment By: danbogos (danbogos)
Date: 2009-06-26 12:38

Message:
Bogdan,

your idea sounds just right to me.

In reality the things are more simple when it comes to radius: radius auth
and radius accounting packets.
So best would be if we could just have these two things in one module and
flexible like  radius_accounting module is now, to specify any kind of avps
inside.

Multumesc,
DanB

----------------------------------------------------------------------

Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2009-06-26 12:27

Message:
The AVP_RADIUS is just for fetching AVPs from a RADIUS server. I agree we
can improve the definition of the owner of requested AVPs and alos what
additional data to be sent (to help in fetching the AVPs)..
But if we explore this direction, I guess we could go for a more generic
module (radius_tools) to allow to send any kind of radius request (you can
define the radius AVPs to be pushed into) and to receive also any RADIUS
AVPs (with definitions where to go)....

Salutari,
Bogdan

----------------------------------------------------------------------

Comment By: danbogos (danbogos)
Date: 2009-06-26 11:37

Message:
Hey Bogdan,

One way could be expanding the avp module, yes. The idea is to be able to
specify the caller, calling and other extra attributes in an auth. EG: for
a prepaid call which is diverted, right now is impossible to query the
radius for maxDuration or anything else, on behalf of the forwarding
party.
I think in a proper way, the changes should be applied to Auth module, but
I have the feeling that this module usage is bounded to the presence of
Auth headers in the request, therefore not applicable in a case when the
remote party is trusted and not presenting any auth headers.

Ta,
DanB

----------------------------------------------------------------------

Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2009-06-26 11:13

Message:
Hi Dan, 

This is related to the AVP_RADIUS module, right ? to be able to fetch AVPs
for users specified via PVARs ?
If so, this is easy to add and I can implemented really fast.

Regards,
Bogdan

----------------------------------------------------------------------

Comment By: danbogos (danbogos)
Date: 2009-06-23 14:12

Message:
Hey Guys,

quite a long time back I have requested some enhancements to the radius
modules.
Anything planned on it? Do  u have another strategy for radius modules?

Ta,
DanB

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086413&aid=2171028&group_id=232389