Second Content Type in XSL is Ignored Causing Call Logic to Fail
(Doc ID 1485515.1)
Last updated on MARCH 17, 2019
Applies to:Oracle Communications Service Broker - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
When trying to modify the InitialDP message content using the SMPME module, only one content type can be used, the second content type entered in the XSL file is ignored, thus not allowing data transformation between two different protocols.
In the example below, the plan was for an InitialDP arriving from the network (CAP4) to be modified and the parameters described below should have been carried in the CAP3 InitialDP towards the AS.
This fails when two different protocols are used in the Content-Type.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document