Replacing the Calling Number in the FROM Header

The Oracle Enterprise Communications Broker (OECB) provides for replacement of the calling number in SIP messages' FROM headers. Applicable messages include INVITEs that match the query, and all messages sent by the OECB to those calls callees. An example application is allowing recipient UEs to display a caller ID that is recognized by the recipient, even during an enterprise's transition to new dialing schemes.

This calling number replacement function refers to LDAP resources as the source of the replacement calling number. You configure a lookup query from the Modify LDAP config dialog to specify this source. Configured lookup queries become available in the FROM header replacement drop-down list, from which you selects their query. This selection specifies and enables the replacement.

This feature piggybacks normal LDAP lookup procedures by collecting an additional value within the LDAP query request and response sequence. The Oracle Enterprise Communications Broker replaces the FROM header of the outgoing message with this value.

While processing this LDAP response for calling number, the OECB stores the result of the query and uses it to create the FROM header user parts for applicable outgoing messages. For traffic in which there is no match to the calling number, the OECB simply uses the original calling number.

You can disable this replacement function by clearing the lookup query attribute name from the FROM header replacement field.