Software: Mera Nextone RideRadius (Asterisk Radius Client) PortaOne Radius Client(Asterisk Radius Client)

Hardware: Cisco Quintum mediatrix

On all of these, the Calling-Station-ID is ALWAYS the same and the Called-Station-ID is always the same (the final translated number).

-----Original Message----- From: 'Jan Janak' [mailto:jan@iptel.org] Sent: Thursday, November 17, 2005 10:33 AM To: Lenir Cc: 'Klaus Darilion'; serdev@lists.iptel.org; serusers@lists.iptel.org; devel@openser.org; users@openser.org Subject: Re: [Users] RE: [Serusers] Re: [Serdev] Inaccurate Radius Accounting

On 17-11-2005 10:21, Lenir wrote:

In this case the radius proxy wont work, because you never can anticipate who hangs up the call, thus radius wont know who hung up the

call...Besides

all other voice applications/hardware (SIP and H323) that use radius do

not

behave like that, the Called-Station-ID ALWAYS remains the same, as with

the

Calling-Station-ID.

Could you name those SIP applications that behave the way you describe ?

Jan

Please read the reply below from one of the maintainers of freeradius:

"Lenir" lenirsantiago@yahoo.com wrote:

But if UserB hangs up on UserA: SER generates a stop-record where the Calling-Station-Id is UserB and the Called-Station-Id is UserA, this is the undesired and incorrect behavior.

It would appear to be a bug in SER.

To me the Calling-Station-Id and the Called-Station-Id should be the same for both start and stop records, am I right by thinking that?

Yes.

According to the developers of SER/OpenSER, this is the correct behavior, whoever sends the hangup signal (BYE or CANCEL) is considered the Calling-Station-Id, and they are unwilling to modify or create a patch to "fix" this.

What they do for something inside of SER is their business. When they generate RADIUS packets, they should follow RADIUS standards and interoperability. The expectation, as you said, is that the Calling/Called-Station-Id doesn't change during a session. If it does, it's a bug and they should fix it.

Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

-----Original Message----- From: 'Jan Janak' [mailto:jan@iptel.org] Sent: Thursday, November 17, 2005 10:33 AM To: Lenir Cc: 'Klaus Darilion'; serdev@iptel.org; serusers@iptel.org; devel@openser.org; users@openser.org Subject: Re: [Users] RE: [Serusers] Re: [Serdev] Inaccurate Radius Accounting

On 17-11-2005 10:21, Lenir wrote:

In this case the radius proxy wont work, because you never can anticipate who hangs up the call, thus radius wont know who hung up the

call...Besides

all other voice applications/hardware (SIP and H323) that use radius do

not

behave like that, the Called-Station-ID ALWAYS remains the same, as with

the

Calling-Station-ID.

Could you name those SIP applications that behave the way you describe ?

Jan.