LIR Format
The LIR format is dependent on the RFC compliance for which you have configured the SBC. When configured for RFC 3588 (3GPP), the LIR contains the following information:
Vendor-Id: 9148
Supported-Vendor-Id: 10415
Supported-Vendor-Id: 13019
Vendor-Specific-Application-Id (grouped):
Vendor-ID: 10415
Vendor-ID: 13019
Auth-Application-ID: 16777216
Origin-Host: IP Address:port of the system’s source interface.
Origin-Realm: Realm-name where the system talks to this HSS.
Destination-Host: IP address of the HSS.
Public-Identity: Request URI of SIP Request
When configured for RFC 6733 (ETSI), the LIR contains the following information:
Vendor-Id: 9148
Supported-Vendor-Id: 13019
Vendor-Specific-Application-Id (grouped):
1* Vendor-ID: 13019
0*1 Auth-Application-ID: 16777216
Origin-Host: IP Address:port of the system’s source interface.
Origin-Realm: Realm-name where the system talks to this HSS.
Destination-Host: IP address of the HSS.
Public-Identity: Request URI of SIP Request
EXAMPLE - CER Format
The CER format is dependent on the RFC compliance for which you have configured the SBC. When configured for RFC 3588 (3GPP), the CER contains the following information:
CER::= < Diameter Header: 257, REQ >
{ Origin-Host }
{ Origin-Realm }
{ Host-IP-Address }
{ Vendor-Id }
{ Product-Name }
[ Origin-State-Id ]
[ Supported-Vendor-Id ]
[ Auth-Application-Id ]
[ Inband-Security-Id ]
[ Acct-Application-Id ]
[ Vendor-Specific-Application-Id ]
[ Firmware-Revision ]
[ AVP ]
When configured for RFC 6733 (ETSI), the CER contains the following information:
CER::= < Diameter Header: 257, REQ >
{ Origin-Host }
{ Origin-Realm }
1* { Host-IP-Address }
{ Vendor-Id }
{ Product-Name }
[ Origin-State-Id ]
* [ Supported-Vendor-Id ]
* [ Auth-Application-Id ]
* [ Inband-Security-Id ]
* [ Acct-Application-Id ]
* [ Vendor-Specific-Application-Id ]
[ Firmware-Revision ]
[ AVP ]