[RADIATOR] Some information lost during Diameter to Radius conversion

Arthur kasjas at hot.ee
Thu Mar 27 09:57:59 CDT 2014


In my incoming Diameter Accounting message I have the following part:

   Code:           271 (Accounting)
   Version:        1
   Flags:          0xc0 (RP)
   Application ID: 3 (Base Accounting)
   Hop-to-Hop ID:  1074033966
   End-to-End ID:  1074033966
   Attributes:
     Session-Id: .M., testmtas00.ims.xxxx.xx;11669386;2722563249;337002;1;0
     Origin-Realm: .M., emm.xxxx.xx
     Origin-Host: .M., testmtas00.ims.xxxx.xx
     Accounting-Record-Type: .M., STOP_RECORD
     Accounting-Record-Number: .M., 1
     Acct-Application-Id: .M., BASE_ACCOUNTING
     Service-Context-Id: .M., 7.Tel-IMS at xxxx.com
     Event-Timestamp: .M., 3604905721
     3GPP-Service-Information: VM.,
        Subscription-Id: .M.,
           Subscription-Id-Type: .M., END_USER_SIP_URI
           Subscription-Id-Data: .M., sip:300000000 at xxxx.xx
        IMS-Information: VM.,
           Role-Of-Node: VM., 0
           Node-Functionality: VM., 6

How to add "Subscription-Id-Data" (and possible "Subscription-Id-Type" 
too) to the Radius conversion? Currently it just dropped and I loose 
this information for the further analysis.

br,
Arthur



More information about the radiator mailing list