I've set up radius accounting in SER 0.9.6 and I'm sure I'm missing something obvious, but when it encodes the URIs for things like CalledStationID or UserName, it's encoding the non-standard characters as hex. For instance, * becomes =2A , so my URI ends up looking like sip:=2A850XXXXXXX@domain.com where it should be sip:*850XXXXXXX@domain.com
Is there something I'm missing in the table setup for the radacct table or a modparam somewhere that I missed in the README?
N.
Are you sure this encoding is done by SER ? I have never seen this, perhaps it is server-side problem ? Can you try to see what is in RADIUS packets sent by SER ?
Jan.
sip wrote:
I've set up radius accounting in SER 0.9.6 and I'm sure I'm missing something obvious, but when it encodes the URIs for things like CalledStationID or UserName, it's encoding the non-standard characters as hex. For instance, * becomes =2A , so my URI ends up looking like sip:=2A850XXXXXXX@domain.com where it should be sip:*850XXXXXXX@domain.com
Is there something I'm missing in the table setup for the radacct table or a modparam somewhere that I missed in the README?
N.
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Jan Janak -
sip