1. Configuration Guide
  2. IMS Support
  3. LIR LIA Lookup to Home Subscriber Server from I-BCF
  4. Compliance for the Vendor-Specific-Application-Id

Compliance for the Vendor-Specific-Application-Id

You can configure the SBC to perform CER and LIR transactions over the Cx interface in compliance with RFC 6733 with respect to the contents of the Vendor-Specific-Application-Id AVP (260). You do this by setting the rfc6733compliant option under the applicable home-subscriber-server. RFC 6733 compliance consists of several behaviors, including limiting the number of Vendor-Ids present in the CER and LIR diameter messages to one. By default, the system aligns with RFC 3588 and sends out both Vendor-IDs in the diameter messages.

In addition to establishing this compliance you can also specify the Vendor-Id for the CERs Vendor-Specific-Application-Id AVP by configuring the vendor-id option under the applicable home-subscriber-server. This option has two valid values, including vendor-id=etsi and vendor-id=3gpp.

The SBC uses both the vendor-id and rfc6733compliant options to determine the contents of the Vendor-Specific-Application-Id AVP it sends in these CER and LIR messages:

If you set the rfc6733compliant option, the SBC includes the following as Vendor-ID, based on your vendor-id setting:

  • If you set vendor-id=3gpp, then SBC sends the value 10415 as Vendor-Id.
  • If you set vendor-id=etsi, then SBC sends the value 13019 as Vendor-Id.

The SBC ignores any vendor-id setting if you have not set the rfc6733compliant option. If you have set the rfc6733compliant option, but not set the vendor-id option, the SBC adds both Vendor-Ids in the Diameter messages.

The syntax for configuring both options, with vendor-id set to etsi, follows: 

ORACLE(home-subscriber-server)# options +vendor-id=etsi 
ORACLE(home-subscriber-server)# options +rfc6733compliant

If you type the option without the plus sign, you overwrite any previously configured options. To append new options to an element's options list, prepend the new option with a plus sign as shown in the example.

You can monitor the processing of this feature in debug logs. Applicable log entries would appear as shown below.

For HSS <hss_name> the configured Vendor-Id option is xxxx

Reporting

You can monitor this feature using the show home-subscriber-server ACLI command to check connection establishment and LIR/LIA transaction detail. 

SBC_1# show home-subscriber-server
02:50:03-186
HSS Status                 -- Period -- -------- Lifetime        -------- 
                Active       High   Total      Total  PerMax    High
Client Trans          0       0       0          2       1       1
Server Trans          0       1       6       2380       4       1
Sockets               1       1       0          1       1       1
Connections           1       1       0          1       1       1                            
---- Lifetime        ----
                    Recent      Total       PerMax
LIR                      0          1       1
Sent Requests            0          1       1
Sent Req Accepted        0          0       0
Sent Req Rejected        0          0       0
Sent Req Expired         0          0       0
Sent Req Error           0          0       0
HSS  Errors              0          1       1