[RADIATOR] AVP with ipv4 or ipv6 values

[Arthur Konovalov]

Hello,

Asking a little suggestion how to solve raised problem.
My system storing Diameter offline charging events to the MySQL.
Usually in the Served-Party-IP-Address AVP I have an ipv4 value and all 
works fine (printout from Wireshark):
AVP: Served-Party-IP-Address(848) l=18 f=VM- vnd=TGPP val=194.106.126.181
AVP Code: 848 Served-Party-IP-Address
AVP Flags: 0xc0
AVP Length: 18
AVP Vendor Id: 3GPP (10415)
Served-Party-IP-Address: 0001c26a7eb1
    Served-Party-IP-Address Address Family: IPv4 (1)
    Served-Party-IP-Address Address: 194.106.126.181

But some equipment send an ipv6 address:
AVP: Served-Party-IP-Address(848) l=30 f=VM- vnd=TGPP 
val=2a00:16e0:20:2:924d:7fc:ff47:7c4c
AVP Code: 848 Served-Party-IP-Address
AVP Flags: 0xc0
AVP Length: 30
AVP Vendor Id: 3GPP (10415)
Served-Party-IP-Address: 00022a0016e000200002924d07fcff477c4c
    Served-Party-IP-Address Address Family: IPv6 (2)
    Served-Party-IP-Address Address: 2a00:16e0:20:2:924d:7fc:ff47:7c4c

and there a problem arise - address not properly converted.
Trace level 4 output for this AVP shows as:
Served-Party-IP-Address: VM., 
<0><2>*<0><22><224><0>0<0><1><4><190>T/<30><17><238>s

For Diameter dictionary entry for this AVP:
VANDORATTR 10415 Server-Party-IP-Address 848 Address
For Radius converted:
VANDORATTR 10415 Server-Party-IP-Address 80 string

Radiator version 4.9 in use.

Is there any suggestion how to implement how to store both ip addresses 
variants to SQL?
Does upgrading Radiator might help there?

br,
Arthur