ASAP Is Unable To Communicate With Network Elements As OTD Is Used At Source Systems

(Doc ID 1982735.1)

Last updated on MARCH 03, 2015

Applies to:

Oracle Communications ASAP - Version 7.0.0 and later
Information in this document applies to any platform.


Oracle Traffic Director (OTD) is implemented at source while sending a request from ASAP to the Network Elements.

However, a user learned that Oracle Traffic Director can only be configured to listen on a single port number that is an integer between 1 and 65535.
It can not be configured to listen on all ports or a range of ports.

But as per their knowledge ASAP is based on multi-threaded architecture, and it can spawn multiple connections with Network Element via different available ports.

Also, such ports are decided at runtime internally by ASAP, they cannot predict that a request would be routed via a particular port. This is causing an issue with using  OTD.

The customer is seeking a work around or alternative so that they  can proceed with such an arrangement where Oracle Traffic Director is used at the source. Can this be implemented in ASAP?



Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms