In the ORACLE_INSTANCEconfigOPMNopmnopmn.xml file, add the

Oracle Communications Universal User Profile 20-7 ■ orclHSSPublicId: Maps to the Public User Identity IMS user profile as defined in the 3GPP TS 23.008 specification. orclHSSPublicId is the filter attribute typically used to query the HSS Sh profile. ■ orclHSSServiceProfile: In ldapsearch results orclHSSServiceProfile contains the binary value of the XML document contained in the User-Data attribute-value pair of the Diameter Response message. This XML document conforms to version 6 Sh XSD. In ldapmodify requests orclHSSServiceProfile contains the RepositoryData serviceIndicator to be updated in the following format: serviceIndicator:serviceIndicator_value ■ orclHSSMSISDN: An alternative to orclHSSPublicId, orclHSSMSISDN maps to the Mobile Station ISDN Number as defined in the 3GPP TS23.008 specification. Example Entry Generally, the Diameter data can be linked to a core record by using the Join View adapter. For example, the subscribers core record exists in the billing database but the phones actual capabilities are stored in the HSS server. The following is an example of what the data may appear like when retrieved and printed out as an LDIF file: uid=user1,ou=uup2,dc=imc,dc=com givenname=Jane sn=Doe telephonenumber=15551234567 objectclass=top objectclass=person objectclass=organizationalperson objectclass=inetorgperson objectclass=orclHSSProfile uid=user1 cn=Jane Doe title=Associate authpassword;oid={SASLMD5}CPvyoxkufZJ69n0YBwfPsw== authpassword;oid={SASLMD5-DN}JnDX4y0mf8vdN1dAHVutDw== authpassword;oid={SASLMD5-U}a3vgMwtjQKe8dEcAdxQwQ== orclHSSPublicId=user1 orclHSSServiceProfile=?xml version = 1.0 encoding = UTF-8? Sh-Data RepositoryData PublicIdentifiers IMSPublicIdentity sip:test.usertest.company.com IMSPublicIdentity PublicIdentifiers ServiceIndicationDualRingDiameterServiceIndication SequenceNumber0SequenceNumber RepositoryData Sh-Data vdejoindn=Diameter:orclhsspublicid=user1,ou=Custom,dc=hsscontractid=2001-A57 Note: Notice the orclHSSServiceProfile attribute value is stored as XML, which allows for a complex data value to be stored for this attribute without needing to reference another LDAP object.