LDAP Request Data MDC
MATRIXX Engine stores Lightweight Directory Access Protocol (LDAP) callout request data in the MtxLdapRequestDataExtension MATRIXX Data Container (MDC).
You can create custom extensions of the MtxLdapRequestDataExtension MDC and use them for custom LDAP call out requests. You can populate fields in MtxLdapRequestDataExtension MDCs by using
data modify actions or selective updates. You can use the following sources for LDAP callout request fields:
- A constant value — A string that is converted to the destination field type.
- A subscriber field — From the MtxSubscriberObject MDC or one of its descendants.
- A field in a message — From the MtxDiamRoMsg, MtxTcapMsg, or a descendant of these MDCs.
- A field in an LDAP response — From the MtxLdapResponseDataExtension MDC, or one of its descendants. The MDC type is determined based on whether calling or called party data is
used, and the MDC key of the LDAP response extension data or its descendant.Note: The LDAP response must have been created already from an LDAP request for an earlier message in this charging session, or from an earlier PreRating profile for this network message. If it has not been created already, then the requested field is not be present.
MDC Format
MtxLdapRequestDataExtension Fields describes the base MtxLdapRequestDataExtension fields:
Field | Type | Description |
---|---|---|
DestinationServer | STRING | (Optional) Specifies the logical pod for LDAP. |
RequestString | STRING | (Optional) Specifies a simple LDAP callout request. |