Terry Robert wrote:
Dear Openser, After some investigation, I discovered that the radius accounting behavior is different between openser-1.2.0-tls, and openser-1.1.1-tls. Specifically, when running the basic UAS/UAC scenario in SIPp, I observe the following:
- Openser-1.1.1-tls - generates 2 accounting start packets, 1
accounting stop. User-Name, CalledStationId, CallingStationId attributes are present.
- Openser-1.2.0-tls - generates 1 accounting start packet, 1
accounting stop. User-Name, CalledStationdId, CallingStationId attributes are missing.
You must use radius_extra parameter to add some useful info into RADIUS request. See at http://www.openser.org/docs/modules/1.2.x/acc.html#AEN319